Hi Steph,

looks like we have the same workflow - with a mistake in mine.
So I remembered the Header size option of TypViewer, which is always defaulted 
to 91: switched to 110 (or higher) the problem is gone.

Jan

> Am 11.02.2020 um 16:49 schrieb Steph <st3ph.mar...@laposte.net>:
> 
> Hi Jan,
> 
> I use a .txt type file from TypViewer.
> In my points file, I got "amenity=taxi [0x13703 resolution 24]".
> No problem to process with mkgmap and this .txt. If I load the generated .typ 
> in TypViewer, all seems correct.
> 
> Regards.
> 
> Steph
> 
> Le 11/02/2020 à 14:35, jan meisters a écrit :
>> 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
> _______________________________________________
> 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