[mkgmap-dev] amenity=restaurant and search index

Fri Apr 28 08:29:14 BST 2017

Hi all,

think I fixed the bug with r3919 in the branch. I am now looking for an option to say which POI should NOT be indexed.
Will repopen this thread later:
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2017q1/025945.html

Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <GPetermann_muenchen at hotmail.com>
Gesendet: Donnerstag, 27. April 2017 20:14:18
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] amenity=restaurant and search index

Hi Bernhard,

yes, that is understood. My problem seems to be caused  by the fact that the index is wrong so that 0x2a00 does
not appear where it should. This is my guess because when I create a gmapsupp in MapSource and analyse the
index I see that it doesn't contain the entry for 0x2a00.
I think the problem is that we don't fully understand some bytes in the index.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Bernhard Hiller <bhil at gmx.de>
Gesendet: Donnerstag, 27. April 2017 19:41:44
An: mkgmap-dev at lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] amenity=restaurant and search index

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
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev