Due to changes on geocaching.com, the mileage of certain TBs is currently not displayed correctly on tb-run.com. This is relevant for race types “distance fair”, “long jump” and “Race to cache”.
We have fixed the issues today (May 8th). As soon as the TB receives a new log, the mileage will show up correctly on the following day on tb-run.com.
Sorry for the inconvenience
[deutsche Version hier]
tb-rescue.com service has been permanently discontinued as of January 2016. For details please see the annoucement.
Similar functionality is now provided by Project GC: .
Since Dezember 2009 tb-rescue.com helped to rescue 2311 Trackables and report 2878 trackables missing.
I would like to thank everyone who supported the project.
It was a lot of fun!
If you are interested, here is the initial Video about tb-rescue.com.
If you like fun with Trackables visit out other website tb-run.com.
it was a long back and forth but finally I have decided to discontinue the service of tb-rescue.com.
(tb-run.com will be kept)
Developing and running the site was a lot of fun and the feedback from the geocaching community was really great. But on the other hand, the usage of tb-rescue went down during the last year.
Changes made by my provider are forcing me to rewrite code which I can and do not want to do at this time. Anyway tb-rescue.com was never completely „done“ and thus never left the „beta“ status.
Moving it from beta to a real service and creating a stable service would be too big at this time. This would include changing to gc.com API which would basically mean rewriting tb-rescue.
I would like to thank everyone who contributed to this project, especially every geocache who helped the more than 2300 trackables.
With immediate effect, no new rescue requests can be created.
The domain as well as the tb-rescue banner will stay online until mid of 2016.
This decision allows me to invest my time into tb-run.com
Unfortunately I did not have the chance to maintain tb-run and tb-rescue during the last months. Other job-related as well as other private projects were the reason that I had almost no time to answer your emails. I feel sorry for that.
In addition, we experience some technical issues.
E.g. the tb-rescue ranking list was not updated. Rescue requests were not closed and rescuers did no receive credit for their rescue missions. This should be fixed now.
But we still see some performance problems with loading times of some of the pages. I am working on this but cannot make an estimation when those will be fixed.
Update 2014/05/02: 90% of the performance problems should are fixed.
Also it is currently not possible to change the watched area in tb-rescue. sorry.
Today, I will focus on answering your email.
As soon as I have any news regarding the current issues, I will provide an update via Twitter/Facebook/Blog.
I hope you have some understanding that tb-rescue and tb-run are just hobby projects and other private and job-related stuff has priority somethimes
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 firstname.lastname@example.org.
The following points are valid for all races that are about “who makes the most mileage” – “distance“, “distance fair” as well as “long jump“:
- 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.
The following point is valid in addition for “distance fair” and “long jump“:
- 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 email@example.com.