Re: [mkgmap-dev] finding out more about the size taken by elements in generated map

Hi Jose GPSMapEdit from  https://www.geopainting.com/ can tell you some of this. The free version should do; install it and open gmapsupp.img or an individual tile. Then look at Map Properties > Statistics tab. Ticker On Thu, 2022-01-27 at 15:31 +0100, jose1711 wrote: > Hello, > can someone re

[mkgmap-dev] finding out more about the size taken by elements in generated map

Hello, can someone recommend a way how I can learn more about what the detailed statistics in respect to the byte size of each element in the map generated by mkgmap? What I am looking for is something like: - lines: 3.2 MB - road_class 0: 1.3 MB - road_class 1: 1.2 MB - road_class

Re: [mkgmap-dev] Code to read locked maps

Hi Gerd I agree with Carlos: It would be quite an achievement to create NT imgs. I looked at the POI structure once to unravel the extra types Garmin uses in its city navigation maps and they looked less daunting than highways & polygons . btw I have a hunch that mapsources' cache can reveal

Re: [mkgmap-dev] Code to read locked maps

That sounds promising, great!! Le 26/1/22 à 13:01, Gerd Petermann a écrit : Hi all, The source code [1] for GPXSee [2] contains a routine demangle() which "unlocks" a locked TRE file. I was aware that there are tools which can do that but never saw open source so far. It's easy to add this in

[mkgmap-dev] Commit r4879: original code for demangle is older, update comment

Version mkgmap-r4879 was committed by gerd on Thu, 27 Jan 2022 original code for demangle is older, update comment http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4879 ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://ww