BaseCamp Geotagging changed in 3.1.2 - unfortunately

Former Member
Former Member
After upgrading to 3.1.2 I noticed the problem of viewing geotagged photos created as waypoints.
Double-clicking on the thumbnail in waypoint properties Microsoft Picture Manager DOES NOT SHOW the photo, instead it shows four icons called Alldata.gdb, Aldata.gdb.bak, FolderData.gfi and FolderData.gfi.bak.
Moreover during geotagging the BaseCamp now creates copies of all geotagged photos (no info on that in help, no possibility to select the folder in spite of the fact that the reason for creating copies is not clear) while still adding the georeference data into the exif of the original photos.
Opening such photo-waypoints in MapSource shows, that the link to the geotagged photo does not reference the original photo but its BaseCamp internal copy.
The problem is that the created link is wrong and therefore double-clicking thumbnail does not show the photo.
  • Former Member
    0 Former Member
    BaseCamp Geotagging changed in 3.1.2

    I want just to add that the AllData.gdb is not readable in BaseCamp anyway - the error message states Unsupported version. MapSource also cannot open this file with the similar error message referenced subsequent version.
  • Former Member
    0 Former Member
    Thanks for reporting the problem, we'll look into it.
  • Former Member
    0 Former Member
    Sample track with Geotagged Photos created as Waypoints

    Here I attach the sample track with geotagged photos created as waypoints.

    The original photos are saved in the folder
    E:\My Pictures\2011\2011-02-26 Zahorska Volkswagen Mlynska

    The waypoint links do not point to the original geotagged photos, instead they point to their copies on C disk. Geotagging next series of photos overwrites the content of this artifical folder and the photos cannot be opened.

    In the previous version the links pointed correctly to the original photos,
    so they could be retrieved and displayed any time.
  • Former Member
    0 Former Member
    Sorry for getting back to you so late on this.

    The behavior that BaseCamp 3.1.2 (and 3.1.3) creates a copy of the original image at C:\Users\Username\AppData\Roaming\GARMIN\BaseCamp\GeotaggedPhotos (or similiar) is working as intended.

    The change was made to make sure that a waypoint that was created as a GeoTagged picture "owns" a copy of the picture. So if you were to move your original picture the waypoint would still have a working link to a picture. We will delete this copy whenever you deleted the waypoint.

    Now, it looks like something is not working right for you if the path to the picture does not seem to work. We tried to reproduce the issue here in the office and had no luck. For us the path to the picture is correct and double-clicking the picture opens it in whatever picture viewer you have associated to the file type.

    So we'd like to find out what exactly is happening on your machine to produce this behavior.

    What happens if you.

    1. Use BaseCamp 3.1.3.
    2. Import a sample track that you use for geotagging.
    3. Geo-tag a folder of pictures (and create waypoints for them).
    4. Now, does double-clicking on the photo in a newly created waypoint work?
    5. If yes, close BaseCamp. Re-start BaseCamp and check again if double-clicking a photo works.

    If any of the above is still failing, I'd be interested in the following:

    1. Are there copies of any of the photos you just geo-tagged in C:\Users\Username\AppData\Roaming\GARMIN\BaseCamp\GeotaggedPhotos?
    2. If you export and open the new waypoints in MapSource what does it say for one of waypoints in the link?
  • Former Member
    0 Former Member
    Issue with Pictures

    I was reading the post on geotagging and noticed your statement:
    "For us the path to the picture is correct and double-clicking the picture opens it in whatever picture viewer you have associated to the file type"

    When I double click on one of the small pictures that is in BaseCamp, I do not get the picture to open in the associated program. All I get is a little larger pic next to it. It will not open in the program assigned to it.

    It does create the folder in BaseCamp like you mention and if you double click on any of the pics that have been geotagged, it opens in the assigned program. BUT not from within BaseCamp on the map.
    Ed
  • Former Member
    0 Former Member
    I was reading the post on geotagging and noticed your statement:
    "For us the path to the picture is correct and double-clicking the picture opens it in whatever picture viewer you have associated to the file type"

    When I double click on one of the small pictures that is in BaseCamp, I do not get the picture to open in the associated program. All I get is a little larger pic next to it. It will not open in the program assigned to it.

    It does create the folder in BaseCamp like you mention and if you double click on any of the pics that have been geotagged, it opens in the assigned program. BUT not from within BaseCamp on the map.
    Ed


    I apologize for wording that badly. I meant double-clicking on the photo when viewing the properties of that waypoint.
  • Former Member
    0 Former Member
    confused

    You comment : I meant double-clicking on the photo when viewing the properties of that waypoint. ?

    When I double click on the original pic in BaseCamp, it becomes a little bigger with the lat/long and name. Then when I double click on that picture - nothing happens. Are you saying it is suppose to open in the assigned program?

    It would be neat if it did open in the assigned program so you can see it.

    Ed
  • Former Member
    0 Former Member
    I attached a picture of BaseCamp 3.1.2 indicating where to double-click. It's not on the map display (double-clicking just selects it there) but from the properties.
  • Former Member
    0 Former Member
    ok - I understand but get an error message

    Totally understand now BUT when I do double click on the pic as you are suggesting, I get an error message.

    Attached is a screen capture of it. I did notice you are doing yours on a MAC, I am doing it on a Windows - XP Pro.

    If I go to the listed folder and double clip on the pic or any of them. They do work correctly.

    I am using BaseCamp 3.1.3
    Ed
  • Former Member
    0 Former Member
    Nope, I would never touch a Mac. ;) I definitely work on a PC.

    Does the image that the error message complains about exist? You'd have to use Windows Explorer (the file explorer, not the browser) to go to the location indicated in the error message and check if the file DSC01411.JPG exists and can be opened as an image.

    If it doesn't, then we might be on to something and there could be a bug in BaseCamp.

    If you wouldn't mind, could you repeat the steps that I outlined a few posts ago and let me know what you experience? That would be of great help to us.