GEMS HABITAT POLYGON DATASET

Open data API in a single place

Provided by Scottish Government SpatialData.gov.scot

Get early access to GEMS HABITAT POLYGON DATASET API!

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

Dataset information

Catalog

Scottish Government SpatialData.gov.scot catalog

Country of origin

United Kingdom

Updated

Created

Available languages

English

Keywords

MPA, Marine Protected Areas, Priority Marine Features, Geodatabase of Marine Features adjacent to Scotlan, Marine habitats, Species distribution, GeMS, Habitats and biotopes, MPA Search Features, Habitats

Datasource

Official portal for European data link

Quality scoring

Dataset description

Collation of habitat polygon records contributing to the Geodatabase of Marine features adjacent to Scotland (GeMS). Records are attributed as to their qualification as protected features of protected areas within the Scottish MPA network. Where appropriate typical record details will include: status as Scottish Priority Marine Features or Annex I Habitat, MNCR biotope, EUNIS habitat, date, date range, year, status, accuracy, determiner and details of where the records are sourced from and intellectual property ownership. Polygon area values in the HECTARES field are calculated using ETRS89-LAEA (EPSG:3035) using the standard centre of projection at 10° E, 52° N.

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