flag

Notos Ultra Trail, 2024 course map and altimetry

Notos Ultra Trail: 2024 route, altimetry, gpx

Note: "Notos Ultra Trail" is NOT organized by goandrace.com

Notos Ultra Trail course map. Lenght: 10 km (6.2 mi).

10 km (6.2 mi) course map of the event "Notos Ultra Trail" in Victoriaville (Saturday, June 15, 2024). Explore the route!

Do you want to fly over the path with a Google Earth 3D video? Click on the following link: Notos Ultra Trail, 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 Notos Ultra Trail event page.

Notos Ultra Trail: route altimetric information


Notos Ultra Trail: GNR-GAP index (v 1.0, experimental, see more)

Notos Ultra Trail: interactive route

You can set the km (or mile) markers and you can select different types of layers (Satellite or Openstreetmap).

Notos Ultra Trail: altimetry graph

Notos Ultra Trail: slope graph

Notos Ultra Trail: percentage distribution of slope

Notos Ultra Trail: 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 146 153 +7 +0.7% 133 152 21 14
KM 1-2 153 215 +62 +6.2% 153 215 73 12
KM 2-3 215 234 +20 +2.0% 215 234 20 0
KM 3-4 234 300 +65 +6.5% 234 313 76 11
KM 4-5 300 306 +6 +0.6% 275 306 28 21
KM 5-6 306 308 +2 +0.2% 295 350 49 47
KM 6-7 308 283 -24 -2.4% 274 308 6 30
KM 7-8 283 245 -38 -3.8% 245 297 11 50
KM 8-9 245 187 -58 -5.8% 185 245 13 71
KM 9-10 187 129 -57 -5.7% 129 186 0 57
KM 10-10.95 129 154 +25 +2.5% 128 154 1279 23

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 19.3% slower.


For example, a runner who maintains a pace of 5'00"/km (8'03"/mi) on a flat 10.95 km course, corresponding to a finish time of 0h54'44", is estimated to complete this course in 1h05'19". The recalculated average pace (GAP) improves to 5'58"/km (9'36"/mi), making it 0'58"/km (1'33"/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 6'/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 at a pace of 4'40"/km (or 7'31"/mi), i.e. in a time of 0h51'05", the estimate is to complete this course in 1h00'58", corresponding to a pace of 5'34"/km (or 8'58"/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 0h58'47" (pace of 5'22"/km or 8'39"/mi) corresponds to a time of 0h49'16" 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"0h32'50"0h39'11"3'35"0'35"5'46"0'56"
3'10"5'06"0h34'40"0h41'22"3'47"0'37"6'05"0'59"
3'20"5'22"0h36'29"0h43'33"3'59"0'39"6'24"1'02"
3'30"5'38"0h38'19"0h45'43"4'11"0'41"6'43"1'05"
3'40"5'54"0h40'08"0h47'54"4'23"0'43"7'03"1'08"
3'50"6'10"0h41'58"0h50'05"4'34"0'44"7'22"1'12"
4'00"6'26"0h43'47"0h52'15"4'46"0'46"7'41"1'15"
4'10"6'42"0h45'37"0h54'26"4'58"0'48"8'00"1'18"
4'20"6'58"0h47'26"0h56'37"5'10"0'50"8'19"1'21"
4'30"7'15"0h49'16"0h58'47"5'22"0'52"8'39"1'24"
4'40"7'31"0h51'05"1h00'58"5'34"0'54"8'58"1'27"
4'50"7'47"0h52'55"1h03'09"5'46"0'56"9'17"1'30"
5'00"8'03"0h54'44"1h05'19"5'58"0'58"9'36"1'33"
5'10"8'19"0h56'34"1h07'30"6'10"0'60"9'55"1'36"
5'20"8'35"0h58'23"1h09'40"6'22"1'02"10'15"1'40"
5'30"8'51"1h00'13"1h11'51"6'34"1'04"10'34"1'43"
5'40"9'07"1h02'02"1h14'02"6'46"1'06"10'53"1'46"
5'50"9'23"1h03'52"1h16'12"6'58"1'08"11'12"1'49"
6'00"9'39"1h05'41"1h18'23"7'10"1'10"11'31"1'52"
6'10"9'55"1h07'31"1h20'34"7'22"1'12"11'51"1'55"
6'20"10'12"1h09'20"1h22'44"7'33"1'13"12'10"1'58"
6'30"10'28"1h11'10"1h24'55"7'45"1'15"12'29"2'01"
6'40"10'44"1h12'59"1h27'06"7'57"1'17"12'48"2'04"
6'50"10'60"1h14'48"1h29'16"8'09"1'19"13'07"2'08"
7'00"11'16"1h16'38"1h31'27"8'21"1'21"13'27"2'11"
7'10"11'32"1h18'27"1h33'38"8'33"1'23"13'46"2'14"
7'20"11'48"1h20'17"1h35'48"8'45"1'25"14'05"2'17"
7'30"12'04"1h22'06"1h37'59"8'57"1'27"14'24"2'20"
7'40"12'20"1h23'56"1h40'10"9'09"1'29"14'43"2'23"
7'50"12'36"1h25'45"1h42'20"9'21"1'31"15'03"2'26"
8'00"12'52"1h27'35"1h44'31"9'33"1'33"15'22"2'29"

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.