This topic contains 24 replies, has 13 voices, and was last updated by 
-
Posts
-
@marc_54140 wrote:
@Team Hemisphere Dancer wrote:
@gotta run wrote:
@Team Hemisphere Dancer wrote:
I write them down on the back of my hand.
But how do you find them in winter then?
I follow Marc!
I always had a weird feeling I was being followed…..
You’re not paranoid, everyone IS out to get you 😯
On the Left Side of the Road...Hm.
Thank you for all your methods. Looks like CJ’s method will work for me.
I’m not into puzzle caches all that much, but with the caching downtime in the winter, I figure I’d try some puzzles.
So far as of this post, I’ve only solved 4 puzzles from home (2 of them found during my milestone run).
I hope to solve a few more though a lot of the puzzles are head scratchers, but eventually I’ll get that “a-ha” moment or the “duh” moment.
Thanks, CJ, for the topic.
I’m actually experimenting with “Corrected Coordinates” as well, but I’m not sold on them yet. I’ll explain what I see as the pros / cons of both options.
Child Waypoints – The new waypoint gets a default “FL” instead of the “GC” for the cache. These are easy to identify on the GPSr as finals. The “bogus” cache location is still a waypoint and can “clutter” the view and confuse you when you see them “pop” into view while chasing other caches. The good thing is that if the “bogus” coordinates are the starting point for simple offsets (i.e. cemetery style caches) then you need both the initial / final if doing the cache a second time (i.e. with the family)
Corrected Waypoints – These reduce the “clutter” by showing only known hide locations on the GPSr. The bad thing is that if the “bogus” coordinates are the starting point for simple offsets (i.e. cemetery style caches) then you need both the initial / final if doing the cache a second time (i.e. with the family)
Some bogus waypoints are also parking spots to park at for the final. That’s the case with the Semaphore cache that I solved and found last week for my 399th find.
What I did for that one was run the Nuvi macro to send the caches to my nuvi, then edited the coordinates for the Semaphore cache on GSAK and sent it to my handheld.
That made it easy for me to find the parking spot with the Nuvi then the cache itself with the handheld.
But as the winter goes on, I know I will solve a few caches without fining them right away. That’s why I wanted to figure out a way to organize my solved puzzles and looks like your method will work for me. I’m sure I’ll come up with my own system soon enough as I solve more puzzles.
You mean there are dummy coordinates posted…….???? 😯 No wonder I can’t find anything, but can swim like a fish!
@-cheeto- wrote:
Printed cache pages with notes all over including in my truck, bedroom, desk drawers, etc. I don’t keep track of past solved coords and usually trash them over time which haunts me later.
yup… except mine are on random sheets of paper… and then months later, I don’t even know which coords go with which cache… I end up having to re-solve the puzzles. Oh well.
@thepharmgirl wrote:
@-cheeto- wrote:
Printed cache pages with notes all over including in my truck, bedroom, desk drawers, etc. I don’t keep track of past solved coords and usually trash them over time which haunts me later.
yup… except mine are on random sheets of paper… and then months later, I don’t even know which coords go with which cache… I end up having to re-solve the puzzles. Oh well.
Been there, done that too!
I create a bookmark list of solved puzzles, make it a private list rather than public and put the solved coordinates in the notes.
@decrepit wrote:
I create a bookmark list of solved puzzles, make it a private list rather than public and put the solved coordinates in the notes.
That’s a pretty darn good idea ❗
Team B Squared, out of the upper peninsula, has bookmarked for solved puzzles, ones he has found (I think), and ones he is thinking about (i.e., can not figure out).
So, yes, bookmarking is a great tool. However, the current limit is 500. I have over 1500 puzzles in GSAK database.
You must be logged in to reply to this topic.