Some scenes that cross the antimeridian and poles produce correct geometry when running on arm64, but incorrect when
running on amd64. This change checks that the area of the geometry is larger than
a correct one should be, that the creation of it fails, which is seen as better than
outputting a bad geometry. Hopefully, we'll be able to figure out the underlying cause
of this in the future
produce a ValueError for scenes that have a geometry of type Polygon with no coordinates (e.g., [ [ ] ]). This is probably a bug in the Singergize processing, since a Polygon with coordinates is invalid. This happens when there's no data in the scene after the L2A processing, even though there was some in the L1C processing. The ValueError will allow consumers to mark these scenes as invalid.
Related issues
Description
Some scenes that cross the antimeridian and poles produce correct geometry when running on arm64, but incorrect when running on amd64. This change checks that the area of the geometry is larger than a correct one should be, that the creation of it fails, which is seen as better than outputting a bad geometry. Hopefully, we'll be able to figure out the underlying cause of this in the future
produce a ValueError for scenes that have a geometry of type Polygon with no coordinates (e.g.,
[ [ ] ]). This is probably a bug in the Singergize processing, since a Polygon with coordinates is invalid. This happens when there's no data in the scene after the L2A processing, even though there was some in the L1C processing. The ValueError will allow consumers to mark these scenes as invalid.Checklist