Grassroots Mapping the Gulf Oil Spill

Hi, all – Oliver Yeh and I are down in New Orleans now trying to meet up with local organizers to begin an independent, grassroots ground-truthing/mapping of the spill.
To be clear – we’re not trying to duplicate the satellite imagery or the flyover data (though we’re helping to coordinate some of the flyovers and […]

Hi, all – Oliver Yeh and I are down in New Orleans now trying to meet up with local organizers to begin an independent, grassroots ground-truthing/mapping of the spill.

To be clear – we’re not trying to duplicate the satellite imagery or the flyover data (though we’re helping to coordinate some of the flyovers and trying to make sure the data is publicly accessible). We believe it’s possible for citizens to use balloons, kites, and other simple and inexpensive tools to produce their own documentation of the spill… and that such imagery will be essential for environmental and legal reasons in coming years.

To learn more, check out our organization page in the Grassroots Mapping wiki.

Please, if you’re involved in the response, and live near the spill, call me at 415 508 6769, email me at warren@mit.edu, and tell us where to come to help you document what’s going on!

To join in the discussion or make contact with us, the mailing list is a great place to start.

1 thought on “Grassroots Mapping the Gulf Oil Spill”

  1. I wish you good travels and hope all of your data is gathered and used in a truthful manner. Meaning, if there is a heavy impact in an area you observe by all means report and share with everyone to help with cleanup. At the same time if you find that the impact is much less than expected or nonexistent share that. This is a very different scenario compared to the incident with the Valdez. Good Luck

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax