Hi, it seems like the Racing Point constructor points have not been updated to reflect the 15 point ‘Tracing Point’ deduction – the API returns 56 points instead of 41 after the 70th Anniversary GP.
hi my friend, it seems like at 2016 australian gp duration of pit stops take for some teams above 18 minutes if i see well. the same with some pit stop times at 2014 and 2017 year.
i saw it when i made avg from all pit stops
That’s when the entire field was in the pits for the red flag period. The official timing data counts this as a pit stop, but not consistently. You can see the previous discussion on that matter a few comment pages back: https://ergast.com/mrd/bugs/comment-page-3/#comment-14735
Hello, there seems to errors in the fastest laps from the 2019 Japan race. The problem is that multiple drivers don’t have their correct fastest laps. An example is Danill Kvyat’s time is reported to be 1:34.921 while the official F1 website says that it is 1:33.239. Not all drivers have the wrong fastest lap associated with them, multiple do.
Was running some queries and noticed that Kvyat’s “qualifying” record for 2019 Brazil (driverId = 826, qualifyId = 8353, raceId = 1029) has the wrong constructorId. It’s set to to Redbull (9) rather than Toro Rosso (5).
Regards,
TK
BTW, Kvyat’s record for this race in the “results” table looks okay; constructor is set to TR.
– The time for result 20992 (Hamilton, 2011 German GP) is wrong. It should be:
‘1:37:30.334’
– The time for result 21088 (Vettel, 2011 Singapore GP) is wrong. It should be:
‘1:59:06.757’
– The miliseconds for result 19302 (Hawthorn, 1954 British GP) is wrong. It should be:
10644000
– The constructor results for races 784 and 790 (1956 Argentine and German GPs) should be removed, because the constructors championship only started in 1958.
According to Race Result, Webber should have no lap times in 2008 Italian Grand Prix.
But there are 52 lap times named Mark Webber in 2008 Italian Grand Prix in DB.
Thank you for correcting the information about the pitstops for Mugello (round 9), but could you also correct the info for Monza (round 8). Also this race was suspended and all the cars went in the pit (and changed tyres).
Have you ever considered adding something to account for race starts like Hungary this year? Grosjean and KMag pitted after the formation lap and started from the pitlane, instead of their original grid spots.
Hi TK,
Thanks for the warning – I’ve corrected these now in 2016/9 and 2020/03 using “0” for starting in the pit lane – an approach used elsewhere in the database. With hindsight it should be a string field rather than an integer :-/
Chris
Hi Wesley, I’m finding it difficult to obtain reliable start times for this year’s amended schedule. Let me know if you find a reliable source (in UTC)
Chris
Hi Chris,
It is possible to get it from the formula 1 website. You can find the complete schedule here: https://www.formula1.com/en/racing/2020.html
Only downside is that you have to click through the pages. You can press any race and then click on full schedule to see all the start times.
Wesley
Regarding the calendar topic, a very good source is also https://f1calendar.com/.
They have all session infos, and also an API. They’ve sent me the link as it’s not officially documented on their website. For season 2020 the URL looks like
what has happened with the database?
Suddenly, all of the time-consuming queries like fetching a driver’s lap times and alltime rankings perform as if they would run locally.
This was causing me so much headache in the past, and now it kinda flies.
Just how?
Hi Indigo,
I had to move to a new server so updated to MySQL 5.7. It may be faster but several things have stopped working so I’m not as happy as you are!
Cheers,
Chris
Hi,
Unfortunately, I don’t have any experience with sqlite, so would be unable to test the results.
Chris
Hi, it seems like the Racing Point constructor points have not been updated to reflect the 15 point ‘Tracing Point’ deduction – the API returns 56 points instead of 41 after the 70th Anniversary GP.
Great API by the way!
Hi Kai,
Thanks for the warning. I hate it when they do that! Now updated.
Chris
hi my friend, it seems like at 2016 australian gp duration of pit stops take for some teams above 18 minutes if i see well. the same with some pit stop times at 2014 and 2017 year.
i saw it when i made avg from all pit stops
That’s when the entire field was in the pits for the red flag period. The official timing data counts this as a pit stop, but not consistently. You can see the previous discussion on that matter a few comment pages back: https://ergast.com/mrd/bugs/comment-page-3/#comment-14735
Hello, there seems to errors in the fastest laps from the 2019 Japan race. The problem is that multiple drivers don’t have their correct fastest laps. An example is Danill Kvyat’s time is reported to be 1:34.921 while the official F1 website says that it is 1:33.239. Not all drivers have the wrong fastest lap associated with them, multiple do.
Hi Colo,
Thanks for the warning – now corrected.
Chris
Hi Chris,
Was running some queries and noticed that Kvyat’s “qualifying” record for 2019 Brazil (driverId = 826, qualifyId = 8353, raceId = 1029) has the wrong constructorId. It’s set to to Redbull (9) rather than Toro Rosso (5).
Regards,
TK
BTW, Kvyat’s record for this race in the “results” table looks okay; constructor is set to TR.
Hi TK,
Thanks for the warning – now corrected,
Chris
Hi,
First of all hats off for this nice database, so much interesting data to look at!
I was wondering if safety car deployments/laps where safety car was active is anywhere in the data, since I can’t find it anywhere?
Kind regards
Hi PZ,
Unfortunately not – it’s not easy to find that data.
Chris
Hello,
I don’t understand the pitstop information from the last race (Mugello). is the ‘red flag’ period not counted?
http://ergast.com/api/f1/2020/9/drivers/bottas/pitstops
Great work to collect all this information.
Ab
Application take some times to give all laptimes for a race , example https://ergast.com/api/f1/2020/9/laps.json
, by adding an index on race table performance increase :
ALTER TABLE `races` ADD INDEX `inxYearRound` (`year` , `round`);
Hi Chris,
When checking the integrity of your database, I detected the following bugs:
– All URLs in tables circuits, constructors, drivers and races should be https instead of http.
– The URL for driver 806 (Oscar Gonzallez) is wrong. It should be:
https://en.wikipedia.org/wiki/%C3%93scar_Gonz%C3%A1lez_(racing_driver)
– The URL for race 909 (2014 German GP) is wrong. It should be:
https://en.wikipedia.org/wiki/2014_German_Grand_Prix
– The time for result 20992 (Hamilton, 2011 German GP) is wrong. It should be:
‘1:37:30.334’
– The time for result 21088 (Vettel, 2011 Singapore GP) is wrong. It should be:
‘1:59:06.757’
– The miliseconds for result 19302 (Hawthorn, 1954 British GP) is wrong. It should be:
10644000
– The constructor results for races 784 and 790 (1956 Argentine and German GPs) should be removed, because the constructors championship only started in 1958.
Thanks, and keep up the good work!
Hi Ab,
Thanks for the warning – they’re now included.
Chris
Hi G.Letellier,
There is a raceId index on this table so the issue is probably due to an inefficient query – I’ll try to speed it up.
Chris
Hi.
According to Race Result, Webber should have no lap times in 2008 Italian Grand Prix.
But there are 52 lap times named Mark Webber in 2008 Italian Grand Prix in DB.
Is the McLaren info correct? They’re supposed to have 155 fastest laps but i can’t get that number from the query
Hi Tiago – fastest lap times are only available from the 2004 season onwards. Does that affect your query?
Chris
Hi Chris,
Thank you for correcting the information about the pitstops for Mugello (round 9), but could you also correct the info for Monza (round 8). Also this race was suspended and all the cars went in the pit (and changed tyres).
you can check with this link;
http://ergast.com/api/f1/2020/8/drivers/stroll/pitstops
Regards,
Ab
Hi Ab,
Thanks for the warning – same issue.
Now updated.
Chris
Hi Kim,
The race result records 53 laps for Webber:
http://ergast.com/api/f1/2008/14/drivers/webber/results
Which matches the number of entries in the laps table:
http://ergast.com/api/f1/2008/14/drivers/webber/laps
Have I misunderstood your query?
Chris
Hey,
It looks like the Mercedes constructor standings is missing after the latest race (raceid 1040) in the csv data.
Thanks for the great work with this.
Richard
Hi Richard,
This seems to be a bug in mysql. I’ll check at the weekend but hopefully it will fix itself after the next Grand Prix.
Chris
Hi Chris,
Have you ever considered adding something to account for race starts like Hungary this year? Grosjean and KMag pitted after the formation lap and started from the pitlane, instead of their original grid spots.
https://en.em.wikipedia.org/wiki/2020_Hungarian_Grand_Prix
Wiki uses an explicit Start Grid column. Maybe adding a record in Pitstops for lap 0, to avoid a schema change?
Regards,
TK
Btw, noticed an inconsistency with the results for 2016 Austria.
Massa and Kvyat started from the pitlane, due to breaking Parc Ferme. But the db still has them in their original grid spots.
http://ergast.com/api/f1/2016/9/results
https://en.m.wikipedia.org/wiki/2016_Austrian_Grand_Prix
TK
Hi TK,
Thanks for the warning – I’ve corrected these now in 2016/9 and 2020/03 using “0” for starting in the pit lane – an approach used elsewhere in the database. With hindsight it should be a string field rather than an integer :-/
Chris
Hi Chris,
The time for the eiffel grand prix race is wrong. It should be 14:10 GMT. Right now it is 15:10 GMT.
Wesley
Hi Wesley, I’m finding it difficult to obtain reliable start times for this year’s amended schedule. Let me know if you find a reliable source (in UTC)
Chris
Hi Chris,
It is possible to get it from the formula 1 website. You can find the complete schedule here:
https://www.formula1.com/en/racing/2020.html
Only downside is that you have to click through the pages. You can press any race and then click on full schedule to see all the start times.
Wesley
Hi Chris,
I just found something else. Look at this page, you can set it to UTC yourself:
https://formulaonecalendar.com/
Wesley
Regarding the calendar topic, a very good source is also https://f1calendar.com/.
They have all session infos, and also an API. They’ve sent me the link as it’s not officially documented on their website. For season 2020 the URL looks like
https://f1calendar.com/api/year/2020
Daniel
Thanks Daniel! Exactly what I was looking for!
Wesley
Hi Chris,
The driver standing list of this season has all zeros in the Wins column.
https://ergast.com/api/f1/current/driverStandings
Wesley
Chris,
what has happened with the database?
Suddenly, all of the time-consuming queries like fetching a driver’s lap times and alltime rankings perform as if they would run locally.
This was causing me so much headache in the past, and now it kinda flies.
Just how?
Hi Indigo,
I had to move to a new server so updated to MySQL 5.7. It may be faster but several things have stopped working so I’m not as happy as you are!
Cheers,
Chris
That’s unfortunate!
I hope you get your problems sorted out. Good luck mate!
Hi Wesley,
Thanks for the warning. Now corrected.
Chris
Hello,
I’ve noticed the positions the Monaco Grand Prix 2019 (1015) particularly are incorrect.
Real Race Result API Result
Ham Ham
Vet Ver
Bot Vet
Ver Bot
There were a few others throughout Monaco, I haven’t checked any other races yet but this was the first one I noticed to be incorrect