BaseCamp 4.2.1 is available

Former Member
Former Member
You should be able to download the installer from http://www8.garmin.com/support/download_details.jsp?id=4435 or update from within BaseCamp.

List of changes:

  • Added Trip Planner
  • Adds an easy way to plan multi-day trips
  • Round trip support
  • Can print a trip itinerary
  • Can add destinations along a route
  • Flying support (airport and flight number look-up)
  • Supports traveling between different time zones
  • Can add Adventures that you'd like to take as part of your trip
  • Routing Improvements
  • Added support for different route profiles for different legs of a route
  • Added RV and Truck routing profiles with special route options
  • Find Improvements
  • Added support for UK postal code search
  • Added support for Yelp search
  • Added support for named POI search (far away POIs should be found if it's an exact name match)
  • Added support for POI category search (you can type 'Hotels, Las Vegas, NV')
  • Added quick search (hover over the map to invoke it)
  • Added ability to display more search results
  • Fixed various find issues
  • Basestation Improvements
  • Added support for displaying BirdsEye while in Basestation mode
  • Added support for displaying and saving the track of the Basestation itself
  • Added support for displaying the most recent update time for Basestation contacts
  • Added support to have different folders and lists with the same name (as long as they have a different parent in the folder hierarchy)
  • Added support for changing the location of BaseCamp's database
  • Added Irish Transverse Mercator grid
  • Fixed an issue where roads from the base map were displaying along with roads from the detailed map
  • Fixed an issue where BaseCamp was not displaying properly localized map labels
  • Fixed issue with Garmap Southern Africa Topo & Rec 2012.3 NT not being displayed in BaseCamp
  • Fixed an issue with certain file names for Adventures and Garmin Cloud
  • Former Member
    0 Former Member over 12 years ago
    Great observation, Dan. I never thought about re-checking the release log. It now seems clear that the Database feature is intended to allow the database to be relocated (i.e., an alternate database location) rather than the ability to create and use an alternate database. This explains why the new database retains the filename of AllData.gdb. It is a shame, since so many Win BC users have been asking for the ability to use multiple databases.


    I think we are getting sideways on this because I'm using Mac speak. When I say Library the Mac uses a "special" folder called a Library which contains all of the BaseCamp required folders and data. If Win-BC supports "alternate" database locations it therefore supports multiple databases. Once you set up an alternate location you will have created ALL of the Win-BC folders and files (databases) necessary and you should be able to "switch" between "locations"; i.e, databases. But, you can not put two of the same AllData.gdb files in the same \Database\v4.2\ folder.

    The issue I have is that Win-BC gets corrupted even creating an alternate database location as well as doing a RESTORE from a Mac-BC BACKUP.
  • Great observation, Dan. I never thought about re-checking the release log. It now seems clear that the Database feature is intended to allow the database to be relocated (i.e., an alternate database location) rather than the ability to create and use an alternate database. This explains why the new database retains the filename of AllData.gdb. It is a shame, since so many Win BC users have been asking for the ability to use multiple databases.


    You can run separate databases in different locations, so you can have multiple databases (I'm running 2 at the moment)
  • Former Member
    0 Former Member over 12 years ago
    This explains why the new database retains the filename of AllData.gdb.


    FYI the BC database consists of more than just AllData.gdb. It includes any Birdseye image files (I have 2.5GB of those) along with a bunch of other files.

    All BC databases use the same folder structure and so on. They therefore need to be in different locations.

    Now when I moved my BC database from its default location to another drive/path it took many minutes to do so through Windows Explorer because of the size (2.5GB) of my Birdseye images folder.

    FYI I relocated the BC database on my XP machine and saved a bunch of disk space since I use two different profiles on that machine and now there's only one copy of the database vs two (one per profile).
  • Former Member
    0 Former Member over 12 years ago
    You can run separate databases in different locations, so you can have multiple databases (I'm running 2 at the moment)


    I'm very new to BaseCamp and have used MapSource for many years
    I have hundreds of files that are saved on my computer using the Microsoft Windows file system of sub-directories (folders) and they are easy for me to find.
    With BaseCamp anything I create or import gets bunched together in "My Collection" and soon I have a lot of data all in one place.
    I'd like to have several databases for different functions. IE one for dual sport routes, another one for motorcycle road routes, another for trips in my vehicle.
    I've tried to do this creating several databases each with a unique name but get jumbled data when I switch databases.

    If I'm understanding this thread correctly I need to put each database in a separate location (sub-directory) (folder)

    Can anyone confirm this?

    thanks
  • I think we are getting sideways on this because I'm using Mac speak. When I say Library the Mac uses a "special" folder called a Library which contains all of the BaseCamp required folders and data. If Win-BC supports "alternate" database locations it therefore supports multiple databases. Once you set up an alternate location you will have created ALL of the Win-BC folders and files (databases) necessary and you should be able to "switch" between "locations"; i.e, databases. But, you can not put two of the same AllData.gdb files in the same \Database\v4.2\ folder.

    The issue I have is that Win-BC gets corrupted even creating an alternate database location as well as doing a RESTORE from a Mac-BC BACKUP.


    While I am not familiar with Mac and the Mac-BC product, I believe that I now understand your explanation of the Mac-BC library structure and how it differs from the Win-BC implementation. Thanks for that explanation!

    I believe my previous comments about Win-BC and "alternate databases" versus "alternate database locations" was not well stated. Clearly, the new Win-BC version 4.2.1 will support an alternate database location. I suspect that is the purpose for which the developers intended this feature to be used, since it retains use of the AllData.gdb file name for the primary database file rather than creating a new database file with the alternate database name specified by the user. (Yes, I understand the BaseCamp is comprised on more than the AllData.gdb file.)

    As already discussed, the new Win-BC version can be used to create and use alternate databases, as long as they are created in location other than the default database location. When I initially tried the alternate database feature, I thought that I could create a new ("alternate") database in the default location and it would receive the new database name (i.e., the one I specified). Obviously this was not the case and was the source of problems with corrupting my main database. I assume this is why FALAGAR did not understand my comment – if I am providing a new database name, I did not believe that I was creating the same AllData.gdb file exactly where the old one was.

    I too experienced the corruption when creating an alternate database. When I attempted to create a new (i.e., an "alternate" rather than a "default" database in a different location on a different hard drive), the process only created the \Database\ folder and caused Win-BC to repeatedly crash. Only by manually creating the subfolders and data files was I able to stop Win-BC from crashing, and then able to swap Win-BC back to the default database in the default location.

    I also experienced a Win-BC corruption problem when I tried to restore from my backup database copy. I made that copy immediately before testing the alternate database feature. Unfortunately, in my panic, I did not document the error message I received. I then tried and was able to restore using a slightly earlier database backup (a pre-version 4.2.1 backup) and then restore again using the latest backup (the one that initially failed the restoration attempt). I would be curious to know if there are an "structural" differences for a backup created using version 4.2.1 versus a pre-version 4.2.1 backup.

    Finally, as noted by another poster, by using the alternate database feature, the user can run with several different databases. However, given the way it is currently implemented in Win-BC (i.e., through the Edit -> Options dialogue window), I suspect this is not how the BC developers intended for this feature to be used. Hopefully FALAGAR will clarify how they intended this feature to be used (i.e., relocation versus alternate database, or both).
  • Former Member
    0 Former Member over 12 years ago
    The issue I have is that Win-BC gets corrupted even creating an alternate database location as well as doing a RESTORE from a Mac-BC BACKUP.


    I cannot reproduce the first issue you mention, and there are lots of people who successfully use this feature (myself included). We'll look into the second one.
  • Former Member
    0 Former Member over 12 years ago
    I too experienced the corruption when creating an alternate database. When I attempted to create a new (i.e., an "alternate" rather than a "default" database in a different location on a different hard drive), the process only created the \Database\ folder and caused Win-BC to repeatedly crash. Only by manually creating the subfolders and data files was I able to stop Win-BC from crashing, and then able to swap Win-BC back to the default database in the default location.


    This is strange. Where did you create this alternate database? Is there maybe some permission issue that BaseCamp cannot create the folders?

    I also experienced a Win-BC corruption problem when I tried to restore from my backup database copy. I made that copy immediately before testing the alternate database feature. Unfortunately, in my panic, I did not document the error message I received. I then tried and was able to restore using a slightly earlier database backup (a pre-version 4.2.1 backup) and then restore again using the latest backup (the one that initially failed the restoration attempt). I would be curious to know if there are an "structural" differences for a backup created using version 4.2.1 versus a pre-version 4.2.1 backup.


    All backup does is zip up the %APPDATA%\Garmin\Basecamp folder. Restoring blows away your current %APPDATA%\Garmin\Basecamp folder and unzips the backup file into that folder. If you have a backup (preferably small) that reproducibly fails to restore, send it my way (share on DropBox/SkyDrive). That would be very helpful.

    Finally, as noted by another poster, by using the alternate database feature, the user can run with several different databases. However, given the way it is currently implemented in Win-BC (i.e., through the Edit -> Options dialogue window), I suspect this is not how the BC developers intended for this feature to be used. Hopefully FALAGAR will clarify how they intended this feature to be used (i.e., relocation versus alternate database, or both).


    This feature is a bit of an advanced feature. We don't expect most of our users to ever user it. We provided a way to switch between databases, but as of now, a re-start of BaseCamp is required to switch. The re-location case isn't very fleshed out yet. Right now creating a new database will result in an empty one. To re-locate, you'd have to backup/restore or move the data manually. But, while currently still requiring a bit of fiddling on the user's part, both the alternate db case, and the relocating db case should be supported.
  • Former Member
    0 Former Member over 12 years ago
    The "English" interface appear to only offer 12 hour (AM/PM) times in 4.2.1

    As far as I can see the only way to get 24-hour times for track points is to switch to some language other than English. Since I don't speak any of those I'm in a bit of a quandary. What gives?

    Leifur
  • Former Member
    0 Former Member over 12 years ago
    The first (and only thing) I've done in 4.2 was to:
    backup my DB
    Change the location to ~my/dropbox/apps/[newfolder"GarminBasecamp"]
    restart Basecamp
    Restore from backup

    I'll poke around with the other features some time, but THANK YOU for adding support for an alternate DB location!

    P.S. OK for me to delete the 3.0 thru 4.1 folders that got dropped there?