Sensor trip ideas

I’ve just put in a Seeed order for some more Grove sensors (because they’re very easy to set up and use). Here’s what I’m thinking of doing with them:

  • Collect the usual environmental data – air quality, dust, temp/humid, water, alcohol – and compare against readings from the same sensor set that’s in the Brck office.
  • Wildlife detection using motion sensor, mike, and camera unit.
  • Investigate fire/smoke effects using smoke and gas sensors; I’m more interested in effects of different types of cooking fuels in houses, but could adapt this for camping too (a group I belonged to lost a member to fumes in their tent, so this is of value to me).
  • Human monitoring using alcohol detector and galvanic skin response (e.g. sweat density) monitor.

I’m also thinking about what sort of UAV or balloon data would be useful from a short trip.

  • Even 10 minutes of data would be good – especially if it’s a) messy (e.g. oblique), and b) contains features like buildings
  • Although 10 minutes of nice clean stabilised downward-looking is also a good thing to have: garbage in, garbage out really does apply to aerial images.

Starting with sensors

[cross-posted from]

sensors at the iHub Kenya

I’m at the iHub Nairobi today with a bunch of sensors (thanks for the loan, Brck team!), because some of the Kenyan ideas for today’s Space Apps Challenge projects are sensor-based.  Those projects didn’t happen, but I’ve been having some very interesting chats with people about the hardware we have here, about their own use of hardware, and about why coders aren’t including hardware in their projects.

Aside from utility (not every project needs sensors, just as not every project needs a web interface), the two big blocks appear to be unfamiliarity and fear.  First, the fear: generally that using hardware will be hard to learn, or that you’ll break equipment irreparably.  And the familiarity: coders are used to software, and hardware can seem very different to software, at first.

The fear: I suffered from these fears too, as I got back into hardware.  That combination of “oh grief I’m going to break it” combined with “but what could I possibly do that’s useful with this stuff”.   The answer is really quite simple.  Buy some kits, start putting them together, and learn from that a) what works and doesn’t, b) why, how, when hardware is useful , and c) how to make your designs more useful.  Yes, things break; no, the outputs aren’t always perfect, but the point of using kits is to learn, and fast.  If that sounds familiar, it’s because it’s the same ethos that drives agile software development: build, fail, learn, build better until it fits what you need.

And speaking of familiarity: electronics is really coding with things.  You have basic units (components), basic things you can do with them (connect together, run voltage through them, read outputs from them etc), that you design together into a working system.  And if you’re using microprocessor-based kits (Arduino, RaspberryPi etc), then you really *are* coding, because you’re programming the microprocessor to send signals, respond to data inputs etc.

I’m doing this the easy way.  I’m starting with components that slot together and have code that’s already written for them: the grove sensor series.   The kit you need to start getting sensor results with these is:

Erm, that’s it.   You’ll need to download the basic Arduino software, and find the example code for your sensor in somewhere like the Seeed wiki, but  for about $45, you too can start experimenting with sensor data. I’ve just left a stack of Grove sensors and a couple of Arduino Unos at the Brck Nairobi office; I’m using the same stack in New Jersey so we can compare results and ideas.   We’ve already got data from this experiment – proving that the Brck office is dustier than the Ushahidi office nextdoor isn’t a great leap forward in knowledge, but taking these sensors out into the field, and getting comparable data from places without good coverage from ‘official’ air quality monitors is.

The journey from here involves lots of placing sensors and learning how they fail, what they do under stress, and what their limitations are.  It’s also, ultimately, to start reducing the number, size and price of components needed to produce usable and useful sensor data, to learn from pioneer communities like Public Laboratory and RiverKeeper, and to make it just ‘normal’ to include sensors in system designs and ‘normal’ to plug them into existing equipment like Brck and mobile phones (I have a Geiger counter that plugs into my phone’s audio port – I’d love to see more of that sort of reuse out there).

And now, back to thinking about questions like “could you build a gas sensor into your clothes”.  I just happen to have an MQ-5 gas sensor in front of me, and am thinking about what it would take to get from there to an alarm ringing on my phone…

Sensor Shopping

[Cross-posted from]


Here’s the list of items that should arrive at home soon: a basic sensor set to supplement the Geiger counter, spectroscopes, cameras, microcontrollers (Arduino and RaspberryPi), accelerometers, temperature, IR and range sensors in my toolkit.

I’m most excited about the dust sensor because it’s it was a component in Matt Schroyer’s DustDuino sensor (as seen on that’s being trialled in the developing world by Internews’ Earth Journalism Network… will be interesting to see what I can get out of it.

Sensors in Weather Reporting

“We all know that the weather with which the barometer sympathises, is considered to consist of three independent variables – the velocity of the wind, its temperature, and its dampness. It is a question how far the direction of the wind need be reckoned as a fourth distinct influence” – Francis Galton (first weather reporter)  [Galton1870]

A Little History

Weather predictions date back millennia, to at least 4th Century BC Babylonians, and recorded weather measurement, on which forecasts are made, date back hundreds of years, to the Central England Temperature series, which was collected by amateurs and has continued to be recorded since 1659 [Saner 2007].

first weather report

Figure 1 First Weather Report, 1875

early weather symbolsFigure 2 1861 Weather Report with Symbols

Weather reporting in the media dates back to 1875 with Francis Galton’s weather observation maps in The Times (above, with Galton’s 1861 map using symbols); radio broadcasts of weather information started in 1916 at the University of Wisconsin-Madison’s 9XM studio, with UK radio broadcasts of weather information  in 1922 (British Broadcasting Company), and commercial US radio reporting of weather forecasts in 1923 (Edward Rideout’s reports on WEEI Boston;  [Kutler 2003]). Television weather reporting started in 1941 at WNBT-TV, New York [Monmonier 2000].

The sensors and platforms used in weather reporting vary from manual reading and reporting of simple sensors in Stevenson screens, to digital instruments, weather balloons and satellite-mounted Doppler radars.  Outputs from these sensors are usually gathered by national, local or global meteorological organisations (e.g. NOAA, or the World Meteorological Organisation); these outputs and/or detailed analysis of them, including weather forecasts, are passed to media outlets for use in weather reports.

Early US television weather reports (e.g. Weather Man in the 1950s) were simple textual descriptions (e.g. “Sunny, chance of showers”) without maps.  The first use of satellites in weather reporting was in 1960, when the TIROS-1 was launched to send back cloud cover images of Earth from two television cameras (one high-resolution, one low-resolution); later (1960-1965) TIROS satellites included radiometers (measuring infrared radiation) with missions including detecting cloud cover during hurricane seasons and detecting snow cover; news stories arising from their use included the early detection of Hurricane Esther in 1961, and the first complete view of the world’s cloud cover in 1965. The camera resolution of the last TIROS satellite launched was 2 miles at the camera centre (the area covered by a camera pixel is typically larger at the camera image’s edges than at its centre), with each image covering 640,000 square miles [NASA 2013].

What’s Available Online Today

Weather reporting using satellite radar pictures and outputs from weather stations are now commonplace.  The radar spectrum has several ‘notches’ where radar waves are absorbed by water molecules, making storm clouds easier to see; weather stations give temperature, rainfall, windspeed, etc.

The availability of personal weather stations (including wifi-enabled personal weather stations) has made it much easier for weather-based communities to form.  Examples of grassroots communities dedicated to sharing local weather reports include:

As personal weather stations become increasingly automated and include more sensor types, this trend for micro-weather reporting and its potential to fill in data gaps in macro reporting in most likely to continue.


What is a Sensor?

“Sensor. Noun. A device that detects or measures a physical property and records, indicates, or otherwise responds to it.” – Google

A sensor detects physical variations in the world, e.g. light, temperature, radiowaves, sound, magnetic fields, vibration, particles (e.g. pollution, radiation) or objects (e.g. water droplets).

Humans contain Sensors

Humans and other creatures contain sensors: eyes, ears, nose, tongue, skin.  Humans are very good general-purpose sensors:

These sensors are sometimes used in sensor journalism, but so too are manmade sensors like cameras, motion detectors and thermometers.

In many situations, manmade sensors are more appropriate:  humans tend to fail the “dull, dirty, dangerous” test: their attention wanders on boring tasks, and it’s not fair to put them into dirty or dangerous situations where a manmade sensor would be more appropriate; they also can’t detect much of the physical world -e.g. radiowaves – without help, and their outputs aren’t always accurate enough for the task in hand.

Manmade Sensors are Old News

Manmade sensors convert common physical quantities (light, temperature etc) into measurements, actions or stimuli (sounds, light etc).  Manmade sensors have been designed and used for centuries, including:

Low-Tech Still Works

One area of journalism where sensors are commonly used is weather reporting.  At the low-tech end of modern weather recording is a Stevenson screen with manually-read instruments.  A Stevenson screen is a wooden box designed in 1864 to shelter a thermometer from direct weather (rain, snow, wind) and other objects (leaves, animals) that might damage the instruments inside it or bias readings from them. Stevenson screens are used for weather reporting worldwide, and contain instruments like:

Stevenson Screens are a good example of the care needed to obtain minimally-biased sensor readings.  The box and its positioning is standardized by the World Meteorological Organisation, to minimize instrument bias, e.g. all boxes are mounted 1.25m high to minimize ground temperature effects, louvred to minimize the effects of still air (e.g. overheating), and with doors opening North, to minimize reading errors from direct sunlight.

But Electronics can be Convenient

Each of the instruments above has an electronic equivalent, e.g. a sensor that can provide data remotely without a person needing to visit the Stevenson screen.  Digital sensors (sensors that convert physical quantities into electrical signals) are more recent, including digital cameras (Sasson 1975) and other sensors whose outputs can be sent to electronic storage, over wifi links or directly to computer processors.  We’ll talk more about these later.