A few quirks I noticed: - `OWN_GOAL` is not implemented and the documentation for it is a bit unclear - `ClearanceEvent` is not implemented. it is a subtype id:12 for event - `BALL LOST` id: 7 - The deserializer code notes the [MS_EVENT_TYPE_CARD](https://github.com/PySport/kloppy/blob/887b5ef1e1fb219ab83cf389b890d258ba4c8132/kloppy/infra/serializers/event/metrica/json_deserializer.py#L84) but is only used to check ball owning team ([here](https://github.com/PySport/kloppy/blob/887b5ef1e1fb219ab83cf389b890d258ba4c8132/kloppy/infra/serializers/event/metrica/json_deserializer.py#L239)) - Similar to the clearance, `InterceptionEvent` is a subtype id:23 for event - `BALL LOST` id: 7 - For the `BallOutEvent` , it [checks if the event ended out of the field and adds a synthetic out event](https://github.com/PySport/kloppy/blob/887b5ef1e1fb219ab83cf389b890d258ba4c8132/kloppy/infra/serializers/event/metrica/json_deserializer.py#L379). This only looks if the [PassResult is OUT](https://github.com/PySport/kloppy/blob/887b5ef1e1fb219ab83cf389b890d258ba4c8132/kloppy/infra/serializers/event/metrica/json_deserializer.py#L86). Maybe it can be updated to use the `BALL OUT` event with id: 6
A few quirks I noticed:
OWN_GOALis not implemented and the documentation for it is a bit unclearClearanceEventis not implemented. it is a subtype id:12 for event -BALL LOSTid: 7InterceptionEventis a subtype id:23 for event -BALL LOSTid: 7BallOutEvent, it checks if the event ended out of the field and adds a synthetic out event. This only looks if the PassResult is OUT. Maybe it can be updated to use theBALL OUTevent with id: 6