...
| 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
...
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
...
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)
...
implemented by STAC API Validator project --> to update
...
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
...
Only = is used in the query, < > etc. should be included
...
yes