Tag-Archive for » Maps «

April 25th, 2010 | Author: paul
No Gravatar

Recently I had the pleasure of creating the event maps for the Cellcom Green Bay Marathon. This event, held in mid-May, consists of a marathon, half marathon, “mini” marathon (2.62 miles), and a marathon relay. The course is flat and fast, and good prize money brings in good competition year after year. Another distinctive about the race is that it starts and ends at Lambeau Field, and being a rabid Packer fan, I think that’s about the coolest race venue ever.

For this event, I created separate maps for the marathon, half marathon, and “mini” marathon, and also an “event-wide” map that shows all of the routes on one page. I included the marathon relay on the marathon map.  One of the challenges of mapping an urban marathon is getting the street annotation to be complete, and look good at the same time. For this task, I used the Maplex labeling engine, an ArcGIS extension. Maplex worked wonderfully for my first pass on the street labels, and although I still had to do my fair share of manual labeling and tweaking, Maplex definitely helped create a higher-quality product.

 

I’d love to run this race one of these years. If I can’t get a Trials Qualifier time at Chicago this fall, I’ll likely take another stab in Green Bay next May. Based on the elevation profile, the course should be a flier.

April 12th, 2009 | Author: paul
No Gravatar

Recently I had the opportunity to create a course map and elevation profile for the Canylonlands Half Marathon. This is one of my favorite races, and I’ve participated in either the half marathon or the 5-mile event for five of the last seven years. My familiarity with the courses would definitely be helpful in creating accurate maps, but I also felt particularly obligated to present the striking beauty of the course through cartography.

Fortunately, the state of Utah has the best GIS data clearinghouse I’ve ever used: the Utah Automated Geographic Reference Center (AGRC) and associated GIS Data Portal. From this website, users are able to download many datasets, include 2007 1-ft color aerial imagery and 5-meter digital elevation models…for most of the entire state…for free. Finding data at that resolution, currentness, and cost is truly amazing, and for that reason I love the AGRC and love making maps for locations in Utah.

The 1-ft color imagery allowed me to zoom into the route very tightly (about 1:1000), and precisely digitize every tangent of the route and closely simulate its certification. This helps makes the elevation profile and the mile markers more accurate.

But the 5m elevation model was the real gem. For most of the United States, the best you can get is 10m resolution. In some places you can get no better than 30m. So to get 5m resolution for a tiny town in the middle of Utah is remarkable. I should note that 2m DEM’s are publicly available for some locations in Utah.

What a 5m DEM provides is better hillshading, which is the backbone of this particular map. Every ridge, canyon, drainage, and other topography are sharply defined, even at large scales. This not only makes the map more vivid, but allows it to be blown up to larger scales (and larger prints), and still look wicked good. In addition, the extra resolution of the 5m DEM accommodates better profiling, especially in narrow canyon areas. For much of the Canyonlands race, runners are tucked right up against a huge sandstone cliff. This can really mess with an elevation model, which tends to interpolate/average elevation values in steep areas. With a higher-resolution DEM, this effect is lessened.

The final maps turned out well, in part to the quality of the underlying data. I ended up making an overall map, an elevation profile, and zoom-in views of the start line and finish line. The race management also printed a poster version of the map, which is available for purchase here.


Canyonland Half Marathon poster


Map showing zoom-in view of finish line

September 16th, 2008 | Author: paul
No Gravatar

In honor of the upcoming Top of Utah Marathon this weekend, today’s topic is about the other race in the event: the Top of Utah 5K. This race is especially of interest to me this year, as I am running it. TOU will be my first 5K since July of 2007, so compound that with my rather “interesting” training this year, I’m not quite certain how I will do.

Fortunately, I do know a few things about the race:

  1. It is certified, so I can expect it to be the correct distance
  2. It is a relatively flat loop course, so I can expect decent times that actually mean something (ie - not downhill).
  3. As part of my sponsorship of the Top of Utah Marathon, I’ve created a course map, so it will be one of the few 5K races out there that actually has a decent map that show the exact turns and the elevation profile.

Most of the maps I make are for relays, marathons, and half marathons; very few short races have the budget or real incentive for maps. However, there is one really nice thing about making a 5K map: scale. What is scale? Think of it as “zoom-factor”. Large-scale means “zoomed in”, small-scale means “zoomed out”. Scale can be represented by ratios, such as 1:6000 (large scale) or 1:100,000 (small scale). Since a 5K loop route does not take up much geographic space relative to a marathon or relay, I have the luxury of creating a large-scale map on a small page size (8.5×11″). This means that I get to show tremendous detail, including aerial photos and crisp turn locations. You just don’t get that on most small-scale maps.

 

From the elevation profile, it’s easy to see that the elevation does not change much during the race. There is a short, abrupt hill around Mile 1.6 (200 S to 100 S), and very subtle uphill on 300 N, and then a short, abrupt downhill near the finish. The last block (0.1 miles) is on an uphill, but who’s counting at that point?

But all this is getting nit-picky; the course can be more concisely described as relatively flat and fast. Although I am still building my base, I hope to at least challenge 16:00 for a finish time. Seeing 15:5x at the end would be great, but I could live with 16:1x as well. It’s hard to find concrete expectations. I do know that the first half should be faster than the second half of the race, due to topography, so I hope to hit 4:5x on the first mile, 5:0x on the second mile, and then see what I have for the end.

Should be fun! (and way easier than the Top of Utah Marathon).