[Tagging] Specify "private" - e.g. resident or employee parking lots

[Minh Nguyen]

Vào lúc 15:10 2022-01-30, Alex đã viết:
> Hey,
> 
> for objects such as parking lots that cannot be used by the general 
> public (access=private), it can be helpful to specify the "private" user 
> group more precisely, e.g. residents or employees. (This can also be of 
> interest for paths/ways, barriers or other objects.)
> 
> I can find several taggings for this in the database (none of them 
> documented, as far as I can see), in particular:
> 
> 1: access=private + private=residents/employees
> 2: access=private + access:residents/access:employees=yes/designated/...
> 3: access=private + residents/employees=yes/designated/...
> 4: access=residents/employees.
> 
> Which tagging would you use/prefer? I like the approach using 
> "access:residents" etc., as it would offer the widest range of tagging 
> possibilities (e.g. a more precise distinction of access for this or 
> even several special user groups) and makes clear, that this information 
> is an access tag. A similar syntax seems to be already in wide use in 
> particular for disabled parking spaces (access:disabled) resp. was once 
> proposed for parking spaces and it's various user groups. 
> "access=residents" or "access=employees" each have thousands of uses, 
> but seem inappropriate to me because they break with typical access 
> conventions/classes.

The recently revised and approved parking:condition=* tagging scheme for 
street parking [1] calls for clarifying a residents-only restriction 
like this:

parking:condition=residents
parking:condition:residents=A (residents with permit A)

It follows that other iterative refinement would be possible, such as:

parking:condition=permit
parking:condition:permit=B
(residents/nonresidents with permit B)

parking:condition=customers
parking:condition:customers=Acme Bar & Grill
(street parking reserved for patrons of a particular abutter)

However, I don't think it's been stated anywhere that these 
parking:condition=* values are meant to be aligned with the 
general-purpose access restriction tagging scheme, even if they happen 
to overlap with access keys.

Aligning these tagging schemes would be desirable. Often, there's no 
real distinction between the kinds of parking conditions at parking lots 
versus on the street. In some places, all parking spaces are mapped as 
individual areas, so it's important that the general-purpose access 
tagging scheme be expressive like the parking:condition=* scheme. Or 
maybe we should just allow parking:condition=* to be tagged on all of 
these things?

[1] 
https://wiki.openstreetmap.org/wiki/Proposed_features/Parking_lane_conditionals

-- 
minh at nguyen.cincinnati.oh.us