Sometimes I have been using the tag "no_exit" instead of "noexit". How can I correct this across all my edits?
Thanks for help
Comment from smsm1 on 9 June 2011 at 06:13
There is currently no easy tool as far as I'm aware. Best to slowly change them as you come across them. If they are in a small area you can load that area into JOSM do a search and then edit that tag on all of them at the same time.
Comment from 42429 on 9 June 2011 at 07:54
Use XAPI or JXAPI to download all data tagged with "no_exit", then change them with JOSM to "noexit" and upload them again.
JOSM und XAPI sind nicht wirklich einfach, aber erlernbar!
Comment from Nachtspazz on 9 June 2011 at 07:57
@smsm1 & FK270673: Thanks a lot for the hints. I guess I have to get familiar with JOSM. Up to now I have been using Potlatch2 only.
Comment from Pink Duck on 9 June 2011 at 08:46
Is there any point recording noexit at all? The data in OSM as used by routing algorithms will determine itself that there's no exit, and they may need to route inside a noexit section too. Other mappers just want to know if somewhere needs more attention, so perhaps use FIXME="Incomplete way" instead on the final node?
Comment from Andy Allan on 9 June 2011 at 08:53
I'm with Pink Duck on this one - there's no point in tagging no_exit, the software figures out whether it's a dead end or not. It's a cargo cult tag.
Comment from Nachtspazz on 9 June 2011 at 11:02
About tagging "noexit":
It is in the group of the top 300 tags
and very popular especially on German OSM maps:
The OSM Wiki explains why it is useful (e.g. Quality Assurance):
If there are good reasons to abandon the tag, please document it in the Wiki.
Comment from Sanderd17 on 9 June 2011 at 15:07
The noexit tag is useful for mapping two roads that are close but not connected. Otherwise armchair mappers could think they are connected and connect them.
Comment from marscot on 9 June 2011 at 21:10
also handy for roads that are still to be finished
Comment from seav on 12 June 2011 at 08:04
noexit is one of those tags useful for a map-in-progress, not for a "complete" and fixed map.
Comment from chriscf on 14 June 2011 at 21:42
"noexit" should potentially represent one and only one thing - a sign on the ground that tells you that there is not a through route along the adjacent way. Occasionally, these signs do appear on roads that aren't cul-de-sacs, but then that's why we have the "destination" access value. Ideally, we should not be adding machine-readable tags to represent calculable characteristics. It should be plainly obvious to a routing engine that there is no advance from a cul-de-sac (for at least some mode of transport). In the case of nearby nodes, add a note to the node indicating that mappers shouldn't join them, and hopefully the people editing in the area will read it and take heed. Machine-readable tags are of little use for issues which will inevitable require human attention. Certainly I remove "noexit" anywhere I come across them, and replace them with something more suitable.
* First item
* Second item
1. First item
2. Second item