The Description templates, including ValueDescription and KeyDescription, provide a description box for describing keys and tags. One of the included parameters is status= which describes the approval or community acceptance status of the key or tag, representing a feature or attribute.
See also: Proposal status values
Keys and tags which have been proposed should have a link to the proposal:
- statuslink: name of the proposal page, for linking
This should always be included for tags with status approved or rejected, and should be included for all tags and keys which had a proposal, even if the status is now de facto or in use - approval statuses which do not require a previous proposal.
de facto tags have usually been accepted and supported by the community, and the majority of features in the database are tagged with one of these tags. Most are listed at Map Features. The wiki highlights these statuses in green.
approvedfeatures and attributes have completed the Proposal process and been approved by a majority or supermajority vote. Mappers and database users can expect these tags to usually be well-thought-out and developed. The original proposal should be available as a small link just to the right of the word "approved".
de factois used to describe the map features and attributes which have been strongly adopted by mappers, without completing the approval process. Many of these tags were developed in the early years of OpenStreetMap, before the approval process developed, but others developed organically more recently. A tag that is marked
de factois used by many mappers and has been used very frequently often for a number of years.
- Note that some of them were rejected in proposal process.
discardable status values are highlighted in red,
rejected is highlighted in dark grey right now. These tags are usually not found on the list of Map Features, except as historical notes, in the case of some
deprecated tags. There may be another tag with the same meaning which is more widely used and supported.
abandonedtags were proposed, but the proposal process for tag was abandoned before completing it. Note that tag itself may independently have in use or de facto status even if the proposal was abandoned.
discardabletags have no use. Usually they were created by an import or clean-up process, but are no longer needed. Editor applications may automatically discard these tags without requiring human intervention.
deprecatedtags should not be used any more. Usually there is an
approvedreplacement tag which has been discussed and agreed upon by the community, and is listed in the page deprecated features
rejectedtags were proposed and discussed, but not approved by the community. Read the linked proposal to see the reasons for rejection. Another tag may be suggested instead
Note that for
rejected proposals, while the initially proposal may have been abandoned, the tag may be in active use and have a different status such as
de facto or
in use. Even some widely used tags began life as an
"In use" status
in use status has a wide range of meaning. These tags have not been voted on and discussed like
approved features and are not as widely used as
de facto tags, but may still be the most common existing tag for a feature. Only a small percentage of
in use tags have been added to the list of Map Features.
in usefeatures and attributes are currently being added to new features by mappers, but have not been
approvedor used so widely to become
- Some feature and attribute tags with
in usestatus are fairly widely used, but are too new or not yet common enough to be tagged as
de facto. However, they may change to
de factoafter another year or two of frequent use.
in usetags are very common, but somewhat debated. There may be another
in usetag with a similar meaning, or the tag may be used for several different features with a similar name.
in usetags may be only used in one country or by a small number of mappers.
in usetags were rejected when proposed, but are still being used but not often enough to qualify as "de facto".
- There is some noticeable usage but not high enough to qualify as de facto. Note that tag that is part of established tagging scheme would require far less use to qualify as
de factothan some completely new tagging scheme.
Proposal process values
voting are used for tags that are currently in the proposal stage. These tags may soon be approved, or the proposal may be abandoned or rejected.
If tag has enough uses to qualify for
de facto or
in use this values should be used instead.
draft: the feature has a draft proposal being written, but may not yet have been discussed widely.
proposed: the feature has been formally proposed and discussed on the Tagging mailing list and at the proposal Talk page, but it has not yet reached the voting stage.
voting: the feature is currently being voted on as part of the approval process, and will soon be either approved or rejected. Recently rejected features might be re-written and resubmitted for approval.
Status may be not defined at all (
There may be also explicit
undefined that gives no extra info or benefit.
Some tags do not qualify for any of the statuses above: the tags below have not been approved or rejected, are not commonly being used by mappers, but do have a wiki page and have some examples in the database.
obsoleteis used for a tag which is no longer found in the database. It may have been replaced by a new tagging method.
importedis used for a tag which was added from an external database.
For a listing of newly approved, added, changed or deprecated tags, see Changelog.