Starkacher

Whole-heartedly Agree. More filter options should include optional Latitude and Longitude limitations (None, Only lower limit, Only upper limit, Lower and upper limit) This can square off 1-4 edges of the "circle" and potentially make it a square. This could actually lesson the burden on the geocaching,com servers as people could run fewer pocket queries to cover an area. That is because they would not have to waste returning duplicate caches within overlapping circles. I have not thought through what happens for people on the zero (or 90?/180) longitude or longitude lines. That may need an OR option for the limits? A similar enhancement would be a distance range. Instead just <= a particular distance, add >= a particular distance (subject to overall individual PQ cache count limitations), or at least add a between X and Y distances. That way you could create Rings around earlier PQs in order to fully cover a desired area (again without having to have wasted/inefficient overlapping circles).

I wanted to load all caches within 100 miles of home (excluding Canada) that I have not found to GSAK. I tried to create a series of queries based on Placed Date Ranges and limited to the three states within that radius (since "United States" is apparently not a Country) and the query returned all the caches in the three states that are within the placed date ranges and ignores the radius limitation of 100 miles. The attempts are still in my Pocket query list since you will probably need to see all the settings.

I also have this issue with the Pocket Queries. I do not want to include Canada caches in a 100 mile radius from my home. To get around this, I selected the three states (OH, IN, MI) that are within that radius. However, the query ignores my 100 mile radius and returned all the caches in those three states that meet my criteria (other than the radius)even if they are 200 miles away.

I propose a change for the "Advanced Search" panel (http://www.geocaching.com/seek/nearest.aspx). Instead of the "By:" option always defaulting to "By Postal Codes", either, it should remember the last option the user had used, or the users should be able to set a preferred option on a search preference panel. I always need to change it to "By GC Code" and wait for the panel to refresh before entering a GC code. This panel is the most efficient way I have found to log my days activities based on the log file from my GPSr.