You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: paracetamolo [Submitted to the original trac issue database at 2.00am, Thursday, 29th August 2013]
Mountains paths for hiking/cycling are rendered without ref or name. Normally a path has an official ref, like 401, and then it could have a common name, like 'Alpine summer walk'.
In some specialized maps like opencyclemap or waymarkedtrails.org or maps.refuges.info only the name is rendered.
I think that, at the appropriate zoom level, the ref should always be rendered, like in all tourism maps, to uniquely identify the path, and in the small number of cases where the name is defined it should be rendered together. In case of space issues the ref seems more important/informative than the name.
This issue prevents the use of osm for tourism hiking/cycling which is a usecase where it could shine.
The text was updated successfully, but these errors were encountered:
Reporter: paracetamolo
[Submitted to the original trac issue database at 2.00am, Thursday, 29th August 2013]
Mountains paths for hiking/cycling are rendered without ref or name. Normally a path has an official ref, like 401, and then it could have a common name, like 'Alpine summer walk'.
In some specialized maps like opencyclemap or waymarkedtrails.org or maps.refuges.info only the name is rendered.
I think that, at the appropriate zoom level, the ref should always be rendered, like in all tourism maps, to uniquely identify the path, and in the small number of cases where the name is defined it should be rendered together. In case of space issues the ref seems more important/informative than the name.
This issue prevents the use of osm for tourism hiking/cycling which is a usecase where it could shine.
The text was updated successfully, but these errors were encountered: