Skip to content

Latest commit

 

History

History
214 lines (129 loc) · 9.01 KB

implementations.md

File metadata and controls

214 lines (129 loc) · 9.01 KB

Implementations

Overview

This page points to servers implementing drafts of the OGC API - Records series.

Implementations:

Servers:

Clients:

Parsers/Encoders:

CubeWerx Inc.

The following server implements a good portion of the current draft OpenAPI document for OGC API - Records. This is a very rough implementation and still needs quite a bit of work but feel free to play with it.

I have currently harvested a bunch of RADARSAT metadata and will shortly have harvested all the SENTINEL-1 metadata that is available on AWS.

Landing page:

API document:

Conformance Page:

List of catalogs:

Description of the catalog:

Records:

pygeoapi

The pygeoapi project implements most of the current OGC API - Records draft.

A sample instance is deployed using sample metadata records from the Dutch Nationaal georegister.

Landing page:

API document:

Conformance page:

List of catalogues:

Describe sample metadata records from Dutch Nationaal georegister

Queryables:

Records:

Single record:

Esri Inc

ArcGIS Pro CSW Client as OGC API - Records consumer

The ArcGIS Pro CSW Client has been updated to include initial support for OGC API - Records. Details may be found on the Geoportal Server wiki, the Visual Studio project to build the Pro addin is available in the Components section of the Geoportal Server github repo.

Geoportal Server OGC API - Records provider

Esri Geoportal Server 2.7.1 public sandbox implementation of the OGC Records API.

Landing page:

API document:

Conformance page:

List of catalogues:

Describe geoportal2 catalogue:

Queryables:

Records:

OpenAPI page:

GeoNetwork opensource

GeoNetwork is a java/xml oriented catalogue application. As part of an ongoing effort, the GeoNetwork API component is extended to support OGC API - Records. The work in progress is available at geonetwork/geonetwork-microservices#23.

GeoNetwork has a concept of sub-portals. In the OGC API - Records implementation these subportals are available as collections of records. GeoNetwork uses an Elastic Search backend, supporting a configurable set of queryables. Records are available in various encodings, such as text/html, application/geo+json, application/dcat.ld+json, application/iso19139+xml, application/iso19115-3+xml, application/dublin-core+xml, application/datacite+xml, through the accept-header mechanism. The html encoding of records contains an embedded schema-org json-ld snippet to facilitate search engines. A Sitemap endpoint is available to notify the search engine of available records.

GeoNetwork supports basic authentication, but can also be set up with alternative authentication mechanisms to facilitate autorisation on subsets of records.

pycsw

pycsw is an OGC CSW server implementation written in Python. Implementation of OGC API - Records is a work in progress for pycsw.

Landing page:

Conformance page:

List of catalogues:

Describe sample metadata records from CSW CITE tests

Queryables:

Records:

Single record:

QGIS

QGIS is a free and open-source cross-platform desktop geographic information system application that supports viewing, editing, and analysis of geospatial data. The QGIS MetaSearch core plugin supports OGC API - Records as a search client.

OWSLib

OWSLib is an OGC Web Services client written in Python which also implements the evolving OGC API standards. See the documentation for example workflow.

pygeometa

pygeometa is a Python package to generate metadata for geospatial datasets. Supports OGC API - Records record metadata generation.

stac-browser

stac-browser is a web client developed for Spatio-Temporal Asset Catalog (STAC) static catalogs. It is compatible with OGC API - Records crawlable catalogs. A live version is available here

mdme

Model Driven Metadata Editor (MDME) is a metadata editor driven by arbitrary json schema models based on vjsf. You can configure it with the OGC API - Records schema to use it to author metadata in the OGC API - Records model. MDME also offers capabilities to transform between models using metadata transformation services provided by pygeoapi.io