What Is The Best Way To Resolve Errors Found Using JaVaWa Device Manager?

You need to totally disable that Open Map Chest map image file to test to verify that it's causing the errors.

Turning off the map(s) from the device's map settings menu on the unit won't necessarily pinpoint the issue.

Older Garmin devices let you disable the mapsets from being seen and parsed by the unit at boot up by changing the map's filename extension from .img to something else.

This no longer works on newer Garmins (unsure when they started this) as all files (the .img extension is ignored) in the Garmin folder will be read and parsed by the device and used if it's a valid mapset.

To disable the map from being seen by the unit, either:

1. Delete the mapset .img file from the device. This can be very time consuming because if you need to copy the file back to the device's internal storage, you are limited by the device's interface speed which can be very slow depending on the device.

2. This is the preferred way that I use: Create a folder, any name (I use "disabled maps") on the device's internal storage. It could be in the root of the device's storage or even within the Garmin folder (of course in it's own separate folder within the Garmin folder). After the folder is created on the device, MOVE (not copy) the mapset .img file to this folder. This will be pretty much instantaneous since the file is remaining on the device itself. You are not deleting it, just changing where it's located.

With the file out of the Garmin root folder, it will NOT be seen by the device so it won't be parsed or used.

Test the unit again for errors and repeat with the different mapsets.

If you have the mapsets on the external storage, again create a "disabled maps" folder and move the file to that folder to disable it. I don't however know how the device scans the external storage for mapsets so you may need to experiment with the location of the "disabled map" folder.

I'd think that the Open Map Chest map is the one causing the issues because it's from a totally different source than the others you've mentioned.

US Auto Midwest
US Auto Mountain
US Auto Northeast
US Auto Pacific
US Auto South Atlantic
US Auto South Central

Sorry, no experience with those maps, but from the names I'm wondering if they are all really just part of the same big map? If so, then there is probably some overlap between them (identical tiles in the overlapping areas). Don't know, but that could be a deal-breaker. Is it possible to download the whole "US Auto" map, where all the tiles would be in one file?

The way OpenMapChest works, the full North America map is not available as a .img file, but only as a .gmap file for BaseCamp. He would have to download the .gmap, drop it into BaseCamp's map directory and build a map for his device that way. He clearly downloaded the individual images that make up OpenMapChest North America, and as you mention, the various regions overlap, causing the warning.

OpenMapChest helpfully provides instructions on adding the .gmap folder to BaseCamp.

I just wanted to mention that the OpenMapChest files are fine.

The errors that I am concerned with are the USA OSM Auto and USA OSM Topo files.

What is the best way to get the USA OSM Topo files as an .img map? The USA OSM Auto extract with a .img file, but the USA OSM Topo don't.

I think it can't be done for these maps. When I used GmapTool to do the conversion from .gmap to .img, the major highways (only the major highways) appeared twice, curved and jagged. Zoomed out, they converge and look fine, but zoomed in you see one smooth curved highway and one from a higher zoom level made of straight line segments. In the USA OSM Topo map .gmap files, there are three TYP files (they determine how the map looks). But .img files can only have one TYP file. So it seems that .gmap supports a more sophisticated way of handling zoom that .img cannot support. Mr GmapTool uses that more sophisticated way in his Topo maps, which is why he doesn't also offer them as IMG maps. His maps are technically brilliant.

Are you sure about that? I gave up on Garmin and their ridiculous map format - which was brilliant in its day and set the stage for almost everything that followed with digital/gps mapping. But it did not age well IMO. And Garmin doesn't care, because they have their own highly-restricted tools for making maps that the rest of us can't use.

Anyway, when I first started making Garmin format maps almost 20 years ago, I bought a program called "Mapwel" which was clearly the most user-friendly option at that time - maybe it still is? No idea, because that is all ancient history to me. But I see that Mapwel still exists.

Now, the interesting thing is, Mapwel had a very non-standard way of using typ files. I forget the details now, but basically, each tile (segment) had its own typ file, so a full map could have quite a few typ's. That reminds me of what you just observed.

This worked fine on the GPS (better on some than others, IIRC) but was completely incompatible with Garmin software or third party Garmin tools. Not interested in going down that rabbit hole again, but am just wondering if your statement that .img files cannot have multiple typ files is actually correct? .img files are merely containers that can hold a variety of things. This always confuses people - one type of .img file can be dropped right into the /garmin folder on your GPS, another cannot. So - my guess is that the .img file format *can* support multiple typ files, but it will break some software, because it doesn't expect multiple typ files.

Here's an old thread from GPSFileDepot that touches on the topic. If you look at other old forum posts there, you should find further discussion

https://forums.gpsfiledepot.com/index.php?topic=2401.0

BTW, "Mr. GmapTool" used to be active at GPSFileDepot as user "Popej". His posts were always very informative and insightful. I do miss those days. But he has not posted there since 2021.

https://forums.gpsfiledepot.com/index.php?action=profile;u=2...

I agree that he is brilliant. Where we part ways is his single-minded focus on Garmin's map format, which is only useful if you buy one of their expensive devices. I remember another thread over at GPSFileDepot discussing raster imagery on Garmin GPS devices (raster imagery is maps that are made from pictures - like aerial imagery or scans of paper maps). He just had no use for any of that, saying that the maps need too much disk space and going even farther to say that nobody needs to see aerial imagery on an automotive GPS. OK, he made a good argument at the time. But this seems like a very old-fashioned point of view in today's world.

But the bottom line is that his work is indeed brilliant and his software remains (arguably) the most powerful tool for working with Garmin maps.

And to bring this rambling post on a stormy Sunday morning back on topic.... I would only suggest that an .img file may be able to do some tricks that might surprise you! The concept of an .img file as a container is actually very powerful, and Garmin deserves a lot of credit for that. It can even contain raster imagery. I remember a map of the Isle of Wight being an example of this. The following is from a Google AI search.....
__________________________________________

Garmin .img files natively support embedded raster imagery overlays using specialized map compiling tools.

A well-known UK-centric example of this implementation involves overlaying BirdsEye Select raster mapping or DEM (Digital Elevation Model) terrain over regions like the Isle of Wight.The Isle of Wight

Example Case
Third-party cartographers and Garmin's legacy BirdsEye Select platform utilize the Isle of Wight as a standard testing environment for high-resolution hybrid maps.

How it Works
Inside the .img File: A standard Garmin .img file uses a FAT-based subfile container system. While natively built for vector data (points, lines, polygons), developer tools like GlobalMapper, MAPC2MAPC, or G-Raster allow creators to inject georeferenced raster tiles (such as GeoTIFFs or scanned paper maps) directly into the .img subfiles.

The Resulting Display (The Example):
When loaded into Garmin BaseCamp or a compatible handheld unit, the vector contour line layers are dynamically rendered on top of the raster imagery background. For example, the steep cliffs of Ventnor (the highest point on the Isle of Wight) will display rich, photographic or shaded raster ground texture underneath clear, routable vector trails.

To be more precise, a TYP file in an IMG can only have one Family ID. There are three TYP files in his .gmap Topo, and they all have the same family ID, but slightly different names. That's impossible using Mkgmap to compile an IMG. Therefore his .gmap tool must allow different TYP files with the same family ID to be invoked at different zoom levels, which Mgkmap cannot do. It seems .gmap can do things .img cannot do, and probably vice-versa. You could use Mgkmap to compile three maps of the same area with three family IDs, for different zoom levels, but not with the same family ID. So my guess is that is why he doesn't make an .img version. If anyone knew how to do it, he would know. All my maps are made with both mkgmap and gmaptool.

Boy that name sure caused a memory jolt...I hadn't heard it in such a long time.

This is useful information.

"Now, that's a name I've not heard in a long time. A long time."