Dieser Blogeintrag ist derzeit nur ein englisch verfügbar.
first let me say this: tb-run.com in general is working fine and the daily updates from geocaching.com are running like a charm ;-).
In the last year, we did not have a single occurence where tb-run did a wrong calculation of the ranking – (as long as the information from gc.com was up to date and gc.com provided the right results).
Most of the mails regarding wrong ranking we get, can be tracked down to the fact that the race tye is set to a „fair“ race. This which will filter out movements by the same geocacher. You find a detailed explanation in a previous blog post.
However, there is a problem right now:
As you all now, tb-run can only work with the mileage that is provided by gc.com. Since a few months, we experience a problem that seems to be related to what gc.com is showing.
We recognized that the mileage delivered from geocaching.com all of a sudden changes from time to time. Example
- For this old TB that was not moved since 2010, the log from 08/14/2008 shows 32.16 Miles – which is correct. Now two days ago, at 1:15 CET gc.com showed 5259.59 for this TB. And an hour later gc.com showed 377.03 Miles. At 3:15 then it was back to 32.16 Miles. At 9:15 it was 464.04 Miles for two hours and then it was correct.
- Or this Race TB from BNJanny (Upsstups)
Log from 01/17/2017 in Cache Kosinus meets China. Correct is 0.15 Miles. Yesterday all of a sudden gc.com showed 5266.23 Miles. One hour later it was back to 0.15 Miles.
It seems that these are not exceptions but this happens across geocaching.com.
We have written a program that pulls the mileage from gc.com every hour for several TB’s to see if we can detect any pattern. We are also checking if this is somehow related to tb-run.com – but don’t think so at this point.
We will update this post once we have any news – hopefully in the next few days.
If you have seen similar behaviour, please leave a comment. This may help us to track down the root cause – or give us more meat when talking to Groundspeak.