1 / 18

Network Conflation Experience- Lessons Learned (so far)

Explore Jonathan Ehrlich's journey in network conflation at Metropolitan Council, highlighting the process, benefits, and challenges faced so far. Learn about the importance of accurate distances, realistic mapping, and error-checking. Discover the timeline of the Tier3 conflation process and the proof of concept involving conflation for 7 counties. Gain insights into the proprietary automated conflation process and the need for more refined coding conventions. Address future challenges like transit mileage changes and off-network coding.

althea-mcdowell
Télécharger la présentation

Network Conflation Experience- Lessons Learned (so far)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

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

  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

More Related