View Full Version : Differing Found Counts

05-12-2011, 07:54 PM
A quick question regarding found count on GSAK vs. what's listed on I've noticed that in GSAK, I have a total of 1078 finds, but when I go to, it says that I have 1076. I just did a pocket query of my finds, so I know that's up to date. The only difference that I can think of is that I have two caches that I found that I later adopted. Does take a cache out of your finds once you've adopted it. I know it's a little nit-picky, but my curiosity is getting the better of me.

05-12-2011, 07:59 PM
I have two that I have as founds that I subsequently adopted and that didn't impact the number of finds I had.

05-12-2011, 08:04 PM
I don't think they exclude them, does your finds PQ have the adopted caches in it?

The other day you were asking about duplicate logs on caches, does GSAK still have both logs in it's database?

05-12-2011, 08:05 PM
There's a column you can add in GSAK called "Found Count". It will show you found almost all you caches just once. There's got to be two that you've logged twice. you can scroll quickly down through, find the double logs, delete them and your counts will match.

05-12-2011, 10:14 PM
I went through the "Found Count" in GSAK and found one cache that had a count of 2. I deleted that cache and downloaded the most current "My Finds" PQ. That brought the counts to within one of each other. I just might delete all my finds and download the same PQ, but that seems a little extreme.

It's probably something that I mucked up somewhere along the line. Thanks for your help, everyone. I'll track this down sooner or later.

05-12-2011, 10:19 PM
And, once again, as soon as I posted the previous message, I went looking and found the cache that the CO deleted my log, but for some reason, GSAK was telling me that I had found it. I might have manually set that cache to "found" before the log was deleted, and the PQ wouldn't have updated the count find on that particular cache. So now, things are in sync.

Again, thank you everyone for your input. Maybe one of these days, I'll get the hang of this geocaching thing. ;)

05-13-2011, 02:41 AM
Glad you found the problem cache.

When you load a PQ vis GSAK, it loads all the logs it finds in the file. Every log has a "log id". If this log id exists in the database, the log is overwritten; if it does not exist the log is added to the database. Easy enough.

The problem comes in the fact that the PQs do not contain every log for a given cache. GSAK can't tell if a log has been deleted or has just not been included in the PQ. So all the old logs build up. Old logs stay in GSAK's database unless they are purged. Perhaps a better way to explain it is like this - suppose you kept a written diary of your caching adventures, using a page for each cache. You've found 100 caches, you've used 100 pages. If 10 people delete your logs online, your diary still has 100 pages of cache logs in it, but would report 90 finds. GSAK works much the same way.

If you don't keep any special data like notes or corrected coordinates in your finds database, the easiest fix is to delete the caches and reload the PQ. If you do keep special data in the database, you can use the Purge Logs option in GSAK's Database menu. Just set Purge logs to greater than to 0, and uncheck "always keep logs by me" as well as "Preserve last 4 logs column..." and all logs will be deleted. (

05-14-2011, 04:06 PM
Amazing the things GSAK will do if you know how to use it. ;)

05-14-2011, 08:34 PM
Do you log waymarks or benchmarks? That's why my gsak found score is very different from my found score.

05-14-2011, 11:04 PM
I don't go after waymarks or benchmarks, so I don't know how to answer that question.

05-15-2011, 06:07 AM
Do you log waymarks or benchmarks? That's why my gsak found score is very different from my found score.

That can be verified easily by filtering out those two cache types in the "Other" tab of GSAK's filter.