DENelson83

Stable, yes. Bugless, no.

All we need now is support for the upcoming European Galileo SatNav system.

Just came across this on Garmin's blog: http://garmin.blogs.com/my_weblog/2014/01/garmin-introduces-gpsmap-64-series-updating-popular-outdoor-handheld.html Expands on the 62 series by pre-loading a quarter-million geocaches, adding more built-in memory, adding the ability to store 3000 more waypoints, and adding GLONASS reception.

Well, to be fair to the CO, it's entirely a possibility that the cache container is still in place and that the last person to find the cache, for whatever reason, failed to put the log back into the container.

And besides, you can't have another cache within 160 metres, so if you find a log sheet at the site of any particular cache, that's the cache the log sheet should belong to.

But I've been through this kind of scenario once, finding a log sheet without a container, and the CO accepted it as a find. If the log is signed, it should count as a find. (D'oh! Rhymes!)

Today, I was on my biggest cache hunt yet, finding over 20 caches in a single day. One of my hunts brought me to a site where all I found was a log sheet out in the open—just the log sheet, no container—and all other search efforts at the site coming up empty. Since it had the geocaching.com logo on it, I signed it, but I could not find a suitable spot to hide the log sheet, because had I simply hidden the log sheet without it being in a container, it would have been practically impossible for anybody else to find. So I left it on a tree branch next to an object mentioned in the cache's hint and moved on, hoping that the CO would very quickly come to the site, replace the container, and rehide it. When I logged the find online, the CO deleted the log very quickly, implicitly claiming that that was not actually the cache, which soured my impression of that cache and presented me with a conundrum: If all you find at a cache site is an out-in-the-open log sheet, can you actually claim a find on the cache? I've done it before with a different cache, and the claim of a find was accepted.

Notice that it doesn't properly parse UTM coordinates with decimal fractions in the easting and northing, such as 10U E 432018.2966 N 5446464.4756.

The precursor to the start of my geocaching activities was rather rough; I only discovered geocaching after resisting a close family member. I bought a GPS from a local electronics store, showed it to him, and he immediately turned Luddite and berated me for wasting my money on a gadget that, IHO, I did not really need. It ended up briefly degenerating into a shouting match as he tried to pressure me to return the GPS and get my money back, but I still kept the unit. A couple of days later, I was out looking for my first find, getting out and exercising as a result.

Turns out my ISP is blocking access to the site and I have to use a foreign proxy to get around it.

I would rather have them added to a Bookmark automatically than put on a watch list. That way I could run a PQ from the bookmark periodically. But that doesn't give you the automatic notification that I use.

But for me, if someone else subsequently finds the cache, it's confirmation to me that it's still in place, and I can then try for it again. If I fail to find a geocache, there's really no point in me making the very next attempt by anyone to find it. I'll just fail to find it again, making it more likely that I'll just strike it from my map as a nuisance and be done with it. As for me being worried about whether the cache is a very long distance away, that's not an issue for me. No cache that I look for is more than 10 km away from where I live.

That's why I said it should be an option. You don't have to if you don't want to, but I'd love to be able to for my DNF's.

Just use the ISO 3166-1 list of countries. Then any issues similar to this could just be offloaded to ISO.

Whenever I log a DNF on a cache, I always like to wait until after someone else has found it before attempting to find it again. To that end, I like to put DNF'd caches on my watchlist so I can know precisely when someone else has logged a find on it, so I don't always have to check. It would be more convenient, though, if this was done automatically upon logging a DNF. Can you give premium members this option?

The only serious injury I got while geocaching was in April 2009, when I stupidly tried to bushwhack about over 100 metres toward a cache that was on a trail. I failed to properly monitor the terrain, and ended up tearing my MCL. It left me unable to move in that kind of terrain, so I was left with no choice but to call 911 and be taken to the hospital in an ambulance. The cache in question ended up being archived without me ever finding it.

Not only that, when you view an offline list in list view, the GPS icon at the top of the screen disappears, indicating the app is not using your GPS at all in that situation.

Today, I decided to go after a multi-cache in my area. But when I arrived at the site of the first stage, I looked its info up and discovered that the cache hadn't been found in 1¼ years, meaning it was highly likely to have been muggled. What I consequently propose is that if a cache has not had a "found it" log for a certain period of time depending on its difficulty and terrain ratings, its listing should automatically be disabled and the owner of the cache should be notified that the cache needs to be verified as still in place and ready to be found. I recognize that this idea may be a bit controversial, though.

Except until you actually submit your "found it" log to the site, the cache is still going to show up on your list and your map as an unfound cache. At least that's the case on the Android app. If you have only saved a "found it" log for a particular cache locally on your device, the app will not treat that cache as found.Really? It has been a while since I've used Groundspeak's Geocaching app, but Neongeo has always showed caches as found once you've saved a "Found It" field note for the cache. Have you (or anyone else) suggested adding this feature to the Groundspeak app? Well, I just did that.

Except until you actually submit your "found it" log to the site, the cache is still going to show up on your list and your map as an unfound cache. At least that's the case on the Android app. If you have only saved a "found it" log for a particular cache locally on your device, the app will not treat that cache as found.

This would be useful to show for people who use smartphones as their geocaching GPS and want to submit a "found it" log while at the geocache site without having to incur data charges over the cell network. In order for this attribute to be applicable, the Wi-Fi being offered needs to be open for public use.

Of course. The proximity zone is one CU in radius.

Here's an idea: Move such conversations to Twitter using the geocache's GC code as a hashtag.

Situations that one commonly finds while geocaching eventually end up being given names, so that they can easily be referred to again, such as "drunken bee dance", "geostripes" or "Markwelling". I've given some of my most common situations names: "Ghost chase", "Green slime cache", "Magnet route", "Marker cache", "Proximity zone", "The Tunnel"; "Nelsoning": Compressing a common situation into three words or less, named after the guy who first applied this technique using acronyms, but has since abandoned such frivolity Have you come up with any terminology you want to share?

Okay, I'll move them to a new topic.