Proposed features/customer
| Customer only access | |
|---|---|
| Status: | Proposed (under way) |
| Proposed by: | MHohmann |
| Tagging: | access=customer |
| Applies to: | node,way,area |
| Definition: | Access is restricted to customers of a specific store, bank, restaurant or other amenity. |
| Rendered as: | Affects rendering similar to other access restrictions (not part of this proposal). |
| Draft start: | 2011-01-15 |
| RFC start: | 2011-01-15 |
| Vote start: | |
| Vote end: | |
Contents |
Description
This tag applies to objects which may be used or accessed only by customers of a specific store, bank, restaurant... Examples of such objects are:
- parking lots
- service ways
- entrances
- toilets
Motivation
Often the owner of a store or restaurant, who also owns objects like a parking lot or toilets, grants access rights only to customers. This very common situation is not covered by access=permissive, which means that access rights are granted to everyone, or by any access=* tag. Therefore it makes sense to introduce a new access tag.
Tagging
Recommended / combinations:
- A site relation could group the object to which the customer access applies (e.g., a parking lot) and the amenity (e.g., store or restaurant) whose customers may access this object.
Rendering
This should differ both from public access and from private / prohibited areas. A rendering similar to, but still different from, access=permissive is recommended (not part of this proposal).
Comments
Please use the discussion page for comments.
