WinTAX KPI demo

F2 Baku 2022 / 2024 / 2025 · data served by the POC API, only the numbers each chart needs

1. Average tyre pressure per lap of the selected run

One API call: POST /api/query {select:{run}, channels:[alias:TyrePressureFL…RR], stats:[avg,min,max]}. The alias maps to TPMS_xxsts_pDash from 2024 and to TPMS_xxsts_pAvg in 2022, so the same chart works across years.

2. Lap times per session across the Baku editions

Every lap of the chosen driver in every ingested year (select:{driver, flying_only}), grouped by year and session kind. Compare how pace evolved between editions.

3. A WinTAX virtual channel, evaluated server-side, one value per lap of the selected session

The expression uses the WinTAX VCH language (337 functions: chmax, integ, timeatcondlap, butterworth…). The server loads only the channels the formula needs, evaluates it per lap, and returns one number per lap. Try chmax(CarSpeed), integ(CarSpeed/3.6) or timeatcondlap(rPedal>95).

4. Whole series streamed to the client at the resolution you ask for

POST /api/stream {select:{lap_ids}, channels:[CarSpeed, RPM, rPedal, pBrakeF, aSteering, expr:...], hz, method, format}. The API returns every sample (native) or a downsampled series, as JSON, raw float32, or delta-coded int16 (0.01 resolution), brotli-compressed over the wire. The byte counter shows what actually crossed the network versus the raw payload.