For your information 0x54 appears as transparent in a TYP file used in the latest Garmin Cycle Map EU 2020 r Nick On 22/05/2020 11:22, Vadim wrote:
Hi Thomas!
Yes, I am sure. I am using cGPSmapper v0100d. ( https://web.archive.org/web/20160414230419/http://www.cgpsmapper.com/downloa... ). Works well with MP-files. But this version of cGPSmapper has another bug: it does not understand the FULL record of non marine types (for example, 0x02800) in TYP files. There were no errors during compilation, just the wrong TYP file was generated with a bad section [_drowOrder].
Example: (.txt source) [_drawOrder] Type=0x02800,1 Type=0x02900,2 Type=0x02A00,3 Type=0x02B00,3 Type=0x02C00,4 Type=0x02D00,5 Type=0x02E00,6 Type=0x02F00,6 Type=0x03000,7 Type=0x03100,8 [end]
(compilation result of cGPSmapper): [_drawOrder] Type=0x000,2 Type=0x000,3 Type=0x000,4 Type=0x000,5 Type=0x000,6 Type=0x000,7 Type=0x000,8 Type=0x000,9 [End]
The same results with Type=0x2800,1 and Type=0x002800,1 :(
Even GpsMapEdit does not work correctly with a full/long TYPE record (Type=0x02800 or Type=0x10f00) in polish MP-files.
Incidentally, the equivalence of the full record (Type=0x10f00) and split (Type=0f/Subtype=00/Marine=Y) described in the "cGPSmapper manual" (page 19)
PS: MkGmap works fine with Type=0x02800,1 in TYP-fifes.
22 may 2020, 8:13 +03:00 от Thomas Morgenstern <webmaster@img2ms.de>: Are you sure, that cgpsmapper works with 0x54 ?. The installationpacket, comes with cgpsmapper V99, includes file RGNtyp.txt. This listed in section RGN 80 as highest Typ 0x53. After that comes the Extended types, beginning with 0x01010 ...Type 0x54 is definitivly not listed in the original cgpsmapper-list . thomas
-- 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