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
We need to decide what the process for a new city onboarding into the project looks like.
To make this project scalable and attract interest, the process should be as self-serve as possible. An interested city needing to send an enquiry, wait for documentation on data standards, send across data files, wait for those to be loaded and then finally receive notice that something is available will likely push the project beyond the interest of most (not to mention introduced a lot of administration on our part).
Could a process be developed that basically allows a new city to:
enter their city name into a web form, that kicks off the process of building segments & intersections from OSM
view our data standards on crashes & concerns, format their available data accordingly and upload it to a public storage service (probably their own initially, as long as the URLs are accessible)
indicated via another form that they have additional data ready to go, and submit the paths to it
have the app pick up their data and integrate it into the predictions
The text was updated successfully, but these errors were encountered:
We need to decide what the process for a new city onboarding into the project looks like.
To make this project scalable and attract interest, the process should be as self-serve as possible. An interested city needing to send an enquiry, wait for documentation on data standards, send across data files, wait for those to be loaded and then finally receive notice that something is available will likely push the project beyond the interest of most (not to mention introduced a lot of administration on our part).
Could a process be developed that basically allows a new city to:
The text was updated successfully, but these errors were encountered: