Better handling of roundabouts

[hungerburg]

Yesterday I created a cycling route that passes by a roundabout. Now the elevation profile has a gap.

Currently, the route enters the roundabout, goes full circle and then jumps to the exit point.

Making the route only follow the actually used part of the roundabout would remedy the gap.

Seems like a nice pastime to ponder over a solution?

[Nekzuris]

I think the issues is your cycling route, it shouldn't have the whole roundabout in it, you should split the roundabout way and only add the used part of the roundabout in the route relation, that should solve your gap in elevation profile.

But the issues with the gap in elevation profile is still present with route that use one way twice (in both direction)

[ppete2]

No: splitting roundabouts just to get closed, linear relations is not good mapping practice. Many OSM mappers even refuse this kind of splitting. A roundabout is one common, single feature, it has the same topograhic logic like a punctual crossing. In OSM editors like JOSM's relation editor, a roundbout logically is a punctual feature and therefor not seperating a route: The route stays connected even if the roundabout is not splitted.

I support the feature request of better integration of unsplitted roundabouts into WMT's elevation profile/GPX-download. But i also understand that this is not a trivial task since WMT hast to create it's own split logic.

[lonvia]

At thi point, WMT doesn't support split routes per direction at all for the elevation profile and/or route download. Once it does, it will split roundabouts appropriately. No need to split them manually.