...
| Requirement | Improvement | Test to add |
|---|---|---|
| STAC-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 properties | report which of the properties are missing --> log the property which is not set | |
| STAC-PRIP-ITEM-REQ-0070 – Expected STAC Assets : Band(s) asset | implement for each mission : Sentinel-2 (L1C, L2A) + Sentinel-3 (OLCI + RBT) | yes |
| STAC-PRIP-ITEM-REQ-0087 – Exposed assets related to sub elements of the EOPF product | to test | yes |
| STAC-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 | |
| STAC-PRIP-API-REQ-0205 – STAC API Extensions | Should list which extensions are missing | |
| STAC-PRIP-API-REQ-0200 – STAC API requirements | implemented by STAC API Validator project --> to update | |
| STAC-PRIP-API-REQ-0203 – STAC API limit parameter | to test | yes |
| Geometry 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 |
...