[x] I've updated to the latest version of floodlight
[x] I've checked if a similar issue exists
Issues in old version
StatsBomb parser splits the events by teams to meet with floodlight standards for data classes. For doing so it uses the tID of the team currently in possession. Therefore, defensive actions like tackles are also added to the event class of the offensive team. Since Statsbomb provides a tID, using this value seems more sensible to me.
The Parser requires a locally stored file to include the match_id. While this seems to be a good solution when accessing data through the Statsbomb API interface (with automatic FileIO) it might lead to problems with local files. This should be re-evaluated and at least documented more clearly.
Suggestions for new version
There has been a python package released by the official StatsBomb account, that reads both the open data as well as protected data from the API. Yet, the returned objects are comparably less concise than floodlight Events objects. Thus, it could make sense to integrate the functionality of that package to the StatsBomb parser pipeline.
Checklist
Issues in old version
StatsBomb parser splits the events by teams to meet with floodlight standards for data classes. For doing so it uses the tID of the team currently in possession. Therefore, defensive actions like tackles are also added to the event class of the offensive team. Since Statsbomb provides a tID, using this value seems more sensible to me.
The Parser requires a locally stored file to include the match_id. While this seems to be a good solution when accessing data through the Statsbomb API interface (with automatic FileIO) it might lead to problems with local files. This should be re-evaluated and at least documented more clearly.
Suggestions for new version There has been a python package released by the official StatsBomb account, that reads both the open data as well as protected data from the API. Yet, the returned objects are comparably less concise than floodlight Events objects. Thus, it could make sense to integrate the functionality of that package to the StatsBomb parser pipeline.
https://github.com/statsbomb/statsbombpy