Currently, we have a place holder for OpenSearch support in the API for data (and process) discovery. It bases on OpenSearch 1.0 and doesn't really fit into our API as it is XML based and not JSON as everything else.
It seems that OGC is working on a new JSON based draft as I could read here:
in the OGC EO-PMOS Standards Working Group we´re currently standardizing a new version of the OpenSearch EO-Extension (13-026r9 -> aligned with OWC Context, CEOS,...). Accompanied by a GeoJSON(-LD) response encoding (OGC 17-047), GeoJSON(-LD) based Metadata Profile for EO-products (granules) (OGC 17-003) and a GeoJSON(-LD) based Metadata Profile for EO-collections (just in draft status). We hope to have final version by 1/2018.
That sounds pretty interesting. They are overdue(?), but maybe we can just wait for the release and incorporate this version in favor of the XML-based version.
Can't really find further information, but there is a presentation from a CEOS meeting regarding the EO OpenSearch GeoJSON Encoding. There are some interesting information included, which we should look at, e.g. regarding on how to format the acquisition information that were proposed also in #64 for the general data discovery endpoint.
Currently, we have a place holder for OpenSearch support in the API for data (and process) discovery. It bases on OpenSearch 1.0 and doesn't really fit into our API as it is XML based and not JSON as everything else.
It seems that OGC is working on a new JSON based draft as I could read here:
That sounds pretty interesting. They are overdue(?), but maybe we can just wait for the release and incorporate this version in favor of the XML-based version.
Can't really find further information, but there is a presentation from a CEOS meeting regarding the EO OpenSearch GeoJSON Encoding. There are some interesting information included, which we should look at, e.g. regarding on how to format the acquisition information that were proposed also in #64 for the general data discovery endpoint.