Mark a cache as Not Found

I accidentally marked a cache as found (clicked on the icon in BaseCamp) and can't mark it not found. I see where all the data files are stored but haven't really dug into what the data bases represent. Is there a way - even "hacking" (technically that term is correct, but has such negative connotation because of main stream media, but I digress...) - to mark the cache as not found?

I've also considered just going to the spot and picking it (and a few others) up, but have been hiking elsewhere.
  • Former Member
    0 Former Member over 12 years ago
    We would like to allow un-finding GeoCaches again, but this won't happen in 4.0 unfortunately.

    "Un-finding" is very cumbersome right now. This is what I would do:

    1. Backup your data, so if anything goes wrong, you can go back to where you were.
    2. Export your data (that is not the same as backup). Be mindful that some data (BirdsEye, Custom Maps, GeoTagged photos) cannot be exported currently. But you might be able to backup those with a device.
    3. Exit BaseCamp. Blow away your data. You can do that by deleting %appdata%\Garmin\BaseCamp and all its subfolders. On my machine, that's C:\Users\falagar\AppData\Roaming\Garmin\BaseCamp.
    4. Start BaseCamp. Re-import your data.
    5. If anything went wrong, restore the backup.

    The found status is stored in AllData.gdb, but that's a binary format and therefore pretty difficult to hack. The steps above should work to remove the found status because exporting doesn't export the found status, and by importing into a new AllData.gdb you should start fresh with unfound caches.

    I freely admit that this is very inconvenient, I am just trying to give you some idea how to fix it. We definitely will allow un-finding in a future feature release.
  • Former Member
    0 Former Member over 12 years ago
    Thanks FALAGAR. I too accidentally set a cache to 'Found' and it was driving me crazy trying to set it back to 'UnFound'. Your method worked perfectly.
  • Former Member
    0 Former Member over 12 years ago
    Not sure if I should start a new thread or use this one as my problem is similar. I have a list of "Found" caches, but two of them have a "Closed Treasure Box" icon and the rest have "opened treasure box" icons. Can the closed icons be changed to open some way? Also using a GPX file to transfer, why did they get transferred into BC with incorrect icons? The properties plainly show "Found Dates". I thought I had read in another thread about this occurrence, but sadly cannot seem to relocate the thread.
  • Former Member
    0 Former Member over 12 years ago
    I did the same thing, clicked the icon and it marked the cache as found. But then I opened it's propreties, clicked to change the icon, changed it back to the unfound cache and that seems to have done the trick. Am I missing something important?
  • That doesn't work with geocaches. It's a known fault in BC, something hopefully that will be sorted sometime :confused:
  • Former Member
    0 Former Member over 12 years ago
    We would like to allow un-finding GeoCaches again, but this won't happen in 4.0 unfortunately.

    "Un-finding" is very cumbersome right now. This is what I would do:

    1. Backup your data, so if anything goes wrong, you can go back to where you were.
    2. Export your data (that is not the same as backup). Be mindful that some data (BirdsEye, Custom Maps, GeoTagged photos) cannot be exported currently. But you might be able to backup those with a device.
    3. Exit BaseCamp. Blow away your data. You can do that by deleting %appdata%\Garmin\BaseCamp and all its subfolders. On my machine, that's C:\Users\falagar\AppData\Roaming\Garmin\BaseCamp.
    4. Start BaseCamp. Re-import your data.
    5. If anything went wrong, restore the backup.

    The found status is stored in AllData.gdb, but that's a binary format and therefore pretty difficult to hack. The steps above should work to remove the found status because exporting doesn't export the found status, and by importing into a new AllData.gdb you should start fresh with unfound caches.

    I freely admit that this is very inconvenient, I am just trying to give you some idea how to fix it. We definitely will allow un-finding in a future feature release.


    I'm not sure if this is correct, but what I did...
    Closed BaseCamp.
    Moved AllData.gdb to another folder (in case I needed to restore it) so that it was no longer in the original folder.
    Renamed AllData.gdb.bak to AllData.gdb
    Restarted BaseCamp and the geocache now showed a closed treasure box. This may lose anything done since the .bak file was created. It may only work if the accidental "found" occurred during the most current BaseCamp session. Or would it lose only the founds done in the current session?

    Also, if one is using Windows7 and has the versions feature turned on, one might be able to rightclick on AllData.gdb, then select an older version that would have the correct icon. Any founds done since that version would have to be "re-found," though. Is that correct?
  • Former Member
    0 Former Member over 12 years ago
    Yeah, this might work.

    There is a potential for corrupting your data though (tracks and Geo-tagged photos come to mind first, there might be others). Track details and photos are not stored inside AllData.gdb so you might get a mis-match.

    Definitely back up your data before you mess with these files.

    If you use Win 8's File History (or the equivalent Win 7 feature) I would revert the entire %APPDATA%\Garmin\BaseCamp folder to an earlier version, not just AllData.gdb.
  • Former Member
    0 Former Member over 11 years ago
    I found another solution in another forum: On your device, select the geocache and start navigating to it. Then 'log your visit' as "did not find" This changes the icon on your device and when you connect to basecamp, it updates as well. Now I can sleep because my icons are correct! :)
  • Former Member
    0 Former Member over 11 years ago
    That doesn't work with geocaches. It's a known fault in BC, something hopefully that will be sorted sometime :confused:


    +1

    Un saludo.
    omortsoN