collection metadata merging: min/max statistics handling

[soxofaan]

While checking https://github.com/openEOPlatform/architecture-docs/issues/288 issues related to stac summaries statistics, e.g. :

TypeError("Error parsing 'eo:cloud_cover' of StacSummaries: Could not parse Statistics object, actual: {'maximum': 100, 'minimum': 0}")

This implementation looks for "min" and "max" fields https://github.com/Open-EO/openeo-aggregator/blob/804ca2214f627fe693e07b1cb9537c42f176449a/src/openeo_aggregator/metadata/models/statistics.py#L14-L52

but https://github.com/radiantearth/stac-spec/blob/v1.0.0-rc.2/collection-spec/collection-spec.md#stats-object works with "minimum" and "maximum"

@JeroenVerstraelen did you get min/max from a spec, or something else? How can it be changed to minimum/maximum?

related to #76

[JeroenVerstraelen]

That requirement comes from the openeo api specification: https://github.com/Open-EO/openeo-api/blob/master/openapi.yaml#L4467

[soxofaan]

Interesting, @m-mohr is there an inconsistency here about stats objects as collection summaries?

• should have fields "min"/"max" according to https://github.com/Open-EO/openeo-api/blob/16b1122c7090cc4fedcabace48686a4f73c1c876/openapi.yaml#L4450-L4474
• should have fields "minimum"/"maximum" according to https://github.com/radiantearth/stac-spec/blob/v1.0.0-rc.2/collection-spec/collection-spec.md#stats-object

[m-mohr]

• min/max was used in STAC 0.9 and we based the openEO API 1.0 on this version.
• minimum/maximum was adopted somewhere in STAC 1.0 beta/rc, so both can occur depending on the STAC version implemented. I'll update to minimum/maximum in the API with the work that is going on to update to STAC 1.0.

[m-mohr]

See https://github.com/Open-EO/openeo-api/commit/8a112b7fa44056abbc30f484634d63a519e23352