Messages

Yes, JAVAWA Device manager will report the number of segments in a map (on a USB stick, in my case)

One possibility....

Try loading the KML into GPSU (www.gpsu.co.uk) - I guess it will appear as a series of broken tracks. If so, you can click on the start of each chunk and use Tools>Join/split track.

And save the result as a GPX.

If there is a large number of pieces, save as a PLT, use a text editor to convert all but the first ",1," to ",0," then reload the PLT and save as a GPX.

I'm using Javawa map convertor and distributing maps as .gmap folder that go into
/programdata/garmin/maps with no need for registry entries.

Are there any other maps on the GPS that might have conflicting segment numbers?

JAVAWA GMTK can help to diagnose this

There are some tools that will convert maps but, because different map systems implement features in different ways, it is unlikely that you will be able to get an exact copy.

However, many of the maps posted on this site have licence conditions that prohibit conversion, re-engineering etc. - so check carefully!

Hi Jack,

The Levels# directive links hardware levels (bits per coordinate like 21 or 23) to zoom levels.
For each object, the Data# directive defines the level at which the objects coordinates apply. My assumption is that the Zoom# directive maps the Data# to the Level#.

For example LevelX=21 ZoomX=Y DataY=(50.1,0.5) .

But, for safety, I keep X and Y the same so it's always, for example Zoom2=2

When compiling maps with cGPSMapper, there is an option POIIndex=Y/N.

But the Garmin IMG format contains 'Points of Interest' and 'Indexed Points of Interest' as separate data items.

It would be nice to switch indexing off or on for individual items (e.g index Hospitals but not trees) - is that possible?

There several tools from Javawa to help you find out what is happening.

Some .img files have a bit set that makes them invisible to Basecamp and Javawa device manage will allow you to change that.

In that case, I can't see a reason for the "Too many JNX files" message.

JNX files are Birdseye (unless you have been making them yourself). Have you downloaded a lot of Birdseye stuff??

The Garmin Custom Map format allows up to 100 map pieces ("tiles") each 1024x 1024 pixels.

There are tools like OKMap and MAPC2MAPC that will convert maps to that format. If the PDF is Georeferenced them MAPC2MAPC (with GDAL installed) will convert it with only a few clicks.

Have you thought of an iPad with a separate Bluetooth GPS device (I use a GNS2000) that you can position for best reception? Or an Android tablet with a separate GPS device? In UK the GNS2000 costs about 70 Pounds - so about US$110.

I compile a Garmin map and install it in Basecamp. I then use Basecamp to install onto the MicroSD card of a Garmin Oregon where it appears as Garmin/gmapsupp.img.

If I now copy that MicroSD card is there any reason why the copies should not work in other Garmin devices (assuming, of course, the card size is supported by the firmware)?

I run Basecamp under Windows 10 with no problem - except that if I try to run parallel streams they sometimes seem to conflict and one will fail. But that may not be specific to W10.

I struggled for several days to get Road and City indexing working - but found a solution which I am sharing.....

I compiled everything with CGPSMapper (paid version, of course), copied the .idx files to the MapsetToolkit mapset files and ran MapsetToolkit.

But my normal NSI installer would not install the map with working indexes (I had  uncommented the relevant lines!).

Then I tried Javawa Map Converter to make a .GMAP folder from the Mapset, copied the .gmap to Program Data/Garmin/Maps and indexing worked perfectly.