Hi WanMil,
Thank you for your debug information.
If the log file says that
N 617233095 ;;;;;;Bezirk Innsbruck-Stadt;;Tirol;;AUT;;
W 45987333 ;;;;;;Bezirk Innsbruck-Stadt;;Tirol;;AUT;;
was assigned to that POI, then from my point of view mkgmap does what it
is told to do. It looks like that mkgmap does not find any city name for
the correcpsonding mkgmap:city tag since no administrative boundary is
present in OSM data. Therefore it leaves the address field for the city
name empty. The reason for displaying another city name instead of no
one might be found in the address index format or in Garmin software
respectively.
However, the solution in my case will be to extend the style file by
additional rules assigning any other name to the mkgmap:city tag if the
desired one cannot be resolved. For example by obtaining the name of the
administrative boundary with the next lower admin_level helps to
overcome the 'random' city name effect in this case.
mkgmap:country=AUT & mkgmap:city!=* & mkgmap:admin_level8=* { set
mkgmap:city='${mkgmap:admin_level8}' }
mkgmap:country=AUT & mkgmap:city!=* & mkgmap:admin_level6=* { set
mkgmap:city='${mkgmap:admin_level6}' }
The the rules in the mkgmap default style only redirects mkgmap to
search for the next boundary with higher admin_level. But due to the
fact that there is no boundary in the OSM data fitting to the rules, the
observed effect occurs.
Bernhard
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
