The consistent naming scheme in monitor_getCurrentStatus() is much better but we should add a couple of useful fields and one for consistency:
last_validLocalTimestamp
previous_validLocalTimestamp
change yesterday_AQI to yesterday_pm25_24hr
include a complete set of last_~ and previous_~ summary variables
Having an overly complete set of summary variables means that we won't have to go back and add things later when someone at the forest service has some crazy new idea.
Details
Here is a comparison the column names of the tibble returned by the soon-to-be-deprecated monitor_currentData():
The motivation for this is the desire to use the monitor_getCurrentStatus() function to replace monitor_currentData() in the monitor_writeCurrentGeoJSON() function. Output from this function can be seen at https://haze.airfire.org/monitoring/latest/geojson/PM2.5_latest10.geojson and will have chunks like:
Task
The consistent naming scheme in
monitor_getCurrentStatus()
is much better but we should add a couple of useful fields and one for consistency:last_validLocalTimestamp
previous_validLocalTimestamp
yesterday_AQI
toyesterday_pm25_24hr
last_~
andprevious_~
summary variablesHaving an overly complete set of summary variables means that we won't have to go back and add things later when someone at the forest service has some crazy new idea.
Details
Here is a comparison the column names of the tibble returned by the soon-to-be-deprecated
monitor_currentData()
:The motivation for this is the desire to use the
monitor_getCurrentStatus()
function to replacemonitor_currentData()
in themonitor_writeCurrentGeoJSON()
function. Output from this function can be seen at https://haze.airfire.org/monitoring/latest/geojson/PM2.5_latest10.geojson and will have chunks like: