Average number of garbage parts in 2017

Open data API in a single place

Provided by Landesamt für Umwelt des Landes Schleswig-Holstein (LfU)

Get early access to Average number of garbage parts in 2017 API!

Let us know and we will figure it out for you.

Dataset information

Catalog
Landesamt für Umwelt des Landes Schleswig-Holstein (LfU) catalog
Country of origin
Germany
Updated
2026.02.24 23:00
Created
2019.02.14
Available languages
English
Keywords
ostsee, llur, meeresstrategie-rahmenrichtlinie, envi, müll, monitoring, schleswig-holstein, ozeanografisch-geografische-kennwerte, inspire, msrlrelevant, mdi-de, mdi-sh, d10, strandmüllmonitoring, eu-richtlinie, msrl, gdi-sh, küstengewässer, umweltüberwachung
Datasource
Official portal for European data link
Quality scoring

Dataset description

Data from beach litter monitoring on the Schleswig-Holstein Baltic Sea coast. Monitoring along the coast of Fehmarn was organised by NABU and carried out with the help of volunteers. The shown number of garbage parts is the average of the collected garbage parts on 100m transects in the mentioned period. Up to 4 surveys are carried out per monitoring year, with the monitoring year covering the surveys from the beginning of December of the previous year to the end of November of that year. The collection of beach litter is carried out according to the OSPAR Beach Litter Guideline (2010).
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.storeBuilt by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacyTerms of Service
Copyright © 2026. Made by Apitalks