The purpose of this cache is to teach you how to use the functionality in the type of GPSr that I use (name withheld) to change coordinates for a waypoint. You don't care about that, you say? Well sorry, but you'll have to learn it anyway if you want to solve this puzzle! I entered the posted coords for this cache into my GPSr, and then used the functionality described below to change the waypoint to have the final coordinates. You will have to use the information below to come up with the final coords. Here's how it works. (Pay close attention, as there WILL be a quiz!)
NOTE: YOU DO NOT NEED TO HAVE THIS TYPE OF GPSR TO SOLVE THE PUZZLE. YOU JUST NEED TO UNDERSTAND HOW IT WORKS.
The picture to the right shows the relevant sections of the GPSr, with the posted coords entered. I have added arrows and a star to indicate movements of the rocker button. The cells with yellow background indicate the current "cursor" location both in the numeric pad, and in the coords. With the cursor on the ">", you press the rocker button straight down to move to the next number in the coords that needs to be changed. Then with the coords cursor on the desired number, you toggle the rocker button up, down, left, right to move to the desired new number on the pad, then press the rocker button again to select that number. After each number selection, the coords cursor automatically moves to the next number, so you don't need to go back and use the ">" button again. So the only time to return to the ">" button is to skip past numbers that don't need to change. You should never need to use the "<" button, unless you make a mistake. (Which of course won't happen!) Then, when the last number has been changed, you use the "down" toggle to get to the "OK" button, and press the rocker to confirm changes. You can go directly down to "OK" in any of the number columns. In other words, it would take four "down" clicks to get to "OK" from either 1, 2, or 3. Also, if needed you can go directly from ">" to "0" with two left clicks, passing through "<". Oh, and just ignore the "+", "-", and up/down arrows to the right. I suppose they have a useful purpose, but I never use them.
|
> to A = 4 clicks
A to B = 2 clicks
B to C = 3 clicks
C to D = 2 clicks
D to > = 5 clicks
> to E = 4 clicks
E to F = 3 clicks
F to G = 2 clicks
G to H = 3 clicks
H to OK = 3 clicks |
Your challenge is to determine the final coords, based on the number of "toggling" clicks needed on the rocker button to change from the posted coords to the final. The final coords are in format N 38 4A.BCD, W 121 1E.FGH. As it happens, none of the eight missing numbers are the same as their counterpart in the posted coords. And each of the eight digits is a different value, with no digit repeated. So in changing the coords, I pressed the rocker four times to get to the "A" position in the coords, then navigated to the new number with toggling clicks, and selected that number. Next navigated to the number for "B" and selected it, etc. After changing the "D" number, I had to return to ">" and click five times to get to the "E" position in the coords. Next selected numbers for E thru H, then navigated back to "OK" to save changes. So, the number of "straight" clicks should be a known number. Number of "toggle" clicks depends on the numbers to be selected. And of course, I always made the minimum number of clicks needed to get to the next position.
The chart below the picture shows how many toggle clicks I made for each of the movements needed. From that info, and knowing rules for distance between posted and final coords, you should be able to find the cache location. A TOOL (OR VERY VERY TINY FINGERS) IS STRONGLY SUGGESTED FOR LOG RETRIEVAL.
Here are some tips for parking:
For a place with a safe way to cross the busy street, but a 0.3 mile walk, subtract 108 from N, and add 321 to W, of final coords.
For a less safe street crossing (be VERY careful!), about 400 feet from GZ, subtract 6 from N, and add 75 to W.
Have fun!
CONGRATULATIONS TO GoldenStateBoy FOR FTF!