Currently, we have three hardcoded building points on our map. We also have a method that can retrieve all the unique buildings in our database.
However, when adding a new fountain with a new building (Ex: if you added a fountain in SCI), then it can't automatically add a new building point for SCI onto the map. This is because it doesn't have any coordinate information for the new building, since the user is never prompted to input any coordinate information.
This leads to an issue, where the fountains are in the database, but can't be seen on our map since their building doesn't have its own point.
This can be fixed in two ways:
Hardcoding every current UTD building
Problem: If UTD ever opens new buildings, then an administrator would have to go into the code and add a new point themselves. It isn't particularly difficult to document a tutorial on how to do so, but ideally we should find a better solution. Another issue would be for them to actually figure out what the building's coordinates are, but this is already available on Google Maps by right clicking the building pin.
Adding an "Add Building" page that lets you move a point, name it, and place it there.
Problem: Much more work, but allows admins to easily add buildings and graphically place them rather than figure out the coordinates.
I will implement the first solution, and the other solution can be a stretch goal for the future.
Currently, we have three hardcoded building points on our map. We also have a method that can retrieve all the unique buildings in our database.
However, when adding a new fountain with a new building (Ex: if you added a fountain in SCI), then it can't automatically add a new building point for SCI onto the map. This is because it doesn't have any coordinate information for the new building, since the user is never prompted to input any coordinate information.
This leads to an issue, where the fountains are in the database, but can't be seen on our map since their building doesn't have its own point.
This can be fixed in two ways:
I will implement the first solution, and the other solution can be a stretch goal for the future.