The current estimate is that more than 80% of the web content is not indexed by search engines. This includes content that is intentionally hidden such as private repositories, but also some organisation specific repositories, academic databases and government reports.
Do you create geospatial data, vocabularies, styles, processes, services or ML models? Do you manage repositories of metadata to describe your resources? Rhe OGC API - Records Standard specifies standard interfaces to expose your resources and metadata, making them discoverable using a Standard vocabulary.
Implementations of the OGC API - Records Standard can ensure that search engines can index geospatial resources in a structured way, so that both humans and machines can find, assess/evaluate and access them.
The OGC API - Records Standard was developed and is maintained by the Open Geospatial Consortium (OGC), , an international Standards Development Organization (SDO). The OGC also offers compliance and certification testing, ensuring maximum interoperability. In addition, the Standard is harmonized with the STAC family of specifications, in order to make sure that STAC catalogs can understand OGC API - Records catalogs and vice versa.
The OGC API - Records Standard defines requirements for key deployment patterns that address different use cases. For instance, a public directory with satellite imagery can benefit from having a crawlable catalog (also called static catalog), which can be created with static files without the need to install any API, middleware or databases.
The OGC API - Records Standard is based on Web technologies and vocabularies, such as REST, OpenAPI, JSON and HTML. These mass market technologies and patterns provide a low barrier experience for any Web developer (where geospatial/GIS expertise is not required).
An implementation of the OGC API - Records Standard provides discovery and access to metadata about geospatial resources. Once a metadata record is found, its API response provides key information to help a user evaluate the resource as well as mechanisms for further interaction (data access, process execution, etc.).
The Standard offers three main reusable API components: a record , a collection of records and a records API .
These three components combined together enable developers to implement a catalog.
Servers | ||||
---|---|---|---|---|
Cubewerx | / | |||
Java | GeoNetwork | / | ||
Esri Geoportal Server Catalog | / | |||
Python | pycsw | / | ||
pygeoapi | / | |||
Clients | ||||
---|---|---|---|---|
Python | OWSLib | / , | ||
JavaScript/Vue.js | STAC Browser | / , | ||
MDME | / , | |||
C/C++ | QGIS | / |
Encoders/Decoders | ||||
---|---|---|---|---|
Python | pygeometa | / , |