# EU Protected Site Habitat Inventory Records — EEA BISE (`nexgensignal/eu-protected-site-habitat-inventory-records`) Actor

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.

- **URL**: https://apify.com/nexgensignal/eu-protected-site-habitat-inventory-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 protected-site habitat records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## EU Protected Site Habitat Inventory Records — EEA BISE

**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

![Sample output — EU Protected Site Habitat Inventory Records — EEA BISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-protected-site-habitat-inventory-records.png)

*Real rows from a live run of this actor (first 5 rows, selected columns).*

One full record from the same run, exactly as delivered:

```json
{
  "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):

```json
{
  "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](https://apify.com/nexgensignal/eu-protected-site-habitat-inventory-records)
- [EU Protected Site Species Inventory Records — EEA BISE](https://apify.com/nexgensignal/eu-protected-site-species-inventory-records)
- [EU Natura 2000 Site Records — EEA](https://apify.com/nexgensignal/eu-natura2000-site-records)
- [EU Water Abstraction Records — EEA WISE](https://apify.com/nexgensignal/eu-water-abstraction-records)
- [EU Reservoir Storage Records — EEA WISE](https://apify.com/nexgensignal/eu-reservoir-storage-records)

*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.*

# Actor input Schema

## `countryCode` (type: `string`):

Optional 2-letter country code (e.g. DE, FR) — matched against the site-code prefix.

## `maxRecords` (type: `integer`):

Maximum records delivered and billed.

## Actor input object example

```json
{
  "maxRecords": 10
}
```

# Actor output Schema

## `results` (type: `string`):

Delivered records.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxRecords": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-protected-site-habitat-inventory-records").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "maxRecords": 10 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-protected-site-habitat-inventory-records").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxRecords": 10
}' |
apify call nexgensignal/eu-protected-site-habitat-inventory-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-protected-site-habitat-inventory-records"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/W8D5MlqGgIfqWQfVF/builds/nnshkVUHDVUsbqyj5/openapi.json