i had not thought to put the collection of AQI calculations into an extension 
to StdWXCalculate

i amend my suggested split of weewx-airlink to an ‘airlink’ data acquisition 
service providing PMx.x values, plus an ‘aqi’ extension to StdWXCalculate to 
convert PMx.x values to AQI-related values

and yes, i’d be happy to code this extension (mainly by pinching john’s code) 
if john wanted to head that direction - i’ll have to code something 
similar/simpler for myself anyway if john doesn't want to go that way (i.e. 
separate ‘aqi’ (sub-)service)

> On 27 Sep 2020, at 10:28 pm, Tom Keffer <[email protected]> wrote:
> 
> The "WeeWX way" is to emit what the hardware offers, then let StdWXCalculate 
> determine whether to keep it or calculate a new value in software.
> 
> Right now, it's fairly easy to extend StdWXCalculate to calculate new types 
> via the XTypes facility. Gary and I are working on a version that will make 
> it even easier.
> 
> On Sat, Sep 26, 2020 at 10:30 PM Graham Eddy <[email protected] 
> <mailto:[email protected]>> wrote:
> i was about to pinch john’s code for the AQI side of things - i get PM2.5 
> values via gw1000 - when i see this new driver announced. (i have found 
> ecowitt’s purported 24 hour average values very unreliable - drifting, random 
> resets, etc - but the actual pm2.5 values seem fine → derive the averaged 
> values myself)
> 
> can i suggest that acquiring PMx.x values and deriving AQI values be kept as 
> separate services? the AQI service would provide AQI xtype (mainly for 
> cheetah) and convert PMx.x values in weewx packets to equivalent AQI values 
> inserted into weewx packet (this is what i was going to implement). 
> design-wise this would also allow support of AQI values derived from multiple 
> pollution types (NO, etc) as well as abstracting the pollutant monitors
> 
>> On 27 Sep 2020, at 1:43 pm, John Kline <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Hi Rich,
>> 
>> I’ve created the github project here:
>> https://github.com/chaunceygardiner/weewx-airlink 
>> <https://github.com/chaunceygardiner/weewx-airlink>
>> 
>> I haven’t had any issues with the extension, but it’s not a priority for me 
>> until more is known about the AirLink.
>> 
>> Cheers,
>> John
>> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/1A05561B-6E18-4D13-B23C-7D3DCA5ADD69%40gmail.com
>  
> <https://groups.google.com/d/msgid/weewx-user/1A05561B-6E18-4D13-B23C-7D3DCA5ADD69%40gmail.com?utm_medium=email&utm_source=footer>.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEATLW%2BWMaguZvAN0VULz%3DbyZWHUO8CHq6V%3DmVhG7nE-Sg%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEATLW%2BWMaguZvAN0VULz%3DbyZWHUO8CHq6V%3DmVhG7nE-Sg%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5A2D0839-5245-4DC3-9642-09F80D65BF71%40gmail.com.

Reply via email to