
Hi devs, one of the reason that I needed so long to figure out the zip/city encoding in the NT format is that LBLFileReader.getZips() returns a more or less shuffled version of the list of zip codes in the LBL file. Reason is that we store the zips in a HashMap instead of an ArrayList. No idea why we do that. It seems it did no harm so far... Gerd

Hi Gerd Fantastic work. I've never see any effect of having a Mdr6 section (where the zips end up) either from mkgmap or any zip searching ability from a GARMIN NT map; both of which had MDR 6 sections. Ticker On Wed, 2022-03-16 at 15:55 +0000, Gerd Petermann wrote:
Hi devs,
one of the reason that I needed so long to figure out the zip/city encoding in the NT format is that LBLFileReader.getZips() returns a more or less shuffled version of the list of zip codes in the LBL file.
Reason is that we store the zips in a HashMap instead of an ArrayList. No idea why we do that. It seems it did no harm so far...
Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (2)
-
Gerd Petermann
-
Ticker Berkin