Saturday, May 9, 2009

Why we Cache - The Experience

One of my businesses is in the auto industry. Probably don't need to mention this, but anything to do with cars and trucks is a challenge right now. I decided to work an area today that, while part of our territory, we don't travel much as it is quite a haul and a little out of the way.

Since I had to come down here, there was a cache or two I wanted to grab. Am I glad I did;

My log from Bird's Eye View.

THIS CACHE WAS MISSING! Read on.

As we pulled up, we figured "no problem, kind of obvious the few hiding places. 10 minutes later, not luck. We were behind the tree line from the road when a green Jeep pulled slowly past our geo-truck. It then stopped. Busted!

We made our way toward the end of the treeline when the jeep owner yelled out "Problem?". "No, just on on sort of a treasure hunting game. For some reason having a problem finding the object, it must be missing." we said. "It is." he replied. "Oh, your a cacher?" "No but what your looking for is back in my truck. I cleaned up all the garbage around here the other day and found it. Couldn't figure out what the heck it was, but kept it. It's in my tool box if you want to follow me back."

We followed hum back ta block or so south to his house. A house I had noticed on the way in because it was ver reminiscent of the property Baloo grew up on in Wheaton when that area was considered rural. After we went to his truck and retrieve the piece, and Baloo explained what the game was all about, the conversation turned to his little farm. He introduced himself as Floyd.




We went into a real small shed where there were several chickens. Now, we're no experts, but he said these were some sort of special breed he was cross breeding that resulted in smaller chickens that laid relatively large eggs for their size. There were about 17 chicks in the one coup he was obviously very proud of. He also showed us how he used golf balls as "nesting eggs".




As we made our way back to the driveway, Baloo in total awe, salivating over the property, the conversation turned to the cache and it's property. When asked if he minded the cache being there, he replied no. His issue is how the property is being treated. We got a short history.

It turns out that this property is an old graveyard dating to at least the early 1800's. Floyd said that sometime in the past couple decades, someone came in and buried the headstones about 4 to eight inches. It turns out that there was a church across the road to the south, hence the graveyard. In the late 1800s, there was a young pastor who cam to work at the church. When he died, he was buried in the graveyard. Many years later, his wife came back and had the body exhumed and moved to parts unknown.

He also said there were a few civil war veterans there. He mentioned that in a couple places to the south, four corners is what we remember him saying as one of them, there is also a similar graveyard in disrepair where he said he has found several coins dating back to around the time of the civil war. Apparently through the years, he has also found several arrowheads, which last month he finally had someone from one of the schools, NIU we presume, come over to look at and took some to evaluate that he is hopeful will prove to have some additional history to add to the area.

We even found out he has a daughter in the banking business up by us in the De Kalb area. We left with an invitation to stop in and visit any time we were into the area. We're betting that invitation goes for all of our extended geo-family.

We took the cache back to it's spot, signed the log and based on the hint and what Floyd had told us where he found it, replaced it.

Driving away we were reminded of cross country motorcycle trips we used to take where we would only travel "blue roads" to meet people in small towns like Floyd and, in fact, those trips are why we bought our first GPSr. We got into geocaching to use our GPSr to discover new areas, glad to see we can use it to discover interesting locals as well.

Sunday, May 3, 2009

update: GPSMAP 60CS - Refining one of my tools

Last night I had posted a question on how to fix the date to 2 characters in the strings I posted below and got the method I posted from Clyde, author of GSAK.

I just checked the thread again and KAI team posted what I think is a better method that gives the option of leaving out the "/" to give even more real estate. The thread can be found here however the specific message I am reposting here.



From KAI Team
posted 3-MAY-09 1017 CDT

%macro gives you the most control over the format of the dates you send and won't slow the export that much (the 60CS only holds 1000 waypoints, after all). If you want to use %macro, go to Macro>Edit/Create and copy and paste the following code into the macro editor:

CODE
$DateString=DateToString($d_LastFoundDate)
$Year=Substr($DateString,3,2)
$Month=Substr($DateString,5,2)
$Day=Substr($DateString,7,2)
$_Special=$Month + $Day + $Year

Go to File>Save in the macro editor and give this macro a name (let's call it "60CSDates.gsk", without the quotes).

Now anywhere you want the date to appear in your 60CS export, just enter:

CODE
%macro="60CSDates.gsk"

You have to use the double quotes around the file name in this case.

This code will produce the smallest possible date in mmddyy format, e.g.: "050309" for today's date. If you want to change the date format, just edit the line that begins with "$_Special". For example, to add slashes as separators (mm/dd/yy), change $_Special to:

CODE
$_Special=$Month + "/" + $Day + "/" + $Year

If you want to change the year to 1 digit (not recommended, since 2010 is closer than we think), modify the $Year line to:

CODE
$Year=Substr($DateString,4,1)


The raw $DateString format is YYYYMMDD. If you want to play around with different formats, just go to Macro>Help in GSAK, click on Commands and Functions, and view the help for SubStr to learn how to modify what's extracted from the master Date String. smile.gif

GPSMAP 60CS - Refining one of my tools

After caching recently with kschu, he mentioned that through the tags feature in GSAK he had put modified hints in his Garmin GPSMAP 60.

Since he had modified the notes manually, I rarely use hints and I already have all the cache information in my Blackberry Curve using Cacheberry, this did not interest me however tweeking my GPS contained information did.

I had used the strings but was finding what I had not doing all I needed and had set it up a few years back when I first got my GPS. It was time to play. The following are my preferences, yours may vary. The tags in GSAK are a wonderful thing.

Using the tag strings, I modified my GPS to show me in the find screen the waypoint designation (sans the "GC"), the cache container, the cache type and the terrain and difficulty.



In the notes area, I show the caches given name, the status of the last four logs, date of last find and if there is a travel bug or not. The date field format is based on the short date format you use in Windows as set in the "Regional and Language Options". Have not played with these settings in Wine yet.



The two tag srings are;

Waypoint name = %drop2-%con1,%typ1,%dif1,%ter1 %notGC%code
Waypoint Description format = %smart=15 %last4 %datelf %bug



This gives me all the information I really need in the field, at least within the limitations of my Garmin GPSMAP 60CS. I hope this gets you thinking of ways to make your GPS more efficient for the way you use it.