On mobile, on train, apologies for lack of formatting. :) Sarah - the problem is that when you say “one single simple instruction to the mapper: sort your route“, the instruction might be simple but carrying it out isn’t.
Let’s say we have a cyclist, new to OSM, who wants to add a newly opened section to an existing route. As Peter says, doing this to said specification “usually requires lots of JOSM”. The steps involved to do this in sorted order are: 1. spend half the afternoon trudging through contradictory pages on the OSM wiki to find out what you have to do 2. apparently it involves this thing called “JOSM”. Download that 3. apparently that involves this thing called “Java”. Download that too 4. learn to use this 80s throwback of a GIS program with the UI of a startled warthog 5. find route sorting stuff in JOSM somewhere 6. make edit 7. get shouted at by sociopaths in changeset comments because unwittingly you did something wrong (I have elided most of the intermediate steps.) That isn’t how OSM works. It might be how Wikipedia works but we are better than that. _If_ route ordering is to be expected, then the burden needs to be on the editing software, not the mapper. That means invisible support in iD, P2, and I’m guessing Vespucci and Go Map (I don’t know what their current support is like). And tbh the burden of providing patches is on the few people who are asking for it. Certainly I’m happy to implement something in P2 if it’s an afternoon’s work and I’m given a fully fleshed out algorithm which copes with the partly loaded relations that are standard for an online editor, but I’m not going to spend two days of dev time on something for which there is no great clamour outwith a couple of people on the tagging list. cheers Richard -- Sent from: http://gis.19327.n8.nabble.com/Tagging-f5258744.html _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
