network conflation experience- lessons learned (so far)

Network Conflation Experience- Network Conflation Experience- Lessons Learned (so far)Lessons Learned (so far)

Jonathan EhrlichJonathan EhrlichMetropolitan CouncilMetropolitan Council

Existing NetworkExisting Network

Why Conflate?Why Conflate?

Accurate distancesAccurate distances

Realistic mappingRealistic mapping

Ability to add data from other sourcesAbility to add data from other sources

Error-CheckingError-Checking

Timeline of ConversionTimeline of ConversionApril/May ’08April/May ’08 Approached by Tier3, sent highway Approached by Tier3, sent highway

networksnetworks

June ’08June ’08 Conflated Network (7-county) received Conflated Network (7-county) received from Tier3from Tier3

July-December ’08July-December ’08 Waiting for working Cube5 ProductWaiting for working Cube5 Product

January ‘09January ‘09 Add Ring CountiesAdd Ring Counties

February-April ‘09February-April ‘09 Debugging…Debugging…

Summer ’09Summer ’09 Release of 2009,2015,2020,2030 Release of 2009,2015,2020,2030 networksnetworks

FutureFuture Previous years, transitPrevious years, transit

Tier3 Conflation ProcessTier3 Conflation Process

Proof of Concept:Proof of Concept:– Conflation of Network for 7 CountiesConflation of Network for 7 Counties– Conflate TAZ Centroids using Control ModelConflate TAZ Centroids using Control Model– Conflation to NAVTEQ Street ProductConflation to NAVTEQ Street Product– Maintain all Demand Network Node Maintain all Demand Network Node

ConnectivityConnectivity– Use Core gConflate TechnologyUse Core gConflate Technology

Tier3 ProcessTier3 Process

Proprietary ProcessProprietary Process

AutomatedAutomated

Relative OffsetRelative Offset

Manual Conflation FixesManual Conflation Fixes

Logic ErrorsLogic Errors

Exposed Coding Bugs!Exposed Coding Bugs!

Find the Error?Find the Error?

Find the Error?Find the Error?

Find the Error?Find the Error?

Find the Error?Find the Error?

Need for More DetailNeed for More Detail

Need More Refined Coding Need More Refined Coding ConventionsConventions

Need More Refined Coding Need More Refined Coding ConventionsConventions

Continuing IssuesContinuing Issues

SoftwareSoftware– SpeedSpeed– Clumsy ToolsClumsy Tools

DataData– Navteq vs TLGNavteq vs TLG– Future “off”-network coding (i.e. HOT)Future “off”-network coding (i.e. HOT)– TransitTransit

Mileage ChangeMileage Change

2009 Network2009 Network LinksLinks MilesMiles

Pre-ConflationPre-Conflation 25,59625,596 16,16316,163

Post-ConflationPost-Conflation 25,77525,775 16,39916,399