flag

1° Prosecco Marathon, 2023 course map and altimetry

1° Prosecco Marathon: 2023 route, altimetry, gpx

Note: "1° Prosecco Marathon" is NOT organized by goandrace.com

1° Prosecco Marathon course map. Lenght: 10 km (6.2 mi).

10 km (6.2 mi) course map of the event "1° Prosecco Marathon" in Vidor, in the Province of Treviso (Sunday, December 3, 2023). Explore the route!

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

1° Prosecco Marathon: route altimetric information


1° Prosecco Marathon: GNR-GAP index (v 1.0, experimental, see more)

1° Prosecco Marathon: interactive route

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

1° Prosecco Marathon: altimetry graph

1° Prosecco Marathon: slope graph

1° Prosecco Marathon: percentage distribution of slope

1° Prosecco Marathon: 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 144 146 +2 +0.2% 143 146 3 1
KM 1-2 146 167 +21 +2.1% 146 167 21 0
KM 2-3 167 179 +12 +1.2% 166 180 14 2
KM 3-4 179 157 -22 -2.2% 157 179 0 22
KM 4-5 157 177 +20 +2.0% 148 177 28 8
KM 5-6 177 195 +18 +1.8% 177 197 19 1
KM 6-7 195 168 -27 -2.7% 168 195 2 29
KM 7-8 168 164 -4 -0.4% 153 168 11 15
KM 8-9 164 152 -12 -1.2% 152 170 6 18
KM 9-10 152 157 +5 +0.5% 144 157 13 8
KM 10-11 157 147 -10 -1.0% 146 160 3 13
KM 11-11.88 147 149 +2 +0.2% 147 152 49 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 4.7% slower.


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

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.