Hi I had suspicions that the line: amenity=restaurant & cuisine ~ '.*pizza.*' [0x2a0a resolution 24] doesn't work, but never bother looking in detail. It would fall through to: amenity=restaurant & cuisine=* [0x2a13 resolution 24] There is a slight reason to use a subtype when cuisine is specified and not matched and no subtype (0x2a00) when no cuisine specified, in that you can find these unknown cuisines by select-category:other An improvement to the default style would be to change above to: amenity=restaurant & cuisine=* {add name='${cuisine|subst:"_=> "}'} [0x2a13 resolution 24] and there are a few other places that would benefit from similar changes Ticker On Thu, 2017-04-27 at 11:18 +0000, Gerd Petermann wrote:
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=restaurant, 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=restaurant & cuisine=* [0x2a13 resolution 24] amenity=restaurant [0x2a00 resolution 24] Why do we use two different types for these "mop up" rules?
Gerd
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev