Versions Compared

Old Version 9

changes.mady.by.user Olivier Gaquiere

Saved on

compared with

New Version Current

changes.mady.by.user Olivier Gaquiere

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Next version of the ICD

...

Here are some addings and improvements already identified for next version: 

TitleDescriptionRef in document
Mission specific requirements 

Comment from Jolyon in version 1.1:

Which would only be needed if we have to add extra queriables for a particular mission?  Otherwise mission class specific json elements should be directly imported from the EOPF STAC metadata?  It could be useful to clarify this in a next version.

2.2

Export PRIP CatalogueFunction to be specified (analyze Geoparquet format)2.2
On demand ProcessingFunction to be specified2.2

Conformance tests

...

.

...

Here is a list of ideas for improvements in a future version

Requirement ImprovementTest to addSTAC-PRIP-COL-REQ-0030 – PRIP STAC Collection mandatory properties

The postman suite should manage to check that the correct collections are defined for each Sentinel/CopEx mission (when defined)

If a collection is not conform, log the property which is not set

STAC-PRIP-ITEM-REQ-0050 – STAC Items common propertiesreport which of the properties are missing --> log the property which is not setSTAC-PRIP-ITEM-REQ-0070 – Expected STAC Assets : Band(s) asset implement for each mission : Sentinel-
2
(L1C, L2A) + Sentinel-3 (OLCI + RBT) yesSTAC-PRIP-ITEM-REQ-0087 – Exposed assets related to sub elements of the EOPF productto testyesSTAC-PRIP-CORE-REQ-0102 – STAC Extensions

Should list which extensions are missing

This will be mission specific, for the postman suite I wonder if we cannot somehow leverage the GIT repository of the EOPF to manage compliance test of the schema (maybe not at the moment while the processors are still in development)

STAC-PRIP-API-REQ-0205 – STAC API ExtensionsShould list which extensions are missingSTAC-PRIP-API-REQ-0200 – STAC API requirements

implemented by STAC API Validator project --> to update

STAC-PRIP-API-REQ-0203 – STAC API limit parameterto testyesGeometry queryable test

Only s_equals operator is used in the query.

implement several queries with various spatial operators (s_intersects, s_contains, etc..), also logical operators NOT, AND etc. (in particular NOT s_intersects)

yes

Published queryable test (and in general datetime queriables)

Only = is used in the query, < > etc. should be included

yes