How AirDesk is used

AirDesk Forecast is an operations room for air quality: it shows what is going to happen over the next few days around a set of emission sources, and what would happen under each operating plan. It is not an archive of results to browse; it is a forecast that advances while you watch it.

This walkthrough takes five minutes and follows what anyone does the first time. Each step has its own page with more detail.

1. Sign in

The demo asks for a user and a password and opens the map; the session lasts 90 days. Language and theme are changed afterwards, from the top-bar menu. The language governs the whole application, and these guides too: the Guides button always opens the page in the application’s language, not the browser’s.

→ Sign in

2. The first look

Opening a demo shows the map: the city, the sources as markers, and above all a coloured concentration layer on the legend’s scale. Below it, the time bar shows where now sits: six hours of past on the left, the forecast on the right. In the top bar, beside VIEWING, a chip says whether the instant is PAST, PRESENT or FORECAST.

What you see is one moment of the forecast. Drag the pointer, or press Play in the Controls panel, and the layer moves with the modelled wind.

→ The first look · The forecast cycle

3. Reading a receptor

A receptor is a point where the concentration matters: in the demos, every monitoring station is one. A click on its marker opens its card with the current value, the alert level and the time series of the whole forecast, to see whether the peak has passed or is still to come.

→ Reading a receptor · Alert levels

4. Comparing a scenario

Every demo carries several scenarios: the base case and one or more alternative plans (a fuel switch, a declared pollution episode, an emergency). The top bar’s picker switches the entire forecast to the chosen scenario — map, receptors and alerts — and changes nothing else, so the difference you see is the difference between plans.

→ Comparing a scenario · Scenarios

And then

The dashboard gathers the same things as tables and charts, one section each: domain, forecast, receptors, inventory, scenarios. Every functionality has its page, and every demo tells what its domain contains and why.