Proposal:Relation:permit

Relation:type=permit
Proposal status: Abandoned (inactive)
Proposed by: Doctau
Tagging: type=permit
Statistics:
Draft started: 2010-05-13


See Proposed features/access=permit for a possible replacement.

The proposal suggests a way to indicate that permits are required for certain areas.

Use cases

  • Parking
  • National parks


  • Be able to specify different permit classes on the members, so you don't need to have multiple relations for similar permits
  • Have a role type which indicates where to get the permits

Rationale

Applies to


Usage Tags and Values


Tags

Key Value Discussion
typepermit
url*Where to get information about the permits
feeyes, noWhether permits require payment (or are free)

Members

Way or Node Role Recurrence? Discussion
requirezero or moreplaces which require a permit to use. Should have access=permit tag
require:*zero or moreplaces which require a permit of a specific class to use, of all the classes specified after the colon. Should have access=permit tag
require_any:*zero or moreplaces which require a permit of a specific class to use, of any the classes specified after the colon. Should have access=permit tag
supplyzero or moreplaces which permits are available from
This article is issued from Openstreetmap. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.