Expand on the Parking API mockup data #264

New issue

Open

opened 2026-04-13 12:35:27 +00:00 by a24timsv · 2 comments

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

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.