Editing bits of roads with loads of routes on them is extremely tedious. I had to remove two pieces of road from ~10 different relations and replace them with another piece of road.
There must be a better way to define routes than relations.
Editing bits of roads with loads of routes on them is extremely tedious. I had to remove two pieces of road from ~10 different relations and replace them with another piece of road.
There must be a better way to define routes than relations.
Discussion
Comment from mnirek on 5 September 2013 at 16:11
Generally, you would know if you are doing it the way it has to take. And sometimes a big hurdle. They do not do badly, even worse.
Comment from Pieren on 6 September 2013 at 09:17
I always campaigned against route relations on segments. This is the easy way fine for data consumers but not for contributors (the real ones, not the ones just talking or developing software). My alternative solution is to define the routes by junctions nodes lists. It’s still not perfect but I noticed that junction nodes are relatively more stable than any other elements in the OSM dataset. And it makes routes modeling less prominent.
Comment from malenki on 6 September 2013 at 13:28
There is “replace geometry” in utilsplugin2 with which one can work very conveniently.
Other way to make this edit:
* split the way with the relations on it two times
* unglue the nodes of the segment
* insert the segment with all the relations where you like