Not Quite Easter Eggs

Sorry people. I have a lot on my mind lately and I want to express myself, but it’s piling up so fast I not only can’t get it all out, I just can’t get started. Unfortunately that’s sort of what happened to my other blog. I got behind and kept wanting to catch up before entering anything new. It never happened and that blog died. Well, maybe. I have something new to post there now, but perhaps I’ll just include it in this one instead, as I think most of my readers are following me here now anyway.

So, where to start. Oh my.....
Perhaps I’ll start with what I just mentioned above.

I’ve been geocaching for the first time this year, and while we didn’t go very far, I do like to tell people where and when I’ve been.

I live in a tiny village, but even here there are four caches available for those who want to look for them. I’ve found a couple of them before, and even another that no longer exists. Easter Sunday was a really nice day to go for a walk, so I took my hubby and headed out.

The first one we looked for (GC26GHY) was what they call a multi cache. That means the way point that is given is not the one where you will find the cache itself. We had to check out a sign at the given way point, find all the numbers on it and then do some mathematics using them. Finding all the numbers is not as easy as it sounds, but we managed, and got the math right too. We know that because the nice person who was giving the clues gave us a way to know for sure that we were arriving at the correct numbers without actually telling us what they were.

Then, that’s where we ran into trouble. One of the numbers would tell us the distance to the cache in metres, while the other was supposed to give us the bearing to the cache in degrees from True North. It said to project a way point on my GPS to calculate where the cache was located. Uh huh. Some of you may understand that but I sure didn’t. I’ll be having to consult my manual to see if my GPS model even does such a thing. I could have tried to walk in a circle, but between the canal and the river, I’m sure I would have drowned in the process.

Never mind. We’re brave souls and we set out to find it anyway. We have enough experience at this that we figured we’d have some idea of where to look.....or at least in which direction to look, and hope we’d find a logical hiding place along the way. What I found was that the beavers had been very busy since my last walk in that area. While I was checking that out, my hubby poked about in a few places, and then found the cache using what he referred to as "man sense." Lovely. I am the registered member of www.geocaching.com, by the way, and I just log him in as +1 after my caching name when we find a cache. So hey, he may have found it, but I’ll still get the credit :)

The other cache (GC1NWQ6) was also nearby. I had looked for it for a few moments last fall, when I first learned about it. I followed the clues and looked where it should have been and it wasn’t. I wasn’t dressed for the adventure so decided to come back someday and look again. I did, and since I didn’t find it where I had expected to previously, I handed off the GPS to the hubby and he went right too it. And yes, it was right where it should have been! It was NOT there when I looked. But I could see where some smart #@$ may have put it just to make things more difficult. Or maybe that’s where it actually belongs and some lazy person didn’t put it back there this time. Either way, we (he) found both caches that day, but it did wet our appetite to go hunting again soon.