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
    Thank you for taking me into account, I think 0,3 m/s (1,1 Km/h) is closer to what you can consider "stopped", you seldom move slower, but sometimes, when you are half-climbing or walking throug a difficult terrain...

    I have checked the track I have attached. I spent 1 hour at 0,0 Km/h, 2h at <= 0,3 Km/h and 2:39 at <= 1,1 Km/h; looking carefully, the stretches below 0,3 Km/h are mainly stops (lunch, photos, views...), over 1,1 are mainly slow displacements (the track is linear) and between 0,3 and 1,1... 50/50. As you say it's a matter of tastes, CompeGPS only considers "stopping time" the speeds of 0,0 Km/h, and the GPS devices... I don't know.

    Thank you and have a happy new year.

    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
    FALAGAR:

    When I installed the most recent beta (3.3) the same thing happened. The first time the program launched, there were no waypoints imported.

    I waited 5 minutes, and exited the program. Upon relaunching it a second time, all the points began to appear from the 3.2 beta install.....

    This has got to have something to do with Win7 64bit......

    I haven't found any missing (invisible) points though......

    I'll see what I can come up with. I'm wondering whether it may have taken some time to capture the 3.2 database into the 3.3 beta data set. (More time than actually allotted before I began to work with the 3.3 beta.) ~ Upon initial launch of 3.3 beta, my waypoints were completely empty. I remember thinking: "Arrrghhh, Garmin never included automatic import in the beta"..... So I began reconstructing my data. I also should have specified this is happening on a windows 7 64bit business system. (A commercial grade Lenovo Thinkpad that has no other "known issues.") ~ Awesome top of the line system at the time......... I've had it for a few years.

    As for the waypoint not showing on the map, I'll see what I can come up with..... I just wish I knew exactly when it happened, so "I could backtrack and reproduce the anomaly."

    I do remember that when I initially found the problem, I had been reviewing all my waypoints, to make sure everything was categorized properly under the right sub folders...... I had seen a recently recorded/captured (within the past month) waypoint in a selected folder/list and noticed it was not being displayed on the map..... There were 5 or 6 waypoints in this folder list, but only 4 or 5 displayed on the map. I'm "thinking" that the specific waypoint must have been "still intact" at the root level, but not fully acknowledged when it was initially placed / "copied" into a sub-directory / list.

    I'm looking at the data now, hoping to find another waypoint like this.... And nope, there are no other waypoints presently missing from the display (that I can see). Also: None of the data seems to be missing from the old version 3.2. (So the problem must be exclusive to 3.3 beta, and likely have something to do with the nested folder support.) ~ Because the missing waypoint had bee moved into a sub-directory, which didn't/couldn't exist in 3.2. ~ I was wondering if somehow the problem was created during the import routine since I had just dragged and dropped these few points over from the GPS. (Hence, duplicate named data was being imported).... I discounted this as a possibility because only one point exhibited this problem.

    I do have many other waypoints imported from kmz files in different organized directories/lists.... These point represent cell towers, Appalachian trail data, and water bodies etc. There's no way I can tell if some of these ones are not displaying properly.... Way too many points.

    It's worth noting that the problem was noticed with waypoints that were originally dragged and dropped from the Garmin Montana. (& possibly a result of the import/upgrade to 3.3) ~ Not from importing kml/kmz files!

    Also, I just remembered (& I'm wondering if this could have been the cause of all this): I ended up installing the beta twice. Immediately upon initial install, I realized that the original 3.2 (non beta) was still running. (I had thought I had closed it out prior to installing, but apparently not.) Since I wasn't sure of the implications, I closed it out and immediately re-ran the installation. Upon running Basecamp the first time, (after that), that's when I saw an empty data set....

    I'm trying to reproduce & find what caused the problems. If and when I do, I will save the data....
  • Former Member
    0 Former Member
    Thank you for taking me into account, I think 0,3 m/s (1,1 Km/h) is closer to what you can consider "stopped", you seldom move slower, but sometimes, when you are half-climbing or walking throug a difficult terrain...

    I have checked the track I have attached. I spent 1 hour at 0,0 Km/h, 2h at <= 0,3 Km/h and 2:39 at <= 1,1 Km/h; looking carefully, the stretches below 0,3 Km/h are mainly stops (lunch, photos, views...), over 1,1 are mainly slow displacements (the track is linear) and between 0,3 and 1,1... 50/50. As you say it's a matter of tastes, CompeGPS only considers "stopping time" the speeds of 0,0 Km/h, and the GPS devices... I don't know.

    Thank you and have a happy new year.


    I'll adjust the threshold to be a bit lower, and will add a registry setting for people who really want to set their own.
  • Former Member
    0 Former Member
    FALAGAR:

    When I installed the most recent beta (3.3) the same thing happened. The first time the program launched, there were no waypoints imported.

    I waited 5 minutes, and exited the program. Upon relaunching it a second time, all the points began to appear from the 3.2 beta install.....

    This has got to have something to do with Win7 64bit......

    I haven't found any missing (invisible) points though......


    Can you upload a backup of your data somewhere? I'd like to see if I can reproduce it. www.dropbox.com would work, for example.
  • Former Member
    0 Former Member
    Can you upload a backup of your data somewhere? I'd like to see if I can reproduce it. www.dropbox.com would work, for example.


    Sending a PM containing link & access pwd....
    Data backup took some time, (large data set is from version 3.3) but no problems.....
    If you need 3.2, or prior non-beta version, let me know....

    (Due to file size limitations on dropbox account, download 3.3 data first if you need it. I'll have to delete the file in order to upload an older version.)

    Happy New-Year everyone!!!

    ~Bob
  • 0
    I'll adjust the threshold to be a bit lower, and will add a registry setting for people who really want to set their own.


    Great, Thank you! Can you also easily add a seting to choose the walking speed? And the ascending and descending speed? ;)
  • Former Member
    0 Former Member
    I'll adjust the threshold to be a bit lower, and will add a registry setting for people who really want to set their own.


    Thank you! I think that's a great improvement, and I do appreciate the way you take people's opinion into account, now I feel an important person!
  • Former Member
    0 Former Member
    Update

    FALAGAR:

    After uploading the 3.3 data set you requested, I have greatly simplified my data-set directory structure. (In doing so, I had to give up display combination options.) ~ Even in 3.3, it can be difficult to display exactly what subset of data (combinations) you want, when working with a "complex" set of data. (not having an option to hide/unhide individual folders/subfolders & lists)*

    Even so, the new 3.3 nested folders capability is proving to be extremely beneficial in terms of data organization! Can't explain exactly why yet, but I feel less envious of Google Earth! ~With the one exception of their imagery timeline feature. (Which can distinguish tree types (transitions / forest lines) via fall foliage color & winter views.)

    *I chose to give up a lot of display combination options because I was concerned with 1.) making errors resulting from frequent moves and 2.) risking data integrity issues associated with frequently moving large containers (folders) around the gui. (to obtain different display results/combinations as needed)

    Sending a PM containing link & access pwd....
    Data backup took some time, (large data set is from version 3.3) but no problems.....
    If you need 3.2, or prior non-beta version, let me know....
  • 0
    Can't walk steps

    Is the map responsible or Basecamp? I cannot create a new route when the map (Topo france) displays steps, though I am "hiking" or "walking".
  • Former Member
    0 Former Member
    Sending a PM containing link & access pwd....
    Data backup took some time, (large data set is from version 3.3) but no problems.....
    If you need 3.2, or prior non-beta version, let me know....

    (Due to file size limitations on dropbox account, download 3.3 data first if you need it. I'll have to delete the file in order to upload an older version.)

    Happy New-Year everyone!!!

    ~Bob


    I'll take a look at this tomorrow. Thanks so much!