1 / 37

Open Source LBS stack

Open Source LBS stack. Users let the users do the work and fix the bugs ..wiki maps. The round trip • move around.. • translate GPS to GPX • upload GPX traces to your account • click the trace to open the editor • draw vectors over the traces in the editor

derica
Télécharger la présentation

Open Source LBS stack

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Open Source LBS stack

  2. Users let the users do the work and fix the bugs ..wiki maps

  3. The round trip • move around.. • translate GPS to GPX • upload GPX traces to your account • click the trace to open the editor • draw vectors over the traces in the editor • click the line segments to annotate, and add street names • recent changes shows other people your new contribution • other people view, correct, improve and validate your contribution

  4. The round trip attraction • game like • god like • meaningful • addictive

  5. User tools • editors - java - flash + community produced editors • viewers - Ajax slippy map interface - flash

  6. Distributed toil • End user street maps: a wiki approach • Anyone can map • Innovate in acquiring and validating basic geodata • Enough people can - map - annotate - validate ..the 4 blocks around their house

  7. International web mapping • europe • eastern europe • south america • south asia • africa • finessed Tiger data in the US

  8. City by city • descend on a city during a festival • get funding from government and local municipalities, and local companies • distribute GPS units to local people • map the city in two weeks

  9. Actively mapping • bounties • paying for gaps • descending on towns and actively getting them to map themselves • active validation

  10. Editorial pyramid Quality of data issues • Stable and unstable • recent changes • Editorial validation • bottom up validation • distributed liability for erroneous data • Regional franchising • algorithmic detection of aberrant behaviour

  11. Structure • foundation - maps and user validations held in trust, stay free distros

  12. Structure • company - actively mapping and filling gaps - stable distributions - analysis derived products - contract mapping methodologies - improving negotiating positions with mapping data providers

  13. Negotiation • getting GIS data from private organisations and Local government • Satellite and aerial imagery • drive-by 3d modelling GPS data • buying mapping data

  14. Relationships • two weeks of courier data (movie) • aerial photography for a section of Europe

  15. Non-loss data collection • supplying commercial drivers with GPS and where relevant with bluetooth and data capable phones. • paying users to carry out customer requested data collection.

  16. Auto-classification • nodes and lines • behaviour • human input

  17. Image processing and analysis • analysis feeds back into tool chain (traffic behaviour informs auto-classification) • behavioural analysis (dimensions stripped from the public data-set) • derive vectors from satellite imagery (thermal and other methods) • auto-derivation of vectors from aggregated GPS traces

  18. On the back end • WMS tile server • hosting • API

  19. People • spatial analysis • mathematicians • graphics programmers • experience in scaling and managing at scale • artists • cartographers • business development

  20. Compatibility • how can we make our data useful for you? • how could we fit our data into your process and tool chains?

  21. Outcomes • cumulatively improving (and even live) data-set • data to analyse (hidden from users for privacy reasons) • analysis derived value (e.g. traffic data • new tools and methodologies • experienced people • a use for users feedback about stuff navteq get wrong

  22. beyond a proof of concept • build more robust back end and tools • scale the project

  23. Support • much of our needs can be met through a foundation model • additional needs can be supported through a business model • cost effective and constrained achievable objectives

  24. Save time • we’re up • we’ve been thinking about this *and* executing • we have a contributor community • we’re connected to the developer community • we’re committed to a long term view

More Related