BaseCamp fixes requests

https://forums.garmin.com/showthread.php?31446-BaseCamp-File-Location

Thanks Bob.

C:\Users\{username}\AppData\Roaming\GARMIN\BaseCamp\Database contains 'folder' 4.4

It also now contains BaseCamp.bat:

del 4.4-5
ren 4.4-4 4.4-5
ren 4.4-3 4.4-4
ren 4.4-2 4.4-3
ren 4.4-1 4.4-2
ren 4.4 4.4-1

And I've put a shortcut on the desktop to BaseCamp.bat

A double-click on the shortcut hides the db files from BC so opening BC opens in a clean state. The batch file keeps 5 or so previous backups of the files in case anything does get lost. This is much simpler than deleting all the individual bits in BC directly.

I guess I could add another batch file called restore that does the same thing in reverse to retrieve previous databases without having to do it 'manually' !

I'll be happy just to get copy and paste into BC. When I'm setting up our spring through fall trip in the RV that is some where around 500 way points so I still use Mapsource because copy and paste is so much less labor intensive and no typo's, very bad for lat/long. For CG's I use the name, the lat/long and driving directions plus add the url.

What exactly are you trying to do? Where are the 500 points coming from? in what format?

What exactly are you trying to do? Where are the 500 points coming from? in what format?

These are generated from the various federal websites, such as US Forest Service, BLM, etc. I go to the web site and pull up the camp ground of interest and then copy and paste the campground name, description, Lat/Long and driving directions into a new waypoint. For this coming trip it is up to 623 waypoints.
When we went to Alaska I even used the BC parks and trails website to make waypoints of their campgrounds. Copy and paste sure beats typing in turn at the white post go three miles and turn left at the rock pile etc.

Have you ever looked at Forestcamping.com?

I have found this website invaluable in attempting to figure out which federal campgrounds I'd like to visit because of their comment field.

However, I do not just copy and paste from any Fed database because I don't trust the Feds to have an accurate Lat./Long, or ANY other relevant information. I have BaseCamp open in another window and the first thing I do is see if that CG is already in the BC database (CNNA, Topo USA or State maps from GPSDepot.com)....if so, I just save it as a waypoint. IF IT IS NOT, I then use a combination of the maps, FS, BLM, Google Earth, and any other source I can come up with to place the waypoint as accurately as possible. Then I add relevant stuff into the notes.


Yes, my method is more time consuming, but at 66, I DON'T LIKE SURPRISES!!!!:mad:

These are generated from the various federal websites, such as US Forest Service, BLM, etc. I go to the web site and pull up the camp ground of interest and then copy and paste the campground name, description, Lat/Long and driving directions into a new waypoint. For this coming trip it is up to 623 waypoints.
When we went to Alaska I even used the BC parks and trails website to make waypoints of their campgrounds. Copy and paste sure beats typing in turn at the white post go three miles and turn left at the rock pile etc.

That sounds like several cut&pastes per waypoint to me. Perfectly doable: with BC open start a new waypoint, open the waypoint's properties and copy the relevant info into Position, Notes, etc. I can't understand why you'd be copying driving directions as such because, presumably, you're putting the waypoints into BC so that you can have it make a route, which would include full driving directions.

Does BC not already have the campgrounds listed in Points of Interest?

BC POI doesn't list the campgrounds we use. Found another thing about BC I really really don't like, if you don't purge everything from the NUVI prior to connecting with BC open it downloads everything from the Nuvi and over writes all waypoints with the same name that are in BC. This means since Garmin GPSr always truncate the comments you lose all the comments you had in the waypoint in BC. Found this out the other night when looking at Kincaid lake a USFS CG we were thinking of changing to. Wasn't part of the route. All the information was gone in the comments except the first 11 characters. Besides the driving directions, I also add CG amenities. We always add the driving directions so they can be compared to a paper map. The CG's are loaded as both part of the route and as custom poi's so we don't have to get out the laptop when a question comes up about what the GPS is indicating we should do. Our routes are not down an interstate, get off at an exit and there is the CG. We use a lot of county roads where the GPS mapping data base has a greater chance of being in error. Never forget Garmins disclaimer "This is a Navigational aid....".

Anyways back to Mapsource until I have a better handle on how to configure BC to my liking if it can be done.
No apparent way to keep data separate in BC; over writes data without warning when connecting the Nuvi, and having to wade thru multi forms instead of a single form like Mapsource to build a waypoint is to much.

Note to today's developers from an old school programmer KISS principle!

Can we have 1ooths on the speed (MPH) column in the track properties ?

It seems my prev. message got lost in the ether!

Found another thing about BC I really really don't like, if you don't purge everything from the NUVI prior to connecting with BC open it downloads everything from the Nuvi and over writes all waypoints with the same name that are in BC.

I'm not sure what you're doing but BC doesn't automatically download anything from a connected GPS into the BC database. So what you're describing could only happen if you manually do it. Even if you do import stuff it doesn't overwrite data, at least I've never seen it do so :confused:

...Even if you do import stuff it doesn't overwrite data, at least I've never seen it do so :confused:

Basecamp has done that or something very similar to that to me!!! Although I forget if it just writes the old data in Basecamp over the new waypoint with the same name or if it writes the new data from the unit over the old data in Basecamp.

In the case of importing a gpx file into BaseCamp which file contains waypoints having the same name as waypoints already in BaseCamp but different locations Basecamp was basically just throwing away the new waypoint location and using the old location. I first became aware of this when importing a purchased waypoint file with approximately 800 waypoints in it. I posted the problem up here in the Mac section but none of the Admins showed any interest in it.