PG-C seem to freak out when a cache has more FP than logs.

Question

I think this would qualify as a bug?

As we know FPs don't dissapear when you delete a log. Because of this we now have a cache with 5 "found it"-logs and 10 FPs. I checked on Project-GC and in the Statistics-> Top logged this cache has 5 logs. In the Statistics->Top favorites it has 10 FPs. So far so good. However, in the Statistics-> Top favorites (%) and in the p-gc script it has 60% FP? This should be 200% (correct) or 100% (maxed out, like geocaching.com does it). Where p-gc got 60% from I have no idea?

The cache Im talking about is https://coord.info/GC7D1GP

Comments

This is very special indeed and normally I would not have thought this would be possible but as you describe it is probably the only way. The 60% can only result if p-gc counted only 3 of the 10 FPs so maybe, by some hidden feature, the deleted logs do not go into the percentage?

---

I checked and you are right, p-gc is of course smart enough to only count the FPs from the actual logs in the percentage. So yes, confusing but I guess this solution (correct %, all the FPs) actually is the one that makes the most sense.

---

Ohh, then that already was an answer ;-) Thinking about it, you could get the same result by any multiple of 3 and 5 but that would have required that 2 FPs have been withdrawn while you deleted 15 logs. Interesting though that percentage is calculated this way.

Answer 1

I honestly did not know that one could boost a geocache's favorite points with such exploit.

What Project-GC does is quite simple.

1. It checks how many users have given an FP. A log is required.
2. It checks how many have logged it, or have given an FP (and has a log). The second part is if they were premium while handing out the FP, but the FP expired.

For this cache, it results in 3 users giving an FP, and 5 premium users logging it. 3/5 = 0.6 = 60%. A number that actually sounds quite correct.

I am surprised that Geocaching.com doesn't handle it correctly though. Is this a new issue? I haven't seen a single geocache where the percentage at Project-GC doesn't agree with Geocaching.com before, and have not heard about this issue, therefore I am quite surprised.

Since I think Project-GC does it in the correct way (which you seem to agree with after understanding what's happening, from reading comments) I don't think we will try to change anything here.

PS! It's super nice with a geocache that doesn't have 50+ logs when analyzing FP issues. Quite fast to calculate this one manually.

Comments

I've seen geocaches that have the wrong percentage before because of the same reason. It was about april or may last year when I first realized that geocaching.com don't delete the FPs when a log is deleted and I know that cache also had diffrent percentage from pg-c and geocaching.com. However I didn't think of it as a bug that time because the cache had so many logs so the diffrence in percentage was pretty small. More like 63% vs 64% which I thought might be due to pg-c not having the latest info on the cache or the exact number beeing 63.47% or something like that and pg-c doing the correct math and geocaching.com beeing nice with the numbers. ;)

And yes, you are right, nothing to fix here. I was outsmarted by pg-c once again. :)