Your SlideShare is downloading. ×
0
Towards Geospatial Architectures of Participation <ul><ul><li>Chris Holmes </li></ul></ul>
The grassroots remapping  can't be stopped <ul><li>Picking up where Schuyler left off </li></ul><ul><li>Collaborative mapp...
From Rebels to the Establishment <ul><li>It took 20 years for collaboratively built software to achieve mainstream success...
How to Speed things up <ul><li>Identify 'tipping points', places it will make economic sense to invest in collaborative ma...
Tipping Points <ul><li>Collaborative approaches to digital good production are cheaper in the long run </li></ul><ul><ul><...
Tipping Points (cont)‏ <ul><li>BUT: the transaction cost of that investment must be low, must be immediate results </li></...
Potential Business models <ul><li>Decouple functions of commercial data providers so market competes on each </li></ul><ul...
Micro Tipping Points  <ul><li>Good enough for context </li></ul><ul><ul><li>Most Mashups just need a bit of context </li><...
Bounty Navigation <ul><li>Car navigation with feedback loop </li></ul><ul><ul><li>When the system gets you lost you can lo...
Encourage Innovation <ul><li>Architecture s   of Participation </li></ul><ul><li>There's more to collaboratively map than ...
Wikipedia <ul><li>One project to rule them all.  </li></ul><ul><ul><li>Works out quite well for a big collective work like...
Open Source <ul><li>An Ecosystem of approaches </li></ul><ul><ul><li>Different licenses, different languages, different se...
Collaborative Mapping? <ul><li>We don't know.. </li></ul><ul><li>Clear early leader with OSM </li></ul><ul><li>May be heal...
GeoServer: CVS for the GeoWeb <ul><li>Easy to install </li></ul><ul><li>Connects to PostGIS, Oracle Spatial, DB2, ArcSDE, ...
GeoServer Collaboration Features <ul><li>Automated validation engine </li></ul><ul><ul><li>Reject 'Chris Rulez!' over the ...
Future features <ul><li>Granular GeoRSS/email notification </li></ul><ul><ul><li>Watch a bounding box </li></ul></ul><ul><...
Legal Ambiguities <ul><li>No clear licenses for mapping data </li></ul><ul><ul><li>Software licenses don't work </li></ul>...
Clearing Legal Ambiguities <ul><li>Clear terms of derivative rights from major mapping portals </li></ul><ul><ul><li>With ...
More clearing <ul><li>Set of licenses with clear terms about derivation and attribution </li></ul><ul><ul><li>Do whatever ...
Thank You! <ul><li>The Open Planning Project: http://topp.openplans.org </li></ul><ul><li>GeoServer: http://geoserver.org ...
Upcoming SlideShare
Loading in...5
×

Towards Geospatial Architectures of Participation

796

Published on

Where 2.0 talk

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
796
On Slideshare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
50
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Transcript of "Towards Geospatial Architectures of Participation"

    1. 1. Towards Geospatial Architectures of Participation <ul><ul><li>Chris Holmes </li></ul></ul>
    2. 2. The grassroots remapping can't be stopped <ul><li>Picking up where Schuyler left off </li></ul><ul><li>Collaborative mapping can't be stopped </li></ul><ul><li>But can we help it go a bit faster? </li></ul><ul><li>Stallman started work in January 1984 </li></ul><ul><li>2004 saw Weber's 'The Success of Open Source' </li></ul>
    3. 3. From Rebels to the Establishment <ul><li>It took 20 years for collaboratively built software to achieve mainstream success </li></ul><ul><li>Open Street Map - started in 2004, amateurs (in the best sense of the word), hobbyists and 'true believers' </li></ul><ul><li>'The Success of Collaborative Mapping'? - a diverse commons of mapping data constantly updated by citizens, governments and the private sector </li></ul>
    4. 4. How to Speed things up <ul><li>Identify 'tipping points', places it will make economic sense to invest in collaborative mapping. </li></ul><ul><li>Encourage innovation </li></ul><ul><ul><li>An Ecosystem of reusable tools, workflows, licenses and communities to evolve the most effective ways to map collaboratively on a wide variety of datasets </li></ul></ul><ul><li>Clear legal ambiguities </li></ul>
    5. 5. Tipping Points <ul><li>Collaborative approaches to digital good production are cheaper in the long run </li></ul><ul><ul><li>No owner to extract rents above the value of the good. Cut out the middle man. </li></ul></ul><ul><li>Every organization buying mapping data will have a point where it's cheaper for them to fund improvement to a collaborative map than it is to purchase from a commercial provider for the accuracy they need </li></ul>
    6. 6. Tipping Points (cont)‏ <ul><li>BUT: the transaction cost of that investment must be low, must be immediate results </li></ul><ul><li>Funding 'mapping parties' </li></ul><ul><ul><li>Great innovation by Open Street Map </li></ul></ul><ul><ul><li>Quite cost effective </li></ul></ul><ul><ul><li>Takes very enlightened, forward thinking funders - a leap of faith </li></ul></ul><ul><ul><li>Like the early investors in open source, for most part ended up great investment, but hard for most to argue effectively for it. </li></ul></ul>
    7. 7. Potential Business models <ul><li>Decouple functions of commercial data providers so market competes on each </li></ul><ul><ul><li>Surveying/mapping - contracts to improve a certain area of a collab map </li></ul></ul><ul><ul><li>Provide Guarantees of accuracy, perform QA </li></ul></ul><ul><ul><ul><li>ie someone to sue </li></ul></ul></ul><ul><ul><li>Services and Consulting - contributions to collaborative maps are the 'calling card' </li></ul></ul><ul><ul><li>Accuracy evaluations of collaborative maps </li></ul></ul><ul><ul><ul><li>Answer the question of 'should I invest in collaborative mapping?' </li></ul></ul></ul>
    8. 8. Micro Tipping Points <ul><li>Good enough for context </li></ul><ul><ul><li>Most Mashups just need a bit of context </li></ul></ul><ul><li>High quality in constrained areas </li></ul><ul><li>Niche verticals </li></ul><ul><ul><li>Not all uses of maps need all the attributes </li></ul></ul><ul><li>Good enough for basic car navigation </li></ul><ul><ul><li>Introduces great feedback loops </li></ul></ul><ul><li>Services built on top that make money in alternate ways </li></ul>
    9. 9. Bounty Navigation <ul><li>Car navigation with feedback loop </li></ul><ul><ul><li>When the system gets you lost you can log in the change right then </li></ul></ul><ul><ul><li>Collects GPS data from all cars on the service, automatically extracts vectors and one way info </li></ul></ul><ul><ul><li>Monthly fee for all, you can reduce your fee and even make money by correcting maps (on the fly or online processing raw tracks)‏ </li></ul></ul><ul><ul><li>Real time bounties for accurate information requested by clients </li></ul></ul>
    10. 10. Encourage Innovation <ul><li>Architecture s of Participation </li></ul><ul><li>There's more to collaboratively map than streets </li></ul><ul><li>Two big 'commons-based peer production' movements: Wikipedia and Open Source </li></ul><ul><li>Will mapping look like one or the other? Something in between? Completely different? </li></ul>
    11. 11. Wikipedia <ul><li>One project to rule them all.  </li></ul><ul><ul><li>Works out quite well for a big collective work like an encyclopedia.  </li></ul></ul><ul><li>Anyone can edit, but also easy to rollback  </li></ul><ul><li>But a bad edit doesn't break everything, like in software. </li></ul><ul><li>Highly evolved mechanisms for watching areas and erasing vandalism </li></ul><ul><li>Automated techniques to get rid of spam </li></ul>
    12. 12. Open Source <ul><li>An Ecosystem of approaches </li></ul><ul><ul><li>Different licenses, different languages, different sets of tools. Encourages alternative innovations, especially for niche areas </li></ul></ul><ul><li>Very few people can edit an individual project as 'breaking the build' is really bad </li></ul><ul><li>Quite easy to start a new project </li></ul><ul><li>Innovation in workflow: FSF was cathedral building until Linus came along and shook techniques up. </li></ul>
    13. 13. Collaborative Mapping? <ul><li>We don't know.. </li></ul><ul><li>Clear early leader with OSM </li></ul><ul><li>May be healthy to have experimentation with niche maps, constrained areas ect. </li></ul><ul><ul><li>Different licenses? </li></ul></ul><ul><ul><li>Vetting of contributors? </li></ul></ul><ul><ul><li>More automation? </li></ul></ul><ul><ul><li>Alternate tools? </li></ul></ul><ul><ul><li>Work with governments? </li></ul></ul><ul><ul><li>Different workflows? </li></ul></ul>
    14. 14. GeoServer: CVS for the GeoWeb <ul><li>Easy to install </li></ul><ul><li>Connects to PostGIS, Oracle Spatial, DB2, ArcSDE, MySQL backends </li></ul><ul><li>Outputs WMS, WFS, KML, Shapefiles, ect. </li></ul><ul><li>Editing through WFS-T standard </li></ul><ul><li>Extended standard for Rollbacks, Diffs, History, Commit comments </li></ul><ul><li>Soon will have granular security settings </li></ul>
    15. 15. GeoServer Collaboration Features <ul><li>Automated validation engine </li></ul><ul><ul><li>Reject 'Chris Rulez!' over the 48 states </li></ul></ul><ul><li>Integrate with 'power tools' through WFS-T </li></ul><ul><ul><li>Many GIS professionals are already passionate about mapping </li></ul></ul><ul><ul><li>But they want to use the tools they know </li></ul></ul><ul><li>'Patches' - a GetDiff result is a WFS-T transaction, can apply it to another service </li></ul>
    16. 16. Future features <ul><li>Granular GeoRSS/email notification </li></ul><ul><ul><li>Watch a bounding box </li></ul></ul><ul><li>Version aware user friendly web and desktop tools with OpenLayers and uDig </li></ul><ul><li>KML Superoverlay output (GS 1.5.1)‏ </li></ul><ul><li>Branches/sandboxes/suggest changes? </li></ul><ul><li>Easy license selection, machine readable </li></ul><ul><li>Whatever you want, it's open source! </li></ul>
    17. 17. Legal Ambiguities <ul><li>No clear licenses for mapping data </li></ul><ul><ul><li>Software licenses don't work </li></ul></ul><ul><ul><li>Creative Commons doesn't really apply to data </li></ul></ul><ul><ul><li>Public domain or don't release? Or use complex contract law </li></ul></ul><ul><li>Open Licenses for Geodata? </li></ul><ul><ul><li>What is a derivative work for geodata? </li></ul></ul><ul><ul><li>What can be copyrighted? Do we need contract law? </li></ul></ul>
    18. 18. Clearing Legal Ambiguities <ul><li>Clear terms of derivative rights from major mapping portals </li></ul><ul><ul><li>With approval from their data providers </li></ul></ul><ul><ul><li>'We think you can' isn't good enough for serious work </li></ul></ul><ul><ul><ul><li>Teleatlas/Navteq will not be pleased with people hand copying their roads </li></ul></ul></ul><ul><ul><ul><li>What about wikimapia/geonames? Trouble later? </li></ul></ul></ul><ul><ul><li>Yahoo! is the clear early leader in enlightened approaches to derivative works </li></ul></ul>
    19. 19. More clearing <ul><li>Set of licenses with clear terms about derivation and attribution </li></ul><ul><ul><li>Do whatever you like but don't sue me (BSD)‏ </li></ul></ul><ul><ul><li>Don't sue me and give me credit (Apache)‏ </li></ul></ul><ul><ul><li>Contribute back fixes to the data (LGPL)‏ </li></ul></ul><ul><ul><li>All derived works must be collaborative (GPL)‏ </li></ul></ul><ul><li>Encourage different communities with different licenses and see what works </li></ul><ul><li>If you're a lawyer let's talk! </li></ul>
    20. 20. Thank You! <ul><li>The Open Planning Project: http://topp.openplans.org </li></ul><ul><li>GeoServer: http://geoserver.org </li></ul><ul><li>My blog: http://cholmes.wordpress.com </li></ul><ul><li>cholmes@openplans.org </li></ul><ul><li>This work is licensed under the Creative Commons Attribution 3.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by/3.0/us/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA. </li></ul>
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×