Five Myths About GIS in 2011 (Bill Dollins)
•
0 likes•563 views
1. The desktop is not dead for GIS work. While web apps are popular, the desktop remains important for starting GIS projects and performing complex spatial analysis. Desktop GIS work can then be shared to web apps. 2. Maps are a powerful part of GIS but spatial analysis and processing adds even more utility. Background tasks like joins, exports, and analysis can be done and results visualized through maps. 3. While the web has disrupted some areas, GIS is also disrupting the web by bringing location and spatial analysis to more web services and applications. Standards like REST and JSON have helped GIS integrate with the web.
Report
Share
Five Myths About GIS in 2011 (Bill Dollins)
- 1. One Man’s Opinion Ahead
- 5. Web Apps Are Cool
- 6. Desktop Apps Are Not
- 7. Web Maps Are Cool
- 8. Desktop Maps Are Not
- 9. Return?
- 11. We Know Where That Got Us
- 12. But then a shift…
- 13. 8 GB RAM(~4,194,304x)250 GB Storage(~8,192,000x)3.06 GHz(~2988x)
- 14. GIS Is “Heavy”
- 15. A casein point:the EsriWeb ADF
- 16. Out of the Box:1 MBRound Trip
- 18. Andits Clients
- 19. Sharing the load
- 20. The desktop is alive and well and living in your browser
- 21. Desktop GIS is the Onramp for Web Mapping
- 23. “90%”- Kate ChapmanGeoIQ“100%”- James FeeWeoGeo
- 25. Why?
- 26. Because no one wants to be that kid
- 27. The “GeoWeb” can’t exist without the “GeoDesktop”
- 28. #2MAPS ARE THETRUE POWEROF GIS!
- 29. Maps can be a lot of things…
- 30. InformativeBy Esri Disaster Response
- 31. BeautifulBy Bill F. Greer
- 33. Maps have been aroundlonger than GIShttp://ny-image1.etsy.com/il_fullxfull.228972589.jpg
- 34. Spatial processing adds power
- 35. 1:11:MM:M
- 37. Use background spatial processing
- 38. Visualize spatial outputs appropriately
- 39. Update QueryExportJoins‘Export’STREAMLINE.ZIP9_POINTSRequired FieldsPREF_CITY_STATE_NAME_LAST_LINEZIPCODE fieldZIP4HIGH ARC_ZIP4Table JoinStep1Required FieldsZIPCODE field ZIP4HIGH ARC_ZIP4CITY_NMECITY_FIPCityRequired FieldsPREF_CITY_STATE_NAME_LAST_LINECITY_NMEFile nameDHS_EDW_AREA_GIS_EXTRACT* CITYRequired FieldsCITY_FIPCITY_NMEUpdate_FIELDSRequired FieldsCITY_NME = Helena – CITY_FIP= 31180CITY_NME = West Helena – CITY_FIP = 74450CITY_NME – Little Rock Airforce Base – CITY_FIP = 41000STAT_FIP = 05STATE_NM = ArkansasALL_FIELDSRequired FieldsCITY_FIPCITY_NMECOUNTFIPCOUNT_NMFEDHREPNSCHDISNUSCHDISNMSTHREPNUSTSENNUMSTAT_FIPSTATE_NMSTCOCFIPZIPCODEZIP4HIGH ARC_ZIP4XYRECRTDTE* COUNTYRequired FieldsCOUNTFIPCOUNT_NMRemove Duplicate Values inZIP_ZIP4 fieldSpatial Join* FED_HOUSEDISTRICTSRequired FieldsFEDHREPNCity ComponentRequired FieldsZIPCODE field ZIP4HIGH ARC_ZIP4CITY_NMECITY_FIPStep2Required FieldsCITY_FIPCITY_NMECOUNTFIPCOUNT_NMFEDHREPNSCHDISNUSCHDISNMSTHREPNUSTSENNUMZIPCODEZIP4HIGH ARC_ZIP4* PUBLIC_SCHOOL_DISTRICTSRequired FieldsSCHDISNUSCHDISNM* ST_HOUSEDISTRICTSRequired FieldsSTHREPNUAdd_FIELDSRequired FieldsSTCOCFIPXYRECRTDTE* ST_SENATEDISTRICTSRequired FieldsSTSENNUM* Asterisks indicates layers that need to be verified and exported to model as changes occurSpatially-Enabled ETLArkansas GIO
- 41. Spatial SQL
- 43. #3GIS IS DISRUPTING THE WEB!
- 45. The Web Loves Location
- 46. The Web and GIS? Not So Much…
- 47. Map Tiles (and Web Mercator)Maptiler.org
- 48. REST
- 49. JSON
- 51. The Web Has Disrupted GIS
- 52. Spatial processing adds power
- 53. #4Code-Free GIS!
- 54. The “Do All” Button
- 55. What are you talking about?1990s2000s2010s?
- 57. Cloud#GeoAgnostic#NoGISAndroidArcGISWeb#PaleoDesktopREST#NeoGeoiOSSOAP#GIS#WMSisDeadFOSS4GWP7#OSM
- 58. Walls suck!
- 59. It’s All Good
- 60. Communities Work
- 61. Bill Dollinsbill@zekiah.comTwitter: @billdollinsZekiah Technologies www.zekiah.comThank You!