-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nodes have also an elevation #418
Comments
Work also for saddles 😄
|
Some examples in France (probably in other countries).
Extract of this overpass query |
May I offer my thoughts? Adjacent nodes can have identical names, that is no problem for integrity, routing and maintenance. Node labels are useful for users, on the planner display and planner output. If we want to show the difference based on elevation, it would be enough to append the ele value (if present) to the name for display and planner output. |
Does two or more adjacent nodes with the same name but with different elevation are the "same" node ? Should be checked, but in point of view of french operators it seem different nodes. |
Start- and endnode can have the same name (example). If on the ground, on the guideposts, the nodes are distinguished from each other by the elevation, then that should be reflected in the node name I think. |
In France in moutains, we could have several node with the same name but with different elevations.
In practice operator don't manage "nodes" but they manage guideposts.
So we have several guidepost with the same tag
name
and different tagele
.Currently we must handle this manually and this is error prone (merge
name
andele
value of the guidepost, add a separator)Could you manage also the tag ele for nodes and use it automatically in the label of the node?
See KISS: keep it simple discussion in the wiki.
The text was updated successfully, but these errors were encountered: