#17844 closed enhancement (fixed)

validation: maxspeed on nodes

Reported by: josm.sanspourriel Owned by: team
Priority: normal Milestone: 19.06
Component: Core validator Version: tested
Keywords: Cc:


JOSM warns for a suspect tag combination when maxspeed is used on nodes.
But if the node has a traffic_sign:forward or traffic_sign:backward using a speed limitation value, for instance FR:B14_(50) this is perfectly valid according to the wiki. Osmose proposes to integrate Mapillary traffic signs and the right way IMHO is to tag the way (compatible with JOSM checker) but also the traffic sign (which seems to be an error according to JOSM).

Attachments (0)

Change History (2)

comment:1 Changed 15 months ago by Klumbumbus

Milestone: 19.06

comment:2 Changed 15 months ago by Klumbumbus

Resolution: fixed
Status: newclosed

In 15194/josm:

fix #17844 - don't warn about maxspeed on suspicious object if traffic_sign:forward or traffic_sign:backward is present

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.