BaseCamp 3.2.2 is available

Former Member
Former Member
BaseCamp 3.2.2 has been released, it is available for download at http://www8.garmin.com/support/download_details.jsp?id=4435.

Currently there is a problem with the Auto-Update, so please use the download link for now.

3.2.2 is a Maintenance Release, that means it is mostly bug-fixes, not new features.

This is a list of changes:

  • Fixed an issue with migrating waypoints with thumbnails from previous versions of BaseCamp to 3.2.1. This issue could have corrupted the database.
  • Fixed an issue with tracks that had been duplicated becoming corrupted.
  • Added a prompt to notify the user when data loss might have occurred.
  • Added a 'restore from previous version' menu item.
  • Added support for exporting of fitness data (heart rate and cadence) in tracks.
  • Changed to attempt to fix the paths in Garmin Custom Maps (KML ground overlay) files at start-up without notifying the user that there were problems with the file.
  • Changed the message displayed at start-up when the current video mode/card doesn't support 3D.
  • Improved initial download size estimates for some BirdsEye products.
  • Fixed some issues with undo/redo.
  • Fixed several issues related to application shutdown.
  • Fixed an issue with not recognizing Garmin mode USB device (such as the GPSMap 60) arrival and removal.
  • Fixed several issues related to aborting transfers to Garmin mode USB devices.
  • Fixed some issues related to ejecting mass storage devices.
  • Fixed some issues with changing folder selection while using the BirdsEye wizard.
  • Fixed an issue with reading geotagged photos from many smartphones.
  • Former Member
    0 Former Member over 13 years ago
    Bicycle routing

    The newest releases of BC ignores roads, which are forbidden for cyclists, completely. This causes routing on these kind of roads (like motorways) even if the activity profile is set to bicycle. In MapSource and on the GPS routing is fine.

    In the attachment you can see bike route made in Openfietsmap (OSM cycle map) in some part of the Netherlands.
    http://www.openstreetmap.org/?lat=52.07645&lon=5.42625&zoom=15&layers=O

    Basecamp routes the cyclists over a major primary road (Randweg N224), forbidden to cyclists (indicated on the map with - - -). Mapsource recognizes this and routes through the village which is correct.

    The test map can be downloaded here:
    http://mijndev.openstreetmap.nl/~ligfietser/openfietsmap/test/OpenFietsMap%20(test).gmapi.zip

    This behaviour does not apply to my maps only but also other OSM maps are affected as well, like the osm world routable maps from http://garmin.openstreetmap.nl as well as cycling maps from Onroute/Waypoint.



    If i try the route on City Navigator 2012.20 then i am route on the highway which is forbidden for cyclists

    See this google maps streetview of the N road.

    This is going wrong in MapSource 6.16.3 and BaseCamp for Mac and Windows.

    I have tried more routes and they all make use of N roads in the routes. I tried pedestrian also, it's a bit better, but also uses N roads for routing.
    Some N road in the Netherlands have separated bicycle paths beside them (N52.21201 E5.50252), but these cycleroads are not drawn on the City Navigator maps. Thats the main reasons there are specialist bicycle maps in The Netherlands.

    The N stands for National or Major Higways for us. And are forbidden for Cyclists. Sometimes there are separate bicycle roads. In Germany these roads named B roads and in France it's also roads beginning with N.
    Interstates have numbers like A or E and are avoided correctly.


    Now the question is; is it a Map error or a wrong interpretation of road classes?
  • Former Member
    0 Former Member over 13 years ago
    Now the question is; is it a Map error or a wrong interpretation of road classes?


    I'll try to find out.
  • Former Member
    0 Former Member over 13 years ago
    Nothing Works in Basecamp

    When I download the free version of basecamp (now using Mapsource) if find most of the commands are greyed out. Is this a buy only mapping program or can I get the one that works since I already own 2 Garmin GPS's?
  • Former Member
    0 Former Member over 13 years ago
    I am guessing here that you have your device data selected when everything is greyed out? You also have an older device like a GPS 60 or similar?

    Select (left-click once) your device's 'All data' folder, then right-click, choose 'Send To' and then 'My Collection'. That will transfer the data from your device to BaseCamp's internal data collection.

    Then select 'My Collection' on the top left under 'Library'. You should now be able to manipulate your data, and add new data. You can also send data from 'My Collection' to your device.

    If I guessed wrong, and something else is awry, let me know.
  • Why, when I download BaseCamp_322.exe, which is shown as 100.91 MB, I get a file that is 96.2MB?

    Then when I click it to install it, it says it is "Extracting Garmin Web Update", after which there is no evidence that BaseCamp exists on my Win7/64 PC?
  • Former Member
    0 Former Member over 13 years ago
    Can't restore tracks and waypoints to my 62s after BaseCamp 3.2.2 update

    Prior to updating to 62s v3.4, I used BaseCamp to export the unit's tracks and waypoints to a file I called 62sbackup.gpx
    As instructed by the update, I then deleted the \Garmin\GPX folder on the 62s, and ran the software update.
    Then I imported 62sbackup.gpx into BaseCamp and used BaseCamp to send the imported file back to the unit.
    The current file structure for tracks is \Garmin\GPX\Track1.....Track25.
    The current file structure for waypoints is a single file \Garmin\GPX\Waypoints.gpx.
    Of the 25 restored tracks only 5 show in the 62s.
    The one track I made after the software update also shows.
    No waypoints show in the 62s.

    Folders in my Garmin folder are: Birdseye, CustomMaps, CustomSymbols, ExtData, Filters, GPX, JPEG, Profiles, and Text.

    Did the update change the folder structure or did it change the format of the GPX files themselves?
  • Former Member
    0 Former Member over 13 years ago
    Can you attach one of the track[number].gpx files that the 62 does not display?
  • Former Member
    0 Former Member over 13 years ago
    Waypoints.gpx and Track2.gpx are attached. None of the waypoints in waypoints.gpx show. Track2.gpx doesn't show.
  • Former Member
    0 Former Member over 13 years ago
    I know that there are some routing changes in the works, so I'll try to make sure this will get fixed. Right now I have no idea why this occurs, but there is a chance though that this might be something that will have to be addressed by the map builder.


    I'm pretty sure it has to do with the access bits. Third party maps like OSM use this for preventing routing on roads to prevent a vehicle takes a certain road that is not allowed to drive/ride/walk on.

    I observed that those access attributes not longer work with the latest release of Basecamp. They do work in Mapsource and still work on the GPS units (unless the firmware will be updated?).
  • Former Member
    0 Former Member over 13 years ago
    Waypoints.gpx and Track2.gpx are attached. None of the waypoints in waypoints.gpx show. Track2.gpx doesn't show.


    Both of these display fine on my test Oregon 450 when I put them in my device's Garmin\gpx folder. The files look good.

    So I am not sure what might be causing this. Maybe try deleting all user data on the Oregon? Or even master-reset (http://garminoregon.wikispaces.com/Miscellaneous#FAQ-M1.%29%20How%20do%20I%20master%20reset%20my%20Garmin%20Oregon?)?