Groundspeak Forums: Pocket Queries by Date Published - Groundspeak Forums

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Pocket Queries by Date Published Feature Request

#1 User is offline   The K9 Crew 

  • Premium Member and Proud of it
  • Group: +Premium Members
  • Posts: 167
  • Joined: 06-August 08

Posted 03 August 2012 - 01:35 PM

Pocket queries are fantastic, it is possible to interrogate the database of caches in all sorts of combinations. Yet one very key feature appears to be missing and that is to be able to select caches by "DATE PUBLISHED".

It is currently only possible to select caches by "DATE PLACED" but if you are creating a Pocket Query for new caches in an area using "DATE PLACED" can miss out caches. For example I have a Weekly Pocket Query that runs to bring back newly published caches in the area outside of my Instant Notification Area. To do this I have set "Date Placed = Last Week" but any caches that were published last week but actually placed sometime before that will be missed out of the query for that week.

The key date for me is date published as that is the first date a cache became available to find. As there is a specific log type for "Published" it is likely that this information is in the Groundspeak data base and would therefore could be be added to the Pocket Query form.

#2 User is offline   StarBrand 

  • StarBrand - WNAG.NET
  • Group: +Charter Members
  • Posts: 18633
  • Joined: 30-January 02

Posted 04 August 2012 - 06:00 AM

Thats been mention before.

One simple solution is to setup a notification centered on that other area.

#3 User is offline   The K9 Crew 

  • Premium Member and Proud of it
  • Group: +Premium Members
  • Posts: 167
  • Joined: 06-August 08

Posted 04 August 2012 - 06:07 AM

View PostStarBrand, on 04 August 2012 - 06:00 AM, said:

Thats been mention before.

One simple solution is to setup a notification centered on that other area.


Thanks Starbrand, that is one solution for sure and thanks for the suggestion, I think that is all I can do at the current time, but it isn't ideal as you have to set up multiple notifications (as you can only do one notification per cache type) and it would be much better to be able to cover it off in a pocket query.

#4 User is offline   Joshism 

  • DFTBA
  • Group: +Premium Members
  • Posts: 1351
  • Joined: 01-January 10

Posted 21 March 2013 - 05:31 PM

View PostThe K9 Crew, on 03 August 2012 - 01:35 PM, said:

For example I have a Weekly Pocket Query that runs to bring back newly published caches in the area outside of my Instant Notification Area. To do this I have set "Date Placed = Last Week" but any caches that were published last week but actually placed sometime before that will be missed out of the query for that week.

The key date for me is date published as that is the first date a cache became available to find. As there is a specific log type for "Published" it is likely that this information is in the Groundspeak data base and would therefore could be be added to the Pocket Query form.


I would very much like to see this feature implemented as well.

Here's my situation: I am particular about what caches I want to seek so I keep a GSAK database for my entire state of caches that will interest me. I live in Florida which is pushing 40,000 active caches, but my database has less than 5,000.

I run a series of weekly PQs: for Earthcaches & Wherigos, for Wireless Beacon (Chirp) caches (my GPS is compatible), UV light requirements (since I own a UV flashlight), tree climbing caches (I've climbed more caches as a geocacher than as a child), etc.

If I run the weekly PQs for "Placed during the last week" then caches with more than 7 days between their Placed and Published Dates will never show up. If I run for the last month there is alot of redundancy each week and the are some caches from the PQs I don't add to my database. (For example, the Tree Climbing attribute seems to get misused on a semi-frequent basis; at least, I've been assuming that 1.5/1.5 caches with the Tree Climbing attribute are rated correctly and merely hanging in a tree.)

#5 User is offline   c-h-b 

  • Premium Member
  • Group: +Premium Members
  • Posts: 37
  • Joined: 21-March 07

Posted 13 May 2013 - 01:07 AM

This would be very useful!

COs often forget to adjust the "placed" date before publishing a cache (sometimes months after creating a new listing...).
Therefore the "published" date is a much more relevant information and it is quite annoying that it can't be used in PQs!

#6 User is offline   SwineFlew 

  • Nobody
  • Group: +Premium Members
  • Posts: 2910
  • Joined: 23-September 09

Posted 13 May 2013 - 10:39 PM

GSAK and API. Its out there. Work well for me.

#7 User is offline   The A-Team 

  • ...now in HTML!
  • Group: +Premium Members
  • Posts: 4047
  • Joined: 15-March 09

Posted 14 May 2013 - 07:11 AM

View PostSwineFlew, on 13 May 2013 - 10:39 PM, said:

GSAK and API. Its out there. Work well for me.

Hmm, it doesn't work for me. I thought I'd try using that function to see if it really uses the publish date, and not the placed date, but I couldn't get it to work. As soon as I change the "Publish date" dropdown to either "Between (Inclusive)" or "Equal to", it refuses to return any results at all, even if I'm 100% positive there are caches that fit the criteria. As soon as I turn off the "Publish date" criteria, it happily brings back a bunch of caches. Oh well.

#8 User is offline   SwineFlew 

  • Nobody
  • Group: +Premium Members
  • Posts: 2910
  • Joined: 23-September 09

Posted 14 May 2013 - 09:22 AM

View PostThe A-Team, on 14 May 2013 - 07:11 AM, said:

View PostSwineFlew, on 13 May 2013 - 10:39 PM, said:

GSAK and API. Its out there. Work well for me.

Hmm, it doesn't work for me. I thought I'd try using that function to see if it really uses the publish date, and not the placed date, but I couldn't get it to work. As soon as I change the "Publish date" dropdown to either "Between (Inclusive)" or "Equal to", it refuses to return any results at all, even if I'm 100% positive there are caches that fit the criteria. As soon as I turn off the "Publish date" criteria, it happily brings back a bunch of caches. Oh well.

I just tested those, and it doesnt work. Only the newer caches does work. This is very interesting. I think its more of a GSAK problem than GS.

#9 User is offline   tozainamboku 

  • geoyokozuna
  • Group: +Premium Members
  • Posts: 7449
  • Joined: 21-February 03

Posted 14 May 2013 - 03:36 PM

This seems to get ask for by people who want to get more caches in their offline database with fewer pocket queries. They usually discover that if they simply ask for new caches by date placed since some recent date that eventualy they miss some caches - either becuase the publication was held up for a while or the hider mistyped the date placed on the cache form.

Attempting to add all the cache in some large area as they are placed (or published) has another problem however. You are going to have many caches in your database that are archived. This is because Groundspeak has chosen to never return archived caches in pocket queries. So if you set up a PQ to look for new caches and for cache that have changed in the past week, you won't ever know when a cache gets archived.

Groundspeak's rationale for doing this is to probably limit the number of caches you can reasonably keep in a offline database. They would prefer that you access the site more often to get fresh caching data - whether this is by using a targetted PQ to get only the caches you will likely be hunting on a certain day or by using the Geocaching.com smartphone app.

The query by placed date allows you to split up the caches in a region by date to creat several PQs with less than 1000 caches apiece. By limiting you to 5 PQs per day, it would would take 8 days to get all the caches in Florida. But in Grounspeak's opinion you don't need to copy that much of their database. They probably feel they are being more than generous with the number caches they allow you to get.

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic