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
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.
We just activated two new race types on tb-run.com:
In principal just as the normal distance race. But here, we only consider the first ‘placed’ log of every cacher. This prevents that cachers keeping trackables, dipping them in every cache and helping them to get high mileage. In case there is more than one log on the first day we will consider the one with the highes mileage on that day.
Also quite like the normal distance race. But if one cacher moves a TB several time we consider only the log with the highest mileage – the longest jump.
This prevents cachers keeping trackables, dipping them in every cache and helping them to get high mileage.
You can find a description of all race rules here.
A big “thank you” goes to team ‘WantedDeadOrAlive‘ for support and testing of the new rules.
In case of isses or questions please leave feedback in the blog comments or contact us at firstname.lastname@example.org.
Hi all. I know, I did not send a single life sign during the last month. Neither in the blog, nor as replies to your emails.
But I was completely snowed under due to private and business projects.
Originally I planned to use thewinter season to implement many ideas for tb-run and tb-rescue and be able to proudly remove the “beta” label from both sites.
But what can I say… I did not and still both sites are running with almost no issues.
I have the impression that 90% of all “my TB is stuck” cases are covered by the current tb-rescue technology.
The service has become well established and seems to be stable.
We receive lots of new rescue requests every day and our server sends out thousands of mails every day to potential rescue teams in the relevant areas. Seems like the western caching civilization is mostly covered – see Map.
The banner ads from Groundspeak on gc.com do supply us with new interested geocachers every day and we have exceeded 8000 registered users.
What else is on the todo list?
Well, first of all we have the topics that are most aksed:
- Watch more than one area
- Have nice statistics about the races
- And my main issue that tb-rescue does not handle some processes too well.
One example is: if a TB owner does not mark his trackable as missing, even though a rescue team has confirmed that its gone – (sigh!).
In this case, the rescuer does not get a rescue point and the request is kept open forever.
Ahh.. the „most Wanted“ functionality is still the creation of rescue request for TBs that are stuck at another CACHER. .
For this, please also read “Rescue a TB that is stuck at another geocacher“.
Well.. Other than that… The situation at tb-run.com is even better: Everything is working fine.
By now we have more than 500 races with over 3800 Trackables in total.
We dont have a standstill, improvements are just postponed
Thats it for now, Yours sincerly, Sascha
(currently crossing the atlantic during a flight… having some time to let my mind wander….)