Presentation on theme: "Network Conflation Experience- Lessons Learned (so far) Jonathan Ehrlich Metropolitan Council."— Presentation transcript:
Network Conflation Experience- Lessons Learned (so far) Jonathan Ehrlich Metropolitan Council
Why Conflate? Accurate distances Realistic mapping Ability to add data from other sources Error-Checking
Timeline of Conversion April/May ’08 Approached by Tier3, sent highway networks June ’08 Conflated Network (7-county) received from Tier3 July-December ’08 Waiting for working Cube5 Product January ‘09 Add Ring Counties February-April ‘09 Debugging… Summer ’09 Release of 2009,2015,2020,2030 networks Future Previous years, transit
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
Tier3 Process Proprietary Process Automated Relative Offset
Manual Conflation Fixes
Exposed Coding Bugs!
Find the Error?
Need for More Detail
Need More Refined Coding Conventions
Continuing Issues Software –Speed –Clumsy Tools Data –Navteq vs TLG –Future “off”-network coding (i.e. HOT) –Transit