Mkgmap/help/Tags

From OpenStreetMap Wiki
Jump to: navigation, search

Tags in use for routing and address search

tag affects initial value possible values 4) note
mkgmap:country address search 1) 3-letter country code, derived from mkgmap:admin_level2 (hard-wired in LocatorConfig.xml). If an object's country code is not defined e.g. in oceans, the values of --country-abbr and --country-name are used, see here (any text) List of values
mkgmap:region given by command line parameter --region-name and --region-abbr, or (none) if these are not used
mkgmap:city (none) - must be set by rule in style 2)


mkgmap:housenumber address search - advanced 1) (none) - must be set by rule in style, e. g. created from the addr:* tags numeric value
mkgmap:street (any text)
mkgmap:postal_code
mkgmap:phone


mkgmap:admin_level2 (nothing) name of the boundary=administrative polygon where the object is located in - depends on option --location-autofill 3) (any text)
...
mkgmap:admin_level11
mkgmap:unpaved routing - avoid options "no" "yes", "no"
toll routing - avoid options "no", if not set explicitly "yes", "no" see Key:toll
access routing - general "yes", if not set explicitly "yes", "no", "destination", ... (?) see Key:access
oneway routing - general "no", if not set explicitly "yes", "no", "-1" see Key:oneway

1) If a node or way should be searchable on the Garmin device, it must contain the three tags mkgmap:country, mkgmap:region, and mkgmap:city (???)

2) These tags are not initialized to a value by default. The corresponding values must be set by the style rules, evaluating the values of admin_level2...admin_level11. Example: Creating a rule in the lines file

mkgmap:country!=* & mkgmap:admin_level2=* { set mkgmap:country='${mkgmap:admin_level2}' }

sets the value of mkgmap:country to the name of the surrounding admin_level2 boundary (which is normally the country), if the tag is not already set

3) The values of the admin_level2 ... admin_level11 tags are initialized by the position of the object. The location information can origin from either boundaries, is_in tags, or from nearest place=* points. The behavior is controlled by the option --location-autofill. See Mkgmap/help/options#Address search options. Note that not all levels are present, depending on the local administration system. Please note that the tags are set according to the position in the data of the boundary files, not within the polygons in the .osm file. It is possible to create the boundaries with mkgmap (option --createboundsfile=...)

4) Although other values are possible and meaningful in OSM data, only these are evaluated by mkgmap and the Garmin device

Discussion in the German forum

Personal tools
Namespaces
Variants
Actions
site
Toolbox