Network Conflation Experience Lessons Learned so far

1
Network Conflation Experience- Lessons Learned
(so far)

• Jonathan Ehrlich
• Metropolitan Council

2
Existing Network
3
Why Conflate?

• Accurate distances
• Realistic mapping
• Ability to add data from other sources
• Error-Checking

4
Timeline of Conversion
5
Tier3 Conflation Process

• Proof of Concept
• Conflation of Network for 7 Counties
• Conflate TAZ Centroids using Control Model
• Conflation to NAVTEQ Street Product
• Maintain all Demand Network Node Connectivity
• Use Core gConflate Technology

6
Tier3 Process

• Proprietary Process
• Automated
• Relative Offset

7
Manual Conflation Fixes
8
Logic Errors
9
Exposed Coding Bugs!
10
Find the Error?
11
Find the Error?
12
Find the Error?
13
Find the Error?
14
Need for More Detail
15
Need More Refined Coding Conventions
16
Need More Refined Coding Conventions
17
Continuing Issues

• Software
• Speed
• Clumsy Tools
• Data
• Navteq vs TLG
• Future off-network coding (i.e. HOT)
• Transit

18
Mileage Change