Pocket Queries Future? in Website Posted August 22, 2004 FWIW, I'll tell you how I use GSAK and the PQ system. I have regular GPX deliveries for found and unfound caches in my area coming weekly, and then more frequently for new and watched caches. When I am planning a trip, I start getting weekly GPX files for the area(s) in question. This is so that I can start preparing for the trip. I start marking caches which look like they are in the right location using GSAK userdata. Right before the trip I get updated GPX files, but the old logs are there in GSAK, so that when I am on the trip, I do have the full history of the cache. This is going to be important going to Orlando in the wake of Hurricane Charley. I usually set the number of caches to 500 just because I don't know the geography yet, and then I can fine tune it later. This was especially useful on my trip to England in July, as I had PQs centered on Cambridge, Waddesdon and London, and 500 caches out from Cambridge didn't really reach too far into Hampshire, but the London query gave me a bunch in Hampshire where we were for a few days. This environment is so dense that in the span of two weeks of short day trips we covered a bunch of different caching areas, but in a relatively small area. The current system for PQ doesn't really allow a lot of interactivity in terms of defining areas geographically according to a trip. Since I rely on GSAK to do that and there is no real integration as to GC.COM know which caches GSAK knows I'm filtering on, much info in the PQs is being wasted. I'd have thought that there are a number of ways to improve this process, but I do find that having the past logs is important - especially for very chatty logs on difficult local caches with a lot of no finds and notes.