1. Geospatial Collaboration Chris Holmes OpenGeo

2. Agenda Background GeoNode TsuDAT/Risiko USGS NHD Editing and Versioning

3. 04/26/10

4. Spatial Data Infrastructure (SDI)

5. “[Spatial Data Infrastructure] provides a basis for spatial data discovery, evaluation, and application for users and providers within all levels of government, the commercial sector, the non-profit sector, academia and by citizens in general.” – SDI Cookbook Spatial Data Infrastructure (SDI)

6. The theory of SDI developed before we learned what was possible with the Internet

7. ...what an ideal SDI would be like Imagine...

8. ...an SDI that makes uploading, sharing, and working with data as easy as blogging Imagine...

9. Publishing data Anthony has some spatial data and wants to display it as part of a blog post.

10. Publishing data Anthony uploads it to a public SDI, styles it, provides a background, and then puts a map widget on his blog.

11. Publishing data Meanwhile, the data, style, and map remain available on the public SDI for others to use.

12. Metadata and reputation The World Organization tells Cameron, their consultant, to put data she has gathered on their SDI.

13. Metadata and reputation Other users notice mistakes in the metadata. They notify Cameron and give it a low rating.

14. Metadata and reputation Cameron fixes the mistakes, and the other users rate the data more highly. Her reputation on the SDI improves.

15. Federated search A regional Health agency and a regional Transit agency have separate SDI systems.

16. Federated search Tom, a GIS analyst doing research, seeks out correlations between health and bicycle routes

17. Federated search Tom searches for data in a single federated index and downloads the data as a batch.

18. How do you make an SDI that's as compelling as modern, widely-used web services?

19. Make an SDI using the best practices of these web services and projects

20. General Principles Grow Bottom Up Align Incentives through Openness Build it for Casual Users Features, not Policies

21. 04/26/10 Grow Bottom-Up Reduce barriers to participation as much as possible. Be useful (if imperfect) as fast as possible.

22. 04/26/10 Grow Bottom-Up Start with data. Let users work with it. Generate metadata as needed.

23. Align Incentives... Align incentives for contribution and use so growth is natural.

24. Align Incentives... Reward data providers for good contributions Encourage users to contribute back Make value of service transparent to system providers

25. ... through Openness Provide a reason to participate Reward collaboration Make it as transparent as possible

26. Build it for Casual Users Using Spatial Data Infrastructure should not require expertise

27. Build it for Casual Users Reading documentation is too much work. The burden is on the system developers to make it intuitive to use.

28. Features, not Policies If SDI technology requires No overhead or compromises there will be No organizational resistance

29. Features, not Policies Look for and implement smart technical solutions to legitimate organizational concerns.

30. is a new software project to build this SDI

31. What does GeoNode actually do ?

32. Give a reason to participate A major problem with SDI is that people lack incentives to use it

33. Problems with Portals No benefit to registering Few real users No recognition or reward for the effort Uses stick, not carrot

34. GIS SDI

35. GIS SDI

36. Embed SDI in the real work of GIS practitioners, and it will have more impact.

37. Embed SDI in the real work of domain experts, and it will have more impact.

38. Embed SDI in the real work of everyone and it will have more impact.

39. Provides styling and cartography tools Users can use the tools on data they upload GeoNode provides a reason to participate

41. Map composer makes Maps Maps are an important content type They bind together ecosystem of geospatial content

44. Maps, Data and Users form an web to be browsed

45. Generic search engines (like Google, Bing) can crawl and rank these pages.

46. Users Have Identity People fill out user profiles to establish identity on the web Profiles are also useful data

47. Meanwhile, Metadata Pain Good metadata for geospatial data is important but hard to produce.

48. GeoNode has user profiles and features them prominently Those profiles have ISO metadata fields within them

49. Metadata Made Easy

50. Metadata Published Metadata is published with open standard CSW using GeoNetwork

51. Open standards and API's

52. Data published by GeoServer in OGC Services: WMS, WFS, WCS Metadata published by GeoNetwork in CSW Output KML for Google Earth, Tile Overlays for Google Maps/Bing/etc.

53. We use open standards for data access. GeoNode also has open APIs

54. HTTP

55. Make Content Portable

57. Let Users Control Content

60. Content owners control access with easy user interface Deep data security extends to OGC services

61. We are building GeoNode to accommodate any institution's access policy

68. OpenStreetMap and Risiko

71. USGS NHD Editing and Versioning

77. 04/26/10

83. Versioning Specs WFS-V (never standardized) OWS-8 GeoSynchronization Service for OGC / NGA WFS 2.0 Versioning for IGN France

86. GeoGit next steps Hook USGS NHD Demo commits to Versioned Layers Build javascript tools for visualization of Diffs, rollbacks, conflict resolution, pull requests Create RESTful spec of advanced features, driven by front end requirements Test in low and no bandwidth scenarios Mobile implementation Test and iterate

87. Data Collaboration Encode business rules and QA as WPS using GeoScript Version to never lose an edit Provenance tracking of every single change Innovation needed, to adapt the governance and advanced tools of Open Source Software to geospatial data and workflows

88. Beyond Portals To real collaboration at all levels: on software, individual layers, and sharing new layers Thousands of nodes of collaboration Custom apps like TsuDAT Data communities like USGS NHD Each feeding in to other nodes that build on top Geospatial becomes a fabric to solve real problems

89. 04/26/10

90. Frequently Asked Questions

91. What's it made of?

92. HTTP

93. 04/26/10

94. What about INSPIRE? GeoServer needs WMS 1.3 to meet INSPIRE standards OpenGeo has found partners to fund this development It is coming soon

95. Open Data Skepticism Isn't GeoNode an open data platform? Doesn't open data raise concerns about data quality and data security?

96. Open Data Optimism Yes, GeoNode is designed to promote open data.

97. Open Data Optimism Features like User reputation Organizational endorsement Flexible security address data quality concerns

98. Open Data Optimism GeoNode supports the continuum of openness with a common platform for institutional GIS and neogeography

99. What about Features X,Y,Z? We welcome your investment in new GeoNode features and involvement in the developer community.

100. GeoNode Action

101. How to Try It Play with the live public demo at http://demo.geonode.org (Warning: Unstable)

102. How to Install It Follow instructions in README at http://github.com/geonode/geonode Email questions to mailing list geonode@librelist.com geonode@librelist.com Talk to developers in #geonode IRC channel

103. Tell us about your experience geonode@librelist.com Your comments will help us Improve it

104. If you want to use GeoNode in production you may want professional quality support How to Buy It

105. Contact OpenGeo at inquiry@opengeo.org Or visit our booth How to Buy It

106. (OpenGeo has a network of regional partners and is looking for others) How to Buy It

107. Is GeoNode perfect for you except that it needs one more feature? How to Invest In It

108. Contact OpenGeo at inquiry@opengeo.org Or visit our booth How to Invest in It

109. How to Join It Contributing Organizations: OpenGeo, World Bank, Civic Works We hope others will join the developer community Patches welcome Community growth a priority

110. Developer Community Join Us! Email geonode@librelist.com to join the mailing listgeonode@librelist.com IRC: #geonode See the issue tracker at – http://projects.opengeo.org/CAPRA

111. If you have any questions about GeoNode Feel free to email seb@opengeo.org

112. Or ask them now. Any questions?