Cedar Point advice

Rev3 CP is my first IM, I’m not fast, and just looking to finish. I believe my training is there, but I want to see if I can get any course specific advice in regards to the Rev 3 Cedar Point full course. I grew up an hour or so away from CP, and visited many times but haven’t been there in at least 10-12 years. I’ve studied the Rev3 site course map and bike elevation, and I’m aware wind can be a factor as I have raced along Lake Erie before (Maumee Bay tri). Seems like mostly small rollers, some easy false flats and one or two shorter climbs. How does the marathon course hold out in terms of difficulty?

Any other specific advice related to this race from the course preview or last years racers?

Thanks

Ask on the Cleveland tri club site, the club has done several well attended course preview rides.

http://clevetriclub.proboards.com/index.cgi

Some friends of rode the course last week he posted it on Garmin Connect
http://connect.garmin.com/activity/108061758#.TlAq2mfIc94.facebook
I don’t know if this link will work for you or not
.

I did the Full rev last year.

I found the humor in the fact that the only climbing on the run was at the halfway and end :wink: (on the bridge back to the park) Also, if you are one of those “bottles behind the saddle” or other “loose” setup, watch it going out of T1, I saw a TON of bottles laying in the road.

It was a pretty great course overall IMO. Enjoy

I previewed the course last weekend with CTC. Nothing to note really on the bike course. Wind may be the biggest factor and “the hills” are very short and at worst a change to stretch. Roads are in good condition.

Water was warm and very flat. The biggest thing I picked up was that the entry to the swim has a prolonged shallow entry (100 meters) so dolphin diving will be a good skill to have in your bag of tricks. We swam further down the lake so I’ll take their word for it.

Thanks for the pointer to the garmin file. Your friend didn’t have elevation correction turned on, which scared the crap out of me for a second, because it seems to have doubled the elevation change on a loop to match the elevation changes for the total 112.