[Todd300]

I just placed a new cache. It got published just before it went down. Don’t blame me 😛

Edit: As of 3:36pm, it’s up.

[Todd300]

I started caching after ALR’s were no longer required. Glad I did so then. I don’t think I would want to do ALR’s. I would rather just sign the log and move on. I would think some ALR caches would be on my ignore list depending on the requirements.

[Todd300]

I’m only a 3, but I don’t play much.

[Todd300]

Was that for the Cache Cow cache? I’m going back for it sometime this month and wanted to be sure you got that fixed.

[Todd300]

Thanks all for your replies.

I should be able to get the Nuvi next week. Bartrod showed me his in action when I was caching with him last week and I was impressed. I then borrowed my ex-wife’s nuvi when I went to Pike Lake. While I didn’t use any macros, I still did the plain Garmin export on GSAK and it did the job well enough for me to visit random caches in the Hartford-Slinger area as well as a few caches around my hotel in Milwaukee and it did a good job locating those caches, even finding a good parking spot for me.

So, many thanks to all of you for your posts on the Nuvi.

[Todd300]

Too bad the escapee does not have coordinates on him. A geocacher can find him – lol.

All kidding aside, is this guy still at large?

[Todd300]

I forgot about this list until today and decided to take a look. Job well done, TBC.

I was near Oconto County’s oldest cache a couple weeks ago. But didn’t know that at the time. Now I do.

I’ll be sure to check that out. Same for Brown County when I do another Green Bay run later this month when I get around to getting a nuvi.

[Todd300]

After hitting quite a few caches in the WSQ series as well as a few other cache series under different names, I’ve gotten used to it and have my own way of doing it.

Basically, when I’m war driving (i.e. driving and looking for caches within a certain distance, say a quarter of a mile) and I know there are WSQ caches in the area, I sort the cache list on my PDA by GC number.

So when said cache pops up on my GPS, I see the GC number, then refer to my PDA that has the sorted list by GC number and can easily read the description and go from there.

I don’t really see a problem going after caches that are part of a series.

I’ll be war driving a lot more once I get my own Nuvi. Currently, I would set my handheld to find caches roadside within 1200 feet and just drive until I see one pop up on the GPS, but that was hard to do for obvious reasons. So I often had to plan a route in advance for a cache run and that took too much time and it became tedious.

Then Bartrod showed me his Nuvi and how he could cache on the fly with it. I was impressed. I then borrowed my ex-wife’s Nuvi to give it a shot myself when I went to Pike Lake and found a few caches when they popped up on the Nuvi. The Nuvi itself also showed identical names cut off near the end, but it also showed the GC number in full and it was easy for me to refer to that number on my handheld so no problem.

I so can’t wait until I get my own Nuvi. Still searching for deals until I can find one, but that’s another topic.

Back on topic, If owners want to make cache names all the same, fine by me, I can work around it – no problem. I will be doing a series of my own soon as I find certain types of containers that I have in mind.

[Todd300]

@gotta run wrote:

Ok, still on this topic.

When you create a PQ, are you leaving caches that you have found in the PQ?

Our weekly PQ basically specifies “Caches within a 30 mile radius of our home coordinates that we do not own and have not found.”

Therefore, we do not receive “found” caches in the PQ.

Therefore, when we update the “Unfound caches” database in GSAK, it is not updating the caches in the existing database as found, because no new information comes through on those caches.

The only way I can see to let GSAK know what you have found is to load found caches in it, but loading ALL the caches in a 30-mile radius exceeds the number limit of the query.

Make sense?

Just run a “My Finds” PQ if you want your finds updated. It can only be ran once a week though,

[Todd300]

TBC, you will not be disappointed. It’s a tough hike up a steep hill and will be even tougher if done in the winter. I recommend doing it before there is significant snow is on the ground.

Take your time and pace yourself.

Good luck if you – or anyone else here – goes for it.

It’s a recommended cache for a milestone.

[Todd300]

Thanks for the congratulations. I just got back in town about a couple hours ago. I caught up on my e-mails, caught up on various forum posts, edited my photos and here I am.

Pike Powder was a challenge and I’m glad to get that one for my 200th find. It was very worthy of a milestone.

I posted some pictures. They are on my log of the cache in which Sandlanders posted the link to.

It will be a while before I get 300. I’ll be too busy to cache as often as I’d like to. But I do plan on making 300 a nice one too. Probably be fall before I get around to it. We’ll see.

And Mr. Greenthumb, yes, I’ll get up to Potato Lake for that new cache. When, I don’t know. But I’ll get up there. I plan on doing a short highway 141 run to grab a few caches that I missed on my last 141 run including the one you just re-enabled. I’ll do that new cache at Potato Lake while I’m at it.

Again, thanks to everyone for the congrats.

[Todd300]

Thanks, Sandlanders.

Hope to run into you on the trails someday.

[Todd300]

Favre: I’m retiring and this time it’s for good.

Vick: That’s cool, dude. I think you ought to think about getting into dog fighting in your retirement.

Favre: Um, no. If I wanted to play prison football, I’d go shoot someone, not do animal cruelty. Hmm..maybe I WILL go shoot someone. You got Ted Thompson’s address?

Vick: Nope. Sorry, dude.

Favre: Damn.

[Todd300]

Where can I find information on the Wisconsin Delorme Challenge? It sounds interesting.

[Todd300]

Way to go, TBC.

So that y’all don’t have to scroll down the page for TBC’s log, here it is.

http://www.geocaching.com/seek/log.aspx?LUID=6a6bb9dd-ad21-4226-9c28-2d20d4155f7e

Again, way to go, TBC!

[Author]

Posts