Published on

GeoNode presentation 2/11/10

Published in: Technology


  1. 1. Spatial Data Infrastructure (SDI)
  2. 2. “[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)
  3. 3. The theory of SDI developed before we learned what was possible with the Internet
  4. 4. ...what an ideal SDI would be like Imagine...
  5. 5. SDI that makes uploading, sharing, and working with data as easy as blogging Imagine...
  6. 6. Publishing data Anthony has some spatial data and wants to display it as part of a blog post.
  7. 7. Publishing data Anthony uploads it to a public SDI, styles it, provides a background, and then puts a map widget on his blog.
  8. 8. Publishing data Meanwhile, the data, style, and map remain available on the public SDI for others to use.
  9. 9. Metadata and reputation The World Organization tells Cameron, their consultant, to put data she has gathered on their SDI.
  10. 10. Metadata and reputation Other users notice mistakes in the metadata. They notify Cameron and give it a low rating.
  11. 11. Metadata and reputation Cameron fixes the mistakes, and the other users rate the data more highly. Her reputation on the SDI improves.
  12. 12. Federated search A regional Health agency and a regional Transit agency have separate SDI systems.
  13. 13. Federated search Tom, a GIS analyst doing research, seeks out correlations between health and bicycle routes
  14. 14. Federated search Tom searches for data in a single federated index and downloads the data as a batch.
  15. 15. Vision
  16. 16. Theory
  17. 17. How do you make an SDI that's as compelling as modern, widely-used web services?
  18. 18. Make an SDI using the best practices of these web services and projects
  19. 19. General Principles  Grow Bottom Up  Align Incentives through Openness  Build it for Casual Users  Features, not Policies
  20. 20. 04/26/10 Grow Bottom-Up Reduce barriers to participation as much as possible. Be useful (if imperfect) as fast as possible.
  21. 21. 04/26/10 Grow Bottom-Up Start with data. Let users work with it. Generate metadata as needed.
  22. 22. Align Incentives... Align incentives for contribution and use so growth is natural.
  23. 23. Align Incentives...  Reward data providers for good contributions  Encourage users to contribute back  Make value of service transparent to system providers
  24. 24. ... through Openness  Provide a reason to participate  Reward collaboration  Make it as transparent as possible
  25. 25. Build it for Casual Users Using Spatial Data Infrastructure should not require expertise
  26. 26. Build it for Casual Users Reading documentation is too much work. The burden is on the system developers to make it intuitive to use.
  27. 27. Features, not Policies If SDI technology requires No overhead or compromises there will be No organizational resistance
  28. 28. Features, not Policies Look for and implement smart technical solutions to legitimate organizational concerns.
  29. 29. Vision Theory
  30. 30. Context
  31. 31. is a new software project to build this SDI
  32. 32. Founders Want GeoNode for disaster reduction  Global Facility for Disaster Reduction and Recovery (GFDRR) and World Bank  UN International Strategy for Disaster Reduction (UNISDR)
  33. 33. Builders  Not-for-profit social enterprise  Builds and supports open source geospatial software  Aims to build the Open Geospatial Web
  34. 34. GeoNode is open source.
  35. 35. Install it for free. Contact the developers directly. Collaborate with us and each other. Build local capacity and be independent of any vendor.
  36. 36. We will soon release GeoNode 1.0
  37. 37. Vision Theory Context
  38. 38. What does GeoNode actually do ?
  39. 39. Give a reason to participate A major problem with SDI is that people lack incentives to use it
  40. 40. Problems with Portals  No benefit to registering  Few real users  No recognition or reward for the effort  Uses stick, not carrot
  41. 41. GISGIS SDI
  42. 42. GISGIS SDI
  43. 43. Embed SDI in the real work of GIS practitioners, and it will have more impact.
  44. 44.  Provides styling and cartography tools  Users can use the tools on data they upload  GeoNode provides a reason to participate
  45. 45.  Map composer makes Maps  Maps are an important content type  They bind together ecosystem of geospatial content
  46. 46. Maps, Data and Users form an web to be browsed
  47. 47. Generic search engines (like Google, Bing) can crawl and rank these pages.
  48. 48. Users Have Identity  People fill out user profiles to establish identity on the web  Profiles are also useful data
  49. 49. Meanwhile, Metadata Pain Good metadata for geospatial data is important but hard to produce.
  50. 50.  GeoNode has user profiles and features them prominently  Those profiles have ISO metadata fields within them
  51. 51. Metadata Made Easy
  52. 52. Metadata Published Metadata is published with open standard CSW using GeoNetwork
  53. 53. Open standards and API's
  54. 54.  Data published by GeoServer in OGC Services: WMS, WFS, WCS  Metadata published by GeoNetwork in CSW
  55. 55. KML for Google
  56. 56. We use open standards for data access. GeoNode also has open APIs
  57. 57. HTTP HTTP HTTP
  58. 58.  GeoNode's components interact through clean API's  Others can build apps around GeoNode  Or swap out components (Drupal...?)
  59. 59. Make Content Portable
  60. 60. Let Users Control Content
  61. 61.  Content owners control access with easy user interface  Deep data security extends to OGC services
  62. 62. We are building GeoNode to accommodate any institution's access policy
  63. 63. All these features are included in the current 1.0 release candidate.
  64. 64. Vision Theory Context Reality
  65. 65. Future
  66. 66. We have even more ambitious plans for GeoNode moving forward
  67. 67. The partnership investing in GeoNode is growing The roadmap expands with the vision and needs of its partners
  68. 68. Use the Social Network
  69. 69. The Social for Search
  70. 70. 04/26/10
  71. 71. 04/26/10
  72. 72.  Record statistics on usage  Let users comment on and rate content  Use that information to improve search results
  73. 73. The Social for Quality
  74. 74.  Ratings affect user reputation  Will encourage quality content on SDI
  75. 75. 04/26/10 Groups Matter
  76. 76. 04/26/10
  77. 77. Organizations will have a presence Allows organizational endorsement of data
  78. 78. There are also features specific to Spatial Data Infrastructure on our roadmap SDI Features
  79. 79. Editing
  80. 80. 04/26/10 Federation
  81. 81. Frequently Asked Questions
  82. 82. What's it made of?
  83. 83. HTTP HTTP HTTP
  84. 84. 04/26/10
  85. 85. What about INSPIRE?  GeoServer needs WMS 1.3 to meet INSPIRE standards  OpenGeo has found partners to fund this development  It is coming soon
  86. 86. Open Data Skepticism Isn't GeoNode an open data platform? Doesn't open data raise concerns about data quality and data security?
  87. 87. Open Data Optimism Yes, GeoNode is designed to promote open data.
  88. 88. Open Data Optimism Features like User reputation Organizational endorsement Flexible security address data quality concerns
  89. 89. Open Data Optimism GeoNode supports the continuum of openness with a common platform for institutional GIS and neogeography
  90. 90. What about Features X,Y,Z? We welcome your investment in new GeoNode features and involvement in the developer community.
  91. 91. GeoNode Action
  92. 92. How to Try It Play with the live public demo at (Warning: Unstable)
  93. 93. How to Build It  Follow instructions in README at  Email questions to mailing list  Talk to developers in #geonode IRC channel
  94. 94. Tell us about your experience Your comments will help us Improve it
  95. 95. How to Learn More  Explore  Email questions to mailing list