# Marine Weather Forecast — Waves & Swell (`ponderable_hydrometer/marine-weather-scraper`) Actor

Marine forecasts — wave height, period, direction, swell & ocean currents — by coast name or coordinates. Free keyless API. For sailing, surfing, fishing & boating.

- **URL**: https://apify.com/ponderable\_hydrometer/marine-weather-scraper.md
- **Developed by:** [Ponderable Hydrometer](https://apify.com/ponderable_hydrometer) (community)
- **Categories:** Developer tools, Automation, SEO tools
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 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/platform/actors/running/actors-in-store#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 Forecast — Waves & Swell

**Marine forecasts for any coastal point — just give a place name and the actor geocodes it for you.** Wave height, period and direction, wind waves, swell and ocean currents, daily and hourly, up to 16 days out, metric or imperial. Powered by Open-Meteo. Keyless.

Perfect for sailing, surfing, offshore fishing, boating and marine planning apps.

### What you get

One result per location:

- **Place** — `location`, `country`, `admin1`, `latitude`, `longitude`, `timezone`
- **Units** — `dailyUnits`, `hourlyUnits` (so you know what each number means)
- **`daily`** — array of day rows. Default fields: `wave_height_max`, `wave_direction_dominant`, `wave_period_max`, `wind_wave_height_max`, `swell_wave_height_max`, `swell_wave_period_max`
- **`hourly`** — array of hour rows (only when you request `hourly` variables), e.g. `wave_height`, `wave_period`, `wave_direction`, `swell_wave_height`, `ocean_current_velocity`, `ocean_current_direction`

Each series is a tidy array of `{ time, <variable>: value, … }` rows — ready to chart or join.

### Modes

- **By place name** — pass `locations` (coastal names); the actor auto-geocodes each. Non-marine points are skipped with a warning.
- **By coordinates** — pass `coordinates` as `"lat,lon"` pairs over water.

Combine both. Pick your own `daily` / `hourly` variables, or use the sensible defaults.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `locations` | array | — | Coastal place names, auto-geocoded |
| `coordinates` | array | — | `"lat,lon"` pairs over water |
| `daily` | array | (6 wave/swell fields) | Daily marine variables |
| `hourly` | array | — | Optional hourly variables |
| `forecastDays` | integer | `7` | 1–16 |
| `pastDays` | integer | `0` | Include this many past days (0–92) |
| `lengthUnit` | string | `metric` | `metric` (m) or `imperial` (ft) |
| `timezone` | string | `auto` | IANA timezone or `auto` |

Provide at least one of `locations` or `coordinates`.

### Example input

```json
{
  "locations": ["Kiel", "San Diego", "Palma de Mallorca"],
  "forecastDays": 7
}
```

Hourly waves + currents:

```json
{
  "coordinates": ["54.32,10.13"],
  "hourly": ["wave_height", "swell_wave_height", "ocean_current_velocity"],
  "forecastDays": 3
}
```

### Example output (one location, trimmed)

```json
{
  "location": "Kiel",
  "country": "Germany",
  "admin1": "Schleswig-Holstein",
  "latitude": 54.32133,
  "longitude": 10.13489,
  "timezone": "Europe/Berlin",
  "dailyUnits": { "time": "iso8601", "wave_height_max": "m", "wave_period_max": "s" },
  "hourlyUnits": null,
  "daily": [
    {
      "time": "2026-07-12",
      "wave_height_max": 0.42,
      "wave_direction_dominant": 47,
      "wave_period_max": 3.15,
      "wind_wave_height_max": 0.4,
      "swell_wave_height_max": 0.12,
      "swell_wave_period_max": 5.7
    }
  ],
  "hourly": []
}
```

### Why this actor

- **Names, not just coordinates** — built-in geocoding means plain coast names work out of the box.
- **Waves + swell + currents** — daily and hourly, in one call, with unit metadata.
- **Complements land weather and tides** — distinct dataset, pairs cleanly with both.
- **Keyless & reliable** — public Open-Meteo Marine API with retry/backoff.

### Notes

- Locations must be at/near the sea; inland points return no marine data and are skipped with a warning.
- Data is from Open-Meteo's Marine API; this actor is independent and not affiliated with Open-Meteo.

### Pricing

Pay per result — **$1.00 per 1,000 results**. No subscription or platform fees; you only pay for the results you get.

### Related actors

- **NOAA Tides & Currents** — tide and current predictions (US stations).
- **Open-Meteo Weather Scraper** — land weather by place or coordinates.
- **Ham Radio Scraper** — callsigns, POTA & SOTA for field operators.

# Actor input Schema

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

Coastal place names to geocode, e.g. \["Kiel","San Diego","Palma de Mallorca"]. Must be at/near the sea.

## `coordinates` (type: `array`):

Explicit "latitude,longitude" pairs over water, e.g. \["54.32,10.13"].

## `daily` (type: `array`):

Daily marine fields. Empty = default (wave height/direction/period max, wind-wave & swell max). Examples: wave\_height\_max, swell\_wave\_period\_max.

## `hourly` (type: `array`):

Optional hourly fields, e.g. wave\_height, wave\_period, wave\_direction, swell\_wave\_height, ocean\_current\_velocity, ocean\_current\_direction.

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

Number of forecast days (1-16).

## `pastDays` (type: `integer`):

Include this many past days as well (0-92).

## `lengthUnit` (type: `string`):

metric (meters) or imperial (feet) for wave heights.

## `timezone` (type: `string`):

IANA timezone or "auto".

## Actor input object example

```json
{
  "locations": [
    "Kiel"
  ],
  "forecastDays": 7,
  "pastDays": 0,
  "lengthUnit": "metric",
  "timezone": "auto"
}
```

# 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": [
        "Kiel"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ponderable_hydrometer/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": ["Kiel"] }

# Run the Actor and wait for it to finish
run = client.actor("ponderable_hydrometer/marine-weather-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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": [
    "Kiel"
  ]
}' |
apify call ponderable_hydrometer/marine-weather-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=ponderable_hydrometer/marine-weather-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/OEERgfTW4NpOBKchj/builds/hTak55KoajGCBgUst/openapi.json