sometimes it happens that a race participant complains about the ranking list not being correct. In this case please, take a look at the following points.
If there are still things unclear after review, we are happy to answer your message at email@example.com.
- Only the mileage after start of the race is considered.
- In case a TB was added to the race after the race started, only the mileage is valued from the date, the TB was added.
In case you want to adjust this please, contact the race-organizer of your race. A simple email from the race-organizer is enough and we will adjust this manually on request.
- At the bottom of the race list, you will find the date of the “last complete update” from geocaching.com.
In case this is old, you will usually see the next update happening within 24 hours.
- As we are not just considering the total mileage but only the mileage since race start (see 1. and 2.) the value “total mileage” from geocaching.com is not relevant (see Screenshot).
- Instead of considering the total mileage tb-run reads the single logs mileages from the log history (see screenshot).
In case geocaching.com does not show the correct mileage here, it sometimes helps to run a “recalculate distance” from the detail page of your trackable on geocaching.com (see screenshot).
If this does not help there is unfortunately nothing we can do about it from our side.
- Here, multiple logs from the same “Mover” will be excluded on purpose. You can find the details in the rule section.
This works pretty well and reliable.
In case you are under the impression that something is not valued correctly, please contact us.
With race type “race to cache” we calculate the distance from the current to the target cache. In the following cases it can happen that the distance is temporary not calculated correctly:
- The TB was just added to the race – tb-run.com will update the data from geocaching.com once per day.
- There is no ‘placed’ log for this TB yet. So we cannot find out where the TB is located..
- The last ‘placed’ log was in a archived cache.
- The last ‘placed’ log was in a ‘Premium Member Only’ Cache.
In all these cases, the situation remains only temporary and the correct position is calculated once the trackable moves to the next cache,
In case you still have questions please contact us with providing the race name as well as the (public) TB case at firstname.lastname@example.org.