Telenav Traffic Locations, presentation October 14, 2012 at OSM State of the Map PDX, Portland, OR

1. Telenav’s Traffic Locations (TTL)
TELENAV’S TRAFFIC LOCATIONS (TTL)
An enabling technology for using traffic data on OSM
SoTM Portland 2012
10/14/12
Ryan Peterson and
Robert Stack

2. Telenav’s Traffic Locations (TTL)
TELENAV’S CUSTOMERS
2
AUTOMOTIVECARRIER APP STORE
White-label &
Telenav Branded
Global
Partnerships
#1 iPhone
Free and Paid Navigation
3/7/2012
More than 30 Million subscribers
Driving over 12 Billion miles per year

3. Telenav’s Traffic Locations (TTL)
YOUR SPEAKERS TODAY
• Ryan Peterson
Product Manager
ryanp@telenav.com
– TrafficGauge, Inc (1998-2009)
• Founder and CEO of VC-funded startup
• Launched first commercial traffic info service in US in 2002
• Multiple patents
• Sold company in 2009
• Robert Stack
Software Engineer
roberts@telenav.com
– Building traffic management systems for
DOTs since 1994 including Boston’s Big Dig
6/6/2013 3

4. Telenav’s Traffic Locations (TTL)
THE NEED FOR TRAFFIC ON OSM
Commercial industry needs OSM traffic information
solutions to enable mainstream consumer navigation
applications based on OSM.
6/6/2013 4

5. Telenav’s Traffic Locations (TTL)
HOW THINGS ARE TODAY (COMMERCIALLY…)
• TMC Location Codes are the industry standard for commercial maps
– Table of unique TMC defined locations common to multiple map vendors unique
road segment IDs (requiring a consortium from commercial map providers)
– License fees in the US and elsewhere
6/6/2013 5
TMC on part of Grand Ave
one for each direction

6. Telenav’s Traffic Locations (TTL)
DESIGN OF TELENAV TRAFFIC LOCATIONS (TTL)
• Telenav creating new and complete location references to describe
traffic flows for OSM
• Telenav TTL to initially cover United States
• OSM Motorway, Trunk, Primary and many Secondary roads
• Follow road topology guidelines—break first at major then minor decision
points (junctions), “number of lane” changes for freeways
• Approximately 1 million TTLs for USA
• Maximum road section lengths:
6/6/2013 6
Urban Rural
Motorway ~0.5 km ~1 km
Others ~2 km ~8 km

7. Telenav’s Traffic Locations (TTL) 6/6/2013 7
COVERAGE OF TTL IN REDMOND, WA

8. Telenav’s Traffic Locations (TTL)
TELENAV TTL MAPPING TO OSM WAYS
• The design philosophy is table based (like TMC) for ease of incorporation into
existing commercial system architectures (otherwise no adoption).
• Many-to-many relationship between OSM ways and Telenav TTL
– Some ways are covered by multiple Telenav TTL, including full and some partial
locations. Some ways are combined with parts of others to make up a location.
6/6/2013 8
Telenav Traffic Link ID OSM Ways
#104765456122139101 6493900, 47338562, 47338561
Telenav Traffic
Location ID
Description Lat/Lon Length OSM Way IDs
104549032122648
352
Westbound, Milwaukie Av
to 17th Av
Start/end lat/lon 0.219km 123385384 (Last 48% of way)
104549032122648
351
Eastbound, 17th Av to 28th
Av
Start/end lat/lon 0.837km 120860705, 96758002,
31527818, 31527817,
96758006

9. Telenav’s Traffic Locations (TTL)
MAP UPDATE PROCESS
• Consistent Telenav TTL identifiers across OSM map releases
• Only new roads, removed roads, upgraded road classifications, or
major changes in road layout create new TTLs
• Output is a table of TTL to OSM ways (e.g. released monthly)
with descriptive meta data
• Vision: TTLs adopted and maintained as a standard
6/6/2013 9

10. Telenav’s Traffic Locations (TTL)
TELENAV TRAFFIC CONTRIBUTIONS TO OSM
• Table of Telenav Traffic Locations for US by year end
– Initial - a posted side table (e.g. on stevecoast.com) with frequent updates
– Goal - integrated into OSM as a new attribute for easy maintenance
• Traffic feed for US by year end
– Limited to non-commercial use and daily download cap
– Commercial use under negotiated license with GPS probe contribution
– Historical model available for license
• Telenav first ever HTML5 (beta) OSM navigation!
– Try today for USA (FREE!)
– http://scoutosm.telenav.com
• Special thanks to Martijn Van Exel and Steve Coast!
• We are hiring!
– Robert Stack roberts@telenav.comroberts@telenav.com
– Ryan Peterson ryanp@telenav.com
6/6/2013 10

11. Telenav’s Traffic Locations (TTL)
ADDITIONAL INFO
6/6/2013 11

12. Telenav’s Traffic Locations (TTL)
MAP UPDATE AUTOMATED WORKFLOW
6/6/2013 12
OSM map database
Accumulated changesets
since last release
Updated traffic location <-> OSM
partial way lookup database
Community contributes:
Update existing traffic
locations to OSM partial ways
Match existing traffic locations to
OSM partial ways in each area
Provided for community:
Identify areas with changed
important highways
Discard traffic locations with no
underlying OSM partial ways
Create new traffic locations for
unmatched OSM partial ways No matchMatch found
Matching complete
Traffic Locations
database

13. Telenav’s Traffic Locations (TTL)
OPEN SOURCE LOCATION REFERENCING
• Enables description of locations independently of a specific base
map layer
• Encodes locations using important attributes and lat/lon
locations that describe them
• Encodings stored in a variety of formats (binary, XML, others)
• Decoding an identifier matches to a similar set of features on a
similar but not identical new map
• Enables lower churn of road section identifiers over time
6/6/2013 13

14. Telenav’s Traffic Locations (TTL)
DETAILED EXAMPLE (1/3)
• Traffic Locations are built from OSM ways. These Locations consist of combined and then split
contiguous roads of the same highway type (“motorway”, “trunk”, …)
• Example below, focusing on SE Holgate Blvd, a Portland, OR Secondary road around 1.3km long
• This road is composed of 6 OSM ways (listed west to east): 123385384, 120860705, 96758002,
31527818, 31527817, 96758006
• Example maximum length of a Traffic Location is 1.0km. Here, the combined SE Holgate Blvd is
too long at 1.3km so the combined road is then split up
• This road is first split at the junction with the most important junction road: SE Milwaukie Av, a
Secondary road
• After this split the east portion is still around 1.1km long, so it is split again at the next most
important junction road: Southeast 17th Av, a Tertiary road
• Now all three Traffic Locations are under 1.0km. There are two per direction for any two way
street, so there are 6 total Traffic Locations (listed west to east): 104549034122654151,
104549033122651163, 104549033122651161, 104549032122648352, 104549032122648351,
104549030122637611
• The first 4 Traffic Locations are composed from of 2 portions of OSM way 123385384. The last 2
Traffic Locations are composed of several OSM ways (including all the other ones listed above).
• Table and illustration for this example on the next 2 slides…
6/6/2013 14

15. Telenav’s Traffic Locations (TTL)
DETAILED EXAMPLE (2/3)
• Example table of Traffic Locations and their underlying OSM Ways, for SE
Holgate Blvd area, Portland, OR:
6/6/2013 15
Traffic Location Description Length OSM Way IDs
104549034122654151 Eastbound, McLoughlin
Blvd to Milwaukie Av
0.233km 123385384 (First 52% of
way)
104549033122651163 Westbound, McLoughlin
Blvd to Milwaukie Av
0.233km 123385384 (First 52% of
way)
104549033122651161 Eastbound, Milwaukie Av
to 17th Av
0.219km 123385384 (Last 48% of
way)
104549032122648352 Westbound, Milwaukie Av
to 17th Av
0.219km 123385384 (Last 48% of
way)
104549032122648351 Eastbound, 17th Av to
28th Av
0.837km 120860705, 96758002,
31527818, 31527817,
96758006
104549030122637611 Westbound, 17th Av to
28th Av
0.233km 120860705, 96758002,
31527818, 31527817,
96758006

16. Telenav’s Traffic Locations (TTL)
DETAILED EXAMPLE (3/3)
• Map of SE Holgate Blvd area, with details for Traffic Location #6 of 6
6/6/2013 16