OSM ERROR MANAGEMENTSOTM Portland 2012

04/14/2023 © 2012 Telenav, Proprietary and Confidential 2

INTRODUCTION

• John Novak• Principal Map Engineer, Telenav (8/12)

• Sr Software Engineer, MapQuest (10/10 – 7/12)• Architect, Telenav (10/08 – 10/10)

04/14/2023 © 2012 Telenav, Proprietary and Confidential 3

TELENAV LOCATION

04/14/2023 © 2012 Telenav, Proprietary and Confidential 4

TELENAV LOCATION

04/14/2023 © 2012 Telenav, Proprietary and Confidential 5

TELENAV LOCATION

04/14/2023 © 2012 Telenav, Proprietary and Confidential 6

OVERVIEW

• OSM Data Quality– Assessment– Trending– Improvement Strategy– Lessons Learned– Results

04/14/2023 © 2012 Telenav, Proprietary and Confidential 7

QUALITY ASSESSMENT

• Just how good is the data– Quality Checks

• External Tools (OSMI, Keepright,…)• SQL Scripts• Applications• Multiple Data Sources

– Example Error Classes• Simple Connectivity• Partial Way Overlaps• Isolated Ways (just added to OSMI ROE as islands)• Routing• GeoCoding

04/14/2023 © 2012 Telenav, Proprietary and Confidential 8

QUALITY TRENDING

• Given the existence of errors, how quickly are they being addressed ?

• How does OSM quality today compare with OSM quality pre-redaction ?

• How to prevent (or at least detect) significant quality regression– Vandalism, for example– Challenging

04/14/2023 © 2012 Telenav, Proprietary and Confidential 9

PRE/POST REDACTION LINKS

04/14/2023 © 2012 Telenav, Proprietary and Confidential 10

PRE/POST REDACTION LINKS

04/14/2023 © 2012 Telenav, Proprietary and Confidential 11

PRE/POST REDACTION CONNECTIVITY

04/14/2023 © 2012 Telenav, Proprietary and Confidential 12

PRE/POST REDACTION CONNECTIVITY

04/14/2023 © 2012 Telenav, Proprietary and Confidential 13

IMPROVEMENT STRATEGY

• Two Tracks– Technology (Top-Down)– Telenav Community (Bottom-Up)

04/14/2023 © 2012 Telenav, Proprietary and Confidential 14

TECH

• Technology (Top-Down)– Leverage map expertise and internal data for detection– Identify errors such as

• Direction of Flow• Grade Separation• Turn Restrictions

– Using internally developed application suite– Publish to OSM community– Leverage existing tools (such as OSMI)– Targeting 24 hour update cycle

04/14/2023 © 2012 Telenav, Proprietary and Confidential 15

TELENAV COMMUNITY

• Telenav Community (Bottom-Up)– Significant proportion of new editors– Training– Edit-a-thon Sessions– Focus on “simple” errors first

04/14/2023 © 2012 Telenav, Proprietary and Confidential 16

LESSONS LEARNED

• “Simple” errors can rapidly become not so simple– Partial Way overlaps– Multiple copies of ways (in some cases, a dozen)– Navigable ways merged with boundaries and areas– Allow error bypass

• Epic Tediousity– The simple is also really boring– Feedback on progress– Bite-sized chunks– Stats

04/14/2023 © 2012 Telenav, Proprietary and Confidential 17

EXAMPLE

• Simple connectivity fixes• Focus on county boundaries• About 2.5 months elapsed time• Approx 350 person hours

04/14/2023 © 2012 Telenav, Proprietary and Confidential 18

OSM US WAY CONNECTIVITY (OSMI 8/23/12)

04/14/2023 © 2012 Telenav, Proprietary and Confidential 19

OSM US WAY CONNECTIVITY (TNAV 10/12/12)

04/14/2023 © 2012 Telenav, Proprietary and Confidential 20

OSM US WAY CONNECTIVITY (TNAV 10/12/12)

04/14/2023 © 2012 Telenav, Proprietary and Confidential 21

MENLO PARK CA ADDRESS POINTS

04/14/2023 © 2012 Telenav, Proprietary and Confidential 22

CLOSING REMARKS

• Generate error status updates as quickly as possible• Staleness blunts momentum (tighten the loop)• Guidance on what and where to apply effort• Provide alternatives• It does not take long to effect major improvements

04/14/2023 © 2012 Telenav, Proprietary and Confidential 23

QUESTIONS