Bug: Better defaults for road surface types

Follow

Anna Ronkainen

• October 16, 2023 09:56
• Edited

It seems that Hammerhead defaults the road surface type to pavement whenever an explicit surface tag is missing from the OSM data for the road in question. (Komoot btw also does the same thing, which is probably responsible for 90+% of the routes it is infamous for...)

More intelligent defaults would probably require quite a bit of work (and would probably also have to depend on the region as well), but as a minimum, could we at least get highway=track (and possibly others) categorized as not paved? Currently, even with the “prefer pavement” option the Karoo wants to reroute me via something like this (actual example, categorized as track but no surface tag):

(I mean, I totally still would ride through that with a road bike, but the route was just a pseudo U-turn that didn’t make any sense in the first place.)

0

• 

  Anna Ronkainen

  • October 16, 2023 13:53

  I’d say highway=bridleway is another one that is not paved almost by definition, and highway=road (unspecified, basically) and highway=unclassified might be worth considering as well. Documentation: https://wiki.openstreetmap.org/wiki/Key:highway

  (For instance in Finland there are even unpaved highway=secondary roads, but with anything from tertiary and above I would definitely just rely on the surface tagging instead.)

  0

  Comment actions Permalink
• 

  Anna Ronkainen

  • May 19, 2024 11:41

  Still broken... Another recent creative reroute example, still while using the “prefer asphalt” option, this one was tagged as highway=path with surface=ground in OSM data:

  

  0

  Comment actions Permalink

Please sign in to leave a comment.