> Access=private works fine, then (along with access=public > andaccess=permissive). Preferably with an additional tag (or relation) > withsome indication of who is allowed to park there. > Maybe access=customer isn't needed after all.
How about something like: access=private permitted=patron/permit_holder/staff There's probably other valid permitted types, but this organization would handle the following types of situations quite well: - Public parking lot (ie you come here and pay to park, regardless of where you're going): access=permissive - Store parking lot for customer: access=private, permitted=patron - Store parking lot for staff only: access=private, permitted=staff - Parking lot for monthly parkers: access=private, permitted=permit_holder A relation to define what businesses are served by the lot could be something like: type=parking_use Where you'd have member roles: lot: a parking lot(s) for_use_by: the business(es) that the parking is intended for. I think in most circumstances it is probably pretty clear which business a parking lot is intended for though. Tyler _______________________________________________ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
