Template:KeyDescription

Template documentation

This documentation is transcluded from Template:KeyDescription/doc. (Edit | history)
Note to editors: Please don't categorize this template by editing it directly. Instead, place the category in its documentation page, in its "includeonly" section.
This template has a sandbox (Edit) and testcases (Edit) for editors to experiment.

Note: This template is used on a lot of pages. In order not to put too much load on the servers, edits should be kept to a bare minimum.
Please discuss proposed changes on the talk page first.
Editing a template causes all pages that use the template to be re-rendered. If the Template is used often, this can put a lot of load on the servers since it fills up the job queue. [statistics]

Intro

This template provides a description box suitable for keys. As of December 2018, a backing data item is created either by a bot or by hand for all pages that use this template. The bot copies many of the template parameters to the data item, making them available in a machine-readable format.

This template uses corresponding data item for some of the missing parameters (e.g. key, image, description, group, status, on*, ...), so in theory most of the template parameters are no longer needed, but they should not be deleted just yet -- some tools like TagInfo do not consume data items directly, but instead try to parse template parameters. Once TagInfo is updated, it will be ok to delete parameters -- just placing {{KeyDescription}} template without parameters to a properly named Key:* or Lang:Key:* page will show values from the data item in the correct language (for other pages key and lang parameters will still be needed).

To view or translate the data item, click the grey pencil icon next to the description, or click the OpenStreetMap Wiki item link in the left sidebar. If the description is different from the data item, it will also show a red pencil icon to edit the wiki page itself. They should be made identical. Description should be one or more complete sentences (start with a capitalized letter, ending with a period), max 250 symbols. Do not use any wiki markup. English label should be identical to the key (usually a lower case word). When translating, make sure to add description, but labels are optional. Do not copy English label if it is the same. Some languages like to add "nativekey" - a localized alternative to the original key. Lastly, add any number of alternative names for the key to the "also known as" (aliases) column. Some tools use aliases to offer a quick key search.

All data item logic is done by Lua code in Module:DescriptionFromDataItem.

Displaying and styling is done by Template:Description.

Copiable example with only required and suggested parameters

{{KeyDescription
| key           = 
| image         = 
| description   = 
| group         = 
| onNode        = 
| onWay         = 
| onArea        = 
| onRelation    = 
| requires      = 
| implies       = 
| combination   = 
| seeAlso       = 
| status        = 
| statuslink    = 
}}

Usage

Full parameter set in vertical format

Vertical list

Prerequisites

Brief instructions/notes

{{KeyDescription
| key           = 
| nativekey     = 
| image         = 
| description   = 
| osmcarto-rendering      = 
| osmcarto-rendering-size = 
| group         = 
| website       = 
| url_pattern   = 
| onNode        = 
| onWay         = 
| onArea        = 
| onRelation    = 
| requires      = 
| implies       = 
| combination   = 
| seeAlso       = 
| status        = 
| statuslink    = 
}}

 
 
 
 
 
 
rendered icon
 
 
website
 
 
 
 
 
 
 
 
 
status

 
 
The key name in native language
 
 
May not work if osmcarto-rendering-size is not set
Usually 14

If a field name is listed in the prerequisites column it is a prerequisite for the field to the left.

Parameters

The following parameters are recognised:

Feature description

key: the key being described (required).
nativekey: the key name in native language.
image: the name of an image to be used to illustrate the feature. For better code readability, it is recommended to copy the page title from the file page instead of from URL:
File:OpenStreetMap logo 2011 - social circle.svg (the same as the file page title)

File:OpenStreetMap_logo_2011_-_social_circle.svg (use spaces instead of underscores)

Image:OpenStreetMap_logo_2011_-_social_circle.svg (use File: instead of Image:)
description: a short description of the feature in question. Description is preferable to a single word, as it reduces chances for miscommunication - author of a definition is unable to assess whatever one specific word is ambiguous to all readers. Should start with a capital letter and end with a period. Must not contain any wiki markup or HTML. Must be less than 250 symbols. (required)
osmcarto-rendering: icon in the standard tile layer
osmcarto-rendering-size: size of the icon in pixels (usually 14)
group: the name of the broader group or category to which this feature belongs (optional). Use lower case.
website: the main website(s) associated with this feature (optional).
url_pattern: pattern to generate deep-link URLs for instances of this feature (optional).

Feature usage

The following parameters are optional. They are however recommended as their absence means that these uses have still not been decided or the use of the tag is still experimental.

onNode: yes if the feature being described is suitable for use on node elements, no otherwise.
onWay: yes if the feature being described is suitable for use on linear (non-area) way elements, no otherwise.
onArea: yes if the feature being described is suitable for use on area elements, no otherwise.
onRelation: yes if the feature being described is suitable for use on (non-multipolygon) relation elements.

Additional information

requires: a list of tags which are necessary (often higher/lower in hierarchy) for this tag and must be set to give its actual meaning (optional)
implies: a list of tags/values which are assumed when absent; see below for examples; tag them explicitly for exceptions (optional)
combination: a list of additional tags which are useful in combination with this one (optional); see below for examples
seeAlso: references to additional pages which may be of interest (optional)
status: the approval status of this feature (should be filled in); possible values include:

content template

approved: the key or tag has successfully completed the approval process
de facto: the tag is in widespread use, and while it was not approved in a proposal process, it has a widespread acceptance among mappers⁽²⁾
deprecated: deprecated tags that are discouraged from being used
discardable: tags that are so useless that editors remove them automatically, for example Tag:odbl=clean
imported is used for a tag which was added from an external database
in use: the key or tag is in use⁽²⁾
obsolete: a key or tag which is no longer found in the database
proposed: the key or tag has been proposed to be used (but not yet approved) and usage of this tagging is minimal⁽¹⁾
undefined or (empty): unclear situation (this may be actually useful in case where data item has invalid value and it is not entirely clear which one should be used and someone is not interested in editing data items)
voting: the key or tag is currently being voted on as part of the approval process

Notes:

By "usage of this tagging is minimal" it is meant that there is minimal usage world wide, for example a tag that has been used 50 times. Note that depending on the tag low usage may be normal, generally properties will have a much higher usage than specific features.
in use and de facto can be used for tags that are in use but have proposal in some stage that was not approved. For example, a heavily used tag with rejected proposal can have de facto status.
inuse was sometimes applied instead in use, the same with defacto instead of de facto. It is highly preferable to avoid this.

statuslink: name of the proposal page, for linking

Language support

lang: (optional) the BCP 47 language tag (most often based on a ISO 639-1 alpha-2 language code, or ISO 639-2 alpha-3 technical language code, or ISO 639-3 alpha-3 language code otherwise, possibly followed by script/region/variant subtags) for the language used to document this feature: this will generate aspects of the description box in the specified language, if translations are available. If a language code is not specified, the default will be determined from the full name of the current page using {{Langcode}}.

Advanced formatting parameters

These parameters can generally be ignored by the majority of users. They are available for fine-tuning the presentation of the description box, and are useful for including in examples, or embedding in tutorial pages.

class: specify the CSS class of the HTML table used to form the description box.
float: specify the CSS float value of the table: set to none to disable the standard right float.
style: the CSS style to be applied to the HTML table: overrides |float= if present.
languagelinks: set to no to inhibit links to corresponding pages in other languages (used for example on this documentation page).

Examples

Note: In these examples, long lines have been wrapped for convenience. The advanced formatting parameters, class, float, style and languagelinks are not show, as their values are specific to use as examples.

{{KeyDescription
| key         = dessert
| image       = 
| description = A dessert is a sweet dish, typically served towards the end of a meal.
| group       = cuisine
| onNode      = yes
| onWay       = no
| onArea      =
| onRelation  = yes
| requires    =
| implies     =
* {{Tag|edible||yes}}
| combination =
* {{Tag|meal|dinner}}
* {{Tag|sweet||yes}}
| seeAlso     =
* {{Tag|dessert|cheesecake}}
* {{Tag|dessert|gateau}}
| status      = imaginary
| lang        = en
}}

dessert

Description

A dessert is a sweet dish, typically served towards the end of a meal.

Group: cuisine

Used on these elements

Implies

edible=yes

Useful combination

meal=dinner
sweet=yes

TemplateData

This is the TemplateData for this template used by VisualEditor.
TemplateData for KeyDescription

This template provides a description box suitable for keys.

Template parameters
This template prefers block formatting of parameters.
Parameter		Description	Type	Status
key	`key`	key of the feature Example highway	String	required
image	`image`	image of the feature Example File:...	File	suggested
description	`description`	a short description of the feature	String	required
group	`group`	The name of the broader group to which this feature belongs. Please use lower-case names from Category:Features or from your namespaced (Category:DE:Features) or l10n version. Example amenities	Page name	suggested
onNode	`onNode`	If the feature can be used on a node. Example yes, no	String	suggested
onWay	`onWay`	If the feature can be used on a way. Example yes, no	String	suggested
onArea	`onArea`	If the feature can be used on a way. Example yes, no	String	suggested
onRelation	`onRelation`	If the feature can be used on a relation. Example yes, no	Boolean	suggested
requires	`requires`	A list of tag(s) which are necessary (often higher/lower in hierarchy) for this tag and must be set to give its actual meaning Example * {{Tag\|key name\|value}}	Content	suggested
implies	`implies`	A list of tag(s) that the feature implies in its defention. Example * {{Key\|paved}} * {{Key\|vehicle}}	Content	suggested
combination	`combination`	A bulleted-list of example tag(s) that can be used in combination with this feature. Example * {{Key\|surface}} * {{Key\|lit}}	Unknown	suggested
seeAlso	`seeAlso`	a list of similar tags Example {{Key\|cycleway}}	String	suggested
status	`status`	The [[approval status]] of this feature Suggested values `approved` `de facto` `deprecated` `discardable` `in use` `obsolete` `proposed` `undefined` `voting` Example approved, de facto, deprecated, discardable, in use, obsolete, proposed, undefined, voting	Line	suggested
statuslink	`statuslink`	The name of the proposal page, for linking.	Page name	suggested
language	`lang`	the ISO 639-2 code for the language used to document this feature: this will generate aspects of the description box in the specified language, if translations are available. If not set, language of page or namespace will be used. Example es, de	Unknown	optional
class	`class`	the CSS class of the HTML table used to form the description box	String	optional
float	`float`	the CSS float value of the table: set to none to disable the standard right float Example left, right, none	String	optional
style	`style`	the CSS style to be applied to the HTML table	String	optional
osmcarto-rendering	`osmcarto-rendering`	an image showing a suggested rendering on a map; alternatively a page name/anchor to link to more detailed description	File	optional
osmcarto-rendering-size	`osmcarto-rendering-size`	The size of the image set in osmcarto-rendering Example 28px	String	optional
osmcarto-rendering-node	`osmcarto-rendering-node`	an image showing a suggested rendering on a map for a node object; alternatively a page name/anchor to link to more detailed	File	optional
osmcarto-rendering-node-size	`osmcarto-rendering-node-size`	The size of the image set in osmcarto-rendering-node Example 28px	String	optional
osmcarto-rendering-way	`osmcarto-rendering-way`	an image showing a suggested rendering on a map for a node object; alternatively a page name/anchor to link to more detailed	File	optional
osmcarto-rendering-way-size	`osmcarto-rendering-way-size`	The size of the image set in osmcarto-rendering-way Example 28px	String	optional
osmcarto-rendering-area	`osmcarto-rendering-area`	an image showing a suggested rendering on a map for a node object; alternatively a page name/anchor to link to more detailed	File	optional
osmcarto-rendering-area-size	`osmcarto-rendering-area-size`	The size of the image set in osmcarto-rendering-area Example 28px	String	suggested
url_pattern (URI)	`url_pattern`	URI (URL / URN) of the web resource; URL pattern; URI template from which $1 can be automatically replaced with the effective property value on items. Example https://www.wikidata.org/entity/$1	URL	optional
languagelinks	`languagelinks`	If the langauge links should appear Example no	Line	optional

Multipolygons, ways which are not areas and other traps

Main article: Template:Description/doc/confusion caused by use on onArea parameter

Template:KeyDescription

Contents

Intro

Copiable example with only required and suggested parameters

Usage

Parameters

Feature description

Feature usage

Additional information

Language support

Advanced formatting parameters

Examples

TemplateData

Multipolygons, ways which are not areas and other traps

See also

Navigation menu

Template:KeyDescription

Intro

Copiable example with only required and suggested parameters

Usage

Parameters

Feature description

Feature usage

Additional information

Language support

Advanced formatting parameters

Examples

TemplateData

Multipolygons, ways which are not areas and other traps

See also

Navigation menu

Search