Hi Carlos,
splitting could be useful, when you'd like to create img in one step.
Other option is to install map on PC and then use MapInstall to create
img. MapInstall does splitting for big maps.
--
Best regards,
Andrzej
___
mkgmap-dev mailing list
The 4GB limit is a result of the fact that Garmin devices use FAT16B
without LFS (only the very oldest) and FAT32 (all the rest) filesystems.
Garmin devices do not support exFAT; though, devices with rewritable
firmware could be made to support exFAT. The reason that FAT file
systems are used a
The other files have to be split as well I am pretty sure. Each map should
also work independently. So it's just a matter of way take 3700MB for .IMG
files to have enough overhead for the MDR/MDX. Except if no address search,
then take 4050MB for split.
On Sun, 18 Oct 2020, 11:16 Carlos Dávila
wr
I'll have a look at that thread later. I can process large files in my
server if needed.
El 18/10/20 a las 9:50, Gerd Petermann escribió:
Hi Carlos,
see
http://gis.19327.n8.nabble.com/Split-gmapsupp-img-files-over-4GB-tc5967656.html
I tried to code this at that time but got stuck because I d
Hi Carlos,
see
http://gis.19327.n8.nabble.com/Split-gmapsupp-img-files-over-4GB-tc5967656.html
I tried to code this at that time but got stuck because I didn't have the time
to create such a large map to find out where MapInstall places the other files
(e.g. MDR, TYP and if any other file or f
As far a I know, mkgmap is able to produce unlimited size gmapsupp
files, but SD cards and internal device memories have a limit of 4 GB in
a single file. To overcome that limit, recent versions of Garmin City
Navigator maps are split into several gmapsupp that work as a single one
in devices w
