Changes between Version 587 and Version 588 of Maps


Ignore:
Timestamp:
2021-08-04T22:00:08+02:00 (3 years ago)
Author:
Klumbumbus
Comment:

+typr mvt, see #17177

Legend:

Unmodified
Added
Removed
Modified
  • Maps

    v587 v588  
    1616Some 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}}}. ||
    1717|| '''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. ||
    18 || '''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. ||
     18|| '''type''' || The type. Can be {{{tms}}}, {{{wmts}}}, {{{wms}}}, {{{wms_endpoint}}} and {{{mvt}}}. 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. ||
    1919|| '''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[...]]>`. (Technically alternatively the `&` character could be replaced by `&amp;` but that makes comparing urls harder and is therefore strongly discouraged.) ||
    2020|| '''custom-http-headers''' || HTTP headers to be sent to server (replacement of {header(''header'', ''value'')}). It has two attributes {{{header-name}}} and {{{header-value}}}. Might be specified multiple times. ||