Related

BaseCamp 3.3.0.2 Beta is available

Former Member
Former Member
BaseCamp 3.3 is here! We are starting off with an early Beta release to give everyone a chance to check out the new features and pound on it for a little bit before we release the final version.

Download it here: http://developer.garmin.com/apps/BC/BaseCamp_3.3.0.2_Beta.exe.

We have incorporated a lot of user requests from this very forum. If your desired feature/bug fix didn't make it into this release, don't hesitate to remind us.

We are very interested in your feedback, please report bugs and oddities you find, and comment on the new features.

This is the change-list from 3.2.2 to 3.3.0.2. I will add some explanations and screen-shots in later posts.

  • Added collapsible list folders and sub-lists for improved organization.
  • Added shaping point support for zumo devices like done in MapSource.
  • Added explicit support for shaping points. These will be transferred to supporting devices.
  • Added support for transfer of waypoint categories on supporting devices. These are displayed in BaseCamp as lists.
  • Added more activity profiles, with improved activity routing on supported maps.
  • Added specific avoidances for various road classes, removed the road selection slider.
  • Added custom activity profiles.
  • Added keyboard short-cuts for editing tools (divide, insert, erase).
  • Added a tools menu for easier discovery of tool keyboard shortcuts.
  • Changed to make GPX files on a memory card directly editable.
  • Changed to read all GPX files on a memory card, similar to how devices behave.
  • Improved graphing of track data.
  • Improved graphing when multiple routes or tracks are selected.
  • Improved layout of geotagged photo, waypoint, route, and track properties.
  • Added additional statistics to route and track properties.
  • Added 'Center on map' check-box on route and track dialogs.
  • Added an easier way to add waypoints to routes (Insert Waypoint button).
  • Added additional data fields to waypoints (such as address and phone number).
  • Added display and updating of date last modified for waypoints.
  • Added display of lists that contain this data item to properties.
  • Added receiving geocache visits from devices.
  • Added logging geocache visits on OpenCaching.com.
  • Added printing of geocaches.
  • Added alternate notification mechanism (less annoying pop-ups).
  • Added display settings to adjust width of routes and tracks.
  • Added support for importing waypoints and tracks from KML/KMZ files.
  • Added suggested file name when exporting (so it isn't always 'untitled').
  • Added more map details for higher detail setting.
  • Added data filters to map view.
  • Added preserving the dialog size for each data type.
  • Added option to reset track's altitude to map data.
  • Added functionality to remember display feature settings per profile.
  • Changed 'Remove List and Contents' to 'Remove list and unique contents'.
  • Added Shift-Delete short-cut for 'Remove list and unique contents'.
  • Improved printing of routes and tracks.
  • Fixed issues with sending routes to the zumo.
  • Fixed elevation profile labels for Windows XP (no longer invisible).
  • Fixed issue when duplicating a route. BaseCamp will now also duplicate the waypoints in that route.
  • Fixed issue with the data filter not being remembered between application runs.
  • Former Member
    0 Former Member
    Moving/stopped time

    Hi!

    I am trying this beta version, and I have found the moving/stopped time calculation very useful, but I don't fully understand the criteria to calculate those times.

    I have tried some of my tracks and in all of them I have found the stopped time excessive. For example, in one track my Oregon 450 showed 2h stopped out of a 7h walk, I manually calculated it and the result was similar, but according to the beta Basecamp I had been stopped for almost 4h!.

    According to my manual calculation, the beta Basecamp considers "stopped time" when you are moving slower than 1 mph, am I right?. In that case, I find that treshold excessive, 1 mph can be a reasonable speed when you are walking up a steep slope, or on a difficult terrain.

    It is true that when you are stopped the device can slightly move your position, but according to my experience that false moving leads to slower speeds (never more than 0.2 mph), so I think that would be a more precise treshold.

    I have another suggestion for further versions: I think the map should zoom in to a more detailed scope, as the GPS device does. Sometimes you can need more detail to check some delicate issues, such as the best way to tackle a summit.

    Thank you and excuse my spanglish
  • Former Member
    0 Former Member
    The current version of Basecamp (non beta version 3.2.2) supports multiple delete via multi-select using shift/ctrl!..... (I just checked, as I have multiple versions currently installed on this system.)

    In the beta 3.3.0.2, you must delete each waypoint individually.....

    ~ What happened to this feature in the new beta version?


    ~Can anyone else confirm this, or is it just my installation?
  • Former Member
    0 Former Member
    Hi
    It seems like it is not Posebyen to uncheck "Shopping". Or, even if unchecked the yellow shopping-symbols are there.
    Joachim Seehusen
  • Former Member
    0 Former Member
    Sorry.
    It should have been "Not possible to uncheck "Shopping"

    Joachim
  • Former Member
    0 Former Member
    The current version of Basecamp (non beta version 3.2.2) does in fact support multiple delete via multi-select using shift/ctrl!..... (I just checked, as I have multiple versions currently installed on this system.) ~ What happened to this feature in the new beta version?

    Are they killing off existing features, or is this just an oversight?


    Multi-select is still working when selecting data. It is not working for folders/lists (this has never worked in previous versions either).

    We'd like to add multi-folder/list selection as well. This will have to wait for another version though.
  • Former Member
    0 Former Member
    Hi,
    I just came over another problem. Sometimes, if I do a right klick on an route I just get the menu entry "reset headers". When is this the case? It's pretty annoying.

    Regards
    Marcus


    This is a bug, we hope to have this fixed in the final 3.3 release.
  • Former Member
    0 Former Member
    I have a suggestion also: When viewing Track Properties/Graph, add a choice of Distance or Time, like Training Center has. I only use TC when I can't do something in BC. I ride my bike on a Trainer up here in the frigid north, and I like to "record" my Cadence and Heartrate using my Oregon 450, but since I don't go anywhere, there is no distance involved. It would be nice to view both of them, in reference to time riding.

    Overall, I'm happy with the changes you've made--kudos :)
    Ron


    Thanks.

    We do want to add time to graphs eventually.
  • Former Member
    0 Former Member
    Hi!

    I am trying this beta version, and I have found the moving/stopped time calculation very useful, but I don't fully understand the criteria to calculate those times.

    I have tried some of my tracks and in all of them I have found the stopped time excessive. For example, in one track my Oregon 450 showed 2h stopped out of a 7h walk, I manually calculated it and the result was similar, but according to the beta Basecamp I had been stopped for almost 4h!.

    According to my manual calculation, the beta Basecamp considers "stopped time" when you are moving slower than 1 mph, am I right?. In that case, I find that treshold excessive, 1 mph can be a reasonable speed when you are walking up a steep slope, or on a difficult terrain.

    It is true that when you are stopped the device can slightly move your position, but according to my experience that false moving leads to slower speeds (never more than 0.2 mph), so I think that would be a more precise treshold.

    I have another suggestion for further versions: I think the map should zoom in to a more detailed scope, as the GPS device does. Sometimes you can need more detail to check some delicate issues, such as the best way to tackle a summit.

    Thank you and excuse my spanglish


    The moving time calculation is somewhat tricky. The GPS has more data available for this that BaseCamp doesn't have, so BaseCamp has to do the best it can with the limited data available to it. Currently there is a threshold of 0.5 m/s (about 1.8 km/h, or 1.1 mph) when calculating the moving/stopped time. Everything slower than that will be considered stopped, everything faster will be considered moving.

    We can definitely tweak that number. 0.2 mph seems a little low for my taste. What about 0.3 m/s (0.45 mph)?
  • Former Member
    0 Former Member
    Sorry.
    It should have been "Not possible to uncheck "Shopping"

    Joachim


    With the new City navigator maps it is indeed not possible to un-check shopping POIs. That's something that has changed in the map data, we are working on a way to fix it.
  • Former Member
    0 Former Member
    Hi Falagar,
    what was the issues with sending routes to the zumo from Basecamp?
    Actually I have a Zumo 220 and I have the problem that some routes created with Basecamp will crash the Zumo during the import process. The device switches off or reboots. Thats realy annoying.

    Regards
    Marcus


    Well, the thing we fixed was something on the 660, but it broke routes for older Zumos.

    Can you attach a route (as gpx) that crashes your Zumo 220? And also let us know which map product and version you used?

    I'd like to verify that our internal fix works for your route as well.

    I apologize for the inconvenience.