Bug on cache logs

Former Member over 15 years ago

Running BC 3.0.5

When pulling in caches from geocaching.com (using the PQ function) if the cache log contains a 'couldn't find' any log entry at this point and later is not displayed. I can reproduce over and over.

I tested pulling the same GPX file into GSAK and all the logs are displayed.

My guess is BC is choking on anything but a 'found' log entry.

Z

0 Former Member over 15 years ago

Thanks for reporting this issue.

Can you please post the .gpx file?

0 Former Member over 15 years ago

We're not able to reproduce the problem.

If any other geocache user experience similar issue, please let us know.

0 Former Member over 15 years ago

Ok, so I was a little taken back that you guys didn't see the issue and now that I've owned it for a little over two months, I have narrowed the issue down.

Roughly, the same issue/bug but I at least know a workaround. These are the steps in case I'm doing something wrong.

1) Load up an old pocket query or GPX file in basecamp.
2) Transfer to 550 memory card
3) Obtain a NEWER pocket query or GPX file of a cache (newer in the sense the cache has newer log entries then step #1)
4) Transfer to 550 memory card

The newer cache (step#3) does NOT overwrite the old (step#1) cache. The workaround is to delete the cache first then transfer, which seems dumb. If I'm importing caches to a list in my collection it should be smart enough to look at the date stamp and overwrite an old cache with a newer one of the same name (which in turn will update the logs). Instead it sees the cache is there, and skips it.

In the nutshell I get a Pocket query every other day for the same 500 closest caches. I import that file into basecamp, and copy all those caches to my 'Geocache' list under my library. Now when I do the same thing a day later the newer caches do not overwrite the old ones, so I see the OLD cache logs.

0 Former Member over 15 years ago

Thanks for troubleshooting the problem. I can confirm the behavior you described.

Unfortunately, overwriting is not always the desired behavior. For example, if I want to import an older pocket query to see what was the state of the cache in 2007, I want to be able to import and view it in BC without screwing with the latest one.

Ideally, BC would prompt you to overwrite, rename or ignore when it detects duplicate items, which is something we would like to support in a future version of BC.