Overview
Corner data defines the physical geometry of the racetrack, providing coordinates and metadata for each numbered corner. This data is essential for spatial analysis, track visualization, and correlating telemetry position data with specific track locations.Corner data enables you to map telemetry coordinates to real track features, create accurate track visualizations, and analyze driver performance through specific corners.
File Location
Corner data is stored once per circuit (consistent across sessions at the same track):Pre-Season Testing 2/Practice 3/corners.jsonBahrain Grand Prix/Race/corners.jsonMonaco Grand Prix/Qualifying/corners.json
The same circuit will have identical corner data across all sessions (Practice, Qualifying, Race).
Data Structure
The JSON file contains parallel arrays where each index represents one corner:Field Reference
Sequential number identifying each corner of the circuit.Range: 1 to number of corners (typically 12-20 corners per circuit)
Example:
Example:
[1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]Horizontal X coordinate of the corner on the track map.Unit: meters
Coordinate system: Arbitrary origin, consistent with telemetry position data
Example:
Coordinate system: Arbitrary origin, consistent with telemetry position data
Example:
[42.41, 820.78, 1912.97, 7487.75, 5820.23, ...]Horizontal Y coordinate of the corner on the track map.Unit: meters
Coordinate system: Arbitrary origin, consistent with telemetry position data
Example:
Coordinate system: Arbitrary origin, consistent with telemetry position data
Example:
[8329.20, 7879.04, 8065.44, 6790.71, 4860.74, ...]Visual offset angle in degrees, used to position corner number markers on track maps in a logical direction (usually orthogonal to the track).Unit: ° (degrees)
Range: -360 to +360
Purpose: Determines where to place corner number labels so they don’t overlap with the track line
Example:
Range: -360 to +360
Purpose: Determines where to place corner number labels so they don’t overlap with the track line
Example:
[-246.62, -101.18, -261.39, -349.60, -211.50, ...]This angle is for visualization purposes only—it positions corner labels away from the track line on a map. It does NOT represent the corner’s turning angle or trajectory.
Distance from the start/finish line to this corner marker, measured along the racing line.Unit: meters
Example:
Example:
[706.12, 802.13, 909.97, 1487.44, 1775.40, ...]This field is crucial for correlating telemetry
distance values with corner numbers. For example, if telemetry shows distance = 1500, you’re between corners 3 (910m) and 4 (1487m).Rotation of the entire circuit coordinate system in degrees. Used to align telemetry position data with official track map orientation.Unit: degrees
Value: Single number (applies to entire track) or
Example:
Value: Single number (applies to entire track) or
null if no rotation neededExample:
92.0 (track is rotated 92° clockwise from north-up orientation)To match official FIA track maps, apply this rotation to all X, Y coordinates from telemetry and corner data:
Real Data Example
Here’s actual corner data from Bahrain International Circuit (Pre-Season Testing 2):- 15 corners total (typical for Bahrain)
- Rotation: 92° - Track map needs significant rotation to match north-up orientation
- Corner 4 (Turn 4) is at distance 1487m - a famous heavy braking zone after the main straight
- Corner 11 (Turn 11) has negative Y coordinate (-664m) - track extends below the origin point
Use Cases
Track Visualization
Plotting the CircuitCorner Performance Analysis
Identify Corner Entry/Exit PointsSpatial Queries
Find Closest Corner to Telemetry PositionTrack Map Rotation
TheRotation field aligns the coordinate system with official track maps:
- Why Rotation Exists
- Applying Rotation
- When to Use Rotation
GPS coordinates and telemetry use an arbitrary coordinate system where:
- Origin (0, 0) is a reference point near the circuit
- X and Y axes may not align with north/south
Rotation value transforms telemetry coordinates to match official map orientation.Data Quality Notes
Corner positions are approximate marker locations, not the exact apex coordinates. They represent a reference point near each corner for visualization and analysis purposes.
The
Distance field is measured along the racing line, which may differ slightly from the telemetry distance field (measured along the actual car path). Expect small discrepancies (±10-20m) when matching corners to telemetry.Circuit-Specific Examples
Bahrain International Circuit
- 15 corners
- Famous corners: Turn 1 (heavy braking), Turn 4 (long apex), Turn 10 (overtaking zone)
- Track length: ~5412m (corner 15 distance: 4969m, plus run to finish line)
- Rotation: 92° (significant rotation needed for north-up maps)
Monaco Street Circuit
- 19 corners (highest on calendar)
- Famous corners: Sainte-Devote (T1), Casino Square (T5), Rascasse (T16)
- Track length: ~3337m (shortest on calendar)
- Minimal rotation (natural north-south orientation)
Circuit de Spa-Francorchamps
- 19 corners
- Famous corners: La Source (T1), Eau Rouge-Raidillon (T3-4), Pouhon (T9)
- Track length: ~7004m (longest on calendar)
- Significant elevation (captured in telemetry Z coordinate)
Related Pages
- Telemetry - 3D position data (x, y, z) and distance values
- Lap Times - Sector times correlated with corner groups
- Race Control - Incidents referenced by track sector (correlates with corners)
- Drivers - Driver information for performance comparison
