EU · weather

meteosat

On demand
On demand — not run on a schedule

always raises by design: the EUMETSAT Data Store needs EUMDAC consumer credentials this connector does not implement.

Meteosat SEVIRI imagery — **no anonymous source exists; this fails on purpose.** It used to read ``s3://eumetsat-odc-sst-msg``, described as a public EUMETSAT subset. That bucket does not exist (S3 answers ``NoSuchBucket``, checked 2026-09-30), so every run fell through to the synthetic sine wave. Alternatives checked: * EUMETSAT Data Store (EUMDAC) — the real archive and near-real-time feed, but it needs a (free) consumer key + secret; not wired up here. * EUMETSAT's own S3 (``s3.r1.cloud.eumetsat.int``) holds a SEVIRI Level-1.5 *climate data record* (historical, not near-real-time) and denies anonymous listing (403). * The AWS Registry of Open Data mirrors GOES and Himawari, not Meteosat. Rather than invent a bucket or data, :py:meth:`fetch` raises :class:`ConnectorError` — even when ``PHRONESIS_ALLOW_SYNTHETIC`` is set.

No observations stored yet
This connector has not written any series to the warehouse, so there is nothing to plot. Run phronesis-energy connector run meteosat to ingest some.

Technical

Coverage
EU
Refresh
hourly
Variables
meteosat_vismeteosat_ir
Licence
ATTRIBUTION
Class
phronesis_energy.connectors.live_extras:MeteosatS3Connector