Version 0.2.2
This schema defines the Event Data as described in the Common Data Format paper.
This schema describes a single JSON Object with a JSON Lines file.
Unique match identifier
Indicates if synced tracking data is available (true) or not (false)
Unique identifier of the event
Absolute time in UTC of when the event started
Name of the event type
Name of the event subtype
Denotes whether the event was successful (true) or not (false)
Detailed event outcome options
Unique identifier of the player performing the action
Unique team identifier of the player performing the action
Unique identifier of the player receiving a pass, leave null if event is not a pass
Absolute time in UTC of the first moment the ball was received
x location where the action of player_id happened (m)
y location where the action of player_id happened (m)
x location where the action of player_id ended (m)
y location where the action of player_id ended (m)
Denotes the body part used by player_id
The match clock as a string in format MM:SS.mm
Calculated xG value between [0,1]
Calculated post-shot xG value between [0,1]
Calculated xPass value between [0,1]
Expected possession value between [-1,1]
Number of opposing players that have been outplayed by a pass according to the traditional packing approach
Number of opposing players that have been outplayed by a pass according to the horizontal packing approach
Was this event reviewed by the video assistant referee (true) or not (false
Was the ruling on the field confirmed (true) or not (false)
Frame identifier from the tracking data related to the event at (x, y)
Frame identifier from the tracking data related to the event at (xend, yend)
x location of the player committing the action according to the tracking data
y location of the player committing the action according to the tracking data