Best way to avoid bike routing in alleys

[Mark Stosberg]

Alleys can have poor visibility at intersections are more likely to have broken glass-- they are often not a good choice for routing bike trips.

Docs recommended adding the `bicycle=discouraged` tag ( https://docs.opentripplanner.org/en/latest/Configuration/ ) as an option, but in four cities I queried, this is rarely used.

From reading "DefaultWayPropertySetSource.java", it appears that routing on ways with highway=service;service=alley is allowed: 

https://github.com/opentripplanner/OpenTripPlanner/blob/8adb5591cef21f25b1a1d5c71a2b3fc78c860837/src/main/java/org/opentripplanner/graph_builder/module/osm/DefaultWayPropertySetSource.java

What's the recommended way to avoid having bike trips routed in alleys?

This reference reminds us that some cities have city code that alleys are not to be used as throughfares, so perhaps it's generally not a good idea to use alleys for routing anyway?

https://help.openstreetmap.org/questions/60950/tagging-alleys

Thanks, 

     Mark

[Leonard Ehrenfried]

Hi Mark,

If you can identify a set of OSM tags that you'd like to avoid you can create your own WayPropertySetSource and either give those alleyways a really bad safety score, leading them to be chosen only as a last resort, or outright ban them by setting the traversal permissions to pedestrian only.

A less clean way would be to modify the DefaultPropertySetSource to do the same.

By the way, OTP is looking for contributors from the US to maintain a US way property set source:

https://groups.google.com/d/msgid/opentripplanner-dev/CAADz6OG3w5A8726ayfk5WRnVHi_zrc1zJad622SB_sY0j2UqyA%40mail.gmail.com?utm_medium=email&utm_source=footer

Background: right now all of the active OTP(2) developers are European and it's possible that decisions that affect routing in the US will be overlooked.

Best

--

  Leonard Ehrenfried

  https://leonard.io

--

You received this message because you are subscribed to the Google Groups "OpenTripPlanner Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to opentripplanner-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/opentripplanner-users/f97e4b32-672d-4d09-a8c4-85eab8aab894n%40googlegroups.com.

[Mark Stosberg]

Leonard,

Thanks for the reply. Is there a file currently that contains US-specific exceptions that we could submit a patch to?

      Mark

[Leonard Ehrenfried]

Since that part of OTP was developed mainly in Portland the default is already quite US-specific. My gut feeling is that it hasn't been updated all that much in last few years.

If you'd like to contribute a US one, you could take inspiration from the one for Germany that I maintain: 

https://github.com/opentripplanner/OpenTripPlanner/blob/dev-2.x/src/main/java/org/opentripplanner/graph_builder/module/osm/GermanyWayPropertySetSource.java

Even creating a new one with just the alleyway exception would already be an acceptable start, which could lead to more fine-tuning further down the road.

All the best.

--

  Leonard Ehrenfried

  https://leonard.io

To view this discussion on the web visit https://groups.google.com/d/msgid/opentripplanner-users/6db0dcce-adf5-404d-9231-665ea3c3c7can%40googlegroups.com.