Changes between Version 440 and Version 441 of Maps


Ignore:
Timestamp:
2017-02-22T22:29:53+01:00 (7 years ago)
Author:
Klumbumbus
Comment:

+hint to use english names, see #12179, other small adjustments

Legend:

Unmodified
Added
Removed
Modified
  • Maps

    v440 v441  
    589589General properties of {{{<entry>}}}: ({{{<name>}}}, {{{<type>}}}, {{{<url>}}} and {{{<id>}}} are mandatory.)
    590590||= '''Property''' =||= '''Description''' =||
    591 || '''name''' || The name of the imagery source, optional attribute: {{{lang}}} containing the language code ||
     591|| '''name''' || The name of the imagery source. Use english here only. These names can then be translated into all supported languages via 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.) ||
    592592|| '''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 description is displayed in JOSM in the mouse over tool tip in the imagery preferences. ||
    593593|| '''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. ||
     
    672672|| '''code''' || A projection name, part of its parent {{{<projections>}}}, e.g {{{<code>EPSG:4326</code>}}} ||
    673673
    674 For WMTS you specify the url to getCapabilities document. JOSM will fetch the document and interpret all the data there. If there is more than one layer within one service, JOSM will ask the user, which tile he wants to work with. Multiple styles are not yet supported.
     674For WMTS you specify the url to the GetCapabilities document. JOSM will fetch the document and interpret all the data there. If there is more than one layer within one service, JOSM will ask the user, which tile he wants to work with. Multiple styles are not yet supported.
    675675 * When {header(''header'',''value'')} is included in URL, this part is stripped and send as HTTP header to the server
    676676
    677677=== Other information ===
    678678
    679  * Use bounds as last property of an entry.
     679 * Use bounds as last property of an entry for better overview, as the bounds block is usually the longest.
    680680 * 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.
    681681 * 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.