Related

BaseCamp 3.2.0.1 beta is available

Former Member
Former Member
A beta version of BaseCamp 3.2 is available (link below). Please read the following:

Warning

This is beta software, or an early peak at an incomplete product. We value your input, so we are providing this to you so that you can send us your comments and ideas. We have tested this beta version extensively, but that doesn't mean that there won't be bugs. Use at your own risk.

Notes
  • Please backup your existing data from BC 3.1 before running the beta.
  • The beta build requires you to allow Garmin to collect statistics on how you use BaseCamp to help us improve the application. This will be optional for the release of BaseCamp 3.2, but it is a required condition for using the beta.
  • We know that routing (especially long routes) have issues. We are working on the issue.
  • Activity profiles are still a work in progress, in particular migrating existing routing options.
  • We have had intermittent success testing BirdsEye Select because of some oddities with the servers. Please let us know your experience.


Changes
  • Moved the various property tabs to a separate dialog
  • Added swapping the map and data list UI regions
  • Added activity profiles to allow easier changes between common routing configurations
  • Added geocache search integration with OpenCaching.com
  • Added photo sharing site upload (currently for Picasa)
  • Added track statistics that correspond to the selection in the track points list
  • Added additional statistics to the elevation profile
  • Added display of elevation profile when batch editing routes or tracks
  • Added heart rate and cadence to the track points list and elevation profile
  • Added route to track conversion
  • Added display mode for geocaches
  • Added the "Duplicate" menu item for most user data types
  • Added continuation of route/track drawing when switching between tools
  • Added route avoidance checkboxes to the route options (such as "Avoid U-turns")
  • Added a basic dialog for creating routes
  • Added draw order control for new BirdsEye Imagery that is downloaded
  • Added user selection of application language (the beta is English only, so this doesn't have much of an impact yet)
  • Added option to restore the application to default settings
  • Added tips dialog when entering full screen mode
  • Added a keyboard shortcut to snap the map back to North up
  • Added file import/export support for the TCX file format.
  • Added file export support for tab-delimited and comma-delimited text
  • Added properties and create waypoint commands to the list of POIs that is displayed when hovering on the map
  • Added optional collection of analytics to help us improve the application
  • Added display of the detailed coverage region of card/device based maps
  • Added notification to user when updates are available for devices
  • Added receiving FIT course points and activity data from many fitness devices. These are converted into waypoints and tracks.
  • Changed geotagging photos from a track to add links to those photos in the track
  • Changed to not allow changing the location of geocaches when they are part of a route
  • Changed the divide tool to create a new waypoint or trackpoint at the division point
  • Fixed issue where we didn't always remove all waypoints created as part of a route


Link
Download the beta here!

We've put a lot of hard work into the features for BaseCamp 3.2, we hope you'll enjoy it.
  • 0
    One issue I've had with the Edge 705 since I got about a year ago is it making errors navigating downloaded GPX files, mainly taking off-road shortcuts on a track that is supposed to be on-road, despite many trackpoints on the skipped road segments. I bought the City Navigator maps on SD card which precludes using MapSource to layout rides, so I figured this was due to using 3rd party websites with different map databases to create the gpx track files...like MapMyRide, GPSies, BikeRouteToaster, etc...

    So, I've been trying to do this with BC. I've had a number of difficulties trying to get BaseCamp to work (Garmin had to send me new SD card maps) but now have it basically working. The problem is, with these GPX files I get segments with doubled magenta courses displayed on the 705. Over these segments, one is on-road, and the other is an off-road shortcut. Also, I get notifications for every store, business, or address that happened to be near the points on map where I clicked in order to create the track.

    It appears that 3.2.0.1 will allow converting/saving it's GPX files as tracks rather than routes. Perhaps this will finally solve my problem?

    The saga continues...
  • Former Member
    0 Former Member
    Beta Feedback

    My complements to you on the changes to the display with the Beta. It is much improved.

    1. On the map, when a route is selected, the right-mouse should display New Waypoint, Insert, New Point, Erase, Divide.
    2. When a route is not selected. nearby POIs and map features should be displayed in a drop down list similar to MapSource, allowing for various functions also similar to MapSource such as Properties, Show on Map (centering, useful for Google Earth calls) and New Waypoint. BaseCamp does some of this, but with the first being a left-click. The >> selection is kind of funky, anywhere on the text of the dialog balloon would be better.
    3. MapSource also allows a left-click highlight on the map of a POI name, address and phone and a right-click copy that I can paste in an email or on a chat board to invite people to a POI. BaseCamp does not.
    4. Whether or not the rubberband is active for inserting a point, a right-click should present a list of very close POIs for selection and properties display. MapSource always displays Map points where the mouse is hovering. With the Zumo series, having Map Intersection via points is very important, as riders typically take the road less traveled and end up with many shaping points. We need the ability of assigning them to intersections so that they remain unflagged and unannounced on the device. That is where the hovering and right-click insert point via the rubberband is essential. We need to have the ability of zooming in/out while the insert rubberband is active so that we can identify the location of an intersection to shape the route. The BaseCamp Beta does this, but frequently drops the rubberband.
    5. BaseCamp needs Project Open and Project Save. When working on more than one ride, having to clear the slates to work on another ride, add in appropriate collections different from the previous work and add in the exported routes is time consuming and repeating each ride setup can be avoided.
    6. BaseCamp has the same lost index problem that MapSource has. When a map update is done, non-Waypoint via point indexes into the updated maps are not updated and throws GPS calculations for a loop. That's for every route via point of type Map Point, Map Line and Map Intersection.
    7. An improvement to both programs would be for the +/- zoom keyboard keys to center the map on the current cursor position, like the Magnifying tool does. While on a rubberband point insert, it would help zooming into the location of an intersection where the programs typically grab a POI instead. Right-click in this situation should present a list of close by POIs or map features for selection as the rubberband insert point.
    8. The unnamed box in the lower left that shows routes intermixed with Waypoints would be better organized similar to Google Earth, where different component lists can be selectively expanded/compressed.
    9. Waypoints should have properties shown in columns similar to MapSource, so the user can sort alphabetically or by symbol.
    10. Display the extended XML address extensions in the right-click properties of Waypoints.
    11. Faster Time algorithm needs work. It does not match my GPS with any setting of the preference slider. Chicago to NOLA varies by over 100 miles further and up to 3 hours slower than the GPS or MapSource.