[Appropriate use or abuse of NM/NA logs?]

Yes. There are very few things worth worrying about in this game. I would recommend posting the log type that you feel appropriate at the time, and move on with your life. If it gets fixed as a result of your log, that's a good thing. If it doesn't, it's not the end of the world as we know it. In the end, it's just another goobered up cache.

Thanks all for the feedback. Seems like there is not universal agreement on this, so I'm going to take Clan Riffster's advice and log 'em as I see 'em, then move along.

[Appropriate use or abuse of NM/NA logs?]

I agree with most of your definitions of NM. I disagree with the 2 about insects.

 

Thanks Ike--

 

Just a clarification, the 2 NMs I did for insects were

1). Stinging insects where I was unable to replace the cache as found and wanted the CO to know

2). Great night cache where I enjoyed the hike/layout, but the cache itself was laying open and had become infested (hundreds of baby spiders inside, among other things)

 

Sounds like a note to the owner as opposed to NM could have been a better way to go.

 

Your NA on GC1ET7N is completely unjustified. The cache has not been MIA for over a year. There is an enabled listing log in August of this year. Just because there have been a few DNFs since then does not mean it's MIA. A note asking the owner to double check it might be appropriate. Even a NM could be argued. But NA does not make sense for that cache.

 

The NA on GC138GJ is just ridiculous. That cache is being actively found, including found by you. If spiders and mice are reasons to archive caches, then you will be busy posting a lot more NA logs.

 

Appreciate the advice GeoBain--

 

To clarify, it wasn't the mice/spiders that bothered me, but that the cache had obviously fallen into disrepair and was no longer being actively maintained (last CO login in 2007). I thought caches not being properly maintained was a good reason to archive it (but that's why I wrote this post, 'cause I wasn't sure).

 

That GC1ET7N having 15 DNFs in a row on a 1.5/1 made me think that maybe it should no longer be listed, but I guess that is more of a reason to ignore the cache than NA it.

 

Again, thanks for the guidance.

[Appropriate use or abuse of NM/NA logs?]

I know this has been discussed before, and I've read the archives, but this doesn't make me feel better as a human being.

 

It feels like I post more "Needs Maintenance" logs than other cachers. I have posted NM logs when the cache:

-log is too full to sign

-log is too wet to sign

-container is broken

-coords are obviously wrong (e.g. in the middle of a lake on a terrain 2)

-is hidden in a recess with stinging insects

-inhabited itself by insects

-(but never because I didn't like a cache)

 

I've also posted "needs archived" logs for 3 out of about 200 caches. But on 2 of those 3, I've been shot down. The other one is going ignored (GCHTB5, GC1ET79, and GC138GJ)

 

I post DNFs on any cache that hasn't been found in at least 2 weeks that I also do not find (if it was logged as found the same day, I don't bother, as I know it was just me).

 

Is life too short to worry about posting these NM/NA/DNF logs? Am I doing it wrong? I feel more like a jerk than a helpful person. I appreciate advice from others who have more experience with this than me.

[San Diego Teacher looking for help]

There is a teacher's curriculum that goes along with a GPS museum exhibit, which has activities appropriate for several grade levels:

 

GPS Adventures Guide for Teachers and Students

[Finding one cache]

Wasn't caching last time we were in Switzerland: GC1DDQ5

[Turning a rare mistake geocoin into TB to be discovered?]

Here is the result (you can see the travel bug page here)

 

My first attempt at wire wrapping, so we'll see how well it holds up.

 

[Turning a rare mistake geocoin into TB to be discovered?]

I'd always be interested in seeing this kind of geocoin. I have to admit that I don't log every travel bug as discovered - only those that have a special story/shape/mission. If you add good photos of your coin to the travel bug page, I would definitely appreciate logging it, as it would be a way for me to see the coin a 2nd time, and I could go back to the TB page if I wanted to study it again.

 

Thanks everyone for the helpful advice. I will make the error coin a trackable TB with a good page so others can log it at events. But not going to release it into the wild.

issueperson

[Turning a rare mistake geocoin into TB to be discovered?]

I'm new to the geocoin community and have a question about a mistake geocoin.

 

I've legitimately acquired a rare mistake geocoin. The creator has allowed me to keep the coin. I will not be releasing the coin, as it would likely go missing.

 

The coin is not trackable. It was a mistake coin and the tracking number was scratched out.

 

If you had the chance to see a rare coin at an event, but it was not trackable, would you be interested? What if the coin were attached as a backpacker to a travel bug, so that it could be logged as discovered that way? It obviously wouldn't have the geocoin icon or be an official find of the released LE coin.

 

Thanks for helping out a trackables newbie.

issueperson