Concrete Surface Treated as Other

Open Source Routing Engine
#1

Hi,

We’ve come across a problem where “CONCRETE” surface types appear to be treated as “OTHER”, so are not being recognised as a suitable surface for bikes in our custom model.

Here’s an example, where the route follows a cycle path and the surface changes from “Asphalt” to “concrete:plates”:

Route with unexpected detour

Correct route

Is this a known issue or are we doing something wrong here? My understanding from the following page, is that “OTHER” is treated as the worst surface:

https://javadoc.io/static/com.graphhopper/graphhopper-core/3.0-pre5/com/graphhopper/routing/ev/Surface.html

#2

Have a look into Way: 1077235613 | OpenStreetMap

This notation xy:ab is not something that we currently consider - I created an issue for it.

Note that “OTHER” is not necessarily the worst surface but just something not in the list.

#3

OK, thanks. For now we might consider allowing “Other” if it is also a bike network, as that should hopefully be fairly safe.