# EU Maritime Environmental Measure Records — WISE (`nexgensignal/eu-maritime-environmental-measure-records`) Actor

Keyless, pay-per-record EEA WISE marine measures. One row per policy measure — code, name, sector, use/activity, status, origin, nature, country, MSFD descriptors. Measure grain, verbatim; EEA acknowledge; no person data.

- **URL**: https://apify.com/nexgensignal/eu-maritime-environmental-measure-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 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 Maritime Environmental Measure Records — WISE

**Keyless. Pay per record. Europe's marine shipping-and-ports environmental policy measures, as one clean catalogue.**

This actor turns the **European Environment Agency (EEA)** WISE marine shipping-and-ports measures dataset into clean, per-measure records — the catalogue of environmental policy measures addressing marine shipping and ports across Europe. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per measure: its catalogue code, name, sector, and use/activity, its status, origin, and nature, the water-body category and spatial scope, the country, and the Marine Strategy Framework Directive descriptors it links to. Policy-measure grain, structured for engineering use, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

The EEA's WISE marine information system catalogues the environmental measures that member states apply to shipping and ports — the policy and management responses to marine pressures. This actor reads that catalogue and flattens each measure into a single analysis-ready record: the catalogue code, the measure name (the text describing the measure), the sector and use or activity it addresses, its status, its legal or policy origin, its nature (legislation, management, and so on), the water-body category and spatial scope, the country, what the measure impacts, and the set of MSFD descriptors (D1–D11) it links to. Values are carried **verbatim** as published. You are billed only for records actually delivered.

### Who buys this and for what job

- **Maritime-policy, port-authority, and environmental-consulting teams** cataloguing the measures that apply to shipping and ports by sector and country.
- **ESG, marine-spatial-planning, and compliance products** mapping policy measures to MSFD descriptors and marine pressures.
- **Researchers and NGOs** studying the marine-measure landscape across Europe.
- **Data engineers** who want the WISE marine measures catalogue as clean rows without writing SQL against the EEA service.

### 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 record. The data is a catalogue of policy measures as published — not a compliance verdict or an assessment of a measure's effectiveness.

### Policy-measure grain — no person data

The unit of every record is a policy measure. The measure name is the text of the measure, not a person; the dataset carries no natural-person fields, and this actor emits none, with a person-key guard as a pure backstop. Catalogue codes, measure text, sectors, origins, and descriptor links are the entire payload.

### Sample output

![Sample output — EU Maritime Environmental Measure Records — WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-maritime-environmental-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": "BD01",
  "catalogue_code": "BD01",
  "measure_name": "Other measures to reduce impacts from marine aquaculture infrastructures and operation",
  "sector": "Ports and traffic",
  "use_or_activity": "Not specified",
  "status": "Taken",
  "measure_origin": "BD (Directive 79/409/EEC)",
  "measure_nature": "not specified",
  "water_body_category": "Not specified",
  "spatial_scope": "Not specified",
  "country": "Germany",
  "measure_impact_to": "Birds",
  "measure_impact_to_details": "Gavia stellata",
  "msfd_descriptors": "D1=1; D2=0; D3=0; D4=0; D5=1; D6=1; D7=0; D8=1; D9=1; D10=0; D11=0",
  "source": "European Environment Agency (EEA) WISE marine measures",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE marine shipping-and-ports measures 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), WISE marine measures (shipping & ports) dataset.",
  "disclaimer": "Marine environmental policy-measure records (shipping and ports) as published by the EEA. Policy-measure grain — no natural-person data. Measure descriptions, origins, and MSFD descriptor links are carried VERBATIM as published; this is a catalogue of measures, not a compliance verdict.",
  "observed_at": "2026-09-25T17:33:03Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `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 |
|-------|------|---------|-------------|
| `countryContains` | string | — | Optional. Keep only measures whose country contains this text. |
| `sectorContains` | string | — | Optional. Keep only measures whose sector contains this text (e.g. Traffic, Ports). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

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

```json
{
  "record_id": "WFD01",
  "catalogue_code": "WFD01",
  "measure_name": "Monitoring, assessment and information before, during and after project ...",
  "sector": "Traffic",
  "use_or_activity": "Navigation dredging",
  "status": "Not specified",
  "measure_origin": "WFD (Directive 2000/60/EC)",
  "measure_nature": "legislation/regulation",
  "water_body_category": "Coastal",
  "spatial_scope": "National",
  "country": "Germany",
  "measure_impact_to": "Habitats",
  "msfd_descriptors": "D1=1; D6=1",
  "source": "European Environment Agency (EEA) WISE marine measures",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Marine environmental policy-measure records ... carried VERBATIM as published ...",
  "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 policy measure. Identity: `record_id` / `catalogue_code` and `measure_name`. Classification: `sector`, `use_or_activity`, `status`, `measure_origin`, and `measure_nature`. Scope: `water_body_category`, `spatial_scope`, and `country`. Impact: `measure_impact_to`, `measure_impact_to_details`, and `msfd_descriptors` (the D1–D11 Marine Strategy Framework Directive descriptors the measure links to, joined verbatim). 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 marine-measures master view through the DiscoData SQL service, applies your optional `countryContains` and `sectorContains` filters, and flattens each measure to one record — carrying the measure text and descriptor links **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 measures catalogue holds on the order of **4,600+ policy measures** across reporting countries and sectors. Because each record carries the `sector`, `country`, and MSFD descriptors, segmenting by sector or country and linking to marine-pressure descriptors is straightforward. Pull one country or sector for a focused view, or the whole catalogue to seed a marine-measures table.

### Working with the catalogue

The catalogue is built to be pivoted several ways, and the fields carry the structure to do it. The `measure_origin` and `measure_nature` distinguish legislative measures from management or voluntary ones, so a policy analyst can isolate the binding responses from the softer ones in a single filter. The `sector` and `use_or_activity` locate each measure against the marine pressure it addresses — navigation dredging, port operations, and the like — while the `msfd_descriptors` field links the measure to the Marine Strategy Framework Directive descriptors (D1 biodiversity through D11 energy and noise), so the catalogue joins cleanly to any descriptor-keyed marine-status dataset. Because the measure text, its status, and its descriptor links all travel verbatim, two pulls taken apart can be diffed to see which measures were added, retired, or re-scoped between EEA reporting rounds, keeping a downstream measures table current without re-ingesting the whole catalogue.

### Cost guidance

One `measure_record` per delivered measure: cost = measures delivered × your plan's per-record price. Scope with `countryContains` or `sectorContains` to keep runs bounded. The whole catalogue is ~4,600 measures; 1,000 measures is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **A catalogue, not a verdict.** These are policy measures as published — not a compliance judgment or an assessment of effectiveness.
- **As published.** Measure text, origins, and descriptor links are carried verbatim; this actor reformats, it does not interpret.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

It is distinct from the fleet's other EEA water and marine cells (bathing water, waste-water, water-body chemistry, nitrate — which carry quality or facility data, not policy measures). Its specific job is the **WISE marine shipping-and-ports measures catalogue** — the policy responses, measure by measure, linked to MSFD descriptors.

### The NexGen Signal family

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

- [EU Waterbody Quality Records — EEA WISE Waterbase](https://apify.com/nexgensignal/eu-waterbody-quality-records)
- [EU Bathing Water Quality Records — EEA BWD](https://apify.com/nexgensignal/eu-bathing-water-quality-records)
- [EU Nitrate Monitoring Records — EEA WISE Nitrates](https://apify.com/nexgensignal/eu-nitrate-monitoring-records)
- [EU Industrial Emissions Records — EEA IED Facilities](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [EU Regulatory Change Records — CELLAR](https://apify.com/nexgensignal/eu-regulatory-change-records)

*Source: European Environment Agency (EEA), WISE marine measures (shipping & ports) dataset (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. A catalogue of policy measures as published, not a compliance verdict. Measure grain; no person data of any kind.*

# Actor input Schema

## `countryContains` (type: `string`):

Optional. Keep only measures whose country contains this text.

## `sectorContains` (type: `string`):

Optional. Keep only measures whose sector contains this text (e.g. Traffic, Ports).

## `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-maritime-environmental-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": 10 }

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

```

## MCP server setup

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