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.

1. One Man’s Opinion Ahead

2. Five MYTHSABOUT GISIN 2011

3. #1 THEDESKTOP IS DEAD!

4. Weallknowthe partyline

5. Web Apps Are Cool

6. Desktop Apps Are Not

7. Web Maps Are Cool

8. Desktop Maps Are Not

9. Return?

10. Mid-‘90stoMid-’00s

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

17. Enter theREST API

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

22. ArcGIS ServerServicesStartOn theDesktop

23. “90%”- Kate ChapmanGeoIQ “100%”- James FeeWeoGeo

24. GeoCatBridge GeoCommonsArcGISToolbar WeoGeoToolsforArcGIS

25. Why?

26. Because no one wants to be that kid

27. The “GeoWeb” can’t exist without the “GeoDesktop”

28. #2 MAPS ARE THE TRUE POWER OF GIS!

29. Maps can be a lot of things…

30. Informative By Esri Disaster Response

31. Beautiful By Bill F. Greer

32. Unusual By Bill Dollins

33. Maps have been aroundlonger than GIS http://ny-image1.etsy.com/il_fullxfull.228972589.jpg

34. Spatial processing adds power

35. 1:11:MM:M

36. http://portal.opengeospatial.org/files/?artifact_id=30402

37. Use background spatial processing

38. Visualize spatial outputs appropriately

39. Update Query Export Joins ‘Export’ STREAMLINE.ZIP9_POINTS Required Fields PREF_CITY_STATE_NAME_LAST_LINE ZIPCODE field ZIP4HIGH ARC_ZIP4 Table Join Step1 Required Fields ZIPCODE field ZIP4HIGH ARC_ZIP4 CITY_NME CITY_FIP City Required Fields PREF_CITY_STATE_NAME_LAST_LINE CITY_NME File name DHS_EDW_AREA_GIS_EXTRACT * CITY Required Fields CITY_FIP CITY_NME Update_FIELDS Required Fields CITY_NME = Helena – CITY_FIP= 31180 CITY_NME = West Helena – CITY_FIP = 74450 CITY_NME – Little Rock Airforce Base – CITY_FIP = 41000 STAT_FIP = 05 STATE_NM = Arkansas ALL_FIELDS Required Fields CITY_FIP CITY_NME COUNTFIP COUNT_NM FEDHREPN SCHDISNU SCHDISNM STHREPNU STSENNUM STAT_FIP STATE_NM STCOCFIP ZIPCODE ZIP4HIGH ARC_ZIP4 X Y RECRTDTE * COUNTY Required Fields COUNTFIP COUNT_NM Remove Duplicate Values in ZIP_ZIP4 field Spatial Join * FED_HOUSEDISTRICTS Required Fields FEDHREPN City Component Required Fields ZIPCODE field ZIP4HIGH ARC_ZIP4 CITY_NME CITY_FIP Step2 Required Fields CITY_FIP CITY_NME COUNTFIP COUNT_NM FEDHREPN SCHDISNU SCHDISNM STHREPNU STSENNUM ZIPCODE ZIP4HIGH ARC_ZIP4 * PUBLIC_SCHOOL_DISTRICTS Required Fields SCHDISNU SCHDISNM * ST_HOUSEDISTRICTS Required Fields STHREPNU Add_FIELDS Required Fields STCOCFIP X Y RECRTDTE * ST_SENATEDISTRICTS Required Fields STSENNUM * Asterisks indicates layers that need to be verified and exported to model as changes occur Spatially-Enabled ETL Arkansas GIO

40. What’sadevelopertodo?

41. Spatial SQL

42. ArcObjects (!?) http://images.spatiallyadjusted.com/killing-arcobjects_001.jpg

43. #3 GIS IS DISRUPTING THE WEB!

44. Location is Everywhere

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. #4 Code-Free GIS!

54. The “Do All” Button

55. What are you talking about? 1990s 2000s 2010s?

56. #5 THIS ISN’T GIS!

57. Cloud #GeoAgnostic #NoGIS Android ArcGIS Web #Paleo Desktop REST #NeoGeo iOS SOAP #GIS #WMSisDead FOSS4G WP7 #OSM

58. Walls suck!

59. It’s All Good

60. Communities Work

61. Bill Dollins bill@zekiah.com Twitter: @billdollins Zekiah Technologies www.zekiah.com Thank You!