Pocket Query Logs

[+imajeep]

When I generate a pocket query, whether it's a query from a bookmark list or a custom query, the five most recent logs are included. I don't see a default or a setting to increase the number to, say, the ten most recent logs.

 

Is there a way to increase the number of logs returned in a pocket query? Can the default number be changed? Thanks!

[robertlipe]

It's been much requested over the years, but "five" is the number.

 

Well, except for an AFPQ where it's your logs only or when you have logs on the caches returned by your PQ where it's five plus your logs.

[+imajeep]

Thanks! Please add my request to the wish list.

[+Miragee]

If you use GSAK, it will keep adding up the Past Logs, so in time, you will have lots of Past Logs. If a cache has been visited 12 times, since the cache was added to the database, I get all 12 logs in Cachemate when I Export from GSAK for my Palm.

[+StarBrand]

Just curious, why do you need to see any more?

[+Miragee]

Sometimes it will be that eighth, or tenth past log that reveals the little hint that allows you to find an elusive cache . . .

 

That is especially true if people have not deleted their "Bug Drop Logs" and only two of the five Past Logs have anything "vital" to say . . .

[robertlipe]

Why do you need more than five? The following log sequence is

fictitious, but certainly not contrived.

 

Cacher1: TNLNSL found with PowerTrain from Bubba's coords

Cacher2: TNLNSL found with PowerTrain from Bubba's coords

Cacher3: TNLNSL found with PowerTrain from Bubba's coords

Cacher4: TNLNSL found with PowerTrain from Bubba's coords

Cacher5: TNLNSL found with PowerTrain from Bubba's coords

Buibba: Called the placer since we just had dinner. Said he made

a typo of a degree in the latitude, so I corrected that and was FTF.

Woo Hoo! What's 62 miles between friends?

 

Do you want to be cacher #6 in this parade?

 

I find it odd that the policy of this site is to discourage offsite databases except

when they compensate for deficiencies of the site....

[CoyoteRed]

I find it odd that the policy of this site is to discourage offsite databases except when they compensate for deficiencies of the site....

We get weekly PQs of our major caching area even if we're not caching simply because of the reasons you and Miragee mention. If the number of logs were bumped to 25 or 50 I'm sure that would satisfy the vast majority of us in this respect. Plus, it's not like our caching area extends in only one direction. If we only pull the area we're going on any particular week, even if it's every week, we'd still pull fewer PQs. Add that to the fact we wouldn't be pulling PQs on the week we don't cache and it adds up.

 

I did a little experiment to answer the difference in zipped PQ size. I exported a 516 cache PQ with 5 logs, 20 logs, 50 logs, and all logs. I've been keeping a running offline database since the inception of GPS style PQs.

 

After zipping:

• 5 logs - 749 KB
  
• 20 logs - 1,136 KB
  
• 50 logs - 1,297 KB
  
• All logs - a whopping 4,669 KB! Many of the caches have logs numbers well into the 3 digits.
  

As one can see bumping the log count to 50 logs doesn't double the size of the file (if this is typical) and is not much larger than 20 logs.

 

Tie this into a the scheduling portion of the PQ page and add "Send me a maximum of 50 logs per cache and uncheck the day of the week after the query runs" and you won't have folks automatically downloading PQs with 50 logs week after week. Otherwise keep the 5 log limit.