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.
  • Map information missing:
    Example: I want to compare the content of two OSM Maps of germany. I load both on an USB stick (J:). The one called gmapsupp_D1.img, the other gmapsupp_D2.img
    If I click now in Basecamp (not Beta)/devices on one of this map icons, It opens the "Map property" window and shows the information, on which map I have clicked, as example "J:\Garmin\gmapsupp_D1.img".
    If I do the same in Basecamp Beta, I get only the information "Map on USB_stick (J:)" which is identical for both maps, so I have to figure out by try and error, which map is linked to which icon.
  • Former Member
    0 Former Member
    Map information missing:
    Example: I want to compare the content of two OSM Maps of germany. I load both on an USB stick (J:). The one called gmapsupp_D1.img, the other gmapsupp_D2.img
    If I click now in Basecamp (not Beta)/devices on one of this map icons, It opens the "Map property" window and shows the information, on which map I have clicked, as example "J:\Garmin\gmapsupp_D1.img".
    If I do the same in Basecamp Beta, I get only the information "Map on USB_stick (J:)" which is identical for both maps, so I have to figure out by try and error, which map is linked to which icon.


    In the mean time (until this is addressed to your needs) you could rename the OSM maps so that they actually show the name you give them BC and on your GPS (if it supports a non-gmapsupp.img name).

    Use JaVaWa GMTK. Great program and it is easy to use. I change my OSM installed map names to reflect Country and version all of the time as I evaluate different maps of the same region but with different TYP files.



    Cheers,
  • Former Member
    0 Former Member
    Getting an Unknown Error importing Waypoints.gpx from Etrex30

    The attached file gives me an error in BaseCamp Beta 3.3.0.3, but opens fine in MapSource.
  • Use JaVaWa GMTK. Great program and it is easy to use.,


    Thanks DRTBYK for your answer. I tried GMTK and it seems really to be a god program for maps which are "installed" and registered in the registry. But the OSM Maps which I use together with my Oregon are not registered. The gmapsupp_xx.img files are only copied to a folder called Garmin on the Oregon or an USB Stick. GMTK does not find this files.
    The "missing information" is not really a problem for me, as I don't compare maps every day and there are workarounds. But if it is possible to correct it in Basecamp 3.3, it would be nice.
    regards
  • Former Member
    0 Former Member
    The attached file gives me an error in BaseCamp Beta 3.3.0.3, but opens fine in MapSource.


    And BaseCamp-Mac v3.3.0.2 reports it as an invalid GPX file as well. Yet, all of my other GPX editing programs open the file just fine.

    Cheers,
  • The attached file gives me an error in BaseCamp Beta 3.3.0.3, but opens fine in MapSource.


    I opened the file in Google earth without adapting the altidute to the ground and found, that the waypoints fossil1 and fossil 3 have an elevation, which is a figure with about 25 digits.(probably far outside the known universe). I confirmed this also with ExiftoolGui.
  • Former Member
    0 Former Member
    ....waypoints fossil1 and fossil 3 have an elevation, which is a figure with about 25 digits...


    Yep. Here's a snippet from the GPX file.

    <wpt lat="37.897266" lon="-112.949892">
    <ele>4999999781011763100000000.000000</ele>
    <time>2012-01-06T22:03:23Z</time>
    <name>Fossil 3</name>
    <sym>Triangle, Green</sym>

    Clearly the elevation is bogus.
  • Former Member
    0 Former Member
    Outside the known universe

    Good to know. Those waypoints were re-samplings of existing waypoints with an Etrex 30. A firmware problem maybe?
  • Former Member
    0 Former Member
    BC does not recalc the same as MS, Z550 or Z665

    Attached route from a friend recalculates the same in my Z550, Z665 and in MapSource. BaseCamp routes differently. The attached jpg from BC shows in red where BC recalculates differently than the others. To test, recalculate this MS route in BC, export either the MS route or the recalculated BC route in the Z550 and recalculate. In the Z665, you must recalculate first as shortest, then as fastest to trigger a real recalculate.
  • Former Member
    0 Former Member
    We don't transfer the categories per se, what BaseCamp does is to create lists (or put waypoints in an already existing list of that name) for all the categories the waypoints are in that you transfer from the device.

    So connect your device, select the waypoints you want to transfer, right-click, 'Send to', pick My Collection.

    If you have categories on the device, but don't transfer waypoints from that category, BaseCamp will not create lists for these categories.

    I hope this makes sense, let me know if it doesn't.


    Falagar,

    I tried several times with nothing in BaseCamp, connect the gps and the data is transferred
    but nothing that I seen that would show that the waypoint categories were created before or
    after the Send to My Collection.

    I did create a folder in My Collection and created 16 lists in that folder for my categories
    and named them as they are in the gps. Moved the 1100 waypoints to the list they belong in.

    I cleared the waypoints out of the gps and used BaseCamp to send them back. The couple of
    points that I checked did end up in the correct category on the gps.

    After that I created a waypoint on the gps and placed it in a category then connected the gps
    to the computer. The waypoint shows up in BaseCamp but is not placed in any category.

    If I use MapSource to receive the data from the gps it will show the waypoint is in the category
    that I placed it in on the gps.

    With BaseCamp I guess I am still missing a step somewhere with the categories.

    Also what I did see is all the time stamp data in my track files were cleared when sent to the
    gps. Anyway to stop the tracks from being sent back to the gps with BaseCamp? With MapSource
    I could deselect tracks and my track data in the gps would not get changed.

    MapSource would clear the time stamp data as well so whatever is going on with that is common
    to both programs and or the gps. Being able to turn the track transfer off when sending data
    to my gps would be a big plus for me when using BaseCamp.

    Mark