I’d like to talk a bit about SDI's. Specifically what I think is the last step in building the dream of INSPIRE. If we're to look at this one definition of SDI INSPIRE has already done most every thing needed - it's written in to law, there are standards, everyone's agreed and it'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
Spatial Data Infrastructure Best Practices with GeoNode
Spatial Data Infrastructure Best Practices With Sebastian Benthall + Galen Evans OpenGeo World Bank
“… 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)
The theory of SDI developed before we learned what was possible with the Internet
...an SDI that makes uploading, sharing, and working with data as easy as blogging Imagine...
Publishing data Anthony has some spatial data and wants to display it as part of a blog post.
Publishing data Anthony uploads it to a public SDI, styles it, provides a background, and then a map widget on his blog.
Publishing data Meanwhile, the data, style, and map remain available on the public SDI for others to use.
Metadata and reputation The World Organization tells Cameron, their consultant, to put data she has gathered on their SDI.
Metadata and reputation Other users notice mistakes in the metadata. They notify Cameron and give it a low rating.
Metadata and reputation Cameron fixes the mistakes, and the other users rate the data more highly. Her reputation on the SDI improves.
Federated search A regional Health agency and a regional Transit agency have separate SDI systems.
Federated search Phillip, a GIS analyst doing research, seeks out correlations between health and bicycle routes
Federated search Phillip searches for data in a single federated index and downloads the data as a batch.
How do you make an SDI that's as compelling as modern, widely-used web services?
Make an SDI using the best practices of these web services and projects
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>
“ Bottom-up SDI” Start with data. Let users work with it. Generate metadata as needed.
“ Bottom-up SDI” Reduce barriers to participation as much as possible.
Align Incentives Align incentives for contribution and use so that it develops naturally
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>
Non-expert User You shouldn't have to be a GIS expert to use your SDI
There's so much more These principles just scratch the surface of the qualities the next generation of SDI should have.
But can it be? These are nice dreams. But will they ever be a reality?
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>
That's the vision and the context. What have we actually built?
Which best practices? How does GeoNode implement them?
Give a reason to participate A major problem with SDI is that too few people have an incentive to use it
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>