Opened 3 months ago

Last modified 3 months ago

#18014 new enhancement

Validator marks no_entry and no_exit-restrictions as an error

Reported by: Peilscheibe Owned by: team
Priority: normal Milestone:
Component: Core validator Version:
Keywords: no_exit no_entry restriction Cc: Peilscheibe


There are the well documented restriction relations "no_entry" and "no_exit" ( which are allowing

  • one or more "from"-members for a no_entry-restriction
  • one or more "to"-members for a no_exit-restriction

However the JOSM-validator is recognizing such relations as an error.

Please update the validation rules accordingly so these relation types are accepted with the valid member numbers as described.
The mentioned restriction types started to be documented somewhen in 2012 and I'm not aware of any issues with them as the definitions are pretty straightforward.


Attachments (0)

Change History (1)

comment:1 Changed 3 months ago by Don-vip

They are not used much (682 and 254 times).

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to Peilscheibe
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment

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

Note: See TracTickets for help on using tickets.