Next version of the ICD.
Here are some addings and improvements already identified :
| Title | Description | Ref 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 Catalogue | Function to be specified (analyze Geoparquet format) | 2.2 |
| On demand Processing | Function to be specified | 2.2 |
Conformance tests
Postman conformance tests has been delivered here : https://gitlab.com/eof-conformance-test-suite/prip-cts/-/tree/main/stac-prip-validation-postman
Here is a list of ideas for improvements in a future version
| 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) | |
| STAC-PRIP-ITEM-REQ-0050 – STAC Items common properties | report which of the properties are missing | |
| STAC-PRIP-ITEM-REQ-0070 – Expected STAC Assets : Band(s) asset | implement for each mission | 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 | |
| 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 |
Add Comment