Olaf Veerman

That's great to know. Should be simple to address with a converter based on something like: https://www.npmjs.com/package/country-code-lookup

The above commit scrapes this page: http://31.24.238.89/home/AQITable.aspx A long list of stations, but they only seem to report values at 11am local time. We could get hourly data for a...

Before re-writing the scraper, we should figure out what units they're reporting in. My fear is that they're already converting the values to some sort of scale:  Couldn't find...

The non-integers may stem from the fact that they're averaging the values on that page. If you select a date range that spans multiple days, they still print 1 hourly...

Thanks @scisco I opened a separate issue to discuss back-calculating AQI.

I remember having this discussion with @jflasher a couple of months ago. The `city` nomenclature doesn't apply to every use case. Alas, there are not a lot of sources that...

I definitely see the value of having a `verified`: `true` / `false` Other questions comments: - assuming that we incorporate something like the `verified` field, what is the use case...

Apart from the data standard side, it will be interesting to see how we can reconcile this data. Should we toss out the unverified measurements for the same timestamp? How...

Only found a reference here: https://github.com/openaq/openaq-api/issues/31#issuecomment-141100344, but I think we might have had a bigger discussion around this topic. Form the above doc, they are using: > The location/ type...

I believe we are backward looking across the adapters. See for example the [Australian adapter](https://github.com/openaq/openaq-fetch/blob/df411d6f482bccd2b6f6b9df612bdf5eeb30a0fd/adapters/nsw.js#L42) On the wiki of the openaq-api we have some guidelines: https://github.com/openaq/openaq-api/wiki/4.-Writing-an-adapter#dealing-with-dates-and-date-ranges Should we revise these...