Opened 7 years ago

Last modified 7 years ago

#13444 new enhancement

A Validator Warning should be produced when Parking Access Tag Keys not correct

Reported by: anonymous Owned by: team
Priority: minor Milestone:
Component: Core validator Version:
Keywords: parking access destination Cc:


What steps will reproduce the problem?

  1. Create a polygon
  2. Add amenity=parking access=destination
  3. Observe no error

What is the expected result?

Parking access keys should be limited to {yes,permissive,private,customers}. Validator should produce warning

What happens instead?

Incorrect keys are accepted

Please provide any additional information below. Attach a screenshot if possible.

Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2016-08-11 21:54:24 +0200 (Thu, 11 Aug 2016)
Build-Date:2016-08-11 22:36:05
Relative:URL: ^/trunk

Identification: JOSM/1.5 (10786 en) Linux Ubuntu 16.04.1 LTS
Memory Usage: 462 MB / 871 MB (177 MB allocated, but free)
Java version: 1.8.0_91-8u91-b14-3ubuntu1~16.04.1-b14, Oracle Corporation, OpenJDK 64-Bit Server VM
Java package: openjdk-8-jre:amd64-8u91-b14-3ubuntu1~16.04.1
Dataset consistency test: No problems found

+ ColumbusCSV (32796)
+ DirectUpload (32699)
+ buildings_tools (32796)
+ colorscheme (32699)

Attachments (0)

Change History (3)

comment:1 Changed 7 years ago by Klumbumbus

Component: CoreCore validator

comment:2 Changed 7 years ago by Klumbumbus

The exact definition of access=destinantion depends on the laws of the country. So I think that access=destinantion on a parking lot can be valid in some circumstances (more opinions?).

The most used access values for amenity=parking according to taginfo are:

  • private -> OK
  • customers -> OK
  • yes -> OK
  • permissive -> OK
  • destination -> could be OK in my eyes
  • public -> duplicate of yes in my eyes
  • unknown -> already has a warning
  • no -> OK
  • designated -> already has a warning

comment:3 Changed 7 years ago by Don-vip

Keywords: parking access destination added; tags removed

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