# EU Habitat Conservation Measure Records — EEA BISE (`nexgensignal/eu-habitat-conservation-measure-records`) Actor

Per-record EU habitat conservation measures mapped to protected habitat types (Habitats Directive Art 17) from EEA BISE. Keyless, pay per record, verbatim, no person data.

- **URL**: https://apify.com/nexgensignal/eu-habitat-conservation-measure-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, 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 habitat conservation measure 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 Habitat Conservation Measure Records — EEA BISE

**Keyless. Pay per record. The official conservation measures mapped to each protected habitat type — measure code, label, and quantity, verbatim.**

This actor turns the **European Environment Agency (EEA) Biodiversity Information System for Europe (BISE) habitat-conservation-measures dataset** into clean, per-record data — the official conservation interventions mapped to Europe's protected habitat types. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per habitat-measure listing, structured for conservation-planning and habitat-management analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Under the Habitats Directive, member states report the conservation measures taken for each habitat type of Union interest. The EEA's Biodiversity Information System for Europe (BISE) compiles those into a habitat-conservation-measures dataset. This actor reads that table and delivers one record per habitat / measure: the Natura 2000 habitat code (code\_2000), the measure CODE and its label carried verbatim (for example, preventing the conversion of natural and semi-natural habitats to agricultural land), and the reported quantity. It is the INTERVENTION layer of Europe's habitat conservation — what is being done for a habitat, distinct from where the habitat occurs or how it is faring.

### Who buys this and for what job

- **Conservation-planning analysts mapping which measures are applied to which habitats**
- **Habitat-management and policy teams tracking the intervention mix across habitat types**
- **Researchers studying conservation-measure patterns across Europe's protected habitats**
- **Data engineers** who want the BISE habitat-conservation-measure 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.

### Habitat / measure grain — no person data

The unit of every record is a conservation measure mapped to a habitat type — an intervention line, never a person. The habitat is a code and the measure is a codelist entry; there is no contact, operator, assessor, or responsible-person field in the source, and none is selected or emitted. A person-key guard runs on every record as a backstop.

### Sample output

![Sample output — EU Habitat Conservation Measure Records — EEA BISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-habitat-conservation-measure-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": "1110:CA01",
  "habitat_code_2000": "1110",
  "measure_code": "CA01",
  "measure_label": "Prevent conversion of natural and semi-natural habitats, and habitats of species into agricultural land",
  "quantity": 1,
  "source": "EEA Biodiversity Information System for Europe (BISE) — habitat conservation measures",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Biodiversity Information System for Europe (BISE) — habitat conservation measures. 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": "Official conservation interventions (measures) mapped to protected habitat types, at habitat / measure grain from the EEA Biodiversity Information System for Europe (BISE) habitat-conservation-measures dataset (Habitats Directive Article 17 reporting). Each record names the Natura 2000 habitat code (code_2000), the measure CODE and its label VERBATIM (e.g. preventing conversion of habitats to agricultural land), and the reported quantity. This is the INTERVENTION layer — the measures taken for a habitat — distinct from where the habitat OCCURS. Habitat / measure grain — there is no contact, operator, assessor, or responsible-person field in the source, and none is selected or emitted; a person-key guard runs on every record as a backstop.",
  "observed_at": "2026-09-25T17:20:45Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `habitat_measure_record` | $0.05 | $0.045 | $0.04 | $0.0335 |

Delivered before charged. Blocked runs and empty results cost nothing.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per habitat-measure listing. Real example (values as reported):

```json
{
  "record_id": "1110:CA01",
  "habitat_code_2000": "1110",
  "measure_code": "CA01",
  "measure_label": "Prevent conversion of natural and semi-natural habitats, and habitats of species into agricultural land",
  "quantity": 1,
  "source": "EEA Biodiversity Information System for Europe (BISE) \u2014 habitat conservation measures",
  "source_url": "https://discodata.eea.europa.eu/",
  "observed_at": "2026-08-25T00: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 habitat-measure listing. Identity: `record_id` (habitat code : measure code) and `habitat_code_2000`. Measure: `measure_code`, `measure_label` (verbatim), and `quantity`. 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 habitat-conservation-measure table (filtered to your `maxRecords` ceiling), 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 records `charge_equals_delivered` in the receipt.

### Coverage and scope

The table holds on the order of **4,776 rows**. Because each record carries the `habitat_code_2000` and the measure code, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

### Working with the data

The measures are an intervention ledger, and the fields make them countable. Because every record pairs a `habitat_code_2000` with a `measure_code` and `measure_label`, an analyst can list every measure applied to a habitat, or every habitat a given measure targets, and roll up the measure mix across a habitat group. The `quantity` field carries the reported count for each measure, so the intensity of intervention can be compared across habitats. Because the `measure_code` is a stable codelist entry, a whole catalogue of measures can be tabulated across every habitat that reports them, and the `measure_label` travels alongside so the analysis stays readable without a separate lookup. Pulling the whole table — under five thousand rows — is cheap enough to seed a warehouse table of the complete European habitat-measure matrix in a single run, then refresh it on a schedule as reporting cycles update.

### Identifiers and joins

Every record carries the `habitat_code_2000`, keying each measure to the companion habitat-conservation-STATUS cell (how the habitat is faring), to the protected-site habitat-inventory cell (where the habitat occurs), and to the Natura 2000 habitat-code reference — so the measures taken can be read directly against the habitat's condition and distribution.

### Measures versus status versus occurrence

Europe's habitat reporting has three distinct layers: WHERE a habitat occurs (the site inventories), HOW it is faring (the conservation-status assessments), and WHAT is being done for it (the conservation measures, this cell). Keeping them as separate actors means a buyer studying the intervention mix pulls the measure rows directly, at habitat/measure grain, and joins back on the habitat code to relate measures to status and occurrence — the full conservation picture, each layer priced and delivered on its own.

### Cost guidance

One `habitat_measure_record` per delivered row: cost = rows delivered × your plan's per-record price. 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 classifications and outcomes, not an independent compliance or conservation assessment.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

This is a **net-new** category for the NexGenData fleet. It is distinct from **eu-habitat-conservation-status-records** (how a habitat is faring) and from the protected-site inventory cells (where a habitat occurs) — this cell carries the MEASURES taken (the interventions); interventions vs condition vs occurrence. Its specific job is the **BISE habitat conservation measures**.

### The NexGen Signal family

Part of the NexGen Signal family of pay-per-record data products:

- [EU Habitat Conservation Status Records — EEA BISE](https://apify.com/nexgensignal/eu-habitat-conservation-status-records)
- [EU Protected Site Negative Impact Records — EEA BISE](https://apify.com/nexgensignal/eu-protected-site-negative-impact-records)
- [EU Species Legal Protection Records — EEA BISE](https://apify.com/nexgensignal/eu-species-legal-protection-records)
- [EU Protected Site Species Inventory Records — EEA BISE](https://apify.com/nexgensignal/eu-protected-site-species-inventory-records)
- [EU Protected Site Habitat Inventory Records — EEA BISE](https://apify.com/nexgensignal/eu-protected-site-habitat-inventory-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. Habitat / measure grain; habitat and measure are codelist entries; no contact/operator/assessor/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

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

Maximum records delivered and billed.

## Actor input object example

```json
{
  "maxRecords": 500
}
```

# 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": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-habitat-conservation-measure-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": 500 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-habitat-conservation-measure-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": 500
}' |
apify call nexgensignal/eu-habitat-conservation-measure-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-habitat-conservation-measure-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/MgtydTNihqV2hcEmt/builds/wdaPgX5PehR607Thv/openapi.json