pystac offers a validate method that would have caught the error (in this case it would have reported the [null] spatial extent); validating the batch job results in all of our batch job integration tests in this way might be a quick win.
Not a validation but added a rudimentary metadata check to os_creodias_openeo_k8s/kube_resources/applications/integrationtests/tests/test_batch.py in the context of #632.
https://github.com/Open-EO/openeo-geopyspark-driver/pull/639 messed up batch job results metadata. This was caught in an integration test that happened to
load_stac
it but it still took some digging to get to the root cause.pystac offers a
validate
method that would have caught the error (in this case it would have reported the[null]
spatial extent); validating the batch job results in all of our batch job integration tests in this way might be a quick win.