The cache is NOT at the posted coordinates, but is within 2
miles.
The first thing I wrote was a tool to convert coordinates from all kinds of
formats, then allow you to view a variety of maps for those
coordinates.
After that, I wrote a tool that makes searching for stuff on Geocaching.com
faster, especially on mobile phones.
Tired of entering coordinates for multis by hand, I wrote a
Coordinate Grabber
that will go to any web page and pull out all the coordinates so
you can download them.
Expanding on that last tool a bit, I wrote a tool which calculates distances between
coordinates or a lot of coordinates, making verifying locationless
cache finds a lot easier.
I also maintain a collection of ExpertGPS calibrated
maps.
Anyway, I'm always thinking about new tools that will make
Geocaching more efficient. The thing that's annoyed me the most is
those dang "500 Server Too Busy" error messages you sometimes get
from the Geocaching website. I've finally decided to do something
about it.
My latest tool is a sophisticated proxy server for geocaching.
It caches pages, much like search engines do, but the site remains
completely interactive. You can even log finds with using its log
posting queue which eliminates all "500 Server Too Busy" messages
you might see otherwise.
I was trying to think of a way to introduce people try out this
new tool, and then idea came to me that I could place a cache for
it. People try out the tool, which on successful use, would give
them coordinates for the cache.
So, here it is, my ultimate 500 error eliminator tool, which
I've called geoCACHE. (Get it?)
Let me know what you think! Once you get it, you'll find the
coordinates. You should get a full 15 digits for the
coordinates.
The cache location is camo'd. It's a magnetic keyholder.
Enjoy, and let me know this or any of my other tools work for
you.