Forum Replies Created
-
AuthorPosts
-
@gotta run wrote:
The only workaround to this I could see would be filtering any unfound remaining caches by GPX date. That is, if it is an unfound cache in your current working database and the record does not get updated with the new PQ, it would have an old date. Filter by dates, then take a look at any old dates to see why they were not updated.
I will sort the last GPX column to see if there is any caches that did not get updated with the last import. I have found two reasons so far why they do not get updated. Archived caches is the first one. Second, if your pulling the max number of caches in a query, as caches in the center increase, the once on the fringe will not be selected anymore. Not a huge deal for me since they are usually about 70 miles away, so I delete them too.
@gotta run wrote:
@SammyClaws wrote:
There is a way to use the file off your Oregon to update your GSAK database and mark the caches found.
Not that I’ve found. Oregon doesn’t make any changes to the GPX file and doesn’t seem to pass any “found” information back to GSAK either way, unless I am just missing it.
I’ll try to when I get home tonite to make sure, but I believe its GPS>Receive Waypoints – on that dialog box, I have mine set to ‘if matched update found status only’.
Wii want to add our congrats too! Heres to your next milestone
Congratulations on your milestone, what a way to tear up the stats page!
That is one wicked milestone Diane. Congratulations, we hope to see you in August and toast your achievement with a glass of suds!
There is a way to use the file off your Oregon to update your GSAK database and mark the caches found. But since we write our found logs in GSAK already, we manually update them. When we are done, we delete all the found caches.
And Team B method for keeping your database clean is spot on. Since I completely load my database with a series of PQs, I just delete the ones that have an old GPX date on them. You will find this method does delete some caches you want to keep, but that is because they land on the fringes of your PQ radius and newer caches are pushing them off your list.
My queries run twice each week, Monday and Friday, that way I pick up all the logs from the weekend and any changes to caches over the week. Its also my way around the 5 log limitation. In fact, I have just begun deleting logs that are over a year and a half old from GSAK.
Hope this helps
The Oregon does not have any way to “edit” the GPX file. It eliminates them from the unfound caches by comparing the found file to the unfound one. I think Garmin’s original intent was to load each and every cache individually as a seperate file then you can just delete the ones you found with using your computer. However, with a PQ or GSAK we are loading multiple caches in one file. Your only course of action is to re-run your query, delete your old GPX file and load a new one. I dont know if you use GSAK or not, but I keep loading the same file over the top of the old one, so that it always has all the unfound on it. It seems like a draw back not to be able to edit the file, but its really just learning a new way to do things.
Congratulations on your milesstone. I dont think there is enough memory to for me to post all 5000 of your smileys in this thread so I’ll just steal this from someone else 😀 x5000
@marc_54140 wrote:
The problem is so many caches do not read what is on the cache pages anymore. With CacheMate, GSAK, iPhones, Blackberries, Oregons or whatever, the coordinates are the only essentials. Evereything else is fluff.
(Puzzles are an obvious exception).
I guess I would have to disagree on your comment abou the Oregons. Now that we acutally have the cache page at our fingertips we read the cache page on our drive to the next cache. In the past, it was too much trying to juggle a palm and a GPS as the same time. However now its a couple taps of your finger, so with the Oregons we read the cache page far more than before. I think in the past, with less sophisticated devices, the coord were essential (or all that was available), but on the new devices its way easier to access everything.
Another vote for the Rayovac Hybrids – an entire day of caching, waas and backlight and an Oregon (i.e. battery hog). We use the Hybrids all over our house – remotes, thermostats, toys … There is always 4 of them charged up and ready to go.
We use a La Crosse Technology BC-9009 AlphaPower Battery Charger – not the cadillac of chargers but has many of the same features of the Maha one for a bit less.
I believe the intent is to see who’s paths have crossed yours. So we leave a tag behind for someone to pick up and keep, period. Our hope is that it gets logged and we can see who found the tag and where.
The fact is some people have picked them up and moved them to another cache to be found. Other were picked up and then logged and then placed in another cache (that had us scratching our heads for a bit). But most grab the tag, keep and log it.
We looked at it this way – since so many geo coins go missing, we’d beat them to the punch and go with the ones people can keep. We’re enjoying ours so much that we are working on another set.
We’ve done quite a bit of caching at night with headlamps along the Root River Parkway and in Whitnall park. I’m pretty sure you can cache Bong at night too. Some of the gates close at dusk but there are plenty that are open. I would look for caches that have a 24/7 attribute.
We’ve never purchased any coins to release into the wild for fear they would go missing. And the one time we did release a group of travel bugs the whole cache went missing afterwards. That is another story.
However, I don’t think coins get lost only from thievery. Some of it is because of mixing trackables in with tradeables. I’m sure we all have seen log where people talk about trading for a geo coin. In fact,during our first few outings geocaching, we were on track to find an ammo can. As we got close to ground zero, we saw 2 couples and 4 kids coming down the trail from the other direction. Being new to this and being not sure if they were muggles or what the etiquette was if they were cachers, we stopped and hung out a ways back. They continued on and found the cache and opened it up and got the log book out. The 4 adults stood around chatting and signing the log while the kids went through the ammo can and divided up the contents between them. As the parents put the log book back, the one mother reminded the kids to “put your quarters in for your trades”.
We grabbed the cache as the parents and kids with bulging pockets walked away, and sure enough there was a log book and 4 quarters. We found 3 more caches in the park in the same condition. So if there were any travel bugs or coins in those caches, they probably ended up at the bottom of a toy box somewhere.
Also having a mission statement attached doesn’t always help either. All of our travel bugs have a laminated mission card attached to them. Only half the time the movers actually read the card.
When you multiply all the layers of risk associated with coins it amazes me how many stay in circulation..
Oh yeah, that right, you like to just clean out all the caches on either side of you while you drive down the road.
The defined route is what had us not driving up the farmers driveway to get to the caches in the park behind his house.
We put the Usort number in front of the smartname before exporting them to the GPS. It makes it much easier to seperate them. We also use the usort number to define our routes.
-
AuthorPosts
