Forecast base time on the summary page will default to most recent forecast -24hours (so there is a days worth of data at least).
The page will now call the API for each valid forecast time between the base forecast time and the current time. The UI will then analyse each of these and show the data for the points with the largest deviation between in-situ and forecasted values.
So for example for London the No2 value could have a large deviation at 03:00, which we would display. The So2 value might have had it largest devation at 18:00, which we would show. The table will still only show one values per city per pollutant, the ones with the maximum deviation.
This pattern will also be followed by the overall AQI value. I.e the values in a row are the ones where the difference between the forecasted and actual AQI levels is at a maximum.
Forecast base time on the summary page will default to most recent forecast -24hours (so there is a days worth of data at least).
The page will now call the API for each valid forecast time between the base forecast time and the current time. The UI will then analyse each of these and show the data for the points with the largest deviation between in-situ and forecasted values. So for example for London the No2 value could have a large deviation at 03:00, which we would display. The So2 value might have had it largest devation at 18:00, which we would show. The table will still only show one values per city per pollutant, the ones with the maximum deviation. This pattern will also be followed by the overall AQI value. I.e the values in a row are the ones where the difference between the forecasted and actual AQI levels is at a maximum.