Get Started in Minutes
This guide will help you access and explore the TracingInsights 2026 F1 data repository. No API keys or authentication required — just clone and start analyzing!Clone the Repository
Clone the repository to your local machine using Git:Alternatively, download specific files directly from GitHub without cloning:
The repository size varies depending on how many sessions have been completed in the season. Expect 1-5 GB for a full season.
- Navigate to the repository
- Browse to the file you need
- Click “Raw” and save the JSON file
Explore the File Structure
The repository is organized by Grand Prix and session type:You’ll see:You’ll find:
- Grand Prix folders — One folder per race (e.g.,
Australian Grand Prix/) - Pre-Season Testing folders — Separate folders for testing sessions
- Python scripts — Data extraction scripts (FP1.py, Q.py, R.py, etc.)
- DATA_REFERENCE.md — Comprehensive field documentation
Practice 1/,Practice 2/,Practice 3/Qualifying/Sprint Shootout/,Sprint/(if applicable)Race/
Navigate a Session Folder
Each session folder contains:Session-level files:
drivers.json— All driver and team informationweather.json— Weather conditions throughout the sessionrcm.json— Race control messages (flags, DRS, penalties)corners.json— Circuit corner positions and layout data
ALB/,VER/,LEC/, etc. — One folder per driver (3-letter code)
1_tel.json,2_tel.json, … — Telemetry data for each laplaptimes.json— Lap timing data for all laps
Load and Explore Data
Let’s load and inspect a JSON file. Here’s an example using Python:Example output:
All JSON files follow a consistent structure. The top-level key matches the data type (e.g.,
{"drivers": [...]}, {"tel": {...}}).Access Telemetry Data
Telemetry data is stored per lap. Each file contains arrays of synchronized data points:Available telemetry fields:
time— Time from lap start (seconds)speed— Speed in km/hthrottle— Throttle position (0-100%)brake— Brake application (0 or 1)rpm— Engine RPMgear— Current gear (1-8)drs— DRS statusx,y,z— 3D position coordinatesdistance— Distance from lap start (meters)acc_x,acc_y,acc_z— Acceleration in three axes
Load Weather Data
Weather conditions are sampled approximately once per minute:
Weather data uses abbreviated field names (e.g.,
wT, wAT, wH). See the Weather Reference for complete field explanations.Common Data Access Patterns
Finding the Fastest Lap
To find a driver’s fastest lap, load their lap times:Comparing Two Drivers
Compare telemetry from two drivers on the same lap:Analyzing Weather Impact
Correlate weather conditions with lap times:Working with Race Control Messages
Race control messages provide context about track conditions:Next Steps
Now that you can access the data, explore more advanced topics:Data Reference
Complete documentation of all fields and data structures
Analysis Guides
Step-by-step tutorials for common analysis tasks
Field Specifications
Detailed field reference and specifications
Python Examples
Real-world examples and visualization projects
Need Help?
If you encounter issues or have questions:- Check the DATA_REFERENCE.md in the repository
- Open an issue on GitHub
- Contact TracingInsights
- Review the FastF1 documentation for additional context
