Duplicate logs....to correct or not correct, that is the question.
You find through project-gc that you've accidentally logged the same cache twice, since you did some power caching and cut and paste logging. The find count is probably the same, and you would have to slog through big lists of probably archived caches to find your errors.
- #1 My choice to be scrupulously honest has me going through and making the corrections.
- #2 My choice to figure it was an honest mistake and the total finds aren't going to change has me use my time for other things.
- #3 Seriously? You're even wanting me to think about this?????? ;)
This topic contains 7 replies, has 8 voices, and was last updated by 
The Happy Hodag! 5 years, 11 months ago.
-
Posts
-
So I became aware of the concept of “bad logs” viewing another forum. I looked at ours on project gc and found a few duplicate logs, probably less than 10. Some I knew…the cache owner allowed additional logs for one reason or another and we took them. We don’t do that anymore, even before gc made it impossible to do so, but it was part of our caching history so we didn’t change them. I did find one duplicate for no known reason and removed it. The other few that remain are probably mistakes on some of the few power trails we’ve done in the past, where there were…gasp!…cut and paste logs that probably missed the cache before or after the doubled one. I’m probably going to let those slide, since the count total is likely the same anyway, and risk being tagged as a “geocheater.” So….making a poll here….what would you do with these?
I don’t worry about it. It probably makes up for ones that I missing logging…I’m sure there are more than a few.
Oconto...the birthplace of western civilization:)
If a cache owner were to contact me about a duplicate log or wondering why I logged every cache before and after it on a power trail, but not that one, I would rectify the issue both in official logging and with an e-mail to the owner saying it was an honest mistake but that I fixed it. Otherwise, so many other priorities in life, I wouldn’t seek out one more thing to do.
Using the app for over 99% of my caches, it’s been fairly obvious if I missed a cache. Having the filter set to hide found caches from view, I haven’t had this problem. I have a lot of problems with the app as it has evolved and like it less now than when it first came out, but this feature is nice.
The best sig is no sig.
I tend to be rather meticulous about logging caches, so I don’t worry about this, but I did find that I had double-logged a cache once, and removed the extra log. I marked answer #1, but in truth my answer would really be closer to 1.5, “This matters to me, but I just don’t make mistakes in the first place so I don’t worry about it.” 🙂
All opinions, comments, and useless drivel I post are mine alone and do not reflect the opinions of the WGA BOD.
Using a free program called “Cachestats,” I found and subsequently removed unintentional duplicate logs long ago. However, back in the earlier days of geocaching, when duplicate logs were done and even expected for certain kinds of caches, we earned those duplicate logs, and haven’t bothered deleting them. It’s only a few, and has been a non-issue for us.
I have deleted duplicated logs of my own before. And BigJim, thanks for putting a smile on my face.
The views expressed here are that of myself only and do not necessarily represent that of the WGA board.
I generally use GSAK for all my logging now, so logging hasn’t been an issue. Even when logging through the website, they’ve had the smiley icon by the “Log This Cache” button for quite a few years on caches you’ve already found.
The buck stops here. . .and gets entered into Where's George.
Where's George? Stimulating the economy one EMS'ed dollar at a time.
You must be logged in to reply to this topic.