Combine annual data from AirNow, AIRSIS and WRCC:

If archiveDataDir is defined, data will be loaded from this local archive. Otherwise, data will be loaded from the monitoring data repository maintained by the USFS AirFire team.

Current year files loaded by this function are updated once per week.

For the most recent data in the last 10 days, use monitor_loadLatest().

For daily updates covering the most recent 45 days, use monitor_loadDaily().

For data extended more than 45 days into the past, use monitor_load().

monitor_loadAnnual(
  year = NULL,
  archiveBaseUrl = paste0("https://airfire-data-exports.s3.us-west-2.amazonaws.com/",
    "monitoring/v2"),
  archiveBaseDir = NULL,
  QC_negativeValues = c("zero", "na", "ignore"),
  epaPreference = c("airnow", "epa_aqs")
)

Arguments

year

Year [YYYY].

archiveBaseUrl

Base URL for monitoring v2 data files.

archiveBaseDir

Local base directory for monitoring v2 data files.

QC_negativeValues

Type of QC to apply to negative values.

epaPreference

Preferred data source for EPA data when annual data files are available from both `epa_aqs` and `airnow`.

Value

A mts_monitor object with PM2.5 monitoring data. (A list with meta and data dataframes.)

Note

This function guarantees that only a single time series will be associated with each locationID using the following logic:

  1. AirNow data takes precedence over data from AIRSIS or WRCC

  2. more recent data takes precedence over older data

This relevant mostly for "temporary" monitors which may be replaced after they are initially deployed. If you want access to all device deployments associated with a specific locationID, you can use the provider specific functions: airnow_loadAnnual, airsis_loadAnnual and wrcc_loadAnnual

Examples

if (FALSE) {
library(AirMonitor)
# Fail gracefully if any resources are not available
try({

monitor_loadAnnual() %>%
  monitor_filter(stateCode %in% CONUS) %>%
  monitor_leaflet()

}, silent = FALSE)
}