Following on from previous posts describing the PM sensors that we are using, the next steps are about testing them before giving them out to volunteers.
This post will describe some of these tests and also give some insight into what data is generated and how it can be used.
Some simple trips with the sensors allow me to capture data and make sure they are working as expected. The data that is captured is stored on the phone (android smartphone) and can be later uploaded to the aircasting website or to any other source. The aircasting website is a community mapping development by HabitatMap and provides a form of crowd-sourced data. An example of this is shown below and can be found here.
Beyond this pooling of data in a community map like the aircasting website, it’s also possible to look at individual data streams. This was part of the testing process for our AirBeam sensors. The data from one trip with one of the sensors (unit 1 for reference) is shown in the diagram below:
This shows a single trip in south Liverpool near Allerton Road. The individual data points are visible, with a simple colour coding according to the spread of the data i.e. green are lower values and red are higher values: this does not necessarily mean that red is unhealthy however, it’s just a higher reading.
The diagram below shows the same trip and data but zoomed it for one part. The reading for one data point is also shown. This reading was taken on 13 October 2016 and the PM reading was 13.12 micrograms per cubic meter.
At this stage I will not go further into how this data can be used. The purpose of this post is simply to share some insight into the testing process. A goal of the project is to find out how this data can be useful to individuals and community groups – at this stage we just want to make sure the data is being generated and that it looks in line with expectations. The journey above supports the view that this sensor is working as expected.
More to follow on testing.