[Statsbomb] Fix freeze frame transformation #526
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes two bugs in the coordinate transformation of freeze frames: - due to an indentation error, freeze frame coordinates were only transformed if an orientation change was needed - since the ball coordinates in the freeze frame were taken from the already transformed event, the ball coordinates were transformed twice Fixes PySport#464
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes two bugs in the coordinate transformation of freeze frames:
Fixes #464
This is an alternative solution for #481. Still, it's maybe not the cleanest fix but at least it keeps everything contained in the StatsBombDeserializer now.