EU Protected Site Habitat Inventory Records — EEA BISE
Pricing
from $33.50 / 1,000 protected-site habitat records
EU Protected Site Habitat Inventory Records — EEA BISE
Per-record inventory of which protected habitats occur at each EU protected site, with coverage in hectares (Natura 2000 / Emerald Standard Data Form) from EEA BISE. Keyless, pay per record, no person data.
Pricing
from $33.50 / 1,000 protected-site habitat records
Rating
0.0
(0)
Developer
NexGen Signal
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Keyless. Pay per record. Which protected habitats occur at each of Europe's protected sites, and their coverage — from the Standard Data Form.
This actor turns the European Environment Agency (EEA) Biodiversity Information System for Europe (BISE) site-habitats inventory into clean, per-record data — which protected habitats occur at each of Europe's official protected sites, and how much of each site they cover. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per site-habitat listing, structured for conservation and site-assessment analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.
What this is, in one paragraph
Europe's Natura 2000 and Emerald protected sites each publish a Standard Data Form listing the habitat types of Union interest that occur there and how much of the site they cover. The EEA's Biodiversity Information System for Europe (BISE) compiles those listings into a site-habitats inventory. This actor reads that table and delivers one record per site / habitat: the protected site code, the Natura 2000 habitat code (code_2000), the habitat group and description, the COVERAGE in hectares, the cave extent, and the priority-habitat flags — all carried as filed. It is the habitat side of the protected-site inventory, the companion to the species inventory.
Who buys this and for what job
- Conservation analysts mapping which protected habitats occur at which sites and their extent
- Site-assessment and impact-review teams checking the habitats listed for a protected site
- Researchers studying habitat distribution and coverage across Europe's protected-site network
- Data engineers who want the BISE site-habitats table as clean rows from a keyless source.
EEA licence — reuse with acknowledgement
One licence rider travels on every record. EEA data may be reused, including commercially, provided the source is acknowledged: "Source: European Environment Agency (EEA)." Where third-party content is marked, it keeps its own terms. These are reported values and labels as filed — not a compliance verdict.
Site / habitat grain — no person data
The unit of every record is a habitat listed at a protected site — a habitat type at a place, never a person. The site is a location code and the habitats are ecosystem types; there is no contact, operator, or responsible-person field in the source, and none is emitted; the free-text remark and metadata narrative fields are excluded at field selection. A person-key guard runs on every record as a backstop.
Sample output

Real rows from a live run of this actor (first 5 rows, selected columns).
One full record from the same run, exactly as delivered:
{"record_id": "AT1101112:6240","site_code": "AT1101112","habitat_code_2000": "6240","habitat_group": "Grasslands","habitat_description": "Sub-Pannonic steppic grasslands","coverage_ha": 9.1,"caves": 0,"priority_form_habitat_type": "0","priority": "1","source": "EEA Biodiversity Information System for Europe (BISE) — protected-site habitat inventory","source_url": "https://discodata.eea.europa.eu/","licence": "European Environment Agency (EEA) Biodiversity Information System for Europe (BISE) — protected-site habitat inventories. Reuse is permitted, including for commercial purposes, provided the source is acknowledged: 'Source: European Environment Agency (EEA)'. Third-party content, where marked, keeps its own terms.","attribution": "Source: European Environment Agency (EEA), Biodiversity Information System for Europe (BISE).","disclaimer": "Which protected habitats occur at each official protected site, and their coverage, at site / habitat grain from the EEA Biodiversity Information System for Europe (BISE) site-habitats inventory (the public Standard Data Form content). Each record names the protected site, the Natura 2000 habitat code (code_2000), the habitat group and description, the COVERAGE in hectares, the cave extent, and the priority-habitat flags — carried as filed. Site / habitat grain — there is no contact, operator, or responsible-person field in the source, and none is emitted; a person-key guard runs on every record as a backstop.","observed_at": "2026-09-25T17:33:34Z"}
Pricing
| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|---|---|---|---|---|
site_habitat_record | $0.05 | $0.045 | $0.04 | $0.0335 |
Delivered before charged. Blocked runs and empty results cost nothing.
Input
| Field | Type | Default | Description |
|---|---|---|---|
countryCode | string | — | Optional 2-letter country code (e.g. DE, FR) — matched against the site-code prefix. |
maxRecords | integer | 500 | Ceiling on records delivered and billed. |
Output
One JSON object per site-habitat listing. Real example (values as reported):
{"record_id": "AT1201000:3220","site_code": "AT1201000","habitat_code_2000": "3220","habitat_group": "Freshwater habitats","habitat_description": "Alpine rivers and their ligneous vegetation","coverage_ha": 12.5,"caves": 0,"priority_form_habitat_type": "No","priority": "No","source": "EEA Biodiversity Information System for Europe (BISE) \u2014 protected-site habitat inventory","source_url": "https://discodata.eea.europa.eu/","observed_at": "2026-08-23T00:00:00Z"}
An unbilled RUN_RECEIPT records the robots check, the filters, rows seen and delivered, and whether charged equals delivered.
Field reference
Each record is one site-habitat listing. Identity: record_id (site code : habitat code) and site_code. Habitat: habitat_code_2000, habitat_group, and habitat_description. Extent: coverage_ha and caves. Priority flags: priority_form_habitat_type and priority. Provenance travels on every record: source, source_url, licence, attribution, disclaimer, and observed_at.
How a run works
A run first re-reads the source host's robots posture from your runtime — the EEA DiscoData host — and stops at the door if that ever changes. It pages the BISE site-habitats table (filtered to your optional countryCode), and flattens each row to one record — carrying every value and label verbatim, never anything person-shaped — delivered before it is charged, so a blocked or empty run costs you nothing. The actor stops at your maxRecords ceiling and records charge_equals_delivered in the receipt.
Coverage and scope
The table holds on the order of 140,404 rows. Because each record carries the site_code (whose prefix is the country), the habitat code, and the coverage, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.
Working with the data
The inventory is a habitat map with extent, and the fields make it quantifiable. Because every record pairs a site_code with a habitat_code_2000 and a coverage_ha, an analyst can total how much of a site each habitat covers, or how much of a given habitat type a country's protected network holds, and the priority and priority_form_habitat_type flags mark the priority habitats that carry stricter obligations. The habitat_group rolls the detailed codes up to families.
Identifiers and joins
Every record carries the site_code, keying each habitat listing to the site register (eu-natura2000-site-records) for the same site and to the companion species-inventory cell for the same site — so a buyer can assemble the full Standard Data Form picture (the site, its habitats, and its species) on one shared identifier. The habitat_code_2000 keys habitats to the Natura 2000 habitat-code reference.
Habitats versus species and the site register
The Standard Data Form has three layers: the site itself, the habitats it protects, and the species it hosts. The site register carries the first; this cell carries the second; the companion species cell carries the third. Keeping the habitat inventory separate means a buyer studying habitat extent pulls the habitat rows directly, at habitat grain with coverage, without carrying the site record or the species rows on every line — and joins back on the site_code when the other layers are needed.
Cost guidance
One site_habitat_record per delivered row: cost = rows delivered × your plan's per-record price. Scope with countryCode to keep runs bounded. 1,000 rows is $50 (Free) / $33.50 (Gold).
Honest limitations
- As reported. Values, labels, and flags are as filed; this actor reformats, it does not audit or recompute.
- A label, not a verdict. These are reported values and classifications, not an independent compliance or conservation assessment.
- Acknowledge the EEA. The acknowledgement travels on every record.
- No person data of any kind.
Differentiation
It is distinct from eu-natura2000-site-records (the site REGISTER — one row per site) and from the companion eu-protected-site-species-inventory-records (which lists SPECIES per site) — this cell lists the HABITATS per site, with their coverage; habitat inventory vs site register vs species inventory. Its specific job is the BISE protected-site habitat inventory.
The NexGen Signal family
Part of the NexGen Signal family of pay-per-record data products:
- EU Protected Site Habitat Inventory Records — EEA BISE
- EU Protected Site Species Inventory Records — EEA BISE
- EU Natura 2000 Site Records — EEA
- EU Water Abstraction Records — EEA WISE
- EU Reservoir Storage Records — EEA WISE
Source: European Environment Agency (EEA), Biodiversity Information System for Europe (BISE) (discodata.eea.europa.eu). EEA data may be reused, including commercially, provided the source is acknowledged: "Source: European Environment Agency (EEA)"; marked third-party content keeps its own terms. Site / habitat grain; the site is a location code and habitats are ecosystem types; free-text remark/metadata fields excluded, no contact/operator/responsible-person field selected or emitted. No natural-person data of any kind. Values and labels as filed, not a compliance verdict.