Ranking Caches by Favorite Points By %

[+edexter]

    I would like to see favorite point % listed rather than simply the absolute number of favorite points a cache has.  (I apologize if this subject has already be discussed to death, but a search didn't turn up a match).  The current sortable feature of total favorite points is great at identifying popular old caches but misses all of the new ones and all of the caches with relatively few finds.  Here's an example: a sort of the 900 plus caches on Cape Cod shows a wide range (from zero to many hundred) and the top ten percent of these have 36 fav points or more.  None of these caches were placed in the last three years and the median placement was in 2012.  If I had never cached on the Cape, I could easily find a large group of very good, very old caches to do by simply sorting by fav points.  However nothing in the past few years shows up.  Project GC has some useful sorts and ranks caches by county with the highest combination of % and finds which is pretty much what I'm looking for but it doesn't distinguish between active and archived caches as far as I can tell: the top 30 have four distinct color bars:  pale green, green, blue and black.  The Green ones seem to be caches I placed that are active.  The Blue one is a highly favored new cache, the Black one a highly favored archived cache.  That leaves 20 Pale Green bars with scores between 47 and 69 (very good).  Checking on each of these one by one is required to reveal if the cache is active or not (most are archived).  

I think showing and being able to sort by fav pt % would be helpful to identify relatively recently placed better than average caches.  What do you think?

[Keystone]

3 hours ago, edexter said:

(I apologize if this subject has already be discussed to death, but a search didn't turn up a match). 

 

Your own thread from 2022 is a good start.  There, you learned that project-gc.com has useful functionality based on Favorite Point percentage.  This API partner uses static data provided through the API.

 

Searching also turns up a number of posts, like this one, that explain the limitation.  Calculating favorite point percentages for a long list of caches for display in real time search results is too big of a drain on server resources.