The Future of GIS

Talk given to SRP

Transcript

1. Where Next? The Future of GIS james fee Weogeo.com
2. GIS is…
3. everywhere!
4. Most of us…
6. but GIS is…
7. difficult to use
8. Where we are today? Proprietary Systems ESRI, MapInfo, Autodesk, Oracle Spatial Open Source MapServer, PostGIS, GDAL/OGR, OpenLayers, QGIS Service Based GIS Google Maps API, Microsoft Virtual Earth, OpenStreetMap
9. Proprietary Systems ESRI ArcGIS Desktop (ArcView, ArcInfo) ArcGIS Server (ArcIMS, ArcSDE) ArcGIS Online (Services)
10. Open Source Web Mapping MapServer GeoServer MapGuide Open Source OpenLayers PostGIS Desktop Applications GRASS GIS OSSIM Quantum GIS (QGIS) gvSIG uDig Geospatial Libraries FDO GDAL/OGR GEOS GeoTools MetaCRS
11. Service Based GIS
12. Web APIs
13. Stacks Microsoft Server 2008 Microsoft SQL Server 2008 Microsoft SharePoint Microsoft Exchange Microsoft Windows Linux Server Apache MySQL or PostgeSQL Perl, PHP or Python Linux Desktop
14. GIS Stacks ArcSDE (Geodatabase) ArcGIS Server ArcGIS Web Service APIs ArcGIS Explorer ArcGIS Desktop Linux PostgreSQL w/ PostGIS MapServer or GeoServer OpenLayers QGIS or uDig STOVEPIPE
15. ArcGIS Server ArcSDE (Geodatabase) PostgreSQL w/ PostGIS Mixing Stacks Microsoft Server 2008 Open architectures, combined with an dual vendor strategy keeps options (both technical and budgetary) open. Google Earth Google Maps Microsoft VE ArcGIS Desktop OpenLayers Microsoft Windows
16. Neogeography Crowdsourcing Databases Interoperability OGC
17. Mixing Silos Neogeography Geographical techniques and tools used for personal activities or for utilization by a non-expert group of users; not formal or analytical. Andrew Turner
19. VGI Volunteered Geographic Information Michael Goodchild @USCB
22. Crowdsourcing
25. Interoperability
26. The ability to use, manage and share spatial data…. which eliminates barriers for data sharing
27. •  Efficiently extract spatial data from a desired datastore •  Transform it into the requested format and data model •  Load it into a target system and present it to end users
28. Spatial ETL E T L xtract oad ransform
29. Databases
30. What Database? Proprietary Systems Oracle, Microsoft SQL Server, IBM DB2 Open Source PostgreSQL, MySQL, SQLite Service Based Google BigTable, Amazon SimpleDB, Microsoft SQL Server Web Edition
31. SQLite Open source Supports standard WKT and WKB formats OGC Simple Features for SQL SQLite database is simply a file SpatiaLite:
32. Open Geospatial Consortium •  Standards Organization •  Responsible for OpenGIS Standards •  WMS, WFS, KML, GML, WCS, …
33. xml-based (GML) 3D city models web services using WFS
34. CityGML
36. Where are we headed?
37. Pay As You Go GIS Pay for what you use Pick and choose the best solutions Enable ArcInfo for ArcView users
38. Cloud-based Services Google Data APIs Amazon Web Services Microsoft Azure Google App Engine
39. Server Appliances
40. Sharing of data
41. GIS Developement
42. Old and Busted
43. New Hotness
44. New GIS Frameworks
45. JavaScript APIs
46. Flex and Silverlight APIs
47. .NET and Java ADFs
48. Ruby and Python
49. Model Builders
50. Using Open Source with ESRI
52. OpenLayers and ESRI •  JavaScript Library •  No server-side dependencies •  Free Software, developed for and by the Open Source software community
53. OpenLayers Basics
54. Example: Identify •  Instantiate Layers to Map Canvas
55. Example: Identify •  Create Identify Task
56. Example: Identify •  Create Identify Callback
57. Code http://www.mkgeomatics.com/apps/REST_Dev/
58. PostgreSQL and ArcSDE
59. ESRI Servers with Linux •  Support for RedHat Enterprise and SUSE •  Data cannot be stored as Personal Geodatabase •  All web based management (can remotely manage via ArcCatalog on Windows) •  64-bit support (ArcSDE)
60. Open Standards
61. The Decision Makers
62. Problem: How to get information to decision makers?
63. Question: “How many sites do I have near the pipeline?”
64. Really means…
65. “How many project sites greater than 500 acres with utility service within 2500 feet of paved roads and with an average slope less than 10% within 1 mile of the ‘transcon1’ pipeline?”
66. GIS dude…
67. Decision maker?
69. NOW!
70. How do we solve this?
71. Fewer Layers…
72. Provide Feedback…
73. Make it Fast…
75. Take Little Bites
77. Hold their hands!
78. Protect users from themselves
79. Release Early! …and often!
80. Listen to feedback
82. Summary:
83. expectations: changed
84. thinkers: needed
85. design: workflows
86. focus: usability
87. performance: critical
88. details: hidden
89. James Fee jfee@weogeo.com Twitter: @cageyjames