GH avoiding specific street results in strange routing

Hey there. I am using the routingAPI. It seems like GH is avoiding the street “bahnhofsstraße”. I cant find any reason for this. Already tried it with different routing providers and they are working quit fine with the OSM map material for this street.
Any help appreciated.

payload:

{
  "points": [
    [
      10.0019536,
      48.3944937
    ],
    [
      10.0256572,
      48.4017838
    ]
  ],
  "details": [
    "road_class",
    "surface"
  ],
  "profile": "car",
  "locale": "en",
  "instructions": true,
  "calc_points": true,
  "points_encoded": false
}

1 Like

This is due to maxweight:conditional=no @ delivery Way: ‪Bahnhofstraße‬ (‪116353640‬) | OpenStreetMap
Will investigate deeper. Is this a tagging issue. What does it mean?

Probably it means no access for weight>7.5t and the weight restriction can be ignored if delivery purpose?

This tagging is very rare (<200) and a central Europe thing:

image

GraphHopper considers “no” as a restriction like for the tagging access:conditional=no @ delivery.

If “none” would be used instead, which makes more sense here (or at least less ambiguous) and is also more frequent > 5500, then this would work and IMO is also more correct:

  • “no” generally negates something that follows it (e.g., no restriction), but it is IMO not the standard way to express the absence of a value in OSM tagging.
  • Using “no” in this context could be misinterpreted as an attempt to negate the existence of the maxweight:conditional tag itself or at least introduce confusion, as “no” is not commonly used to represent “unlimited” in OSM schemas.
1 Like