-
Notifications
You must be signed in to change notification settings - Fork 1
Charter 3: Explore retrieved forecast range using different cities to discover if range is implemented correctly
mwalker-scottlogic edited this page Sep 16, 2024
·
3 revisions
Charter: Explore retrieved forecast range using different cities to discover if range is implemented correctly
- Mike Walker-Rose
- 28/05/24
- 45 mins
This charter is focused on understanding if the range of retrieved forecast data is T+5 days (rather than T+1-5), using different cities and any other variables to observe if the forecast for a city is 5 days ahead with 3hr increments
- The
forecast
database
- Explore using the list of cities to establish if there are any differences using different data
- Delete all db data, run
run_forecast_etl.py
- export dataset as csv
- Explore data in excel to establish if behaviour is correct around
forecast_base_time
&forecast_valid_time
- ran check to see if every single
forecast_base_time
was the same - ran check to see if every single
last_modified_time
was the same - ran check to see if every single
created_time
was the same - ran check to see if every single city had same pattern of valid_date_times (line by line checking each matched an expected valid time that was taken from the Vienna dataset (which had been manually checked to verify incrementing by 3 hrs from
valid_base_time
)
- No surprises in the data, all checks in the Notes section passed
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)