Related

BaseCamp 3.3.0.2 Beta is available

Former Member
Former Member over 13 years ago
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 over 13 years ago
    Thanks guys for reporting the Zumo issues, we are looking into this and we are making good progress.
  • Former Member
    0 Former Member over 13 years ago
    One of the users over on zumoforums provided a route that was acting strange on his Z550. Each time he sent it from BC and imported it, the end point and possibly all 4 intermediate waypoints were not present in the route, though the distance and map of the route looked good.

    I had difficulty repeating it, but discovered that if I changed the 4 waypoints to shaping points, the imported route looked like his. But then in BC, I changed the 4 waypoints back to display as normal. The Z550 imported route would still not display them or the endpoint.

    Finally I exported the list to a gpx and opened it with MapSource, sent it to the Z550 and the import of the route showed the 4 waypoints and endpoint as it should.

    My theory is that the route <extensions> starts by resetting the subclass with
    <gpxx:Subclass>000000000000FFFFFFFFFFFFFFFFFFFFFFFF</gpxx:Subclass>
    that may be a requirement on certain devices, but missing from the BC gpx.

    The attached Waypoint Route.gpx is an export from BC. The attached Waypoint Route_MS.gpx is a Save As from MapSource after opening the BC Waypoint Route.gpx. Both files in the attached zip. Compare the two gpx files and you'll see the differences between one that works (MS) and one that doesn't (BC) for the same route.

    Update:
    I edited in the above XML expression to the BC gpx file that doesn't work right to the <rtept> <extensions> for each of the 6 total waypoints in the <rte> and the BC gpx now displays the flags and edit of the add/remove for the route in my Z550 shows them again as should be.

    Summary:
    While switching a waypoint to a shaping point and back to not a shaping point seems to have caused this behavior, possibly by a software switch not being reset, this is probably a glitch when using the insert route point ends up on an intersection and the user resets the automatic set to a shaping point.


    Thanks for taking the time and investigating this. You are absolutely correct about the missing subclass being the problem here.

    That messes up the Zumo 4xx and 5xx. We put in that change to address an issue with the 6xx which doesn't like the invalid subclass (all 0s and Fs is not a valid subclass), but weren't aware of the fall-out for the older devices.

    So we'll revert the change, and there will have to be a device firmware fix to address the 6xx issue.
  • Former Member
    0 Former Member over 13 years ago
    Z665 ok

    I sent the MS version with the null subclass to my Z665 and did not have any trouble.

    I don't envy the task development has with the multiplicity of devices, exceptions and the like. We end-users do appreciate the work you all do supporting our favorite devices.
  • Former Member
    0 Former Member over 13 years ago
    Developers Listening..

    Yes, we certainly don't envy the complexity. I used to be an application developer, specification and test, and can't imagine the conflicts your programs deal with each execution.

    As I user now, I don't care. I just want my Maypo! :)
  • Former Member
    0 Former Member over 13 years ago
    Problem sending routes to Zumo 550

    Thanks guys for reporting the Zumo issues, we are looking into this and we are making good progress.


    Falagar,

    I love my Zumo 550, and have had nothing but the absolute best experience with customer service, or tech support, on the few times I've had problems.

    Not to mention how well my 550 has performed on my many trips, rain or shine!

    I would NEVER switch to another brand of GPS.

    And I repeat these comments to other potential, or current, GPS users, whenever I get a chance.

    I am completely confident the people at Garmin will resolve the current problem with the 550 soon.

    Thanks so much,
    Don
  • Former Member
    0 Former Member over 13 years ago
    Garmin XML

    [Deleted my unlearned question]

    Is it possible to get a breakdown of the gpxx:Subclass fields? I've got a comparison of an identical BC and MS route and am trying to resolve why there are a few different nibbles.
  • Former Member
    0 Former Member over 13 years ago
    It's somewhat strange that there are two end expression delimiters in a route I'm examining, i.e.,
    <gpxx:RoutePointExtension /> in BaseCamp
    </gpxx:RoutePointExtension> in MapSource

    Is the BC one legal?

    Is it possible to get a breakdown of the gpxx:Subclass fields? I've got a comparison of an identical BC and MS route and am trying to resolve why there are a few different nibbles.


    Are you saying the BaseCamp v3.3.0.2 created a Route with the GPX shown? It's been quite a while since I wrote XML but looking at the Garmin XSD would tell me that is NOT a valid delimiter for a Type. The "/>" expression is the delimiter for a single expression like:

    <gpxx:rpt lat="47.827177047729492" lon="-119.95945930480957" />


    Did that GPX file actually work in BaseCamp or on a GPS?

    Cheers,
  • Former Member
    0 Former Member over 13 years ago
    My ignorance. MS did have an expression, BC did not. XML was legal and I learned something.
  • Former Member
    0 Former Member over 13 years ago
    Feature Request - Center map on cursor

    I'm not sure if this is the correct place to ask this question.

    Is there a way to center the map on the cursor in BC?

    I know about the check box in the Route Properties.

    What I would like is to be able to left click the cursor, particulalry when using the Zoom Tool, and have the map centered on that point.

    Street Atlas does this, and it's extremely helpful.

    Merry Christmas!

    Don
  • Former Member
    0 Former Member over 13 years ago
    • Fixed issues with sending routes to the zumo.

    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