Hi, attached is a patch that implements the proposed completion of the destination tag. It can be enabled with the --enable-destination-completion The code logs which ways are additionally tagged with destionation and which are skipped: uk.me.parabola.mkgmap.reader.osm.LinkDestinationHook.level=INFO Please give it a try. Maybe someone find some additional useful rules how to complete the destination tag. At the moment only a "forward" completion is performed, i.e. for all *_link ways the destination tag is copied to all connected ways in driving direction. This is not done if the connected way has itself multiple connections. WanMil
Hi, I added following lines to my style file in order to display the "destination"-Tag on motorway-junctions:
----------
# Set the routing direction (highway=motorway|highway=motorway_link) & destination=* { add display_name = '${ref} (${destination})' } (highway=trunk|highway=trunk_link) & destination=* { add display_name = '${ref} (${destination})' }
# Set highway names to include the reference if there is one
----------
This works well (see pictures [2] and [3]), but:
When using the Garmin Types 0x08 and 0x09 (Ramp), Garmin is evaluating the first way behind all the _link ways.
This is not what is stated in the wiki [1]. In most cases, only the _link ways are tagged.
So the idea is a new mkgmap option --process-destination which does following pre-processing:
For all _link ways which have a destination-Tag copy the tag to the following non-link way (motorway or trunk).
Chris
[1] http://wiki.openstreetmap.org/wiki/Key:destination [2] http://up.picr.de/11670098jg.png [3] http://up.picr.de/11670102jj.png