Pocket Query

[+Jimmy G]

I would like to see the Pocket Query filters for 'Found in the last 7 days' changed to either a specified number of days or to found since a specified date.

 

Seven days is often not long enough; last 30 days or since October 1st, 2012 would be better.

 

Thanks for considering this request.

[+doug_hollyNKC]

I think putting in a specific day would much better! 7 days doesn't do much at all, especially when in the hotter then heck summer months or two feet of snow on the ground winter months.

[+NanCycle]

I agree. The ability to specify a number of days for "Found" or "Updated" would be a useful feature.

[RuideAlmeida]

It is already possible to specify two different dates, to begin and end the search.

Please look at the bottom of the PQ request... "Placed during" and "Between".

[+Jimmy G]

I'm not interested in when it was placed, but rather when it was last found.

[RuideAlmeida]

I'm not interested in when it was placed, but rather when it was last found.

 

I bet that you can get some good results, if you set the field "That (And)", together with a large date margin on "Placed During".

Give it a try!

[+NanCycle]

I'm not interested in when it was placed, but rather when it was last found.

 

I bet that you can get some good results, if you set the field "That (And)", together with a large date margin on "Placed During".

Give it a try!

 

I bet that using the date placed you would not get anything close to what the OP is asking for. OP wants caches placed anytime that have been found within the last month (for example) but not caches placed within the last year (for example) that have not been found in the last 2 months (for example.)

 

Some of us get it, even if you don't.

[+Totem Clan]

I'm not interested in when it was placed, but rather when it was last found.

 

I bet that you can get some good results, if you set the field "That (And)", together with a large date margin on "Placed During".

Give it a try!

 

I bet that using the date placed you would not get anything close to what the OP is asking for. OP wants caches placed anytime that have been found within the last month (for example) but not caches placed within the last year (for example) that have not been found in the last 2 months (for example.)

 

Some of us get it, even if you don't.

Exactly

 

 

To the OP, I think it's a good idea. I don't think I would use it much because I use GSAK to sort my PQs.

 

GSAK will do what you want for now, but GC.com should consider this.

[+Jimmy G]

I'm not interested in when it was placed, but rather when it was last found.

 

I bet that you can get some good results, if you set the field "That (And)", together with a large date margin on "Placed During".

Give it a try!

 

I bet that using the date placed you would not get anything close to what the OP is asking for. OP wants caches placed anytime that have been found within the last month (for example) but not caches placed within the last year (for example) that have not been found in the last 2 months (for example.)

 

Some of us get it, even if you don't.

Exactly

 

 

To the OP, I think it's a good idea. I don't think I would use it much because I use GSAK to sort my PQs.

 

GSAK will do what you want for now, but GC.com should consider this.

 

Thanks. I wasn't familiar with GSAK. I'll give it a try.

 

I'm just trying to weed out caches that haven't been found in the last couple of months.

 

Jim

[+NanCycle]

I'm sure I would use this feature if it were available. I do not use GSAK and have no intention of trying it.

[AZcachemeister]

While I do see the value of selecting out caches that have been hunted in the last (time period) but not found (as in 12 DNF this month), simply selecting out caches that have not been found in the last (time period) because nobody looked for them seems not very helpful.

 

I must be missing something...

[+JL_HSTRE]

While I do see the value of selecting out caches that have been hunted in the last (time period) but not found (as in 12 DNF this month), simply selecting out caches that have not been found in the last (time period) because nobody looked for them seems not very helpful.

 

Some people don't want to search for caches that have no been found recently because of a increased chance of the cache being missing or at least more concealed (plant growth, etc).

 

Some people like searching for caches that haven't been logged in awhile, particularly a year or more (aka "Lonely Caches"). There is a simple novelty or difficulty factor for some, but there are also Challenge Caches that care about this. In my area, there is a Challenge Cache that you need to find a cache where the last Found It log before yours was more than 365 days ago. After qualifying for this cache on an infrequently solved puzzle, I decieded to make a list of other Lonely Caches in my region. I ended up with a list of 219 caches; after posting the bookmark list on the local forum at the end of November that list has been cut to 173, with over two dozen different accounts making finds (several of whom already qualified for the Challenge Cache). Clearly, there is some appeal in Lonely Caches.

 

Assembling that list was a small headache. There are 3519 active caches when I do the basic "caches near me" search from my profile (which I believe defaults to a 100 mile radius). That means a PQ isn't a viable option, even excluding caches published in the last year. I could try to run several PQs at different locations and hope I don't miss anything. Instead, I had to sort that list by Date Found, check the box to select all caches on the page, click Download All Waypoints, go to the next page, and repeat. There are only 20 caches per page when searching caches. If I wanted to make a list of Lonely Caches in the entire state of Florida instead of my 6 county "local" area, there would be over 800. Thank goodness I at least have GSAK to take all those LOC downloads, filter out counties outside my area, and upload them all at once to a bookmark list. Most people wouldn't want to deal with all that work.

 

If I could have a PQ option for "Caches Not Found In The Last Year" then suddenly my PQ is only a few hundred caches in a single GPX file instead of a bunch of LOCs.

[+frinklabs]

I found an only-lonely-online cache last autumn. It hadn't been logged online for a couple of years, but the logbook had more recent written entries in it. And they were definitely cachers, not random civilians, because one of them included "TFTC" in their written log.

 

Meanwhile, in another thread I suggest a hoped-for optimization to the alleged PQ interface overhaul:

 

Ideally, the new PQ interface will have an advanced mode where you could enter in pseudo-SQL statements much like the WHERE window in a GSAK macro, like this:

 

Difficulty = 1 AND Terrain = 3.5
OR
Difficulty = 1 AND Terrain > 4.0
OR
Difficulty = 1.5 AND Terrain > 3.5 

 

If that's too much, then a semi-advanced mode might work where you have the checkbox selection interface now, but the ability to add multiple instances of them.

 

 

It is slightly inaccurate. The pseudocode is actually in the GSAK Filter WHERE window; the macro equivalent would be the MFILTER statement.

 

If they did that, the PQ could include this:

 

LastFoundDate < date('now','localtime','-365 days')