Zh_CN:TaggingPresets – JOSM

wiki:Zh_CN:TaggingPresets

Context Navigation

incomplete translation

其他语言:

标签预设
开发新预设
XML 格式描述
Translation
1. Internal Preset
2. External Presets
Icon handling
See also

如果你想了解预设的安装步骤，请参阅标记预设 (en)中的注册。标签预设 (en)中的注册。偏好设置 (en)
如果你想使用预设或需要完整的预设参考，请参阅预设

标签预设

JOSM 支持分布式标签预设。这是一个 XML 配置文件，描述了输入标签（或属性、注释，有时也称为地图特征）的图形用户界面。

这些预设可以放置在网络或用户本地文件系统的任何地方。JOSM 可以配置为使用自定义的本地或远程预设。

开发新预设

标记预设说明采用非常简单的 XML 格式。详见 below。

请参阅defaultpresets.xml ，其中的示例涵盖了下面列出的大部分可能性。

示例：

No image "Change 1 object.png" attached to Zh_CN:TaggingPresets

<?xml version="1.0" encoding="UTF-8"?>
<presets xmlns="http://josm.openstreetmap.de/tagging-preset-1.0">
  <item name="Oneway highway" type="way">
    <label text="Inserting a unidirectional highway" />

    <combo key="highway" text="Type" values="trunk,motorway" />
    <text key="name" text="Name (e.g. Angel Road)" />
    <text key="ref" text="Ref (e.g. A406)" />

    <!-- This is a oneway preset, so make oneway default -->
    <check key="oneway" text="Oneway" default="on" />

    <!-- Always setting asphalt surface -->
    <key key="surface" value="asphalt" />
  </item>
</presets>

Zh_CN:TaggingPresets-preset.xml, Zh_CN:TaggingPresets.zip

No image "Change 1 object.png" attached to Zh_CN:TaggingPresets

XML 格式描述

完整的 XSD 模式可从命名空间 URI (https://josm.openstreetmap.de/tagging-preset-1.0) 以及源存储库获取。

<presets>:：

必须是文件的主标签。支持以下属性 xmlns=“http://josm.openstreetmap.de/tagging-preset-1.0” author - 预设的作者姓名 version - 文件的版本号。要对本维基中管理的预设进行自动版本调整，必须使用两个内部变量：[[修订]]（维基页面的最新版本号）和[[日期]]（最后一次编辑的日期），例如`version=“1.修订_日期”。 description (i18n) - 文件内容描述 shortdescription (i18n) - 非常简短的概述，即预设的 "名称 link (i18n) - 更多详细信息的网络链接（可选）

图标* - 整个预设的图标 baselanguage - 当基础语言不是英语时，请在此处指定（使用非英语预设文本将阻止自动翻译，一旦实现（#11392））。

(i18n）表示值也可以本地化（例如 de.description）。

Comments

: The document can contain embedded comments.

Preset group creation

<group>: Used to group items in sub menus. name="" is required, icon="" is optional attribute.
<item>: Every item is one annotation set to select from. name="" is required, type="" and preset_name_label="" are recommended, icon="", name_template="" and match_expression="" are optional attributes.
<separator />: Insert a line separator into the menu.

Preset window layout

<label />: Labels are static texts for display. text="" is a required attribute, icon="" and icon_size="" are optional.
<space />: Add some space (i.e. a newline).
<optional>: Used to group some optional elements of an item. The text="" attribute is optional. If used without text="" then this is equivalent to <space /><label text="Optional Attributes:" /><space />
<item_separator />: Add a horizontal separator line between items.
<link />: Specify a web link for this feature or to anything else of use. Either the wiki="" (referring to an OSM wiki page, e.g. "Tag:leisure=park") or the href="" (full URL) attribute is required. When the wiki="" attribute is used the link points to the wiki page of the language JOSM is set to. If it doesn't exist the English page is shown. If using wiki="", the OSM wiki page must not be URL encoded, e.g., it must not be "Tag:leisure%3Dpark" and must instead be "Tag:leisure=park".
<checkgroup>: To group checks. The columns="" attribute is required.
<roles>: This is required around <role /> and adds the heading ("Available roles role count elements") to the table which is generated by several <role />.
<role />: To specify possible roles of members in relations. The key="" attribute is required, text="", requisite="", count="", type="", member_expression="" and regexp="" are optional.
<preset_link />: Adds a link to an other preset with a label on top. The preset_name="" attribute is required, text="" to override the label (default is "Edit also …") and text_context="" are optional. A sequence of <preset_link /> without text="" or a identical text="" value are grouped below one label.
Watch out for presets with identical name="" as it is not predictable to which preset the link will lead to, see #12716.
Having the same tag in both presets does not work, see #18992.
Using <preset_link /> in presets opened from relation editor (en) produces exceptions, see #20044.

Set a fixed key value pair

<key />: This tag will always set a key to a specific value. key="" is required and if value="" is present, the key will be set. If value="" attribute is omitted, the key is removed. The match="" attribute is optional.

Attribute entry and selection dialog boxes

<text />: A text edit field to enter any arbitrary string from the user. key="" is mandatory, text="", default="", use_last_as_default="", auto_increment="", length="", alternative_autocomplete_keys="", match="", icon="" and icon_size="" (both since r17605) are optional.
<combo />: Displays a multiple choice combo box. key="" and values="" are mandatory, text="", default="", editable="", delimiter="", values_from="", display_values="", short_descriptions="", use_last_as_default="", values_searchable="", length="", values_no_i18n="", values_sort="", match="", icon="" and icon_size="" (both since r17605) are optional.
If editable="" is true (default), combo boxes can be edited as if they were text fields (additional to the drop down menu). Non editable combo boxes can only contain one of the specified values.
If the key is colour or colour:* or *:colour, a color preview and color picker is added on the right (see #8352).
<multiselect />: Displays a list from which zero or more items can be chosen. key="" and values="" are mandatory, and text="", default="", delimiter="", values_from="", rows="", display_values="", short_descriptions="", use_last_as_default="", values_searchable="", values_no_i18n="", values_sort="", match="", icon="" and icon_size="" (both since r17605) are optional. The selected values will be concatenated with the specified delimiter (default: semicolon, ;) and written to the tag value. If a tag value has already been set when the preset dialog is opened, the <multiselect /> will attempt to mark the appropriate items in the list as select. If the tag value cannot be represented by a combination of choices in the list, then the list will be disabled so that the user cannot accidentally overwrite a custom value. In contrast to the <combo /> element, the <multiselect /> expects the list of values, descriptions etc. to use the specified delimiter, i.e. by default you will have to use a semicolon. You can specify delimiter="," but then a comma will also be used in the tag value.
<list_entry />: Used in <combo> and <multiselect>. More information see short_descriptions="", below. The attributes are value="", display_value="", short_description="", icon="" and icon_size="".
<check />: A checkbox which the user can select, deselect or set as unset. The key="" attribute is mandatory. text="", default="", match="", value_on="" , value_off="", disable_off="", icon="" and icon_size="" (both since r15437) are optional.

Templates

<chunk>: To define a template of elements for later (repeated) use. The id="" attribute is mandatory.
<reference>: To include an earlier defined template. The ref="" attribute is mandatory.

Attributes

The attributes of the tags have the following meaning:

name="a_name"

Specify a name for an item. This name will be used in the GUI to display the tagging preset.

name_context="context"

Translation context for name attribute to separate equals words with different meaning (not required for in-file translations).

type="data_type"

When specified, only objects of the given type will work with this tagging preset. Can be "node", "way", "closedway", "multipolygon", "relation" or any comma separated combination of them. Note that "multipolygon" is not included in "relation", so if the preset should apply for multipolygons and other relation types, you need to specify both: "multipolygon,relation". Also used in the <role> tag to specify which object types are allowed for a specific relation member.

icon="iconname"

A name or link to an icon. The image will be used as icon to display in the selection list and when adding the preset to the toolbar. Icons can also be used in <item>, <label />, plus all attribute entry and selection dialog boxes (since r17605, before it was only <list_entry /> and <check />). It is placed in front of <text /> The icon should be quadratic in size. See Icon handling (en) how icons can be specified.

icon_size="a number"

The maximal size of an icon in px. If no value is given, default is 16 for <label /> and the default icon size for <list_entry /> (in <combo> and <multiselect>).

key="some_key"

This specifies the property key that will be modified by the item. In case of <role> it is the role name used in a relation.

text="Any text"

The description, that will be displayed before the gui element, (in case of <check /> after the gui element and the optional icon). Also used for <label> and <optional>.

text_context="context"

Translation context for text attribute to separate equals words with different meaning (not required for in-file translations).

default="default_value"

An explicitly declared default value for the item. This value is only applied through a preset when the object the preset is applied to has zero keys. If no value for default is specified, no value is set to the key. Used in <check />, <text />, <combo /> and <multiselect />. For <check /> only the values "on" and "off" are valid.

values="entry1,entry2,entry3"

A list of entries (for the <combo /> box and <multiselect />). The list has to be separated by commas (for the combo box) or by the specified delimiter (for the multiselect). If a value contains the delimiter, the delimiter may be escaped with a backslash. If a value contains a backslash, it must also be escaped with a backslash.

values_from="JAVA code"

To use instead of values="" if the list of values has to be obtained with a Java method of this form: public static String[] getValues(); The value must be: "full.package.name.ClassName#methodName".

values_no_i18n="true|false"

Disables internationalisation for values to avoid mistakes, see #11696. Default is "false". Used in <combo /> and <multiselect />. (Useful e.g. for keys opening hours or brand.) Not needed with keys with only numbers as values like layer or level which are already excluded from translation.

values_sort="true|false"

Values of <combo /> and <multiselect /> are sorted alphabetic in every language. With this attribute you can disable the alphabetic sorting if the values should keep the given order, see #5509 and #11926. (In the JOSM internal preset this is used e.g. for the keys tracktype, direction, network, smoothness, visibility or trail_visibility.) Default is "true".
Users can globally disable sorting with the preference key taggingpreset.sortvalues.

values_context="context"

Translation context for values attribute to separate equals words with different meaning (not required for in-file translations).

display_values="Entry1,Entry2,Entry3"

A list of entries that is displayed to the user. Must be the same number and order of entries as values="" and editable="" must be "false" or not specified. For the delimiter character and escaping, see the remarks at values="". Used in <combo /> and <multiselect />.

value="foobar"

Specify a value to be entered in the <key> tag.

value_on="foobar"

Specify the true value to be entered in the <key> tag of a checked <check /> (default is "yes").

value_off="foobar"

Specify the false value to be entered in the <key> tag of a unchecked <check /> (default is "no").

disable_off="true"

Whether the off value of a <check /> is disabled in the dialog, i.e., only unset or "yes" are provided.

editable="false"

The combo box is read only, which means that the user can only select an item in the list. Default is "true", which means, the user can add other values as text. (Feature was not working properly for a long time but should work again since r18221, see #6157.)

use_last_as_default="true|false|force"

For <combo />, <multiselect /> or <text /> fields the last used value is used as default. Using "force" enforces this behavior also for already tagged objects. Default is "false".

rows="count"

Specify the number of rows to display in <multiselect /> entry (if not set, it is auto determined by java or the look and feel and results in e.g. 8).

name_template="template", name_template_filter="search expression"

Custom name formatter for osm primitives matching this preset. See name template details below.

match="none|key|key!|keyvalue|keyvalue!"

Allows to change the matching process, i.e., determining whether the tags of an OSM object fit into this preset. If a preset fits then it is linked in the Tags/Membership dialog (en).

none: neutral, i.e., do not consider this item for matching
key: positive if key matches, neutral otherwise
key!: positive if key matches, negative otherwise
keyvalue: positive if key and value matches, neutral otherwise
keyvalue!: positive if key and value matches, negative otherwise

Note: For a match, at least one positive and no negative is required. Default is "keyvalue!" for <key> and "none" for <text />, <combo />, <multiselect /> and <check />.

match_expression="search expression"

additional criteria for matching primitives, specified in JOSM search (en) syntax. (since r17662)
Quotes (") need to be written as ".
For instance, a preset with match_expression="foo=bar" requires OSM objects to have the tag foo=bar. You may want to use the match_expression="" to exclude certain OSM objects, e.g. when a more specific preset is present.

id="unique_identifier"

the unique identifier for this <chunk>

ref="unique_identifier"

the unique identifier of the (already defined) template to include

columns="a number"

the number of columns of grouped <check />

requisite="optional|required"

If a relation member is optional or required. Default is "optional".

count="a number"

How often can a role occur (if not given unlimited number is assumed)

member_expression="search expression"

an expression, in JOSM search (en) syntax, for objects of this role
Quotes (") need to be written as ".

regexp="true"

set to "true" if the key of a role is a regular expression.
This allows variable roles e.g. <role key="level_-?\d+" text="Building level" regexp="true" requisite="optional" type="relation" /> allows the roles level_0, level_1,...

preset_name="exact_name"

The exact name of the preset to link to.

preset_name_label="false|true"

Whether to insert "[preset name]" label in dialog (defaults to "false" for backward-compatibility on external presets).

length="a number"

The length of a <text /> or <combo /> box (number of characters allowed).

alternative_autocomplete_keys="some_key(s)"

A comma separated list of alternative keys to use for auto completion of <text>.

auto_increment="-2,-1,+1,+2"

May contain a comma separated list of integer increments or decrements, e.g. "-2,-1,+1,+2". A button will be shown next to the <text /> field for each value, allowing the user to select auto-increment with the given stepping. Auto-increment only happens if the user selects it. There is also a button to deselect auto-increment. Default is no auto-increment. Mutually exclusive with use_last_as_default="".

delimiter="special character"

The character that separates values. In case of <combo /> the default is comma (,). In case of <multiselect /> the default is semicolon (;) and this will also be used to separate selected values in the tag. More information see <multiselect />, above.

short_descriptions="Entry1,Entry2,Entry3"

A delimiter-separated list of texts to be displayed below each display_value="". (Only if it is not possible to describe the entry in 2-3 words.) Instead of a comma separated list using values="", display_values="" and short_descriptions="", the following form is also supported:
<list_entry value="" display_value="" short_description="" icon="" icon_size="" />

values_searchable="true|false"

Whether to search in values="" and display_values="", respectively, value="" and display_value="" of <combo /> or <multiselect /> searching for presets.

value_template="template"

A template to generate the value automatically based on other tag values of the object. The same syntax as in name_template="" is used, see below. (since r17639)
For instance, "Bus {ref}: {from} → {to}" can be used to generate the name of a bus route relation.
Note: There are some minor problems with this attribute, see #20851 and #20861.

name_template and value_template details

Name templates can be used to define custom formatting for OSM primitives or GPX waypoints (for example in the Relations or Selection panels).

<?xml version="1.0" encoding="UTF-8"?>
<presets>
        <item name="Public transportation" type="relation"
                name_template="Bus({operator} {ref} ?{'{from} - {via} - {to}' | '{from} - {to}' | '{from}' | '{to}'})"
                name_template_filter="type=route route=bus">
        </item>
</presets>

Samples

Template	Tags	Result
`House number {addr:housenumber}`	`addr:housenumber=10`	House number 10
`?{ 'House number {addr:housenumber} at {addr:street}' \| 'House number {addr:housenumber}' }`	`addr:housenumber=10`	House number 10
	`addr:housenumber=10 addr:street=Abbey road`	House number 10 at Abbey road
`?{ admin_level = 2 'NUTS 1' \| admin_level = 4 'NUTS 2' \| admin_level = 6 'NUTS 3' \| 'Admin level {admin_level}'}`	`admin_level=4`	NUTS 2
	`admin_level=5`	Admin level 5
`{admin_level} - {name} !{parent() type=boundary '?{'(part of {admin_level} - {name})' \| ''}'}`	`admin_level=6 name=Vysocina`, member of relation `admin_level=4 name=Jihovychod`	6 - Vysocina (part of 4 - Jihovychod)
	`admin_level=2 name=Czech republic` (no parents)	2 - Czech republic

Syntax

{tag} - insert the value of the tag.
?{condition1 'value1' | condition2 'value2' | 'value3'} - use value1 if condition1 is satisfied, else use value2 if condition2 is satisfied, finally use value3 if no condition is satisfied. Condition can be either explicit - in JOSM search (en) syntax - or implicit: The value is used when all tags referenced inside exist.
!{search_expression 'template'} - search_expression is evaluated and first matching primitive is used as context for template. Useful for example to get tags of parent relation.
\ - use a backslash to escape special characters '{', '}', '?', '!'. E.g. What is this\? It is a {type}\!.

Available values

For formatting of OSM primitives, the value of any tag can be used. Use the tag {special:everything} to display all available tags, eg. on your gpx waypoints.

You can also use these virtual tags:

{special:everything} prints all available values, available for formatting of both primitives and waypoints.
{special:id} prints the ID of the osm primitive.
{special:localName} prints the localized name, that is the value of name:lang for your language if it is available, or the value of name if it is not.

Deprecated Attributes

The following attributes are deprecated and no longer supported by JOSM:

delete_if_empty="true": was removed in r5155. You can simply remove this attribute if still used in your preset.
required="true": replaced by match="" since r5155

Translation

To support translations, all textual elements (name="", text="", display_values="") can be localized. E.g. de.name="" would represent the name when the German language support is loaded. In the preset XML code the English term must be the first, before possible translations can be added.

Internal Preset

The translation for the internal preset is done at Launchpad.

In the internal preset , all name="", text="" and display_values="" are translated via the above service, as long as no specific translation has been given within XML file. When no display_values="" are supplied, then values="" will be treated as display_values="" and translated instead.

When the same English word has different translations in different contexts, the specific translation context needs to be specified. Use name_context="", text_context="" or values_context="" for this purpose. The context should be a meaningful short description to help translators.

External Presets

The translation of external presets on this website is, so far, only possible inline within the preset XML source code, see #11392.

Presets hosted elsewhere can also add a data directory with the JOSM-style .lang files for translation (like in JOSM itself or plugins).

However, when words are used in the external preset that already exist in the internal preset, the translation from the internal preset applies to the external as well. This is useful as long as the context is the same. When the context in the external preset is different, it needs to be distinguished by adding name_context="", text_context="" or values_context="".

Icon handling

See Styles (en).