+hukilaulau Posted February 24, 2009 Share Posted February 24, 2009 GSAK lists 1912 caches in my finds. profile says I have 1913 logs. Apparently I logged a cache twice. How do I find it? Help! I can't sleep til I resolve this! Quote Link to comment
+ScoutingWV Posted February 24, 2009 Share Posted February 24, 2009 There are several options. You could go to the pocket queries, run the "My finds" query, send that file to itsnotaboutthenumbers.com, then review the results. Or you could sort them in GSAK or some other cache app ... Quote Link to comment
+WatchDog2020 Posted February 24, 2009 Share Posted February 24, 2009 (edited) You could do Pocket Query's and open them in Excel. Sort by cache ID and look for the that is listed twice. Since you have so many finds you would have to do a couple of Pocket Query's with differnt values since you are only allowed 999 results. Edited February 24, 2009 by WatchDog2020 Quote Link to comment
+hukilaulau Posted February 24, 2009 Author Share Posted February 24, 2009 The trouble with working it out in GSAK is that it is only showing 1912 (all caches) but says the count is 1913. When I run the findstats macro it says "1913 logs on 1912 distinct caches." Quote Link to comment
+sbell111 Posted February 24, 2009 Share Posted February 24, 2009 INATN is probably the easiest solution. Quote Link to comment
+OienLabs Posted February 24, 2009 Share Posted February 24, 2009 Get the "My finds" query. Make a new empty database in GSAK. Drop the "My finds" gpx in that database. Then in GSAK set filter, logs, Required logs greater than or equal to 2. Should do the trick. Quote Link to comment
+hukilaulau Posted February 24, 2009 Author Share Posted February 24, 2009 ITATN weeded out the culprit! (Well, the culprit was me I guess.) Thanks! Quote Link to comment
Mushtang Posted February 24, 2009 Share Posted February 24, 2009 Since you have so many finds you would have to do a couple of Pocket Querys with different values since you are only allowed 999 results. I can think of at least 2 things wrong with this post. Quote Link to comment
+uxorious Posted February 24, 2009 Share Posted February 24, 2009 Or you could wait a while. Someone is bound to notice that you logged a cache twice, and come here to complain about it. Then you will know which one it is. Quote Link to comment
+Vinny & Sue Team Posted February 24, 2009 Share Posted February 24, 2009 Could you, and would you please advise me of the waypoint ID of the cache in question, and would you please leave your accidental double find in place for at least a week so that I may forthwith start a thread about how enraged I am that people log multiple finds, and wherein I will advocate the death penalty, or at least life in prison at hard labor, as punishment for committing this most horrid of offenses? Thank you for doing the needful! . Quote Link to comment
Clan Riffster Posted February 24, 2009 Share Posted February 24, 2009 I may forthwith start a thread about how enraged I am that people log multiple finds Weird! Our thoughts on this are eerily similar. It appears almost as if an occult hand had reached down from above and copy/pasted your "outrage" to my feeble grey matter in an attempt to disrupt the geocaching space/time continuum. Quote Link to comment
+Jeepster++ Posted February 24, 2009 Share Posted February 24, 2009 (edited) The trouble with working it out in GSAK is that it is only showing 1912 (all caches) but says the count is 1913. When I run the findstats macro it says "1913 logs on 1912 distinct caches." To find the extra log using GSAK you can set filter. (Thanks Clyde!) Edited February 24, 2009 by Jeepster++ Quote Link to comment
+briansnat Posted February 25, 2009 Share Posted February 25, 2009 ITATN weeded out the culprit! (Well, the culprit was me I guess.) Thanks! Numbers padder! Quote Link to comment
AZcachemeister Posted February 25, 2009 Share Posted February 25, 2009 ITATN weeded out the culprit! (Well, the culprit was me I guess.) Thanks! Numbers padder! We are only allowed to do that on events with temp caches... 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.