Welcomer Aurelia Moser (@auremoser) to our Map of the Week series. She is a developer for [Knight Mozilla Open News] in Brooklyn, NY. She has worked on projects for Ushahidi and Internews Kenya, building interactive visualizations to support data journalism and crisis mapping globally. Find her at algorhyth.ms, and listen in for her radio show based on the semantic web at Stereo Semantics.
There’s a part of Paul Ford’s talk 10 Timeframes, where he goes over the various incrementations we apply to our daily lives and how our understanding of time with the advent of computers has become progressively more infintessimal, down now to the nanosecond. Eventually, he settles on the “heartbeat” as the most genuine temporal segment, selected for its consistency in tenor-ing time, and for its humanity.
Often when we build digital things, I think we emphasize the mechanics of them over the human expressive potential they enable. There’s a humanism to making maps, human-designed guides for global navigation, and sometimes I get the opportunity to plot data to a map like the thumpthump of a heartbeat on our planet; somehow feebily expressive of the natural breath and health of our globe as it grows. I work for a tech company that builds open source tools to crowdsource mapping accross the planet; we’re called Ushahidi, a word that means “witness”” in Swahili. Occasionally, we dabble in plugging sensor data into deployments of our self-titled mapping platform.
The resulting projections are a kind of crowdsourcing, like the reports and UGC we generally port to populate our maps, but with sensor data, you get an objective read on the natural wealth and environmental health of a place, from weather gauging, to temperature and chemical readings to seismic conditions that fuse in a larger planetary pulse. Vital Signs is an NGO whose objective is to do just that: read the pulse of east African argriculture and sustainability in sensor data collected across Tanzania, and this blog post is about a map we built for their team to help monitor that water gauging stations in the SAGCOT district of TZA.
Vital Signs has been collecting water gauging information with sensors embedded in over 170 stations throughout SAGCOT (Southern Agricultural Growth Corridor) region of Tanzania for decades. They’ve been analyzing these data sets and readings for anomolies that can contribute to the corpus of information they have about agricultural health in portions of Tanzania. Of late, we’ve been partnering with them to develop a dashboard or larger platform that can aggregate and make sense of the mass of data they’ve assembled, and this project was a pilot to prototype that effort for water data.
VS measures water security and quality via water flow rate [dmf], temperature, rainfall level, waterlevel data, and this usually takes the form of text files with a collection date and a sensor reading. The data can be pretty variable and messy, and in some cases the sensors have been taking daily readings for more than 40 years, so contextual analsis of those data can be tough. This Water Availability visualization was meant to apply data to geo-locations for the sensor stations and assess their coverage and concentration of study moving forward.
My task was to build something that would map those station locations with some other relevant geo-context like river locations, the boundaries of the SAGCOT region, and collection clusters, all of which figure as visible layer toggles in the resulting map.
To compliment the map, we had a corpus of station-level datasets as .txt files and our goal was to connect them to the actual locations of the gauging stations. Much of the work went into connecting those data sets to the plotted points and enabling a “pop-up” graph or pair of graphs to render, filter, and scroll above the page fold.
Processing the data required both a scrub of the raw data sets and some scripting to coordinate the map and the data graphs.
Like a lot of public data, the raw data sets were variable in format and content due to the range of manual and automagic collection practices for the past 40+ years of data assemblage.
For the pre-visualization data processing, I wrote something that could shape the data for consistent rendering. This needed to be a process that might be potentially repeatable since we created this preliminary visualization as a pilot with only a portion of the datasets collected. Presumably, the incoming (new) data would also need to be standardized to suit our current schema, so fix-csv.js is a node script that runs through the raw station files datasets in this directory, cleans them of inconsistent dates and null reading values, and maps them to a unique station ID that can then match the rendered stations on the Carto map.
Part of the complication in building the map to match the datasets, is that each station was equipped with multiple sensors, so we had multiple collected data files for certain stations; this script also groups partner data sets to that same station ID, outputing them as mapping.json and enabling multi-data set graph-render on-click.
Full Script here:
For the visualization, Vital Signs wanted to be to view both the location of the stations, their associated data types, and then peruse the actual data collected at those points. To this end, waterdata.js sets all of the parameters for the chart rendering using Highstock, a library affiliated with HighCharts but with a much faster render-time presumably because it’s built to accommodate financial data. The mapping portion of the code is pretty abbreviated thanks to much of the automagic that Carto affords, but you can find all those details in main.js.
Styling was based on the existing Vital Signs design guide, favoring yellows, greens and Helvetica. To unify the overall UI, I appended the carto default legend (which coded the points as with or without data) to a #key div along with the “visible layers” dropdown and some general definitions of the domain-specific acronyms in the charts. I set the lat/log center and zoom to focus pretty tightly on the region of interest in Tanzania and made the map the main page feature on load to enable some initial exploration of the terrain before diving into the data.
Most of the interaction for the app is explained in the respository readme along with screenshots if you want to delve.
In brief, the visualization lets you view station information and toggle between geo layers as well line graphs for datasets affliated with those stations.
Since most posters are SQL supermen, I’m embarrassed to say on this blog that I didn’t run any fancy SQL to make this work. There’s a column in my gauging station data set where I log the data sets associated with station locations, and at some point I SELECT from WHERE’d in Carto to sort the locations by the types of data they had, and created a binary column that would prioritize those stations that had data, eventually color the points according to this TRUE/FALSE. This was mostly an aesthetic move, since many of the stations did not have data for the proof of concept version of this map, so there needed to be some visual indication of which stations would render a chart on-click (hint: the dark blue ones) and which ones were as-yet “empty” (light blue).
For now, the visualization iframes into a Vital Signs site designed to audit their data processing and plan for future visualizations. As a pilot that took about one week to prototype and a few more days to tweek, it’s a pretty-o.k. rendering of the sensor pulse in a portion of the TZA water landscape. Limited training was necessary to communicate the UI and utility of the app to the Vital Signs team, and that was the goal. With more thought, maybe a custom D3 visualization or graph might be worthwhile, something that illustrates what water level means and not just the numerical value of a gauging reading.
When I make stuff, I think a lot, and rather dramatically, about the Paul Ford’s thoughts in 10 Timeframes:
If we are going to ask people, in the form of our products, in the form of the things we make, to spend their heartbeats—if we are going to ask them to spend their heartbeats on us, on our ideas, how can we be sure, far more sure than we are now, that they spend those heartbeats wisely?
And think about how I can make something that gives data some kind of kinetics or interactive pulse, without wasting anyone’s heartbeats. And with this, I had the chance to do that :).
If you’re a Spatial Data Scientist there’s probably one operation type you’ll be performing all the time; maybe more than anything else. The Spatial Join. Spatial Joins are...Data Processing
Please fill out the below form and we'll be in touch real soon.