Skip to content

OSM tag highway=path often unsuitable for bikes - and how to customize this behavior #7495

@jeanbaptistevilain

Description

@jeanbaptistevilain

Hi,
First of all, thank you for your continuous work on this project (and apologies in advance if this is not the right place to ask this).
For context : OTP 2.9.0, we are working on an OTP deployment in a non-urban territory. We have received feedback from users who warn us about OTP route segments that are said to be suitable for cycling, while in reality they are pedestrian only and sometimes dangerous for bikes.
After investigating the OSM tags, these segments are tagged as highway=path and therefore fall under the PEDESTRIAN_AND_BICYCLE modes in the default OsmTagMapper.
I understand that ideally the OSM data should be completed to tag those ways as non suitable for bikes, but in the meantime I would like to know how we can work on a custom TagMapper to make sure we don't push dangerous itineraries to cycling users.
More specifically, if we come up with a CustomTagMapper, should we rebuild the whole shaded jar locally and use it, or can we just add it in the classpath in a separate jar to avoid building the whole OTP jar locally ?
Thanks in advance for your help on that topic

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions