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
My proposal is not addressed by the documentation or examples
Existing issues
Nothing similar appears in an existing issue
What problem does your feature proposal solve?
Consider https://www.openstreetmap.org/way/6878440
This street is only bidirectional for buses.
When searching for a path for city buses, edges along this way are not considered.
What is your proposed solution?
Expose oneway exception types to graph API, similar to network_type.
Contributing guidelines
Documentation
Existing issues
What problem does your feature proposal solve?
Consider https://www.openstreetmap.org/way/6878440
This street is only bidirectional for buses.
When searching for a path for city buses, edges along this way are not considered.
What is your proposed solution?
Expose oneway exception types to graph API, similar to network_type.
https://wiki.openstreetmap.org/wiki/Key:oneway:bus
https://wiki.openstreetmap.org/wiki/Key:oneway:psv
https://wiki.openstreetmap.org/wiki/Key:oneway:bicycle
graph = ox.graph_from_polygon(bounds, network_type="drive_service", oneway_type="bus")
should consider
oneway:bus
if it exists,oneway
otherwise.What alternatives have you considered?
Workaround considered: Download graph, change oneway attribute, rebuild graph
However, it seems to me that
graph_from_gdfs
does not consideroneway
.Additional context
Example: https://www.openstreetmap.org/way/6878440
The text was updated successfully, but these errors were encountered: