gpdata

Disclaimer: This is an unofficial, fan-made project built for personal/educational use. It is not affiliated with, endorsed by, or connected in any way to Formula 1, Formula One Management, the FIA, or any F1 team, driver, or sponsor. All F1-related names, logos, and marks are the property of their respective owners. Data is sourced from F1's public live-timing feeds for non-commercial, informational use only.

Scope

A browsable archive of Formula 1 season data: every Grand Prix weekend (race, qualifying, and sprint sessions where applicable) from 2018 onward, with results, weather, and timing pulled from F1's own live-timing service into a local database.

The season/calendar grid view and the per-GP detail page (full qualifying/race classification with Q1/Q2/Q3 breakdown, weather, and results tables) are both fully working end-to-end.

Live at gpdata.app.

Prerequisites

• Node.js 26 (pinned in .nvmrc — nvm use will pick it up)
• Docker (for local Postgres via docker-compose.yml)
• npm

How it works

Data pipeline — lib/crawler/ fetches season and session data directly from F1's public live-timing API (https://livetiming.formula1.com/static/): calendar, drivers, qualifying results, race results, and weather, per Grand Prix. Data is normalized and upserted into Postgres (schema in migrations/) via Knex, so re-running the crawler is safe and idempotent.

UI — a Next.js app reads directly from Postgres to render:

• a season grid (/) — one tile per race/sprint weekend, with round info, winner, pole, and weather at a glance, filterable by year
• a per-GP detail page (/gp/[key]) — full session breakdown: weather, a Qualifying/Race (or Sprint Qualifying/Sprint) tab switch, Q1/Q2/Q3 classification, and race results with gap/best lap/pit stops/fastest-lap badge

Database schema

erDiagram
    GRANDS_PRIX ||--o{ SESSIONS : has
    SESSIONS ||--o{ QUALIFYING_RESULTS : has
    SESSIONS ||--o{ RACE_RESULTS : has
    DRIVERS ||--o{ QUALIFYING_RESULTS : has
    DRIVERS ||--o{ RACE_RESULTS : has

    GRANDS_PRIX {
        int id PK
        int number
        int year
        text official_name
        text name
        text circuit_name
        text country_code
        text location
        text sprint_qualifying_path
        text sprint_path
        text qualifying_path
        text race_path
    }

    SESSIONS {
        int id PK
        session_type type
        int gp_id FK
        timestamptz start_date
        timestamptz end_date
        timestamp start_date_local
        timestamp end_date_local
        text gmt_offset
        numeric air_temp
        numeric track_temp
        numeric humidity
    }

    DRIVERS {
        uuid id PK
        int racing_number
        text name
        text team_name
        text team_color
        text headshot_url
    }

    QUALIFYING_RESULTS {
        uuid id PK
        int session_id FK
        uuid driver_id FK
        int position
        text q1_time
        text q2_time
        text q3_time
        boolean knocked_out
    }

    RACE_RESULTS {
        uuid id PK
        int session_id FK
        uuid driver_id FK
        int position
        text best_laptime
        text gap_to_leader
        text gap_to_position_ahead
        boolean dnf
        int number_of_pit_stops
    }

Loading

grands_prix and sessions use F1's own numeric IDs as primary keys (not generated); drivers, qualifying_results, and race_results use generated UUIDs. See migrations/ for the full DDL.

How to run it

1. Install the pinned Node version and dependencies:

   nvm use
   npm install

2. Start Postgres:

   docker compose up -d

3. Run migrations to create the schema:

   npm run migrate

4. Hydrate the database with real F1 data (one year, or every available year):

   npm run hydrate -- 2026        # single season
   npm run hydrate-all            # every season in lib/years.ts

5. Start the app:

   npm run dev

   Visit http://localhost:3000.