Successfully reported this slideshow.
Your SlideShare is downloading. ×

Spatial Data Infrastructure Best Practices with GeoNode

Loading in …3

Check these out next

1 of 94 Ad

More Related Content

Similar to Spatial Data Infrastructure Best Practices with GeoNode (20)


Recently uploaded (20)


Spatial Data Infrastructure Best Practices with GeoNode

  1. 1. Spatial Data Infrastructure Best Practices With Sebastian Benthall + Galen Evans OpenGeo World Bank
  2. 2. Spatial Data Infrastructure (SDI)
  3. 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. 4. The theory of SDI developed before we learned what was possible with the Internet
  5. 5. ...what an ideal SDI would be like Imagine...
  6. 6. SDI that makes uploading, sharing, and working with data as easy as blogging Imagine...
  7. 7. Publishing data Anthony has some spatial data and wants to display it as part of a blog post.
  8. 8. Publishing data Anthony uploads it to a public SDI, styles it, provides a background, and then a map widget on his blog.
  9. 9. Publishing data Meanwhile, the data, style, and map remain available on the public SDI for others to use.
  10. 10. Metadata and reputation The World Organization tells Cameron, their consultant, to put data she has gathered on their SDI.
  11. 11. Metadata and reputation Other users notice mistakes in the metadata. They notify Cameron and give it a low rating.
  12. 12. Metadata and reputation Cameron fixes the mistakes, and the other users rate the data more highly. Her reputation on the SDI improves.
  13. 13. Federated search A regional Health agency and a regional Transit agency have separate SDI systems.
  14. 14. Federated search Phillip, a GIS analyst doing research, seeks out correlations between health and bicycle routes
  15. 15. Federated search Phillip searches for data in a single federated index and downloads the data as a batch.
  16. 16. How do you make an SDI that's as compelling as modern, widely-used web services?
  17. 17. Make an SDI using the best practices of these web services and projects
  18. 18. General Principles <ul><li>Build Bottom Up </li></ul><ul><li>Align Incentives </li></ul><ul><li>Be Open </li></ul><ul><li>Non expert use </li></ul>
  19. 19. “ Bottom-up SDI” Start with data. Let users work with it. Generate metadata as needed.
  20. 20. “ Bottom-up SDI” Reduce barriers to participation as much as possible.
  21. 21. Align Incentives Align incentives for contribution and use so that it develops naturally
  22. 22. Be Open <ul><li>Give users a reason to participate in the system </li></ul><ul><li>Reward collaboration with recognition and harvest the results </li></ul><ul><li>Make as much information transparent for others to use as possible. </li></ul>
  23. 23. Non-expert User You shouldn't have to be a GIS expert to use your SDI
  24. 24. There's so much more These principles just scratch the surface of the qualities the next generation of SDI should have.
  25. 25. But can it be? These are nice dreams. But will they ever be a reality?
  26. 26. is a new software project to build this SDI
  27. 27. It's open source. Of course.
  28. 28. Founders <ul><li>Founders are interested in GeoNode primarily for disaster risk management </li></ul><ul><ul><li>Global Facility for Disaster Reduction and Recovery (GFDRR) and World Bank </li></ul></ul><ul><ul><li>UN International Strategy for Disaster Reduction (UNISDR) </li></ul></ul>
  29. 29. That's the vision and the context. What have we actually built?
  30. 30. Which best practices? How does GeoNode implement them?
  31. 31. Give a reason to participate A major problem with SDI is that too few people have an incentive to use it
  32. 32. Problems with Portals <ul><li>No benefit to registering </li></ul><ul><li>Few real users </li></ul><ul><li>No recognition or reward for the effort </li></ul><ul><li>Uses stick, not carrot </li></ul>
  33. 33. GIS SDI
  34. 34. GIS SDI
  35. 35. Embed SDI in the real work of GIS practitioners, it will have more impact.
  36. 36. <ul><li>Provides styling and cartography tools </li></ul><ul><li>Users can use the tools on data they upload </li></ul><ul><li>GeoNode provides a reason to participate </li></ul>
  37. 38. <ul><li>Map composer makes Maps </li></ul><ul><li>Maps are an important content type </li></ul><ul><li>They bind together ecosystem of geospatial content </li></ul>
  38. 41. Maps, Data and Users form an ecosystem to be browsed
  39. 42. Users Have Identity <ul><li>People like to fill user profiles to establish identity on the web </li></ul><ul><li>Profiles then become useful data </li></ul>
  40. 43. Metadata pain Good metadata for geospatial data is important but hard to produce.
  41. 44. <ul><li>GeoNode has user profiles and features them prominently </li></ul><ul><li>Those profiles have ISO metadata fields within them </li></ul>
  42. 45. Metadata Made Easy
  43. 46. Metadata Published Metadata is published with open standard CSW using GeoNetwork
  44. 47. Open standards and API's
  45. 48. <ul><li>Data published by GeoServer in OGC Services: WMS, WFS, WCS </li></ul><ul><li>Metadata published by GeoNetwork in CSW </li></ul>
  46. 49. KML for Google
  47. 50. We use open standards for data access. GeoNode also has open APIs
  48. 51. HTTP HTTP HTTP
  49. 52. <ul><li>GeoNode's components interact through clean API's </li></ul><ul><li>Others can build apps around GeoNode </li></ul><ul><li>Or swap out components (Drupal...?) </li></ul>
  50. 53. Make Content Portable
  51. 55. Let Users Control Content
  52. 58. <ul><li>Content owners control access with easy user interface </li></ul><ul><li>Data security extends to OGC services </li></ul>
  53. 59. All these features are included in the current 1.0-beta release.
  54. 60. DEMO
  55. 61. They only scratch the surface. GeoNode has a much more ambitious roadmap.
  56. 62. Use the Social Network
  57. 63. The Social for Search
  58. 68. <ul><li>Record statistics on usage </li></ul><ul><li>Let users comment on and rate content </li></ul><ul><li>Use that information to improve search results </li></ul>
  59. 69. The Social for Quality
  60. 70. <ul><li>Ratings affect user reputation </li></ul><ul><li>Will encourage quality content on SDI </li></ul>
  61. 71. Groups Matter
  62. 73. Organizations will have a presence Allows organizational endorsement of data
  63. 74. These features, based on the best practices of the web, will likely be developed within a year Big Plans
  64. 75. There are also features specific to Spatial Data Infrastructure on our roadmap Even Bigger Plans
  65. 76. Editing
  66. 77. Federation
  67. 78. Frequently Asked Questions
  68. 79. What's it made of?
  69. 80. HTTP HTTP HTTP
  70. 81. Today, Sept 9 14:00, right after lunch Room 4 “ GeoNode Architecture” David Winslow
  71. 82. What about INSPIRE? <ul><li>GeoServer needs WMS 1.3 and WFS 2.0 for GeoNode to meet INSPIRE standards </li></ul><ul><li>OpenGeo is looking for partners to fund this development </li></ul>
  72. 83. Open Data Skepticism Isn't GeoNode an open data platform? Doesn't open data raise concerns about data quality and data security?
  73. 84. Open Data Optimism Yes, GeoNode is designed to promote open data.
  74. 85. Open Data Optimism Features like User reputation Organizational endorsement Flexible security address data quality concerns
  75. 86. Open Data Optimism GeoNode supports the continuum of openness with a common platform for institutional GIS and neogeography
  76. 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)
  77. 88. GeoNode Action
  78. 89. August 6 th - GeoNode 1.0-beta release September 27 th ?? - GeoNode 1.0 released
  79. 90. Developer Community <ul><li>Contributing Organizations: OpenGeo, World Bank, Civic Works </li></ul><ul><li>We hope others will join the developer community </li></ul>
  80. 91. Developer Community <ul><li>Join Us! </li></ul><ul><li>Email [email_address] to join the mailing list </li></ul><ul><li>IRC: #geonode </li></ul>
  81. 92. OpenGeo: We're Hiring! OpenGeo is hiring to fill GeoNode software developer and consultant positions
  82. 93. OpenGeo: We're Selling! OpenGeo is offering a FOSS4G Special on GeoNode 1.0 Support, Deployment, and Services Inquire at our booth.
  83. 94. Any questions?

Editor's Notes

  • I’d like to talk a bit about SDI&apos;s. Specifically what I think is the last step in building the dream of INSPIRE. If we&apos;re to look at this one definition of SDI INSPIRE has already done most every thing needed - it&apos;s written in to law, there are standards, everyone&apos;s agreed and it&apos;s moving forward. But I have a worry:
  • Underlying all of this is our commitment to open source, as it is the reason for our success, and we want to spread it widely
  • Make the data findable on Google Maps, not just on catalogs Should be accessible on as many places as possible, not locked in to the portal We’re starting to do this with GeoServer, putting actual data on the map, but with links back to the important metadata for the whole dataset