Docstoc

Network Conflation Experience - Lessons Learned _so far_

Document Sample
Network Conflation Experience - Lessons Learned _so far_ Powered By Docstoc
					Network Conflation Experience-
   Lessons Learned (so far)

        Jonathan Ehrlich
         Metropolitan Council
Existing Network
          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
Logic Errors
Exposed Coding Bugs!
Find the Error?
Find the Error?
Find the Error?
Find the Error?
Need for More Detail
Need More Refined Coding
      Conventions
Need More Refined Coding
      Conventions
        Continuing Issues
Software
– Speed
– Clumsy Tools
Data
– Navteq vs TLG
– Future “off”-network coding (i.e. HOT)
– Transit
         Mileage Change

2009 Network      Links    Miles

Pre-Conflation    25,596   16,163


Post-Conflation   25,775   16,399

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:4/3/2013
language:English
pages:18