wiki:Presets/Access_Mapping_Indonesia

Version 2 (modified by wonderchook, 13 years ago) ( diff )

adding to preset

<?xml version="1.0" encoding="UTF-8"?> <presets xmlns="http://josm.openstreetmap.de/tagging-preset-1.0"> <!--

Pics have been derived from http://de.wikipedia.org/wiki/Bildtafel_der_Verkehrszeichen_in_Deutschland (german street sign SVGs) http://commons.wikimedia.org/wiki/Image:National_Park_Service_sample_pictographs.svg (various monochrome pictograms) http://www.kde.org http://openclipart.org/media/view/media/clip_art http://www.sjjb.co.uk/mapicons/ (meanwhile in osm svn)

--> <!-- item:

name: the text to display icon: the icon to display

  • relative to the icon path
  • URL's are also supported to allow remote icons (are cached locally) type: the data types - way,node,relation,closedway (separated by comma) name_template: define custom formatting for OSM primitives

see http://josm.openstreetmap.de/wiki/NameTemplate

link: link to the relating map features website

href: the URL

label: simple static text label

text: the text to display

key: fixed key/value pair to be set

key: key to set value: value to set match: none/key/key!/keyvalue (default is "keyvalue", see below for more information)

text: text box

key: key to set text: fixed label to display default: default string to display (defaults to "") use_last_as_default: true/false/force (default is "false") match: none/key/key!/keyvalue (default is "none", see below for more information)

combo: combo box, with multiple choices and possible to enter free form text

key: key to set text: fixed label to display values: comma separated list of values display_values: comma separated list of values to be displayed instead of the

database values, order and number must be equal to values

short_descriptions: comma 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 comma separeted list

instead using values, display_values and short_descriptions, the following form is also supported:

<list_entry value="" display_value="' short_description="" icon=""/>

default: default string to display (defaults to "") use_last_as_default: true/false/force (default is "false") match: none/key/key!/keyvalue (default is none, see below for more information)

multiselect: list of values from which zero or more can be selected

key: key to set text: fixed label to display delimiter: character that separates values (default: semicolon) - this

will also be used to separate selected values in the tag.

values: delimiter-separated list of values (delimiter can be escaped with backslash) rows: specify the number of rows to display (default -1) display_values: delimiter-separated list of values to be displayed instead of the

database values, order and number must be equal to values

short_descriptions: 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 separated list

instead using values, display_values and short_descriptions, the following form is also supported:

<list_entry value="" display_value="' short_description="" icon=""/>

default: default string to display (defaults to "") use_last_as_default: true/false/force (default is "false") match: none/key/key!/keyvalue (default is "none", see below for more information)

check: checkbox

key: key to set text: fixed label to display default: ticked on/off value_on: the value to set when checked (default is "yes") value_off: the value to set when unchecked (default is "no") match: none/key/key!/keyvalue (default is "none", see below for more information)

role: type to specify possible roles in relations

key: the role name used in relation text: fixed label to display requisite: optional/required (default is "optional") count: how often can the role occur (if not given unlimited number is assumed) type: the data types - way,node,relation,closedway (separated by comma)

presets: For external files <presets> should have following attributes:

author: the author of the preset version: a version number of some sort (e.g. creation date) description: what is your preset meant to be shortdescription: very short description link: a link to a helpful website (optional)

The fields description, shortdescription and link may also be localized (e.g. de.link)

See also http://josm.openstreetmap.de/wiki/TaggingPresets.

The fields "name", "text", "display_values" may also be localized (e.g. de.name). When translations of equal words but different meanings may conflict, a translation context should be specified. Use "name_context", "text_context" or "values_context" for this. The context should be a meaningful short description to help translators.

In JOSM internally all "name", "text" and "display_values" are translated when no specific translation has been given in XML file. When no "display_values" are supplied, then "values" will be treated as "display_values" and translated instead.

The match attribute allows to change the matching process, i.e., determining whether the tags of an OSM object fit into this preset.

  • 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, negative otherwise

Note that for a match, at least one positive and no negative is required. -->

</presets>

Note: See TracWiki for help on using the wiki.