Skip to content

coddiwomple Mystery Cache

This cache has been archived.

BrianDiane: Nope - ain't goin' back there. Time to let this one rest on its laurels, or rather "evils."

More
Hidden : 8/1/2016
Difficulty:
3.5 out of 5
Terrain:
2 out of 5

Size: Size:   micro (micro)

Join now to view geocache location details. It's free!

Watch

How Geocaching Works

Please note Use of geocaching.com services is subject to the terms and conditions in our disclaimer.

Geocache Description:

The image below was sent to me by a local cacher (who shall remain nameless to protect his/her safety), along with the suggestion, made by another unnamed cacher, that “… it could very well be the name of the next BrianDiane cache.”   See – it’s not my fault!


coddiwomple

When the suggestion arrived, I was completely barren of both intent and ideas, evil or otherwise, for another cache. But, when duty calls, one must rise to the challenge. I struggled for quite a while to come up with the etymological origin, or origins, of this fascinating, and totally geo-appropriate, verb.

Then, after a few days without my meds, it came to me when the entrails of the chicken I was preparing for dinner spoke to me! “It comes from two words,” said the entrails in plain English (for once) – “One part of “coddiwomple” is a fictitious person’s first name and the other part is an approximation of a verb.”

Now, all I had to do was convert those two words into the decimal minutes of a suitable cache location. Hmmm… I consulted the entrails one more time, and the method was revealed to me in plain chickenspeak.

Partially translated, they decreed I must firstly scromgoggle to get the surname of the fictitious person and hrunze it into a two-digit wvnip and then into a one-digit wvnip, and then secondly versmutk the other word to get the verb and hrunze it the same way.

Then the chicken entrails shut up, and I was left with two, three-digit numbers. I went to this location, using the first number I’d scromgoggled and hrunzed to replace the decimal digits of the posted N coordinates and the second number I’d versmutked and hrunzed to replace the decimal minutes of the posted W coordinates. While it might appeal to a chicken, it was certainly unsuitable for a cache.

Discouraged, I returned home and checked the green bin for the chicken’s entrails. Sure enough, as I opened the lid, I heard, again in partial chickenspeak, “You blumphly zunker, didn’t you hear us say to subtract 380 from the first three-digit wvnip and subtract 299 from the other?” Then they shut up once and for all, without telling me which number was the N and which was the W.

After popping my meds, I checked both results on GoogleEarth and saw, to my surprise, that both yielded possible locations to hide a cache. I went to each, and placed the container at the only suitable one, the other one being physically inaccessible. I took a slightly circuitous route to the cache to avoid the poison parsnips.

Since the meds had not taken full effect, I decided to not include a GeoChecker, “reasoning” the GoogleEarth results would pretty much confirm the correct three-digit numbers (or wvnips).

BTW, the chicken was delicious!

Additional Hints (No hints available.)