OSM Tag Combination "highway=living_street" and "bicycle=designated" prevent Drive routing. #2374
Comments
Hi @robludwig, that file is indeed the right place to derive permissions from OSM tags. Adding a rule for a really specific set of tags, as you have done, fixes the problem. But the root of the problem may be the more general rule here: /* bicycle=designated, but no bike infrastructure is present */
setProperties(props, "highway=*;bicycle=designated",
StreetTraversalPermission.PEDESTRIAN_AND_BICYCLE, 0.97, 0.97); This makes all roads with |
robludwig
added a commit
to robludwig/OpenTripPlanner
that referenced
this issue
Dec 7, 2016
novalis
added a commit
that referenced
this issue
Dec 30, 2016
Re #2374. Allow Cars on highway=*;bicycle=designated
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As mentioned in the Google Group I had a problem routing Drive Only trips on an OSM street tagged "living_street" in the Palo Alto area (steps to reproduce are in the linked thread).
I found that the specific combination of tags "highway=living_street" and "bicycle=designated" made the edge bike/walk only. Thanks to input from Nawak Khurshid, I found that I could edit DefaultWayPropertySource to add an entry for that specific combination:
setProperties(props, "highway=living_street;bicycle=designated", StreetTraversalPermission.BICYCLE_AND_CAR, 2, 2);
and routing worked.I know car routing is not a priority of the project, but is this the preferred way to make this edit or is there a better place to put the change that I'm not seeing?
The text was updated successfully, but these errors were encountered: