# Marine Weather & Wave Forecast Scraper (`ninhothedev/marine-weather-scraper`) Actor

$0.35/1K 🔥 Marine weather scraper! Wave height, swell, period & sea temperature forecasts worldwide. No key. JSON, CSV, Excel or API in seconds. Power surf, sailing & shipping apps ⚡

- **URL**: https://apify.com/ninhothedev/marine-weather-scraper.md
- **Developed by:** [ninhothedev](https://apify.com/ninhothedev) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.35 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Marine Weather & Wave Forecast Scraper

Hourly **marine weather and wave forecasts** for any coastal or offshore point on
Earth — wave height, wave period, wave direction, swell, wind waves, sea surface
temperature and ocean currents — plus a derived **sea state** label (Calm →
High). No API key, no login, no proxy required.

Powered by the free [Open-Meteo Marine API](https://open-meteo.com/en/docs/marine-weather-api)
(ECMWF / MFWAM wave models).

***

### ⚠️ Coastal coordinates only

The marine wave model runs on an **ocean grid**. Coordinates that fall on land
return `null` for every variable. This Actor detects those rows, skips them, and
logs a warning naming the offending location.

| Input | Result |
| --- | --- |
| `54.18,7.88,Helgoland` | ✅ 72 hourly rows |
| `36.96,-122.02,Santa Cruz` | ✅ 72 hourly rows |
| `-33.89,151.28,Bondi Beach` | ✅ 72 hourly rows |
| `52.52,13.40,Berlin` | ❌ 0 rows — inland, no marine data |

**Rule of thumb:** put your point on the water, or within a few kilometres of the
shoreline. Deep bays, river mouths and lakes are frequently outside the model
grid too. If a run returns nothing at all, the Actor fails loudly with a message
listing the coordinates that produced no data.

***

### What you get

One dataset item per **location × hour**.

| Field | Description |
| --- | --- |
| `location_name` | Your label, or `"lat,lon"` when no label was given |
| `latitude`, `longitude` | Model grid-cell centre actually used |
| `timezone` | Timezone of the returned timestamps (GMT) |
| `time` | ISO-8601 timestamp of the forecast hour |
| `wave_height_m` | Significant wave height, metres |
| `wave_direction_deg` | Mean wave direction, degrees |
| `wave_period_s` | Mean wave period, seconds |
| `wind_wave_height_m` | Wind-sea component height, metres |
| `wind_wave_direction_deg` | Wind-sea direction, degrees |
| `wind_wave_period_s` | Wind-sea period, seconds |
| `swell_wave_height_m` | Swell component height, metres |
| `swell_wave_direction_deg` | Swell direction, degrees |
| `swell_wave_period_s` | Swell period, seconds |
| `sea_surface_temp_c` | Sea surface temperature, °C |
| `ocean_current_velocity_kmh` | Surface current speed, km/h |
| `ocean_current_direction_deg` | Surface current direction, degrees |
| `sea_state` | Derived label — see table below |
| `source` | Always `open-meteo-marine` |
| `scraped_at` | UTC timestamp of the run |

#### Sea state bands

Derived from `wave_height_m` using the WMO sea-state scale:

| Wave height | `sea_state` |
| --- | --- |
| < 0.5 m | Calm |
| < 1.25 m | Smooth |
| < 2.5 m | Moderate |
| < 4 m | Rough |
| < 6 m | Very rough |
| ≥ 6 m | High |

***

### Input

| Field | Type | Default | Notes |
| --- | --- | --- | --- |
| `mode` | select | `forecast` | Hourly marine forecast per location |
| `locations` | array | Helgoland + Santa Cruz | `"lat,lon"` or `"lat,lon,Label"` — **coastal only** |
| `forecastDays` | integer | `3` | 1–7 days, 24 rows per day |
| `maxItems` | integer | `1000` | Hard cap across all locations, max 10000 |

```json
{
  "mode": "forecast",
  "locations": [
    "54.18,7.88,Helgoland",
    "36.96,-122.02,Santa Cruz",
    "-33.89,151.28,Bondi Beach"
  ],
  "forecastDays": 3,
  "maxItems": 1000
}
```

### Sample output

```json
{
  "location_name": "Santa Cruz",
  "latitude": 36.958336,
  "longitude": -122.04166,
  "timezone": "GMT",
  "time": "2026-07-28T00:00:00+00:00",
  "wave_height_m": 1.26,
  "wave_direction_deg": 266.0,
  "wave_period_s": 9.95,
  "wind_wave_height_m": 0.58,
  "wind_wave_direction_deg": 302.0,
  "wind_wave_period_s": 4.1,
  "swell_wave_height_m": 0.72,
  "swell_wave_direction_deg": 251.0,
  "swell_wave_period_s": 12.4,
  "sea_surface_temp_c": 15.8,
  "ocean_current_velocity_kmh": 0.8,
  "ocean_current_direction_deg": 178.0,
  "sea_state": "Moderate",
  "source": "open-meteo-marine",
  "scraped_at": "2026-07-28T13:42:11.204871+00:00"
}
```

***

### Use cases

- **Surf forecasts** — combine `swell_wave_height_m` and `swell_wave_period_s`
  to rank break quality across a list of spots every morning.
- **Sailing & yacht routing** — pull `wave_height_m`, `wave_direction_deg` and
  ocean currents along a planned route and flag rough legs.
- **Shipping & logistics** — monitor sea state at ports and along shipping lanes
  to anticipate delays and heavy-weather routing.
- **Offshore operations** — wind farms, survey vessels and crew transfers need
  workability windows below a wave-height threshold; alert when `sea_state`
  crosses `Rough`.
- **Aquaculture & coastal engineering** — track sea surface temperature and wave
  loading at fixed sites over rolling forecast windows.

### Pricing

Roughly **$0.5 per 1,000 items**. A three-day forecast for one location is 72
items, so ten coastal spots for three days costs about **$0.36**. Only pay for
platform usage — the underlying data source is free and needs no key.

### Tips

- One location + 7 days = 168 rows. Budget `maxItems` accordingly.
- Timestamps are returned in GMT/UTC — convert locally if you need local tide
  or daylight alignment.
- Run it on an Apify schedule (e.g. every 6 hours) to build a wave-history
  dataset for hindcasting or model comparison.
- Rows where the model has no data at all are dropped, so an empty dataset means
  every one of your coordinates was off-grid.

### Related Actors

- [Met.no Weather Scraper](https://apify.com/ninhothedev/metno-weather-scraper)
- [Weather Scraper](https://apify.com/ninhothedev/weather-scraper)
- [NOAA Weather Alerts Scraper](https://apify.com/ninhothedev/noaa-weather-alerts-scraper)
- [OpenSky Flights Scraper](https://apify.com/ninhothedev/opensky-flights-scraper)

### Legal

Fetches publicly available forecast data from the Open-Meteo Marine API. No
personal data is collected. Open-Meteo data is provided under CC BY 4.0 —
attribute Open-Meteo when republishing.

# Actor input Schema

## `mode` (type: `string`):

Scraping mode. 'forecast' fetches the hourly marine forecast (waves, swell, sea temperature, currents) for every coordinate in the Locations list.

## `locations` (type: `array`):

List of COASTAL or offshore points as "lat,lon" or "lat,lon,Label" (e.g. "54.18,7.88,Helgoland"). The marine model only covers ocean grid cells - inland coordinates return no data and are skipped. Stay on the water or within a few km of the shoreline.

## `forecastDays` (type: `integer`):

How many days of hourly forecast to fetch per location (24 rows per day). Minimum 1, maximum 7.

## `maxItems` (type: `integer`):

Hard cap on the number of hourly rows pushed to the dataset across all locations. Keeps runs cheap and predictable. Maximum 10000.

## Actor input object example

```json
{
  "mode": "forecast",
  "locations": [
    "54.18,7.88,Helgoland",
    "36.96,-122.02,Santa Cruz"
  ],
  "forecastDays": 3,
  "maxItems": 1000
}
```

# Actor output Schema

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

Open the dataset preview for this run.

# 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 = {
    "locations": [
        "54.18,7.88,Helgoland",
        "36.96,-122.02,Santa Cruz"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ninhothedev/marine-weather-scraper").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 = { "locations": [
        "54.18,7.88,Helgoland",
        "36.96,-122.02,Santa Cruz",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("ninhothedev/marine-weather-scraper").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 '{
  "locations": [
    "54.18,7.88,Helgoland",
    "36.96,-122.02,Santa Cruz"
  ]
}' |
apify call ninhothedev/marine-weather-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ninhothedev/marine-weather-scraper"
        }
    }
}
```

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/E7Vyfa76LF4Z7o0Dd/builds/ziKi5hGzLPkhUtQM5/openapi.json