You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Curious as to the archive directory structure - I pulled data from ~500 sensors and saved the data and meta for each as csv files (/project/deviceDeploymentID_data.csv, /project/deviceDeploymentID_meta.csv), and now can't figure out how to read them back in to a pa_timeseries object.
@jeanmico By creating csv files you have basically left the world view of the AirSensor package. It isn't currently straightforward to reenter that world view and create pat_timeseries objects.
As you can see from this GitHub issue, we are working on some documentation to demonstrate how to create your own archive of 'pas' and 'pat' objects as compressed binary files -- ".rda" files.
After @AstridSanna finishes this document, we will be curious to get your feedback.
It is possible to create new 'pas' and 'pat' objects directly from the PurpleAir and ThingSpeak data sources. But this takes a long time.
For this article you will need to create a new archive for sensors in the Methow Valley. These sensors are seen with:
This document should go through the following steps:
flat directory structure
setArchiveBaseUrl()
to get initial 'pas' object onlydeviceDeploymentIDs
for MVCAA sensorspat_createNew()
create 'pat' objects for each sensor. I think it will get the last week if you don't specifystartdate
andenddate
~/Data/my_project/
)load()
use the archive structure
Do the same but create monthly 'pat' files and store both the 'pas' and the 'pat' files in the "well known" archive directory structure.
setArchiveBaseDir()
instead ofsetArchiveBaseUrl()
The text was updated successfully, but these errors were encountered: