Greetings! I'm working on tracing some underground pipelines, and I'm using an Overpass XML script (via overpass turbo) to bring existing map nodes, ways, and relations (man_made=pipeline) in to JOSM to build upon. Some pipelines have existing (and inaccurate) TIGER data for various segments. Unfortunately, the TIGER data frequently has nodes which are shared with other map elements such as roads, political borders, rivers, etc. etc. When I delete these TIGER pipeline ways after replacing them, the shared nodes throw conflict warnings because JOSM wasn't aware of their shared nature. I need some assistance in crafting an Overpass XML script which will include not only the (man_made=pipeline) ways, but also any ways which are "shared" by the nodes I retrieve in the process. That way, when I delete the TIGER pipeline after its been replaced, any other element which may share a node is there and remains intact, causing no conflicts. Are there any experts who can lead me down the right path for this? I'd appreciate it greatly! asked 02 Jan '14, 15:34 greggerm |
After you have selected the ways, you probably have a
(The last recurse-down makes sure that the "shared" ways also get loaded completely.) answered 02 Jan '14, 15:58 tyr_asd Bingo. I had to make some adjustments to account for my poor script writing, but adding the new up/down has accomplished the goal. Thanks so much!
(02 Jan '14, 17:12)
greggerm
|