Yellowstone Half Marathon & 5K, 2024 course map and altimetry
Yellowstone Half Marathon & 5K: 2024 route, altimetry, gpx
Note: "Yellowstone Half Marathon & 5K" is NOT organized by goandrace.com
Yellowstone Half Marathon & 5K course map. Lenght: 21.098 km (13.1 mi).
21.098 km (13.1 mi) course map of the event "Yellowstone Half Marathon & 5K" in West Yellowstone, Montana (Saturday, June 8, 2024). Explore the route!
Do you want to fly over the path with a Google Earth 3D video? Click on the following link: Yellowstone Half Marathon & 5K, fly over the path (3D video).
GPS track - .gpx file download
Download the gps race path by clicking here.
You can send the .gpx file to your
Garmin watch or other compatible device and follow the path. For instructions on how to upload the GPX file onto your
Garmin watch
click here.
.gpx file download
NB: it is possible that the length calculated from the gpx file is greater than
that of the race, with an error typically of 1-2%, so for example a half-marathon could be 2-300 meters longer.
Click the following link to visit the Yellowstone Half Marathon & 5K event page.
Yellowstone Half Marathon & 5K: route altimetric information
Yellowstone Half Marathon & 5K: GNR-GAP index (v 1.0, experimental, see more)
Yellowstone Half Marathon & 5K: interactive route
You can set the km (or mile) markers and you can select different types of layers (Satellite or Openstreetmap).
Yellowstone Half Marathon & 5K: altimetry graph
Yellowstone Half Marathon & 5K: slope graph
Yellowstone Half Marathon & 5K: percentage distribution of slope
Yellowstone Half Marathon & 5K: Km by km route altimetry analysis
| Lap | Start Alt. | End Alt. | Diff. Alt. | Aver. Slope | Min Alt. | Max Alt. | Tot Climb | Tot Descent |
|---|---|---|---|---|---|---|---|---|
| KM 0-1 | 2030 | 2032 | +1 | +0.1% | 2030 | 2031 | 1 | 0 |
| KM 1-2 | 2032 | 2033 | +1 | +0.1% | 2032 | 2033 | 1 | 0 |
| KM 2-3 | 2033 | 2030 | -3 | -0.3% | 2030 | 2033 | 0 | 3 |
| KM 3-4 | 2030 | 2028 | -2 | -0.2% | 2029 | 2030 | 0 | 2 |
| KM 4-5 | 2028 | 2028 | -1 | -0.1% | 2028 | 2028 | 0 | 1 |
| KM 5-6 | 2028 | 2026 | -2 | -0.2% | 2026 | 2027 | 0 | 2 |
| KM 6-7 | 2026 | 2023 | -3 | -0.3% | 2022 | 2026 | 1 | 4 |
| KM 7-8 | 2023 | 2028 | +5 | +0.5% | 2023 | 2028 | 7 | 2 |
| KM 8-9 | 2028 | 2057 | +29 | +2.9% | 2029 | 2056 | 29 | 0 |
| KM 9-10 | 2057 | 2105 | +49 | +4.9% | 2057 | 2104 | 49 | 0 |
| KM 10-11 | 2105 | 2109 | +4 | +0.4% | 2107 | 2117 | 12 | 8 |
| KM 11-12 | 2109 | 2110 | +1 | +0.1% | 2107 | 2110 | 3 | 2 |
| KM 12-13 | 2110 | 2084 | -26 | -2.6% | 2086 | 2110 | 0 | 26 |
| KM 13-14 | 2084 | 2034 | -49 | -4.9% | 2034 | 2082 | 0 | 49 |
| KM 14-15 | 2034 | 2032 | -3 | -0.3% | 2032 | 2036 | 2 | 4 |
| KM 15-16 | 2032 | 2028 | -4 | -0.4% | 2028 | 2031 | 0 | 4 |
| KM 16-17 | 2028 | 2038 | +11 | +1.1% | 2027 | 2038 | 12 | 1 |
| KM 17-18 | 2038 | 2023 | -16 | -1.6% | 2023 | 2039 | 1 | 16 |
| KM 18-19 | 2023 | 2025 | +3 | +0.3% | 2022 | 2025 | 3 | 0 |
| KM 19-20 | 2025 | 2027 | +2 | +0.2% | 2026 | 2027 | 2 | 0 |
| KM 20-21 | 2027 | 2028 | +1 | +0.1% | 2028 | 2028 | 1 | 0 |
| KM 21-21.07 | 2028 | 2029 | 0 | 0% | 2029 | 2029 | 0 | 0 |
GNR-GAP index - Go&Race Algorithm Estimate
Based on the elevation profile analysis, running on this course is estimated to result in a pace that is 3.1% slower.
For example, a runner who maintains a pace of 5'00"/km (8'03"/mi) on a flat 21.1 km course, corresponding to a
finish time of 1h45'21", is estimated to complete this course in 1h48'35". The recalculated average pace (GAP) improves to 5'09"/km (8'18"/mi), making it 0'09"/km (0'15"/mi) slower.
The following graph illustrates the Pace Adjustment (PA) factor applied to the pace along the course. The horizontal red line represents a PA of 1, meaning no pace adjustment. Above the line, the pace is slower; below the line, it is faster. The table below also provides estimates for other pace ranges.
Predict your race or analyze your performance!
This following table shows simulations for paces between 3 and 8'/km.
RACE PREDICTION
To estimate a possible race time, use the "Pace" or "Time without slopes" column, which are valid for a flat course.
For example, if you think you can cover this distance on a flat course at a pace of 4'40"/km (or 7'31"/mi), i.e. in a time of 1h38'19", the estimate is to complete
this course in 1h41'20", corresponding to a pace of 4'49"/km (or 7'44"/mi).
PERFORMANCE ANALYSIS
If you have run this race, use the table to estimate the equivalent time on a flat course. Check the "GAP" column and find the value closest
to your pace, or compare the "Time with slopes" column with your time: on the same row you will find the pace and the equivalent time on a
flat course in the "Pace" and "Time without slopes" columns.
For example, a time of 1h37'43" (pace of 4'38"/km or 7'28"/mi) corresponds to a time of
1h34'49" on a flat course (pace of 4'30"/km or 7'15"/mi).
| Pace (min/km) | Pace (min/mile) | Time without slopes (hh:mm:ss) | Time with slopes (hh:mm:ss) | GAP (min/km) | Δ Pace (min/km) | GAP (min/mile) | Δ Pace (min/mile) |
|---|---|---|---|---|---|---|---|
| 3'00" | 4'50" | 1h03'12" | 1h05'09" | 3'06" | 0'06" | 4'59" | 0'09" |
| 3'10" | 5'06" | 1h06'43" | 1h08'46" | 3'16" | 0'06" | 5'15" | 0'09" |
| 3'20" | 5'22" | 1h10'14" | 1h12'23" | 3'26" | 0'06" | 5'32" | 0'10" |
| 3'30" | 5'38" | 1h13'44" | 1h16'00" | 3'36" | 0'06" | 5'48" | 0'10" |
| 3'40" | 5'54" | 1h17'15" | 1h19'37" | 3'47" | 0'07" | 6'05" | 0'11" |
| 3'50" | 6'10" | 1h20'46" | 1h23'14" | 3'57" | 0'07" | 6'22" | 0'11" |
| 4'00" | 6'26" | 1h24'16" | 1h26'52" | 4'07" | 0'07" | 6'38" | 0'12" |
| 4'10" | 6'42" | 1h27'47" | 1h30'29" | 4'18" | 0'08" | 6'55" | 0'12" |
| 4'20" | 6'58" | 1h31'18" | 1h34'06" | 4'28" | 0'08" | 7'11" | 0'13" |
| 4'30" | 7'15" | 1h34'49" | 1h37'43" | 4'38" | 0'08" | 7'28" | 0'13" |
| 4'40" | 7'31" | 1h38'19" | 1h41'20" | 4'49" | 0'09" | 7'44" | 0'14" |
| 4'50" | 7'47" | 1h41'50" | 1h44'57" | 4'59" | 0'09" | 8'01" | 0'14" |
| 5'00" | 8'03" | 1h45'21" | 1h48'35" | 5'09" | 0'09" | 8'18" | 0'15" |
| 5'10" | 8'19" | 1h48'51" | 1h52'12" | 5'20" | 0'10" | 8'34" | 0'15" |
| 5'20" | 8'35" | 1h52'22" | 1h55'49" | 5'30" | 0'10" | 8'51" | 0'16" |
| 5'30" | 8'51" | 1h55'53" | 1h59'26" | 5'40" | 0'10" | 9'07" | 0'16" |
| 5'40" | 9'07" | 1h59'23" | 2h03'03" | 5'50" | 0'10" | 9'24" | 0'17" |
| 5'50" | 9'23" | 2h02'54" | 2h06'40" | 6'01" | 0'11" | 9'41" | 0'17" |
| 6'00" | 9'39" | 2h06'25" | 2h10'18" | 6'11" | 0'11" | 9'57" | 0'18" |
| 6'10" | 9'55" | 2h09'56" | 2h13'55" | 6'21" | 0'11" | 10'14" | 0'18" |
| 6'20" | 10'12" | 2h13'26" | 2h17'32" | 6'32" | 0'12" | 10'30" | 0'19" |
| 6'30" | 10'28" | 2h16'57" | 2h21'09" | 6'42" | 0'12" | 10'47" | 0'19" |
| 6'40" | 10'44" | 2h20'28" | 2h24'46" | 6'52" | 0'12" | 11'03" | 0'20" |
| 6'50" | 10'60" | 2h23'58" | 2h28'23" | 7'03" | 0'13" | 11'20" | 0'20" |
| 7'00" | 11'16" | 2h27'29" | 2h32'01" | 7'13" | 0'13" | 11'37" | 0'21" |
| 7'10" | 11'32" | 2h31'00" | 2h35'38" | 7'23" | 0'13" | 11'53" | 0'21" |
| 7'20" | 11'48" | 2h34'30" | 2h39'15" | 7'33" | 0'13" | 12'10" | 0'22" |
| 7'30" | 12'04" | 2h38'01" | 2h42'52" | 7'44" | 0'14" | 12'26" | 0'22" |
| 7'40" | 12'20" | 2h41'32" | 2h46'29" | 7'54" | 0'14" | 12'43" | 0'23" |
| 7'50" | 12'36" | 2h45'03" | 2h50'06" | 8'04" | 0'14" | 12'60" | 0'23" |
| 8'00" | 12'52" | 2h48'33" | 2h53'44" | 8'15" | 0'15" | 13'16" | 0'24" |
Notes on the calculation of the length of the route, on the altimetry and on the slope
Note 1: the length of the route is calculated using the geographic coordinates of the points that compose it,
thanks to a specific formula. This value may differ slightly from the official length declared by the organizers of the race,
which is valid in case of discrepancies.
Note 2: the altimetry may not correspond exactly to the real values. For routes obtained via Google API, it is
possible that the altitude is that of the terrain, without considering the presence of any tunnels or viaducts. If, however,
the route was obtained from GPS tracking (for example with sports watches), the error is arbitrary and may depend
both on the GPS coverage at the time it was recorded and on the performance of the device used.
Note 3: the percentage slope is found by calculating considering sections of at least 50 meters and is subsequently subjected
to a "smoothing" process to reduce the possibility of artifacts and obtain a more realistic trend. For classification purposes,
roads with gradients between -3% and +3% are considered flat, those with gradients between +3% and +7% are uphill,
and those with gradients greater than +7% are considered steep. The same classification applies to descents.
This classification is to be considered arbitrary and is a choice of goandrace.com.