Suggested changes in Pocket Query defaults

[+jim_carson]

Suggestions I sent to geocaching.com, who recommended I post them here for discussion. I am not sure what the protocol is for this, so bear with me.

 

Suggestion 1. Change the default filter options. Nearly every time I create a PQ, I find I always change/select:

• I haven't found
  
• Is Active
  
• Are not on my ignore list
  
• I don't own
  

The first seems like it should be the default because one can run the weekly "send me all of my finds" PQ and not have to work around the search engine limitations (<= 500, geographical area). The second one is pretty obvious. Without it, you'll get caches that are temporarily unavailable, which is very annoying when this happens in the field and you don't have paperless capabilities.

 

The other two options are primarily conveniences from having to delete caches after loading the PQ. The ignore list should be ignored unless specifically specified otherwise.

 

Suggestion 2. Change the default options for Terrain and Difficulty. The current default is unticked with "greater than or equal to" and a value of "1." I often find that I'm selecting Terrain to filter out caches requiring special equipment (e.g. boats). If I'm in a hurry, I sometimes forget to change the "greater than or equal to" to "less than or equal to" and get something vastly different than I was expecting.

 

It'd be nice if the form were changed to have both to be "less than or equal" and "5." The unticked query behaves the same.

[+beejay&esskay]

The trouble with changing defaults is there are some (perhaps in the majority) who prefer the defaults the way they are.

 

One way to handle your situation would be to create a template PQ. Set your defaults in it the way you like. Then, when you want a new PQ, copy from the template rather than starting from scratch.

[+pppingme]

Just create a query with the defaults you like, then when you need to create a new one, instead of clicking on the new query link, copy your default query and edit away.

[+Markwell]

I think there should be some changes to the interface anyway to eliminate mutually exclusive criteria (example).

 

However, barring that change but I much prefer that the default settings return ALL of the caches and then each criteria added further limits the data. This is much simpler for the majority of users. With the current abilities if the default of "I don't own" is already checked and a newbie selects the "I own" - because they want to see their caches, if they then don't UNSELECT the "I don't own", they get zero caches.

 

It's much easier to explain to a new user that you'll get all the caches - at least the first 500 caches - if there are no criteria set. Then as you add criteria, each cache must fulfill the criteria (each cache must have travel bugs, each cache must be one you own, etc.). So while your defaults may aid you in speed, my guess is that it will constantly hinder and frustrate new users, who will then give up before coming here to the forums for an explanation.

 

I have no problem with the terrain and difficulty you've suggested, as it won't affect the default "gimme all the caches" status.

[+PLMerry]

I like Markwell's format. Except I think the middle box should add 'All caches except my ignores' as a third option. The 'Caches I'm Ignoring ' was probably a typo and should have been 'Exlude caches I'm Ignoring,' I think the option 'Caches I'm Ignoring' is good since it might be smart to review this list once in a while.

 

I also think the terrain and difficulty of >=1 or <=5 is a moot point. The result is the same either way.

 

I have to read through my PQ a couple of times to make sure all the logic is straight. Also after I hit submit, but before I check any of the days at the top I run a test and a Google map of the caches. I hate using one of my 5 PQs for the day just to find out that I got useless data.

[+DanOCan]

I like the idea of automatically excluding caches I have on my Ignore list unless I specifically select to have them included.

 

That being said, on those occasions when I create a new query I just copy an existing one so my standard settings come across anyway.

[+geomouser]

I'd like to see a check box added to the Pocket Query to allow Attributes to be included in the GPX file. As things stand now, I'd also add a warning note that checking the box is at your own risk, and may not work with all GPSr units.