Opened 6 years ago

Last modified 3 years ago

#15640 new enhancement

Check for possible unneeded only_* restrictions

Reported by: naoliv Owned by: team
Priority: normal Milestone:
Component: Core validator Version:
Keywords: turn restriction Cc:

Description (last modified by naoliv)

Could JOSM detect some unneeded only_* turn restrictions, like the attached example?

The left example is valid (since we have multiple branchs), while the example on the right side has an unneeded only_straight_on (ie, there is only one way to follow and we don't need a restriction to say the obvious)

This could be possibly implemented by counting the number of connected ways at the via node. If = 2 then probably it's unnecessary.


Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2017-12-05 00:58:56 +0100 (Tue, 05 Dec 2017)
Build-Date:2017-12-05 02:33:31

Identification: JOSM/1.5 (13194 pt_BR) Linux Debian GNU/Linux testing (buster)
Memory Usage: 769 MB / 7168 MB (420 MB allocated, but free)
Java version: 9.0.1+11-Debian-1, Oracle Corporation, OpenJDK 64-Bit Server VM
Screen: :0.0 1600x900, :0.1 1280x1024
Maximum Screen Size: 1600x1024
Java package: openjdk-9-jre:amd64-9.0.1+11-1
Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-13
VM arguments: [--add-modules=java.activation,, -Dawt.useSystemAAFontSettings=on]
Dataset consistency test: No problems found

Attachments (2)

example.osm (1.9 KB ) - added by naoliv 6 years ago.
example2.osm (3.5 KB ) - added by naoliv 6 years ago.
Another example, with 3 ways

Download all attachments as: .zip

Change History (5)

by naoliv, 6 years ago

Attachment: example.osm added

comment:1 by naoliv, 6 years ago

Description: modified (diff)

by naoliv, 6 years ago

Attachment: example2.osm added

Another example, with 3 ways

comment:2 by anonymous, 6 years ago

Maybe there would be a u-turn possible but not allowed (emergency only).

comment:3 by skyper, 3 years ago

Keywords: turn restriction added

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 naoliv.
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.