CEOS OpenSearch conformance testing WGISS-43 Doug Newman (NASA Earthdata – Raytheon) The material is based upon work supported by the National Aeronautics and Space Administration under Contract Number NNG15HZ39C
Agenda Using the web application Using the web service
Concept Supply an OSDD location Validation tool performs a series of tests to measure compliance of OpenSearch API Split by specifications, extensions and best practices Success – what you gain Failure – what you lose More than just your OSDD. Searches are performed to test two-step etc.
What we can validate OpenSearch Specification Version 1.1 Draft 5 Geo extension Version 1.0 Draft 2 Time extension Version 1.0 Draft 1 ESIP Best Practices Version 1.0 Parameter extension Version 1.0 Draft 1 Relevancy extension Version 1.0 Draft 1 OGC Extensions Version 13-026r6 CEOS Best Practices Version 1.1.1 CEOS Developer Guide 2.0D3
What to be careful of ‘More than just your OSDD. Searches are performed to test two-step etc.’ How do we do that? We use the example query in your OSDD So chose your example query wisely and as exhaustively as possible. Example browse.
Web application
https://api.echo.nasa.gov/cwic-smart/validations Via CWICSmart https://api.echo.nasa.gov/cwic-smart/validations
Via CWICSmart
Web service
Via CWICSmart https://api.echo.nasa.gov/cwic-smart/api-docs for swagger documentation (in XML and JSON format)
Coming soon…
Open sourcing Run tests against developing, non-public APIs Extend validations to new standards etc
Thank you very much Questions?
This material is based upon work supported by the National Aeronautics and Space Administration under Contract Number NNG15HZ39C.