River Agriculture Pressures

Open data API in a single place

Provided by Environmental Protection Agency

Get early access to River Agriculture Pressures API!

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

Dataset information

Country of origin
Updated
2026.04.07 15:06
Created
2017.11.20
Available languages
English
Keywords
impact, environment, ie, environmental risk, hydrography, pollution, phosphate, wfd, pollutant pathway, surface water, water framework directive, critical source area, critical load, pasture, environmental impact, pressure, risk, agriculture, farmyard, characterisation, nitrate, environmental pressures, point source, point, nutrient, diffuse, pathway, pollution impact potential (pip), arable farming, catchment, sediment, source, subcatchment, environmental policy, receptor, river, environmental impact of agriculture
Quality scoring

Dataset description

Significant pressures have been identified for waterbodies that are At Risk of not meeting their water quality objectives under the Water Framework Directive. While there are a multitude of pressures in every waterbody, the significant pressures are those pressures which need to be addressed in order to improve water quality. Many of our waterbodies have multiple significant pressures. A robust scientific assessment process has been carried out to determine which pressures are the significant pressures. This has incorporated over 140 datasets, a suite of modelling tools, and local knowledge from field and enforcement staff from the Local Authorities, Inland Fisheries Ireland and EPA. Impacts from agriculture include nutrient and organic pollution. A significant agricultural pressure can be diffuse and/or point source of pollution. Agricultural pressures are subcategorised into pasture, arable, farmyard and agriculture.
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.

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

Copyright © 2026. Made by Apitalks