PolishMapDataSource.checkType()) invalid type 0x5400 for POLYGON
Good day or night! :) I am surprised, but the MkGmap does not understand this definition of TYPE like this: [POLYGON] Type=0x05400 but works fine with Marine types: [POLYGON] Type=0x10F01 Yes, I know that I can divide this long record into three parts: [POLYGON] Type=0x54 Subtype=0x00 Marine=N But it is a little inconvenient. :( When working with a TYPE file: [_polygon] Type=0x05400 such an error does NOT occur! By the way, cGPSmapper works well with both TYPE recording options. -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
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
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
Hi Vadim, with r4496 the type 0x5400 is accepted again. See http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4496 Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Pinns UK <osm@pinns.co.uk> Gesendet: Freitag, 22. Mai 2020 12:57 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] PolishMapDataSource.checkType()) invalid type 0x5400 for POLYGON 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
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Thank you very much, Gerd! But the problem is solved only for types without subtypes (0xx00/xx00). The same error message still appears for types with subtypes (0xx0x/0xx1x / xx0x/xx1x). SEVERE (MapFailedException): American Lake_v2.kmz.mp: (thrown in PolishMapDataSource.checkType()) invalid type 0x2801 for POLY GON, line 81 Link to test MP: https://yadi.sk/d/6Al6_yGpMe4LgQ -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
Hi Vadim, I might be wrong but I think the IMG format doesn't support subtypes with lines or polygons unless you use the extended types. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Vadim <bombur@mail.ru> Gesendet: Freitag, 22. Mai 2020 18:39 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] PolishMapDataSource.checkType()) invalid type 0x5400 for POLYGON Thank you very much, Gerd! But the problem is solved only for types without subtypes (0xx00/xx00). The same error message still appears for types with subtypes (0xx0x/0xx1x / xx0x/xx1x). SEVERE (MapFailedException): American Lake_v2.kmz.mp: (thrown in PolishMapDataSource.checkType()) invalid type 0x2801 for POLY GON, line 81 Link to test MP: https://yadi.sk/d/6Al6_yGpMe4LgQ -- 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
Hi Gerd! You're right! Sorry, I didn’t know that. cGPSmapper compiles MP-files with types 0XXYY of polygons and polylines without any errors. But all types in the resulting IMG are casts to XX. Thanks again! -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
Hi Gerd! Sorry, but can you fix same "error" with polylines ? :) SEVERE (MapFailedException): C:\work\AmericanLake.kmz.mp: (thrown in PolishMapDataSource.checkType()) invalid type 0x0e00 for POLYLINE, line 381 -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
Hi Vadim, sure, sorry that I forgot it yesterday. See r4497. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Vadim <bombur@mail.ru> Gesendet: Freitag, 22. Mai 2020 21:29 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] PolishMapDataSource.checkType()) invalid type 0x5400 for POLYGON Hi Gerd! Sorry, but can you fix same "error" with polylines ? :) SEVERE (MapFailedException): C:\work\AmericanLake.kmz.mp: (thrown in PolishMapDataSource.checkType()) invalid type 0x0e00 for POLYLINE, line 381 -- 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
Everything worked as it should! Thank you, Gerd, once again! -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
participants (3)
-
Gerd Petermann -
Pinns UK -
Vadim