MeteoAlarm CAP feed for Portugal
Every CAP warning message in MeteoAlarm's Portugal feed, one line each: area, hazard, level, onset, expiry, time of issue and text, with what appeared or left since the read before.
Three layers: the source (who publishes it, the terms, when it was read), the raw data as the publisher served it, and the processed data, what this site makes of it. The processing is where the value is: named fields, places joined, gaps marked, every value kept with its source and time.
1. The source
At a glance
| Field | Value |
|---|---|
| Publisher | MeteoAlarm (EUMETNET), from IPMA |
| Source | https://feeds.meteoalarm.org/api/v1/warnings/feeds-portugal |
| Reader page | https://www.meteoalarm.org/en/live/region/PT |
| Schedule | hourly: the Pages workflow (.github/workflows/pages.yml), on a schedule at 17 minutes past each hour, and on every push to dev |
| Owner | data@PrompTugal.dinis |
| Collector | sources/meteoalarm-pt/collect.mjs |
| Since | 2026-11-17 |
| Last read | 2026-11-18 19:17 UTC |
| Last run | ok: 1 requests ok, 0 failed |
| Now | 66 messages, 27 not expired |
| Licence | The data: the source's terms (MeteoAlarm (EUMETNET), for IPMA). This page, the card and the records we add: CC BY 4.0. |
Reuse terms
MeteoAlarm: re-users must name the national service (IPMA), keep the time of issue, link www.meteoalarm.org and publish MeteoAlarm's disclaimer. latest.json carries all four. Reuse: with conditions (above).
Terms page: https://www.meteoalarm.org/en/live/page/terms-and-conditions, read on 2026-11-11.
2. The raw data
As MeteoAlarm (EUMETNET) served it at the latest read (2026-11-18 19:17 UTC), unprocessed. The files: feeds-portugal.json.
3. The processed data
The collector reads the CAP messages, keeps area, level, hazard and times, and marks what appeared since the last read. The result: latest.json.
More about this source
What runs by code, by agents and by people
Code
- the collector reads the source and writes latest.json, reads.json and the vault copy
- GitHub Actions runs it every hour and deploys the site
- the build makes the API, the OpenAPI description and the pages
Agents
- data@PrompTugal.dinis (Opus) wrote the collector, this card and the pages on 17 November 2026; data.dev@ and data.design@ (Sonnet) wrote parts of the site build and the design variations
People
- Dinis Cruz instructs; no person has checked the values yet (not reviewed)
Cost
| Field | Value |
|---|---|
| per run tokens | 0 |
| per run model cost usd | 0 |
| runner | GitHub Actions on a public repository: no charge (GitHub's terms for public repositories); about 3 minutes a run for all sources together (measured locally, 17 November 2026) |
| build tokens | not measured: accountant@'s ledger is not running on this account; to be added when it is |
| note | Code only: no model is called when the data is collected. |
API addresses
These addresses stay for the life of v1 (the contract).
curl -s https://data.promptugal.news/api/v1/meteoalarm-pt/latest.json
curl -s https://data.promptugal.news/api/v1/meteoalarm-pt/reads.json | head -c 600
Vault
| Field | Value |
|---|---|
| Vault id | whliuye4 |
| Public read key | sgit_public_read_e4142959bb0a044c31d0f2a5e8b8aca8fe4793d4eb091cff2211abb6d9f8e5c0 |
| Clone | sgit clone sgit_public_read_e4142959bb0a044c31d0f2a5e8b8aca8fe4793d4eb091cff2211abb6d9f8e5c0:whliuye4 |
| Note | Public read key: the source is public, so anyone may read the vault. A read key is derived one way and cannot write. The write key is never in this repository. |
Last runs
| Time (UTC) | Requests ok | Requests failed | Reads with changed bytes |
|---|---|---|---|
| 2026-11-18 19:17 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 19:12 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 19:08 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 19:05 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 18:57 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 18:53 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 17:56 UTC | 1 | 0 | 1 of 1 |
| 2026-11-18 17:41 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 16:32 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 16:13 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 16:10 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 16:06 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 16:01 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 15:57 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 15:53 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 15:49 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 15:45 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 15:42 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 15:38 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 15:35 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 15:30 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 15:15 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 15:10 UTC | 1 | 0 | 0 of 1 |
| 2026-11-18 15:07 UTC | 1 | 0 | 0 of 1 |
Showing 24 of 48 runs kept. Full detail with sha256: reads.json.
Preview of the values
The first 5 of 66 entries in messages, as read 2026-11-18 19:17 UTC. Source: https://feeds.meteoalarm.org/api/v1/warnings/feeds-portugal. Long values are shortened here; the file has them whole.
| id | sent_utc | msg_type | area | emma | level | Source |
|---|---|---|---|---|---|---|
| 2.49.0.0.620.0.PT.261113013218.PO-10-6350 | 2026-11-13T01:32:18Z | Update | Viana do Castelo | PT006 | yellow | source |
| 2.49.0.0.620.0.PT.261113013218.PO-10-6351 | 2026-11-13T01:32:18Z | Update | Braga | PT022 | yellow | source |
| 2.49.0.0.620.0.PT.261113013218.PO-10-6352 | 2026-11-13T01:32:18Z | Update | Porto | PT009 | yellow | source |
| 2.49.0.0.620.0.PT.261113013218.PO-10-6353 | 2026-11-13T01:32:18Z | Update | Vila Real | PT007 | yellow | source |
| 2.49.0.0.620.0.PT.261113144303.PO-10-6357 | 2026-11-13T14:43:03Z | Update | Viseu | PT011 | yellow | source |