Thank you, Gerd for your analysis. Turns out I was not communicating with eTrex properly (hint: it is important to wait for each packet's ack - not just write to serial bus like crazy) - had nothing to do with the file format. Thank you again, jose On Mon, Dec 27, 2021 at 9:51 AM Gerd Petermann < gpetermann_muenchen@hotmail.com> wrote:
Hi Jose,
I found mkgmap_vs_qlandkarte.zip in https://files.mkgmap.org.uk/detail/539
Garmins Basecamp can open the gmapsuppMKGMAP.img but not the other file. Same with GMapTool. The gmapsuppQLAND.img contains large blocks of 0x00 or 0xff and the Garmin sub files are aligned to 0x10000 boundaries: LBL starts at 0x10000 RGN starts at 0x20000 TRE starts at 0x70000 MDR starts at 0x80000 SRT starts at 0x90000
Maybe the eTrex Legend requires this alignment?
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <gpetermann_muenchen@hotmail.com> Gesendet: Sonntag, 26. Dezember 2021 17:31 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] generated gmapsupp incompatible (?) with eTrex Legend
Hi Jose,
sorry, I don't know how to help here. Maybe you can upload the two files to files.mkgmap.org.uk/ and we can check what the difference is.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von jose1711 <jose1711@freeshell.de> Gesendet: Samstag, 25. Dezember 2021 23:34 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: [mkgmap-dev] generated gmapsupp incompatible (?) with eTrex Legend
hello,
i am using mkgmap to generate gmapsupp img from an osm file, then uploading it via serial connection to eTrex legend (b/w version). i noticed the following behaviour:
- gmapsupp file created by mkgmap does not always show in the device (sometimes even the map metadata is missing) or there are glitches (lines across the whole screen on some zoom levels)
- same file opens just fine in gpxsee (https://www.gpxsee.org/)
- if i open tdb and matching .img file in qlandkarte (no longer being developed), select submap and export to gmapsupp, the new file is larger and the issues after uploading to garmin device are gone
what sometimes helps (with file coming out of mkgmap) is uploading with a speed of 9600 bauds (as opposed to 115200).
here's an example:
- mkgmap gmapsupp.img - 302592 bytes
- qlandkarte gmapsupp.img (same map) - 786432 bytes
i was checking a diff but could not make out anything (too many differences). haven't tried older versions of mkgmap or checking out other tools yet.
could you please advise?
thank you,
jose
ps: i can share both map files if it helps in any way. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev