Phillip and I went out last night to replace the "Genmaicha" travel bug, in Lake Forrest Park. When we got there, it was dark. The city is not too far from home, but the cache was in an area I'm not familiar with. It's a residential area with undeveloped areas, winding streets, and no street lights. We got very lost. Using the GPS receiver, we finally found the park where the cache is hidden. The park, however, closes at dusk (which the cache listing didn't mention). We left frustrated, and got lost trying to find our way back home.
I went out early this morning, alone, and found the cache. I dropped off the duplicate "Genmaicha" (I'm not sure what's going to happen if the original shows up somewhere) as well as another travel bug we'd picked up at a previous cache. There's another cache .6 miles from this morning's cache, so I figured I'd try it while I was in the area. When I got home and logged our "Did Not Find" on that second cache, I noticed that it had last been found in June, and that there were two DNF's in July, I'm guessing that it's been muggled.
We had planned to go to Pet's house this afternoon, and spend two nights there. Phillip's recovering from a cold, or something, so we decided to leave tomorrow and make it a one-night stay.
We did, however, hide our fourth cache this morning. It's more my cache this time. We seem to be following a pattern. It's at a bench I'd seen for years on my drives over Capitol Hill. It's not too far from "I Can See The Dawghouse From Here!" - but just far enough to get by the "no closer than 528 feet" geocaching rule. I probably started thinking about the location as a cache site when we hid "I Can See The Dawghouse From Here!" It didn't seem like an inspired idea, though - just a bench in a nothing special place. That's why it took me so long to get moving on it.
Then, earlier this week, an idea for a "puzzle cache" came to me. I did searches on geocaching.com, using keywords for what I'd guess people would name such a puzzle. I found one cache in Germany that used the same idea as I had come up with. That was OK with me - puzzle caches often use similar puzzles, and as long as my idea didn't show up in the Seattle area, I was happy.
I went out Tuesday evening to get the coordinates for the hide. I was amazed to discover that what I had thought was a bench all these years was actually the railing for the stairs that go down the hill. (It's partially hidden behind a Jersey barrier, you see.) Still, it was a pretty good place to hide a cache.
I've worked on this cache hide more than we worked on our previous hides. (I suspect that's normal for a puzzle cache.) I did research on the puzzle, and then constructed the puzzle. I thought up a good location for the "false" coordinates, and found those coordinates. (That's how puzzle caches work: False coordinates are posted for the cache location - those have to be within a mile or two of the actual cache, and also no less than 528 feet from another cache - and then the cache hunters have solve some sort of puzzle to find the real coordinates.)
I spend some time camouflaging the cache container on Thursday and Friday.
As of this morning, I still hadn't completely decided on a name for our new cache. Before it turned into a puzzle cache, I'd been thinking of "Curve Ahead" or "Where The Rubber Meets The Road" or "The Two Bostons." When I'd decided to make it a puzzle, I was thinking of "I Thought It Was A Bench" or, more in tune with the nature of the puzzle, "Uhura" or "Universal Translator." Phillip had suggested "Babble On" or "Babelfish." I was afraid of giving too much away in the title, so I was leaning more toward calling it "U.T." - which is what it turned out to be.
We submitted the cache listing for "U.T." at 11:20 this morning, then we hid the cache on our way to removing litter from "Get Christie, Love." The cache was approved and listed at 2:35 this afternoon. (Caches in our area have been approved rather quickly lately, but I thought we'd get a day or two delay since it's the Labor Day weekend.) fauxSteve was "First To Find" at 4:47.
I went out early this morning, alone, and found the cache. I dropped off the duplicate "Genmaicha" (I'm not sure what's going to happen if the original shows up somewhere) as well as another travel bug we'd picked up at a previous cache. There's another cache .6 miles from this morning's cache, so I figured I'd try it while I was in the area. When I got home and logged our "Did Not Find" on that second cache, I noticed that it had last been found in June, and that there were two DNF's in July, I'm guessing that it's been muggled.
We had planned to go to Pet's house this afternoon, and spend two nights there. Phillip's recovering from a cold, or something, so we decided to leave tomorrow and make it a one-night stay.
We did, however, hide our fourth cache this morning. It's more my cache this time. We seem to be following a pattern. It's at a bench I'd seen for years on my drives over Capitol Hill. It's not too far from "I Can See The Dawghouse From Here!" - but just far enough to get by the "no closer than 528 feet" geocaching rule. I probably started thinking about the location as a cache site when we hid "I Can See The Dawghouse From Here!" It didn't seem like an inspired idea, though - just a bench in a nothing special place. That's why it took me so long to get moving on it.
Then, earlier this week, an idea for a "puzzle cache" came to me. I did searches on geocaching.com, using keywords for what I'd guess people would name such a puzzle. I found one cache in Germany that used the same idea as I had come up with. That was OK with me - puzzle caches often use similar puzzles, and as long as my idea didn't show up in the Seattle area, I was happy.
I went out Tuesday evening to get the coordinates for the hide. I was amazed to discover that what I had thought was a bench all these years was actually the railing for the stairs that go down the hill. (It's partially hidden behind a Jersey barrier, you see.) Still, it was a pretty good place to hide a cache.
I've worked on this cache hide more than we worked on our previous hides. (I suspect that's normal for a puzzle cache.) I did research on the puzzle, and then constructed the puzzle. I thought up a good location for the "false" coordinates, and found those coordinates. (That's how puzzle caches work: False coordinates are posted for the cache location - those have to be within a mile or two of the actual cache, and also no less than 528 feet from another cache - and then the cache hunters have solve some sort of puzzle to find the real coordinates.)
I spend some time camouflaging the cache container on Thursday and Friday.
As of this morning, I still hadn't completely decided on a name for our new cache. Before it turned into a puzzle cache, I'd been thinking of "Curve Ahead" or "Where The Rubber Meets The Road" or "The Two Bostons." When I'd decided to make it a puzzle, I was thinking of "I Thought It Was A Bench" or, more in tune with the nature of the puzzle, "Uhura" or "Universal Translator." Phillip had suggested "Babble On" or "Babelfish." I was afraid of giving too much away in the title, so I was leaning more toward calling it "U.T." - which is what it turned out to be.
We submitted the cache listing for "U.T." at 11:20 this morning, then we hid the cache on our way to removing litter from "Get Christie, Love." The cache was approved and listed at 2:35 this afternoon. (Caches in our area have been approved rather quickly lately, but I thought we'd get a day or two delay since it's the Labor Day weekend.) fauxSteve was "First To Find" at 4:47.