Team Van Dyk

I'm constantly seeing people referring to loading caches into their Garmin Nuvis. Presumably, this is done by loading a GPX file (or zip file full of them from a PQ). Well, now that Garmin has an iPhone app, I'm wondering if that's possible in the app. Ive had the TomTom app forever and am not inclined to change, but will if there's a way to get caches to shop up in the Garmin App. Anyone know?

Magellan ToughCase is really the perfect (albeit, pricey) answer. Tough, waterproof, built-in battery and improved GPS antenna. I don't think there is am iPhone 4 specific version, but rumor has it that the iPhone 4 fits into the 3Gs version.

Pretty much any of the caches in the Paycho Urban Cache Series are right up there on my want list, but particularly, #9: http://coord.info/GCTA5E

Moun10Bike, I just downloaded and installed v.4.5.2 (the "next release"). Where is the "visited" option for trackables promised in the feedback forum?

Go to the bookmark list on the gc.com site; create a pocket query from the bookmark list; download the created pocket query in the app. Hopefully, eventually, they'll cut out that middle man and allow you to sync your lists directly (preferably, both ways), but for the time being, pocket query is the way to do it.

While that may be true for you, the fact is there are a great many people that are interested in social networks ... those two to be precise. There are entire geocaching communities who are based on Facebook groups. Having the ability to connect a log (vs the old like a cache feature) is a good thing. Those who use it wrong will lose followers, unless their followers are interested in getting slammed with logs in their news feeds. Same as any other use for the social networks. Those that go on about silly things don't have many followers. The twitter integration has been around for a long, long time already and most people (with followers that is) already know how to keep that signal to noise ratio to something sane. Used selectively it can be great way to highlight a specific cache visit to your followers/friends. I like that you can link to your log - that way instead of sharing the cache, you can share your story about that cache. So put me down as one who "likes" this feature And while this new development may suit YOUR needs, it doesn't do squat for me. Sure, I'm behind the times and a retro-grouch to boot. Certainly every other geocacher is on facebook and uses twitter. Here's a good solution, then. Don't enable it. Ignore it (which should be easy since you'd have to go out of your way to even find a mention of it on the gc site if you don't have it enabled), and ignore threads discussing it. Problem solved. --Matt P.S. This is a very good point, though: http://forums.Groundspeak.com/GC/index.php?showtopic=279241&view=findpost&p=4799185 It would be nice if they did something with that friends feature; even a simple stream of most recent "found it" logs tucked away under the friends tab would be nice.

I don't think that's how it works. It's not. It is some nice FUD, though.

We've got a series built, in part, on QR Codes. Don't need a smartphone; there are some links in the cache description for a couple of alternatives to decoding the QR Codes. http://coord.info/GC2YPCX

Once you solve the puzzle, you can input the coordinates as a waypoint in the app (flag icon near the top right of the "navigate to cache" map).

http://twitter.com/search/coord.info BTW, I'm with the others here who say they'd probably use it if you could do so selectively and avoid spamming twitter followers and facebook friends. Until you can do that, it's a pretty useless feature.

Don't know about other platforms and software, but on my Android phone, using Barcode Scanner, it displays the URL and you have to press a button before it goes there. Same for Red Laser on iOS.

I use 3M Ultrathon or Off Deep Woods Sportsman II. Both around 30%. Both work very well. Only ticks we've gotten is when we've forgotten to put it on before deciding to wade through head-high grass. Never heard of that permathin that people use to treat their clothes, but we, too, have a set of "cachin' clothes", so we're gonna pick some of that up now. Great to get these ideas now that tick season is winding down!!!

Perhaps, but pirates were certainly behind PMOs.

Not sure about other parts of the country (or the world, for that matter), but scuttlebutt around here has been that caches placed "too close" to letterboxes have a nasty habit of growing legs and walking off. For that reason, I always try to find the nearest LB before placing. Certainly not a rule or anything though.

Ha! Awesome. First, +1. Second, I hadn't considered switching from "muggle" to "muggler" as a way of distancing myself from Potterers, but I like this idea. A lot. "Muggler" it is.* --Matt *I'd be lying if I said I wasn't looking forward to the first time someone corrects me on this so I can give them the explanation. Thanks Seeker!!

Based on the last few logs of Jack Frost and northwind123, looks like this could be his profile: http://www.geocaching.com/profile/?guid=c20d7121-bfaa-491c-8c78-e992824a3a5e What a sad, sad story. Will definitely make me think twice about some of the risks involved. Heart goes out to the family.

I've found it's just easier to manually write the HTML and stay with as basic a set of code as you can.

+1 This is an all-too-familiar refrain.

Almost all of my DNFs are memorable. I tend to move heaven and earth before abandoning a search, so if I've DNF'd it, I've spent a long, generally memorable, time trying to find it. In fact, I dare say I have an easier time remembering the details of most of my DNFs than I do many of my finds!

I know there's a general consensus that perhaps feedback isn't acted upon quickly enough, and in this case, that's certainly true, but for those who really want to see some sort of system implemented to address this, I would encourage you to please add your voice (vote and comment) to the chorus here: http://feedback.geocaching.com/forums/75775-geocaching-com/suggestions/1070029-trackables-no-longer-in-caches?ref=title

So, you just don't like geocaching at all, then? I'm kidding (sort of), but am curious what part it is you like given the above and given the nature of the game.

This is a Top 10 Request: http://feedback.geocaching.com/forums/75775-geocaching-com/suggestions/1070029-trackables-no-longer-in-caches?ref=title If you haven't already, I would encourage you to vote and add a comment. Hopefully, they address this soon.

I'm very confused by this. All of the TBs were last retrieved and then dropped in the It's a Dime cache by stellarscapes (who, curiously, is not the CO). ALL of the drops in the It's A Dime cache are dated 7/7/10 regardless of whether that date is before or after the date stellarscapes retrieved it. In fact, in the case of TB3MJRN, the sequence (by log date, anyway), is (i) stellarscapes drops it in It's A Dime cache on 7/7/10; (ii) TB is first RELEASED by its owner on 9/30/10; (iii) stellarscapes retrieves it on 6/17/11. This pattern repeats for a number of the bugs; in fact, most of them were retrieved by stellarscapes from the Hidden Cardinal cache on 11/3/10 and "then" dropped in It's a Dime on 7/7/10. Is s/he logging drop in It's a Dime to clear it from his/her inventory and then just keeping the TB for some reason (backdating the drop in hopes of hiding the pattern)? Given stellarscapes' apparently solid cache and TB history, it sure seems odd. Very, very strange. --Matt EDITED: If you look at the 7/7/11 log entry for It's a Dime, it appears that stellarscapes actually gave the TBs to the CO (didn't drop them in the cache); probably dropped them in the cache for mileage purposes (although, the CO should probably retrieve them all out). I'm guessing the 7/7/10 log date issue is just an error and supposed to be 7/7/11.

Ticks, Mosquitos, poison ivy. In that order.

I didn't think it was kosher to have a finder be required to email the cache owner for coordinates. They don't actually email the CO. They email an empty, unmonitored email address with an auto-reply (not unlike the several caches discussed around here which require finders to call a phone number and listen to a voicemail greeting). If they're concerned about privacy, there's nothing stopping them from doing so from a dummy email address. In any event, given where we put the final and the 2 mile proximity rule on mystery caches, burying parts of the coords in the codes made it too susceptible to brute force.