-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Street space evaluation #370
Labels
Comments
3 tasks
Thinking about how to represent this, heads-up @mvl22, any thoughts let me know. |
Width requirements:
TBC... |
Red-amber-green for parking. |
Robinlovelace
added a commit
that referenced
this issue
Mar 21, 2024
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This aims to:
Will cover:
High level approach:
This involves
Building to building (B2B) widths (critical)
Obtaining and processing data on carriageway widths
Incorporating estimates of road widths in segment level results
Making results available in attributes at the segment level:
Example of open pavements data: https://www.arcgis.com/apps/webappviewer/index.html?id=783e530d92994246bcaeb7419437fd78
Currently ignores:
We may be unable to publish the results in the user facing web app if we use licenced data.
The text was updated successfully, but these errors were encountered: