# EU Natura 2000 Site Records — EEA Protected Sites (`nexgensignal/eu-natura2000-site-records`) Actor

Keyless, pay-per-record EEA/BISE protected-site data. One row per site — code, name, country, type, designation, ecosystem, area, protected habitat/species counts. Site grain; EEA acknowledge; no person data.

- **URL**: https://apify.com/nexgensignal/eu-natura2000-site-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 site 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 Natura 2000 Site Records — EEA Protected Sites

**Keyless. Pay per record. Every protected nature site in Europe, as one clean table.**

This actor turns the **European Environment Agency (EEA)** BISE protected-sites dataset into clean, per-site records — the register of Natura 2000 and related protected sites across Europe. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per site: its code and name, the country, the site type and designation, the major ecosystem type, the area, the year established, and the counts of protected habitat types and species. Protected-site grain, structured for engineering use, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Natura 2000 is the EU's network of protected nature sites, and the EEA's Biodiversity Information System for Europe (BISE) publishes the site register. This actor reads that register and flattens each protected site into a single analysis-ready record: the site code and name, the country, the site type and designation (with the national-language designation), the major ecosystem type, the area in square kilometres and hectares, the year established, the number of protected habitat types and species, the regions, whether a management plan exists, and the site description. It is the protected-area layer of Europe's environmental map — the published constraints on where development is restricted. Values are exactly as published. You are billed only for records actually delivered.

### Who buys this and for what job

- **Environmental due-diligence, planning, and infrastructure teams** checking whether a location intersects a protected site before siting or development.
- **ESG, renewable-energy, and land-use products** screening portfolios against protected-area constraints by country and ecosystem.
- **Researchers and conservation NGOs** studying the coverage, designation, and biodiversity of the protected-site network.
- **Data engineers** who want the protected-site register as clean rows without writing SQL against the EEA service or paging a large table.

### 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. This rider is carried in this README and on every single record. The data is a site register of published designations — **facts as published, never a development or planning verdict**: the presence of a site record states a designation exists, not that any specific project is permitted or barred.

### Site grain — no person data

The unit of every record is a protected site. The `site_name` and `country_name` are place names, not people; the register carries no natural-person fields, and this actor emits none. A person-key guard runs on every record as a pure backstop. The site, its designation, its area, and its biodiversity counts are the entire payload.

### Sample output

![Sample output — EU Natura 2000 Site Records — EEA Protected Sites](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-natura2000-site-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": "100037",
  "site_code": "100037",
  "site_name": "Matka Canyon",
  "country_name": "Macedonia (FYR)",
  "site_type": "NATDA",
  "designation": "Designated area not yet reviewed",
  "designation_national_language": "Zastiteni podracja koi seuste ne se revidirani",
  "major_ecosystem_type": "terrestrial",
  "area_km2": 65,
  "area_ha": 6575,
  "year_established": "1994",
  "number_protected_habitat_types": null,
  "number_protected_species": null,
  "regions": null,
  "management_plan": null,
  "site_description": null,
  "source": "European Environment Agency (EEA) / BISE protected sites",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) / BISE Natura 2000 & protected-site data. 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) — protected sites.",
  "disclaimer": "Protected-site register records (Natura 2000 and related designations) as published by the EEA/BISE. Site grain — no natural-person data. Site attributes, designations, area, and protected habitat/species counts are as published; this is a site register of published constraints, never a development or planning verdict.",
  "observed_at": "2026-09-25T17:21:21Z"
}
```

### Pricing

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

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

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `countryName` | string | — | Optional. Keep only sites whose country name contains this text (e.g. Germany, France). |
| `siteType` | string | — | Optional. Keep only sites of this type/designation code. |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per protected site. Real example (values as published):

```json
{
  "record_id": "102224",
  "site_code": "102224",
  "site_name": "Unteres Odertal",
  "country_name": "Germany",
  "site_type": "NATDA",
  "designation": "National Park",
  "designation_national_language": "Nationalpark",
  "major_ecosystem_type": "terrestrial",
  "area_km2": 105.4,
  "area_ha": 10540.0,
  "year_established": "1995",
  "number_protected_habitat_types": 20,
  "number_protected_species": 45,
  "regions": "Brandenburg",
  "management_plan": "Yes",
  "source": "European Environment Agency (EEA) / BISE protected sites",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Protected-site register records ... site register of published constraints, never a development ... verdict ...",
  "observed_at": "2026-08-22T00: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 protected site. Identity: `record_id` / `site_code`, `site_name`, and `country_name`. Designation: `site_type`, `designation`, and `designation_national_language`. Character: `major_ecosystem_type`, `area_km2`, `area_ha`, and `year_established`. Biodiversity: `number_protected_habitat_types` and `number_protected_species`. Context: `regions`, `management_plan`, and `site_description`. Provenance: `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 then queries the BISE protected-sites table through the DiscoData SQL service, pushing your optional `countryName` and `siteType` filters into the query so the dataset is bounded server-side, and pages through the results. Each site is flattened to one record — reading only site attributes, never a person — 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 protected-sites table holds on the order of **130,000+ sites** across reporting countries. Because each record carries `country_name`, `site_type`, and the area and biodiversity counts, segmenting by country or designation and filtering by size is straightforward. Pass a `countryName` to scope to one country, or pull the whole table to build a Europe-wide protected-area layer for screening.

### Working with the site register

The register is a screening layer, not a verdict engine. Each `site_code` is the stable identifier the wider Natura 2000 and BISE ecosystem uses, so a site record pulled here joins cleanly to habitat, species, and boundary datasets keyed on the same code. The `country_name` and `site_type` fields let you narrow to a jurisdiction and a designation class before any spatial work, and the `area_km2` / `area_ha` pair plus the protected-habitat and protected-species counts give a first-pass sense of a site's scale and sensitivity without opening the full designation dossier. Because designations change slowly, a periodic pull keeps a downstream screening table current with a small refresh — and every record carries the explicit reminder that a designation existing is a published fact, never a determination about any particular project.

### Cost guidance

One `site_record` per delivered site: cost = sites delivered × your plan's per-record price. Scope with `countryName` or `siteType` to keep runs bounded — one country is typically a few thousand to tens of thousands of sites. 1,000 sites is **$50** (Free) / **$33.50** (Gold). Pull one country for a focused screen; the full ~130,000-site table is a larger one-time seed.

### Honest limitations

- **A register, not a verdict.** These are protected-site records as published — the designation exists as stated, but this is not a planning permission, an environmental-impact assessment, or a development determination.
- **As published.** Site attributes, designations, and counts are exactly as the EEA distributes them; this actor reformats, it does not interpret.
- **Acknowledge the EEA.** Reuse requires acknowledging the EEA as the source; the acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

This is a **net-new** category for the NexGenData fleet — no existing fleet actor covers the European protected-site network. It is distinct from the fleet's emissions, waste-water, and industrial-facility cells (which carry pollution, treatment, or installation data, not protected-area designations). Its specific job is the **EEA/BISE protected-site register** — the Natura 2000 and related designations, site by site, that environmental-screening and land-use systems check locations against.

### The NexGen Signal family

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

- [EU Wastewater Compliance Records — EEA UWWTD](https://apify.com/nexgensignal/eu-wastewater-compliance-records)
- [EU Industrial Emissions Records — EEA IED Facilities](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [Natural Hazard Event Records — NASA EONET](https://apify.com/nexgensignal/natural-hazard-event-records)
- [England Flood Station Records — EA Monitoring](https://apify.com/nexgensignal/england-flood-station-records)
- [Air Quality Monitor Records — US EPA AQS](https://apify.com/nexgensignal/air-quality-monitor-records)

*Source: European Environment Agency (EEA), Biodiversity Information System for Europe (BISE) protected sites (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 register of published designations, never a development or planning verdict. Site grain; no person data of any kind.*

# Actor input Schema

## `countryName` (type: `string`):

Optional. Keep only sites whose country name contains this text (e.g. Germany, France).

## `siteType` (type: `string`):

Optional. Keep only sites of this type/designation code.

## `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-natura2000-site-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-natura2000-site-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-natura2000-site-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-natura2000-site-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/ylS0wZwp4YBejOuo5/builds/iao297AG06SQOdQKi/openapi.json