wildlifewriter

No difference at all... One contains a large amount of hot air, which emerges from time to time. The other contains a timid creature with poor eyesight, which is also an occasional nuisance. Both images might relate to the same person, or they might not.

Well... as hatchet jobs go, there wasn't much of an edge to it. HH: The person concerned seeks attention for his unpleasant little vendetta, and all your OP does is give it to him. Difficult though it may seem, your best recourse is to ignore it (and him) completely. Complaining to Groundspeak may seem like an option, but I doubt if there's much they can do for practical purposes.

Given the facts that: (1) The sea comes right over the lighthouse island, during Atlantic storms. (2) There is an Atlantic storm every second Tuesday, when there's an "R" in the month. And even when there isn't. (3) The page mentions a tupperware box. It does not mention the box being protected by a frame of steel girders, bolted to solid concrete. (4) It is a strong possibility that there never was a cache there in the first place. ... your guess is as good as mine.

This is why it hasn't been found...

Easy... Buy a Garmin iQue 3600. Add an Otterbox case to protect it as they're a bit fragile Buy Fugawi OS maps to run on it. Buy extra memory cards as the supplied one isn't adequate. Source an external battery pack, as the built-in one only lasts 2 hours Throw away everything else. Sell first-born child into slavery to pay for it all. Sorted.

There always is. Even if the hint says: "Find a gold-plated rabbit with a sign round its neck saying Saucepan in Welsh."... ...this just means that there'll be two of the dagdum things: one at the WGS84 co-ordinates and the other at OSGB.

Great idea! A hoax cache, complete with encrypted clue on genuine fake medieval parchment - sort of like a locationless, but only for the really gullible. When you find the cache, check out the swap items - there won't be a grain of truth in it...

I never thought of that... ... dadgum and blost.

The e-mail quoted is a forgery. There are no spelling mistakes in the body text - therefore ipso facto it cannot be from anyone at the BBC.

Ha! You have been autocensored - a free service from Geocaching.com Nip over to the testing area, to experiment with other words that don't appear exactly as you typed them.

Cobblers. Initially, the co-ords for that cache were 205 metres away. They're still about 30m off - in dense undergrowth, and the cache owner stubbornly refuses to alter the listing. If I hadn't logged the accurate waypoint, it's possible that no-one else would ever have found it. Read the logs.... -Wlw

<Wlw studies map on site...> A small point, but please stop referring to "UK" when what you actually mean is "Great Britain". Thanks.

Much better. Do LOTS more testing, though, because... I know what it means. If you like, put the source code in a file on the web, send me a link by PM and I'll take a look at it for you.

Sorry Barry, but your converter isn't even close ... Example: N52º 26.0000 W1º 39.0000 (Near Meriden) Correct grid ref: SP 23892.1 81762.0 Garmin conversion: SP 23893 81767 Your web conversion: SP 23942 81813 Approx errors in distance- Garmin:5m Yours:71m ... Not really a geocaching tool, then.

Nice article. Beautiful photography, as well.

If the cache is as difficult to find, as its web page is difficult to read... ... this one could take a while.

Serious answer: it depends how much of this you intend to be doing. For multiple waypoints, Chris 'n Maria's waypoint workbench as mentioned above, is very good and more than accurate enough for this purpose. Needs MS-Excel on PC, though.

Needless use of long words, where short ones would do the same job. Point taken - I accept the implied rebuke.

It appears that my shot hit its intended target. ... excellent.

By taking a slight (perhaps, not so slight) liberty with the usual route, you could say it's simply N53º, W5º Or... there a nice palindrome (on the route) at N53º 22.050 W05º 02.235 Or... well, perhaps that's enough.

Well... I knew what Forester was talking about, but I'm b______d if I understood any of THAT. Why do show-offs like LostAgainAndAgain keep trying to bamboozle the rest of us with this gratuitous technical jargon? It's not big and it's not clever....

Just so. For the Rev.2 (non-mapping) models, I concede the point. The basic (yellow) eTrex doesn't seem to have had a firmware revision since before the old King died.

Well done again (More comebacks than Frank Sinatra, that Seasider bloke.)

The 'kicker' is, of course, that it doesn't work the other way round - not on Garmin handhelds, anyway. Change the display format and, yes, the datum setting alters automagically... BUT, if you then go down the menu and alter a datum, the display format stays the same... ... at which point, new caches start to move and all sorts of horrible things can happen. I'll let you know when the book comes out.

Because, as I established (to my slight embarrassment) in this experiment - if a waypoint is downloaded from the site, and transferred (from PC) to a GPSr - it DOESN'T MATTER what datum or format the thing is set to: it'll still track to the position. However, as we have seen, it sure as hell matters when one is placing a cache! Well done on finding it - I reckon I should be awarded a find too , just for working all this stuff out...