There has been a rather spirited discussion on the FastRunningBlog message boards recently, debating which downhill Utah race course is faster: the new Utah Valley Marathon route, or the St George Marathon route. I am of the opinion that nothing can touch St George. Its downhill simply special, and you can flat-out roll on that course, especially the second half. I don’t think any other course will ever touch it in terms of speed. Nothing personal against Utah Valley, or any other race, but facts are facts. 
Other people, of course, disagreed with me (most notably the Utah Valley race director). They argued that the Utah Valley course has a better distribution of downhill. Although the drop is not as great, there is no Vejo hill and no Dammeron Valley hill, and the downhill is more even and mellow at UVM, thus granting less quad bashing and better times. Fair enough.
Still others pointed out the higher elevation of UVM in comparison to St George. The uphills at UVM would have a larger detriment than to those at St George. Fair enough.
After the UVM race concluded (June 12, 2010), the debate really didn’t resolve. Most people conceded that UVM might be just a little slower than St George, maybe a minute or two. I still held the opinion that it was 6-8 minutes slower, which brought on sharp disagreement. As with most running-related arguments (okay, all arguments), little progress was made over time.
This was all in good fun. I actually don’t care if I’m right or wrong, but it’s fun to talk about and fun to debate. Sorry if anyone took it personally. After all, being the fastest race doesn’t imply that it’s the best. But this whole discussion gave me enough motivation to update my Utah Marathon Comparison profile. I originally made this back in fall of 2007, right before the St George race. The chart compared the elevation profiles between 3 classic Utah marathons: Top of Utah, Ogden, and St George. I found it interesting to look at, and it has actually helped me in race preparation. Other people have told me the same. I’ve been meaning to add other races to it, especially since more and more local marathons keep popping up.
So yesterday I finally digitized the Utah Valley course, extracted elevations, and added the profile. I made sure to zoom in very tightly to make sure I got the route exact on the road and not up on a cliff or anything (an issue with canyon races). I then pulled elevations at a 0.25-mile interval, and used a 5-meter elevation model as the data source. Most states do not have 5m models available, but we are very lucky to have them here in Utah for most of the state. This is a high enough resolution to avoid most errors due to canyon walls, plus Provo Canyon is relatively wide compared to other marathon routes (ie - Top of Utah). So the elevations should be pretty good for UVM, much better than anything you’d get off of Gmap, MapMyRun, or any other USGS-based elevation web service. I also did an extraction at 0.1-mile intervals, which gives a bit higher resolution, but I ended up settling on 0.25-mile intervals in order to match the other three profiles that I made back in 2007. Using 0.25-mile instead of 0.1 would potentially “chop” some of the hills and valleys, which actually leads to a more conservative, smoothed-out profile. But when comparing uphills between these races, perhaps conservative is good.
I also need to mention that digital elevation models are generally bare earth, meaning that things like highway overpasses do not show up in the model. After all, there is ground under the overpass, and that is what is included in the model. Road cuts, however, do show up in the model, and the road cut is obvious in Provo Canyon. Long story short, the infamous “overpass hill” during the last mile of UVM does not show up in the profile, which eliminates an entire hill. I could have fudged it in, but I left it out in order to pad UVM’s numbers against St George a little bit, and also to send a hint to get rid of that hill in real life. 
Okay, enough technical gibber-jabber. The result is shown below. Click on the image for a higher-res PDF file. It’s easy to see that Utah Valley is indeed the highest elevation of all the marathons. It also has the most cumulative uphill (slightly more than St G). Again, these are conservative numbers. It has the second-highest total downhill and net downhill out of all the marathons. There are no hills as big as Vejo or as long as Dammeron at UVM, but its hills are still substantial in a few spots. Interestingly, if you compare the average finish times between all of the races on MarathonGuide.com, Utah Valley comes out as second fastest, behind St George.
The Utah Valley event is a great race, and there’s no doubt it’s a fast course. But how fast is hard to determine, and no amount of “stats” or elevation comparisons, or time cross-references, or anecdotes can really quantify it. There are a lot of variables that go into course speed, and on top of that, every individual runner is different, and will respond differently to each course. My strength may be someone else’s weakness, and vice versa. So again, this is all in good fun.
Anyway, enjoy the new profile chart. They are fun to make, and I certainly find them useful. At some point I’ll add the Salt Lake City Marathon and Des News as well, but I think I’ve got the four biggest marathons on there for now.
Recently I had the opportunity to create a course map and elevation profile for the 
