Related

BaseCamp 4.0.0.5 is released

Former Member
Former Member over 12 years ago
We are releasing another public Beta of 4.0. This release contains a bunch of bug fixes and a few added features.

You should be able to update from within 4.0.0.4. Or download it directly at http://developer.garmin.com/apps/BC/BaseCamp_4.0.0.0_Beta.exe.

If you had trouble updating from 4.0.0.4 to 4.0.0.5 please use the download link, don't update from within BaseCamp.

Please give it a spin, report any errors and leave feedback here or via feedback option within BaseCamp. Thanks!

The What is new in BaseCamp 4.0? Thread still applies. Adventures are still the focus of this release.

We disabled the 'Unlisted Data' list for now till we get it working correctly.

A long-standing issue with shopping card POIs showing up on the map even if users turned of the display of points has been fixed.

You can now import into folders and lists (before we would always create a new list in My Collection).


Full change list:

Added ability to import into folders and lists (and not always import into My Collection).
Added ability to archive/un-archive adventures.
Added header for the folder data list.
Added easy way to display elevation profile from adventure.
Added ability to duplicate geotagged photos.
Added link the BaseCamp license agreement in help menu.
Added info icon for adventures in folder list.
Added ability to undo/redo on supported devices.
Added ability to drag and drop folders with BaseCamp data from the file system.
Added ability to accept Google Maps coordinate format when centering map at position.
Added new dog icons.
Added more information to adventure find results.
Added ability to permanently hide the adventure group.
Changed the simple route dialog to transition into the route properties so the route can edited further.
Don't let scroll-wheel change detail setting after changing setting.
Made sure waypoint creation date is visible by default in the waypoint properties dialog.
Fixed an issue where turning off the display of points would leave a lot of "shopping cart" POIs on the map for certain map products.
Fixed an issue where the selection was lost when left-clicking on the map with the hand tool.
Fixed issues where BaseCamp erroneously allowed you to create waypoints and would crash.
Fixed issues with route/track creation and joining.
Fixed issues with deleting data on devices.
Fixed issues with creating routes from tracks.
Fixed transfer of waypoint categories to device.
Fixed issue when BirdsEye selection box was dragged too far North.
Fixed issue with displaying custom maps on devices.
Fixed various adventure issues.
Removed Unlisted Data list (it will be back).
  • Former Member
    0 Former Member over 12 years ago
    Invert Route crashes Basecamp

    I just noticed that inverting a route crashes Basecamp beta. It works OK in v3.3.3
  • Former Member
    0 Former Member over 12 years ago
    I just noticed that inverting a route crashes Basecamp beta. It works OK in v3.3.3


    Did you send in the error report for it? So I can try to track down what happened?

    Does this happen for any route? I don't seem to be able to reproduce it.

    Can you attach a gpx file of that route and tell me which map you used.

    Thank you!
  • 0 over 12 years ago
    I'm testing my maps with BaseCamp, I'm looking at many free maps available on Internet, I'm viewing demo maps offered by Garmin. Every time I install new map on device / pendrive, action goes like this:





    Please make it reasonable. This should be a tool, not a FPS game.
  • Former Member
    0 Former Member over 12 years ago
    Careful with that Import

    There's a new feature with 4.0.0.5 Beta Import. If you have a List Folder selected, the Imported file will be a List in that List Folder.

    Use care, as if you have a List selected, Import will add the contents to that List. There is no indication that this happened, so if you don't notice it and exit, the undo function won't fix it and you could have a big task to remove that data. (I'd like to see a warning box before an import into an existing List.)
  • Former Member
    0 Former Member over 12 years ago
    Backups are Huge.

    I understand that the BaseCamp backups include almost everything in the c:\Users\%username%\AppData\Roaming\Garmin\BaseCamp\DataBase folder. It is twice as large as it would be if only one version of BaseCamp were installed. But the backup and the DataBase folder could potentially be much smaller.
    1. Why backup both my 3.3 and 4.0 folders? It seems that each BaseCamp version should only backup its own version.
    2. Why backup the AllData.gdb.bak and FolderData.gfi.bak files? That doubles the size of the backup.
    3. Why backup the TrackSegments folder that has increased in size from 13MB (vsn. 3.3) to 1.0 GB (vsn. 4.0)? Won't that folder be rebuilt as necessary? If that and the 1.2GB Thumbnails folders are working storage, when do they get cleaned up? Maybe they should be in a normal Temp folder so standard software utilities can recover space during normal system maintenance.
    4. Why isn't the GeotaggedPhotos folder backed up? I was under the impression that my Geotagged Photos remained at the location where I've stored them and that GeoTagging mods the EXIF of my original photos, not copies in GeotaggedPhotos folder. I had planned on all my photos being geotagged in BaseCamp and displayed from their original locations. Duplicating all those large photos would make this not feasible.
  • Former Member
    0 Former Member over 12 years ago
    I understand that the BaseCamp backups include almost everything in the c:\Users\%username%\AppData\Roaming\Garmin\BaseCamp\DataBase folder. It is twice as large as it would be if only one version of BaseCamp were installed. But the backup and the DataBase folder could potentially be much smaller.
    1. Why backup both my 3.3 and 4.0 folders? It seems that each BaseCamp version should only backup its own version.
    2. Why backup the AllData.gdb.bak and FolderData.gfi.bak files? That doubles the size of the backup.
    3. Why backup the TrackSegments folder that has increased in size from 13MB (vsn. 3.3) to 1.0 GB (vsn. 4.0)? Won't that folder be rebuilt as necessary? If that and the 1.2GB Thumbnails folders are working storage, when do they get cleaned up? Maybe they should be in a normal Temp folder so standard software utilities can recover space during normal system maintenance.
    4. Why isn't the GeotaggedPhotos folder backed up? I was under the impression that my Geotagged Photos remained at the location where I've stored them and that GeoTagging mods the EXIF of my original photos, not copies in GeotaggedPhotos folder. I had planned on all my photos being geotagged in BaseCamp and displayed from their original locations. Duplicating all those large photos would make this not feasible.


    These are all excellent observations. BaseCamp should be smarter when creating backups.

    1. & 2. Agreed.

    Regarding #3: The Track Segments file CANNOT be deleted. It contains information that cannot be regenerated. The information if the track segments files used to be in the gdb file directly. We moved it out so we could lazy-load track information. That was done as a performance measure and speeds up startup for people with lots of tracks. Like yourself. :) Still, 1 GB sounds like an awful lot. How many tracks do you have, and how many track points total?

    You also do not want to delete the thumbnails. But I do agree that those should be regenerated if they are missing. However, I don't think that is how it works currently. If they could be regenerated, I agree they should be in the temp folder (where e.g. the map tile cache already is).

    Regarding #4: BaseCamp does back up the geotagged photos that are located in the BaseCamp folder. When you geotag a photo (and import it into BaseCamp) the original photo is first geotagged and then copied BaseCamp's data folder. So that's definitely something to keep in mind.
  • Former Member
    0 Former Member over 12 years ago
    I'm testing my maps with BaseCamp, I'm looking at many free maps available on Internet, I'm viewing demo maps offered by Garmin. Every time I install new map on device / pendrive, action goes like this:

    Please make it reasonable. This should be a tool, not a FPS game.


    I hear you. I'll see what I can do. But that might not make it into 4.0.
  • Former Member
    0 Former Member over 12 years ago
    I am still having troubles with the "catch" or "lock" to roads issue when moving the via-points. It ends just were you leave it, I would prefer to have it locked to the road, each small movement can place the via-point just from left to right somewhere on the road, Can you just make it cetered?

    Another issue which is reported in Mapsource is still in Basecamp. ---> zumo 550 and quest are definiety affected by this. Sometimes when naviagting the display of the GPS displays all different (erroneous) lines when approaching a turn. This always happens at the same crossings, is reproducabe. This even happens when the route is recalculated when using the PC with same card material. This also happens with other (opentreetmap and ONROUTE card material) So it is NOT int he card material but inthe programs. The spurious lines disappear only of the route is recalculated in the device.
    NOTE: thiis is only visible at the GPS display, not at the desktop screen.

    In the old versions of Mapsource this is not the case. It is correct. What found is that the older MS versions use coordinates with less digits, the newer versions use more digits for coordinates. All versions with the big coordinates created the problems in the GPSses.

    gr Wim
  • Former Member
    0 Former Member over 12 years ago
    These are all excellent observations. BaseCamp should be smarter when creating backups.

    1. & 2. Agreed.

    Regarding #3: The Track Segments file CANNOT be deleted. It contains information that cannot be regenerated. The information in the track segments files used to be in the gdb file directly. We moved it out so we could lazy-load track information. That was done as a performance measure and speeds up startup for people with lots of tracks. Like yourself. :) Still, 1 GB sounds like an awful lot. How many tracks do you have, and how many track points total?

    You also do not want to delete the thumbnails. But I do agree that those should be regenerated if they are missing. However, I don't think that is how it works currently. If they could be regenerated, I agree they should be in the temp folder (where e.g. the map tile cache already is).

    Regarding #4: BaseCamp does back up the geotagged photos that are located in the BaseCamp folder. When you geotag a photo (and import it into BaseCamp) the original photo is first geotagged and then copied BaseCamp's data folder. So that's definitely something to keep in mind.


    #3, I've got 200 Tracks, 55K mi, 440K track points in BaseCamp.

    #4, I've got a BC backup and it only contains the data in \Database. \GeotaggedPhotos is at the same level as \Database and is not in the backup. That's probably a good thing, as from 3 weeks of riding, I've 1.3GB of photos there. \GeotaggedPhotos probably could use some design reflection.
    a)\GeotaggedPhotos are not in the BC backup, so restoring on another computer does not restore \GeotaggedPhotos.
    b) After a photo is geotagged and imported, moving photos to correct missing track segments, etc. are not reflected back in the original photos. Save As would work, but is very cumbersome.
    c) I've got 60GB of photos, many of which are geocoded. Copying even a portion of those to \GeotaggedPhotos does not seem a good way.
    d) Deleting a photo waypoint in BC does not delete the copy in \GeotaggedPhotos.
    e) Should BC be making smaller copies of my photos than the full jpeg size of 4288x2848 pixels (3MB) exclusively for \GeotaggedPhotos? I'd still want to see manual geotagging updates to reflect back to the original photos.

    What I'd like to see is to leave the photos in their original locations. The photo waypoints can just as well point to the original locations and repositioning a photo would be applied to the original as desired to maintain geotags. The user would need to recognize that another computer would also need the photo locations synced to view the photos. My photos are in the Picasa cloud, so changes recognized by Picasa would be reflected online if whatever date Picasa checks shows a BC updated date.
  • 0 over 12 years ago
    Suggestion to BaseCamp..

    I made this suggestion log time ago, but still is not implemented.

    When you send a map to a Garmin unit or a removable memory using MapInstall, the map is being sent using a unique name (gmapsupp.img)

    This causes two potential problems or annoyiances:
    1. The possibility of removing a previous map you already have saved..
    2. Or the need (in the newest Garmin units) to previously change the img's name kept already in the unit to avoid the annoying substitution of the map

    Since BaseCamp can recognize the GPS model you connect to you computer I am wondering why you don't let to choose the name of the map at the time of sending it to your GPS if that unit is compatible with names different to gmapsupp.img