History of proposals to fix highway=path ambiguity – and a wayforward?

As far as I can see, 4. is the only solution to the highlighted problems. The great majority of renderers only support the top-level tags (e.g. highway) and do not have any interest in supporting additional tags, besides maybe sac_scale and mtb:scale for some outdoor apps. Dangerous situations, and rescue operations happened because end-users relied on general-purpose apps (not the outdoor ones) and followed along a path they expected to be a hiking trail, not e.g. a climbing route requiring equipment.

I favor this approach because we can move forward step by step. The main challenge, besides agreeing on the scope of each new tag, will be to get enough votes since there seem to be quite a few members opposing categorically new tags.

1 Like