I played with 3-digit points and found mkgmap not being able to compile a Typ 
file containing these.
E.g. points with code 0x137/00-0x137/09 appear in the compiled typ as points 
with the same code 0x001/00 for all of them.

My input file is a txt-file prepared with TypViewer, with which I can save such 
a file as Typ correctly.

I never stumbled upon this before, but it might be known to others.
Is there a workaround, or a mistake by me?

Jan


> Am 04.02.2020 um 14:29 schrieb Pinns UK <o...@pinns.co.uk>:
> 
> Personally I have not come across line types > 130 although I have seen 135 
> as a poi in a city navigator map
> 
> On 04/02/2020 13:18, Gerd Petermann wrote:
>> Hi Nick,
>> 
>> not sure about the limit of extended types. 0x1f for the lowest byte, but 
>> mkgmap doesn't seem to limit the higher byte. So maybe 1ff1f.
>> I think I'll add code to perform the same type checks for *.mp files as for 
>> style files.
>> 
>> Gerd
>> 
>> ________________________________________
>> Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von 
>> Pinns UK <o...@pinns.co.uk>
>> Gesendet: Dienstag, 4. Februar 2020 11:48
>> An: mkgmap-dev@lists.mkgmap.org.uk
>> Betreff: Re: [mkgmap-dev] Garmin Lines Visibility
>> 
>> Hi Gerd
>> 
>> Yes, I used a mp file - no error message was shown
>> 
>> I presume extended line types have a maximum of 13F1f?
>> 
>> Regards
>> 
>> Nick
>> 
>> On 04/02/2020 10:44, Gerd Petermann wrote:
>>> Hi Nick,
>>> 
>>> yes, 0x3f is also coded as limit in mkgmap. It complains when you use a 
>>> higher line type like 0x57 in the style:
>>> Error: invalid type 0x57 for POLYLINE in style file lines, line 121
>>> 
>>> Maybe it doesn't complain with polish (*.mp) input?
>>> 
>>> Gerd
>>> 
>>> ________________________________________
>>> Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von 
>>> nwillink <o...@pinns.co.uk>
>>> Gesendet: Dienstag, 4. Februar 2020 11:29
>>> An: mkgmap-dev@lists.mkgmap.org.uk
>>> Betreff: [mkgmap-dev] Garmin Lines Visibility
>>> 
>>> Hi All
>>> 
>>> Following from Jorics' response to Gerd  have done some more research
>>> regarding lines on Basecamp:
>>> 
>>> *Lines with non extended types*
>>> 
>>> it seems that the highest line type is 0x3F
>>> 
>>> Strangely Mapsource shows a repeat of lines 0 to 3F starting from 0x40
>>> This looks like  mkgmap allows such types but Garmin seems to set a 'flag'
>>> of some kind and regards 0x40 as 0x0 etc
>>> 
>>> Not Visible : 0x17 , 0x 2c , 0x30 - 0x3F
>>> 
>>> Not customisable Labels: 0x20 - 0x22
>>> 
>>> *Extended Lines*
>>> 
>>> Not Visible : 0x10200 - 102FF ,
>>>                    1080e ,
>>>                    0812 - 1081f,
>>>                   10b05-10b1f ,
>>>                  12e00 -anything higher
>>> 
>>> 
>>> 
>>> No Labels : 0x10906 - 1091f , 10b02-10b04
>>> 
>>> <http://gis.19327.n8.nabble.com/file/t339487/lines.jpg>
>>> 
>>> 
>>> 
>>> 
>>> --
>>> Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
>>> _______________________________________________
>>> 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
> _______________________________________________
> 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

Reply via email to