[mkgmap-dev] Question about using different ROAD CLASS's andROAD SPEED's for one linetype.

Sun Mar 6 15:12:10 GMT 2016

If I have a list of custom FUEL icons in my line file:

amenity=fuel & (name ~ '.*[Bb][Pp].*' | brand ~ '.*[Bb][Pp].*')        {set
mkgmap:label:1=' '} [0x6018 resolution 24]
amenity=fuel & (name ~ '.*[Cc]itgo.*' | brand ~ '.*[Cc]itgo.*')        {set
mkgmap:label:1=' '} [0x600b resolution 24]
amenity=fuel & (name ~ '.*[Ee]xxon.*' | brand ~ '.*[Ee]xxon.*')        {set
mkgmap:label:1=' '} [0x600a resolution 24]
amenity=fuel & (name ~ '.*[Kk]roger.*' | brand ~ '.*[Kk]roger.*')      {set
mkgmap:label:1=' '} [0x6003 resolution 24]
amenity=fuel & (name ~ '.*[Mm]arathon.*' | brand ~ '.*[Mm]arathon.*')  {set
mkgmap:label:1=' '} [0x6009 resolution 24]
amenity=fuel & (name ~ '.*[Mm]obil.*' | brand ~ '.*[Mm]obil.*')        {set
mkgmap:label:1=' '} [0x6001 resolution 24]
amenity=fuel & (name ~ '.*[Ss]hell.*' | brand ~ '.*[Ss]hell.*')        {set
mkgmap:label:1=' '} [0x6000 resolution 24]
amenity=fuel & (name ~ '.*[Ss]peedway.*' | brand ~ '.*[Ss]peedway.*')  {set
mkgmap:label:1=' '} [0x6002 resolution 24]
amenity=fuel & (name ~ '.*[Ss]unoco.*' | brand ~ '.*[Ss]unoco.*')      {set
mkgmap:label:1=' '} [0x600d resolution 24]
amenity=fuel & (name ~ '.*[Vv]alero.*' | brand ~ '.*[Vv]alero.*')      {set
mkgmap:label:1=' '} [0x600c resolution 24]
amenity=fuel {name '$(name)'} [0x2f01 resolution 24]

You are telling me that these will NOT be found in a FUEL SEARCH (0x2f01)
on the GPS because I do not have 'continue_with_actions' at the end of each
action?

Do I have to add CONTINUE_WITH_ACTIONS or could I just use CONTINUE?

If this is correct, this is why you define 0x2f01 as INVISIBLE, but is
necessary in order to preform a POI SEARCH?

Greg

On Sun, Mar 6, 2016 at 5:03 AM, Walter Schlögl <Walter.Schloegl-Resch at aon.at
> wrote:

> Hi Greg,
>
> all supermarkets are found in the POI list if you give supermarket the POI
> Nr 2E02.
> shop=books is the POI Nr 2E03, shop=mall is POI Nr 2E04 and so on.
>
> So usually all supermarkets would have the same Icon also,
> but with the solution shown below you can give different supermarkets
> different icons.
>
> If you would just map all Aldi-supermarkets to 3501 without continue
> it would get the correct icon, but not found any longer in the search list.
>
> Do you use this feature on your Garmin device, to search for Point of
> interests?
>
> Walter
>
>
> *From:* greg crago <gregcrago at gmail.com>
> *Sent:* Saturday, March 05, 2016 10:53 PM
> *To:* Development list for mkgmap <mkgmap-dev at lists.mkgmap.org.uk>
> *Subject:* Re: [mkgmap-dev] Question about using different ROAD CLASS's
> andROAD SPEED's for one linetype.
>
> 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 at 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 at gmail.com>
>> *Sent:* Friday, March 04, 2016 11:37 PM
>> *To:* Development list for mkgmap <mkgmap-dev at 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 at 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 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
>>
>> _______________________________________________
>> 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
>
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20160306/a78b2fa0/attachment-0001.html>