There are 20-ish TX sites and 1 WA site that have UTC offset set to 0 erroneously (exact numbers/sites depend on time period). I reported this to AirNow, and they said they will fix, but monetio could still do a quick check for this based on lon and just drop those rows.
and/or we could use timezonefinder (if installed / as an optional dependency) to compute the values.
There are 20-ish TX sites and 1 WA site that have UTC offset set to 0 erroneously (exact numbers/sites depend on time period). I reported this to AirNow, and they said they will fix, but monetio could still do a quick check for this based on lon and just drop those rows.
and/or we could use timezonefinder (if installed / as an optional dependency) to compute the values.
This was noticed by @colin-harkins