What I want to do
I want to have a discussion about how we might embed Riffle data in MapKnitter as map annotations.
I think that the goal here is to enable users to upload data directly from Riffle sensors and have that data displayed on or beside the map in a way that will substantively augment the information payload of the map.
What I've done
I looked around the Public Lab website and found some research notes that discuss or use Riffle data. In particular:
There's a lot of data here. I don't think it's feasible or even desirable to want to present the data set to the users in raw form, or even to try to visualize all of the data. I think it would be nice if we could create templates that automatically visualized one or two key parameters from the data.
The workflow / processsing pipeline that I envision is:
- User uploads Riffle data set (the data set above is in
- Built-in templates display Riffle directly on the map - no "embedded" charts or graphs - using d3 and Leaflet.
- A link to the data set is added to the sidebar so that viewers can click through and see the full, raw dataset.
Next Steps / Additional Questions
The key question is: What default templates should we provide for visualizing the Riffle data? @mathew? @WalkerJeffD? @donblair? @warren? Let's start with a single data visualization. What is the data that will be most helpful to the most number of people? (I'm thinking maybe temperature plotted against location, as @WalkerJeffD has done here).
How flexible / extensible should this system be? Is it desirable to allow users to create their own custom visualizations using their own d3 and Leaflet code, or should we assume that users who are savvy enough to use d3 and Leaflet are savvy enough to do that kind of analysis on their own and publish it to GitHub, etc.
How much should users be able to customize the way that the data is displayed?