Logging DNF's
-
- 4500 or more caches found
- Posts: 706
- Joined: 20 March 04 10:34 pm
- Location: Melbourne
Logging DNF's
DNF (did not find) sounds simple but it appears some cachers have DNLNDF(do not log DNFÂ’s) phobias. Why? Hopefully the poll and this thread will help those who fear to log a DNF. To me a DNF is more important on my own caches than a find, it alerts me that there may be a problem with my cache and a cache maintenance check may be needed. I also have no problem in logging a cache I could not find, It helps others who may experience the same situation or circumstances at the cache, and at times it compliments the owner on a very good hide. Over to you...........................?
-
- 1250 or more geocaches found
- Posts: 482
- Joined: 17 March 05 9:29 pm
- Location: Dubbo, NSW
Sometimes we log a dnf. If we have had a good search, most definately. If it was hot, or we were rushing and didn't have a proper look, then we won't. If someone finds it straight after we didn't, we probably wouldn't log a dnf - how embarrassment! Some cache hunts have a funny story, if a dnf is accompanied by this we will definately log it.
Of course, sometimes we just clean forget that we even looked for it! If it's not in our field notes, it gets missed
However, as Mr Coffee suggested, a dnf can be an alert that something is amiss at GZ. It can also tell you that you've totally messed up the coords if it's the first log (been there done that).
Okay, short answer - sometimes we do, sometimes we don't, but it's more often that we do.
1st lady
Of course, sometimes we just clean forget that we even looked for it! If it's not in our field notes, it gets missed
However, as Mr Coffee suggested, a dnf can be an alert that something is amiss at GZ. It can also tell you that you've totally messed up the coords if it's the first log (been there done that).
Okay, short answer - sometimes we do, sometimes we don't, but it's more often that we do.
1st lady
- TeamAstro
- 5000 or more caches found
- Posts: 625
- Joined: 01 April 04 10:57 pm
- Location: Adelaide
- Contact:
Ah ha. My Fundamental Caching Law of Nature rule number 1. :
1. Don’t get too upset if you can’t find the cache if you are under pressure and in a rush. (still log a no find though – if I know I am in so much of a rush, I may refrain from looking even if it’s a drive by). Rushing never assists and normally results in a Bloke’s Look.
see the other thread.
clear skies, Astro.
1. Don’t get too upset if you can’t find the cache if you are under pressure and in a rush. (still log a no find though – if I know I am in so much of a rush, I may refrain from looking even if it’s a drive by). Rushing never assists and normally results in a Bloke’s Look.
see the other thread.
clear skies, Astro.
Double ditto! Caches logging no finds on our caches alert us to check them, 7-10 caches are there . But without logging dnf's our mantaince would not be right up there till to late!GIN51E wrote:If i didn't find the cache then i log a DNF simple as that. what do i have to hide?
Thanx to all that log no finds on our caches!
president & 1st lady wrote:Sometimes we log a dnf. If we have had a good search, most definately. If it was hot, or we were rushing and didn't have a proper look, then we won't.
president & 1st lady wrote:Some cache hunts have a funny story, if a dnf is accompanied by this we will definately log it.
dittopresident & 1st lady wrote:However, as Mr Coffee suggested, a dnf can be an alert that something is amiss at GZ. It can also tell you that you've totally messed up the coords if it's the first log (been there done that).
Okay, short answer - sometimes we do, sometimes we don't, but it's more often that we do.
- CraigRat
- 850 or more found!!!
- Posts: 7015
- Joined: 23 August 04 3:17 pm
- Twitter: CraigRat
- Facebook: http://facebook.com/CraigRat
- Location: Launceston, TAS
- Contact:
-
- 10000 or more caches found
- Posts: 1067
- Joined: 13 October 03 11:45 am
- Location: Travelling Australia using a Garmin Montana 650T
I voted sometimes - because If I am prevented from finding the cache because of muggles, pressures of time (blokes look), or some other reason that prevents me from having a good look then I don't bother.
On the other hand - if I have done a thorough job and am convinced that the cache is not there then I always log the DNF.
Comments by others in a log about "my third attempt at this one" don't faze me because there are many reasons for an abortive attempt on a cache.
On the other hand - if I have done a thorough job and am convinced that the cache is not there then I always log the DNF.
Comments by others in a log about "my third attempt at this one" don't faze me because there are many reasons for an abortive attempt on a cache.
- TeamAstro
- 5000 or more caches found
- Posts: 625
- Joined: 01 April 04 10:57 pm
- Location: Adelaide
- Contact:
Agree, if I get to "very near" GZ and it's, say, on an island in the Torrens (I think I said "Dam! Where's the kayak?") ...yep, I can see it but can't get to it, I won't log a no find ..well you have sort of found it but can't reach it. Maybe you POST A NOTE in that instance. Obviously, if you've had a look and can't find it, post a DNF. Can't see why you would not. Surely cachers don't get embarrassed about not finding a cache do they???ian-and-penny wrote: Comments by others in a log about "my third attempt at this one" don't faze me because there are many reasons for an abortive attempt on a cache.
clear skies, Astro.
Logging DNF's
All good arguments - We'll log all DNF's in future and indicate whether it was due to our tardy searching (and therefore not a problem with the cache) or give an indication that we did all we could to find it and failed (which may indicate a problem with the cache)
We always log our DNF's.
Besides alerting the cache owner that there may be an issue (most likely we didn't look hard enough ), but it helps us when our pocket queries are imported into GSAK. You can then run a filter on caches you have had DNF's with and revisit them at a later date.
When we find one of our DNF's, we edit the original log and add our "Found" text underneath it, change the date we found it, then flag it as Found.
Makes record keeping easy.
Besides alerting the cache owner that there may be an issue (most likely we didn't look hard enough ), but it helps us when our pocket queries are imported into GSAK. You can then run a filter on caches you have had DNF's with and revisit them at a later date.
When we find one of our DNF's, we edit the original log and add our "Found" text underneath it, change the date we found it, then flag it as Found.
Makes record keeping easy.
- Cached
- 2500 or more caches found
- Posts: 3087
- Joined: 24 March 04 4:32 pm
- Location: Launceston, Tasmania
- Contact:
I used to do this when I first started, only problem is the owner never sees your updated log or any indication that it has changed unless they happen to notice it on the cache page.When we find one of our DNF's, we edit the original log and add our "Found" text underneath it, change the date we found it, then flag it as Found.
Makes record keeping easy.