MNCR Area Summaries - Inlets in eastern England - Part 1

Open data API in a single place

Provided by Joint Nature Conservation Committee

Get early access to MNCR Area Summaries - Inlets in eastern England - Part 1 API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
GB000282, Seabed Habitats and Geology, B230, Corpulent, Show on webGIS, Diver survey, MNCR, Intertidal survey, Translated to EUNIS, Data Provider Agreement not required - owned by JN, Nature Conservation, Marine
Quality scoring

Dataset description

A series of twelve marine inlets on the East Anglian and north Kent coasts (MNCR sector 6) have been studied as part of the Marine Nature Conservation Review programme. Comparable data from other organisations have been added to provide information on over 460 sites within the twelve inlets and analysed to classify the biotopes present. This data has been split into two parts. This is Part 1. Part 2 is available at: https://data.gov.uk/dataset/f476cb85-62ad-480c-a4f7-1b080b681123/mncr-area-summaries-inlets-in-eastern-england-part-2. Additional information source: Hill, T.O., Emblow, C.S., & Northern, K.O. (1996) Marine Nature Conservation Review Sector 6. Inlets in eastern England: area summaries. Peterborough, Joint Nature Conservation Committee. (Coasts and seas of the United Kingdom. MNCR series)
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