[mkgmap-dev] Commit: r2580: - correct check-styles: overlays are not used for points and polygons

Fri May 10 17:44:13 BST 2013

well best add to it, that for extended types, for many there is also 
special treatment - and they won't appear on all devices - even if they 
display in Mapsource 6.13.6 (this is still the best indicator, as many 
extended types that won't be shown on GPS devices from Garmin, won't be 
shown in 6.13.6 - but will be shown in later versions of Mapsource (>=6.14).

The only really "safe" extended types for lines are 0x10e?? to 0x10f??. 
Types 0x11??? are not shown on many old devices. Types 0x10??? are about 
50% shown. You need to experiment - and keep in mind that especially 
Nuvi and other non outdoor Garmin GPS display less types!
On 10.05.2013 06:49, WanMil wrote:
> Hi,
>
> thanks! I think we should try to keep the documentation up to date for
> new commits and improve other things step by step.
>
> I am not very familiar with garmin ids but you are right: it would be
> good if there is a chapter about them. Recently there was a question
> about that in the german forum:
> http://forum.openstreetmap.org/viewtopic.php?id=21135
>
> You description with 1) to 4) is fine for me. So in any case it is
> better to have this "rule-based" description than no description :-)
> Maybe someone else has a good idea for a better description later on?
>
> WanMil
>
>> Hi,
>>
>> done. I think the doc should also contain details regarding Garmin types
>> that
>> are usable in mkgmap, but it's difficult to document them without writing
>> pseudo-code :-(
>> These are the rules that I found:
>> 1) If a type is >= 0x0100 (means it has more than one byte), the rightmost
>> byte
>> must be between 0x00 and 0x1f, so e.g. 0x011f is ok, 0x0120 is not.
>> 2) if a type is > 0x010000, it is an extended type, which can be used for
>> points, lines, and polygons.
>> 3) if the type is not extended, it must be >= 0x0100 for a point, <= 0x7f
>> for a line, and <= 0x3f
>> for a polygon.
>> 4) a routable type is between 0x01 and 0x13 or one of: 0x1a,0x1b,0x16
>>
>> I don't know how to put that into the doc.
>>
>> Gerd
>>
>>
>> WanMil wrote
>>> Hi Gerd,
>>>
>>> can you please add some words about the new check-styles options to the
>>> documentation. There is already a chapter "4.1 Testing a style" which
>>> seems to be a perfect place :-)
>>>
>>> Thanks
>>> WanMil
>>>
>>>> Version 2580 was committed by gerd on Sat, 27 Apr 2013
>>>>
>>>> - correct check-styles: overlays are not used for points and polygons
>>>> - separate code for check-styles and list-styles option, check only a
>>>> single style if --style was used.
>>>> _______________________________________________
>>>> mkgmap-dev mailing list
>>>>
>>> mkgmap-dev at .org
>>>> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>>>
>>> _______________________________________________
>>> mkgmap-dev mailing list
>>> mkgmap-dev at .org
>>> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>>
>>
>>
>> --
>> View this message in context: http://gis.19327.n5.nabble.com/Commit-r2580-correct-check-styles-overlays-are-not-used-for-points-and-polygons-tp5758735p5760426.html
>> Sent from the Mkgmap Development mailing list archive at Nabble.com.
>> _______________________________________________
>> mkgmap-dev mailing list
>> mkgmap-dev at lists.mkgmap.org.uk
>> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev