1992 - 2017 Centre for Environment, Fisheries & Aquaculture Science (Cefas) Predictor variables and sedimentation rate samples used to predict sedimentation rates within the Baltic Sea from 1992 - 2017
Open data API in a single place
Provided by Government Digital Service
Get early access to 1992 - 2017 Centre for Environment, Fisheries & Aquaculture Science (Cefas) Predictor variables and sedimentation rate samples used to predict sedimentation rates within the Baltic Sea from 1992 - 2017 API!
Input data used to predict sedimentation rate for the Baltic Sea. Observation
data includes: Sedimentation rate data derived from isotope 137Cs tracers and
pseudo-samples of zero sedimentation rate randomly placed in areas of rocky
habitat. Sixteen predictor variables were considered for use in the
sedimentation rate model. These were: Bathymetric Position Index (at three
neighbourhood sizes); the Standard Deviation of bathymetry (at three
neighbourhood sizes); Distance from Rivers (three layers representing
different river catchment sizes); Substrate class (developed at a 1:1,000,000
scale for the Baltic Sea, classified to Folk5 level); satellite derived
estimate for Suspended Particulate Matter in the water column (a winter and
summer layer); Orbital Velocity at the seabed (a winter and summer layer); and
Current Speed (a winter and summer layer).
To access and download the data contact `[email protected]`_
For additional details regarding the predictor data variables see the
publication associated with this data:
`https://doi.org/10.1016/j.csr.2020.104325`_
.. _`[email protected]`:
mailto:[email protected]%20
.. _`https://doi.org/10.1016/j.csr.2020.104325`:
https://doi.org/10.1016/j.csr.2020.104325
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.