Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/MazamaScience/AirMonitor
Utilities for working with air quality monitoring data
https://github.com/MazamaScience/AirMonitor
Last synced: about 2 months ago
JSON representation
Utilities for working with air quality monitoring data
- Host: GitHub
- URL: https://github.com/MazamaScience/AirMonitor
- Owner: MazamaScience
- License: gpl-3.0
- Created: 2021-10-08T00:14:10.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-02-12T12:03:20.000Z (5 months ago)
- Last Synced: 2024-03-22T04:33:50.101Z (3 months ago)
- Language: HTML
- Homepage: https://MazamaScience.github.io/AirMonitor
- Size: 14.5 MB
- Stars: 7
- Watchers: 3
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Lists
- open-sustainable-technology - AirMonitor - Utilities for working with hourly air quality monitoring data with a focus on small particulates PM2.5. (Natural Resources / Air Quality)
- awesome-air-quality - AirMonitor - _Utilities for working with air quality monitoring data_ [CRAN](https://cran.r-project.org/web/packages/AirMonitor/index.html) (Software Libraries)
README
[](https://cran.r-project.org/package=AirMonitor) [](https://cran.r-project.org/package=AirMonitor)
[](https://zenodo.org/badge/latestdoi/414793919)
A dedicated Slack channel has been created for announcements, support and to help build a community of practice around this open source package. You may request an invitation to join from [email protected].
# AirMonitor
```
Utilities for working with hourly air quality monitoring data
with a focus on small particulates (PM2.5). A compact data model is
structured as a list with two dataframes. A 'meta' dataframe contains
spatial and measuring device metadata associated with deployments at known
locations. A 'data' dataframe contains a 'datetime' column followed by
columns of measurements associated with each "device-deployment".
```
## Background
The USFS AirFire group is focused on air quality measurements associated with
wildfire smoke and maintains both historical and real-time databases of PM2.5
monitoring data obtained from stationary monitors. This data is used in
operational displays and for retrospective analysis. Data ingest and management
of air quality “stationary time series” are both important ongoing activities.
## Related Packages
The **[AirMonitorIngest](https://github.com/pnwairfire/AirMonitorIngest/)**
package is used to create data archives for the **AirMonitor** package and
isolates the work of meticulously cleaning, validating and harmonizing data from
various sources.
The **AirMonitor** package contains data access functions to easily download
harmonized data files as well as data manipulation functions that
make it easy to create "recipe style" analysis pipelines. The combination allows
analysts to work efficiently with short, readable R scripts. Interactive and
base R plotting functions allow for visual review of the data.
The **[AirMonitorPlots](https://github.com/mazamascience/AirMonitorPlots)**
package contains **ggplot2** based plotting functions for advanced plots.
## Installation
*NOTE: This package has not yet been uploaded to CRAN*
Install the latest version from GitHub with:
`devtools::install_github('mazamascience/AirMonitor')`
## Data Model
The **AirMonitor** package uses the _mts_ data model defined in
**[MazamaTimeSeries](https://mazamascience.github.io/MazamaTimeSeries/)**.
In this data model, each unique time series is referred to as a
_"device-deployment"_ -- a timeseries collected by a particular device at a
specific location. Multiple device-deployments are stored in memory as a
_monitor_ object -- an R list with two dataframes:
`monitor$meta` -- rows = unique device-deployments; cols = device/location metadata
`monitor$data` -- rows = UTC times; cols = device-deployments (plus an additional `datetime` column)
A key feature of this data model is the use of the `deviceDeploymentID` as a
"foreign key" that allows `data` columns to be mapped onto the associated
spatial and device metadata in a `meta` row. The following will always be true:
```
identical(names(monitor$data), c('datetime', monitor$meta$deviceDeploymentID))
```
Each column of `monitor$data` represents a timeseries associated with a particular
device-deployment while each row represents a _synoptic_ snapshot of all
measurements made at a particular time.
In this manner, software can create both timeseries plots and maps from a single
`monitor` object in memory.
_**Note:**_ The `monitor` object time axis specified in `data$datetime` is
guaranteed to be a regular hourly axis with no gaps.
------------------------------------------------------------------------
This project is supported by the [USFS AirFire](https://www.airfire.org) group.