Changes between Version 557 and Version 558 of Maps

Timestamp:

2018-12-02T20:36:15+01:00 (7 years ago)

Author:

Klumbumbus

Comment:

reorder

Maps

@@ -11 +11 @@
 ||= '''Property''' =||= '''Description''' =||
 || '''name''' || The name of the imagery source. Use English here only. These names can then be translated into all supported languages via [https://translations.launchpad.net/josm/trunk/+pots/josm Launchpad]. (Optional attribute: {{{lang}}} containing the language code to give a translated name here in the xml file. However this should be avoided. This also overrides the translation from Launchpad.) ||
+|| '''id''' || Unique identifier of a map to allow automatic updates of map data in JOSM. Don't use white spaces and special characters here (except `-` and `_`). Never change an existing id as this would break the idea behind the id. ||
+|| '''oldid''' || In case renaming is necessary this can contain an old id. The attribute {{{date}}} containing an ISO data like {{{2018-08-14}}} is required. Multiple entries are possible. ||
+|| '''category''' || Type of imagery: {{{photo}}} aerial or satellite photo, {{{map}}} a map, {{{historicmap}}} historic or otherwise outdated map, {{{osmbasedmap}}} map based on OSM data, {{{historicphoto}}} historic or otherwise outdated aerial or satellite photo, {{{other}}} any other type or WMTS/wms_endpoint sources containing layers of different categories.[[BR]]Some notes: the historic variant of photo and map should be used either if the source shows very old data or if there is a newer variant of the same source from the same provider available. E.g. for the entries london_orthophoto_2016, london_orthophoto_2017 and london_orthophoto_2018 use {{{photo}}} for the 2018 variant and {{{historicphoto}}} for the other two. If a source is specialized on one feature e.g. shows only landuses or only roads or only buildings use {{{other}}} rather than {{{map}}}. ||
 || '''description''' || Description of the imagery source, when not self explaining - i.e. when not aerial imagery or other relevant specific information, required attribute: {{{lang}}} containing the language code. The first description must be in English with the language code {{{en}}} for translation in Launchpad. The description is displayed in JOSM in the mouse over tool tip in the imagery preferences, the Imagery menu and in the toolbar. ||
 || '''type''' || The type. Can be {{{tms}}}, {{{wmts}}}, {{{wms}}} and {{{wms_endpoint}}}. If {{{wms_endpoint}}} is used then the user can choose one of the provided wms layers when adding the entry as background. In addition, there are the special types {{{bing}}} and {{{scanex}}} with hardcoded behaviour. ||
 || '''url''' || The URL of the service. Can contain templates, e.g.{{{ {zoom} }}} will be replaced by the current zoom level (see below). The list of services is a XML document, so if the URL contains a `&` character, the URL must be wrapped in `<![CDATA[...]]>`. Alternatively the `&` character is replaced by `&amp;` (not recommended). ||
-|| '''id''' || Unique identifier of a map to allow automatic updates of map data in JOSM. Don't use white spaces and special characters here (except `-` and `_`). Never change an existing id as this would break the idea behind the id. ||
-|| '''oldid''' || In case renaming is necessary this can contain an old id. The attribute {{{date}}} containing an ISO data like {{{2018-08-14}}} is required. Multiple entries are possible. ||
 || '''default''' || If set to "true", the entry is in the [Help/Menu/Imagery users list] by default. (Only josm wiki administrators can change default entries.) ||
 || '''date''' || Creation date of imagery in form YYYY-MM-DD;YYYY-MM-DD. DD and MM as well as a second date are optional. a single "-" marks an unknown or open timespan. Examples **2015** or **2015;2016** or **2015-10;2016-01** or **-;2015** or **2015;-**. The date is displayed in JOSM in the mouse over tool tip in the imagery preferences, the Imagery menu and in the toolbar. ||
@@ -36 +37 @@
 || '''metadata-header''' || {{{header-name}}} attribute specifies a header returned by tile server, that will be shown as {{{metadata-key}}} attribute in Show Tile Info dialog ||
 || '''valid-georeference''' || Set to {{{true}}} if imagery source is properly aligned and does not need imagery offset adjustments. This is used for OSM based sources too. ||
-|| '''category''' || Type of imagery: {{{photo}}} aerial or satellite photo, {{{map}}} a map, {{{historicmap}}} historic or otherwise outdated map, {{{osmbasedmap}}} map based on OSM data, {{{historicphoto}}} historic or otherwise outdated aerial or satellite photo, {{{other}}} any other type or WMTS/wms_endpoint sources containing layers of different categories.[[BR]]Some notes: the historic variant of photo and map should be used either if the source shows very old data or if there is a newer variant of the same source from the same provider available. E.g. for the entries london_orthophoto_2016, london_orthophoto_2017 and london_orthophoto_2018 use {{{photo}}} for the 2018 variant and {{{historicphoto}}} for the other two. If a source is specialized on one feature e.g. shows only landuses or only roads or only buildings use {{{other}}} rather than {{{map}}}. ||
 ||= '''Attribute''' =||= '''Description''' =||
 || '''last-check''' || Date of last check of the data to be valid and accessible, in the form YYYY-MM-DD  ||
@@ -110 +110 @@
 === Other important information ===
 
- * Please use the preferred order of properties for better readability: {{{name}}}, {{{id}}}, {{{category}}}, then everything else, and at the end {{{icon}}}, {{{bounds}}}. (The last two are usually the longest.)
+ * Please use the preferred order of properties for better readability: {{{name}}}, {{{id}}}, {{{old-id}}} (if present), {{{category}}}, then everything else, and at the end {{{icon}}}, {{{bounds}}}. (The last two are usually the longest.)
  * JOSM uses [/maps this] URL to fetch the imagery sources. The URL can be customized in the advanced preferences (key {{{imagery.layers.sites}}}). Using multiple sources at the same time is possible.
  * Normally JOSM ignores any elements that it does not recognize. However, it will skip the entire imagery entry, when one of the unsupported tags has the attribute {{{mandatory='true'}}}. This is only relevant, when essential new features are added, but old versions of JOSM are still in use.