|
iD's 'transform to circle' tool is pretty nice to tweak roundabouts which were previously uneven or had too few nodes. However this doesn't work if the roundabout consists of several ways due to parts of it being part of different relations. is there a workaround? |
|
You could make a new helper-way which uses all the roundabout's nodes and make this way a circle. Then delete the helper-way again. However, not that easy to do. I would not recommend to do this with iD. iD seems not to allow multi-selecting individual nodes of different ways. I could not get it done in Potlatch 2, too. It does work in JOSM (although I think it does not have a function to insert more nodes into a circle, still making a circle of your existing nodes would work). However, you need to be careful about the positions of the nodes - they may represent in- and out- connections. So, likely this is also no good option. All in all: do it careful and rather manually. You can overlay another (new) helper-way which is a perfect circle to have a template for manual node insertions and movements. Remember to delete your new helper-way before saving. 1
Using JOSM if there are enough nodes, I would not use the helper way, but simply select all the ways that are part of the roundabout, <control>+<shift>+N (using Windows, MacOS may use a different modifier) to select all of the nodes belonging to them, and then "O" (to align the nodes in a circle)
(13 Dec '13, 18:08)
MCPicoli
1
@Pieren, this is not a policy discussion/vote here (also you should not downvote my answer just because this is a not a kind of mapping you like – at least it seems to me like you did therefore). Also note that I did not recommend to split. The split roundabout is the current state of the data.
(16 Dec '13, 13:41)
aseerel4c26 ♦
1
@Pieren: regarding the issue itself: there are objective "pro" reasons (which you are likely ignoring). Just one: If you use your inflated-node roundabout in a route relation you get a wrong route length.
(16 Dec '13, 14:51)
aseerel4c26 ♦
@aseerel4c26: once you know that the route relation contains full roundabouts, it's easy to compute the correct length. Again, my advice is the best workaround : don't split roundabouts for routes.
(16 Dec '13, 15:07)
Pieren
@Pieren: sure, there are ways to get the correct length (estimation by leaving away half of a roundabout length or even primitive routing through roundabounts). All of this require additional processing which may be not a good thing. And just because there are workarounds it does not mean that there are no "pro" reasons as you claimed.
(16 Dec '13, 15:15)
aseerel4c26 ♦
showing 5 of 6
show 1 more comments
|
|
It's not directly answering your question but in my country, we tend to not split roundabouts for route relations. In routing, we consider a roundabout like an intersection node (it's just an inflated node ;-). The question still exists when e.g. part of the roundabout is a bridge but it's much less common than route relations. 3
This is a very error-prone suggestion :(. Please don't do this unless you are very familiar with relations. And even then it is better to use an editor which doesn't have this shortcoming.
(09 Dec '13, 14:20)
scai ♦
Spliting a roundabout for route relations IS very error-prone. My first advice is to not do this. If the way is split for other reasons like a bridge, it has nothing to do with relations and is therefore easy to follow and maintain during the merge and re-split (simple tags on simple ways).
(09 Dec '13, 15:50)
Pieren
|
