Opened 10 years ago

Last modified 4 years ago

#10263 new enhancement

better validation of roundabouts

Reported by: sommerluk Owned by: team
Priority: normal Milestone:
Component: Core validator Version:
Keywords: roundabout Cc:

Description (last modified by sommerluk)

Please provide a better check/validation of roundabouts.

1.) A so-called “hamburger roundabout”, in spite of its name, isn’t a roundabout. By defination, a roundabout is where the circle traffic has priority and where you have a non-transversable island. So it would be great if JOSM could recognize when doing the check before uploading some data. JOSM could check

– that all the ways that are connected to a way with roundabout=yes are
connected at the same side of the roundabout
– and that they end at the roundabout and do not cross the roundabout
– otherwise (=if you have a so-called “hamburger roundabout” instead of a
real roundabout) the tag junction=roundabout must be removed.

2.) Check if the way(s) of the roundabout form really a circle. The wiki recommands to make roundabouts as one single – closed – way. In OSM there are many cases where peoples split the roundabout in various ways. But maybe JOSM could check at least, if the roundabout (also when it is composed by various ways) forms a closed way.

Attachments (0)

Change History (6)

comment:1 by sommerluk, 10 years ago

Component: CoreCore validator

comment:2 by Don-vip, 10 years ago

Type: defectenhancement

comment:3 by Don-vip, 9 years ago

Keywords: roundabout added

comment:4 by Don-vip, 8 years ago

Ticket #12428 has been marked as a duplicate of this ticket.

comment:5 by mdk, 4 years ago

I think the second check is not always correct. See

Last edited 4 years ago by Klumbumbus (previous) (diff)

comment:6 by sommerluk, 4 years ago

Description: modified (diff)

I think the second check is not always correct.

Okay, I’ve made a bad descripton. Instead of “forms (geometrically nearly) a circle“ I would like to say “forms a closed way“. I’ve updated the bug description.

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user.
Next status will be 'needinfo'. The owner will be changed from team to sommerluk.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from team to anonymous. Next status will be 'assigned'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.