You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#11 should probably be implemented first since it's more straightforward and this item naturally builds off of it
Our custom map layers are Google spreadsheets that should be easily editable by their maintainer(s). However, there's no easy mechanism to help contribute to keep this data up-to-date (hey! xyz closed down, abc just opened), or volunteer to become a maintainer of a map layer.
On an easy level, this might just mean displaying links to suggestion mode in the backing Google sheet for a map layer, or maybe working more closely with the OpenMap API to automate functions around maintainers once hackgvl/OpenData#27 is implemented
The text was updated successfully, but these errors were encountered:
I think it's more of just implementing hackgvl/OpenData#27 into the mapping application if this map application is intended to be the flagship consumer of the mapping api 😄
So as to say, I think this issue is pretty dependent on whatever solution is landed on in that ticket
#11 should probably be implemented first since it's more straightforward and this item naturally builds off of it
Our custom map layers are Google spreadsheets that should be easily editable by their maintainer(s). However, there's no easy mechanism to help contribute to keep this data up-to-date (hey! xyz closed down, abc just opened), or volunteer to become a maintainer of a map layer.
On an easy level, this might just mean displaying links to suggestion mode in the backing Google sheet for a map layer, or maybe working more closely with the OpenMap API to automate functions around maintainers once hackgvl/OpenData#27 is implemented
The text was updated successfully, but these errors were encountered: