2017 Tour de Pologne
2017 UCI World Tour, race 27 of 37 | |||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Race details | |||||||||||||||||||||||||||||||||
Dates | 29 July – 4 August 2017 | ||||||||||||||||||||||||||||||||
Stages | 7 | ||||||||||||||||||||||||||||||||
Distance | 1,122 km (697.2 mi) | ||||||||||||||||||||||||||||||||
Results | |||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||
The 2017 Tour de Pologne was a road cycling stage race that took place between 29 July and 4 August in Poland. It was the 74th edition of the Tour de Pologne and was the twenty-seventh event of the 2017 UCI World Tour.[1][2] The race was won by Dylan Teuns riding for You have called {{Contentious topics}}
. You probably meant to call one of these templates instead:
Alerting users
- {{alert/first}} ({{Contentious topics/alert/first}}) is used, on a user's talk page, to "alert", or draw a user's attention, to the contentious topics system if they have never received such an alert before. In this case, this template must be used for the notification.
- {{alert}} ({{Contentious topics/alert}}) is used, on a user's talk page, to "alert", or draw a user's attention, to the fact that a specific topic is a contentious topic. It may only be used if the user has previously received any contentious topic alert, and it can be replaced by a custom message that conveys the contentious topic designation.
- {{alert/DS}} ({{Contentious topics/alert/DS}}) is used to inform editors that the old "discretionary sanctions" system has been replaced by the contentious topics system, and that a specific topic is a contentious topic.
- {{Contentious topics/aware}} is used to register oneself as already aware that a specific topic is a contentious topic.
Editnotices
- {{Contentious topics/editnotice}} is used to inform editors that a page is covered by the contentious topics system using an editnotice. Use the one below if the page has restrictions placed on the page.
- {{Contentious topics/page restriction editnotice}} is used to inform editors that the page they are editing is subject to contentious topics restrictions using an editnotice. Use the above if there are no restrictions placed on the page.
Talk page notices
- {{Contentious topics/talk notice}} is used to provide additional communication, using a talk page messagebox (tmbox), to editors that they are editing a page that is covered by the contentious topics system. The template standardises the format and wording of such notices. Use the below if there are restrictions placed on the page.
- {{Contentious topics/page restriction talk notice}} is used to inform editors that page restrictions are active on the page using a talk page messagebox (tmbox). Use the above if there are no restrictions placed on the page.
- If a user who has been alerted goes on to disruptively edit the affected topic area, they can be reported to the arbitration enforcement (AE) noticeboard, where an administrator will investigate their conduct and issue a sanction if appropriate. {{AE sanction}} is used by administrators to inform a user that they have been sanctioned.
Miscellaneous
- {{Contentious topics/list}} and {{Contentious topics/table}} show which topics are currently designated as contentious topics. They are used by a number of templates and pages on Wikipedia..
Schedule
The race route was announced on 15 May 2017 at the BGŻ Arena in Pruszków.[3]
Stage | Date | Route | Distance | Type | Winner | ||
---|---|---|---|---|---|---|---|
1 | 29 July | Kraków to Kraków | 130 km (81 mi) | Hilly stage | Peter Sagan (SVK) | ||
2 | 30 July | Tarnowskie Góry to Katowice | 142 km (88 mi) | Flat stage | Sacha Modolo (ITA) | ||
3 | 31 July | Jaworzno to Szczyrk | 161 km (100 mi) | Mountain stage | Dylan Teuns (BEL) | ||
4 | 1 August | Zawiercie to Zabrze | 238 km (148 mi) | Hilly stage | Caleb Ewan (AUS) | ||
5 | 2 August | Nagawczyna to Rzeszów | 130 km (81 mi) | Medium-mountain stage | Danny van Poppel (NED) | ||
6 | 3 August | Wieliczka Salt Mine to Zakopane | 189 km (117 mi) | Mountain stage | Jack Haig (AUS) | ||
7 | 4 August | Terma Bukowina Tatrzańska to Bukowina Tatrzańska | 132 km (82 mi) | Mountain stage | Wout Poels (NED) | ||
Total | 1,122 km (697.2 mi) |
Participating teams
As the 2017 Tour de Pologne was a UCI World Tour event, all eighteen UCI WorldTeams were invited automatically and obliged to enter a team into the race. Along with a Polish national team, three other squads were given wildcard places into the race, and as such, formed the event's 22-team peloton.[5] The number of riders allowed per squad was seven, down from eight,[6] in 2016; all teams except You have called {{Contentious topics}}
. You probably meant to call one of these templates instead:
Alerting users
- {{alert/first}} ({{Contentious topics/alert/first}}) is used, on a user's talk page, to "alert", or draw a user's attention, to the contentious topics system if they have never received such an alert before. In this case, this template must be used for the notification.
- {{alert}} ({{Contentious topics/alert}}) is used, on a user's talk page, to "alert", or draw a user's attention, to the fact that a specific topic is a contentious topic. It may only be used if the user has previously received any contentious topic alert, and it can be replaced by a custom message that conveys the contentious topic designation.
- {{alert/DS}} ({{Contentious topics/alert/DS}}) is used to inform editors that the old "discretionary sanctions" system has been replaced by the contentious topics system, and that a specific topic is a contentious topic.
- {{Contentious topics/aware}} is used to register oneself as already aware that a specific topic is a contentious topic.
Editnotices
- {{Contentious topics/editnotice}} is used to inform editors that a page is covered by the contentious topics system using an editnotice. Use the one below if the page has restrictions placed on the page.
- {{Contentious topics/page restriction editnotice}} is used to inform editors that the page they are editing is subject to contentious topics restrictions using an editnotice. Use the above if there are no restrictions placed on the page.
Talk page notices
- {{Contentious topics/talk notice}} is used to provide additional communication, using a talk page messagebox (tmbox), to editors that they are editing a page that is covered by the contentious topics system. The template standardises the format and wording of such notices. Use the below if there are restrictions placed on the page.
- {{Contentious topics/page restriction talk notice}} is used to inform editors that page restrictions are active on the page using a talk page messagebox (tmbox). Use the above if there are no restrictions placed on the page.
- If a user who has been alerted goes on to disruptively edit the affected topic area, they can be reported to the arbitration enforcement (AE) noticeboard, where an administrator will investigate their conduct and issue a sanction if appropriate. {{AE sanction}} is used by administrators to inform a user that they have been sanctioned.
Miscellaneous
- {{Contentious topics/list}} and {{Contentious topics/table}} show which topics are currently designated as contentious topics. They are used by a number of templates and pages on Wikipedia. (six riders) did so, and therefore the start list contained a total of 153 riders.
UCI WorldTeams
- AG2R La Mondiale
- Astana
- Bahrain–Merida
- BMC Racing Team
- Bora–Hansgrohe
- Cannondale–Drapac
- Team Dimension Data
- FDJ
- Team Katusha–Alpecin
- LottoNL–Jumbo
- Lotto–Soudal
- Movistar Team
- Orica–Scott
- Quick-Step Floors
- Team Sky
- Team Sunweb
- Trek–Segafredo
- You have called
{{Contentious topics}}
. You probably meant to call one of these templates instead:
Alerting users
- {{alert/first}} ({{Contentious topics/alert/first}}) is used, on a user's talk page, to "alert", or draw a user's attention, to the contentious topics system if they have never received such an alert before. In this case, this template must be used for the notification.
- {{alert}} ({{Contentious topics/alert}}) is used, on a user's talk page, to "alert", or draw a user's attention, to the fact that a specific topic is a contentious topic. It may only be used if the user has previously received any contentious topic alert, and it can be replaced by a custom message that conveys the contentious topic designation.
- {{alert/DS}} ({{Contentious topics/alert/DS}}) is used to inform editors that the old "discretionary sanctions" system has been replaced by the contentious topics system, and that a specific topic is a contentious topic.
- {{Contentious topics/aware}} is used to register oneself as already aware that a specific topic is a contentious topic.
Editnotices
- {{Contentious topics/editnotice}} is used to inform editors that a page is covered by the contentious topics system using an editnotice. Use the one below if the page has restrictions placed on the page.
- {{Contentious topics/page restriction editnotice}} is used to inform editors that the page they are editing is subject to contentious topics restrictions using an editnotice. Use the above if there are no restrictions placed on the page.
Talk page notices
- {{Contentious topics/talk notice}} is used to provide additional communication, using a talk page messagebox (tmbox), to editors that they are editing a page that is covered by the contentious topics system. The template standardises the format and wording of such notices. Use the below if there are restrictions placed on the page.
- {{Contentious topics/page restriction talk notice}} is used to inform editors that page restrictions are active on the page using a talk page messagebox (tmbox). Use the above if there are no restrictions placed on the page.
- If a user who has been alerted goes on to disruptively edit the affected topic area, they can be reported to the arbitration enforcement (AE) noticeboard, where an administrator will investigate their conduct and issue a sanction if appropriate. {{AE sanction}} is used by administrators to inform a user that they have been sanctioned.
Miscellaneous
- {{Contentious topics/list}} and {{Contentious topics/table}} show which topics are currently designated as contentious topics. They are used by a number of templates and pages on Wikipedia.
UCI Professional Continental teams
National team
Stages
Stage 1
The opening stage of the 2017 Tour de Pologne was a ride around Krakow, effectively designed for the sprinters. Having left from the city's Old Square, the peloton completed an anti-clockwise loop around the city, which contained the only two categorised climbs, in the villages of Bachowice and Kaszów, both fourth category. Once the riders returned to Kraków, they first passed the sole intermediate sprint, before completing three laps around a 4 km (2.5 mi) circuit, to complete the day's running.
|
|
Stage 2
- 30 July 2017 – Tarnowskie Góry to Katowice, 142 km (88.2 mi)[9]
The second stage was another opportunity for the sprinters. After the start in Tarnowskie Góry, the riders headed south-east, passing through the intermediate sprints in Piekary Śląskie, Chorzów and Siemianowice Śląskie, following devious roads before hitting the 17 km (10.6 mi) finishing circuit in Katowice. It contained the two category four climbs of the day, and the final metres before the finish line headed slightly downhill, with speeds of about 80 kilometres per hour (50 mph) expected from the top riders.
|
|
Stage 3
After the opening two sprint stages, the next stage took the riders into the Silesian Beskids with a route that favoured the climbers. After a reasonably flat first half, the first category Salmopol was climbed, before the riders entered a circuit containing the Zameczek climb, which was climbed twice. Once the riders had descended, they returned over the Salmopol, going in the opposite way from that climbed previously, with the summit coming 11.3 kilometres (7.0 miles) before the finish line. The final ascent was only 1.2 kilometres (0.7 miles) long, but averaged 11.3%.
|
|
Stage 4
With a length of 238 kilometres (148 miles), the fourth stage was the longest stage of the 2017 Tour de Pologne. Having started in Zawiercie, the first section of the route was hilly, covering the sole categorised climb of the day in Olkusz, where there was also an intermediate sprint, with the other two being in Jastrzębie-Zdrój and Rybnik. A finishing circuit was also utilised in the finishing city of Zabrze, with three laps of a 6.5 km (4.0 mi) long loop being completed to complete proceedings.
|
|
Stage 5
- 2 August 2017 – Olimp Nagawczyna to Rzeszów, 130 km (81 mi)[14]
The stage started from Olimp Nagawczyna, near Dębica, heading south-east, through the Podkarpackie Voivodeship. The route was hilly throughout, with four categorised climbs all coming in the second half of the section – two ascents in Gmina Lubenia and one in Łany (part of the village Matysówka), before the riders entered Rzeszów, where the only intermediate sprint was held. There, the peloton entered the lengthy 22.5 km (14.0 mi) circuit, to be covered once, and containing another ascent of Łany, the summit coming 10.6 km (6.6 mi) before the finish.
|
|
Stage 6
- 3 August 2017 – Wieliczka Salt Mine to Zakopane, 189 km (117 mi)[15]
Stage 7
Classification leadership tableIn the 2017 Tour de Pologne, four different jerseys were awarded. The general classification was calculated by adding each cyclist's finishing times on each stage, and allowing time bonuses for the first three finishers at intermediate sprints (three seconds to first, two seconds to second and one second to third) and at the finish of all stages: the stage winner won a ten-second bonus, with six and four seconds for the second and third riders respectively.Template:Sfn The leader of the classification received a yellow jersey;Template:Sfn it was considered the most important of the 2017 Tour de Pologne, and the winner of the classification was considered the winner of the race.
There was also a mountains classification, the leadership of which was marked by a purple jersey.Template:Sfn In the mountains classification, points towards the classification were won by reaching the top of a climb before other cyclists. Each climb was categorised as either first, second, third, or fourth-category, with more points available for the higher-categorised climbs. Double points were also awarded for the premier first-category climb on the final stage.Template:Sfn Additionally, there was a sprints classification, which awarded a white jersey.Template:Sfn In the points classification, cyclists received points for finishing in the top 20 in a stage.Template:Sfn For winning a stage, a rider earned 20 points, with a point fewer per place down to 1 point for 20th place.Template:Sfn The fourth and final jersey represented the active rider classification, marked by a blue jersey.Template:Sfn This was decided at the race's intermediate sprints, awarding points on a 3–2–1 scale.Template:Sfn There was also a classification for Polish riders,Template:Sfn with the highest-placed rider appearing on the podium each day. As well as this, a teams classification was also calculated,Template:Sfn in which the times of the best three cyclists per team on each stage were added together; the leading team at the end of the race was the team with the lowest total time. ReferencesSourcesExternal links |