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

General talk
,
140

Just trying to get a sense of where everyone stands right now:

What’s the best approach to improve the scope of highway=path?
  • Add a sub-type, e.g., highway=path + path=*
  • Introduce a new top-level tag, such as pathway=*, with values based on usage or function, similar to how highway works.
  • Move use cases to new highway=* tags, reserving highway=path solely for outdoor trails
  • Reclassify outdoor paths as highway=trail, limit highway=path to multi-use pathways, and relocate other use cases
  • Create new highway=* tags for all existing use cases, and treat highway=path as a placeholder for unknown/unverified paths (similar to highway=road but for pathways)
  • Just keep things as they are and add the proper physical tags.
  • Stick with the current setup but add a proper foot scale or grade.
0 voters

Notes:

  • Other use cases include pathless routes, multi-use paths, scrambling, climbing, and mountaineering routes.
  • Feel free to select multiple options if you’re unsure between different approaches