Changes between Version 567 and Version 568 of Maps


Ignore:
Timestamp:
2020-01-11T20:40:44+01:00 (3 months ago)
Author:
Klumbumbus
Comment:

see #18172 - update categories

Legend:

Unmodified
Added
Removed
Modified
  • Maps

    v567 v568  
    1313|| '''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. ||
    1414|| '''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. ||
    15 || '''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 (e.g. hill shading, OSM validation overlays, ...) 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 or two features e.g. shows only landuses or only roads and rivers or only buildings use {{{other}}} rather than {{{map}}}. ||
     15|| '''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, {{{elevation}}} a map of digital terrain model, digital surface model or contour lines, {{{qa}}} map for quality assurance, {{{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_2018, london_orthophoto_2019 and london_orthophoto_2020 use {{{photo}}} for the 2020 variant and {{{historicphoto}}} for the other two. If a source is specialized on one or two features e.g. shows only landuses or only roads and rivers or only buildings use {{{other}}} rather than {{{map}}}. ||
    1616|| '''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. ||
    1717|| '''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. ||