Hi. My first post, a new premium member, and new to geocaching--6 finds so far.
There was no way I could read all of the previous posts in this thread, but I skimmed because I was looking for an answer to a question I have regarding this same subject. I frequently go on dualsport motorcycle rides. These are typically 150 to 250 miles country road mini-adventures. I like to load all the geocaches that are in the area I'll be riding so they'll pop up on my GPS while riding...then I can hunt if I feel like it (and I usually do).
Before becoming a premium member, I would search based on a zip code or coords roughly in the center of the area I'd be riding. I'd get 100 to 500 results or so. At 20 per page, to download the waypoint files, I have to download 5 to 25 pages or so......then cut & paste the XML together to create one .LOC file to drop into my Garmin Trip & Waypoint Mgr. This works great, but of course I'm thinking...man I wish I could get all 300 in one download.
So I quickly read the premium member features and incorrectly understood that I'd be able to get result sets with up to 500 caches in one file. I see the query option---and that it has to be queued for batch processing.....yuck. I typically don't get around to loading up my GPS until the night before a trip. So I'm back to downloading one file per page for the result set....argh.
I apologize now for the length of this post, and I sincerely appreciate feedback from those of you with knowledgable replies and helpful ideas. Now I have some questions.....
What can you query with a Pockey Query (PQ) that you can't do with a normal advanced search? I'm sure I'm missing something here. I understand that I'll get a single file with up to 500 caches from the search results, but other than that...how is the search and ability to find data different from the advanced search? And..if they provide the same results (perhaps I'm incorrect), why can a person do an advanced search and immediately get back a result set (with pagination) yet a PQ must be queued up for batch processing due to server load? How is the PQ search any more load on the database and server than an advanced search?
The other point I might make is this--I'm a programmer--specifically a web developer of data-driven applications. If server load is the worry, understand that if you don't give the people what they really want, they'll get it other ways---often in ways that put more load on your server than would be caused if you provided the feature. For example, a solution I'm capable of developing, and would consider if I don't find any way to download 100 to 500 waypoints in a single download, is a page-scraping solution where my program runs the search, then automatically hits each page of the resultset, clicks All, and downloads the file. The program would of course then combine the multiple download files into a single data file. This would undoubtedly cause a greater hit to the server than if the feauture were part of the site's offering.
Hopefully you guys will explain that I simply missed the way to download a larger resultset as a single file! Let me say a huge THANKS to all that run the geocaching.com website. It's a very nice looking website and the speed and functionality are very good. I love the Google Maps API integration! What a great service to the community. I'm glad to pay the premium membership to do my part.