-
Notifications
You must be signed in to change notification settings - Fork 1
Charter 1: Explore forecast database with reference to latest air quality forecasts for the list of the CNN cities to discover if pollutant values are correct for given cities.
Explore forecast database with reference to latest air quality forecasts for the list of the CNN cities to discover if pollutant values are correct for given cities.
• Mike Walker-Rose
• 17/05/24
• 2 hours (approx. 15:00 – 17:00
• Testing the forecast database to establish if the forecast data is correctly extracted from CAMS and associated to the specified cities • Use the ECMWF’s forecast as an oracle to measure forecast accuracy, record differences
• List of stations (https://myftp.ecmwf.int/view/public/cams/products/cams_global_forecast/surface_concentrations/CAMS_locations_V1.csv) • Latest air quality forecasts for the list of the CNN cities in CSV format (https://myftp.ecmwf.int/files/public/cams/products/cams_global_forecast/surface_concentrations/)
- Clear the qa env forecast database, and run the forecast script to re-populate with data from CAMS
- Use the below query in mongo db to filter all data for 5 days from start date of 17/05/24
{ measurement_date: { $gte: new ISODate('2024-05-17T00:00:00.000Z'), $lte: new ISODate('2024-05-22T00:00:00.000Z') } }
- Export to csv
- Get the forecast for the same time period from ECMWF as CSV
- Run analysis on specific cities for the different available pollutants
Notes:
- PM10 & PM2.5 forecast and database values are very close, usually out by 0.00 – 0.01%
- O3 & NO2 are consistently over 10% out
Conclusion
- Single-level data is a lot more accurate than multi-level, could be problems with the request.
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)