The index may be sometimes confusing: there are categories which sum up
other categories, and that also depends on the device type.
See http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/POI_Types
E.g. 0x2a04 is shown under
- All Categories
- Asian
- Chinese
on an Oregon 600, but the category "Asian" is missing on some other devices.
According to that site, "International" shows 0x2a06 only on most Garmin
devices, but additionally 0x2a13-0x2a1f on Oregon 600.
The categories are hard-coded by Garmin (well, you can edit the language
file and change their meaning), so they will show up on your device even
if there is no POI available for that category.
Am 27.04.2017 um 13:18 schrieb Gerd Petermann:
Hi all,
I've postponed the problems regarding --lower-case and looked at other problems
in the index.
I've noticed that some restaurants do not show up where expected.
I am not sure if this is caused by wrong data in the index or simply by style
rules, probably both.
For example:
I have a small test file containing some amenity=staurant, but none has
cuisine=international (0x2a06) , still
the search menu shows an entry for that category but finds no entry.
On the other hand, many restaurants are found where not expected, for example
in category pizza I find all 0x2a00
The default style contains rules to add POI with type 0x2a and it seems to
work for many of them,
but at least these last two rules look suspicious:
amenity=staurant & cuisine=* [0x2a13 resolution 24]
amenity=staurant [0x2a00 resolution 24]
Why do we use two different types for these "mop up" rules?
Gerd
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
