I have re-read your posts and I think I am still confused about your statement "you can also club together POIs with different Icons to the same POI-List entry" Again, what is a 'POI-list entry' and how is this a benefit? I understand about specific store BRANDS and using unique POINTS and then use a GENERIC icon for the rest of the category. Greg On Sat, Mar 5, 2016 at 4:49 AM, Walter Schlögl <Walter.Schloegl-Resch@aon.at
wrote:
Hi Greg,
here an example for supermarkets
shop=supermarket & (name~'Hofer.*' | name~'HOFER.*') { set mkgmap_symbol=yes} [0x3501 resolution 23 continue with_actions] shop=supermarket & (name~'Aldi.*' | name~'ALDI.*') { set mkgmap_symbol=yes} [0x3501 resolution 23 continue with_actions] shop=supermarket & (name~'Lidl.*' | name~'LIDL.*') { set mkgmap_symbol=yes} [0x3502 resolution 23 continue with_actions] ... shop=supermarket & mkgmap_symbol!=yes [0x3500 resolution 23 continue with_actions] shop=supermarket [0x2E02 resolution 21] # POI
There is one common symbol on 3500 and dedicated symbols on 3501 and above. (Hofer and Aldi is the same supermarket with the same Logo but with different names in Austria and Germany) If I find a dedicated name of the supermarket, I will show the corresponding symbol. (at the moment about 30 in my list) All other supermarkets will get the common symbol. And all of them will get additionally an unvisible POI (well, not totally unvisible but just 1 dot) for the POI-List Since this 1 dot POI is placed at resolution 21, I can click on it also in lower zoom levels.
I’m doing the same with amenity=fuel (more than 20), shop=car and many others. My map has many dedicated symbols which makes it easier to find a POI at one short look even without using the search function.
Walter
*From:* greg crago <gregcrago@gmail.com> *Sent:* Friday, March 04, 2016 11:37 PM *To:* Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk> *Subject:* Re: [mkgmap-dev] Question about using different ROAD CLASS's andROAD SPEED's for one linetype.
I am still confused. Can you explain it one more time and use an example.
Greg
On Fri, Mar 4, 2016 at 11:13 AM, Bernd Weigelt <weigelt.bernd@web.de> wrote:
Hi Greg
No, this line catches only cuisine=french *or* cuisine=sea food, not 'cuisine=french;sea food;...' This key/value pair will be ignored
--- cuisine~'.*;.*' { set cuisine='${cuisine|part:}'; }
This rule helps, to use the first part in the POIs, but all other will be ignored, too. Have it in my filter file.
My example in my first answer is not really good, because the rule has to be executed in a loop until the last value, but i think MKGMAP didn't do this
Bernd
Am Freitag, 4. März 2016, 10:01:52 CET schrieb greg crago:
Bernd, Is this the same as (in the line file)
amenity=restaurant & (cuisine=french | cuisine=sea food | cuisine=german | cuisine=..... ) [0x01150 resolution 24]
Greg
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
------------------------------ _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev