1. How reliable is the information provided?
Significant time is invested in researching all of the data. While we cannot guarantee that every data point is 100% accurate, we can assure you that every effort is made to continually evaluate and update the information provided.
2. Why are there only half iron distance and greater events?
What about shorter races? There are a few reasons for this decision. Typically much more significant time, effort, and money is invested into half or full iron distance races compared to sprint or Olympic triathlons.
Secondly, based on our research, while triathletes often travel great distances for a half iron or iron distance race, for the most part, the same is not true of shorter races. For shorter, local races, triathletes are typically quite familiar with the courses, topography, climate and other potential race conditions. The same cannot be said of a far away race, possibly in another country, where the triathlete is likely unfamiliar with the course and climate conditions.
3. Why should I rely upon your elevation data compared to what is offered on the actual race site?
For elevation gain data, wherever possible, we calculate an average based upon an aggregate of many results utilizing a variety of devices. By comparison, most race directors are very busy and only have time to measure a course themselves one time. Or they utilize a popular web GPS mapping tool to plot the course and post the resulting elevation gain. Some of these tools, unbeknownst to the race directors, are often flawed.
4. How is the elevation gain data calculated?
Our results are based upon an average of many different users’ calculations. Furthermore, in order to protect data integrity we discard out outliers. For example, 18 competitors each recorded bike course elevation gains in a range of 3,000’-4,000’ but 2 racers each recorded 10,000’. The 10,000’ results would be discarded and not included in the overall average.
5. Which technology do you use to measure elevation gain?
Whenever possible our results are measured with a device that utilizes a barometric pressure altimeter. Based on our research, a barometric altimeter offers the most accurate representation of true elevation gain. This is best explained by Triathlon technology guru Ray Maker at his blog DC RAINMAKER: http://www.dcrainmaker.com/2010/05/understanding-sport-device-gps.html
6. What if I find an error or disagree with information or data provided on the site?
Feel free to notify us by completing a contact form. We will investigate potential discrepancies and do our best to respond directly to your inquiry.
7. I am a race director. I would like you to add my race to your site.
Please submit the contact form with the website link for your race and any other pertinent information.
8. I found the bike course to be much windier than what your site indicated.
There are likely two reasons for this. First, keep in mind all the data we provide is merely an average. Therefore, even though the average peak wind speed for race day might be 15 mph, depending upon the actual weather for that day, the actual wind speed could be 30 mph or only 5 mph. Secondly, all the data provided is specific to the host city of the event. Over the course of 112 miles a bike course can take the rider into differing geographies where it might be much more or less windy than at the start of the bike. For example, the Ironman Arizona bike course tends to be much more windy out in the open desert on the Bee Line Highway compared to the urban portion of the course in Tempe. However our data is compiled based on typical conditions for the city of Tempe and not the Bee Line Highway.
9. Your site indicated the water clarity to be good whereas I found it to be very poor.
Similar to wind conditions this is an average or expected result. It may be that there was a recent storm that stirred up a lot of sediment or sand the day before or the morning of the race.