-
Notifications
You must be signed in to change notification settings - Fork 1
Product Description
The Copernicus Atmosphere Monitoring Service (CAMS) provides forecasts of air quality around the world. CAMS products have a wide reach to the general public through smartphone apps and, notably, through daily broadcasts of air quality index forecasts for different cities by CNN International. The accuracy of the forecasts in comparison to what is experienced can vary, which can be accentuated by local events, e.g. plumes from wildfires not correctly captured by the model. The model is evaluated via extensive quality-checks against official air quality measurements, but there are parts of the world where these aren’t available.
The rise of affordable air quality sensors and data aggregation sites such as OpenAQ means that there are in-situ readings available for cities that are not currently quality-checked. The readings are not calibrated, there are often gaps and errors, but there is still an opportunity to increase the coverage of forecast quality-checking.
vAirify will regularly poll open air quality data so that it is as close to real-time as possible, and will apply a level of filtering to remove obviously inaccurate data. For a particular city vAirify will combine the readings to give a single value, which can then be compared with the forecast.
vAirify will provide an intuitive user interface that allows forecasters to explore variations between CAMS forecasts and the actual readings on the ground. At a glance, forecasters will be able to see the biggest differences, and will be able to drill down to the local area using a map view. vAirify will help forecasters make choices about the selection of observation stations, so that stations giving anomalous readings can be discounted.
To help forecasters to see long-term patterns, e.g. to determine whether a particular variation is a one-off or regular occurrence, vAirify will also be able to display historical data, for one city at a time.
Together these features will help forecasters improve the forecasting models and be more responsive to variations when they occur.
Getting Started and Overview
- Product Description
- Roles and Responsibilities
- User Roles and Goals
- Architectural Design
- Iterations
- Decision Records
- Summary Page Explanation
- Deployment Guide
- Working Practices
- Q&A
Investigations and Notebooks
- CAMs Schema
- Exploratory Notebooks
- Forecast ETL Process
- In Situ air pollution data sources
- Notebook: OpenAQ data overview
- Notebook: Unit conversion
- Data Archive Considerations
Manual Test Charters
- Charter 1 (Comparing ECMWF forecast to database values)
- Charter 2 (Backend performance)
- Charter 3 (Forecast range implementation)
- Charter 4 (In situ bad data)
- Charter 5 (Filtering ppm units)
- Charter 7 (Forecast API input validation)
- Charter 8 (Forecast API database sizes)
- Charter 9 (Measurements summary API input validation)
- Charter 10 (Seeding bad data)
- Charter 11 ()Measurements API input validation
- Charter 12 (Validating echart plot accuracy)
- Charter 13 (Explore UI after data outage)
- Charter 14 (City page address)
- Charter 15 (BugFix diff 0 calculation)
- Charter 16 (City page chart data mocking)
- Charter 17 (Summary table logic)
- Charter 18 (AQI chart colour banding)
- Charter 19 (City page screen sizes)
- Charter 20 (Date picker)
- Charter 21 (Graph consistency)
- Charter 22 (High measurement values)
- Charter 23 (ppm -> µg m³)
- Charter 24 (Textures API input validation)
- Charter 25 (Graph line colours)
- Charter 26 (Fill in gaps in forecast)
- Charter 27 (Graph behaviour with mock data)
- Charter 28 (Summary table accuracy)
- Re‐execute: Charter 28
- Charter 29 (Fill in gaps in situ)
- Charter 30 (Forecast window)
- Charter 31 (UI screen sizes)