pat_monitorComparison() function and pwfsl_closestMonitorID

[jbootman]

Hi,
I have a question regarding the pat_monitorComparison() function in the AirSensor package.
The pat_monitorComparison() function appears to use an already assigned pwfsl_closestMonitorID in the pat meta data to pull the AirNow regulatory monitor data using a PWFSLSmoke function.
pwfsl_closestMonitorID -- identifier for the nearest regulatory monitor and according to a reference document, the "pwfsl", official monitors are obtained from the USFS AirFire site using the PWFSLSmoke R package, but it is not clear how the ID is assigned.

The concern:
I saw that Iowa DNR regulatory monitors associated with PurpleAir's all have the post fix "_01".
But the regulatory monitors are continuous (hourly) FEMs that are typically POC3s or POC4s.
Iowa DNR POC1s do not have hourly data but 24hr data.
So the ID associated with the closest regulatory monitor that has the post fix "_01" does not correspond to a POC1 but to a POC3 or POC4.
This causes confusion as to which regulatory monitor is being selected for comparison to the PurpleAir.
Is there a way to get the appropriate POC# as part of the pwfsl_closestMonitorID for the regulatory monitor ID being used in comparison?
pwfsl_closestMonitorID is using the appropriate AQS ID, just not the appropriate POC#.
Or is there a location, where one can look up the assigned pwfsl_closestMonitorID's to determine which POC it is using for comparison?
Thank you for your help.

[jonathancallahan]

Jasmine,

We are trying to consolidate questions about the AirSensor package in a dedicated Slack channel where everyone working with this package can see our answers. Our hope is to build up a community of users who may begin to help each other out in the future.

I would appreciate it if you would repost your question in the MazamaPackageSupport Slack workspace in the #air-sensor channel. Here is an invite:

https://join.slack.com/t/mazamapackagesupport/shared_invite/zt-vl8u0p4l-31z~wUCEqpiGHNzzTBgbRg

Don't hesitate to contact [email protected] directly if you are unable to post in the Slack channel.

Jon