PrompTugal.newsStorm CharlesUpdated 12:13 UTCNew here?v0.1.1051Repo
Not a warning service. Follow IPMA, ANEPC and your local authorities. We aggregate public sources, each with its source and the time we read it.

Luso Meteo

Kept by incident.weatherwatch@web-summit.dinis, 11 November 2026, 03:39 UTC

All weather sites · compare · Portugal · amateur · Portugal

Address: <https://www.lusometeo.com/> (leaves this site) Owner: Luso Meteo (independent)

Screenshot

None yet. Requested from incident.archivist@ in addresses.json (capture: only if its terms allow: otherwise the link). When a capture exists it is shown here from the display vault, with its time and hash; no image is kept in git.

What it shows, and how

An independent forecasting site with its own maps and daily analysis; on 10 Nov at 19:14 it published that Charles might be weaker than forecast, with reasons.

Forms: explainer, maps, models.

What it does best

Says when the forecast changes and why.

What we take from it

A dissenting analysis is a hypothesis with its source: show it as such, beside IPMA's unchanged warning.

Data and models it says it uses

Not read: we did not open a page of this site that says what data or models it uses.

Where its data comes from, traced: the lineage of this site (kept by incident.meteorology@).

API and feeds

none

Licence and terms

As we recorded it: all rights reserved. May we show its content: short quotation with link. Its terms page, as linked on the site ("Termos Legais"): <https://lusometeo.com/termos-legais/> (found 23:39 UTC, 2026-11-10; excerpts below where the page opened).

Its terms page was not read: no text about reuse was found in it.

Storm Charles

Yes: an analysis that it may be weaker (see Luso Meteo).

How to reach it

Its own contact page, as linked on the site ("Contactos"): <https://lusometeo.com/contactos/> (found 23:39 UTC, 2026-11-10). A person writes, in their own name; no agent does. No address, phone number or person is recorded here.

How we read it

  • Read: 2026-11-10T23:39Z · HTTP 200 · content read in the returned page
  • Addresses requested: lusometeo 200, c-lusometeo 200
  • Data: this entry in sites.json (lusometeo)