beejay&esskay

so no, your idea to do a powertrail will not fall into this The powertrail is just a part of the protest. The rest is to not log any caches found that day as being found that day.

"We want to see how many geocachers can go geocaching on a single day! We've chosen 10-10-10, since the date represents 10 years of geocaching and 10 years of Groundspeak in 2010. Bring your friends, bring your family, bring your worst enemy (if that's what it takes) and let's see if we can beat the previous record of 56,654 accounts logging on April 18, 2010. Even one log counts since we are counting how many accounts log a cache rather than the number of caches logged." - newsletter Something struck me as funny about this considering the plan to hide count information when looking at logs and the angst about power trails. I think I'll do a power trail on 10/10 and not log it as found until the next day.

I think the "do-it-yourself" limit is 528 ft.

My guess is that there are still a handful of counties with no caches out there. There are some counties with very few caches, but I don't know of any county with no caches. Maybe Alaska. Not meaning to be even slightly snarky, but have you actually checked? I can't help but be curious... I know there are (or were) caches in every county for the 9 states I've completed. (Some,at the time, only had 1 cache.) And for the other 2 states I'm contemplating, I know there is a cache in every county (or was). So far we have one counter-example of a county in Hawaii. (Which, of course, disproves the claim of a cache in every county...how about "every county but 1"?) Any more counter-examples?

Any chance you asked for more than 500 caches? In which case, the file is waiting to be downloaded, it won't be e-mailed.

"Requests for specific content in the photograph (must include the visitor's face, for example) will be considered an additional logging requirement and must be optional. Cache owners may not delete the cache seeker's log based solely on optional tasks. Geoaware" - above The log will be reinstated if you appeal to the right person...not sure who that is. (Which is one reason I skip ECs that threaten impermissable deletions.)

I assume you mean "odd"? Not really strange if that is how they have the two PQ processes set up. From the data reported above, it surely is that way.

I think that is true. Just a few days ago I was thinking "Boy, it's been a while since we had a PQ issue". Give your PQ processes a little extra hamster chow as a reward. Not sure about Odd Regular...but I'm sure he had a good excuse for sleeping in.

I have 4 ("regular") PQs that run every Thursday. 2 of them have run. 2 others are still waiting to run. Since they normally run so early, I suspect there is some issue. At one point there were two different processes to handle regular (not route, not bookmark) PQs, one to handle the odd numbered and one to handle the even. Ran: 3391090, 3391092 Not yet run: 3391091, 3391093 Time to wake up the "odd" hamster?

I just had the same error message when trying to upload a route (GPX file).

My guess is that there are still a handful of counties with no caches out there. There are some counties with very few caches, but I don't know of any county with no caches. Maybe Alaska.

"Chances are?" The probability is over 50%? I think not.

No, you are doing nothing wrong. Route PQs return all the caches that meet the criteria. You can't predict the order.

Yes, and make it a separate paragraph. If you don't have a hint, leave it blank. Enter any hints or spoiler information below. ... I don't really need to be told "none needed".

I would support an optional setting to hide your find counts and another optional setting not to show you anyone else's find counts. Especially if that would end the idea of making it harder for those of us who want to see counts to see what is currently available on cache listings (except for those who want to hide.)

If the log is deleted, I don't think you are getting it in the PQ. I suspect you still have the log in GSAK and need to delete the log there.

GSAK doesn't delete all the logs that don't appear in a PQ and you wouldn't want it to. As you probably discovered, you just need to delete your erroneous log in the GSAK database.

GC184ZH

Looks OK to me. http://www.geocaching.com/seek/cache_detai...&Submit6=Go

Sounds slower than e-mail.

"As usual, the coords are just close enough to make you work a little. " - from a nearby "traditional". (And not posted by a "kid".)

That would be my bet. I used to have the problem until I was much more careful about not pushing the button to turn on backlight.

I just tried the link on the OP and got: The server at coord.info is taking too long to respond. I haven't had trouble with these links in notification e-mails. Firefox 3.6.6 [Edited to add: But just tried one from an e-mail and got the same error. http://coord.info/GC2AYT4 ]

The best place to get GSAK support is at that website: http://gsak.net/board/index.php

Oh, I missed 10. Could you post that as a new thread? "Bug 10 (Mynor) I skipped #10 in reporting bugs - Pinehurst" It would serve to amuse those of us who like self-referential posts. (And to address a MAGOR bug, could you add some text about what the bug is to the Topic Title or Topic Description. As helpful as it is to have you number the bugs you find, it would be more useful to see a short description.)