Air

Air Quality Egg: It's all about the data. Part One

For many reasons the Air Quality Egg represents a profound shift from the current regiem of regulator controlled Air Quality monitoring   Specifically, the current model of AQ monitoring sees a regulator (government) define the AQ issue, the substances of concern, and the monitoring response to these top-down defined concerns.  The AQEgg turns this model on its head by allowing, though citizen lead (though still early adopter) monitoring technology that is accessible to those who can afford a $185 sensor, or have the knowhow to build their own via 3D printers and electronic schematics. In other words, the model shift from top down to bottom up where a citizen, or group of citizens, can define where monitoring should occur. As detailed in this post, the current AQ monitoring network focuses on a regional level of air quality.  For instance, there are three sensors in Edmonton that provide a regional overview of the air quality through a metric called the Air Quality Health Indicator.  Southern and Western Ontario have a total of 15 stations (see map below) that provide air quality data for over 6 million people.

ON_airmonitoring_map

The AQ Egg provides three distinct advantages:

  1. They can be located at street level more easily. We really have no idea what is happening on street level and that the numbers may be well above what the regional AQ network reports.;
  2. The map provided my COSOM is more interactive and open. In fact, developers have already started developing products in support of the AQEgg. See the Air Quality Egg Helper Chrome extension;
  3. The AQ Egg data are open and available for download and analysis.  This open data philosophy is not consistent across all regulators.

The one big advantage of regulator monitoring is the quality of the sensor, and thus the data where the measure of a sensor is the quality of the data it provides. As stated on the AQEgg wiki "...more work is really needed to make the low cost sensors sensitive to ambient pollutant concentrations." This can be seen in the sensitivity of the NO2 sensor as compared to actual ambient concentrations. In Vancouver, for instance (from the 2011 Lower Fraser Valley Air Quality Monitoring Report [PDF], pp. S-9) the annual average NO2 goal for Vancouver is 40 ug/m3 or less, with the one hour range being up to 122 ug/m3. The range of the NO2 sensor is 94 - 9400 ug/m3, less sensitive than the 'normal' ambient concentrations as detected by the regulator sensor.

Furthermore, the quality of the data is confounded by cold (an issue where I am from in Edmonton), and humidity. Regulator sensors heat or cool the air feed to a standard temperature and strip out any humidity to create a 'clean' sample.

My next post, hopefully coming soon, will examine some of the initial data generated by the AQEggs as compared to the regulator data.

Air Quality Egg: Up and Running

My egg is now up and running!  I was able to easily figure out the instructions for connecting the AQE to my computer and applying a software fix to the AQE.  The Vimeos for the fix can be found here. There are three components to the AQE that I really like:

  1. It's open sourced;
  2. The data streams are easily accessible in various formats;
  3. A Dashboard to access your data, and the data of those whom you follow.

Open Sourced Air Quality Monitoring

schematic

The above schematic is but one example of how the AQE people endeavor to make the framework for the egg as open as possible. Granted, it is an elite person who could go out and build one from scratch, but having everything that goes into the egg available on-line means that individuals can carve off a little section of the project that they can personally improve, and make it better. Perhaps you are not a hardware person, then you can build the software, or perhaps you want to establish a AQE community in your city, or maybe you want to shell out you 185$ to simply monitor the air outside your home. Whatever fits your mood.

Data is available

Granted, this is similar to Cosm's open hard- and soft-ware approach, but it is worth noting based on how accessible the data is.  As a novice data user, I appreciate that they support basic graph making within their platform, and provide tools to embed your graph into a blog post, Facebook, or on Twitter.

graph

'Triggers' can also be created. A trigger is defines a set of criteria for the data to meet, and if those criterium are met, then a tweet is sent out via your account alerting you, and the world, to the pertinent information.  From the image above, an alert will be sent out when the temperature is >-8C or <0C.  A user friendly tool that alters you to user defined changes in the data stream.

Location

The data is also accessible via JSON, XML and CSV. While I am not capable of creating a data feed through JSON into, for instance, Excel, the feeds are available for those who are.  I will, though, access the CSV function and compare the AQE feed with Alberta Environments NO2 feed for the City Center monitoring site. Coordinates for the AQE, Feed ID, and other information are provided clear and obvious.

myconsole

Dashboard or 'Console'

Finally, Cosm has provided a console interface to allow the user control over the data feeds that they follow, including API keys for each feed, and the ability to create apps.  I have not yet explored the app feature to any extent, but I will report back when I do!

Finally, you can access and review the NO2, CO, Temperature and Humidity data that I am collecting from here.