|
In a recent question, heunigreenfreak asked how to edit large structures. He is using the iD editor with which it's not really possible. Respondents suggested he use JOSM, which is much more capable. I have been using JOSM for quite a while and feel fairly comfortable with it but yet am unsure about the best way to do what heunigreenfreak asked. In particular, there is a very large multipolygon (natural=wood) in northern Thailand that has grown to include 769 members. It has many "outer" segments and many "inner" segments. When one is modifying it, adding inner regions for example, one should first download the entire structure, a task that leaves plenty of time for a long coffee break. (id:1599039). Its become very unwieldy and I would like to break it into several smaller parts, say along river valleys or highways, areas that are not actually wooded. So how does one go about splitting such a large structure in JOSM? It cannot be entirely seen in one normal download and worse, because of its size any edits run the risk of encountering conflicts if such editing isn't done in a short time frame. Resolving potentially numerous conflicts is what keeps me from trying this on my own. Anybody care to provide a step-by-step guide to splitting large areas in JOSM?
showing 5 of 6
show 1 more comments
|
|
If there are no common attributes of the areas (for example a name or similar) there is nothing stoping you from moving individual outer polygons to their own multi-polygons (with any enclosed inner polygons), or even better (if small enough and no holes) to normal polygons. Doing this has a minimal risk of causing conflcts and is simple to carry out without causing the need for artificial breaks. 1
Thanks for your suggestions. I couldn't begin to figure out which inner multipolygon belongs with which outer one. This thing is a monster! 325 km north to south and 150 km wide. I'm whittling away at it by combining inner polygons that delimit a major highway one at a time. When I reach the outer edges, I'll be in a better place to split it.
(08 Jan '15, 13:16)
AlaskaDave
It's too big for even mapki to process at the moment!: http://osm.mapki.com/history/relation.php?id=1599039 Further to what Simon says above, if you're working on a section at the edge of it I'd artificially split the bit that you're working on into a new outer polygon (with new ways separating it from the rest of the monster if needed), then make sure each new relation has only the correct inners for it (and not the other one).
(08 Jan '15, 13:33)
SomeoneElse ♦
1
I can see your problem, however there do seem to be natural features, for example I just saw a river that is not in OSM on the imagery, that should make the monster easier to break up at obviously places.
(08 Jan '15, 13:44)
SimonPoole ♦
2
The project I had envisioned is simply too complex for me at this point. Some of the ways are part of the Burma-Thailand border, some have roles in two or more relations. Grrrrr.... However, I have learned a bit from fooling around. Adding and removing ways from relations is easier than it was before. As I split out areas that are not wooded (creating & expanding inners) I had to redefine certain inner ways as outers to make the resultant multipolygon correct. I will continue working at it piecemeal and eventually maybe the overall task will become clearer. Thanks for your comments.
(10 Jan '15, 10:05)
AlaskaDave
|
meta: If your question is "step-by-step guide to splitting large areas in JOSM", I think it would be better to title it that way, don't you think? And a general best-practise question would deserve another question.
Perhaps it would but the question that inspired mine has that title and I was intending for user heunigreenfreak to notice it. It's a general title for what I want to know.
As for the second part of your reply, I don't know the difference between asking for help and asking for a "best practices" tutorial. All I know is that I can't proceed without some help.
@AlaskaDave: with "general best-practise question" I meant a question which does not focus on a specific sub-topic of working with "large structures" (like your question here does).
Just to make sure, are you downloading the entire area (Download from OSM) or just the relation and its members (Download object)? I'm not sure what you meant by "It cannot be entirely seen in one normal download."
@Paul_012 That's a great help. I made a few changes using that technique just now but it raises new questions. I have not been able to download the "entire relation" because it seems to be composed of many individual smaller relations. The id I gave in the original post, 1599039, is only one piece of the giant one. When splitting other portions of the giant, how can I be sure I'm not splitting a "shared" way, that is, one shared by two or more pieces of the puzzle?
I find it difficult to even describe the problem in words LOL. Perhaps there is a "parent relation" - if so, I cannot find it.
@AlaskaDave: relation 1599039 has no "parent relation" – otherwise it would be listed at the bottom of the linked data page with the text "Part of Relation xxxx".
Alternatively, you could also see this in JOSM if you select the relation in the TagsMembership dialog (see the example image on the docu page). This way you also find out to which "pieces of the puzzle" a "shared" way belongs (select the way to be inspected before, of course).