This article was originally published on Cache Up NB. It has been mirrored here for archive purposes only.
I am not one for puzzle caches. In fact, as a general rule I avoid them. Most times it’s simply because I really suck at trying to solve them. But every once in awhile I do one or go out with someone who has it solved and hence I am slowly approaching my 100 puzzle caches found. However, there is one in Moncton that I tried for awhile ago without actually solving the puzzle. It’s this cache.
I have heard through the grapevine where the final for this cache is so I had contemplated going to try and find it without the final coordinates. I got a hint as to the whereabouts from another cacher so in early June, I set out to try and find it. I spent a good hour in the area searching through every tree and shrub I could find, but came up with nothing. I put the cache on my watchlist and decided I would try for it another day.
Now, the fact is, I am just too lazy to watch all of the movies, and for me, there’s a sort of challenge in whether or not I can find it using other means other than what the original hider had in mind. After all, the idea is to solve for the final coordinates right?
Well, given the information provided on the cache page, today I decided to try and use a bit of logic. A checksum is given and portions of the coordinates are also given. Knowing that the numbers displayed would need to be added to the numbers not displayed gave me a number for both north and west. I knew that the last 3 digits for both would have to add up to this number in order for the checksum to be right. For example, if the north coordinates were shown as “N 23 31.BCD” and the checksum was 18, I know that B+C+D must equal 9. Using similar logic, I figured out the same kind of number for the north and west coordinates. This meant I now had a means to try and figure out about where this container would be.
I then did some math, and wrote a little program to help me, to figure out every possible 3 digit number that would “fit” within the parameters given. Knowing where the general area is, I used Google Earth to narrow down certain numbers. If you go too far in any direction, the numbers would be too low/high so it helped me create a “range” for which this cache could be in. Other numbers were easy to figure out because when I created a waypoint in that general area, they were always the same and when I plugged them into the puzzle, they worked with the other numbers I had already figured out.
After I had the possible area figured out, I then converted that into 130 different sets of possible coordinates. I then exported those coordinates from GSAK into Mapsource, Google Maps, and Garmin Basecamp to overlay their locations with an actual map. This then provided me with a good idea of where exactly the cache could be. But more importantly than that, it helped me eliminate where the cache could not be based on the land area, roads, etc. A large chunk of the sets of coordinates were overlayed on water and highway so I immediately knew to steer clear of those areas. Of the four “groups” of coordinates I plotted, it would seem that the cache itself would likely be located in one specific area. An area I did not check when I was there last. Not having my GPS with me, I couldn’t go out and test it so I had to wait until that evening to go and try out my plan.
I got home tonite, had supper, and then headed out to try and find this cache. I figured I would try in the opposite end of the area I was before and see if I had any luck. It was quite a hike through a lot of the tall grass and I did get to the first area and no luck. I then saw another area where it could possibly be but it also meant that I would be passing by a pile of trees. Since I knew the container was ground level, I figured I would check. No luck.
I then proceeded around a pile of reeds and then spotted what looked like a pretty cool looking tree. I thought to myself, if I was going to hide a cache, I would hide it there. I then spotted what looked like a reflection of some kind. At first I thought it might have been a small animal but as I got closer, it was indeed a plastic container filled with toys. I had found the cache!
Signed the log and replaced it and felt a serious sense of accomplishment. I took about an hour today to do all of the “calculations” and I think it payed off in the end. It may not be the way the cache owner intended folks to find it, but it certainly worked. Cross one puzzle cache off my list.
10 Responses to Solving a puzzle cache with brute force