April 30 & May 1, 2010 Storms

1,147 views
1,090 views

Published on

This was a test of the utility of Twitter during a couple of weather events. The test was performed by the Arkansas Geographic Information Office. The kml can be downloaded from http://bit.ly/bKzf5T

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,147
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

April 30 & May 1, 2010 Storms

  1. 1. Apologies for the use of text in this slide show. <br /> This was slide deck is intended to provide the findings of a Tweet test performed by the Arkansas Geographic Information Office.<br />1<br />
  2. 2. This was Just a Test<br />Prepared by: <br />Arkansas Geographic Information Office<br />www.gis.arkansas.gov<br />2<br />All pictures shown; tweeted with #Arwx<br />A KMZ can be downloaded from <br />http://bit.ly/bKzf5T<br />Still working on date/time format<br />
  3. 3. #ARwx Tweet TestApril 23-26, 2010April 29 – May 3, 2010<br />Prepared by: <br />Arkansas Geographic Information Office<br />www.gis.arkansas.gov<br />3<br />All pictures shown; tweeted with #Arwx<br />A KMZ can be downloaded from <br />http://bit.ly/bKzf5T<br />Still working on date/time format<br />
  4. 4. There is a geographic component to Tweets<br />4<br />All tweets were not located properly during this test<br />
  5. 5. There is a geographic component to Tweets<br />5<br />Location is a significant component<br />
  6. 6. Purpose of Test<br />Determine twitter use for an event<br />Determine acceptance of a hashtag<br />Determine acceptance of geoenabled tweets<br />Figure out if this is useful<br />http://www.srh.noaa.gov/lzk/?n=svr0410a.htm<br />6<br />
  7. 7. 7<br />
  8. 8. Results April 23-26, 2010<br />Safe Software Twitter Workbench worked properly<br />Data was captured and stored in a database<br />Data can be viewed in GoogleEarth<br />Tweets<br />32 unique users<br />10 geotagged (lat/long)<br />77 profile was used to locate<br />9 could not be located<br />96 total number of tweets during this event<br />8<br />
  9. 9. Results April 23-26, 2010<br />Safe Software Twitter Workbench worked properly<br />Data was captured and stored in a database<br />Data can be viewed in GoogleEarth<br />Tweets<br />32 unique users<br />10 geotagged (lat/long)<br />77 profile was used to locate<br />9 could not be located<br />96 total number of tweets during this event<br />Yeah!!!<br />Nota ‘significant’ Event<br />9<br />
  10. 10. Information Captured<br />Date / Time Created<br />Tweet ID<br />Tweet Text<br />Tweet User<br />Tweet User Profile Image<br />Location (lat-long / profile)<br />Search Text = #arwx<br />Geometry<br />10<br />
  11. 11. Results April 30-May 3, 2010<br />Safe Software Twitter Workbench- Failed*<br />A number of tweets were not captured <br />Issues identified:<br /> Number of Twitter API calls per hour<br />Configuration of scripts<br />Each of these are being addressed for next test<br />An export from Twapper allowed analysis<br />Captured Tweets<br />Georefrenced using profiles captured from failed test<br />Manually inserted several based on profile description<br />Exported to KML<br />11<br />*Failure of the workbench was due to implementation; not the Safe Software product<br />
  12. 12. Results April 30-May 3, 2010<br />Tweets<br />219 unique users<br />19 geotagged (lat/long)<br />1,425 profile was used to locate<br />135 could not be located<br />1,579 total number of tweets during this event<br />Users<br />Most tweets by a single user 100<br />User retweeted the most 108 (@wxmandan – LR NWS)<br />12<br />
  13. 13. Process Used to Generate KML<br />Exported #ARwx from Twapper<br />Performed table join based on userid to the data captured from the failed test<br /> Inserted location to a number of tweets from Twapper<br />Removed duplicates<br />Attempted to adjust date and time to CST<br />Ran Safe Software workbench to generate a kml<br />13<br />
  14. 14. General ObservationsApril 30 – May 3, 2010<br />14<br />
  15. 15. General ObservationsApril 30 – May 3, 2010<br />15<br />
  16. 16. General ObservationsApril 30 – May 3, 2010<br />16<br />
  17. 17. General ObservationsApril 30 – May 3, 2010<br />17<br />Event was primarily southeast of this area. Twitter activity corresponds.<br />
  18. 18. General ObservationsApril 30 – May 3, 2010<br />18<br />Tweets increased as event unfolded and decreased as threat subsided.<br />
  19. 19. General ObservationsApril 30 – May 3, 2010<br />19<br />That’s just cool.<br />
  20. 20. General Test Observations<br />Determine twitter use for an event<br />Twitter proved useful for communicating the events as they unfolded. Tweets provided on the ground information and pictures.<br />Determine acceptance of a hashtag<br />The hashtag was generally accepted, but took roughly 18 hours for uptake <br />Determine acceptance of geoenabled tweets<br />The majority of tweets were not geotagged. Several profiles did not allow for any location information to be identified.<br />Figure out if this is useful<br />No doubt twitter is useful for communicating events. The next step will be evaluating protocols needed for real-time analysis and bi-directional communication<br />20<br />
  21. 21. The power of location<br />Why test the use?<br />21<br />
  22. 22. County Boundaries<br />22<br />
  23. 23. Earthquake Intensity<br />23<br />
  24. 24. Roads<br />24<br />
  25. 25. Bridges<br />25<br />
  26. 26. Bridges<br />For Example:<br />Crowd source damage<br />assessments following an <br />earthquake<br />26<br />
  27. 27. Considerations<br />Network<br />Assumes network access<br />Assumes Twitter (in this case) is available<br />Education<br /> Enabling geotagging<br />Acceptance<br />Geotagging<br /> Ability to provide reports<br />Mapability<br /> API works properly<br /> API provides useful information <br />Usability<br />Filtering the noise<br />Can the appropriate protocols be put in place to make this a useful tool for hearing those that ‘call for help’ or submit ‘field reports’?<br /> The handling of date/time stamps<br />27<br />
  28. 28. Summary<br /> The recent events have provided us with good information to use in our test. We will continue to analyze the information and determine how the power of the technology might be further used in future events.<br />28<br />
  29. 29. 29<br />Learon.Dalby@arkansas.gov<br />Twitter: @learondalby<br />http://www.slideshare.net/learondalby<br />Special Thanks to @Kirrilian for technical work<br />

×