Science · R&D · Innovation

Science that turns weather into measurable readiness.

Our research focuses on three questions: how to process meteorological data without losing its origin, how to bring preparedness forward for weather-driven natural disasters, and how to measure the risk that shifts with climate change. We explain our method openly — not the details that make the product different.

  • 7named source institutions: ECMWF, NOAA, DWD, AEMET, Météo-France, EUMETSAT, Copernicus
  • T+6 … T+48lead-time ladder in the verification design
  • 5,376samples in the 14-day verification matrix (design)
  • 9capabilities with a public maturity status

Our goals

Three areas, measurable goals.

Goals are not measured success. Next to each one we write down how progress will be measured.

01 · Data processing

Every number traceable to its source.

Processing multi-source meteorological data while preserving its meaning and origin.

  • Every input is stored with its institution, product, run time and content identity
  • Incompatible sources are not silently blended or resampled
  • A product not checked against real observations is never called “verified”

Criterion · share of outputs without a lineage record · open verification reports

02 · Natural disasters

Shortening the time from warning to action.

Floods and flash floods, storms, strong wind, heatwaves, snow and ice, coastal events.

  • Make the chain official warning → awareness → acknowledgement → readiness measurable
  • Rehearse the real event in advance with scenario-based exercises
  • Connect after-action learning to the next threshold review

Criterion · time from warning to the first preparation action · in exercise and event records

03 · Climate change and adaptation

Making shifting thresholds visible.

Translating climate-scale change into the language of local operating thresholds.

  • Track how often local thresholds — hot days, intense-rain hours, frost nights — are crossed, using reanalysis data
  • Produce inputs for municipal and sector adaptation plans
  • Keep climate-scale and weather-scale decisions apart

Criterion · trends in local threshold frequency · decisions that become adaptation plans

Our scientific model

A shared core. Activity-specific meaning.

Weather information is only the beginning. The model has four layers: each inherits the previous layer’s output together with its origin, and no layer silently changes the evidence that came before it.

Calculation, rules and language do not replace one another

Numerical model

calculates

Produces the values, ranges and verification metrics for your point from forecast fields.

Every number you see on screen comes only from here.

Rule engine

applies

Applies your thresholds and the sector pack’s rules deterministically.

Every trigger shows which rule ran, with which value.

Language model

explains

Translates the result into the language of your work and writes briefing and checklist text.

It does not calculate, set thresholds or decide.

Public scientific architecture

  1. 01

    Source processing

    Forecast fields, official warnings, station observations and satellite products are taken in with their name, time and content identity.

    Source evidenceVerification

    Evidence
  2. 02

    Local probabilistic model

    Multi-model evidence for your point is ordered by lead time. The model range is shown openly; calibration comes only after verification.

    Hazard

    Uncertainty
  3. 03

    Impact model

    Your thresholds and exposure meet the weather evidence: which job, at what time, how much it may be affected.

    ExposureImpactRiskTiming

    Impact
  4. 04

    Decision and evidence

    Recommendation, checklist, decision record and exercise. Every step can be traced back to its source.

    PreparationActionOutcomeLearning

    Decision

We explain openly how the layers work. Details of threshold calibration, sector rule sets and the order in which evidence is combined are part of the product. This is explanatory architecture — not a formula, a scoring function, a live-engine claim or a ranked provider list.

Public scientific principles

Seven rules every layer obeys.

How trust is kept
  1. 01

    Source remains source.

    A provider’s record is never re-labelled as ours.

  2. 02

    Missing is not zero.

    A missing value stays missing; it never becomes “no rain” or “low risk”.

  3. 03

    Agreement is not probability.

    Models resembling each other is not a measured likelihood.

  4. 04

    Severity is not confidence.

    How strong an event could be says nothing about how sure we are.

  5. 05

    Official warning is not advisory.

    The issuing authority’s warning keeps its own lane; our output never takes its place.

  6. 06

    No silent data fusion.

    Sources are combined only by documented rules, and the combination stays visible.

  7. 07

    No public claim without evidence.

    A capability is described at the stage its published evidence supports.

Numerical analysis

Forecast meets observation.

Verification is done on the forecast’s own grid and at the exact valid time. The error definition, the metrics and the matching rule are public: an academic should be able to reproduce the same result.

Point sampling

The value is taken from the model’s own grid and the sampling method is recorded. No height correction is applied silently.

Lead-time ladder

The same valid time is viewed from the T+6, T+12, T+24 and T+48 runs, so you see how forecast skill changes with lead time.

Time alignment

Forecast and observation are matched at the exact valid time, with zero tolerance. Nearby timestamps are not silently substituted for exact observation times; an unmatched sample stays out, with its reason recorded.

Uncertainty

The range between models is shown openly. Agreement between models is not presented as a probability.

Metrics

Mean error, mean absolute error and root-mean-square error — by lead time, station and model. Missing data are not treated as zero.

No ranking

Models are not ranked until a verification campaign is complete and its results are published.

Error and metric definitions

e = F − O
forecast minus observation
Bias = (1/n) Σ e
mean error
MAE = (1/n) Σ |e|
mean absolute error
RMSE = √[(1/n) Σ e²]
root-mean-square error

The canonical unit is the kelvin. Observations come from official national station networks: AEMET in Spain, Météo-France in France.

Verification campaign · 2 m air temperature

8stations4lead times3models56runs

5,376expected samples · 14 days

The campaign is a controlled pilot panel and makes no claim to represent a whole country. Its launch gates are being checked; results will be published when the campaign is complete.

Big-data processing

From immutable raw data to a traceable decision.

Model fields, warning feeds, station measurements and satellite imagery arrive in different formats and at different speeds. Our pipeline processes all of them with the same discipline.

  1. 01

    Ingest

    GRIB2, NetCDF, CAP and station data pulled from each institution by name

  2. 02

    Raw store

    Kept byte for byte, unchanged, with a content identity

  3. 03

    Decode

    Meteorological codes read with standard tools; meaning preserved

  4. 04

    Canonical cube

    Variable, valid time and lead time in one schema

  5. 05

    Sampling

    Sampled to station, site and route points

  6. 06

    Matching

    Forecast and observation matched at the exact time, with a unique key

  7. 07

    Archive

    Daily export and independent verification

  • Immutable raw data

    A raw file is never overwritten. Every product can be traced back to the bytes it came from.

  • Content identity

    Every record carries a SHA-256 content identity: the same data is not counted twice, and changed data is noticed.

  • Reproducibility

    Deterministic identities and idempotent jobs: an interrupted job can be safely run again.

  • Locks and heartbeats

    Two concurrent processes cannot write the same record; long jobs keep their lock alive.

  • Separate lanes

    Forecasts, observations and official warnings are kept in separate tables, with separate meanings.

  • Measured scale

    Capacity is planned from measured data; an estimate is never labelled “measured”.

Verification and maturity

We state plainly where we are.

Every scientific capability stands on one of five steps. A step is climbed only when its evidence is published. No capability is at the “in production” step today.

Source: public capability manifest

Maturity of scientific capabilities, from the public capability manifest
Capability1Code present2Locally verified3Verified with a live source4Calibrated5In production
2 m air temperatureCanonical variable · kelvinCurrent stage: Verified with a live sourcereachedreachedcurrent stagenot reachednot reached
Forecast–observation matching2 m air temperature onlyCurrent stage: Verified with a live sourcereachedreachedcurrent stagenot reachednot reached
Temperature verification metricsBias, MAE and RMSE · 2 mCurrent stage: Locally verifiedreachedcurrent stagenot reachednot reachednot reached
Heavy precipitation evidenceNot calibratedCurrent stage: Verified with a live sourcereachedreachedcurrent stagenot reachednot reached
Wind hazard evidenceNot calibratedCurrent stage: Verified with a live sourcereachedreachedcurrent stagenot reachednot reached
Confidence engineNo scored confidenceCurrent stage: Code presentcurrent stagenot reachednot reachednot reachednot reached
Impact risk modelNot publishedCurrent stage: Code presentcurrent stagenot reachednot reachednot reachednot reached
FloodHazard evidenceCurrent stage: Not developed yetnot reachednot reachednot reachednot reachednot reached
Climatological anomalyNeeded for the climate goalCurrent stage: Not developed yetnot reachednot reachednot reachednot reachednot reached

Canonical native-lead forecasts, provenance, and official-warning source state are shown separately. Fusion, hazard probability, confidence, and impact risk remain unfinished. This is not a certification.

Research areas

Statuses come from the public research configuration. VERIFIED is not used as a marketing badge.

  • Official warning connectivityLIVE
  • Source provenanceLIVE
  • Forecast verificationIN VALIDATION
  • Prospective reference-skill researchIN VALIDATION
  • Operational impact modellingIN DEVELOPMENT
  • Calibration researchIN RESEARCH
  • Outcome learningPLANNED

Preparedness research

From warning to readiness

Official warnings remain authoritative. MetOry preparation and advisory outputs are decision support. The two lanes stay parallel and are never merged.

Lane 1

Official warning — authoritative

Issued and owned by the national authority, shown unchanged and with attribution. A missing feed does not mean there is no warning.

Lane 2

MetOry preparation / advisory — decision support

A separate reading for your activity. Not an official warning, not a safety order and not an all-clear.

  1. 1

    Detect

    Weather evidence or an official warning becomes relevant.

  2. 2

    Reach

    The information reaches the responsible person or team.

  3. 3

    Acknowledge

    Receipt and awareness can be recorded.

  4. 4

    Assess

    Operational relevance is reviewed in context.

  5. 5

    Prepare

    Preparation steps are reviewed, assigned and tracked.

  6. 6

    Exercise / act

    A drill, a preparation action or a real response can be recorded.

  7. 7

    Review

    Outcome and lessons are captured for next time.

Preparedness Evidence Trail

Where it applies, an organisation can record a structured trail of warning, delivery, acknowledgement, assignment, action, exercise and review. This describes product and research direction; not every state is live today.

  • Warning receivedLIVE
  • Notification deliveredIN DEVELOPMENT
  • Warning viewedIN DEVELOPMENT
  • Warning acknowledgedIN DEVELOPMENT
  • Responsible person or team assignedIN DEVELOPMENT
  • Preparation startedIN RESEARCH
  • Preparation completedIN RESEARCH
  • Exercise completedPLANNED
  • Outcome reviewedPLANNED
SYNTHETIC / EXAMPLE

Exercise: heavy rain warning at a logistics facility

Illustrative / synthetic scenario. Not a real customer activity, not an observed outcome, and not an official warning.

  1. 01Heavy rain warning
  2. 02Logistics facility
  3. 03Drainage inspection
  4. 04Outdoor stock protection
  5. 05Route review
  6. 06Manager acknowledgement
  7. 07Post-exercise review

Process records are not a claim that MetOry prevented damage, saved money or reduced risk by a percentage, unless that result is independently measured and verified.

Research & Applied Science

Five programmes, one evidence chain.

Each programme carries its current status from configuration — not a marketing claim.

01LIVE

Multi-source meteorological evidence

Forecast, observation, satellite / Earth-observation and official-warning evidence, retained with source, product, time and provenance.

02IN VALIDATION

Forecast verification

Where suitable observations exist, forecast evidence can be tested against real observations. Historical and prospective verification methods are under active research.

03IN DEVELOPMENT

Weather-to-impact modelling

Studying how meteorological hazards interact with location, exposure and operational context. Not a published loss or probability product.

04IN RESEARCH

Warning & preparedness behaviour

Studying whether warning information reaches the right person, is acknowledged in time and results in preparation.

05PLANNED

Exercises, outcomes & learning

Evaluating preparedness procedures through exercises, records and post-event learning.

Partner on a programme

Get in touch

Event-day programme

Match day, race day, fair day: one decision chain for a crowd on the move.

Tens of thousands of people travel to one place at one time, stand outdoors for hours and leave together. The event-day product applies the MetOry evidence chain to that day in four phases and keeps every value traceable to its source.

Open the event-day page

A stadium gathers its crowd in the two hours before kick-off and releases it in one hour after the final whistle. Rain chance, gusts and rain amount at those moments decide covers, gates, queues and the journey home.

  1. TransportAirport, station or home to the stadium on a traffic-aware route, with the forecast hour at each point for the time you pass it.
  2. EntryThe two hours before kick-off at the gates: queues, concourses and open stands.
  3. EventKick-off to the final whistle on the pitch and in the stands, with the worst of rain chance, gusts and rain amount.
  4. ExitThe hour after the final whistle: the crowd leaves together and transport is saturated.

On the evidence chain

  • HazardHazard evidence on the forecastHourly rain chance, gusts and rain amount from the live forecast feed, shown as published; missing is not zero.LIVE
  • ExposureExposure at the venueThe venue point and the phases of the day: entry, event and exit as the organiser sets them.LIVE
  • ExposureExposure on the wayA traffic-aware route from airport, station or address, with the forecast hour at each sampled point for the time of passage.LIVE
  • HazardLocal official thresholdsWhere the national weather service publishes its own warning limits per zone (AEMET for Barcelona, Girona and Madrid), the event day is compared with them too. Other zones follow as their tables are verified.LIVE
  • TimingDecision timingFollowed from T72: countdown, refresh every 10 minutes and the same window read again as the forecast updates.LIVE
  • PreparationPreparation timelineReview points at T−72, T−24, T−6 and T−1 before the gates open, with steps that grow with the level reached. Rain chance alone now reaches Attention at most (display rule v2).LIVE
  • PreparationFollowed days on the accountToday a followed day lives on the device. Account sync and a notification on a colour change are in development.IN DEVELOPMENT
  • ImpactVenue-specific thresholdsThe three colours use MetOry's published display thresholds. Calibrating them per venue type against observed event days is in research.IN RESEARCH
  • LearningOutcome learningRecording what happened on the day (covers used, gates held, delays) and learning from it is planned.PLANNED

Nothing on this tab is an official warning, a probability or a safety order. Official warnings for the venue's area stay with the issuing authority and are listed on the warnings page.

Collaboration

Become a research partner.

We welcome joint verification campaigns, exercise research and adaptation studies with universities, meteorological services, municipalities and civil-protection bodies — and dialogue on responsible data use, verification and interoperability.

This describes the direction of MetOry’s work and does not imply official affiliation, endorsement or funding by the European Union, EUMETSAT or any meteorological authority.

Named sources are not ranked, and attribution is not endorsement. MetOry does not replace national meteorological authorities. This page explains method and maturity: it is not an operational dashboard and not an official warning. Goals are not measured success.