1. Towards the Open Geospatial Web –Chris Holmes

2. “Architectures of Participation” – Coined by Tim O’Reilly

4. An “Architecture of Participation” is both social and technical, leveraging the skills and energy of users as much as possible to cooperate in building something bigger than any single person or organization could alone.

5. Architectures of Participation Software: The first domain to see benefits The process can be applied to other fields

6. Geospatial Data Creation Sharing

7. Primary Goal “…the sources, systems, network linkages, standards, and institutional issues involved in delivering spatially- related data from many different sources to the widest possible group of potential users at affordable costs.” Geo Data Sharing… – Groot & McLaughlin 2000

8. The Success of SDIs?

9. Compelling Initiative User at the Center User Responsibility No Barriers or Difficulty Factors for Success

10. Contribute to Compelling Initiative. Mandated law != useful Few real users No recognition No reward for the effort Try again in five years? vs.

11. Quickly add data to quality map Ease of customization Recognition: Shared, emailed, blogged about… Indexed & Searchable Contribute to Compelling Initiative

12. Consumers ≠ Producers Data from “official” sources Metadata takes training GIS Professionals Only Users as Contributors

13. Maps Consumers = Producers Everyone encouraged to contribute Community members grow in to experts Even used for ‘real GIS’ …it’s easier than getting on an SDI

14. SDI Contributing: Data

15. Hardware

16. Software

17. Metadata

18. Metadata Training

19. A Catalog to Register On

20. Contributing Data to Google…

22. Barriers to Entry… Browser Metadata Training Server Hardware WMS Software Sharing Agreements Catalog Registration

23. Does user contribution alone make an SDI?

24. Let commercial players run SDI? SDI’s are a public good Commercial players have profit motive Commercial players seek monopoly DANGER: Governments are handing over data without opening it to anyone else!

25. Towards the Open Geo Web Inclusive Infrastructure Single “Geo Web” Project Unlimited Potential Build on existing Architectures of Participation

26. Principles: Towards the Open Geo Web Not just policies, requirements & mandates Align incentives to create a single Geospatial Web

27. Geospatial Data Creation Sharing

28. OpenStreetMap Geo Data Creation: Is already here… MapShare™

29. OSM Maps

30. OSM

31. …Though far from mature Licensing is a big problem Tools are unsophisticated Few different workflow options But huge potential has been proven

32. Towards Maturity: Workflow vs

33. Towards Maturity: Scope vs

34. Towards Maturity: Tools Compatibility with GIS tools Advanced workflow management Sandboxes, approval before acceptance Automatic validation (topology, required fields) Branches and merging with Conflict Resolution Automatic change notification email / rss Automatic feature extraction: GPS tracks and Satellite images

35. Towards Maturity: Licensing For Geodata?

36. Towards Maturity: Cooperation Align efforts so that amateur, commercial, NGO and governmental creators all naturally collaborate Figure out workflows, tools and licenses that work for everyone Put NMCAs at the center, incentivizing updates to core layers (from citizens and companies) Towards living data, constantly evolving - authoritative and always up to date

37. Towards Maturity: The role of the NMCA Natural leader, the most experience capturing and maintaining the highest quality data Must build upon success of accurate and official maps with latest techniques to improve with participation Look to derive revenue from services around the data Use Open Source Business models as examples

38. Learning from Open Source Business Hosted Services Geocoding Route finding Custom Tiles Hosting additional layers, etc. Guarantee of accuracy Value add packaging - formats, documentation, software Subscription to latest updates

39. Build on other Architectures of Participation Don’t go it alone MapShare™ Align their success with yours

40. Beyond Portals Web Portals went out of fashion in 2001 ‘GeoWeb Node’ = GeoPortal 2.0 GeoPortal goal: find existing data GeoWeb Node goal: increase creation and sharing of data End goal of both is easier to find and use data

41. No more Aquariums!

42. Join the Web!

43. A Geo Web Node Building SDI’s from the bottom up

44. GeoWeb Node: Rooted in Data Access PostGIS Oracle Spatial DB2 ArcSDE MySQL

45. GeoWeb Node: Spreading to the Geo Web Google Earth Virtual Earth Google Maps NASA WorldWind Yahoo! Maps

46. GeoWeb Node: Integrated Viewer

47. GeoWeb Node: Online Styling

48. GeoWeb Node: Easy upload Choose FileGeofile.shp Upload

49. GeoWeb Node: Searchable by Google

50. GeoWeb Node: Editing

51. GeoWeb Node: Versioning and advanced workflow

52. GeoWeb Node: User accounts User statistics Comments, ratings, tags Collaborative Filtering Rankings of best ‘views’ and data sets contributed Highest rated, most viewed, most shared

53. GeoWeb Node: Metadata Derive from user actions Don’t require metadata to put out data Wiki type editing of metadata Automatically available with the Catalog standards

54. GeoWeb Node: The bottom up SDI Traditional SDI start with metadata Metadata -> Users -> Data GeoWebNodes start with data Data -> Users -> Metadata Built like the web, once there is enough valuable data available others will come along to help solve the harder search problems

55. Where to put these nodes? Everywhere! Anywhere you might put a portal Anywhere you have an ‘Enterprise GIS System’ Anywhere people share data with each other Handling all these use cases will evolve GeoWeb nodes to be truly useful

56. Open vs Closed Geo Data Most important thing is that data is accessible in all standard formats But the Geo Web will be built on Open Data Google has proven this An open base will lead to more contributions on top

57. Official vs. User-contributed Data One Infrastructure Limited User Permissions Optional Commenting & Rating

58. A National GeoWeb Node Provide a user friendly fully hosted infrastructure for sharing data. Easy for anyone to create maps: add data, style existing maps, mash-up diverse sources, edit other's data, export results out Free for small and government users, cost recovery for larger uses Resulting maps available as WMS, WFS, Catalog, on Google Earth

59. Spreading the GeoWeb Nodes Build the national on Open Source Software Allow anyone to use the same package Local levels may improve software in other ways that national node can use Encourage internal use, make it the easiest way to create and share data Sync nodes up and down for increased performance Result is a true information infrastructure

60. Building the GeoWeb Node The OpenGeo Suite

61. OpenGe o Enterprise Don’t have to go it alone

62. The future is users Geo Participation GIS Professionals Amateur Neo Geographers Anyone with a locative device Technology & Community The Future: Beyond Portals

63. My GeoWeb Goal Let’s build a Geo Web that’s so compelling and easy-to-use that everyone: Citizens, Governments, NGO’s and Companies all naturally collaborate towards the same infrastructure for public good.

64. What you can do: Go beyond portals, build National Geo Web Nodes with free hosting for open contributors Try opening data in open source / share alike and/or non-commercial ways, align incentives back Look for new business further up the value chain, just selling data may not last Partner with companies who are correcting data and moving up the value chain, don’t go it alone Experiment with participation, both internally and externally

65. Learn more… www.geoserver.org www.opengeo.org www.cholmes.wordpress.com This work is licensed under a Creative Commons Share Alike Attribution License. Please attribute Chris Holmes, and keep the OpenGeo.org logo on all slides, unless alternate permission is given. Contact cholmes@opengeo.org for more informationcholmes@opengeo.org