stac-extensions/card4l

Clarify open Optical questions with CEOS

Closed this issue · 2 comments

m-mohr commented

  • 2.13 (SR): CARD4L lists no specific requirements thus it's missing in this document, too.

  • 3.2 (SR) / 3.3 (ST): Measurement Uncertainty is not required and it was not clear in which form this should be provided.
    Also the CARD4L specification states for SR that

    "[i]n current practice, users determine fitness for purpose based on knowledge of the lineage of the data,
    rather than on a specific estimate of measurement uncertainty."

    Thus this requirement is not captured in this document.

  • 3.3 (SR): Measurement Normalisation is not required and it was not clear in which form this should be provided.
    Thus this requirement is not captured in this document, but we have added a link relation type to link to information on measurement normalisation.

  • 4.1 (SR): This requirement doesn't list any direct requirements for the metadata.

m-mohr commented

I received some responses from CEOS:

  • 2.13 (SR): CARD4L lists no specific requirements thus it's missing in this document, too.

Agreed – not a requirement at this time for either Threshold or Target, so that makes sense to me.

  • 3.2 (SR) / 3.3 (ST): Measurement Uncertainty is not required and it was not clear in which form this should be provided.

Agreed – not a requirement at this time at the Threshold level.

  • 3.3 (SR): Measurement Normalisation is not required and it was not clear in which form this should be provided.
    Thus this requirement is not captured in this document, but we have added a link relation type to link to information on measurement normalisation.

Agreed – not a requirement at this time at the Threshold level. I’m not clear about adding the link. That sounds like additional information. Is that done with other parameters as well? (If so, may want to evaluate consistency with that approach across all the parameters?)

  • 4.1 (SR): This requirement doesn't list any direct requirements for the metadata.

Agreed – this is not a General Metadata requirement. This is part of the Geometric Corrections section, which provides direction on accuracy requirements (BTW, we are discussing this parameter as part of our annual update.). General Metadata requirements are in 1.8 and 1.9, so I wouldn’t expect any STAC metadata requirements aligned with this section.

m-mohr commented

So it seems there's no real change required. We'll just leave it as it is.