The visible_area represents the portion of the pitch that is visible to the broadcast camera at a given frame. It is provided as a polygon in pitch coordinates and reflects the camera’s current field of view, excluding areas that are off-screen or obscured. As far as I know, this is only used by StatsBomb, but it seems relevant for other broadcast tracking data providers too.
At the moment, visible_area data (when available from providers such as StatsBomb) is stored in .other_data and is not transformed when coordinate transformations are applied. Thus, users must manually transform and manage this data. This issue was previously mentioned in #464.
By making visible_area part of the model it can be automatically transformed alongside player and ball positions such that users no longer need provider-specific or ad-hoc handling via .other_data.
The
visible_arearepresents the portion of the pitch that is visible to the broadcast camera at a given frame. It is provided as a polygon in pitch coordinates and reflects the camera’s current field of view, excluding areas that are off-screen or obscured. As far as I know, this is only used by StatsBomb, but it seems relevant for other broadcast tracking data providers too.At the moment,
visible_areadata (when available from providers such as StatsBomb) is stored in.other_dataand is not transformed when coordinate transformations are applied. Thus, users must manually transform and manage this data. This issue was previously mentioned in #464.By making
visible_areapart of the model it can be automatically transformed alongside player and ball positions such that users no longer need provider-specific or ad-hoc handling via.other_data.