Retrieving data

DEIMS-SDR offers multiple ways of programmatically extracting information that always reflects the latest version of information in the DEIMS-SDR database.

REST-API

DEIMS-SDR has a REST-API (https://deims.org/api) following the Open API 3.0 specification. It allows to get lists (as .json or .csv) of ressources as well as detailed information about every record. For perfomance reasons, all jsons returned by the API are NOT pretty printed. There the usage of a browser plugin for formatting the results is recommended.

by adding ?format=csv each list can also be returned as .csv, e.g. https://deims.org/api/sites?format=csv

The site list currently allows very basic filtering by network ids and whether or not sites are verified members.

As an example, the following request returns all verified LTER Japan sites: https://deims.org/api/sites?network=6a7c82f8-f472-40ad-ae28-3035e239f3b6&verified=true

These lists always include the title, the unique ID used in DEIMS-SDR, coordinates and change date of a site. The ID can be used to get the detailed record of a resource.

The following requests are examples for each record type:

These records contain all available information and are only available as .json.

While the current release of the REST-API is stable und ready for production use, we plan on releasing new version in the coming months that will add additional filter functionality and improve overall perfomance.

WMS/WFS

DEIMS-SDR provide WMS/WFS services for site records. These services can be used to include site information in web maps or in desktop GIS applications.

The services also allow to download the information featured in the various layers in a variety of formats, e.g. Shapefile, GeoPackage, GeoJSON, CSV, ...

For a complete and up to date list of layers, please refer to the GetCapabilities links.

CSW/OAI-PMH

DEIMS-SDR provides site, dataset and activity records as ISO19139 served by OGC-CSW and OAI-PMH. Please be aware that ISO 19139 records only provide a limited subset of information compared to the full records served by the REST-API.

For further information on how to implement these services, please consult official documentation for each service.