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
{{ message }}
This repository was archived by the owner on Jan 9, 2024. It is now read-only.
The problem is that there a lots of tags in OSM files.
Maybe we could come up with some specific key/values ?
Also how would you represent those tags in the output (as csv file or database) ?
I certainly think this would be useful, however it may be implemented. There are a lot of erroneous tags in the OSM for my own city that prevent pedestrian access to edges that do have footpaths and crossings. Once I've run this tool, all I know is that an edge has been deemed accessible or not, but not the tag that was used to determine this. If I had this information in the output, I could make appropriate adjustments.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be useful if the node and way tags could be included in the output.
The text was updated successfully, but these errors were encountered: