Difference between revisions of "Crisis Mapping: RDTN.org"
(Created page with 'http://RDTN.org - ''a collective voice helping others stay informed'' Radiation info from Japan and beyond aggregated from a number of sources, displayed via map, soon to be K…') |
|||
| Line 1: | Line 1: | ||
| − | http://RDTN.org - ''a collective voice helping others stay informed'' | + | Presentation by Uncorked Studios on their project [http://RDTN.org/ RDTN.org] - ''a collective voice helping others stay informed'' |
| − | + | RDTN.org maps radiation info from Japan and beyond, aggregating data from a number of sources. Soon to be a KML feed. | |
| − | + | The site rolled out just 72 hours after the original "back of envelope" sketch. | |
| − | 1) made assumptions | + | == How it happened == |
| + | |||
| + | 1) made [[#The assumptions|assumptions]] | ||
2) built a trust network | 2) built a trust network | ||
| Line 11: | Line 13: | ||
3) launched early, iterated often | 3) launched early, iterated often | ||
| − | + | === The assumptions === | |
1) people will buy geiger counters | 1) people will buy geiger counters | ||
| Line 25: | Line 27: | ||
6) they are qualified to do this | 6) they are qualified to do this | ||
| + | The presentation stressed that many of these assumptions are, in fact, wrong. | ||
| + | But the sense of urgency created momentum that allowed the developers to overcome the faulty initial assumptions and to push on to create something of value. | ||
| + | |||
| + | Operating in crisis mode allows more quickly building a network of contacts. One of the connections led to http://pachube.com/ (pronounced "patch-bay") Pachube has a network of sensors so they became a source for data with an api allowing direct queries). | ||
| + | |||
| + | In ordinary circumstances, Pachube would have been seen as a competitor that might have derailed the whole project. ("It's been done already, let's just skip it!") In crisis mode, Pachube became a valued collaborator. | ||
| − | + | Much of the data in RDTN.org is scraped from government or commercial sources. Scraping is necessary because these agencies make data available in polished reports (eg daily PDFs or screenshots) that are easy to view but difficult to harvest as data sources. | |
| − | + | US EPA for example, has an interface for accessing the data that is relatively useless for app developers. Data.gov doesn't help either - almost makes the situation worse by raising expectations. Data.gov showcases the data on the front page, promises downloadable data, and feeds, but really all the links lead back to the same frustrating EPA interface. To be fair, the sharing of data via feeds is still in its infancy, and as one attendee commented, GIS data was in the same situation only a few years ago. | |
| − | At least one interesting example (from Germany) of a contributing source using crowd-sourcing not to contribute original data, but to transform (scrape) it out of PDFs into usable form. | + | At least one interesting example (from Germany) of a contributing source using crowd-sourcing not to contribute original data, but to transform (scrape) it out of PDFs into usable form. Volunteers read the PDF reports and re-enter data in a machine-readable format. |
| − | Return to [ | + | Return to [[Unconference_Sessions|2011 Unconference Sessions]]. |
Revision as of 12:27, 2 April 2011
Presentation by Uncorked Studios on their project RDTN.org - a collective voice helping others stay informed
RDTN.org maps radiation info from Japan and beyond, aggregating data from a number of sources. Soon to be a KML feed.
The site rolled out just 72 hours after the original "back of envelope" sketch.
How it happened
1) made assumptions
2) built a trust network
3) launched early, iterated often
The assumptions
1) people will buy geiger counters
2) people will trust us
3) radiation units are simple
4) people will understand info on site
5) no one else to solve same problem
6) they are qualified to do this
The presentation stressed that many of these assumptions are, in fact, wrong. But the sense of urgency created momentum that allowed the developers to overcome the faulty initial assumptions and to push on to create something of value.
Operating in crisis mode allows more quickly building a network of contacts. One of the connections led to http://pachube.com/ (pronounced "patch-bay") Pachube has a network of sensors so they became a source for data with an api allowing direct queries).
In ordinary circumstances, Pachube would have been seen as a competitor that might have derailed the whole project. ("It's been done already, let's just skip it!") In crisis mode, Pachube became a valued collaborator.
Much of the data in RDTN.org is scraped from government or commercial sources. Scraping is necessary because these agencies make data available in polished reports (eg daily PDFs or screenshots) that are easy to view but difficult to harvest as data sources.
US EPA for example, has an interface for accessing the data that is relatively useless for app developers. Data.gov doesn't help either - almost makes the situation worse by raising expectations. Data.gov showcases the data on the front page, promises downloadable data, and feeds, but really all the links lead back to the same frustrating EPA interface. To be fair, the sharing of data via feeds is still in its infancy, and as one attendee commented, GIS data was in the same situation only a few years ago.
At least one interesting example (from Germany) of a contributing source using crowd-sourcing not to contribute original data, but to transform (scrape) it out of PDFs into usable form. Volunteers read the PDF reports and re-enter data in a machine-readable format.
Return to 2011 Unconference Sessions.