Facebook
TwitterAbout Dataset This dataset is designed for Formula 1 (F1) enthusiasts, researchers, and data scientists aiming to analyze performance metrics of F1 drivers and cars. It includes telemetry data collected and preprocessed from FastF1 and Ergast APIs, offering valuable insights into driver performance across various races and scenarios.
The dataset is structured to facilitate dynamic updates and high-quality visualizations, making it suitable for advanced analyses such as race strategy optimization, performance comparisons, and machine learning applications. Key metrics include lap times, sector splits, RPM, throttle, speed, and more, enabling users to identify critical performance bottlenecks and trends.
Features High-Resolution Telemetry Data: Every tenth of a second for temporal data and lap-based aggregates. Sector and Mini-Sector Analysis: Performance indices calculated for each driver in every circuit mini-sector. Driver and Race Comparisons: Facilitate multi-driver evaluations with ready-to-use datasets. Dynamic Database: Updates automatically with preprocessed data after each race. Use Cases Build advanced visualizations to understand F1 performance dynamics. Apply machine learning models to predict driver or team success. Study the impact of car setups and driving styles on race outcomes. Structure Driver Data: Includes detailed lap times, RPM, and braking data. Race Information: Metadata about circuits, weather, and track conditions. Preprocessed Tables: Optimized for quick access and analysis. Intended Audience F1 fans exploring race telemetry. Researchers in motorsports analytics. Developers building visualization or simulation tools.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The dataset is a comprehensive, structured collection of historical Formula 1 race data compiled from the Ergast API. It is organized in a relational format across multiple CSV files, each capturing a different aspect of the sport. The `races.csv` file includes metadata on each race such as date, circuit, and season. The `results.csv` file provides final race outcomes for every driver, while `qualifying.csv` contains qualifying session results. `lap_times.csv` and `pit_stops.csv` offer granular, session-level data for each driverโs performance throughout the race. Additional files such as `drivers.csv` and `constructors.csv` provide biographical and team-related information, while `constructor_standings.csv`, `driver_standings.csv`, and `constructor_results.csv` track season-long performance. Files like `circuits.csv`, `status.csv`, and `seasons.csv` provide supporting metadata that enhances the usability and relational structure of the dataset. This dataset is well-suited for time series analysis, predictive modeling, performance evaluation, and motorsport analytics.
Facebook
TwitterAttribution-ShareAlike 4.0 (CC BY-SA 4.0)https://creativecommons.org/licenses/by-sa/4.0/
License information was derived automatically
Formula 1 Comprehensive Dataset (2020-2025)
Dataset Description This comprehensive Formula 1 dataset contains detailed racing data spanning from 2020 to 2025, including race results, qualifying sessions, championship standings, circuit information, and historical driver statistics.
Perfect for:
๐ F1 performance analysis
๐ค Machine learning projects
๐ Data visualization
๐ Championship predictions
๐ Racing statistics research
๐ Files Included 1. f1_race_results_2020_2025.csv (53 entries) Race winners and results from Grand Prix weekends
Date, Grand Prix name, race winner
Constructor, nationality, grid position
Race time, fastest lap time, points scored
Q1, Q2, Q3 session times
Grid positions, laps completed
Driver and constructor information
Points accumulation over race weekends
Wins, podiums, pole positions tracking
Season-long championship battle data
Constructor points and wins
Team performance metrics
Manufacturer rivalry data
Track length, number of turns
Lap records and record holders
Circuit designers and first F1 usage
Career wins, poles, podiums
Racing entries and achievements
Active and retired driver records
Multiple data types in one file
Ready for immediate analysis
Comprehensive F1 information hub
๐ง Data Features Clean & Structured: All data professionally format
Facebook
TwitterWelcome to the Formula 1 dataset!
This page includes a Formula 1 dataset that has been scraped from two main sources. The first source is the Formula 1 website, and the second source is data.world. Both sources are highly reliable, and the data from these sites have been used as part of Kaggle competitions in the past. Four csv files named circuits, constructors, drivers and driverGrid are available on this page. The data can be used for a range of beneficial outcomes, such as exploratory data analysis, back-end database building or for creating an application.
I wish you all the best in your learning journey!
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Explore how Google's F1 database technology evolved from NoSQL to power $100B+ in ad revenue, and what this means for modern data infrastructure startups.
Facebook
Twitterhttps://creativecommons.org/publicdomain/zero/1.0/https://creativecommons.org/publicdomain/zero/1.0/
Formula One is the highest class of international racing for open-wheel single-seater racing cars sanctioned by the Fรฉdรฉration Internationale de l'Automobile (FIA). Ever since its inaugural season in 1950, Formula1 has been regarded as the pinnacle of motorsport.
This dataset contains detailed information about qualifying and race results for all the tracks over the course of multiple seasons. There is a separate directory for each season. There are 2 sub-directories for each season, namely: Qualifying Results and Race Results. The Race Results directory contains an overall_race_results.csv file which summarizes the race results throughout the entire season. It also contains multiple .csv files for the results of each race in the season. The Qualifying Results directory contains multiple .csv files for the qualifying results before the start of each race.
For the 1982 season and before the qualifying results contain only 1 entry in the file which is that of the polesitter. The lap times of the other drivers were not accounted for, and on the official website there is only 1 entry under the qualifying results.
F1 is one of my favorite sports and I almost never miss a race ๐
The motivation behind creating this dataset was to learn more about web scraping and try to perform a statistical analysis of the data. Some of the things you could do with the entire dataset are as follows: - Identify the driver with the most poles - Compare qualifying times of different drivers (championship contenders, team-mates, etc) - Determine how often a particular driver out-qualifies his team-mate - Compare qualifying lap times of a race from previous seasons - Identify the driver with the most number of wins at a particular track - Analyze how the championship battle unfolded based on the number of points scored by the drivers (specially interesting for the 2021 f1 season ๐) - Identify drivers with the highest number of wins, podiums, DNFs, etc - Compare the average lap times of different tracks to identify the slowest and fastest tracks on the calendar - Compare the number of laps for each race in the season (Belgium 2021 being the clear winner ๐) - Find out who won the Driver's Championship based on the total number of points - Find out who won the Constructor's Championship based on the total number of points for each team
DNF: Did Not Finish. Commonly used nomenclature for drivers that crashed/failed to complete the entire raceDNQ: Did Not Qualify. Eliminated missing values from the qualifying datasets by introducing this abbreviation for drivers who failed to qualify.NC: Not Confirmed. For drivers that DNF the term NC is used in the Position columnDQ: Disqualified. Generally drivers are disqualified from races due to technical infringements or a breach of sporting regulations (Example: Sebastian Vettel was disqualified from the 2021 Hungarian Grand Prix due to fuel irregularites and stripped of all the points he earned from finishing the race in P2)As I collect more data for the previous seasons, I will create new versions for the dataset. The goal with this dataset is to create an archive of qualifying and race data from 1950-2021. The dataset will also be updated when the 2022 season commences.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
227 Global export shipment records of F1 Mobile with prices, volume & current Buyer's suppliers relationships based on actual Global export trade database.
Facebook
TwitterAttribution-NonCommercial 4.0 (CC BY-NC 4.0)https://creativecommons.org/licenses/by-nc/4.0/
License information was derived automatically
This dataset is a result of extensive scraping, merging, and processing from multiple F1 data sources including: 1. FastF1 API โ for lap data, stint & tire compound info 2. Open-Meteo โ for historical weather per race location 3.Ergast API / Telemetry tools โ for race schedules and positions
What the Dataset Contains: Each row represents a driver's stint in a particular race and includes: 2. Driver & Race Details: Driver, Race Name, Season, Team, Round 3. Behavior Metrics: Aggression score, Fast lap attempts, Tire usage aggression 4. Pit Stop Data: Number of pit stops, average stop time, stint length, pit lap, pit duration 5. Weather Metrics: Track temperature, air temperature, humidity, wind speed
Facebook
Twitterwasmdashai/db-arabic-f1-nn dataset hosted on Hugging Face and contributed by the HF Datasets community
Facebook
TwitterThis data was recorded during Flight 1 of the Blue Origin Deorbit, Descent, and Landing Tipping Point (BODDL-TP) Game Changing Development (GCD) Program. The flight included IMU, cameras for terrain relative navigation, and range and velocity lidar sensors. The flight was completed under NASA contract 80LARC19C0005 in October 2020.
Facebook
TwitterThis dataset provides information about the number of properties, residents, and average property values for Road F1 cross streets in Schuyler, NE.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Comprehensive dataset containing 15 verified F1 locations in Indonesia with complete contact information, ratings, reviews, and location data.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Comprehensive dataset containing 32 verified Formula 1 locations in Russia with complete contact information, ratings, reviews, and location data.
Facebook
Twitterhttps://creativecommons.org/publicdomain/zero/1.0/https://creativecommons.org/publicdomain/zero/1.0/
https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F18335022%2Ff10720cabaa8ea7568c73b26c1b2a6d2%2FScreenshot%202025-04-07%20213220.png?generation=1744116657962022&alt=media" alt="">
The Japanese Grand Prix is a motor racing event in the calendar of the Formula One World Championship.
The dataset was generated using the FastF1 API by loading the Japanese Grand Prix race session (denoted as "R") for the 2025 season. Instead of directly accessing a dedicated pit stop attribute (which might not exist in some versions of the API), the data is obtained by filtering the laps data to identify laps that include pit stop times. This approach leverages the 'PitOutTime' field to capture when pit stops occurred during the race.
The context of this data is rooted in understanding the in-race strategies related to pit stops, which can greatly influence race outcomes. Teams and analysts use such information to assess the efficiency of pit stop timings and their impact on overall performance.
Circuit length: 5.807 km (3.608 miles)
First held: 1963
Laps: 53
Most wins (constructors): McLaren (9)
Most wins (drivers): Michael Schumacher (6)
Number of times held: 50
The dataset consists of all information on the Formula 1 Japanese Grand Prix 2025, drivers, constructors, qualifying, lap times, and pit stops.
Time period: 4 - 6 April 2025
The data is fetched using Fast F1 Package.
Unlock strategic insights and race trends from the Japanese Grand Prix to fuel your data analysis, visual storytelling, or predictive modeling in motorsport analytics.
"Racing is life. Anything before or after is just waiting." โ Steve McQueen
https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F18335022%2Fb4411127cf9ae6df2b503fd67fb8099d%2FScreenshot%202025-04-07%20213245.png?generation=1744116687810902&alt=media" alt="">
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
454 Global exporters importers export import shipment records of F1 mobile with prices, volume & current Buyer's suppliers relationships based on actual Global export trade database.
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Max Verstappen's Full Race Car Data: 2024 Miami Grand Prix
Data Source
Data obtained using the fastf1 API, ensuring reliability and accuracy in the collected data.
Metrics
The dataset comprises a comprehensive range of metrics crucial for analyzing Max Verstappen's performance during the 2024 Miami Grand Prix, including:
Data: Timestamps for each recorded data point. RPM: Engine revolutions per minute, indicating engine performance and power delivery. Speed:โฆ See the full description on the dataset page: https://huggingface.co/datasets/Draichi/Formula1-2024-Miami-Verstappen-telemetry.
Facebook
TwitterThis archived Paleoclimatology Study is available from the NOAA National Centers for Environmental Information (NCEI), under the World Data Service (WDS) for Paleoclimatology. The associated NCEI study type is Borehole. The data include parameters of borehole with a geographic location of China, Eastern Asia. The time period coverage is from 450 to -33 in calendar years before present (BP). See metadata information for parameter and study location details. Please cite this study when using the data.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
592 Global export shipment records of F1 Phone with prices, volume & current Buyer's suppliers relationships based on actual Global export trade database.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
11 Global import shipment records of F1 Phone with prices, volume & current Buyer's suppliers relationships based on actual Global export trade database.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Biomedical texts provide important data for investigating drug-drug interactions (DDIs) in the field of pharmacovigilance. Although researchers have attempted to investigate DDIs from biomedical texts and predict unknown DDIs, the lack of accurate manual annotations significantly hinders the performance of machine learning algorithms. In this study, a new DDI prediction framework, Subgraph Enhance model, was developed for DDI (SubGE-DDI) to improve the performance of machine learning algorithms. This model uses drug pairs knowledge subgraph information to achieve large-scale plain text prediction without many annotations. This model treats DDI prediction as a multi-class classification problem and predicts the specific DDI type for each drug pair (e.g. Mechanism, Effect, Advise, Interact and Negative). The drug pairs knowledge subgraph was derived from a huge drug knowledge graph containing various public datasets, such as DrugBank, TwoSIDES, OffSIDES, DrugCentral, EntrezeGene, SMPDB (The Small Molecule Pathway Database), CTD (The Comparative Toxicogenomics Database) and SIDER. The SubGE-DDI was evaluated from the public dataset (SemEval-2013 Task 9 dataset) and then compared with other state-of-the-art baselines. SubGE-DDI achieves 83.91% micro F1 score and 84.75% macro F1 score in the test dataset, outperforming the other state-of-the-art baselines. These findings show that the proposed drug pairs knowledge subgraph-assisted model can effectively improve the prediction performance of DDIs from biomedical texts.
Facebook
TwitterAbout Dataset This dataset is designed for Formula 1 (F1) enthusiasts, researchers, and data scientists aiming to analyze performance metrics of F1 drivers and cars. It includes telemetry data collected and preprocessed from FastF1 and Ergast APIs, offering valuable insights into driver performance across various races and scenarios.
The dataset is structured to facilitate dynamic updates and high-quality visualizations, making it suitable for advanced analyses such as race strategy optimization, performance comparisons, and machine learning applications. Key metrics include lap times, sector splits, RPM, throttle, speed, and more, enabling users to identify critical performance bottlenecks and trends.
Features High-Resolution Telemetry Data: Every tenth of a second for temporal data and lap-based aggregates. Sector and Mini-Sector Analysis: Performance indices calculated for each driver in every circuit mini-sector. Driver and Race Comparisons: Facilitate multi-driver evaluations with ready-to-use datasets. Dynamic Database: Updates automatically with preprocessed data after each race. Use Cases Build advanced visualizations to understand F1 performance dynamics. Apply machine learning models to predict driver or team success. Study the impact of car setups and driving styles on race outcomes. Structure Driver Data: Includes detailed lap times, RPM, and braking data. Race Information: Metadata about circuits, weather, and track conditions. Preprocessed Tables: Optimized for quick access and analysis. Intended Audience F1 fans exploring race telemetry. Researchers in motorsports analytics. Developers building visualization or simulation tools.