Welcome, Guest. Please login or register.

Login with username, password and session length
Forums Search:  

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Boyd

Pages: [1] 2 3 ... 270
GPSr Units / Re: Garmin GPS Map 60cx not seeing maps
« on: September 21, 2022, 10:36:40 AM »
Oh well, you certainly tried. Honestly, you're not missing much there. I know the 60c(s)x has its fans, but IMO it's day has long passed. Very limited mapping capability (2000 tile limit), no raster imagery, tiny low resolution screen, slow processor, 8-bit color, awkward pushbutton interface.

I loved mine back in 2006, but got the first Oregon in 2008 and it was so much more capable. The good things about the 60 series is that the screen is very readable in bright light without a backlight, so you get good battery life. The SirfStar chipset is also still pretty respectable as for accuracy, aided by the quad helix external antenna.

Anyway, certainly sounds like something is wrong. Maybe somebody else will come along with another idea?

Maps can contain POI, but that is completely different from what Basecamp considers "data". They cannot contain waypoints in Garmin's system, those are a form of user data that you create or load separately.

Search the map to find any included POI. I think some map authors here have included .gpx files along with their maps, not sure if that's the case with what you downloaded however.

Not familiar with what you downloaded, however maps and data are two different things in Basecamp. Data would be things like waypoints, tracks and routes. These would have to be imported separately info Basecamp - for example, from your GPS.

So, unless the package you downloaded included a separate file (such as a .gpx file) and you imported it, then data will be blank. After you import data into Basecamp, it will always be there, regardless of the map you are using.

GPSr Units / Re: Garmin GPS Map 60cx not seeing maps
« on: September 19, 2022, 09:47:07 AM »
Yes, a card that is too big or has files that are too big would be a problem. However, the OP says these same maps/cards work on his Montana 600. That should rule out the file size issue, since it also uses the FAT32 Filesystem.

You have probably done this, but just in case.... are you sure the map you want is enabled (and any other maps disabled)? See page 45 of the owners manual


Also look at the card info, as shown on page 69 of the manual. That should confirm whether the device actually "sees" the card and detects a map on it.

Problems with the contacts and the microSD card were not unheard of on the 60csx, which would prevent the card from being recognized.

GPSr Units / Re: Garmin GPS Map 60cx not seeing maps
« on: September 17, 2022, 10:43:17 AM »
Yes, the 60csx is a bit of an antique these days (have had one myself since around 2006). It will only recognize one map file named gpmapsupp.img and it must be in a folder named Garmin. The Montana doesn't care what the map file is named, as long as it has a .img extension. So, re-name one of your maps gmapsupp.img and see if that works.

Since it can only have one map file, if you want multiple maps on the 60csx, they must all be bundled into the same gmapsupp.img file. MapInstall is supposed to figure this out automatically if you use it, but I don't trust it, LOL.

I would only use Mapsource, Garmin's older software with the 60csx. There are tutorials on this site for getting and using it if you don't already have a copy. Just realize, your City Navigator and Bluecharts maps may not work on the 60csx, depending on exactly what maps you purchased. The DVD and download versions of City Navigator become locked to the first GPS they are installed on. The version that Garmin sells on memory cards can be used in multiple devices, but the cards are copy protected so they can't be duplicated.

Map Making Support / Re: Map colors on GPS device
« on: September 15, 2022, 10:20:43 AM »
Just realized that you are talking about a DriveTrack 70 (an older model) and I have the newer DriveTrack 71. I would not expect that to matter, but perhaps it does?

Here's my map of New Jersey, it works on my DriveTrack 71, DriveSmart 61, Dezl 760 and several Nuvi devices. I'd be surprised if it doesn't work on your DriveTrack 70. I discontinued this map last year but am bringing it back for a limited time since there still seems to be some interest.

Anyway, see if it works for you. The documentation is pretty thorough and there are several different .typ files and map themes enclosed for customizing the appearance. They might point you in the right direction. Just be aware, I take some liberties with Garmin road types, so that could be confusing.

If you want to look at these, let me know after you have downloaded them. I will be deleting these files soon and will not offer them again.

Mac Version for installation in Basecamp:


Windows Version for installation in Basecamp and Mapsource:


File Version for direct installation on the GPS only:


Map Making Support / Re: Map colors on GPS device
« on: August 22, 2022, 05:31:07 AM »
You could also play around with map themes, they are just little files that you put on the GPS. No need to re-compile your map


Should go without saying... if you are going to mess with files on the GPS, make sure you have a good backup first. And on a similar note, with the DriveTrack, you really need a backup of any Birdseye imagery. Garmin has effectively "orphaned" this device by discontinuing Birdseye.

Map Making Support / Re: Map colors on GPS device
« on: August 21, 2022, 03:42:29 PM »
Wow, I thought I was the only person in the world with a DriveTrack 70!  ;D

I have used several of my own maps on mine and it has no problem recognizing a standard Garmin .typ file. So I suspect the problem is MapWell. It has been many years since I used it, but they were doing something very strange and non-standard to customize the map appearance. IIRC, they inserted a separate .typ file in each map tile (segment). I had problems with this back in the days when I had a Nuvi device.

IIRC, you can export an .mp file from Mapwel. You could then re-compile it with cgpsmapper and use a standard .typ file.  You could then use typviewer to customize the appearance. That was my favorite .typ file editor (back when I was still making Garmin maps).


The DriveTrack and othe recent Garmin devices also can use Garmin "map themes" (.kmtf files) to customize map appearance. These can over-ride what your .typ file is doing, so it gets rather confusing.

You would need to do a Google search to learn more about these, it's been too long since I made one. But they can be created/modified with a text editor. You will find some examples if you look in the Themes folder on your DriveTrack.

Map Making Support / Re: Experiments with LIDAR
« on: July 24, 2022, 12:50:52 PM »
Am planning to expand the map to a much larger area later this summer.

The new, expanded map is now available! This is the new coverage area - over twice the size of the original map, more than 600 gb with almost 22 million map tiles!  8)

Here's Shenandoah, Virginia in 3d


3d view of the Catskills


This is how it looks on a phone.

You can view the 3d map in 2d North-up mode if you prefer - just click the compass to toggle between 2d/3d. But there's a separate 2d version of the same map without the elevation data if you aren't interested in 3d views, it loads much faster (note that 3d maps appear in blue text in the map menu)

Here's the 2d map of Martha's Vineyard, for example.


I would like to continue expanding this map to cover an even larger area in the future. I still have over 200gb free disk space on the server but need to find the best use for it. Ultimately, I'll need to lease additional disk space to support future expansion.

It's not practical to create a map this large in one piece, so I divide it into smaller blocks of 100gb to 150gb of uncompressed 32-bit floating point DEM data. After processing this, I end up with blocks of a few hundred thousand .png map tiles which are ~1/4 the size of the source files. Then there is a companion set of .png tiles that contain the elevation data in Mapbox RGB format. The elevation tiles only use about half the space of the map tiles.

Before creating the RGB tiles, the geoTIFF DEM source file must be processed with Mapbox rasterio, which is a rather complex command-line program


This encodes the DEM data as a .tif raster image which can be exported as .png map tiles. It took awhile to figure out exactly how to do all of this, Mapbox does not really support creating your own RGB DEM, they expect you to use their own pre-packaged DEM. But their DEM is about 5-meter resolution and I wanted 1-meter DEM. Using their own content can also result in usage charges but it's free to use their API with your own data. But you're pretty much on your own, I could find very little information about how to implement all of this locally but eventually figured it out through trial and error.

I create all the the tiles with Globalmapper using the option to only export fully-covered tiles, this prevents gaps between different blocks of data when I merge them with the full map. Finally, I zip the tiles, upload them to the server and unzip.

There are so many steps to the process and so many different files, I had to create a spreadsheet to track my progress!

You could try Mapsource, Garmin's older software. It was discontinued long ago but still available. Since you already have Basecamp, it should be easy - Mapsource should see the map that you have already installed. See this


And this


Map Making Support / Re: Aerial images
« on: July 05, 2022, 07:49:41 AM »
OK, just tried this on my DriveTrack and it lets me download Birdseye to the computer even though I no longer have an active subscription (same as always). When I try to send to the GPS, this is what I get - again, same as always.

But when I click the link to subscribe, this is what I get. Nice job Garmin. I was disillusioned about them before, but this is a new low.  >:(

Map Making Support / Re: Aerial images
« on: July 05, 2022, 05:24:00 AM »
Birdseye is a Garmin product, but the imagery comes from Digital Globe. I have two devices that are Birdseye-compatible: a broken Montana that I no longer use and a DriveTrack 70 that I still use in the car (with my own .jnx files). The DriveTrack included a 1-year Birdseye subscription when I purchased it.

Have you actually tried to renew a Birdseye subscription for your GPS? I have not, but in discussing this, another Montana owner claimed that it was possible to renew his subscription if he did it with Basecamp (as opposed to purchasing from Garmin's website). Not sure if he actually did this, but apparently he got a message asking if he wanted to renew in Basecamp.

I will give this a try myself soon, just for fun. If they are actually not allowing current Birdseye users to renew their subscriptions, Garmin is going to have a lot of angry customers.  >:(

I see that a number of retailers are still selling Birdseye subscription cards. Wonder what happens if you buy one of these?



And Garmin still has support FAQ's for Birdseye too


Available BirdsEye Products

Subscription Based:

The subscription lasts for 1-year from the activation date. The imagery downloaded to your device during the 1-year subscription does not expire. When the subscription expires, the imagery cannot be transferred to the device from BaseCamp. The imagery already on your device remains on the device. If you wish to renew your expired subscription, you just need to purchase a new subscription.

Map Making Support / Re: Aerial images
« on: July 01, 2022, 09:34:18 AM »
Garmin is ending Birdseye? Wow, I had not heard that. Do you have any more information about this? I found these with a quick search


If this is true... then you can probably disregard everything we have posted about making your own .jnx files. If Garmin is discontinuing it in basecamp, you would not be able to authorize your home-made .jnx files and they would be useless on the GPS.  >:(

Map Making Support / Re: Aerial images
« on: June 29, 2022, 02:51:34 AM »
True, but actually it is rather constraining. You need an *active* Birdseye subscription to be able to use .jnx files. You then must trick Garmin's servers into believing your imagery is actually Birdseye, because it must be authorized by Garmin or it won't work on the GPS. This all works fine, but (apparently) you can only have one Birdseye map per subscription.

This becomes an issue if you want to use "real" Birdseye imagery in addition to your own. If you have them both loaded on the GPS, they will be merged together which is a mess. So you would need separate SD cards - one with your own .jnx files and another with Garmin .jnx files if you want to use both. Now, there may be some way around this but I could not find it the last time I tried.

I suppose it would be possible to have multiple active Birdseye subscriptions (such as topo and satellite) if you want to have two kinds of imagery on the GPS at the same time. Of course, none of this gets around the terrible performance of raster imagery on Garmin handhelds. It is really slow to zoom and pan the map. And the screens on my Garmin GPS'es look terrible with aerial imagery, it's a "muddy mess" on my Montana 600 and the colors are all wrong too. Garmin has optimized their screens for high-contrast vector maps, not aerial photography with subtle shades of green and brown.

Map Making Support / Re: Aerial images
« on: June 28, 2022, 10:35:59 AM »
Getting back to aerial imagery... in your earlier post you said

For shading and basic 3D the 3" are fine for basecamp and gps and they are 2.75mb for each tile vs 25mb for the 1".

At first I didn't understand this, but then realized you were using the quote character to denote arc-seconds, in other words 1" = one arc second. Is that correct? And I also assume you are only talking about the DEM? Of course, one arc-second would be really low resolution for aerial imagery.

The comparison below might be useful for the OP. IMO, you want at least 4 feet/pixel resolution for hiking but 1 foot would be even better. The last example is a 30m or 1 arc-second view of the same area.

With a 100-tile limit for most Garmin handhelds, the "custom map" (.kmz) format will only permit a map that is 10240 x 10240 feet using 1-foot imagery. That's slightly less than 2 miles x 2 miles. Using 4-foot imagery you could cover an area about 8 miles x 8 miles. You can do the math yourself for other resolutions, just multiply 10240 times the resolution in feet.

Although I haven't used it myself, I believe one nice feature about mapc2mapc is that it will help you make the best use of 100 map tiles when making custom maps, and even has a grid where you can create irregularly-shaped maps that show exactly your area of interest.

As discussed above, you can get around the 100 tile limit by using .jnx files and fooling Garmin's servers to think they are Birdseye to authorize them for your gps. That will allow you to use something like 50,000 tiles.

Pages: [1] 2 3 ... 270