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
    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".


    I am afraid I do not quite understand your question. What do you mean by steps? Can you maybe provide a screenshot to demonstrate the issue?

    Thanks!
  • 0
    Can't route stairs

    What do you mean by steps?


    Sorry, the right word is stairs! Here attached is an image of it!
  • Former Member
    0 Former Member
    This is probably a map issue, the stairs are most likely not set up with the right properties on the map.
  • Former Member
    0 Former Member
    Basecamp Epiphany

    Working in Basecamp this evening I had an epiphany.....

    Previously it was mentioned that no warning is provided when deleting waypoints. (And also that the undo function is there throughout the session to restore mistakes.)

    But.... Why then is there no "Recycle Bin" feature in Basecamp?
    That way, deleted files would always be recoverable without the annoyances of confirming deletes!

    Until items are manually removed from the "Recycle Bin" they could remain here along with deletion dates, "sort-able" like in the other lists. (and still be recoverable & "showable" on the map!) ;)

    Without the ability to show/hide, and lock/unlock folders & lists, complex data sets can be difficult to maintain and work with. And it's literally impossible to keep tabs on all the data to ensure you haven't removed (or changed) anything by accident.

    The one beautiful thing regarding Basecamp is it's apparent ability to efficiently work with large data sets. Between imported KMZ area overlays (enclosed tracks) POI data, and my own data I literally have nearly 18,000 individual data points being maintained within Basecamp. Basecamp is still quite fast too! (Even with 3d topo and BirdsEye imagery enabled!) ~ A testament to the software's core design!

    Prior to version 3.3 I never would have attempted this! (particularly without folder nesting for organization!) ~ Congratulations to the software engineers (Mike?) for a stable, powerful, and user friendly tool! Thank you!

    Basecamp has now become my "Go-To" software, and Google Earth has become a tool for conversion. "3.2 to 3.3 provides a significant improvement in usability. I'm almost scared to think about what a full point revision consists of!" IMHO, the only advantage Earth still maintains is the ability to show different "timeline satellite imagery." (winter/summer/fall imagery that shows transition lines, tree types from foliage colors - things you won't see with the existing BirdsEye imagery)

    Here's a tip for everyone: Regarding enclosed tracks (shaded overlays in google earth that I have exported to KMZ files and then imported into Basecamp) ~ This is a great alternative/"workaround" to converting data to .IMG files for display within Basecamp. (since only one .img/map file can be displayed at a time on Basecamp) Using this approach, you can see everything at once. Just don't try to send/export these huge data sets to your GPS. (Your GPS will not be able to deal with these massive data sets when exported/converted to .GPX files. ~ For this, you will still need to find a way to convert the data to an .IMG file! ;)

    PS: It's very nice to be able to "bulk change" colors on these tracks for "differentiation." (When imported, these KMZ files appear as "closed loop tracks") But it would be a nice enhancement to be able to select an entire list and lightly shade any/all enclosed regions ("closed loop tracks"), and/or fill all items with "color select-able banding." ~ Some of the data I have imported (nature conservancy overlays for example) are very complex and it's hard to tell which portions of the map are "in", and which portions are "out." (regions within areas are actually exceptions, not inclusions so I see "polygons inside of polygons" ~ shading/banding would show these "omission areas" areas as "un-shaded/un-banded exceptions")
  • 0
    Display "Symbol & comment" for Waypoints

    Since the waypoints must have unique names in BC, it is good that there is an option to display "symbol and comment" instead of "symbol and name". With my new eTrex, it is also possible to type and modify the comment (or "note"). Unfortunately, there is no option to display "symbol and comment" instead of "symbol and name" on the eTrex. I must click the waypoint to see the "note". This is not a BC issue, but could the BC developers insist that the devices offer the same options as BC?
  • 0
    send track alone to GPS unit

    When I send a track alone to my Garmin eTrex30, it does not appear in the list of tracks of the unit. When I send the same track included in a list of BC collection, it appears, with the right name of the track...

    (OTOH, when I send only a waypoint, it appears on the unit.)
  • 0
    lists also on the GPS units ?

    Since BC uses lists in its collection, couldn't the GPS devices like the eTrex30 also display their "all data" in lists? (That is, could BC display them in lists when the device is connected via USB?) Since we sent these data as lists, I suppose that the unit keeps record of the fact that some tracks and waypoints belong to the same list (the same GPX file if this format is used internally?).

    When I update a hike on my PC, it is indeed difficult to update it on my eTrex (connected via USB), since I cannot select easily all the data belonging to this hike, while I can do it easily from BC "collection". For example, I cannot easily delete from the unit waypoints that I have renamed or suppressed. Is this a BC or a device issue? Could BC display "all data" in lists, even if the unit does not? Has BC the necessary info to tell to which list each waypoint belongs? If not, could the units adopt the way BC organizes data?!

    It is all the more important since the units now have huge internal memory, so that we can keep many hikes on them, instead of deleting everything each time and sending only one hike at a time to the unit...
    If we have only tracks, it is clear on the unit, but if the tracks are complemented by waypoints, it is the same mess as BC without lists...
  • Former Member
    0 Former Member
    When I send a track alone to my Garmin eTrex30, it does not appear in the list of tracks of the unit. When I send the same track included in a list of BC collection, it appears, with the right name of the track...

    (OTOH, when I send only a waypoint, it appears on the unit.)


    We'll investigate.
  • Former Member
    0 Former Member
    Since BC uses lists in its collection, couldn't the GPS devices like the eTrex30 also display their "all data" in lists? (That is, could BC display them in lists when the device is connected via USB?) Since we sent these data as lists, I suppose that the unit keeps record of the fact that some tracks and waypoints belong to the same list (the same GPX file if this format is used internally?).

    When I update a hike on my PC, it is indeed difficult to update it on my eTrex (connected via USB), since I cannot select easily all the data belonging to this hike, while I can do it easily from BC "collection". For example, I cannot easily delete from the unit waypoints that I have renamed or suppressed. Is this a BC or a device issue? Could BC display "all data" in lists, even if the unit does not? Has BC the necessary info to tell to which list each waypoint belongs? If not, could the units adopt the way BC organizes data?!

    It is all the more important since the units now have huge internal memory, so that we can keep many hikes on them, instead of deleting everything each time and sending only one hike at a time to the unit...
    If we have only tracks, it is clear on the unit, but if the tracks are complemented by waypoints, it is the same mess as BC without lists...


    The units use a different format internally, and currently have no list support. We only write out the lists each waypoint belongs to, in form of categories. I believe there is something in the works to allow units to easier categorize user data.
  • Former Member
    0 Former Member
    GUI Refinements

    Two minor GUI issues: "(I wish I could find more to complain about ~ although direct .IMG import sure would be a nice touch!)" :D

    (The second issue is introduced as a result of the new nested folders feature.) It actually becomes more irritating as data sets grow. (Particularly the more you organize the map configuration/display with nested folders.)

    1.)
    When selecting a waypoint (item) from the map, the waypoint list is scrolling to display the approximate location of the waypoint. (where it is located within the list.) But the (map selected) waypoint does not get highlighted. (If you select the item from within the list, it does become highlighted.)

    Maybe this is not "feasible" due to the data filters located below the list? (It does however display in the filter entry box.)

    2.)
    When clicking on the + and - (folders), folder behavior is a bit odd (and CPU/time consuming) for a windows application. (IMHO)

    I frequently find myself viewing nested folders by clicking on the + and minus (beside the folder) expecting only to expand the folders without viewing all the underlying data (on the map). But doing this always results in not only expanding/contracting the folder, but also changing the view of what you see in the map....

    This may seem like a minor thing, butif you have a lot of waypoints (within nested folders) and you're browsing the folder layout searching for a list..... A lot of CPU/time is wasted waiting for the map display to update and display the containers entire contents. (something you don't necessarily want to view.)

    This behavior (moving to that folder's view) "makes sense" when double clicking on the folder, but not when clicking on the + or -.

    IMHO, merely clicking on the + or - should only expand/contract the specific folder, and not change the map view. As a "seasoned windows user" I would expect the following behavior to occur:

    Clicking on +/- should only expand/contract folder/subfolders. (not change map view as it does now.)
    Double-clicking should expands / contracts & changes to that view displaying all sub folders & lists etc.
    Expand all/Contract all options added to right click (alt menu) when focus is on folder.

    I am pleased that the folder display remains persistent after closing and re-launching Basecamp!:)