| Literature DB >> 34062961 |
Tiago Veiga1, Arne Munch-Ellingsen2, Christoforos Papastergiopoulos3, Dimitrios Tzovaras3, Ilias Kalamaras3, Kerstin Bach1, Konstantinos Votis3, Sigmund Akselsen2.
Abstract
Air pollution is a widespread problem due to its impact on both humans and the environment. Providing decision makers with artificial intelligence based solutions requires to monitor the ambient air quality accurately and in a timely manner, as AI models highly depend on the underlying data used to justify the predictions. Unfortunately, in urban contexts, the hyper-locality of air quality, varying from street to street, makes it difficult to monitor using high-end sensors, as the cost of the amount of sensors needed for such local measurements is too high. In addition, development of pollution dispersion models is challenging. The deployment of a low-cost sensor network allows a more dense cover of a region but at the cost of noisier sensing. This paper describes the development and deployment of a low-cost sensor network, discussing its challenges and applications, and is highly motivated by talks with the local municipality and the exploration of new technologies to improve air quality related services. However, before using data from these sources, calibration procedures are needed to ensure that the quality of the data is at a good level. We describe our steps towards developing calibration models and how they benefit the applications identified as important in the talks with the municipality.Entities:
Keywords: air quality; data visualization; low-cost sensors; sensor calibration; warning systems
Mesh:
Substances:
Year: 2021 PMID: 34062961 PMCID: PMC8124547 DOI: 10.3390/s21093190
Source DB: PubMed Journal: Sensors (Basel) ISSN: 1424-8220 Impact factor: 3.576
Figure 1Overview of data collection, process and application pipeline.
Figure 2(Left): sensor network map (Blue: deployed low-cost sensors; Yellow: planned low-cost sensors; Purple: NEA network of industrial sensors). (Right): highlight of locations where low-cost sensors are co-located with reference sensors.
Figure 3Photographs of the placement of low-cost sensors, highlighted in the pictures. (a): Co-located with a reference sensor at Elgeseter; (b): at Berg school.
Figure 4Photo of deployed sensor casing, including gas and particulate matter sensors, controller and power boards, and respective legend.
Technical specifications of Alphasense OPC-N3 particle monitor, as specified by the manufacturer [15].
| Name | Measures | Detection | Num. Bins | Max Particle | Max Coincidence |
|---|---|---|---|---|---|
| Alphasense OPC-N3 | PM1 | 0.35–40 | 24 | 10,000 |
Data collected between 15 November 2020 and 23 February 2021 for reference and low-cost sensors at locations where both are co-located. Data were not pre-processed and we used reference data “as is” from public API; therefore we maintained negative values that might be explained by the calibration procedures for industrial reference sensors.
| ( | ||||||||
|
|
| |||||||
|
|
|
|
| |||||
| PM2.5 | PM10 | PM2.5 | PM10 | PM2.5 | PM10 | PM2.5 | PM10 | |
|
| 2314 | 2314 | 2344 | 2344 | 2340 | 2340 | 2345 | 2345 |
|
| 9.09 | 12.88 | 1.43 | 3.26 | 9.06 | 11.45 | 1.11 | 2.00 |
|
| 11.73 | 13.67 | 1.46 | 4.28 | 10.64 | 12.57 | 1.02 | 1.86 |
|
| −4.81 | −3.80 | 0.00 | 0.00 | 0.10 | 0.10 | 0.02 | 0.04 |
|
| 1.86 | 3.84 | 0.45 | 0.97 | 2.50 | 3.10 | 0.39 | 0.72 |
|
| 4.92 | 8.17 | 0.98 | 1.94 | 5.00 | 6.70 | 0.82 | 1.45 |
|
| 12.16 | 17.94 | 1.87 | 3.73 | 11.30 | 15.00 | 1.50 | 2.64 |
|
| 90.44 | 96.10 | 14.70 | 71.48 | 83.40 | 135.10 | 10.33 | 13.72 |
| ( | ||||||||
|
|
|
|
| |||||
| Elgeseter | PM2.5 | 0.61 |
| |||||
| PM10 |
|
| ||||||
| Torget | PM2.5 |
|
| |||||
| PM10 |
|
| ||||||
Figure 5Scatter plots between low-cost sensor data and references with data collected between 15 November 2020 and 23 February 2021 at Elgeseter.
Calibration results with both prediction and classification models.
| ( | ||||||
|
|
|
|
| |||
|
|
|
|
|
|
| |
|
| ||||||
| PM2.5 |
|
|
|
|
|
|
| PM2.5, Temperature (OPC), Humidity (OPC) |
|
|
|
|
|
|
| PM2.5, Temperature, Humidity |
|
|
|
|
|
|
| PM2.5, Weather |
|
|
|
|
|
|
| PM1, PM2.5, PM10, Weather |
|
|
|
|
|
|
| PM1, PM2.5, PM10, Weather, Traffic |
|
|
|
|
|
|
| PM1, PM2.5, PM10, Weather, Hour of Day, Day of week |
|
|
|
|
|
|
|
| ||||||
| PM10 |
|
|
|
|
|
|
| PM10, Temperature (OPC), Humidity (OPC) |
|
|
|
|
|
|
| PM10, Temperature, Humidity |
|
|
|
|
|
|
| PM10, Weather |
|
|
|
|
|
|
| PM1, PM2.5, PM10, Weather |
|
|
|
|
|
|
| PM1, PM2.5, PM10, Weather, Traffic |
|
|
|
|
|
|
| PM1, PM2.5, PM10, Weather, Hour of Day, Day of week |
|
|
|
|
|
|
| ( | ||||||
|
|
|
| ||||
|
|
|
|
|
|
| |
|
| ||||||
| PM2.5 |
|
|
|
|
|
|
| PM2.5, Temperature (OPC), Humidity (OPC) |
|
|
|
|
|
|
| PM2.5, Temperature, Humidity |
|
|
|
|
|
|
| PM2.5, Weather |
|
|
|
|
|
|
| PM1, PM2.5, PM10, Weather |
|
|
|
|
|
|
| PM1, PM2.5, PM10, Weather, Traffic |
|
|
|
|
|
|
| PM1, PM2.5, PM10, Weather, Hour of Day, Day of week |
|
|
|
|
|
|
|
| ||||||
| PM10 |
|
|
|
|
|
|
| PM10, Temperature (OPC), Humidity (OPC) |
|
|
|
|
|
|
| PM10, Temperature, Humidity |
|
|
|
|
|
|
| PM10, Weather |
|
|
|
|
|
|
| PM1, PM2.5, PM10, Weather |
|
|
|
|
|
|
| PM1, PM2.5, PM10, Weather, Traffic |
|
|
|
|
|
|
| PMPM1, PM2.5, PM10, Weather, Hour of Day, Day of week |
|
|
|
|
|
|
Data collected between 15 November 2020 and 23 February 2021 for reference and calibrated low-cost sensors at locations where both are co-located (in μg/m3). Both sensors were calibrated using the model trained with Elgeseter data. Data were not pre-processed and we used reference data “as is” from the public API; therefore we maintained negative values that might be explained by the calibration procedures for industrial reference sensors.
| ( | ||||||||
|
|
| |||||||
|
|
|
|
| |||||
| PM2.5 | PM10 | PM | PM | PM2.5 | PM10 | PM | PM | |
|
| 2314 | 2314 | 2344 | 2344 | 2340 | 2340 | 2345 | 2345 |
|
| 9.09 | 12.88 | 9.63 | 12.95 | 9.06 | 11.45 | 8.66 | 10.96 |
|
| 11.73 | 13.67 | 9.86 | 10.45 | 10.64 | 12.57 | 9.00 | 9.32 |
|
| −4.81 | −3.80 | −1.23 | −1.54 | 0.10 | 0.10 | −1.18 | −1.33 |
|
| 1.86 | 3.84 | 3.52 | 6.12 | 2.50 | 3.10 | 3.11 | 5.27 |
|
| 4.92 | 8.17 | 6.33 | 9.54 | 5.00 | 6.70 | 5.83 | 8.12 |
|
| 12.16 | 17.94 | 12.10 | 17.48 | 11.30 | 15.00 | 9.92 | 14.05 |
|
| 90.44 | 96.10 | 62.79 | 66.59 | 83.40 | 135.10 | 62.73 | 65.46 |
| ( | ||||||||
|
|
|
|
| |||||
| Elgeseter | PM2.5 |
|
| |||||
| PM10 |
|
| ||||||
| Torget | PM2.5 |
|
| |||||
| PM10 |
|
| ||||||
Figure 6Scatter plots between calibrated low-cost sensor data and references. Data collected between 15 November 2020 and 23 February 2021 at Elgeseter.
Figure 7Adjacent low-cost sensors used in the baseline models for every reference sensor. Red: reference sensors. Green: two of the three closest adjacent low-cost sensors used in the average value baseline model. Yellow: the third and closest adjacent low-cost sensor used both in the average value and closest low-cost sensor baseline models. Red/Yellow: in the Torget and Elgeseter areas there is a low-cost sensor next to the reference sensor, so a dual coloring is used to mark both.
Pollutants prediction based on low-cost sensor data. Data collected between 15 November 2020 and 23 February 2021. Train–test split:0.75/0.25.
| Models | Training Set | Test Set | ||
|---|---|---|---|---|
| RMSE | R2 | RMSE | R2 | |
|
| ||||
| Random Forest Regressor |
|
|
|
|
| Closest low-cost sensor value |
|
|
|
|
| Closest 3 low-cost sensors avg value |
|
|
|
|
|
| ||||
| Random Forest Regressor |
|
|
|
|
| Closest low-cost sensor value |
|
|
|
|
| Closest 3 low-cost sensors avg value |
|
|
|
|
Results for prediction of air quality levels with low-cost sensor data (calibrated) and NEA as input. Data collected between 15 November 2020 and 23 February 2021. Train–test split: . Thresholds: PM2.5 = 25, PM10 = 45.
| Inputs | Test (w/Low-Cost Sensor) | Test (w/NEA) | ||||
|---|---|---|---|---|---|---|
| Recall | Precision | AUC | Recall | Precision | AUC | |
|
| ||||||
| Pollutants |
|
|
|
|
|
|
| Pollutants, Weather |
|
|
|
|
|
|
| Pollutants, Weather, Traffic |
|
|
|
|
|
|
| Pollutants, Weather, Traffic, Temporal |
|
|
|
|
|
|
| Pollutants, Weather, Traffic, Temporal, Delta |
|
|
|
|
|
|
| Pollutants, Weather, Traffic, Temporal, Delta, Forecast |
|
|
|
|
|
|
|
| ||||||
| Pollutants |
|
|
|
|
|
|
| Pollutants, Weather |
|
|
|
|
|
|
| Pollutants, Weather, Traffic |
|
|
|
|
|
|
| Pollutants, Weather, Traffic, Temporal |
|
|
|
|
|
|
| Pollutants, Weather, Traffic, Temporal, Delta |
|
|
|
|
|
|
| Pollutants, Weather, Traffic, Temporal, Delta, Forecast |
|
|
|
|
|
|
Figure 8Visualizations for the low-cost sensor data. Left: map view; a star-like glyph is used to display the measurements of each sensor. Right: graph view; each sensor corresponds to a node, with nearby nodes denoting similar measurements. Bottom: timeline view; the progress of the pollutants in time.
Figure 9Close-up of a star glyph used in the map view. Each spike angle corresponds to a different type of measurement. The larger the spike’s length, the larger the corresponding measurement. The numeric details as shown here appear upon mousing over a selected glyph.
Figure 10Example of linked graph and map visualization. (a) On a particular day, the graph view reveals groups of sensors with similar previous behavior. One group was selected by the user and the corresponding sensors are highlighted on the map. (b) A few hours later, the selected sensors exhibit similar behavior, measuring high pollutant concentrations, distinguished from the behavior of the other sensors.