Expand on the Parking API mockup data

a24timsv commented

2026-04-13 12:35:27 +00:00

Collaborator

Currently the Parking API shows 4 areas with 3 spots per area. This needs to be expanded in way that reflects the schools parking areas and spots, the occupied data will be mockup.

a24timsv self-assigned this

2026-04-13 12:35:30 +00:00

a24timsv added the

API

label

2026-04-13 12:35:58 +00:00

hGustavs commented

2026-04-13 13:22:49 +00:00

Owner

As discussed in the customer meeting, I feel that it is suitable to reflect the 3 main parking areas as closely as possible including relative coordinate layout of parking spots. At the very least the following customizations.

We want to easily add new parking areas and
New parking spots in existing areas
Disable non-usable parking spots temporarily or permanently

As discussed in the customer meeting, I feel that it is suitable to reflect the 3 main parking areas as closely as possible including relative coordinate layout of parking spots. At the very least the following customizations. * We want to easily add new parking areas and * New parking spots in existing areas * Disable non-usable parking spots temporarily or permanently

a24sakma was assigned by a24timsv

2026-04-16 10:41:26 +00:00

a24timsv commented

2026-05-15 10:19:27 +00:00

Author

Collaborator

The parking API now currently can send data to the frontend via its endpoints. It is currently missing a visualization of the data and some admin tools should be implemented.

We might not be able to implement the admin tools this year as we don't have users or roles at the moment, but a frontend component might be plausible.

The parking API now currently can send data to the frontend via its [endpoints](https://git.webug.se/Andras/BoundlessFlowCampus2K/wiki/Parking-endpoints). It is currently missing a visualization of the data and some admin tools should be implemented. We might not be able to implement the admin tools this year as we don't have users or roles at the moment, but a frontend component might be plausible.

a24sakma commented

2026-05-25 07:27:06 +00:00

Collaborator

How long I am came a long on this issue:

What is done

The below branch contains information on adding a new spot. It has a form and a way to handle to post the data

What is left

the update of existing areas and disable temporarily or permanently is not implemented.

What to consider before starting this issue

The new structure has changed and files may have been moved. This code is from early weeks of 2026. So Make sure you rebase the branch or you just copy paste what you need.

How long I am came a long on this issue: ## What is done The below branch contains information on adding a new spot. It has a form and a way to handle to post the data ## What is left the update of existing areas and disable temporarily or permanently is not implemented. ## What to consider before starting this issue The new structure has changed and files may have been moved. This code is from early weeks of 2026. So Make sure you rebase the branch or you just copy paste what you need.

Screenshot from 2026-05-25 09-22-36.png

18 KiB

a24sakma removed their assignment

2026-05-25 07:27:15 +00:00

a24timsv was unassigned by a24sakma

2026-05-25 07:27:24 +00:00

Rows
Columns

Expand on the Parking API mockup data #264

What is done

What is left

What to consider before starting this issue