+K2D2 Posted March 5, 2010 Share Posted March 5, 2010 I'm logging caches this evening and noticed that the number of caches Geocaching.com says I have differs from my own count by one. I had just run FindStatsGen in GSAK, and the number it generated also differed by one. I have spent the past half hour painstakingly comparing the geocaching.com list with my list in GSAK, and also imported both lists into a spreadsheet and did a computerized compare. Sure enough, both lists are (in my case) 873 finds long... except, while GSAK counts them correctly, geocaching.com says I have 872. To be clear about this: it's not a matter of a missing cache; when I ask geocaching.com to show me the list of "all finds," it shows me 873 entries, all unique. But it counts them as 872. Anyone else having this problem? K2D2 Quote Link to comment
+baloo&bd Posted March 5, 2010 Share Posted March 5, 2010 (edited) I'm logging caches this evening and noticed that the number of caches Geocaching.com says I have differs from my own count by one. I had just run FindStatsGen in GSAK, and the number it generated also differed by one. I have spent the past half hour painstakingly comparing the geocaching.com list with my list in GSAK, and also imported both lists into a spreadsheet and did a computerized compare. Sure enough, both lists are (in my case) 873 finds long... except, while GSAK counts them correctly, geocaching.com says I have 872. To be clear about this: it's not a matter of a missing cache; when I ask geocaching.com to show me the list of "all finds," it shows me 873 entries, all unique. But it counts them as 872. Anyone else having this problem? K2D2 Just a thought. Run a MyFinds PQ, load in GSAK. Then make sure the FCOUNT column is activated in GSAK and sort on that column from largest to smallest. I am betting there is a "2" that will show up meaning there is a double log somewhere. Edited March 5, 2010 by baloo&bd Quote Link to comment
+Swamper68 Posted March 5, 2010 Share Posted March 5, 2010 I just looked at your profile and it says 873 like you quoted. 873 in your FindStats. 873 under your found geocaches on your profile. 873 on your last post of the last find you had. If you are talking about the stats bar only showing 872? Sometimes you have to give that a few minutes to update. If it doesn't update, since it is a generated image, hold down the shift key and click refresh on the browser page to reload the image. Does that help? Quote Link to comment
+K2D2 Posted March 15, 2010 Author Share Posted March 15, 2010 Finally found it! I went through again, with the help of an Excel spreadsheet, and compared GSAK's records with those of geocaching.com. Turns out it was one of my OWN caches that GSAK erroneously had recorded as having been found by me, which bumped up its total count by one. Not sure how that happened, but when I deleted that waypoint and re-downloaded the GPX file from geocaching.com to GSAK, the problem went away. My counts now match! Quote Link to comment
+Chrysalides Posted March 15, 2010 Share Posted March 15, 2010 (edited) Not directly related to your current issue (which you've already solved) but sort of related. One thing to note about GSAK, while it will add new logs to your DB, it cannot detect deleted logs from the DB. If you download a GPX and it contains log entry X, you add it to GSAK, and log entry X is subsequently deleted, it will remain in GSAK unless you delete all log entries for the cache and reload. What this means is that if you log a cache, download the GPX into GSAK, delete that log, then log it again, you're going to end up with 2 finds for that cache. Edited March 15, 2010 by Chrysalides Quote Link to comment
Keystone Posted March 15, 2010 Share Posted March 15, 2010 Since this turned out to be a GSAK issue I am moving it out of the website bugs forum. Quote Link to comment
+Walts Hunting Posted March 15, 2010 Share Posted March 15, 2010 You might want to check the logs for your cache. It is likely you logged a find when you wanted a note. It is not likely that GC returned a found on it unless you did log it. If you don't correct the original problem on the website then the next My Finds Query will bring it back. Quote Link to comment
+MorrisonHiker Posted September 28, 2010 Share Posted September 28, 2010 I've noticed a similar discrepancy with my cache counts for some time. Right now, Geocaching.com shows I have 346 finds. However, when I view the GPX file, there are only 345 finds. When I generate my stats on MyGeocachingProfile.com, it shows Total Caches 346 (345 distinct caches). Where is the other cache coming from? I believe when I first started caching that I accidentally logged a find twice...but I believe I later removed that found log. I've tried many times over the past few months to review the GPX file...but since I'm "short" a record, I don't know how I'm going to find what's missing. Any ideas? Quote Link to comment
+MorrisonHiker Posted September 28, 2010 Share Posted September 28, 2010 I did a little more checking and found that page 17 (of my 18 pages) only has 19 finds listed and the last page has 6. The 17th page should be showing 20 finds (20*17)+6 = 346. Looks like it's really only showing 20*16 + 19 + 6 = 345. I'm guessing I had an incorrect entry at one time...and now the counts are off...and the pagination is incorrect on that page. I guess I'll be reporting a bug to Groundspeak. Quote Link to comment
+ecanderson Posted September 28, 2010 Share Posted September 28, 2010 I've noticed a similar discrepancy with my cache counts for some time. Right now, Geocaching.com shows I have 346 finds. However, when I view the GPX file, there are only 345 finds. When I generate my stats on MyGeocachingProfile.com, it shows Total Caches 346 (345 distinct caches). Where is the other cache coming from? I believe when I first started caching that I accidentally logged a find twice...but I believe I later removed that found log. A double log is certainly the easiest way to get 345 unique caches but 346 finds. The GPX file isn't going to show the same cache twice, so you'd only see the 345 there. Quote Link to comment
+MorrisonHiker Posted September 29, 2010 Share Posted September 29, 2010 I finally found the duplicate entry. Instead of opening the GPX file as an XML document in Excel, I opened it as a read-only worksheet. This allowed me to see multiple entries for each cache location...and see the duplicate log. I removed it and that reduced my Found count. I'm chatted with Groundspeak and they are aware of the bug which prevents 20 caches from appearing at a time. A fix is on its way. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.