greibe

He's not using stale data. He's using the PQ to get the caches into GSAK, then using the api to periodically refresh them. He's missing caches because they have funny placed dates. The problem is that you can only set a date period for a PQ back to 1988. Presumably, no caches listed on the site have been place prior to that. The field is configurable by the cache owner, however, so it can basically be any date. Some people use strange dates as part of their puzzle, or a clue, or they just think that they'll be cute. As it is, I'm not sure that his solution is feasible as I don't believe that they have been tracking publish dates and the information is probably not in the db. There has never been a "publish date" in the GPX and it sure isn't in the api. Everything is based on "placed date". Thanks for your input, if the published data is not in the db, then the only option left for Groundspeak is to not allow placed dates before current date. I think I will continue to only run pg's for new caches and then now and then run all my pg's for older dates. I will always miss the caches with dates before the possible search from date in the PG, but anyway there are plenty of caches out there;-)

Right, it is 26 queries to many, but I meant 10000's saved for Groundspeak. There must be 1000 of geocachers all running 25 or more PG's every week just to get caches with 'wrong' placed date - if we could trust the placed date we all needed only one to run every week getting last weeks changes. Also requires that gsak refresh cache data is used before downloading to gps in order to get the last status and remove archived caches - so not everybody might reduce their pg's - but anyway;-)

Until now I thought I could make my PG's for Denmark by splitting on placed date and then when it has ran once, I could use the 'update cache data' in GSAK to refresh data. So I only needed one active pg. Now I discovered that the placed by date is not trustable and that people can add the date way back in history, so I need to rerun old pg's. If this was changed, so the date placed was right, or change PG search so we can search on published date, Groundspeak could save 10000's of PG's to run every day - and I and many other would only need to maintain a single pg for new caches. Or, is there another way I can accomplish the same?