Pathway=* for ways not used by or intended for cars

[julcnx]

@_MisterY

It looks to me that this is the growing consensus at the moment. Is that a fair assessment?

Another no. See:

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 eq…

There’s definitely a growing consensus to find a solution, but I haven’t seen agreement on the best approach yet. Update: created a survey to get a better sense where everyone stands.