Try out the EMODnet OGC web services in our R tutorial. View the tutorial here or run it interactively with Binder:
This document has links to all EMODnet web services that allow you to search, visualise and download EMODnet data and data products.
The EMODnet central catalogue offers the ability to search collections of metadata for data, services and related information objects related to the different EMODnet thematics. The data catalogues offer a CSW endpoint to other client applications to connect to the service and query the available metadata records.
| Thematic | CSW GetCapabilities |
|---|---|
| Central Catalogue | https://emodnet.ec.europa.eu/geonetwork/emodnet/eng/csw?service=CSW&request=GetCapabilities&VERSION=2.0.2 |
The mandatory GetCapabilities operation allows CSW clients to retrieve service metadata from a server. The response to a GetCapabilities request shall be an XML document containing service metadata about the server. This subclause specifies the XML document that a CSW server shall return to describe its capabilities.
GetRecords requests allows to query and filter the catalogue metadata records.
GetRecords example:
GetRecordById requests retrieves catalogue metadata records using their identifier.
GetRecordById example
The Web Map Service standard (WMS) provides a simple HTTP interface for requesting geo-registered map images from one or more distributed geospatial databases. A WMS request defines the geographic layer(s) and area of interest to be processed. The response to the request is one or more geo-registered map images (returned as JPEG, PNG, etc) that can be displayed in a Geographic Information System (GIS) or in your own web application (OpenLayers, Leaflet,...).
The WMS supports the GetCapabilities, GetMap and GetFeatureInfo operations as defined in the Open Geospatial Consortium (OGC) WMS standard.
The EMODnet WMS services are accessible from 7 thematics at the Pan-European scale or global scale for some specific data products. Enter one of the following WMS endpoint URLs into your WMS client (QGIS, ArcMap, MapInfo etc.):
The mandatory GetCapabilities operation allows WMS clients to retrieve service metadata from a server. The response to a GetCapabilities request shall be an XML document containing metadata of the service (proposed layers, associated projections, author ...).
The standard to construct a WMS GetCapabilities request, depending on the version:
{wms endpoint url}?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetCapabilities
or
{wms endpoint url}?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetCapabilities
Using the information given in the GetCapabilities request, the GetMap request returns a raster map containing the requested data layer selected from all the available layers as defined in the XML document. The elements such as the data layer, region, projection, size of the returned image, image format, etc. are defined in the form of arguments.
Example of a GetMap request that returns an image of the EMODnet Bathymetry Mean depth (DTM) based on source resolution of 1/8 arc minute (~250 meter) in multi colour style:
Returns:
In contrast to a WMS service, which offers real time rendered georeferenced images for a custom geographic extent, a Web Map Tile Service (WMTS) serves pre-rendered georeferenced map tiles with a fixed geographic extent for different zoom levels. As images are pre-rendered and can be cached (locally or remotely), WMTS offers a superior performance for web map viewer applications.
The EMODnet WMTS service are accessible from following endpoints:
The EMODnet data layers are available as a Web Feature Service (WFS) or Web Coverage Service (WCS) in accordance with the Open Geospatial Consortium (OGC) specifications (www.opengeospatial.org).
Note that some thematics provide other, non-OGC, web services too. For example a central EMODnet ERDDAP server, a REST service to the EMODnet Bathymetry DTM, EMODnet Biology allows specific parameters in the WFS requests, EMODnet Chemistry has an OPeNDAP service. See section Non-OGC web services
WFS defines a standard for exchanging vector data by querying both the data structure and the source data. The basic operations are GetCapabilities, DescribeFeatureType, and GetFeature. WFS supports a variety of WFS output formats (Ex: GML, shapefile, json, geojson, CSV,...). The full list of output formats supported can be found by performing a WFS GetCapabilities request.
The EMODnet WFS services are accessible from following endpoints:
A GetCapabilities request generates a metadata document (xml) describing a WFS service provided by server as well as valid WFS operations and parameters.
A DescribeFeature request returns a description of feature types supported by a WFS service.
Example of a EMODnet Biology DescribeFeature request:
Example of a EMODnet Human Activities DescribeFeature request:
A GetFeature request returns a selection of features from a data source including geometry and attribute values.
Example of a EMODnet Human Activities GetFeature request:
EMODnetWFS is an R package developed to access WFS data from EMODnet. You can install with:
remotes::install_github("EMODnet/EMODnetWFS")The EMODnet thematics provide Web Coverage Services (WCS) to support requests for coverage data (rasters) or gridded data products. Enter one of the following addresses into your WCS client:
| Thematic | Description | WCS GetCapabilities |
|---|---|---|
| Bathymetry | Data Products | https://ows.emodnet-bathymetry.eu/wcs?SERVICE=WCS&REQUEST=GetCapabilities&VERSION=2.0.1 |
| Biology | Data Products | https://geo.vliz.be/geoserver/Emodnetbio/wcs?SERVICE=WCS&REQUEST=GetCapabilities&VERSION=2.0.1 |
| Biology | New Data Products | https://ows.emodnet.eu/geoserver/biology/ows?SERVICE=WCS&REQUEST=GetCapabilities&VERSION=2.0.1 |
| Human Activities | Data and Data Products | https://ows.emodnet-humanactivities.eu/wcs?SERVICE=WCS&REQUEST=GetCapabilities&VERSION=2.0.1 |
| Seabed Habitats | Individual habitat map and model datasets | https://ows.emodnet-seabedhabitats.eu/geoserver/emodnet_open_maplibrary/wcs?SERVICE=WCS&REQUEST=GetCapabilities&VERSION=2.0.1 |
A WCS GetCapabilities request retrieves a list of the server's data, as well as valid WCS operations and parameters.
A WCS DescribeCoverage request retrieves a metadata (XML) document that fully describes the requested coverages.
Example of an EMODnet Bathymetry DescribeCoverage request:
A WCS GetCoverage request returns a coverage in a well known format. Like a WMS GetMap request, but with several extensions to support the retrieval of coverages.
Example of an EMODnet Bathymetry GetCoverage request:
| Thematic | web service | URL |
|---|---|---|
| EMDOnet | ERDDAP | https://erddap.emodnet.eu/erddap/index.html |
| Bathymetry | REST API | https://rest.emodnet-bathymetry.eu/ |
| Chemistry | THREDDS | http://opendap.oceanbrowser.net/thredds/catalog/data/emodnet-domains/catalog.html XML version: http://opendap.oceanbrowser.net/thredds/catalog/data/emodnet-domains/catalog.xml |
| Physics | ERDDAP | https://prod-erddap.emodnet-physics.eu/erddap/index.html |
- Biology Github: https://github.com/EMODnet/EMODnet-Biology-Guidance
- Chemistry GitHub: https://github.com/gher-ulg/EMODnet-Chemistry
- Physics GitHub: https://github.com/EMODnet-Physics
- Seabed habitats GitHub: https://github.com/emodnetseabedhabitats
- Other repos in the main EMODnet GitHub: https://github.com/EMODnet
Having trouble? Verify the status of the EMODnet OGC services at https://monitor.emodnet.eu.
Provided by EMODnet. See our terms of use
