Related

BaseCamp 3.3.0.3 Beta available

Former Member
Former Member
We decided to release another Beta before 3.3.1. This release fixes some of the shaping point issues for Zumo 4x0 and 5x0, so we are especially interested in feedback on that (please use https://forums.garmin.com/showthread.php?t=24732 to provide feedback regarding that topic). We also fixed some other issues, and added a few more features that weren't done at the time of the first Beta.

Download the Beta here: http://developer.garmin.com/apps/BC/BaseCamp_3.3.0.3_Beta.exe. If you used 3.3.0.2, you should also be able to update from within BaseCamp.

If you haven't tried 3.3.0.2, make sure to check out https://forums.garmin.com/showthread.php?t=24413, there have been a lot of changes!

Change list from BaseCamp 3.3.0.2 to 3.3.0.3
  • Fixed zumo 5x0 and 4x0 route transfer issues. Note that this may cause route transfer issues on the zumo 660. A future firmware update on the 660 will address this issue
  • Update waypoint references to map data when recalculating routes. Advice for the first beta that said that shaping points only worked for brand new routes can now be ignored
  • Added hiding of Activity profiles
  • Added creating OpenCaches from waypoints
  • Added calculating ascent and descent for direct routes
  • Added indication of data filter visibility state on the data list
  • Change to prevent property dialogs becoming lost off screen after screen resolution changes
  • Fixed any profiles from BaseCamp 3.2 that have invalid routing preferences (ie invalid vehicle types and incorrect avoidances)
  • Fixed list in-place rename requiring pressing enter to complete the edit
  • Fixed the "Reset Headers" context menu being displayed after renaming an item
  • Fixed issue writing out altitude when exporting to the GDB file format
  • Fixed track filtering "automatic mode" for tracks with no time information


Known issues
  • Doing a “Send to” from the root device folder to “My Collection” crashes. This is when selecting the entire contents of the device in the folder list, and only when selecting the root My Collection in the folder/list picker dialog.
  • Sending geocaches to some of our older devices (first generation Oregons and older) fails when there aren’t already geocaches on that device (a geocaches.gpx file).


These will be fixed in the final release.
  • Former Member
    0 Former Member
    How do you distinguish between "category" lists and other lists that a waypoint name appears in when a waypoint is saved back to the device? ... .... If a waypoint name appears in two category lists and two other lists that are used for, say, route planning, does that mean the waypoint will end up on the device with the two correct categories or is it going to end up there with four categories: two correct and two incorrect?

    - I created a "Categories" folder with a TEST list in it.
    - Then I created two more lists with the names ROUTE1 and ROUTE2 in My Collection.
    - I created a new waypoint.
    - I dragged and dropped it to all three lists.
    - Then I dragged the waypoint from My Collection and dropped it on the All Data folder in the Device.

    As you would expect, since there is no way to identify whether a list is a "category" or just another list, when the waypoint is transferred to the device it ends up with categories of all the lists it appears in: TEST, ROUTE1, ROUTE2.

    That`s not especially useful. Especially since it`s just plain wrong.

    ...ken...
  • Former Member
    0 Former Member
    GDB Export not compatible with MapSource GDB

    In BC 3.2.2 and I think in BC 3.3.0.2Beta, if I import a MapSource gdb file and Export the list containing the imported gdb as type gdb, I can open that file in MapSource. This makes for great interoperability between the two products. With BC 3.3.0.3Beta, I cannot open a gdb export from BC in MapSource.

    With MapSource, when I open a route containing waypoints, those waypoints are converted to unique Map Points and no longer point to the Waypoints. That makes for an advantage to gdb files as they are not modified when opened in MapSource.

    Is it possible in BaseCamp to continue using Version 3 gdb format for exports to remain compatible with MapSource?
  • Former Member
    0 Former Member
    experience & requests after using 3.3.03

    1) No problem to leave mapsource for what it is
    2) after selecting detail level (low, medium, high etc) via toolbar the control keeps the focus: focus back to map?
    3) with route dialog / window open, scrolling through waypoints/shapepoints and moving them to roads (basecamp does a bad job in snapping them to roads while making a route while cliking on 'roads'), the route recalculation starts and after that the dialog undergoes a reset with the first routepoint at the top: the focus should come back to last selected route point, to be able to proceed with adjusting... same when reordering the waypoints (e.g. after inserting a new one accidentely at the bottom) compare with behaviour in Mapsource!
    4) import of user POI files
    5) the zoom level at which standard POIs are show,n is now linked to the selected detail level and zoom level. an option to turn pois on and off? or a user setting in the display setting of an activity profile at which zoom level they should be shown?
    6) in the route dialog: add a button "show on map" as in Mapsource (mapsource is not forgotten totally :o)

    Kind regards
  • Former Member
    0 Former Member
    In BC 3.2.2 and I think in BC 3.3.0.2Beta, if I import a MapSource gdb file and Export the list containing the imported gdb as type gdb, I can open that file in MapSource. This makes for great interoperability between the two products. With BC 3.3.0.3Beta, I cannot open a gdb export from BC in MapSource.

    With MapSource, when I open a route containing waypoints, those waypoints are converted to unique Map Points and no longer point to the Waypoints. That makes for an advantage to gdb files as they are not modified when opened in MapSource.

    Is it possible in BaseCamp to continue using Version 3 gdb format for exports to remain compatible with MapSource?


    That is the intention, BaseCamp is still exporting Version 3 gdb. Can you attach a gdb file that was exported by BaseCamp 3.3 that MapSource cannot open?
  • Former Member
    0 Former Member
    This just gets weirder all the time. ... Instead of going to all the trouble of adding a "Lists" tab to the waypoint properties dialog and putting category list names in there, why didn't you just add Categories as a waypoint property in the first place?

    When or if you add the ability to add list names to the Lists tab, what if you want to add a category that there is no list for? Will the new list be automatically created and the waypoint name added to it? Or will the user have to remember to create the new list first?

    How do you distinguish between "category" lists and other lists that a waypoint name appears in when a waypoint is saved back to the device? ... That is a question that applies even now, not just when or if we get the ability to add list names to the Lists tab. If a waypoint name appears in two category lists and two other lists that are used for, say, route planning, does that mean the waypoint will end up on the device with the two correct categories or is it going to end up there with four categories: two correct and two incorrect?

    .... Never mind ... I`ll test it and see what happens.

    ...ken...


    We didn't create a separate way to categorize waypoints, because we already have one: lists. No need to complicate matters by having two parallel ways to categorize things.

    Once we allow to add a waypoint to a category/list in the lists tab we will create a new list with the waypoint in it, yes.

    There is no distinction between "categories" and lists because a list IS a category.

    Why would you put a waypoint in a route1, route2 or test list unless it belonged there for some reason? I would assume you put it there because there was a good reason for this waypoint to be in that list, and so it makes perfect sense to me that it would show up as that category on the device.

    I admit that it is different than the categories in MapSource that you are accustomed to, but for someone starting out in BaseCamp I think it's quite straight-forward. No need to create categories in some obscure options dialog, no need to sync categories between device and application, no arbitrary restriction to 16 categories. All you do is what you would already do in BaseCamp: categorize your data into lists, send it to the device and they will be categorized without your knowing that a feature "waypoint categories" even exists.
  • Former Member
    0 Former Member
    That is the intention, BaseCamp is still exporting Version 3 gdb. Can you attach a gdb file that was exported by BaseCamp 3.3 that MapSource cannot open?

    Exported BC file that cannot be opened in MS:
  • Former Member
    0 Former Member
    BaseCamp cannot open it either, so it's a corrupted gdb file. Can you attach a gpx export file as well? Hopefully I will be able to import the gpx, and then export as gdb to reproduce the issue.
  • Former Member
    0 Former Member
    Simple gpx that cannot be read after exporting as a gdb

    Simple gpx that cannot be read after exporting as a gdb. Importing this gpx into BC and exporting as a gdb makes a gdb that cannot be opened in either BC or MS. Note the original route was made in MS and imported into BC.
  • Former Member
    0 Former Member
    I still cannot reproduce this. I have a suspicion this is caused by some route settings that we do not handle correctly.

    Which activity profile do you have set for that route? And can you give me a screen-shot of the route settings for that profile/that route?
  • Former Member
    0 Former Member
    I'm using Automotive profile:


    A backup of my BC context is here http://garmin-mapsource.wikispaces.com/file/view/2012FLashMobBug.Backup. It won't be available tomorrow due to the Wiki shutdown protest of SOPA.
Copyright © 1996-2025 Garmin Ltd. or its subsidiaries