[mkgmap-dev] typfile curiosity

Wed Apr 17 20:27:01 BST 2019

Normaly, i prefer also the single line form. But in case you use the typ
viewer to change something in the typ file and you want to write it
back, the typ viewer changes all single line forms into the other way
:-(. And that happans again to me somme days before and until i noticed
that, i have build some maps with wrong POIs

Am 16.04.2019 um 23:38 schrieb Steve Ratcliffe:
>
> Hi
>
>> i just stumbled again about a curious effect of the built-in
>> typ-compiler from mkgmap. Just figured out that hex-ids for points,
>> which are built in the way Type = 0x108, SubType = 02 or equal are mixed
>> up after the compile to 0x00102 ?  I can avoid this by building the
>> hex-id only in one line, i.e Type = 0x10802. Its not for all of the ids,
>> may be only for points with ids > 0x100. Any idea ?
>
> When a type is written as 0x10802 it doesn't mean that the type is
> 0x108, since types are one byte.  The first '1' means that it is
> an extended (also called marine) type, with type=0x8 and subtype=0x2.
>
> When you write Type=0x102 then that means Type=0x1, SubType=0x02, just
> as Type=0x411 means Type=0x4, SubType=0x11
>
> The original way of writing it would be:
>
>     Type=0x08
>     SubType=0x02
>     Marine=Y
>
> The Marine=Y isn't supported in the TYP compiler, since I don't think
> anyone write TYP files using that notation.  It could be added if
> there really are lots of TYP files out there using it.
>
> I'd recomend always using the single line form.
>
> Steve
>
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
--

#####################################################

      Viele Grüße und 73 de Manfred Haiduk, DD8KQ
      e-mail mhaiduk at t-online.de dd8kq at gmx.de

#####################################################