The document discusses the process of geocoding and managing addresses related to the Bastrop Complex fire damage using Fusion Tables and ArcMap. It highlights challenges faced, such as dealing with bad addresses and limitations in mapping, while also sharing technical resources and potential improvements for future efforts. Additionally, it emphasizes the use of Excel formulas and tools for better data management and presentation.

1. Deconstructing aFusion Tables mapBastrop Complex Fire Damaged Structures

2. Our AgendaWalk through processChallenges facedHow can we do it easier?What can we do better?

3. Getting the addresses

4. Cleaning up addressesMy goal was to Geocode in ArcMap (why later)Lots to learn about Excel formulas=RIGHT(A5,LEN(A5)-SEARCH(" ",A5,1))=LEFT(B5,SEARCH("SMITHVILLE",B5)-2)=RIGHT(B5,16)=LEFT(D5,SEARCH(" ",D5)-1)=RIGHT(D5,5)

5. Geocoding in ArcMap

6. Shpescape.com is awesome

7. Fusion Table styling

8. Layering Fusion Tables

9. Just publish it

10. Addresses alone were not enoughA new full list each dayRecoding bad addressesNo diff toolSome addresses don’t map5-layer max for FTExcel formulas are great, but hurt my headChallenges faced

11. What’s a good diff tool?Cheat sheets for Excel formulas?Regex?ArcMap alternatives/Geocoding tools?How can we do it easier?

12. What can we do better (or next)?Before & after?Insurance claims?FEMA data?Rebuild list?Census profile (yes!)

13. Google Fusion Tableshttp://www.google.com/fusiontables/Fusion table exampleshttps://sites.google.com/site/fusiontablestalks/storiesShape to Fusionhttp://shpescape.com/FusionTablesLayer Builderhttp://gmaps-samples.googlecode.com/svn/trunk/fusiontables/fusiontableslayer_builder.htmlTechnicalbent.com | @crit| cmcdonald@statesman.comLinks