Changes between Version 2 and Version 3 of NameTemplate


Ignore:
Timestamp:
2011-10-17T19:49:27+02:00 (14 years ago)
Author:
Polyglot
Comment:

Tried to make explanation clearer and more complete

Legend:

Unmodified
Added
Removed
Modified
  • NameTemplate

    v2 v3  
    11Name templates can be used to define custom formatting for gpx waypoints or osm primitives (for example in the Relations or the Selection lists).
     2
     3= Where to define =
     4
     5Create a text file as described below. Then refer to it from Tagging Presets (F12, Map Settings (3rd item), 3rd tab)
     6
     7= Configuration file =
     8The configuration file can look like this:
     9
     10<?xml version="1.0" encoding="UTF-8"?>[[BR]]
     11<presets>[[BR]]
     12        <item name="Public transportation" type="relation"[[BR]]
     13                name_template="Bus({operator} {ref} ?{'{from} - {via} - {to}' | '{from} - {to}' | '{from}' | '{to}'})"[[BR]]
     14                name_template_filter="type=route route=bus">[[BR]]
     15        </item>[[BR]]
     16</presets>[[BR]]
    217
    318= Syntax =
     
    1429
    1530= Available values =
    16 For formatting of OSM primitives , the value of any tag can be used, use {special:everything} to see what values are available for your gpx waypoints.
     31For formatting of OSM primitives , the value of any tag can be used. You can use {special:everything} to see what values are available for your gpx waypoints.
     32
    1733Some additional variables are available  via the special prefix:
    1834- {special:everything} prints all available values, available for formatting of both primitives and waypoints.