The Present and Future Minnesota Rail Network:

Transcription

1 The Present and Future Minnesota Rail Network: Modeling Current Rail Network Conditions and Proposed Rail Infrastructure Projects for the Minnesota Rail Plan Using GIS presented to Minnesota GIS/LIS Conference 2010 Annual Conference Duluth, Minn. presented by Kevin Ebright-McKeehan, Cambridge Systematics, Inc. October 14, 2010

2 Overview Rail Plan Goal Develop an overall vision for effective utilization of the state s rail network and its future development For Passenger Rail: Identify priority rail corridors, programs, and projects that will offer effective improvements or expansion for passenger travel in and out of Minnesota For Freight Rail: Enhance freight access to markets and efficient, competitive services to rail customers, as well as improvements to overall freight flows and logistics 1

3 Overview Why is this rail plan unique? GIS in central analytical role Award-winning plan Winner 2010 FHWA Transportation Excellence Award Link: Quote: The judges noted the plan s data-driven approach 2

4 Overview The Role of Geographic Information Systems (GIS) To provide analytical support for the plan Why did GIS succeed? Data organized in manner to maximize data capabilities (LRS) GIS buy-in / Adoption of organization scheme Creation and use of LRS Development of Service Standards Use of dynamic events in modeling Final Analytical Products 3

5 Overview The Challenges Capture real time operational rail data Given the proprietary nature of rail data Turn rail data into information and analysis Model current and future operational aspects of the Minnesota rail system The Process 4

6 Step 1 Build a Linear Referencing System Overview of Linear Referencing Systems (LRS) LRS allows for the centralization and modeling of data associated with a measured linear feature or network Enterprise GIS Figures From ESRI Common Uses Analysis of disparate data relating to a common network For example: Tables containing pavement type, traffic counts, level of service can all be related to a common reference line, joined to RID and MPs, and dynamically segmented. Mileposting repository 5

7 6 Rail System Evaluation Process: Step 1 Build a Linear Referencing System Rationale Why Bother? Most project data are linear with definitive termini points Tool needed to inventory all rail line data via mileposts Ex. - Where is the Automated Block Signaling (ABS) on the Staples subdivision? Provide basis for modeling current and future conditions Through dynamic segmentation RID (BNSF Hinckley Sub) 22 Seg ID 3 Begin MP End MP Owner BNSF Users1 UP Users2 CP Users3 Reason for Begin Junction Reason for End Junction Segment Type Main Segment Length Active / Inactive Active Use Rail Number of Tracks (ratio) 1.14 FRA Track Class 4 Clearance Envelope Yes 286K capability Yes TrCts 14 TrkSpeed 50

8 Step 1 Build a Linear Referencing System Results from Duluth Results from Coon Creek Junction 7

9 Step 2 Data Collection 8 Data Needed for Data- Driven Analysis Data Collected on 2 Tracks Baseline data used: American Association of Railroads Signaling Systems MnDOT Field Data Team from TKDA in the field (or on the phone) collecting data from railroads Used to quality check and round out AAR and MnDOT data Rail Line Inventory.gdb Most Data Stored in tables for use with LRS

10 Step 3 Current Rail System Conditions LRS + data with mileposts created a comprehensive picture.. Allowed Level of Service Calculation Components CS developed LOS standard Volume-to-capcity Signalization, Track Ratio, Speed, Train Volumes, etc. LOS <C is nearing capacity and functionally deficient Statewide 2009 Rail Line Level of Service Ratings 9

11 Step 3 Current Rail System Conditions and allowed for detailed snapshot of bottlenecks Coon Creek Junction BNSF line from Twin Cities to Duluth 10

12 Step 4 Stakeholder Involvement But is that picture the correct one? Rail data is often proprietary; a closely held secret Feedback sought from railroads, MnDOT modal experts, etc. 95% of system correct Example of constructive feedback: Twin Cities and Western 11

13 Step 5 Future Rail System Conditions Modeled Conditions for 2030 Coon Creek Junction circa

14 Step 5 Future Rail System Conditions No Build-Increased Service Statewide Scenario for

15 Step 6 Future Scenarios and Costs A dizzying array of upgrades and scenarios considered 14 Different combinations of passenger service High-speed rail Commuter rail Service/No service to Duluth Track ratio and/or signal upgrade Level of Service of C must be achieved, along with other minimal standards Cost assigned to each type of upgrade

16 Step 6 Future Scenarios and Costs After Improvements Before Improvements 15

17 Conclusions Identified 7 Phase I passenger rail corridors Detailed freight upgrades for each railroad 16

18 Conclusions Rail System Evaluation Process Revealed: GIS-driven analysis can form report backbone A basic LRS organizes vast amounts of data Modeling with dynamic events allows multiple scenarios 17

19 18 Questions?

20 Acknowledgements From Cambridge Systematics, Inc. Andreas Aeppli, Dan Beagan, Marc Cutler, Nathan Higgins, Kimon Proussaloglou, Erika Witzke From TKDA Tim Havlicek, Jim Hoschka From Kimley-Horn Paul Danielson, Brian Smalkoski From MnDOT Dave Christianson, Bill Gardner, Dan Krom Others Minnesota s railroads My wife Amy and the boys: Kellan and Finn and another on the way 19

21 20 Thank You!