1 Million PQ's

[+trainlove]

Do I understand that there have been over a million PQ's based on this filename for a recent one of mine?

1100725.zip

I think I smell burning hampster fur.

[BRTango]

Do I understand that there have been over a million PQ's based on this filename for a recent one of mine?

1100725.zip

I think I smell burning hampster fur.

 

I don't believe they are numbered that way. Someone else can probably speak with more authority, but I know that my "My Finds" PQ's all have the same number. So if they are numbered sequentially, then there have been many more than that (if you include all the My Finds PQs that have been run).

[+trainlove]

I don't believe they are numbered that way.

 

I think you are partially right, My finds is numbered with your super secret geocacher ID code number.

But I think ALL other PQ's are numbered sequentially, well, I've never done one Along a Route but it's probably the same.

 

P.S. My spidy sense is tingling, within a minute of my posting this question, there were at least 10 viewers of the post. Are lurkers watching me? Or is that just how fast that some posts get read?

[Keystone]

You're correct; pocket queries are numbered sequentially as they're created. Your "All Finds" PQ retains its number, just like the saved queries in your list. The queries I've used since late 2002 have four-digit numbers and the ones I created last week are numbered higher than 1,000,000.

 

It's important to remember that many queries ran once and then were deleted, or are sitting on people's lists, waiting for the checkmark that launches them to run on the selected day. I have queries that are several years old that have never been run -- I use them simply for the online preview feature.

 

There are not 1,000,000 queries actively running each week!

[+trainlove]

There are not 1,000,000 queries actively running each week!

 

I didn't think that, but I'm sure that others reading the post might misunderstand.

 

If 1 million PQ were run a week I think the hampsters would go on strike.

 

Yes, there are more or less than a million that have actually run, some as you say are created but never run, and My Finds is run by thousands of cachers each week. But my guess is 2 million actual total runs since 2000.

 

Oh, I never did check to see if My Finds's zip name is my super secret geocacher ID but now I know that idea is wrong. It's just the sequential number generated on the day I became a premium member or the first day I ran My Finds.

 

thanks

[Guyute1210]

My Finds query number is in the 900k range, and my super special number is not.

[+welch]

There are not 1,000,000 queries actively running each week!

 

I didn't think that, but I'm sure that others reading the post might misunderstand.

 

If 1 million PQ were run a week I think the hampsters would go on strike.

 

Yes, there are more or less than a million that have actually run, some as you say are created but never run, and My Finds is run by thousands of cachers each week. But my guess is 2 million actual total runs since 2000.

...

 

I don't think PQs were available in 2000 or 2001... at least I wouldn't think so since paid memberships weren't offered till March 2002 ??

[+ZSteve]

You're correct; pocket queries are numbered sequentially as they're created. Your "All Finds" PQ retains its number, just like the saved queries in your list. The queries I've used since late 2002 have four-digit numbers and the ones I created last week are numbered higher than 1,000,000.

 

It's important to remember that many queries ran once and then were deleted, or are sitting on people's lists, waiting for the checkmark that launches them to run on the selected day. I have queries that are several years old that have never been run -- I use them simply for the online preview feature.

 

While I really like the route queries, I wouldn't be surprised if these are really adding to the numbers. With a normal pq, I can go edit the criteria and effectively use the same numbered query for a different area or purpose over and over again. With a route query, it's seems to be a one shot deal - that route only. A lot of the routes that I run are ones that I either travel only once or infrequently. So, in order to work within the 40 query limit and/or the 500 cache per query limit, I generally have to delete route queries after each trip. I may need them again, but those will be a new query and therefore a new corresponding number.