Water Body RNAGS Tees

Open data API in a single place

Provided by Environment Agency

Get early access to Water Body RNAGS Tees API!

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

Dataset information

Catalog

Environment Agency catalog

Country of origin

United Kingdom

Updated

Created

Available languages

English

Keywords

Datasource

Official portal for European data link

Quality scoring

Dataset description

Water body reasons for not achieving good status (RNAGS) identify the pressures that are impacting the status classification of water bodies. Reasons for deterioration (RFDs) identify the pressures that have caused the status of individual quality elements to deteriorate. This dataset includes the latest RNAGS and RFDs of all water bodies in the Tees catchment. A level of certainty (suspected, probable or confirmed) is also assigned to each reason for not achieving good status. This data supports the Water Framework Directive river basin management plans that can be found here: https://www.gov.uk/government/collections/river-basin-management-plans-2015 and is available to view interactively here: http://environment.data.gov.uk/catchment-planning/ManagementCatchment/3093 Attribution statement: © Environment Agency copyright and/or database right 2016. All rights reserved.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

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.store Built by Apitalks

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

About api.storePrivacy Terms of Service