# EU Protected Site Positive Impact Records — EEA BISE (`nexgensignal/eu-protected-site-positive-impact-records`) Actor

Keyless pay-per-record EEA BISE Natura 2000 positive-impact records — site code, coded beneficial practice and recorded intensity, as filed. Site grain, no person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-protected-site-positive-impact-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 positive-impact 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 Positive Impact Records — EEA BISE

**Keyless. Pay per record. The beneficial management practices recorded at Europe's Natura 2000 protected sites.**

This actor turns the **European Environment Agency (EEA) Biodiversity Information System for Europe (BISE)** into clean, per-record data — the POSITIVE impacts and beneficial management practices recorded at Natura 2000 protected sites, with their intensity. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per positive impact, structured for conservation and land-management analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Alongside the threats and pressures that harm protected sites, member states record the beneficial activities that help them — extensive grazing, mowing, restoration, and the like — each with an intensity. This actor reads the BISE positive-impact table and delivers one record per entry: the Natura 2000 SITE CODE, the coded positive impact / management PRACTICE, and its recorded INTENSITY (as a label and a number) — all carried as filed. It is the beneficial-management layer of Europe's protected-site reporting, the positive counterpart to the negative-impact cell.

### Who buys this and for what job

- **Conservation NGOs and site managers** benchmarking which beneficial practices are recorded across the network.
- **Agri-environment programme designers** linking supportive land-use to protected-site outcomes.
- **Biodiversity researchers** analysing beneficial-management intensity by practice and site.
- **Data engineers** who want the BISE positive-impact 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 classifications as filed — not an assessment of this actor's making.

### Site grain — no person data

The unit of every record is a positive impact at a protected site — a site code, a practice, and an intensity, never a person. BISE reporting is at site level: there is **no contact, site-manager, or named-individual field** in the source table, and none is selected or emitted. A person-key guard runs on every record as a backstop. The site code identifies a place in the Natura 2000 network, never a person.

### A note on scale, honestly

The source table holds **27,455 rows** as verified by an exact `COUNT(*)` at build time, which matches the planning index for this category. It spans the protected sites and beneficial practices reported across the network. The live count above is authoritative.

### Sample output

![Sample output — EU Protected Site Positive Impact Records — EEA BISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-protected-site-positive-impact-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:Grazing:High",
  "site_code": "AT1101112",
  "impact_description": "Grazing",
  "intensity": "High",
  "intensity_number": 3,
  "source": "EEA Biodiversity Information System for Europe (BISE) — Natura 2000 site beneficial (positive) impacts",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Biodiversity Information System for Europe (BISE) / Natura 2000 reporting. 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) / Natura 2000 (discodata.eea.europa.eu).",
  "disclaimer": "Beneficial (POSITIVE) management practices and impacts recorded at Europe's Natura 2000 protected sites, at site / practice / intensity grain from the EEA BISE database. Each record carries the Natura 2000 SITE CODE, the coded positive impact / management PRACTICE, and its recorded INTENSITY (label and number) VERBATIM. Site grain — there is no contact, site-manager, or named-individual field in the source, none is selected or emitted, and 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 |
|-------|-----------|--------|--------|---------------------------|
| `protected_site_positive_impact_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 positive impact. Representative example (values as reported):

```json
{
  "record_id": "AT1101112:Grazing:High",
  "site_code": "AT1101112",
  "impact_description": "Grazing",
  "intensity": "High",
  "intensity_number": 3,
  "source": "EEA Biodiversity Information System for Europe (BISE) — Natura 2000 site beneficial (positive) impacts",
  "observed_at": "2026-08-27T00: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 positive impact at a protected site. Identity: `record_id` and `site_code`. Impact: `impact_description` (the coded beneficial practice), `intensity` (the label), and `intensity_number` (the numeric intensity). 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 positive-impact table, ordered by the high-cardinality site code, and flattens each row to one record — carrying every coded label and value **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 **27,455 rows** across protected sites and beneficial practices. Because each record carries the `site_code`, the `impact_description`, and the `intensity`, segmenting by site or practice is straightforward. Pull the whole table to seed a conservation warehouse, or a slice by site code.

### Working with the data

The positive impacts are a stewardship layer, and the fields make them actionable. Because every record pairs a `site_code` with an `impact_description` and an `intensity_number`, an analyst can rank the most common beneficial practices across the network, find the sites with the most intensive positive management, and — joined to the negative-impact cell on the site code — weigh beneficial against harmful activity for any site.

### Reading the intensity scale

Every positive impact carries both a text intensity label (`intensity`) and a numeric intensity (`intensity_number`), so the data works for both human reading and machine aggregation. The numeric scale lets you compute an intensity-weighted count of beneficial practices per site — a simple proxy for how actively a site is being managed for conservation — without parsing the label text. Because the label and number travel together, you can also validate one against the other, and pivot the whole table into a site-by-practice matrix where each cell is the recorded intensity. Practices that recur at high intensity across many sites point to the management interventions member states lean on most; practices that appear rarely, or only at low intensity, mark where beneficial management is thin.

### The Natura 2000 context

Natura 2000 is the EU's network of protected areas established under the Birds and Habitats Directives, and the beneficial-impact reporting sits inside the six-yearly Article 17 / standard-data-form reporting that member states file for each site. The positive impacts recorded here are drawn from the same controlled activity vocabulary as the threats and pressures, which is what makes the positive and negative cells directly comparable on a shared code. Because the vocabulary is standardised across all reporting countries, a beneficial practice such as extensive grazing is coded the same way in Austria as in Portugal — so cross-country comparison needs no translation layer. This actor delivers the beneficial half of that picture as clean rows, ready to join to the species, habitat, and negative-impact cells for a full view of any site.

### Cost guidance

One `protected_site_positive_impact_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.** Practices and intensities are as filed by member states; this actor reformats, it does not audit or recompute.
- **Coded practices.** The `impact_description` is a controlled-vocabulary label (e.g. "Grazing"), not free narrative.
- **Site grain only.** This is the beneficial-impact record; site names and geometries live in the companion protected-site cells.
- **Acknowledge the EEA**, and note there is **no person data** of any kind.

### Differentiation

It is the POSITIVE counterpart to **eu-protected-site-negative-impact-records** (the threats and pressures) — a distinct source table — and complements the protected-site species and habitat inventory cells. Its specific job is the **BISE Natura 2000 beneficial-impact records**.

### The NexGen Signal family

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

- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-records)
- [EU Nitrate Monitoring Records — EEA](https://apify.com/nexgensignal/eu-nitrate-monitoring-records)
- [EU Bathing Water Quality Records — EEA](https://apify.com/nexgensignal/eu-bathing-water-quality-records)
- [EU Industrial Emissions Records — EEA](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [EU Surface Water Priority Substance Records — EEA](https://apify.com/nexgensignal/eu-surface-water-priority-substance-records)

*Source: European Environment Agency (EEA), Biodiversity Information System for Europe (BISE) / Natura 2000 (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 grain; no contact, site-manager, or responsible-person field is selected or emitted, no natural-person data of any kind. Reported classifications as filed, not an assessment.*

# Actor input Schema

## `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-positive-impact-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-positive-impact-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-positive-impact-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-positive-impact-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/aaMYW8uh1hIjIaYd8/builds/riDZO1m1y68gsTN9I/openapi.json