Why don't we have locations?

Location

The approximate location of the cars on the circuit, at a sample rate of about 3.7 Hz.
Useful for gauging their progress along the track, but lacks details about lateral placement — i.e. whether the car is on the left or right side of the track. The origin point (0, 0, 0) appears to be arbitrary and not tied to any specific location on the track.

curl "https://api.openf1.org/v1/location?session_key=9161&driver_number=81&date>2023-09-16T13:03:35.200&date<2023-09-16T13:03:35.800"

Output:

[

  {

    "date": "2023-09-16T13:03:35.292000+00:00",

    "driver_number": 81,

    "meeting_key": 1219,

    "session_key": 9161,

    "x": 567,

    "y": 3195,

    "z": 187

  },

  {

    "date": "2023-09-16T13:03:35.752000+00:00",

    "driver_number": 81,

    "meeting_key": 1219,

    "session_key": 9161,

    "x": 489,

    "y": 3403,

    "z": 186

  }

]

HTTP Request

GET https://api.openf1.org/v1/location

Sample URL

https://api.openf1.org/v1/location?session_key=9161&driver_number=81&date>2023-09-16T13:03:35.200&date<2023-09-16T13:03:35.800

Attributes

Location
The approximate location of the cars on the circuit, at a sample rate of about 3.7 Hz.
Useful for gauging their progress along the track, but lacks details about lateral placement — i.e. whether the car is on the left or right side of the track. The origin point (0, 0, 0) appears to be arbitrary and not tied to any specific location on the track.

curl "https://api.openf1.org/v1/location?session_key=9161&driver_number=81&date>2023-09-16T13:03:35.200&date<2023-09-16T13:03:35.800"
Output:

[
{
"date": "2023-09-16T13:03:35.292000+00:00",
"driver_number": 81,
"meeting_key": 1219,
"session_key": 9161,
"x": 567,
"y": 3195,
"z": 187
},
{
"date": "2023-09-16T13:03:35.752000+00:00",
"driver_number": 81,
"meeting_key": 1219,
"session_key": 9161,
"x": 489,
"y": 3403,
"z": 186
}
]
HTTP Request
GET https://api.openf1.org/v1/location

Sample URL
[https://api.openf1.org/v1/location?session_key=9161&driver_number=81&date>2023-09-16T13:03:35.200&date<2023-09-16T13:03:35.800](https://api.openf1.org/v1/location?session_key=9161&driver_number=81&date%3E2023-09-16T13:03:35.200&date%3C2023-09-16T13:03:35.800)

Attributes
Name Description
date The UTC date and time, in ISO 8601 format.
driver_number The unique number assigned to an F1 driver (cf. [Wikipedia](https://en.wikipedia.org/wiki/List_of_Formula_One_driver_numbers#Formula_One_driver_numbers)).
meeting_key The unique identifier for the meeting. Use latest to identify the latest or current meeting.
session_key The unique identifier for the session. Use latest to identify the latest or current session.
x The 'x' value in a 3D Cartesian coordinate system representing the current approximate location of the car on the track.
y The 'y' value in a 3D Cartesian coordinate system representing the current approximate location of the car on the track.
z The 'z' value in a 3D Cartesian coordinate system representing the current approximate location of the car on the track.

The issue describes a missing location data endpoint in an F1 API. Start by examining the existing API structure and data sources in the repository to understand how other endpoints (like session_key, driver_number) are implemented. Look for similar data models and service classes to see where location data (x, y, z coordinates) should be integrated. Determine what 'done' looks like by checking if the new endpoint returns location data as shown in the example JSON.

由索引模型根据 Issue 内容生成。