Martijn van Exel - Collaborate to compete: Regain your Competitive Edge with osm
•Télécharger en tant que PPTX, PDF•
1 j'aime•872 vues
*** Presented at State of the Map 2013 in Birmingham, UK *** For more info please see http://lanyrd.com/2013/sotm/scphch/ The increased use of OpenStreetMap in commercial products creates many opportunities and challenges for the OSM community and its commercial users. While the creation of spatial data remains the domain of a few experts, the continued growth of mobile applications results in the creation of massive geodata by consumers from which the OSM project can certainly benefit. In parallel, commercial users will need to feel less constrained to protect their geodata allowing them to shift their focus on developing greater competitive solutions for their customers. This session will explore possible collaboration models between commercial users of OSM and the broader community, and offer insights into reaching greater participation in the OSM project.
Recommandé
Recommandé
Contenu connexe
En vedette
En vedette (20)
Plus de OSMFstateofthemap
Plus de OSMFstateofthemap (10)
Dernier
Dernier (20)
Martijn van Exel - Collaborate to compete: Regain your Competitive Edge with osm
- 1. COLLABORATE TO COMPETE: REGAIN YOUR COMPETITIVE EDGE WITH OSM Martijn van Exel martijnv@telenav.com @mvexel (Twitter) 11/1/2013 © 2013 Telenav, Proprietary and Confidential 1
- 2. 11/1/2013 © 2013 Telenav, Proprietary and Confidential 2
- 3. 11/1/2013 © 2013 Telenav, Proprietary and Confidential 3
- 4. 11/1/2013 © 2013 Telenav, Proprietary and Confidential 4
- 5. 11/1/2013 © 2013 Telenav, Proprietary and Confidential 5
- 6. 11/1/2013
- 8. m.scout.me 11/1/2013 © 2013 Telenav, Proprietary and Confidential 8
- 9. Overpass API XAPI .pbf! .osm.bz2 11/1/2013 © 2013 Telenav, Proprietary and Confidential 9
- 10. What now? Who will let go first? 11/1/2013 © 2013 Telenav, Proprietary and Confidential 10
- 11. 11/1/2013 © 2013 Telenav, Proprietary and Confidential 11
- 12. A large and tremendously fast growing crowd of mappers Tight local and global communities who really care about creating the best map in the world Open model! 11/1/2013 © 2013 Telenav, Proprietary and Confidential 12
- 13. Big things don’t get done The data is messy and still incomplete 1.3M sounds nice but most don’t actually map Open model… 11/1/2013 © 2013 Telenav, Proprietary and Confidential 13
- 14. This is a mess! This is a mess! 11/1/2013 © 2013 Telenav, Proprietary and Confidential 14
- 15. maproulette.org/battlegrid 11/1/2013 © 2013 Telenav, Proprietary and Confidential 15
- 16. Community score card 95% of edits done by 26% of users 80% untouched TIGER 0.4 avg version increase of TIGER roads 1% of features touched in last 3 months, 7% in last year 20° 11/1/2013 © 2013 Telenav, Proprietary and Confidential 16
- 17. 11/1/2013 © 2013 Telenav, Proprietary and Confidential 17
- 18. 11/1/2013 © 2013 Telenav, Proprietary and Confidential 18
- 19. 11/1/2013 © 2013 Telenav, Proprietary and Confidential 19
- 20. Who is this man? And why is he wearing a cape? They told me to smile. Smi-ile. 11/1/2013 © 2013 Telenav, Proprietary and Confidential 20
- 21. 11/1/2013 © 2013 Telenav, Proprietary and Confidential 21
- 22. 11/1/2013 © 2013 Telenav, Proprietary and Confidential 22
- 23. 11/1/2013 © 2013 Telenav, Proprietary and Confidential 23
- 24. 11/1/2013 © 2013 Telenav, Proprietary and Confidential 24
- 25. Collaboration only works when both sides benefit 11/1/2013 © 2013 Telenav, Proprietary and Confidential 25
- 26. We need to acknowledge each other’s strengths and weaknesses 11/1/2013 © 2013 Telenav, Proprietary and Confidential 26
- 27. Make a conscious choice 11/1/2013 © 2013 Telenav, Proprietary and Confidential 27
- 28. Stakeholders and community share the huge responsibility of dealing with many new users we expose to OSM. How do we get them to map? To share? Without overburdening our coveted power mappers! 11/1/2013 © 2013 Telenav, Proprietary and Confidential 28
- 29. Thank you! And thank you Flickr Commons for the photos 11/1/2013 © 2013 Telenav, Proprietary and Confidential 29
Notes de l'éditeur
- goodmorningMy gosh it’s great to be back at SOTM after a year of absence. Had to miss last year after Four straight years of great SOTMs, one of which I was closesly involved in organizing. I’ve already had a chance to catch up with some of you, three days of great talks and fun ahead.Funny how four years ago we organized the first ‘business track’ at SOTM 09, back then I saw the potential but didn’t see myself up there – to me OSM was for fun but not for profit.. Since I moved to the United States two years ago, my relationship with OSM has grown a new limb. I am an OSM specialist at Telenav. Have been with Telenav since beginning of the yearLet me first talk about Telenav and what we are doing really briefly, and then I will spend most of my time sharing some thoughts and ideas on collaboration between stakeholders and OSM.
- Telenav is based in Sunnyvale in the heart of Silicon ValleyWe operate in the automotive and mobile navigation space.
- We have been around for a while.Telenav started in 1999.We currently market navigation systems for in your car as well as for mobile phonesOur flagship product for mobile is Scout, our personalized navigation app available for Android, iOS and Windows Phone 8
- This is what it looks like in real life. I wanted to highlight it because our Scout products is where you will be most likely to see OSM integration first.
- Today, we serve over 30 million usersIn an expanding range of countries including US, Canada, Mexico, Brazil.We are the preferred navigation provider for some of the leading cellular carriers including ATT and Sprint
- We have been looking at OSM as a data provider for a few years nowWhy?A few reasons
- The richness of the data is unparallelledThe project grows at tremendous speedOSM allows for much fresher data for our usersWe can be more independent from vendors
- We are releasing OSM first on our HTML5 based navigation product Scout for BrowsersAfter that we will work to integrate OSM into our other Scout products for mobile and auto.
- We realized early on that OSM data is not a one stop shop. You cannotjustpickit up, loadit and expectsmoothsailing.A deepunderstanding of how the OSM communityworks, how the data isbuilt and maintained, and how conventions come about, is essential. We have about a dozen people working on our OSM effort todayworking on data analysis and processing, infrastructure and testing.So using OSM is not all about saving money – althoughithelpssweeten the deal.
- To reach the deep understanding needed to adopt OSM successfully, we can’t afford not collaborate with the community.(With collaboration, I mean working together to build something new or improve something existing.)This is what I wanted to share some thoughts and ideas about this morning.I want to explore two topics:How stakeholders and OSM can collaborateWhat their relationship can or should be----- Meeting Notes (9/6/13 09:13) -----don't have to explain collab
- Let’s look first at how we can collaborate.I think a successful collaboration is born from looking at each others strengths and weaknesses,And choosing areas of collaboration based on what you come up with.
- The strengths of the OpenStreetMap project are A large and fast growing crowd of mappersLocal and global communities who care about creating the best map in the worldOpen model
- The weaknesses of the OSM project areTotal lack of hierarchy means big things don’t get doneThe data is pretty messy and still not completeHuge churn rate – very few active contributors in relation to total accounts. And again, the open model – it is both a strength and a weakness
- So let’s look at a couple of these weaknesses and see how stakeholders can play a role in alleviating them,First let’s look at the messy data.One of the things Telenav is really worried about is the poor quality of TIGER data in many places in the US.The potential strength of a stakeholder is its focus on a specific problem,This can help to target specific problems, either local or thematic.
- So we applied our expertise and resources to the problem to create the Battle Grid, highlighting weak areas in the TIGER data.The idea is to make the problem visible and provide focus and prioritization to folks who want to help fix it.(By the way this would be an ideal challenge for another great example of tooling built by a stakeholder with a clear need to address a specific problem: The OSM Tasking manager built by HOT)
- Same thing for the churn rate. This is a tough problem to crack. How do you keep folks engaged?We don’t need all 1.3 million registered users to be active contributors. But we do definitely need better coverage of active mappers in certain places. In the US, we still have large metros with no significant mapping activity!
- Again one external stakeholder focused on this problem helps OSM make a huge leap MapBox stepped up to make OSM editing much more accessible with the new iD editor.An idea that had been floating around for a while – we need a better web based editor.Initial work was done by @RichardFBut thanks to external effort the project got done and the result is phenomenal.
- I have to add one element to this stakeholder engagement with OSM Also corporate stakeholders can get more eyes on the map by exposing all their users to OSM. This is what happens right now with Foursquare, Craigslist. And now we are coming along with millions of users.That comes with a huge responsibility!! How are you going to help OSM harness all that local knowleddge? We are still figuring this out and I hope to get lots of inspiration here.
- We can’t just have them all put in notes, we wouldn’t be able to keep up with them.
- Next let’s talk about relationship. This has sometimes been an awkward topic I feel. There seem to be so many opinions on what role a stakeholder could or should take when they want to collaborate with osm.Is there a secret sauce? A magic recipe?I don’t think so. I hope I have already shown that successful collaborations work because a corporate stakeholder applies their strengths to target specific problems in OSM.Focus on a specific goal , combined with Resources to pursue that goal can drive a big improvement home, help OSM make leaps that it could not otherwise make very easily.
- To srtreamline talking about that relationship, here’s a collaboration matrix I came across that may give us some more pointers. It is based on two variables: Flat or hierarchical governance, and Open and Closed collaboration.Open collaboration is a situation where everyone can submit ideas. Closed is where the contributors are hand picked.Hierarchical forms have a leader defining the problems to solve, whereas in flat collaborations everyone has a say in which problems will be solved.There is not one magic slot in which all OSM – stakeholder collaboration fits.You might be tempted to say closed does not fit with OSM, but let me give you an example where that worked really well – at least at first.
- Let’s look at MapRoulette, a tool I started developing about a year and a half ago, meant to rally the community to fix specific map problemsWho here has heard of MapRoulette?This started out as a problem I personally wanted to see addressed. I could have started by explaining the need I saw and asking the community for possible solutions to the problemThat would have been an open and flat approach. Instead, I thought I already had a really great idea and started building it.
- So MapRoulette started out in the Closed / Hierarchical quadrant. As an elite circle: meNow that MR is established, more people are involved in development and determine its direction. Also, in the upcoming release, basically everyone will be able to add data problems to MapRoulette for the community to fix.So also in that respect, the project has moved from the Elite Circle to the Innovation Community.
- Which path you define in this quadrant for your intended collaboration really depends on what you want to do. What I am saying is that there is no inherent right or wrong way.Some fundamental changes in OSM can only be brought about starting in an elite circle.Like a bold redesign of the web site Or traffic segments.This may not be the best possible example because I started building MapRoulette as a Concerned Community Member, not really an external stakeholder.But I can think of more examples that at least started out as great ideas by external stakeholders, that have proven to be of great value to the community.POI editors first by Cloudmade, then by Spatial NetworksAlso many of the QA tools we currently have – Osm Inspector, ITO maps.Example of collaboration project that pretty much started out as an Innovation Community is the AND data donation for NL.
- Choose open or closed, flat or hierarchical on a piecemeal basisBut make that choice consciouslyThere are no inherently bad ways as long as the mutual benefit is clear.