The document discusses GeoNode, an open source software project that aims to build a next generation Spatial Data Infrastructure (SDI) based on best practices from modern web services. Some key points: - GeoNode aims to make uploading, sharing, and working with spatial data as easy as blogging by reducing barriers to participation. - It aligns incentives for contribution and use through features like user profiles, reputation systems, and ability to style and share maps. - The software implements open standards and APIs to make data accessible and allow other applications to integrate.

1. Spatial Data Infrastructure Best Practices With Sebastian Benthall + Galen Evans OpenGeo World Bank

2. Spatial Data Infrastructure (SDI)

3. “… 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.” – Groot & McLaughlin 2000 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 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 Phillip, a GIS analyst doing research, seeks out correlations between health and bicycle routes

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

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

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

19. “ Bottom-up SDI” Start with data. Let users work with it. Generate metadata as needed.

20. “ Bottom-up SDI” Reduce barriers to participation as much as possible.

21. Align Incentives Align incentives for contribution and use so that it develops naturally

23. Non-expert User You shouldn't have to be a GIS expert to use your SDI

24. There's so much more These principles just scratch the surface of the qualities the next generation of SDI should have.

25. But can it be? These are nice dreams. But will they ever be a reality?

26. is a new software project to build this SDI

27. It's open source. Of course.

29. That's the vision and the context. What have we actually built?

30. Which best practices? How does GeoNode implement them?

31. Give a reason to participate A major problem with SDI is that too few people have an incentive to use it

33. GIS SDI

34. GIS SDI

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

41. Maps, Data and Users form an ecosystem to be browsed

43. Metadata pain Good metadata for geospatial data is important but hard to produce.

45. Metadata Made Easy

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

47. Open standards and API's

49. KML for Google

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

51. HTTP HTTP HTTP

53. Make Content Portable

55. Let Users Control Content

59. All these features are included in the current 1.0-beta release.

60. DEMO

61. They only scratch the surface. GeoNode has a much more ambitious roadmap.

62. Use the Social Network

63. The Social for Search

69. The Social for Quality

71. Groups Matter

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

74. These features, based on the best practices of the web, will likely be developed within a year Big Plans

75. There are also features specific to Spatial Data Infrastructure on our roadmap Even Bigger Plans

76. Editing

77. Federation

78. Frequently Asked Questions

79. What's it made of?

80. HTTP HTTP HTTP

81. Today, Sept 9 14:00, right after lunch Room 4 “ GeoNode Architecture” David Winslow

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

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

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

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

87. What about Features X,Y, Z? OpenGeo: We welcome your investment in new GeoNode features! Inquire at the OpenGeo Booth. (Also, patches are very welcome)

88. GeoNode Action

89. August 6 th - GeoNode 1.0-beta release September 27 th ?? - GeoNode 1.0 released

92. OpenGeo: We're Hiring! OpenGeo is hiring to fill GeoNode software developer and consultant positions

93. OpenGeo: We're Selling! OpenGeo is offering a FOSS4G Special on GeoNode 1.0 Support, Deployment, and Services Inquire at our booth.

94. Any questions?