Going to be heading down to Orange County to grab this particular Dash Point. We got lucky when the computer program for this month set that one up. It's in Ronald W. Caspers Wilderness Park very near a fire road trail, so it should be easily reached after about a two mile hike or so.
I ran a PQ centered around that point and got the strangest looking PQ map I've seen in awhile. This is a pretty rural area but I was still expecting to see more caches along the Ortega Hwy. The arc to the west is in urban Orange County, but the nothingness to the east of the center of the PQ was surprising until I thought about it. The area to the east is pretty rugged and mountainous. I think I was surprised that there weren't more caches hidden along the Hwy. I guess we'll find out when we get there on Saturday. It could be that it's not safe to stop along most of the road. If you're not from this area, the grey area to the south is Camp Pendelton Marine Corp Base.
The Dash Point is in the center of the map and we'll be going for the caches located there. Most of them are along the trail and so they're not micros, but good sized caches. When the Tadpole found out about that, his immediate reaction was, "Score!" I have to agree with him. I'll be sure to take the camera along to get some pictures.
Another surprise was I couldn't find a public route query for the highway either, so I had to create my own. That wasn't too much of a problem. Just opened up Google Earth and asked for directions between San Juan Capistrano and Lake Elsinore. That gave me a route that I saved to my computer which I then uploaded to Geocaching.com. I put in some parameters for the route and came up with 69 caches along the route, most of which are centered around San Juan Capistrano and up around Lake Elsinore. There really aren't that many caches along that route. I've made the route public. You can search for it using keywords, Ortega, Elsinore or Capistrano.
Thursday, October 9, 2008
Surprising Results
Labels: geocaching, GeoDashing, Pocket Queries, Ribbit, Route queries
Tuesday, June 3, 2008
Two digit GC numbers
The planning has already begun for the annual summer camping trip. Last year, our adventures took us east of
Labels: camping, national parks, Ribbit, Route queries
Wednesday, May 21, 2008
Backroads
This past weekend I drove up to Hey, she held on to her scholarships, made new friends, grew musically and over all, had a great time this year, so it sounds pretty successful to me. I’m starting to have problems separating the trips up since I’ve made so many in the last couple of years, first when we were checking out the school and now either fetching her for holidays or just visiting.
There were micros, mixed in with larger containers that were big enough to hold travel bugs and other swag. It was a good mix of different sorts of caches, with the scenery helping everything along.
This route took me through the delta region of central
And sorry I could not travel both
And be one traveler, long I stood
And looked down one as far as I could
To where it bent in the undergrowth.
Then took the other, as just as fair,
And having perhaps the better claim,
Because it was grassy and wanted wear;
Though as for that the passing there
Had worn them really about the same.And both that morning equally lay
In leaves no step had trodden black.
Oh, I kept the first for another day!
Yet knowing how way leads on to way,
I doubted if I should ever come back.
I shall be telling this with a sigh
Somewhere ages and ages hence:
Two roads diverged in a wood, and I--
I took the one less traveled by,
And that has made all the difference.
Pictures were taken at or near the following caches:
A Green Valley View by Sloigo
Old School by Pal_Al
Stop Staring at Me! by Momaqna
Take a Sit by Scooterman
Are we there Yet III? by Sloigo
Labels: back roads, geocaching, GeoDashing, Ribbit, Road trip, Route queries
Tuesday, May 20, 2008
Halfway there...
This weekend, I put over 1000 miles on my van driving up to Stockton to pick up the Musicmaker from her first year of college. I made it a little bit of a road trip and took a more scenic route going up to try and bag a few more counties that I hadn't cached in before. The route I'd planned was going to net me three more counties, which would have put me over the halfway point for Discovering & Logging California's 58 Counties.
As anyone knows who caches on a regular basis, things happen. And actually, this was a good thing. The first new county that I encountered on this trip was San Benito County. It's a smallish county located on the eastern side of the coastal ranges in California. The biggest town I believe is Hollister, which is probably fairly well known these days because of a brand of clothing. Anyway, the scenery in San Benito County was spectacular and I ended up spending way more time caching and taking pictures there than I had intended to, so I didn't get the other two counties. Except, the next day I had more time to kill, so I started caching from the other end of my Route PQ and found myself in Contra Costa County. I found two caches there, bringing my total of counties cached in to 29, exactly halfway to the 58 County Challenge. Now I just need to get to Northern California.
Labels: Ribbit, Road trip, Route queries
Wednesday, May 7, 2008
Future trips
My last road trip was a three day affair back in February to visit my daughter at her school. I’m heading back up there for another shorter road trip in 10 days time, to pick her up from school. I tell you it’s not fair. She started school the same day I did back in August and she’s going to be done a whole month before me, and she had a longer Christmas vacation too. Where’s the justice here? My older son keeps shaking his head when he found out she’s coming home next weekend. He keeps repeating the mantra, “One more year.” Yeah, well, then there’s four years of college and then all that free time ends.
I have found two caches in
I have no idea how many new counties I’ll add to my caching total with that trip. The return trip hasn’t been cemented in stone, so I’m not sure which ones we’ll be traveling through yet.
I just hope that I can get some good pictures on this trip. The last road trip, I got some pretty interesting shots, some of which I’ve posted here. I would imagine that
Carson Hill: A Very Historical Place - by tmkbk & olympicwannabe
Beam Me Up - by Ktquilt
Mariposa History - by halfdome and shortcircuit
Mr. Mother Lode - by Uncle Al from Sacramento
Labels: geocaching, GeoDashing, GeoVexilla, Ribbit, Road trip, Route queries
Monday, February 11, 2008
Road Trip Part II
Now that the route queries have been set, the puzzles have been solved and the reservations made for the first night’s stay in
England Needs Geocachers Geocoin – this one is a non-trackable geocoin, with a travel
bug tag attached to it.
Yellow Fish
Team Ace Personal Geocoin
"Yantongshan, China" Unite for Diabetes Travel Bug – Funny, but I had this one late last year and placed it in a cache on New Year’s Day, only to find it in another cache. I guess it’s meant to be for me to take this one north.
Robin's Wildlife Muggles Red Wacker Geocoin
frotu33's Humane Society Geocoin
RShetley's WMA Vest Geocoin - I met the owner of this coin at the event on Sunday and realized that I've known his dad for about 20 years or so, as he teaches in the school district just north of me. Small World.
Nickell Geocoin
Proximity Guideline Geocoin – I was given this geocoin by the owner to take north with
Photogal64's Jailbreak Geocoin
All will get some nice mileage bumps before their final placement. I also know of a couple of caches in the Coalinga area that I’ll be traveling by that have some geocoins dropped by a friend of mine. I plan on grabbing those and moving them further north to other caches.
The one drawback to taking geocoins and travel bugs on a trip like this is the possibility that they’ll get taken from a cache before I’ve had a chance to log them into the cache in the first place. Once on a camping/caching trip to Utah, I attached little notes to each travel bug that I dropped saying that if they were picked up, please wait until such and such a date so I could successfully log them once we got back from our camping trip. One person didn’t heed that advice, while two others did. The one person who didn’t follow the note, dropped the travel bug into the cache that I’d put it in anyway, so it still got the mileage credit which was my purpose for the notes in the first place.
This time, I’ll probably be taking a lap top with me, to make my logs at the end of each day and possibly post something here as well on a nightly basis. Hopefully, there will be some hot WiFi spots that I can take advantage of from my motel room, so I’ll be able to log the day’s finds. I know there’s a hot spot at my first night’s stay, but I’ll be staying in a new place on the second night and so won’t really know until I get there. I guess, I’ll just have to play that one by ear.
Labels: Events, Geocoins, Ribbit, Road trip, Route queries, travel bug
Wednesday, January 30, 2008
Road Trip
I graduated from college with a degree in geography, so I love maps. I’ve always loved getting out the atlas and pour over the individual state maps and see where I might want to go next on a vacation. Where was our next road trip going to take us? Should we take this road, or that one? I wonder what this town is like? Next month, I’m planning a road trip to
There is a mystery cache in
of the summer. Anyway, this series of articles is just designed the document the road trip.
This particular road trip took some advanced planning. I decided that this one was going to take the scenic route, so I’m going to be traveling on a lot of back roads this time, which is fine with me, but making the route queries for this one took a little bit longer. After searching the geocaching data base, I was only able to find this one route that fit my needs for any part of the trip. All the other routes, I had to create. In the end, I have 8 different route queries that I’m going to have to run right before I take off on my road trip. That also is going to take some planning since I can only run five per day. I need to remember to run at least three of them two days before I leave, otherwise I’m screwed.
My next step has been to go through each route and check out the mystery/puzzle caches to see if I can solve some of the puzzles and get those. Interestingly, there don’t seem to be a whole lot of puzzle caches, but I have gone through and solved 12 puzzles for the upcoming road trip. Several of them are right along county lines and involved looking up local history for each county. Right now, I’m a little bit more knowledgeable about Calaveras, Amador,
There was a puzzle cache that used Pig Latin, one that used the symbols from a computer keyboard, one that had me investigating a certain government agency within Kern County and two cipher puzzles. All of these puzzles have been solved, now my next step is probably going to be to whittle down the list. I have over 500 caches right now, and since my GPSr doesn’t have a memory card slot, I need to get that down to under 500 waypoints for them to all fit in the unit. Once I load all the queries into GSAK I’ll start by eliminating the puzzles that I haven’t solved. That will probably do the trick, but if it doesn’t I’ll then probably drop the multi-caches. I like multi-caches, but they tend to take a little bit longer to find than regular caches and I do have some time constraints so it makes sense to drop them next.
Tick, tick, tick, tick, tick, tick, tick, tick, tick, tick, tick, tick, tick, tick, tick.
Labels: Delorme Challenge, GSAK, Map, mystery caches, Ribbit, Road trip, Route queries
Monday, January 14, 2008
To route, or not to route, that is the question
When I first started geocaching, I was strictly a paper kind of guy, since I had an old school GPSr Garmin 12. No computer connection with that one, so every coordinate had to be entered by hand. Make one mistake and your searching far away from your intended cache.
Once I got the new GPSr - yeah it's still a Garmin - and a PDA, I went paperless. It was great having the nearest 500 caches in your GPSr all the time. Going out on an errand? Oh look! There's a cache over there. I took my daughter to a music audition and she "gave" me permission to find a cache before we came home. That was assuming that I had my GPSr with me she asked. I gave her a wry look and off we went, to find a really nifty lamppost cache. Well, the cache wasn't nifty perhaps, but the surrounding landscape was very cool, a sculpture made from some of the remnants from the Northridge earthquake from about ten years ago. The power of Mother Nature is awesome.Now where was this going? My youngest is the only one who caches with me on a regular basis. Every summer, we'd pick a place to go camping and then we'd start plotting out which caches looked good to get. Then, I'd print out the cache pages and we'd have a stack of 15 to 25 cache pages that we would attempt to find. It was not a very efficient way of caching. If we couldn't find the cache, that was one cache we couldn't find and we wouldn't necessarily have any other close caches to find because of our paper stack. Throwing away those printed pages, was almost like throwing away a friend. Our best trip was a camping trip we took to Utah and Nevada where we ended up finding 18 caches, many of those were locationless caches (before they'd been archived out of the system) and virtuals.
This past summer, we decided that we'd be camping at the Grand Canyon and surrounding areas down near Flagstaff. I'd played around with the Google Routes in the past, but this was the first time I actually put the route query into play. From our area in Southern California, I ran my first route from Barstow, CA to Cameron, AZ, which is north of Flagstaff. I'd originally thought of just sending it to Flagstaff, but I couldn't get Google to create a route the way I wanted to go if I stopped the first route in Flagstaff, so I had to make the route a little longer, so it would go the correct way.From there, I created a second route from Cameron to Grand Canyon and then I created a third from the Grand Canyon to Williams, AZ creating a large backwards shaped P lying on its back across the Arizona landscape following Interstate 40 and other Arizona Highways with the footing of the P in the eastern California Mojave desert.
I then saved the routes from Google, uploaded them to Geocaching.com and then ran the queries. With the route, I was able to set parameters, like how far off the route do you want to search? What kind of caches? I set the width at 2 miles figuring we wouldn't be doing off roading and also figuring that some towns that had been bypassed by the Interstate, might have some interesting caches, but might be more than a mile from the Interstate.
Once that was done, I then did some spot queries to fill in gaps. I ran one around Flagstaff, since we'd be spending some time there and one around Grand Canyon since I noticed that the route didn't pull in the four virtuals that were in the western part of the park, more than 2 miles from the route. With that done, I then loaded all the queries into GSAK and found I had 429 caches for this seven day trip. I knew we wouldn't be able to find all of those, but it was nice to know we had those available to look for depending upon where we ended up going. I figured that if we found 5% of the ones in the GPSr, we'd be doing pretty well.
Once we started on our trip, it became evident that we'd find a lot more than that. We found four on the first day without any difficulty at all, just stopping at rest areas along the way. Using the old way of searching Geocaching.com, we might not have even noticed all of those caches along the road. This way, all we had to do was watch the GPSr and let it do the work for us as opposed to the other way around. "Oh, look Dad, there's a rest area up ahead with a geocache. PDA cache page says it's an ammo can!" Yep, we're going for this one.
In the end, we ended up finding a variety of caches of nearly all types - some puzzles, some virtuals and a lot of traditionals - for a grand total of 43 caches in six days. That was double my original estimate and a pretty good average of 7 cache finds per day. Yeah, we probably could have had more, but we also took in the views as well. This was the first time I'd ever used a route query and I was hooked. One of the nice aspects of the route, was you had a full set of caches at your disposal, not just a couple that you'd printed out. If you couldn't find a particular cache, it wasn't going to be the end of the world, because you knew there were others close by. Just do a search with your GPSr for closest caches and pick another. That was especially handy when I had the kid in tow. He wanted to find caches. This made it much easier.
I've used a route query now four more times, with varying degrees of success, but always with better success than just picking caches that "look good" while looking at areas that you might be near. My last trip, this past weekend, I was able to find 5% of the caches that I uploaded into the GPSr and if I'd been a little bit more patient in my search techniques, the results would have been higher. Getting back to the title of this article - I know what the answer will be for me in the future.
Labels: camping, Grand Canyon, Ribbit, Route queries