Summary

F1DB provides a comprehensive, free, open-source database of all-time Formula 1 racing data and statistics. It caters to developers, researchers, and enthusiasts building applications, websites, or performing data analysis, offering extensive historical race, driver, constructor, and circuit information. The project aims to be the definitive data source for Formula 1, updated promptly after each race.

How It Works

F1DB offers data in multiple formats including CSV, JSON, Smile, and SQL dumps (MySQL, PostgreSQL, SQLite), allowing flexible integration. Recent versions include detailed circuit layouts and corresponding SVG assets. Data is versioned using a customized CalVer scheme (YYYY.RR.MICRO) that reflects the racing season and round number, ensuring clear tracking of updates.

Quick Start & Requirements

• Build from Source: Requires Java 21. Run ./gradlew clean build. Running tests requires Docker.
• Dependencies: Java 21, Docker (for tests).
• Links: GitHub Discussions for community, GitHub Issues for data problems.

Highlighted Details

• Comprehensive data coverage: All drivers, constructors, engines, tyres, circuits (with layouts and SVG assets), and seasons from 1950 to present.
• Detailed race data: Includes practice, qualifying, sprint, race results, fastest laps, pit stops, and standings.
• Multiple data formats: CSV, JSON, Smile, and SQL dumps for MySQL, PostgreSQL, and SQLite.
• Prompt updates: New releases are published as soon as possible after each race.

Maintenance & Community

The project is maintained by Marcel Overdijk (Creator and core maintainer) and Jules Roy (Circuit SVG assets). Community interaction, questions, and project sharing occur on GitHub Discussions. Data issues are tracked via GitHub Issues. Updates can be followed on X and Bluesky.

Licensing & Compatibility

F1DB is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0). This license permits commercial use and distribution, provided attribution is given to the original authors.

Limitations & Caveats

Building from source with tests requires a Docker environment. While comprehensive, users should verify data accuracy for critical applications, as with any open-source data project. Specific SQL dump compatibility for non-standard database systems might require manual adaptation.