Beach to Battleship

Does the bike course have any mileage markers on it? If so, what is the distance between markers?

For those of you that did last year HIM distance, did the course measure long or short compared to you bike computer?

Yes ... there are mileage markers. They were WAY off last year. I really hope they get it right this year. The event was an A+, but would have been an A++ if they hadn't screwed up the mileage on the course so badly and if they hadn't messed up with the water taxis. Aside from that, it was all aces!

I was doing the bike leg of a relay and had a "wildest dream" time in my head. When I passed the sign that said I'd covered 100 miles, I figured my "wildest dream" time was out the window. Too much distance to cover and not enough time. I just kept my steady pace and pressed on. Turns out I wasn't near that far from the end. The next thing I knew, I was seeing things that I knew were only 2 or 3 miles out. If I'd known I'd really covered more like 105 miles when the sign told me I was at 100, I'd have really gunned it the final miles and I'd have made that wildest dream time -- probably by a decent margin. As it was, I missed it by 90 seconds and it ticked me off.

I believe they're supposed to have signs every 5 miles per USAT rules.

I've actually been wondering since last year if the bike course for the full was, in fact, 112 miles. I know from 100-110 was only 6 miles according to my computer. A few people were commenting on that in the changing tent prior to the run. The course could have been 112 in total, though, I guess, and that portion may have been used to make up for miscalculations in the first 100 miles. I had it about 4 miles short, but I'm sure the computer I had then probably was not perfect. I ask, because if this year's course were to be 4 miles longer that could easily add 10-12 minutes compared to last year's bike and overall splits.

RunRun wrote:I've actually been wondering since last year if the bike course for the full was, in fact, 112 miles. I know from 100-110 was only 6 miles according to my computer. A few people were commenting on that in the changing tent prior to the run. The course could have been 112 in total, though, I guess, and that portion may have been used to make up for miscalculations in the first 100 miles. I had it about 4 miles short, but I'm sure the computer I had then probably was not perfect. I ask, because if this year's course were to be 4 miles longer that could easily add 10-12 minutes compared to last year's bike and overall splits.

My garmin said 112 on the nose.

My garmin also had it right at 112 miles.

I have noticed with both my bike computers and both GPS systems that there are discrepancies. My bike computers have been Cateye Micro 8 and more recently a Cateye Micro wireless. I have programmed them according to the instructions and they both seem to be about .04-.05 miles short. Not much until you multiply it by 56 or 112. Both GPS systems (Timex and Garmin) read within feet every time I use them.

The difference may be due to tire pressures and sizes. Theoretically the number you program into your bike computer, when you select your tire size, should not change for a given size tire. But the radius of your wheel changes with tire pressure. I know this is splitting hairs, but over a long measured distance it matters. The computer figures distance on how many revolutions a certain size tire is SUPPOSED to make in a mile. GPS uses geostationary satellite signals to figure distance.

I trust my GPS over my bike computer any day. So I would believe the guys with the Garmins that say it was right.

Used a wireless Cateye last year in the half, and it was spot on at 56 miles, even after switching from clinchers to tubulars for race day.

I used a Cateye Strada and I always roll out my wheels/tires for calibration. I had the course spot on 112 miles.