Presentation is loading. Please wait.

Presentation is loading. Please wait.

Network Conflation Experience- Lessons Learned (so far) Jonathan Ehrlich Metropolitan Council.

Similar presentations


Presentation on theme: "Network Conflation Experience- Lessons Learned (so far) Jonathan Ehrlich Metropolitan Council."— Presentation transcript:

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 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

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

12

13

14 Need for More Detail

15 Need More Refined Coding Conventions

16

17 Continuing Issues Software –Speed –Clumsy Tools Data –Navteq vs TLG –Future “off”-network coding (i.e. HOT) –Transit

18 Mileage Change 2009 Network LinksMiles Pre-Conflation25,59616,163 Post-Conflation25,77516,399


Download ppt "Network Conflation Experience- Lessons Learned (so far) Jonathan Ehrlich Metropolitan Council."

Similar presentations


Ads by Google