Context Navigation

← Previous Change
Wiki History
Next Change →

MapCSSImplementation

Timestamp:: (multiple changes)
Author:: (multiple changes)
Comment:: (multiple changes)

Legend:

: Unmodified
: Added
: Removed
: Modified

Help/Styles/MapCSSImplementation

-              v138
+              v268
 [[TranslatedPages]]
+[[PageOutline(1-10,Table of Contents)]]
+This page documents details on JOSM's [osmwiki:MapCSS/0.2 MapCSS] implementation. This is used for the following features in JOSM:
+* [wiki:Styles Mappaint styles]
+* [wiki:Rules Validator rules]
+* [Help/Action/Search Search dialog]
+[[PageOutline(2-10,Table of Contents)]]
+= MapCSS Implementation=
+JOSM's implementation of [osmwiki:MapCSS/0.2 MapCSS] is used for the features:
+* [wikitr:/Styles Mappaint styles]
+* [wikitr:/Rules Validator rules], see [wikitr:/Help/Validator/MapCSSTagChecker MapCSS tag checker] for the special part for rules only.
+* [wikitr:/Help/Action/Search Search dialog]
+Consider installing the [https://marketplace.visualstudio.com/items?itemName=whammo.mapcss-syntax MapCSS Syntax Highlighter] in VS Code to add visual highlighting for MapCSS paint and validator syntax.
 == General Structure ==
 …
     set: class;
     set: .class;
+    /* note that validator rules do not use the colon after set */
+}
 }}}
 …
 }}}
+== Selectors ==
+''Selectors'' denote the filter expressions of a MapCSS rule. The rule is only applied to a map object, if its selectors match
+with the object.
+Selectors in MapCSS are different from standard CSS for the web. MapCSS only supports a subset of the standard CSS selectors, but
+extends them with additional selectors required for OSM data.
+== Selectors == #Selectors
+''Selectors'' denote the filter expressions of a MapCSS rule. The rule is only applied to a map object, if its selectors match with the object.
+Selectors in MapCSS are different from standard CSS for the web. MapCSS only supports a subset of the standard CSS selectors, but extends them with additional selectors required for OSM data.
 Some basic examples:
 …
 way[highway=residential] {  /*  the styles */}
 /* applied to new, closed ways on layer 1, provided they have the tag amenity=parking and access=public, and provided
+/* applied to new, closed ways on layer 1, provided they have the tag amenity=parking and access=customers, and provided
  * the zoom level is between 11 and 14
  */
 way|z11-14[amenity=parking][access=public]:closed:new::layer_1 {...}
 area[amenity=parking][access=public], area[amenity=parking][!access] {...}
+way|z11-14[amenity=parking][access=customers]:closed:new::layer_1 {...}
+area[amenity=parking][access=customers], area[amenity=parking][!access] {...}
 relation[type=route][route=foot] > way::relation_underlay {..}
 }}}
 …
 === Type selector ===
+{{{#!th align=left valign=top
+{{{#!th valign=top
 '''Selector'''
 }}}
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Description'''
 }}}
 |-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
+{{{#!td align=center  valign=top
+*
 }}}
 …
 }}}
 |-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
 {{{node}}}, {{{way}}}, {{{relation}}}
+{{{#!td align=center  valign=top
+`node`, `way`, `relation`
 }}}
 {{{#!td align=left  valign=top
 …
 }}}
 |-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
+{{{area}}}
+{{{#!td align=center  valign=top
+`area`
 }}}
 {{{#!td align=left  valign=top
 …
 way[natural=beach], relation[type=multipolygon][natural=beach] {...}
 }}}
 Note that {{{area}}} selects unclosed ways as well, so it may be useful to add the {{{:closed}}} pseudo class. The JOSM Validator will give a warning for unclosed ways that have an area style.
+}}}
+|-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
+{{{meta}}}
+Note that `area` selects unclosed ways as well, so it may be useful to add the `:closed` pseudo class. The JOSM Validator will give a warning for unclosed ways that have an area style.
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=center  valign=top
+`meta`
 }}}
 {{{#!td align=left  valign=top
 The {{{meta}}} selector starts a special rule that should stand at the beginning of the file. It gives some general information on the style sheet. All software that supports MapCSS should be able to parse this sections without errors, so do not use exotic syntax extensions in this part.
+The `meta` selector starts a special rule that should stand at the beginning of the file. It gives some general information on the style sheet. All software that supports MapCSS should be able to parse this sections without errors, so do not use exotic syntax extensions in this part.
 {{{
 #!mapcss
 meta {
     title: "Parking lanes";   /* title shown in the menu */
     icon: "images/logo.png";  /* small icon shown in the menu next to the title */
+    icon: "logo_16x16x8.png"; /* small icon shown in the menu next to the title */
     version: "1.2";           /* the version of the style */
     description: "...";       /* one or two sentences of describing the style */
     author: "...";            /* the author(s) of the style */
     link: "http://...";       /* URL to the web page of the style */
+    link: "https://...";      /* URL to the web page of the style */
     min-josm-version: 6789;   /* the minimum JOSM version where this style works */
+}
 …
 }}}
 |-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
+{{{canvas}}}
+{{{#!td align=center  valign=top
+`canvas`
 }}}
 {{{#!td align=left  valign=top
 …
 }}}
 |-
+{{{#!td
 {{{fill-color}}}
+{{{#!td align=center
+`fill-color`
 }}}
 {{{#!td
 Specifies the overall fill/background color (`background-color` is deprecated since r7110).
 }}}
+{{{#!td
+{{{#!td align=center
 ''Color''
 }}}
 {{{#!td align=center
+{{{black}}}
+`black`
 }}}
 |-
+{{{#!td
 {{{default-points}}}
+{{{#!td align=center
+`default-points`
 }}}
 {{{#!td
 Whether default point style should be added to nodes where no style applies.
 }}}
+{{{#!td
+{{{#!td align=center
 ''Boolean''
 }}}
 {{{#!td align=center
+{{{true}}}
+`true`
 }}}
 |-
+{{{#!td
 {{{default-lines}}}
+{{{#!td align=center
+`default-lines`
 }}}
 {{{#!td
 Whether default line style should be added to ways where no style applies.
 }}}
+{{{#!td
+{{{#!td align=center
 ''Boolean''
 }}}
 {{{#!td align=center
+{{{true}}}
+`true`
 }}}
 }}}
 …
 * The functions ''prop()'' and ''is_prop_set()'' are only supported on the right side of the > sign.
 * The functions ''parent_tag'' and ''parent_tags'' (see below) can be used to access tags from the parent(s).
+* For compatibility with the MapCSS 0.2 standard, `relation[type=route][route=foot] way {/*...*/}`, without the greather-than-sign `>` is supported, too. However, no [[#Linkselector]] may be specified in this case.
+* For compatibility with the MapCSS 0.2 standard, `relation[type=route][route=foot] way {/*...*/}`, without the greater-than-sign `>` is supported, too. However, no [#LinkSelector Link selector] may be specified in this case.
 === Parent selector ===
 …
 Similar to a child selector, a parent selector only matches if both the parent and the child object match. In contrast to the child selector, the character < is used.
 In contrast to the child selector, the parent object will be "selected". In other words, the properties in the {{{{...}}}}-Declaration Block apply to the object on the right hand side of the "<" sign.
+In contrast to the child selector, the parent object will be "selected". In other words, the properties in the `{{{...}}}`-Declaration Block apply to the object on the right hand side of the "<" sign.
 Example:
 …
 === Condition selector ===
+Selectors can include a set of conditions. If any of these conditions evaluates to false, the selector doesn't match and the style
+rule isn't applied.
+An '''attribute condition''' specifies a condition on a tag of an OSM object.
+Selectors can include a set of conditions. If any of these conditions evaluates to false, the selector doesn't match and the style rule isn't applied.
+An '''attribute condition''' specifies a condition on a tag of an OSM object.
 [=#condition_selector_operators]
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Operator'''
 }}}
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Description'''
 }}}
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Example'''
 }}}
 |-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
+{{{#!td align=center valign=top
 `=`
 }}}
 {{{#!td align=left  valign=top
+{{{#!td align=left valign=top
 Exact match of the value.
 }}}
+{{{#!td align=left  valign=top
+{{{
+#!mapcss
+way[highway=residential]                   /* without quotes always case insensitive */
+node[name="My name"]                       /* use quotes for if value includes spaces or if case sensitive matching is important */
+node["MY_Special_TAG"="another value"]     /* use quotes for tag names if case sensitive matching is required */
+node["ÖPVN"=tram]                          /* use quotes for tag keys with special characters */
+                                           /*   note that these are not common in OSM at the moment */
+}}}
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=left  valign=top
+{{{#!td align=left valign=top
+{{{
+#!mapcss
+way[highway=residential]                    /* is case sensitive, i.e. does NOT match e.g. highway=Residential or Highway=residential   */
+node[name="My name"]                        /* use quotes if key or value includes spaces                                               */
+node["name:pl"="Królewiec"]                 /* use quotes if key or value includes special characters like colons or unicode characters */
+}}}
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=center valign=top
 `!=`
 }}}
+{{{#!td align=left  valign=top
+Value not equal
+}}}
+{{{#!td align=left  valign=top
+{{{
+#!mapcss
+way[highway!=residential]                   /* without quotes always case insensitive */
+node[name!="My name"]                       /* use quotes if value includes spaces or if case sensitive matching is important */
+node["MY_Special_TAG"!="another value"]     /* use quotes for tag names if case sensitive matching is required */
+node["name:fr"!="mon nome"]                 /* use quotes for tag names with special characters like colons*/
+}}}
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=left  valign=top
+{{{#!td align=left valign=top
+Value not equal
+}}}
+{{{#!td align=left valign=top
+{{{
+#!mapcss
+way[highway!=residential]
+node[name!="My name"]
+node["name:pl"!="Królewiec"]
+}}}
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=center valign=top
 `<`, `>`, `<=`, `>=`
 }}}
 {{{#!td align=left  valign=top
 Comparision for numeric values.
+}}}
 {{{#!td align=left  valign=top
+{{{#!td align=left valign=top
+Comparison for numeric values.
+}}}
+{{{#!td align=left valign=top
 {{{
 #!mapcss
 node[population >= 50000]                   /* population greater than or equal to 50000 */
+node[ele = 3000]                            /* elevation with exactly 3000 meters */
+}}}
+}}}
+|-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
+{{{^=}}}
+}}}
 {{{#!td align=left  valign=top
+node[ele = 3000]                            /* elevation with exactly 3000 meters        */
+}}}
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=center valign=top
+`^=`
+}}}
+{{{#!td align=left valign=top
 Prefix match
 }}}
 {{{#!td align=left  valign=top
+{{{#!td align=left valign=top
 {{{
 #!mapcss
 …
 }}}
 |-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
+{{{#!td align=center valign=top
 `$=`
 }}}
 {{{#!td align=left  valign=top
+{{{#!td align=left valign=top
 Postfix match
 }}}
 {{{#!td align=left  valign=top
+{{{#!td align=left valign=top
 {{{
 #!mapcss
 …
 }}}
 |-----------------------------------------------
 {{{#!td align=left  valign=top
+{{{#!td align=center valign=top
 `*=`
 }}}
 {{{#!td align=left  valign=top
+{{{#!td align=left valign=top
 Substring match
 }}}
 {{{#!td align=left  valign=top
+{{{#!td align=left valign=top
 {{{
 #!mapcss
 …
 }}}
 |-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
+{{{#!td align=center valign=top
 `~=`
 }}}
 {{{#!td align=left  valign=top
+{{{#!td align=left valign=top
 List membership
 }}}
 {{{#!td align=left  valign=top
+{{{
+#!mapcss
 *[vending~=stamps]                          /* the tag value for the tag 'vending' consists of a list of ;-separated values    */
                                             /* and one of these values is 'stamps'                                             */
+}}}
+}}}
+|-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
+{{{#!td align=left valign=top
+{{{
+#!mapcss
+*[vending~=stamps]                          /* the tag value for the tag 'vending' consists of a list of ;-separated values */
+                                            /* and one of these values is 'stamps'                                          */
+}}}
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=center valign=top
 `=~`
 }}}
 {{{#!td align=left  valign=top
 [https://download.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html#sum Regular expression] match
+}}}
 {{{#!td align=left  valign=top
+{{{#!td align=left valign=top
+[https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/regex/Pattern.html#sum Regular expression] match
+}}}
+{{{#!td align=left valign=top
 {{{
 #!mapcss
 *[name=~/^My_pattern.*/]                    /* the value of the tag 'name' matches with the regular expression '^My_pattern.*' */
+                                            /* Note, that reqular expressions have to be enclosed in /.../                     */
+}}}
+Case-insensitive matching can be enabled via the embedded flag expression `(?i)` (see [https://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html#CASE_INSENSITIVE Pattern.CASE_INSENSITIVE]).
+{{{
+#!mapcss
+*[name =~ /^(?U)(\p{Lower})+$/]              /* name consists of only lower case unicode characters */
+}}}
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=left  valign=top
+                                            /* Note, that reqular expressions have to be enclosed in /.../                     */
+}}}
+Case-insensitive matching can be enabled via the embedded flag expression `(?i)` (see [https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/regex/Pattern.html#CASE_INSENSITIVE Pattern.CASE_INSENSITIVE]).
+{{{
+#!mapcss
+*[name =~ /^(?i)(parking)$/]                 /* matches parking, Parking, PARKING, PaRkInG,...      */
+*[name =~ /^(?U)(\p{Lower})+$/]              /* name consists of only lower case unicode characters */
+}}}
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=center valign=top
 `!~` (since r6455)
 }}}
 {{{#!td align=left  valign=top
 negated [https://download.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html#sum Regular expression] match
+}}}
 {{{#!td align=left  valign=top
+{{{#!td align=left valign=top
+negated [https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/regex/Pattern.html#sum Regular expression] match
+}}}
+{{{#!td align=left valign=top
 {{{
 #!mapcss
 …
 }}}
 |-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
+`∈` ([http://www.fileformat.info/info/unicode/char/2208/index.htm U+2208], since r6609)
+}}}
 {{{#!td align=left  valign=top
+{{{#!td align=center valign=top
+`∈` ([https://www.fileformat.info/info/unicode/char/2208/index.htm U+2208], since r6609)
+}}}
+{{{#!td align=left valign=top
 element of
+}}}
+{{{#!td align=left  valign=top
+{{{
+#!mapcss
+node[amenity=parking] ∈ *[amenity=parking] {
+Matches when an object matches the right selector(s) contains at least one element which match the left selector(s).
+}}}
+{{{#!td align=left valign=top
+{{{
+#!mapcss
+*[amenity=parking] ∈ area[amenity=parking] {
   throwWarning: tr("{0} inside {1}", "amenity=parking", "amenity=parking");
+}
 }}}
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=left  valign=top
+`⧉` ([http://www.fileformat.info/info/unicode/char/29c9/index.htm U+29C9], since r6613)
+}}}
+{{{#!td align=left  valign=top
+Finds areas with `amenity=parking` that contain at least one node or area with `amenity=parking`. Since r15064 this rule produces one warning for each element on the left when there are multiple matches.
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=center valign=top
+`⊆` ([https://www.fileformat.info/info/unicode/char/2286/index.htm U+2286], since r15102)
+}}}
+{{{#!td align=left valign=top
+Subset of or Equal To
+Synonym for `∈`.
+}}}
+{{{#!td align=left valign=top
+{{{
+#!mapcss
+*[amenity=parking] ⊆ area[amenity=parking] {
+  throwWarning: tr("{0} inside {1}", "amenity=parking", "amenity=parking");
+}
+}}}
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=center valign=top
+`⊇` ([https://www.fileformat.info/info/unicode/char/2287/index.htm U+2287], since r15102)
+}}}
+{{{#!td align=left valign=top
+Superset of or Equal To
+Matches when an object matches the right selector(s) and is contained in one or more elements which match the left selectors.
+}}}
+{{{#!td align=left valign=top
+{{{
+#!mapcss
+area[amenity=parking] ⊇ *[amenity=parking]
+}}}
+finds nodes or areas with `amenity=parking` inside areas with `amenity=parking`. Slower than `⊆` and thus not useful in validator rules, but can be useful in the search dialog.
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=center valign=top
+`⊈` ([https://www.fileformat.info/info/unicode/char/2288/index.htm U+2288], since r15102)
+}}}
+{{{#!td align=left valign=top
+Neither a Subset of nor Equal To
+Matches when an object matches the right selector(s) and does not contain any element which matches the left selectors.
+}}}
+{{{#!td align=left valign=top
+{{{
+#!mapcss
+*[highway=street_lamp] ⊈ area:closed2[amenity=parking][lit=yes]
+}}}
+finds areas amenity=parking that have lit=yes but don't contain a lamp. Always add `:closed2` to avoid false positives as unclosed areas never contain something.
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=center valign=top
+`⊉` ([https://www.fileformat.info/info/unicode/char/2289/index.htm U+2289], since r15102)
+}}}
+{{{#!td align=left valign=top
+Neither a Superset of nor Equal To
+Matches when an object matches the right selector(s) and is not contained in any area which matches the left selectors.
+}}}
+{{{#!td align=left valign=top
+{{{
+#!mapcss
+area[landuse=residential] ⊉ *[building]
+}}}
+finds buildings which are not inside any landuse=residential area. Note that this operator is likely to produce false positives when you have `landuse=residential`areas which don't match `:closed2`.
+}}}
+|-------------------------------------------------------------------------------
+{{{#!td align=center valign=top
+`⧉` ([https://www.fileformat.info/info/unicode/char/29c9/index.htm U+29C9], since r6613)
+}}}
+{{{#!td align=left valign=top
 crossing
+}}}
+{{{#!td align=left  valign=top
+}}}
+{{{#!td align=left valign=top
 {{{
 #!mapcss
 …
+}
 }}}
+}}}
+Since r6554, it is possible to prefix the "value" (i.e., expression after the operator) with a `*` in order to "de-reference" it (i.e., obtain consider it as another key and obtain its value). Thus, `[key1 = *key2]` compares the value of `key1` with the value of `key2`, and `[key =~ */pattern/]` considers the value of the key `pattern` as a regular expression and matches it against the value of `key`.
+takes `layer` tag into account if set (since r12986)
+}}}
+Since r6554, it is possible to prefix the "value" (i.e., expression after the operator) with a `*` in order to "de-reference" it (i.e., obtain consider it as another key and obtain its value). Thus, `[key1 = *key2]` or `[key1=*key2]` compares the value of `key1` with the value of `key2`, and `[key =~ */pattern/]` considers the value of the key `pattern` as a regular expression and matches it against the value of `key`.
 In addition, you can test whether a tag is present or not:
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Condition'''
 }}}
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Example'''
 }}}
 …
 {{{
 #!mapcss
+way[highway]                     /* matches any way with a tag 'highway'                                              */
+way["VALSOU"]                    /* use quotes if case sensitive matching is required                                 */
+way["name:fr"]                   /* use quotes if the tag name includes special caracters (white space, colons, etc.) */
+way[highway]                     /* matches any way with a tag 'highway' (is case sensitive)                                              */
+way["name:fr"]                   /* use quotes if the tag name includes special caracters (white space, colons, unicode characters, etc.) */
 }}}
 }}}
 …
 {{{
 #!mapcss
+way[!highway]                     /* matches any way which does not have a tag 'highway'                               */
+way[!"VALSOU"]                    /* use quotes if case sensitive matching is required                                 */
+way[!"name:fr"]                   /* use quotes if the tag name includes special caracters (white space, colons, etc.) */
+way[!highway]                     /* matches any way which does not have a tag 'highway' (is case sensitive)                               */
+way[!"name:fr"]                   /* use quotes if the tag name includes special caracters (white space, colons, unicode characters, etc.) */
 }}}
 }}}
 |-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
 Presence of tag by [https://download.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html#sum Regular expression] match (since r6547)
+Presence of tag by [https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/regex/Pattern.html#sum Regular expression] match (since r6547)
 }}}
 {{{#!td align=left  valign=top
 …
 "yes", "true", or "1". All other values are evaluated to false.
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Condition'''
 }}}
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Example'''
 }}}
 …
 {{{
 #!mapcss
 way[oneway?]                  /* matches any way with a truth value in the tag 'oneway'  */
+way[oneway?]                   /* matches any way with a truth value in the tag 'oneway' */
 }}}
 }}}
 …
 {{{
 #!mapcss
+way[oneway?!]                  /* matches any way with a false value in the tag 'oneway'  */
+}}}
+}}}
+=== Territory selector ===
+You can test whether an object is located inside or outside of a specific territory. JOSM has an internal database for this. The territories file is an osm file and can be downloaded [/export/HEAD/josm/trunk/data/boundaries.osm here] and opened in JOSM to investigate it [attachment:boundaries.png (screenshot preview)]. It contains borders of all countries of the world. Due to performance reasons the borders are simplified. They can be refined for special cases on request. The territories are "tagged" with their [https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 ISO_3166-1_alpha-2 codes]. USA, Canada, China, India and Australia have additional boundaries for their subdivisions. See the following examples on how to use the territory selectors. Territory selectors are less useful in mappaint styles and can be very resource heavy there. However they are much more useful for [wiki:Help/Validator/MapCSSTagChecker mapcss based validator rules]. To select territories with left-hand-traffic or right-hand-traffic, there is a simpler way, see [#PseudoClasses]. See #10387 for main implementation of this feature.
+{{{
+#!mapcss
+node[inside("FR")]                    /* matches any node located inside of France (this includes all the overseas territories)                                     */
+node[inside("FX")]                    /* matches any node located inside of Metropolitan France (i.e. only the mainland part with its near islands including Corse) */
+node[inside("EU")]                    /* matches any node located inside of the European Union                                                                      */
+node[inside("FR,DE")]                 /* matches any node located inside of France __OR__ inside of Germany                                                         */
+node[inside("US-FL")]                 /* matches any node located inside of the US state Florida                                                                    */
+node[outside("FR")]                   /* matches any node located outside of France                                                                                 */
+node[outside("FR,DE")]                /* matches any node located outside of France __AND__ outside of Germany                                                      */
+node[inside("US")][outside("US-FL")]  /* matches any node located inside of the USA except the state Florida                                                        */
+}}}
+=== Link selector ===
+way[oneway?!]                  /* matches any way with a false value in the tag 'oneway' */
+}}}
+}}}
+=== Territory selector === #Territoryselector
+You can test whether an object is located inside or outside of a specific territory. JOSM has an internal database for this. The [source:/trunk/resources/data/boundaries.osm territories file] can be downloaded and opened in JOSM to investigate it [attachment:boundaries.png (screenshot preview)]. It contains borders of all countries of the world. Due to performance reasons the borders are simplified. They can be refined for special cases on request. The territories are "tagged" with their [https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 ISO_3166-1_alpha-2 codes]. USA, Canada, China, India and Australia have additional boundaries for their subdivisions. See the following examples on how to use the territory selectors. Territory selectors are less useful in mappaint styles and can be very resource heavy there. However they are much more useful for [wikitr:/Help/Validator/MapCSSTagChecker mapcss based validator rules]. To select territories with left-hand-traffic or right-hand-traffic, there is a simpler way, see [#PseudoClasses Pseudo Classes]. See #10387 for main implementation of this feature.
+{{{
+#!mapcss
+                                      /* matches any node located …                             */
+node[inside("FR")]                    /* … inside of France (includes the overseas territories) */
+node[inside("FX")]                    /* … inside of Metropolitan France (i.e. only the
+                                         mainland part with its near islands including Corse)   */
+node[inside("EU")]                    /* … inside of the European Union                         */
+node[inside("FR,DE")]                 /* … inside of France __OR__ inside of Germany            */
+node[inside("US-FL")]                 /* … inside of the US state Florida                       */
+node[outside("FR")]                   /* … outside of France                                    */
+node[outside("FR,DE")]                /* … outside of France __AND__ outside of Germany         */
+node[inside("US")][outside("US-FL")]  /* … inside of the USA except the state Florida           */
+}}}
+=== Link selector ===#LinkSelector
 In a child selector, you can formulate conditions on the link between a parent and a child object.
 …
 }}}
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Operator'''
 }}}
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Description'''
 }}}
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Example'''
 }}}
 |-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
+{{{#!td align=center  valign=top
 `=`
 }}}
 {{{#!td align=left  valign=top
 Exact match of the role name. The name name {{{role}}} is compulsory in this context.
+Exact match of the role name. The name `role` is compulsory in this context.
 }}}
 {{{#!td align=left  valign=top
 {{{
 #!mapcss
+relation >[role=residential] way           /* without quotes always case insensitive */
+relation >[role="My name"]   way           /* use quotes for if the role value includes spaces or if case sensitive matching is important */
+}}}
+}}}
+The operators {{{!=, ^=, $=, *=, and ~=}}} are supported too. Please refer to [#condition_selector_operators condition selector operators].
+Nodes in ways and members in relations are ordered. You can formulate conditions on the position of a node in a way or a member
+object in a relation. Positive numbers count from first to last element, negative numbers (since r8236) count from last to first element.
+relation >[role=residential] way
+relation >[role="My name"]   way           /* use quotes if the role value includes spaces or other special characters */
+}}}
+}}}
+The operators `!=`, `^=`, `$=`, `*=` and `~=` are supported too. Please refer to [#condition_selector_operators condition selector operators].
+Nodes in ways and members in relations are ordered. You can formulate conditions on the position of a node in a way or a member object in a relation. Positive numbers count from first to last element, negative numbers (since r8236) count from last to first element.
 {{{
 …
 }}}
 === Zoom selector ===
+You can decorate a type selector with a '''zoom selector'''. The zoom selector restricts the range of zoom levels
+at which the respective MapCSS rule is applied.
+{{{#!th align=left valign=top
+'''Example'''
+}}}
+{{{#!th align=left valign=top
+'''Description'''
+}}}
+|-------------------------------------------------------------------------------
+|| {{{way|z12 {...} }}} || At zoom level 12 ||
+|| {{{way|z13-15 {...} }}} || From 13 to 15 ||
+|| {{{way|z16- {...} }}} || 16 and above ||
+|| {{{way|z-12 {...} }}} || 12 and below ||
+|| {{{way {...} }}} || any zoom level ||
+You can decorate a type selector with a '''zoom selector'''. The zoom selector restricts the range of zoom levels at which the respective MapCSS rule is applied.
+||= '''Example 1''' =||= '''Example 2''' =||= '''Example 3''' =||= '''Description''' =||
+|| `way|z12 {...}` || `node|z12 {...}` || `node|z12[...] {...}` || At zoom level 12 ||
+|| `way|z13-15 {...}` || `node|z13-15 {...}` || `way|z13-15[...] {...}` ||From 13 to 15 ||
+|| `way|z16- {...}` || `node|z16- {...}` || `node|z16-[...] {...}` || 16 and above ||
+|| `way|z-12 {...}` || `node|z-12 {...}` || `node|z-12[...] {...}` || 12 and below ||
+|| `way {...}` || `node{...}` || `way[...] {...}` || any zoom level ||
 The precise definition of scale ranges for each zoom level may change in the future. By rule of thumb you can expect to be approximately at zoom level ''n'' when imagery displays slippymap tiles of level ''n''.
+=== Pseudo Classes ===
+See [/doc/org/openstreetmap/josm/gui/mappaint/mapcss/Condition.PseudoClasses.html Javadoc] for the up-to-date list of pseudo classes supported by JOSM's MapCSS implementation.
+|| {{{:closed}}} || true for ways where the first node is the same as the last and for any (completely downloaded) multipolygon relation ||
+|| {{{:closed2}}} || same as above, but this one ignores if a mulipolygon is downloaded completely (since r9099) ||
+|| {{{:completely_downloaded}}} || true for a relation whose members are all downloaded (since r9099) ||
+|| {{{:new}}} || all new objects ||
+|| {{{:connection}}} || true for nodes that are used by more than one way ||
+|| {{{:unconnected}}} || true for nodes that are not used by any way (since r6687) ||
+|| {{{:tagged}}} || What JOSM considers tagged, i.e. an object that with a tag key other than the following: {{{source*, source_ref, note, comment, converted_by, created_by, watch*, fixme, FIXME, description, attribution}}} (version r4008; in this list, {{{*}}} is a glob)
+|| {{{:righthandtraffic}}} || true if there is right-hand traffic at the current location (since r7193); see [[left-right-hand-traffic]] for screenshot of areas ||
+|| {{{:clockwise}}} || Whether the way is closed and oriented clockwise, or non-closed and the 1st, 2nd and last node are in clockwise order. ||
+|| {{{:anticlockwise}}} || Whether the way is closed and oriented anticlockwise, or non-closed and the 1st, 2nd and last node are in anticlockwise order. ||
+|| {{{:unclosed_multipolygon}}} || true for fully loaded unclosed multipolygon relations (since r8252) ||
+|| {{{:open_end}}} || to select end nodes of unclosed multipolygon relations with `relation:unclosed_multipolygon >:open_end node` (since r8252) ||
+|| {{{:in-downloaded-area}}} || true if an object is within source area and false if in the hatched area (since r8495). ||
+|| {{{:selected}}} || true if an object is selected in the editor (since r9341). ||
+|| {{{:modified}}} || changed objects (since r7193). ||
+You can also negate pseudo classes. E.g. {{{!:new}}} for all old objects.
+=== Pseudo Classes ===#PseudoClasses
+See [/doc/org/openstreetmap/josm/gui/mappaint/mapcss/ConditionFactory.PseudoClasses.html Javadoc] for the up-to-date list of pseudo classes supported by JOSM's MapCSS implementation.
+||= '''Class''' =||= '''Description''' =||
+|| `:closed` || true for ways where the first node is the same as the last and for any (completely downloaded) multipolygon relation ||
+|| `:closed2` || same as above, but this one ignores if a multipolygon is downloaded completely (since r9099) ||
+|| `:completely_downloaded` || true for a relation whose members are all downloaded (since r9099) ||
+|| `:new` || all new objects ||
+|| `:connection` || true for nodes that are used by more than one way ||
+|| `:unconnected` || true for nodes that are not used by any way (since r6687) ||
+|| `:tagged` || What JOSM considers tagged, i.e. an object that with a tag key other than the following: `source*`, `source_ref`, `note`, `comment`, `converted_by`, `created_by`, `watch*`, `fixme`, `FIXME`, `description`, `attribution` (version r4008; in this list, `*` is a glob)
+|| `:area-style` || true if the object has an area style ||
+|| `:righthandtraffic` || true if there is right-hand traffic at the current location (since r7193); see [wikitr:/left-right-hand-traffic left-right-hand-traffic] for screenshot of areas ||
+|| `:clockwise` || Whether the way is closed and oriented clockwise, or non-closed and the 1st, 2nd and last node are in clockwise order. ||
+|| `:anticlockwise` || Whether the way is closed and oriented anticlockwise, or non-closed and the 1st, 2nd and last node are in anticlockwise order. ||
+|| `:unclosed_multipolygon` || true for fully loaded unclosed multipolygon relations (since r8252) ||
+|| `:open_end` || to select end nodes of unclosed multipolygon relations with `relation:unclosed_multipolygon >:open_end node` (since r8252) ||
+|| `:in-downloaded-area` || true if an object is within source area and false if in the hatched area (since r8495). ||
+|| `:selected` || true if an object is selected in the editor (since r9341). ||
+|| `:highlighted` || true if the object is highlighted ||
+|| `:modified` || changed and new objects (since r7193). ||
+You can also negate pseudo classes. E.g. `!:new` for all old objects.
 === Layer Identifier ===
 Layers can be used to create more than one style for a single object. Here is an example:
 {{{
 …
+}
 way[access][access!=public]::non_public_access_layer {
+way[access][access!=yes]::non_public_access_layer {
     width: +2;
     color:red;
 …
+}
 }}}
 This draws all secondary and tertiary roads in yellow and orange respectively. Any road with an access tag other than public will get an extra line style below ('''{{{object-z-index:-1.0;}}}''') the main line. If that part of the street happens to be a bridge, it will also get a half transparent blue overlay. The relative width value ('''{{{width: +2;}}}''') refers to the width on the default layer (2 or 3 in this case).
+This draws all secondary and tertiary roads in yellow and orange respectively. Any road with an access tag other than yes will get an extra line style below ('''`object-z-index:-1.0;`''') the main line. If that part of the street happens to be a bridge, it will also get a half transparent blue overlay. The relative width value ('''`width: +2;`''') refers to the width on the default layer (2 or 3 in this case).
 The name for the layer can be any identifier.
 If you omit the layer in the selector, this is the same as using {{{::default}}}.
+If you omit the layer in the selector, this is the same as using `::default`.
 One more example:
 …
 The result looks this way:
+[[Image(multiple_icons_and_texts.png)]]
 In addition, you can use the * layer to override and initialize all layers.[[br]]
+[[Image(multiple_icons_and_texts.png,link=)]]
+In addition, you can use the * layer to override and initialize all layers. \\
 It overrides all existing subparts, so
 …
 way::A { a; }
 way::B { b; }
+way::* { c; }
+way::* { c; }  /* overrides all existing subparts */
 }}}
 is equivalent to
 …
 way::A { a; }
 way::B { b; }
+way::A { c; }
+way::B { c; }
+way::A { c; } /* overrides a with c all existing subparts */
+way::B { c; } /* overrides b with c all existing subparts */
 }}}
 And it initializes new subparts. In other words:
 …
 }}}
 === Grouping ===
 Rules with common declaration block can be grouped into one:
 {{{
 …
 way.path { text:auto; text-color: green; text-position: line; text-offset: 5; }
 }}}
+You can also negate classes. E.g. {{{way!.path}}} for all ways, which are not part of the class ''.path''.
+== @supports rule for conditional processing [''since 8087''] ==
+@supports rules are used to skip a section of the style under certain conditions. Typically you want to use a feature which is introduced in a newer version of JOSM, but like to have a fall back style for users of older JOSM clients. Example:
+You can also negate classes. E.g. `way!.path` for all ways, which are not part of the class ''.path''.
+=== Classes and Layer together ===
+If you want to use layer and classes together, please note that you have to identify the class via is_prop_set.
+{{{#!mapcss
+node[railway=signal] { set sgnl; }
+/* it doesn't work */
+node.sgnl::layer_signal_icon  { z-index: 1000; ... icon: icon/signal-icon.svg; ... }
+node.sgnl::layer_signal_text  { z-index: 1010; ... text: concat("Name of signal: ", tag("ref")); ..... )
+/* use instead: is_prop_set("...", "default") */
+node[is_prop_set("sgnl", "default")]::layer_signal_icon  { z-index: 1000; ... icon: icon/signal-icon.svg; ... }
+node[is_prop_set("sgnl", "default")]::layer_signal_text  { z-index: 1010; ... text: concat("Name of signal: ", tag("ref")); ..... )
+}}}
+=== @supports Conditional Processing  ===
+@supports rules are used to skip a section of the style under certain conditions. Typically you want to use a feature which is introduced in a newer version of JOSM, but like to have a fall back style for users of older JOSM clients. This feature came with r8087. Example:
 {{{
 #!mapcss
 …
 }}}
 {{{#!td
 Only include {{{@supports}}} section when the current version of JOSM is greater than or equal to the specified number.
+Only include `@supports` section when the current version of JOSM is greater than or equal to the specified number.
 }}}
 |-
 …
 }}}
 {{{#!td
 Only include {{{@supports}}} section when the current version of JOSM is lower than or equal to the specified number.
+Only include `@supports` section when the current version of JOSM is lower than or equal to the specified number.
 }}}
 |-
 …
 }}}
 {{{#!td
 Only include {{{@supports}}} section when the name of the editor / renderer matches the given string. In JOSM, the only accepted value is {{{josm}}}.
+}}}
 Conditions can be combined with {{{and}}}:
+Only include `@supports` section when the name of the editor / renderer matches the given string. In JOSM, the only accepted value is `josm`.
+}}}
+Conditions can be combined with `and`:
 {{{
 …
 }}}
 Other logical operators like {{{or}}} and {{{not}}} can also be used. Parentheses are needed if you want to combine different logical operators:
+Other logical operators like `or` and `not` can also be used. Parentheses are needed if you want to combine different logical operators:
 {{{
 …
 }}}
+Since @supports rules are only supported in JOSM 8087 and later, you should also specify this as minimum JOSM version in the meta selector:
+Since @supports rules are only supported in JOSM r8087 and later, you should also specify this as minimum JOSM version in the meta selector:
 {{{
 …
 }}}
 == Style settings ==
+[[Help/Dialog/MapPaint/StyleSettings|Styles settings]] are used to provide the user settings to customize a mappaint style. The user can use them in the MapPaint dialog. Style settings are availible since r7450. The internal style provides style settings since r7454. Note that there are plans to extend the implementation of style settings (currently there are only boolean values supported), so the mapcss syntax for style settings could change in the future (see #10435).
+create a setting:
+[wikitr:/Help/Dialog/MapPaint/StyleSettings Styles settings] are used to provide the user settings to customize a mappaint style. The user can use them in the [wikitr:/Help/Dialog/MapPaint MapPaint dialog]. The following `type` of settings are available:
+* `boolean` (since r7450)
+* `double` (since r15731, see #10435)
+* `string` (since r15731, see #10435)
+* `color` (since r16843, see #10435)
+=== Settings of type `boolean` ===
+Create a setting of type `boolean`:
 {{{
 #!mapcss
 …
+}
 }}}
+use a setting:
+Use a setting of type `boolean`:
 {{{
 #!mapcss
 …
 }}}
+== Properties ==
+=== Settings of type `double` ===
+Create a setting of type `double`:
+{{{
+#!mapcss
+setting::place_font_size {
+  type: double;
+  label: tr("Set place name font size...");
+  default: 11;
+}
+}}}
+Use a setting of type `double`:
+{{{
+#!mapcss
+node.place, way.place, area.place {
+  font-size: setting("place_font_size");
+}
+}}}
+=== Settings of type `string` ===
+Create a setting of type `string`:
+{{{
+#!mapcss
+setting::textdisplay {
+  type: string;
+  label: tr("key used for displaying");
+  default: "name"; /* examples for usage: alt_name, old_name, addr:housename, ref, operator, ... */
+}
+}}}
+Use a setting of type `string`:
+{{{
+#!mapcss
+way {
+  text: tag(setting("textdisplay"));
+}
+}}}
+=== Settings of type `color` ===
+Create a setting of type `color`. The `default` color can be any color as understood under [wikitr:/Help/Styles/MapCSSImplementation#Propertyvaluesexplanations Property values explanations]:
+{{{
+#!mapcss
+setting::colordisplay {
+  type: color;
+  label: tr("key used for displaying");
+  default: colorDisplayCustomPref#FF00FF;
+}
+}}}
+Use a setting of type `color`:
+{{{
+#!mapcss
+way {
+  color: setting("colordisplay");
+}
+}}}
+=== Grouping settings ===
+Similar settings can be grouped together by defining ''settings groups'' (since r15289):
+{{{
+#!mapcss
+settings::my_group {
+  label: tr("my wonderful group");
+  icon: "my_beautiful_icon";
+}
+}}}
+Label is mandatory, icon is optional.
+Once a setting group is defined, it can be referenced from all settings belonging to it:
+{{{
+#!mapcss
+setting::hide_icons {
+  type: boolean;
+  label: tr("Hide icons at low zoom");
+  default: true;
+  group: "my_group";
+}
+}}}
+Settings groups are displayed as sub-menus from the style settings menu. If at least two settings belong to a group, a special "Toggle all settings" menu item allows to quickly switch on/off all settings from this group at once. Usage example: [wikitr:/Styles/MapWithAI MapWithAI].
+== Properties ==#Properties
 === General properties ===
 ||=  '''Key''' =||= '''Description''' =||= '''Value Format''' =||= '''Default Value''' =||
 || {{{z-index}}}                                 || Specify the order the objects are drawn: The objects with higher z-index are drawn on top of objects with lower z-index || ''Number'' (can be negative) ||  0  ||
 || {{{major-z-index}}} || Similar to {{{z-index}}}, but it has higher priority than {{{z-index}}}. So if one object has a higher {{{major-z-index}}} than the other, it is drawn on top. If the {{{major-z-index}}} is the same, {{{z-index}}} decides. || ''Number'' (can be negative) ||  Depends on style element: area: 1, casing: 2, left-/right-casing: 2.1, line-pattern: 2.9, line: 3, point: 4, default-point: 4.1, line-text: 4.9, point-text: 5   ||
 || {{{object-z-index}}} || Similar to {{{z-index}}}, but has lower priority. Controls the painting order for overlapping objects. E.g. for two crossing ways with text: Use {{{z-index}}} or {{{major-z-index}}} if you first want to draw the two lines and then the two captions. Use {{{object-z-index}}} if one of the ways should be completely on top of the other. || ''Number'' (can be negative) ||  0  ||
 || {{{modifier}}} || Better control, whether a default line / node symbol is generated by JOSM. This happens when there is no proper style ({{{modifier=false}}}) found on any layer. || {{{false}}} or {{{true}}} || {{{false}}} for the default layer and {{{true}}} for any other layer ||
+|| `z-index` || Specify the order the objects are drawn: The objects with higher z-index are drawn on top of objects with lower z-index || ''Number'' (can be negative) ||  0  ||
+|| `major-z-index` || Similar to `z-index`, but it has higher priority than `z-index`. So if one object has a higher `major-z-index` than the other, it is drawn on top. If the `major-z-index` is the same, `z-index` decides. || ''Number'' (can be negative) || Depends on style element: area: 1, casing: 2, left-/right-casing: 2.1, line-pattern: 2.9, line: 3, point: 4, default-point: 4.1, line-text: 4.9, point-text: 5 ||
+|| `object-z-index` || Similar to `z-index`, but has lower priority. Controls the painting order for overlapping objects. E.g. for two crossing ways with text: Use `z-index` or `major-z-index` if you first want to draw the two lines and then the two captions. Use `object-z-index` if one of the ways should be completely on top of the other. || ''Number'' (can be negative) ||  0  ||
+|| `modifier` || Better control, whether a default line / node symbol is generated by JOSM. This happens when there is no proper style (`modifier=false`) found on any layer. || `false` or `true` || `false` for the default layer and `true` for any other layer ||
+Note that due to performance reasons the values for the three z-indexes are limited to 24 bit float values with max. 5 decimal digits. Currently the internal mappaint style uses values with max. 2 digits before and after the decimal separator. To avoid problems use values of z-indexes between -99.999 and +99.999. (See also #14485)
 === Icon and symbol styles ===
 ||=  '''Key''' =||= '''Description''' =||= '''Value Format''' =||= '''Default Value''' =||
 || {{{icon-image}}} || The icon at node position || ''Image'' ||  -  ||
 || {{{icon-opacity}}} || Opacity of the icon image || ''Opacity'' ||  1.0  ||
 || {{{icon-width}}} || Width of the icon. If only one of the properties {{{icon-width}}} and {{{icon-height}}} is given, the image will be scaled proportionally. The icon will keep the original size, if neither {{{icon-width}}} nor {{{icon-height}}} is set. || ''Number'' ||  -  ||
 || {{{icon-height}}} || Height of the icon. (See {{{icon-width}}}) || ''Number'' ||  -  ||
+|| `icon-image` || The icon at node position. See also [wikitr:/Help/Styles/Images Images]. || ''Image'' ||  -  ||
+|| `icon-opacity` || Opacity of the icon image || ''Opacity'' ||  1.0  ||
+|| `icon-width` || Width of the icon. If only one of the properties `icon-width` and `icon-height` is given, the image will be scaled proportionally. The icon will keep the original size, if neither `icon-width` nor `icon-height` is set. || ''Number'' ||  -  ||
+|| `icon-height` || Height of the icon. (See `icon-width`) || ''Number'' ||  -  ||
 || `icon-offset-x` || Shift the icon in horizontal direction (positive values to the right) (since r8085) || ''Number'' ||  0  ||
 || `icon-offset-y` || Shift the icon in vertical direction (positive values downwards) (since r8085) || ''Number'' ||  0  ||
+|| `icon-rotation` || Rotate the icon clockwise or anti clockwise (negative value)(since r8260) || `[rad]`, `[rad]rad`, `[deg]°`, `[deg]deg`, `[grad]grad`, `[turn]turn` ([https://developer.mozilla.org/en/docs/Web/CSS/angle definition]) or a cardinal direction (e.g. `northeast` or `sw`); See also the functions `degree_to_radians`, `cardinal_to_radians`. ||  -  ||
+|| `icon-position` || Define the position of the icon for areas. Same as `text-position` (since r11730). || {{{center}}}, {{{inside}}}, {{{line}}} || {{{center}}} ||
+|| {{{symbol-shape}}}                               || Display a symbol at the position of the node || {{{square}}}, {{{circle}}}, {{{triangle}}}, {{{pentagon}}}, {{{hexagon}}}, {{{heptagon}}}, {{{octagon}}}, {{{nonagon}}}, {{{decagon}}} ||  -  ||
+|| {{{symbol-size}}} || Size of the symbol || ''Number'', can be relative ("+4") ||  10  ||
+|| {{{symbol-stroke-width}}} || outline stroke width || ''Width'' ||  1.0 if {{{symbol-stroke-color}}} is set  ||
+|| {{{symbol-stroke-color}}} || line color || ''Color'' || {{{#FFC800}}} if {{{symbol-stroke-width}}} is set ||
+|| {{{symbol-stroke-opacity}}} || line opacity || ''Opacity'' ||  1.0  ||
+|| {{{symbol-fill-color}}} || fill color for the shape || ''Color'' || {{{blue}}}, unless either {{{symbol-stroke-width}}} or {{{symbol-stroke-color}}} is set ||
+|| {{{symbol-fill-opacity}}} || fill opacity || ''Opacity'' || 1.0  ||
+|| {{{text-...}}}, {{{font-...}}} ||||||  general text & font properties  ||
+|| {{{text-anchor-horizontal}}} || horizontal text label placement || {{{left}}}, {{{center}}}, {{{right}}} ||  {{{right}}}  ||
+|| {{{text-anchor-vertical}}} || vertical text label placement || {{{above}}}, {{{top}}}, {{{center}}}, {{{bottom}}}, {{{below}}} ||  {{{bottom}}}  ||
+Do not rely on the default values for {{{symbol-...}}} properties (except for {{{opacity}}}). They are intended for "quick & dirty" style sheets and should be set to an explicit value.
+=== Line styles ===
+|| `icon-rotation` || Rotate the icon clockwise or anti clockwise (negative value)(since r8260) || `[rad]`, `[rad]rad`, `[deg]°`, `[deg]deg`, `[grad]grad`, `[turn]turn` ([https://developer.mozilla.org/en/docs/Web/CSS/angle definition]) \\ or a cardinal direction (e.g. `northeast` or `sw`); \\ or `way` to rotate the icon in the direction of the parent way. \\ See also the functions `degree_to_radians`, `cardinal_to_radians`. \\Since version 18678 function parent_way_angle() is an alternativ to way: e.g. {{{ way > node[...]::layer_x { ... icon-rotation: parent_way_angle(); ... } }}}  ||  -  ||
+|| `icon-position` || Define the position of the icon for areas. Same as `text-position` (since r11730). || `center`, `inside`, `line` ||  `center`  ||
+|| `symbol-shape` || Display a symbol at the position of the node || `square`, `circle`, `triangle`, `pentagon`, `hexagon`, `heptagon`, `octagon`, `nonagon`, `decagon` ||  -  ||
+|| `symbol-size` || Size of the symbol || ''Number'', can be relative ("+4") ||  10  ||
+|| `symbol-stroke-width` || outline stroke width || ''Width'' || 1.0 if `symbol-stroke-color` is set ||
+|| `symbol-stroke-color` || line color || ''Color'' || `#FFC800` if `symbol-stroke-width` is set ||
+|| `symbol-stroke-opacity` || line opacity || ''Opacity'' ||  1.0  ||
+|| `symbol-fill-color` || fill color for the shape || ''Color'' || `blue`, unless either `symbol-stroke-width` or `symbol-stroke-color` is set ||
+|| `symbol-fill-opacity` || fill opacity || ''Opacity'' ||  1.0  ||
+|| `text-...`, `font-...` ||||||  see general '''Text & Font properties''' ||
+Do not rely on the default values for `symbol-...` properties (except for `opacity`). They are intended for "quick & dirty" style sheets and should be set to an explicit value.
+=== Line styles ===#LineStyles
 ||=  '''Key''' =||= '''Description''' =||= '''Value Format''' =||= '''Default Value''' =||
+|| {{{width}}} || Line width || ''Width'' ||  -  ||
+|| {{{color}}} || Line color || ''Color'' ||  value of {{{fill-color}}} or (if unset) JOSM's default untagged color ({{{#808080}}}) ||
+|| {{{opacity}}} || How transparent the line is. || ''Opacity'' ||  1.0  ||
+|| {{{dashes}}} || An array of alternating on/off lengths || list of numbers, e.g. [[br]]> 15, 5 [[br]][[br]]may be written as expression: [[br]] > {{{list(3, 4, 5, 6)}}} [[br]][[br]]or the keyword {{{none}}}[[br]]to turn dashes off ||  -  ||
+|| {{{dashes-offset}}} || shift the dash pattern by a certain amount || ''Number'' (>= 0) ||  0  ||
+|| {{{dashes-background-color}}} || The color to use in between the dashes (optional) || ''Color'' ||  -  ||
+|| {{{dashes-background-opacity}}} || Opacity value for the dashes background || ''Opacity'' ||  value of {{{opacity}}}  ||
+|| {{{linecap}}} || Shape at the end of the line (see [https://www.w3.org/TR/SVG/painting.html#StrokeLinecapProperty here]) || {{{none}}}, {{{round}}}, {{{square}}} ||  {{{none}}}  ||
+|| {{{linejoin}}} || Shape at the line corners || {{{round}}}, {{{miter}}}, {{{bevel}}} ||  {{{round}}}  ||
+|| {{{miterlimit}}}                                   || Applies for {{{linejoin: miter}}}. Sets the maximum overshoot when line segments meet at a very small angle || ''Number'' (>= 1.0) ||  10.0  ||
+|| {{{offset}}} || Move line to the left or right (when looking in way direction). This could be used to draw multiple lanes for one way or mark left and right side of a way differently. || ''Number'' (positive value moves line to the left, negative to the right) ||  0  ||
+|| {{{text-position}}} || set to {{{line}}}, if text should be drawn along the line || {{{line}}}, {{{center}}} ||  -  ||
+|| {{{text-...}}}, {{{font-...}}} ||||||  general text & font properties  ||
+|| `repeat-image` || repeated image along a line ''[since 5801]'' || ''Image'' ||  -  ||
+|| `repeat-image-width` || Width of the image (optional, see `icon-width`) ''[since 5811]'' || ''Number'' ||  -  ||
+|| `repeat-image-height` || Height of the image (optional) ''[since 5811]'' || ''Number'' ||  -  ||
+|| `repeat-image-align` || Alignment of the image. Top-, bottom edge or the (horizontal) center line of the image will be along the line ''[since 5801]'' || `top`, `center`, `bottom` ||  `center`  ||
+|| `repeat-image-offset` || Offset from the line ''[since 5801]'' || ''Number'' ||  0  ||
+|| `repeat-image-spacing` || Spacing between repeated images ''[since 5801]'' || ''Number'' ||  0  ||
+|| `repeat-image-phase` || Initial spacing at the beginning of the line ''[since 5812]'' || ''Number'' ||  0  ||
+All these properties (except for {{{text-...}}} and {{{font-...}}}) exist also with the {{{casing-}}} prefix. The casing is a second independent line element, that is drawn below the normal line and can be used to draw a thin frame around the line in another color.
+|| `width` || Line width || ''Width'' ||  -  ||
+|| `color` || Line color || ''Color'' ||  value of `fill-color` or\\(if unset) JOSM's default \\untagged color (`#808080`) ||
+|| `opacity` || How transparent the line is. || ''Opacity'' ||  1.0  ||
+|| `dashes` || An array of alternating on/off lengths || list of numbers, e.g. \\> 15, 5 \\ \\may be written as expression: \\ > `list(3, 4, 5, 6)` \\ \\or the keyword `none` \\to turn dashes off ||  -  ||
+|| `dashes-offset` || shift the dash pattern by a certain amount || ''Number'' (>= 0) ||  0  ||
+|| `dashes-background-color` || The color to use in between the dashes (optional) || ''Color'' ||  -  ||
+|| `dashes-background-opacity` || Opacity value for the dashes background || ''Opacity'' ||  value of `opacity`  ||
+|| `linecap` || Shape at the end of the line (see [https://www.w3.org/TR/SVG/painting.html#StrokeLinecapProperty here]) || `none`, `round`, `square` ||  `none`  ||
+|| `linejoin` || Shape at the line corners || `round`, `miter`, `bevel` ||  `round`  ||
+|| `miterlimit` || Applies for `linejoin: miter`. \\Sets the maximum overshoot when line segments meet at a very small angle || ''Number'' (>= 1.0) ||  10.0  ||
+|| `offset` || Move line to the left or right (when looking in way direction). \\This could be used to draw multiple lanes for one way or mark left and right side of a way differently. || ''Number'' (positive value moves line to the left,\\negative to the right) ||  0  ||
+|| `text-position` || set to `line`, if text should be drawn along the line || `line`, `center` ||  -  ||
+|| `text-...`,\\`font-...` |||||| see general '''Text & Font properties  ||
+|| `repeat-image` || repeated image along a line ''(since r5801)'' || ''Image'' ||  -  ||
+|| `repeat-image-width` || Width of the image (optional, see `icon-width`) ''(since r5811)'' || ''Number'' ||  -  ||
+|| `repeat-image-height` || Height of the image (optional) ''(since r5811)'' || ''Number'' ||  -  ||
+|| `repeat-image-align` || Alignment of the image.\\Top-, bottom edge or the (horizontal) center line of the image will be along the line ''(since r5801)'' || `top`, `center`, `bottom` ||  `center`  ||
+|| `repeat-image-offset` || Offset from the line ''(since r5801)'' || ''Number'' ||  0  ||
+|| `repeat-image-spacing` || Spacing between repeated images ''(since r5801)'' || ''Number'' ||  0  ||
+|| `repeat-image-phase` || Initial spacing at the beginning of the line ''(since r5812)'' || ''Number'' ||  0  ||
+|| `repeat-image-opacity` || Opacity of the repeated image ''(since r16700)'' || ''Number'' ||  1.0  ||
+All these properties (except for `text-...` and `font-...`) exist also with the `casing-` prefix. The casing is a second independent line element, that is drawn below the normal line and can be used to draw a thin frame around the line in another color.
 ||=  '''Key''' =||= '''Description''' =||= '''Value Format''' =||= '''Default Value''' =||
 || {{{casing-width}}}               || Width of the border on both sides of the main line. In JOSM < 5214: Total width of the casing || ''Width'' (revers to {{{width}}} if relative width is specified) ||  -  ||
 || {{{casing-color}}} || Casing color || ''Color'' ||  value of {{{fill-color}}} or (if unset) JOSM's default untagged color ({{{#808080}}}) ||
 || {{{casing-opacity}}} || How transparent the casing is. || ''Opacity'' ||  1.0  ||
 || {{{casing-}}}... || ... || ... ||  ...  ||
 Similar to {{{casing-}}}, there is also the {{{left-casing-}}} and {{{right-casing-}}} prefix. It draws additional lines to the left and to the right of the main line.
+=== Area styles ===
 ||=  '''Key''' =||= '''Description''' =||= '''Value Format''' =||= '''Default Value''' =||
 || {{{fill-color}}} || Color in which to fill the area. Until 11700, the alpha component was set to 50 to create a transparency effect. || ''Color'' ||  -  ||
 || {{{fill-image}}} || Image pattern || ''Image'' ||  -  ||
 || {{{fill-extent}}} || Set this property, to draw only the outline of the area. The number specifies, how far to fill from the border of the area towards the center. (If unset, the area will be filled completely) ''[since 9008]'' || ''Number'' ||  -  ||
 || {{{fill-opacity}}} || How transparent the fill is; applies to both color and image || ''Opacity'' || 0.2 ''[since 11700, 1.0 before that]'' (can be changed with the {{{mappaint.fillalpha}}} and {{{mappaint.fill-image-alpha}}} preferences)  ||
 || {{{text-position}}} || set to {{{center}}}, if text should be drawn in the center of the area. Set to {{{inside}}} to place the text completely inside the area (since r11722). || {{{line}}}, {{{center}}}, {{{inside}}} ||  -  ||
 || {{{text-...}}}, {{{font-...}}} ||||||  general text & font properties  ||
 Required properties to create an Area style: {{{fill-color}}} or {{{fill-image}}}
+|| `casing-width` || Width of the border on both sides of the main line. \\In JOSM < 5214: Total width of the casing || ''Width'' (revers to `width` if relative width is specified) ||  -  ||
+|| `casing-color` || Casing color || ''Color'' ||  value of `fill-color` or (if unset) \\JOSM's default untagged color (`#808080`) ||
+|| `casing-opacity` || How transparent the casing is. || ''Opacity'' ||  1.0  ||
+|| `casing-`... || ... || ... ||  ...  ||
+Similar to `casing-`, there is also the `left-casing-` and `right-casing-` prefix. It draws additional lines to the left and to the right of the main line.
+=== Area styles ===#AreaStyles
+||= '''Key''' =||= '''Description''' =||= '''Value Format''' =||= '''Default Value''' =||
+|| `fill-color` || Color in which to fill the area. Until 11700, the alpha component was set to 50 to create a transparency effect. || ''Color'' ||  -  ||
+|| `fill-image` || Image pattern || ''Image'' ||  -  ||
+|| `fill-extent` || Set this property, to draw only the outline of the area. The number specifies, how far to fill from the border of the area towards the center. (If unset, the area will be filled completely) ''(since r9008)'' || ''Number'' ||  -  ||
+|| `fill-extent-threshold` || Set this property, to draw full area when the given percentage of coverage is reached. Can be greater than 100% as the covered area is estimated as **perimeter * extent**. || ''Number'' ||  -  ||
+|| `fill-opacity` || How transparent the fill is; applies to both color and image || ''Opacity'' || 0.2 ''(since r11700, 1.0 before that)'' \\(can be changed with the `mappaint.fillalpha` and \\`mappaint.fill-image-alpha` preferences)  ||
+|| `text-position` || set to `center`, if text should be drawn in the center of the area. Set to `inside` to place the text completely inside the area. ''(since r11722)'' || `line`, `center`, `inside` ||  -  ||
+|| `text-...`, `font-...` ||||||  see general text & font properties  ||
+Required properties to create an Area style: `fill-color` or `fill-image`
 === Text & Font properties ===
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Key'''
 }}}
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Description'''
 }}}
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Value Format'''
 }}}
 {{{#!th align=left valign=top
+{{{#!th valign=top
 '''Default Value'''
 }}}
 |-------------------------------------------------------------------------------
 {{{#!td align=left  valign=top
+{{{text}}}
+`text`
 }}}
 {{{#!td align=left  valign=top
 How to find the label text. No label is displayed, unless this instruction is present.
+How to find the label text.\\No label is displayed, unless this instruction is present.
 }}}
 {{{#!td align=left  valign=top
+{{{auto}}}
    Derive the text automatically. The default name tags are: "{{{name:}}}"+''<LANG>'', "{{{name}}}", "{{{int_name}}}", "{{{ref}}}", "{{{operator}}}", "{{{brand}}}" and "{{{addr:housenumber}}}".
    Configure a list of tag names in the preference "{{{mappaint.nameOrder}}}" in order to change this list. (After changing the list, a restart of JOSM is required.)
+`auto`
+  Derive the text automatically. The default name tags are: "`name:`"+''<LANG>'', \\"`name`", "`int_name`", "`ref`", "`operator`", "`brand`" and "`addr:housenumber`".
+  Configure a list of tag names in the preference "`mappaint.nameOrder`" in order \\ to change this list. (After changing the list, a restart of JOSM is required.)
 ''String''
    Denotes the key of the tag whose value is used as text.
+  Denotes the key of the tag whose value is used as text.
 ''Expressions''
   You can enter an expression to compute the text to be displayed. Examples:
   * {{{eval("this is a static text")}}} - renderes a static text
   * {{{eval(concat(tag("first"), "-", tag("second")))}}} - displays the concatenated tags "first" and "second"
+{{{""}}}
+  * `eval("this is a static text")` - renderes a static text
+  * `eval(concat(tag("first"), "-", tag("second")))` - displays \\ the concatenated tags "first" and "second"
+`""`
    To delete a previous set text.
 }}}
 …
 }}}
 |-------------------------------------------------------------------------------
+|| {{{text-color}}} || the text color || ''Color'' ||  {{{white}}} for lines and nodes, {{{#c0c0c0}}} for areas (JOSM "{{{text}}}" and "{{{areatext}}}" color preferences) ||
+|| {{{text-opacity}}} || how transparent the text is || ''Opacity'' ||  1.0  ||
+|| {{{text-offset-x}}} || shift the text horizontally, (not supported for text along line) || ''Number'' ||  0  ||
+|| {{{text-offset-y}}} (can also be written as {{{text-offset}}})  || shift the text vertically, positive values shift the text in upwards direction  || ''Number'' ||  0  ||
+|| {{{text-halo-radius}}} || size of text background border (to make text visible on background with a similar color) || ''Number'' ||  -  ||
+|| {{{text-halo-color}}} || color of the text halo || ''Color'' ||  complement of the text color  ||
+|| {{{text-halo-opacity}}} || transparency for the text halo || ''Opacity'' ||  1.0  ||
+|| {{{font-family}}} || font family || ''String'' ||  "Helvetica"[[br]](JOSM preference "mappaint.font")  ||
+|| {{{font-size}}} || font size || ''Number'' ||  8[[br]](JOSM preference "mappaint.fontsize")  ||
+|| {{{font-weight}}} || bold or not || {{{bold}}}, {{{normal}}} ||  {{{normal}}}  ||
+|| {{{font-style}}} || italic or not || {{{italic}}}, {{{normal}}} ||  {{{normal}}}  ||
+|| `text-color` || the text color || ''Color'' ||  `white` for lines and nodes,\\`#c0c0c0` for areas \\(JOSM "`text`" and "`areatext`"\\color preferences) ||
+|| `text-opacity` || how transparent the text is || ''Opacity'' ||  1.0  ||
+|| `text-offset-x` || shift the text horizontally, \\(not supported for text along line) || ''Number'' ||  0  ||
+|| `text-offset-y`\\(can also be written as\\`text-offset`)  || shift the text vertically, positive values shift the text in upwards direction  || ''Number'' ||  0  ||
+|| `text-halo-radius` || size of text background border \\(to make text visible on background \\with a similar color) || ''Number'' ||  -  ||
+|| `text-halo-color` || color of the text halo || ''Color'' ||  complement of the text color  ||
+|| `text-halo-opacity` || transparency for the text halo || ''Opacity'' ||  1.0  ||
+|| `text-anchor-horizontal` || horizontal text label placement || `left`, `center`, `right` ||  `right`  ||
+|| `text-anchor-vertical` || vertical text label placement || `above`, `top`, `center`, `bottom`, `below` ||  `bottom`  ||
+|| `text-rotation` || Rotate the text clockwise or anti clockwise (negative value)\\(since r16253) || `[rad]`, `[rad]rad`, `[deg]°`, `[deg]deg`, `[grad]grad`, `[turn]turn` \\([https://developer.mozilla.org/en/docs/Web/CSS/angle definition]) or a cardinal direction (e.g. `northeast` or `sw`); \\ or `way` to rotate the text in the direction of the parent way. \\See also the functions `degree_to_radians`, `cardinal_to_radians`. \\Since version 18678 function parent_way_angle() is an alternativ to way: e.g. {{{ way > node[...]::layer_x { ... text-rotation: parent_way_angle(); ... } }}} \\(Note that the direction means where the upper edge of the text faces.\\That means with the default direction of north the text flows to east\\(with a left to right language). \\So if you want to flow it to e.g. south you need to set east.) ||  -  ||
+|| `text-position` |||||| see [#AreaStyles Area styles] and [#LineStyles Line styles] ||
+|| `font-family` || font family || ''String'' ||  "Droid Sans" \\(JOSM preference "`mappaint.font`")  ||
+|| `font-size` || font size || ''Number'' ||  8 \\(JOSM preference "`mappaint.fontsize`")  ||
+|| `font-weight` || bold or not || `bold`, `normal` ||  `normal`  ||
+|| `font-style` || italic or not || `italic`, `normal` ||  `normal`  ||
+=== User defined properties ===
+* In [wikitr:/Styles Mappaint styles] you can define any custom property, e.g.: `crc: CRC32_checksum(tag(name))/429496.7296;`
+* In [wikitr:/Rules Validator rules] they must be prefixed by a `-`, e.g.: `-osmoseItemClassLevel: "1210/1/1";`
+=== Property values explanations === #Propertyvaluesexplanations
 '' '''Width''' ''
  - 14.0 (any positive number)
  - {{{default}}} (use JOSM's default line width, which is 2, but can be configured)
  - {{{thinnest}}} (draws the line as thin as possible)
  - +3 (with plus sign in front) adds the amount to the width on the default layer. This applies only for styles that are not on the default layer, e.g. highlights. Another way to write this would be {{{prop("width","default")+3}}}. For {{{casing-width}}}, this refers to the {{{width}}} value on the same layer.
+ - `default` (use JOSM's default line width, which is 2, but can be configured)
+ - `thinnest` (draws the line as thin as possible)
+ - +3 (with plus sign in front) adds the amount to the width on the default layer. This applies only for styles that are not on the default layer, e.g. highlights. Another way to write this would be `prop("width","default")+3`. For `casing-width`, this refers to the `width` value on the same layer.
 '' '''Image''' ''
  See [wiki:Help/Styles/Images].
+ See [wikitr:/Help/Styles/Images].
 '' '''Color''' ''
  * named color as found in [https://www.w3.org/TR/css3-color/#svg-color this] list
+ * html style: '''{{{#RRGGBB}}}''', '''{{{#RGB}}}''', '''{{{#RRGGBBAA}}}'''
+ * '''{{{rgb(/*r*/, /*g*/, /*b*/)}}}''' - rgb value with arguments from 0.0 to 1.0
+ * '''{{{rgba(/*r*/, /*g*/, /*b*/, /*alpha*/)}}}''' - rgb value with alpha
+ * '''{{{hsb_color(/*hue*/, /*saturation*/, /*brightness*/)}}}''' - color from HSB color space
+ * html style: '''`#RRGGBB`''', '''`#RGB`''', '''`#RRGGBBAA`'''
+ * '''`rgb(/*r*/, /*g*/, /*b*/)`''' - rgb value with arguments from 0.0 to 1.0
+ * '''`rgba(/*r*/, /*g*/, /*b*/, /*alpha*/)`''' - rgb value with alpha
+ * '''`hsb_color(/*hue*/, /*saturation*/, /*brightness*/)`''' - color from HSB color space
+ * if the color is prefixed with a name and #, e.g. `color: highway_track#6e541c;` it will appear in the [wikitr:/Help/Preferences/ColorPreference Color Preference] and end users can adjust the color there themself
 '' '''Opacity''' ''
 …
 '' '''String''' ''
  * any character sequence, in quotes, e.g. {{{"images/fill.png"}}}. If the string is an identifier, quotes are optional. (Quote and backslash sign can be escaped.)
+ * any character sequence, in quotes, e.g. `"images/fill.png"`. If the string is an identifier, quotes are optional. (Quote and backslash sign can be escaped.)
 '' '''Number''' ''
 …
  * has a special meaning if you put a "+" sign in front (relative width)
+== Eval expressions ==
+See [/doc/org/openstreetmap/josm/gui/mappaint/mapcss/ExpressionFactory.Functions.html#method_summary Javadoc of Functions] for the up-to-date list of functions supported by JOSM's MapCSS implementation.
+== Eval expressions ==#Evalexpressions
+See [/doc/org/openstreetmap/josm/gui/mappaint/mapcss/Functions.html#method_summary Javadoc of Functions] for the up-to-date list of functions supported by JOSM's MapCSS implementation.
  +, -, *, /::
 …
  ||, &&, !::
   boolean operations
+ <, >, <=, >=, ==::
+ <, >, <=, >=, ==, !=::
   comparison operators
+ asin, atan, atan2, ceil, cos, cosh, exp, floor, log, max, min, random, round, signum, sin, sinh, sqrt, tan, tanh::
   the usual meaning, [https://download.oracle.com/javase/7/docs/api/java/lang/Math.html details]
+ asin, atan, atan2, ceil, cos, cosh, exp, floor, log, max, min, mod (since r17759), random, round, signum, sin, sinh, sqrt, tan, tanh::
+  the usual meaning, [https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Math.html details]
  cond(b, fst, snd)::
  b ? fst : snd::
   if ('''b''') then '''fst''' else '''snd'''
  list(a, b, ...)::
   create list of values, e.g. for the {{{dashes}}} property
+  create list of values, e.g. for the `dashes` property
  get(lst, n)::
+  get the ''n''th element of the list ''lst'' (counting starts at 0) [''since 5699'']
+  get the ''n''th element of the list ''lst'' (counting starts at 0) [''since r5699'']
  split(sep, str)::
+  splits string ''str'' at occurrences of the separator string ''sep'', returns a list [''since 5699'']
+  splits string ''str'' at occurrences of the separator string ''sep'', returns a list [''since r5699'']
  prop(''p_name'')::
   value of the property ''p_name'' of the current layer, e.g. prop({{{"width"}}})
+  value of the property ''p_name'' of the current layer, e.g. prop(`"width"`)
  prop(''p_name'', ''layer_name'')::
   property from the layer ''layer_name''
 …
   get the value of the key ''key_name'' from the object's parent
  parent_tags(''key_name'')::
+  returns all parent's values for the key ''key_name'' as a list ordered by a natural ordering [''since 8775'']
+  returns all parent's values for the key ''key_name'' as a list ordered by a natural ordering [''since r8775'']
  has_tag_key(''key_name'')::
   true, if the object has a tag with the given key
 …
   create color value (arguments from 0.0 to 1.0)
  hsb_color(''h'', ''s'', ''b'')::
+  create color from hue, saturation and brightness (arguments from 0.0 to 1.0) [''since 6899'']
+  create color from hue, saturation and brightness (arguments from 0.0 to 1.0) [''since r6899'']
  red(''clr''), green(''clr''), blue(''clr'')::
   get value of color channels in rgb color model
  alpha(''clr'')::
+  get the alpha value of the given color [''since 6749'']
+  get the alpha value of the given color [''since r6749'']
  length(''str'')::
   length of a string
  count(''lst'')::
+  length of a list, i.e., counts its elements [''since 7162'']
+  length of a list, i.e., counts its elements [''since r7162'']
  length(''lst'')::
+  length of a list [''since 5699''] – deprecated ''since 7162''
+  length of a list ([''since r5699''] – deprecated ''since r7162''
  any(obj1, obj2, ...)::
+  returns the first object which is not null (formerly coalesce, [''since 7164''])
+  returns the first object which is not null (formerly coalesce, [''since r7164''])
  concat(''str1'', ''str2'', ...)::
   assemble the strings to one
  join(''sep'', ''str1'', ''str2'', ...)::
   join strings, whith ''sep'' as separator [''since 6737'']
+  join strings, with ''sep'' as separator [''since r6737'']
  join_list(''sep'', ''list_name'')::
+   joins the elements of the list ''list_name'' to one string separated by the separator ''sep'' [''since 8775'']
+   joins the elements of the list ''list_name'' to one string separated by the separator ''sep'' [''since r8775'']
  upper(''str'')::
+   converts string to upper case [''since 11756'']
+   converts string to upper case [''since r11756'']
  lower(''str'')::
+   converts string to lower case [''since 11756'']
+   converts string to lower case [''since r11756'']
+ title(''str'')::
+   converts string to title case [''since r17613''] (`"i am FINE"` → `"I Am Fine"`)
  trim(''str'')::
+   remove leading and trailing whitespace from string [''since 11756'']
+   remove leading and trailing whitespace from string [''since r11756'']
+ trim_list(''list_name'')::
+   remove leading and trailing whitespace from a list of strings, will remove entries that are empty afterwards [''since r15591'']
  JOSM_search("...")::
   true, if JOSM search applies to the object
  tr(str, arg0, arg1, ...)::
+  translate from English to the current language (only for strings in the JOSM user interface) [''since 6506'']
+  translate from English to the current language (only for strings in the JOSM user interface) [''since r6506'']
  regexp_test(regexp, string)::
+  test if ''string'' matches pattern ''regexp'' [''since 5699'']
+  test if ''string'' matches pattern ''regexp'' [''since r5699'']
  regexp_test(regexp, string, flags)::
+  test if ''string'' matches pattern ''regexp''; flags is a string that may contain "i" (case insensitive), "m" (multiline) and "s" ("dot all") [''since 5699'']
+  test if ''string'' matches pattern ''regexp''; flags is a string that may contain "i" (case insensitive), "m" (multiline) and "s" ("dot all") [''since r5699'']
  regexp_match(regexp, string)::
+  Tries to match ''string'' against pattern ''regexp''. Returns a list of capture groups in case of success. The first element (index 0) is the complete match (i.e. ''string''). Further elements correspond to the bracketed parts of the regular expression. [''since 5701'']
+  Tries to match ''string'' against pattern ''regexp''. Returns a list of capture groups in case of success. The first element (index 0) is the complete match (i.e. ''string''). Further elements correspond to the bracketed parts of the regular expression. [''since r5701'']
  regexp_match(regexp, string, flags)::
+  Tries to match ''string'' against pattern ''regexp''. Returns a list of capture groups in case of success. The first element (index 0) is the complete match (i.e. ''string''). Further elements correspond to the bracketed parts of the regular expression. Flags is a string that may contain "i" (case insensitive), "m" (multiline) and "s" ("dot all") [''since 5701'']
+  Tries to match ''string'' against pattern ''regexp''. Returns a list of capture groups in case of success. The first element (index 0) is the complete match (i.e. ''string''). Further elements correspond to the bracketed parts of the regular expression. Flags is a string that may contain "i" (case insensitive), "m" (multiline) and "s" ("dot all") [''since r5701'']
  substring(str, idx)::
+  return the substring of ''str'', starting at index ''idx'' (0-indexed) [''since 6534'']
+  return the substring of ''str'', starting at index ''idx'' (0-indexed) [''since r6534'']
  substring(str, start, end)::
   return the substring of ''str'', starting at index ''start'' (inclusive) up to ''end'' (exclusive) (0-indexed) [''since 6534'']
+  return the substring of ''str'', starting at index ''start'' (inclusive) up to ''end'' (exclusive) (0-indexed) [''since r6534''], a negative end index counts from the string end [''since r19259'']
  replace(string, old, new)::
    Replaces any occurrence of the substring ''old'' within the string ''string'' with the text ''new''
  osm_id()::
+  returns the OSM id of the current object [''since 5699'']
+  returns the OSM id of the current object [''since r5699'']
+ osm_user_name()::
+  returns the OSM user name who last touched the current object [''since r15246'']
+ osm_user_id()::
+  returns the OSM user id who last touched the current object [''since r15246'']
+ osm_version()::
+  returns the OSM version number of the current object [''since r15246'']
+ osm_changeset_id()::
+  returns the id of the changeset the current object was last uploaded to [''since r15246'']
+ osm_timestamp()::
+  returns the time of last modification to the current object, as timestamp [''since r15246'']
+ parent_osm_id()::
+  returns the OSM id of the object's parent (matched by child selector) [''since r13094'']
  URL_encode(str)::
+  [https://en.wikipedia.org/wiki/Percent-encoding percent-encode] a string. May be useful for data URLs [''since 6805'']
+  [https://en.wikipedia.org/wiki/Percent-encoding percent-encode] a string. May be useful for data URLs [''since r6805'']
  URL_decode(str)::
+  [https://en.wikipedia.org/wiki/Percent-encoding percent-decode] a string. [''since 11756'']
+  [https://en.wikipedia.org/wiki/Percent-encoding percent-decode] a string. [''since r11756'']
  XML_encode(str)::
   escape special characters in xml. E.g. {{{<}}} becomes {{{&lt;}}}, other special characters: {{{>}}}, {{{"}}}, {{{'}}}, {{{&}}}, {{{\n}}}, {{{\t}}} and {{{\r}}} [''since 6809'']
+  escape special characters in xml. E.g. `<` becomes `&lt;`, other special characters: `>`, `"`, `'`, `&`, `\n`, `\t` and `\r` [''since r6809'']
  CRC32_checksum(''str'')::
+  calculate the CRC32 checksum of a string (result is an integer from 0 to 2^32^-1) [''since 6908'']
+ is_right_hand_traffic() [''since 7193'']::
+  Check if there is left-hand or right-hand traffic at the current location.
+ number_of_tags() [''since 7237'']::
+  returns the number of tags for the current OSM object
+ print(o) [''since 7237'']::
+  prints a string representation of `o` to the command line (for debugging)
+ println(o) [''since 7237'']::
+  prints a string representation of `o` to the command line, followed by a new line (for debugging)
+ JOSM_pref(''key'', ''default'') [''since 7238, with restrictions since 3856'']::
+  Get value from the JOSM advanced preferences. This way you can offer certain options to the user and make the style customizable. It works with strings, numbers, colors and boolean values. [[br]][This function exists since version 3856, but with some restrictions. `JOSM_pref` always returns a string, but in version 7237 and earlier, the automatic conversion of string to boolean and color was not working. You can use the following workarounds for boolean values and color in version 7237 and earlier: `cond(JOSM_pref("myprefkey", "true")="true", "X", "O")` and `html2color(JOSM_pref("mycolor", "#FF345611"))`. These explicit conversions should be no longer necessary in version 7238 and later. Automatic conversion to a number works in any version.]
+ setting() [''since 7450'']::
+  to use a [[Help/Styles/MapCSSImplementation#Stylesettings|style setting]]
+ degree_to_radians() [''since 8260'']::
+  returns a in degree given direction in radians
+ cardinal_to_radians() [''since 8260'']::
+  returns a cardinal direction in radians
+ waylength() [''since 8253'']::
+  returns the length of the way in metres
+ areasize() [''since 8253'']::
+  returns the area of a closed way in square meters
+  calculate the CRC32 checksum of a string (result is an integer from 0 to 2^32^-1) [''since r6908'']
+ siunit_length(''str'')::
+   convert length units to meter (fault tolerant, ignoring white space) [''since r19089'']
+ is_right_hand_traffic()::
+  Check if there is left-hand or right-hand traffic at the current location. [''since r7193'']
+ number_of_tags()::
+  returns the number of tags for the current OSM object [''since r7237'']
+ print(o)::
+  prints a string representation of `o` to the command line (for debugging) [''since r7237'']
+ println(o)::
+  prints a string representation of `o` to the command line, followed by a new line (for debugging) [''since r7237'']
+ JOSM_pref(''key'', ''default'')::
+  Get value from the JOSM advanced preferences. This way you can offer certain options to the user and make the style customizable. It works with strings, numbers, colors and boolean values. \\[This function exists since version r3856, but with some restrictions. `JOSM_pref` always returns a string, but in version r7237 and earlier, the automatic conversion of string to boolean and color was not working. You can use the following workarounds for boolean values and color in version r7237 and earlier: `cond(JOSM_pref("myprefkey", "true")="true", "X", "O")` and `html2color(JOSM_pref("mycolor", "#FF345611"))`. These explicit conversions should be no longer necessary in version r7238 and later. Automatic conversion to a number works in any version. Furthermore, in version r16590, can be used to set color properties. So `* { set_color: JOSM_pref("pref", #000000); }` will create a color property now.]
+ setting()::
+  to use a [wikitr:/Help/Styles/MapCSSImplementation#Stylesettings style setting] [''since r7450'']
+ degree_to_radians()::
+  returns a in degree given direction in radians [''since r8260'']
+ cardinal_to_radians()::
+  returns a cardinal direction in radians [''since r8260'']
+ waylength()::
+  returns the length of the way in metres [''since r8253'']
+ areasize()::
+  returns the area of a closed way in square meters [''since r8253'']
+ at(lat,lon)::
+  returns true if the object centroid lies at given ''lat''/''lon'' coordinates, e.g. to check for nodes at "null island" `node[at(0.0,0.0)]` [''since r12514'']
+ is_similar(''str1'', ''str2'')::
+  returns true if the two strings are similar, but not identical, i.e., have a Levenshtein distance of 1 or 2. Example: `way[highway][name][is_similar(tag(name), "Main Street")]` checks for streets with a possible typo in the name (e.g. Main Streeg). [''since r14371'']
+ gpx_distance()::
+  returns the lowest distance between the OSM object and a GPX point [''since r14802'']
+ count_roles()::
+  returns the number of primitives in a relation with the specified roles [''since r15275'']
+ sort(''str1'', ''str2'', ''str3'', ''...'')::
+  sorts an array of strings [''since r15279'']
+ sort_list(''list_name'')::
+  sorts a list of strings [''since r15279'']
+ tag_regex(''regex'')::
+  returns a list containing the values of keys that match the regex [''since r15317'']
+ to_boolean(''str'')::
+  returns the string argument as a boolean [''since r16110'']
+ to_byte(''str'')::
+  returns the string argument as a byte [''since r16110'']
+ to_short(''str'')::
+  returns the string argument as a short [''since r16110'']
+ to_int(''str'')::
+  returns the string argument as a int [''since r16110'']
+ to_long(''str'')::
+  returns the string argument as a long [''since r16110'']
+ to_float(''str'')::
+  returns the string argument as a float [''since r16110'']
+ to_double(''str'')::
+  returns the string argument as a double [''since r16110'']
+ uniq(''str1'', ''str2'', ''str3'', ''...'')::
+  returns a list of strings that only have unique values from an array of strings [''since r15323'']
+ uniq_list(''list_name'')::
+  returns a list of strings that only have unique values from a list of strings [''since r15323'']
+ parent_way_angle()::
+  returns the angle of the parent way as a double in rad [''since r18664''] (see: text-rotation or icon-rotation)
+ convert_primitive_to_string(''PrimitiveId'')::
+  returns the primitive id as a string [''since r18829'']
+ convert_primitives_to_string(''PrimitiveId'', ''PrimitiveId'', ''...'')::
+  returns a list of primitive ids converted to strings [''since r18829'']
+ parent_osm_primitives(''optional key'', ''optional value'')::
+  returns a list of primitive ids which match the key and value (if present) [''since r18829'']
 === Examples ===
 * circle symbol for house number with size depending of the number of digits
 {{{
 …
 }}}
+* casing on inside of area
+{{{
+#!mapcss
+area[building]:clockwise {
+    right-casing-width: 10;
+}
+area[building]:anticlockwise {
+    left-casing-width: 10;
+}
+/* or */
+area[building][is_clockwise()] {
+    right-casing-width: 10;
+}
+area[building][is_anticlockwise()] {
+    left-casing-width: 10;
+}
+}}}
+* case insensitive selector. This matches: `Name=Main Street`, but also `naMe=MAIN STREET`
+{{{
+#!mapcss
+way[/(?i)^name$/ =~ /(?i)^Main Street$/] {
+}
+}}}
 == Compatibility notes ==
 === MapCSS 0.2 ===
 ==== Grammar ====
+ * {{{way[oneway=yes]}}} does not have any magic, you can use {{{way[oneway?]}}} instead
+ * no {{{@import}}}
+ * JOSM does not require {{{eval(...)}}} to be wrapped around expressions, but for compatibility with other MapCSS implementations you should write it out.
+ * `way[oneway=yes]` does not have any magic, you can use `way[oneway?]` instead
+ * no `@import`
+ * JOSM does not require `eval(...)` to be wrapped around expressions, but for compatibility with other MapCSS implementations you should write it out.
 ==== Properties ====
 At the moment, JOSM does ''not'' support the following properties:
  line: ::
   {{{image}}}
+  `image`
  label: ::
   {{{font-variant, text-decoration, text-transform, max-width}}}
+  `font-variant, text-decoration, text-transform, max-width`
  shield: ::
   not supported
 === Halcyon (Potlatch 2) ===
  * Text label is placed in the center of the icon. For compatibility with Halcyon put
 {{{
 …
  at the beginning of your style sheet.
  * standard z-index in Halcyon is 5, but it is 0 in JOSM
  * '''{{{image: circle;}}}''' corresponds to '''{{{symbol-shape: circle;}}}'''
+ * '''`image: circle;`''' corresponds to '''`symbol-shape: circle;`'''
 === Kothic ===
  * Kothic has support for eval, which probably differs from JOSM's eval.
  * Kothic understands units, whereas JOSM always calculates in pixel.
+ * The extrusion features are not available in JOSM
+ * The extrusion features are not available in JOSM.
 === Ceyx ===
+ * seems to have {{{[tunnel=1]}}} instead of {{{[tunnel=yes]}}} (Halcyon) or {{{[tunnel?]}}} (JOSM)
 == Media queries [''since 6970'']  (deprecated) ==
+ * seems to have `[tunnel=1]` instead of `[tunnel=yes]` (Halcyon) or `[tunnel?]` (JOSM)
+== Media queries (deprecated) ==
 {{{#!td style="background-color: #faa"
 Note: media queries are deprecated. You should use @supports rules instead (see above).
 }}}
+Media queries are used to skip a section of the style under certain conditions. Typically you want to use a feature which is introduced in a newer version of JOSM, but like to have a fall back style for users of older JOSM clients. Example:
+Media queries are used to skip a section of the style under certain conditions. Typically you want to use a feature which is introduced in a newer version of JOSM, but like to have a fall back style for users of older JOSM clients. This feature came with r6970. Example:
 {{{
 #!mapcss
 …
 }}}
 {{{#!td
 Only include {{{@media}}} section when the current version of JOSM is greater than or equal to the specified number.
+Only include `@media` section when the current version of JOSM is greater than or equal to the specified number.
 }}}
 |-
 …
 }}}
 {{{#!td
 Only include {{{@media}}} section when the current version of JOSM is lower than or equal to the specified number.
+Only include `@media` section when the current version of JOSM is lower than or equal to the specified number.
 }}}
 |-
 …
 }}}
 {{{#!td
 Only include {{{@media}}} section when the name of the editor / renderer matches the given string. In JOSM, the only accepted value is {{{josm}}}.
+}}}
 Conditions can be combined with {{{and}}}:
+Only include `@media` section when the name of the editor / renderer matches the given string. In JOSM, the only accepted value is `josm`.
+}}}
+Conditions can be combined with `and`:
 {{{
 …
 {{{#!comment
 There is also the {{{not}}} keyword (see the linked css doc for details).
+There is also the `not` keyword (see the linked css doc for details).
 This is implemented, but probably not very useful. Feel free to add documentation.
 }}}