Category Archives: tb-run.com

Why does the mileage of my TB not show up correctly?

Update 30.July

After groundspeaks last update to gc.com the mileage bug should be fixed.
In case you still experience issues please try a “Recalculate Distance” first.
If there are still logs on gc.com where the milease is missing please let us know the public TB code.

We will now start the update process that updates all races. Should be done by friday morning (2.July) latest.

———-

Hi all,

since groundspeak did the last update to geocaching.com at the biginning of june 2010 we receive quite some complaints from you, asking why tb-run.com shows the wrong mileage for a TB.

Here comes the short answer

Due to a bug on geocaching.com we are missing the mileage of the last log.
As soon as a new “placed” log is added to this TB, the previous one is considered as well.

In detail:

tb-run.com does not simply use the total mileage that gc.com shows for a trackable. This is sometimes not correct but even more important:  This number has all mileage – but we must only read the mileage that occured during the race of the TB (from start to end date of the particular race).

Thus, we collect the individual mileage that is shown behin every “placed” log – see screenshot:

And exactly here the bug on geocaching.com hits us.

For some reasons, in some cases the last log on gc.com does not show any mileage.
gc.com does consider it in the total mileage figure and it is also shown in the Google Maps Vie (“View Map”).

However, on the TB overview page that tb-run.com alway the mileage of the last “placed” log is missing- see Screenshot:

Our experience is, that also a “Recalculate Distance” does not solve this issue.

But:

As soon as a new “placed” log is added, the milease of this (now last but one) log show up. Again,  the mileage of the new log is missing (and so on).

We have informed Groundspeak about the issue and they have promised to work on fixing this.
Until then, we have to live with the problem.

“Recalculate Distance” Howto and why?

From time to time we receive emails asking why tb-run.com does not consider all mileage of a TB.  You can be sure that tb-run.com does the maths right – as long as we get the right information.

The information is only as good as the data we receive from geocaching.com. And sometimes, gc.com does not calculate the mileage correctly. The relevant miles for tb-run.com is not the total mileage you see behind “Tracking History”. tb-run.com gets the data from each mile number for the single logs. And especially there, gc.com does forget some data from time to time.

Ususally it helps if you execute a “recalculate distance” on gc.com:

  1. Lookup your TB Details page, e.g. http://www.geocaching.com/track/details.aspx?tracker=TBABCDE
  2. Choose from the drop-down box that shows “Mark Item Missing” the entry “Recalculate Distance” (see screenshot)
  3. Click the “Go” Button
  4. Then it will usually take 1-10 minutes until gc.com corrects the calculation
  5. tb-run.com will update the race stats once per day.  After the next update, we will consider all miles we get from gc.com

Connectivity issues to gc.com fixed

We have just solved the connectivity issues from tb-rescue.com and tb-run.com to geocaching.com.
The Update of the TB information and positions will take a while – until 6 AM GMT (we do reduce the connection speed on purpose).

From tomorrow on, everything should be back to normal.
Only the creation of new rescue requests taked 5-30 seconds instead of 1-2 secs because we need to gather more data after the recent changed on gc.com.
We will be working on optimizing this in the next weeks.