1. Build Bottom-Up SDI With Sebastian Benthall OpenGeo

2. Spatial Data Infrastructure (SDI)

3. “[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)

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

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

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

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

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

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

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

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

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

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

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

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

16. Vision

17. Theory

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. Vision Theory

31. Context

32. is a new software project to build this SDI

33. Founders Want GeoNode for disaster reduction Global Facility for Disaster Reduction and Recovery (GFDRR) and World Bank UN International Strategy for Disaster Reduction (UNISDR)

34. Builders Not-for-profit social enterprise Builds and supports open source geospatial software Aims to build the Open Geospatial Web

35. GeoNode is open source.

36. Install it for free. Contact the developers directly. Collaborate with us and each other. Build local capacity and be independent of any vendor.

37. We will soon release GeoNode 1.0

38. Vision Theory Context

39. What does GeoNode actually do ?

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

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

42. GIS SDI

43. GIS SDI

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

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

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

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

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

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

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

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

55. Metadata Made Easy

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

57. Open standards and API's

58. Data published by GeoServer in OGC Services: WMS, WFS, WCS Metadata published by GeoNetwork in CSW

59. KML for Google

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

61. HTTP

62. GeoNode's components interact through clean API's Others can build apps around GeoNode Or swap out components (Drupal...?)

63. Make Content Portable

65. Let Users Control Content

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

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

70. All these features are included in the current 1.0 release candidate.

71. Vision Theory Context Reality

72. Future

73. We have even more ambitious plans for GeoNode moving forward

74. The partnership investing in GeoNode is growing The roadmap expands with the vision and needs of its partners

75. Use the Social Network

76. The Social for Search

79. 04/26/10

81. Record statistics on usage Let users comment on and rate content Use that information to improve search results

82. The Social for Quality

83. Ratings affect user reputation Will encourage quality content on SDI

84. 04/26/10 Groups Matter

85. 04/26/10

86. Organizations will have a presence Allows organizational endorsement of data

87. There are also features specific to Spatial Data Infrastructure on our roadmap SDI Features

88. Editing

89. 04/26/10 Federation

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?