multimodal its data integration and perfomance...
TRANSCRIPT
1
Robert L. BertiniPortland State UniversityNorth American Travel Monitoring Exhibition & ConferenceSan Diego, California June 30, 2004
Multimodal ITS Data Integration and Perfomance Measurement in Portland, Oregon
2
OutlineRegional VisionRegional ITS Partners and Data IntegrationWorking with Metropolitan Planning Organization
Empirical data for travel demand modelPerformance measures for annual report
ITS Data IntegrationVideo Imaging Processing and Loop Detector Data to Provide Vehicle ClassificationFreeway Incident Management Performance AssessmentUsing Bus AVL Systems and Loop Detector Data to Characterize Corridor Performance Using Bus AVL Data To Characterize Arterial Performance (Session 21)
3
ITS Data IntegrationRegional Vision
Warehouse ITS data at their most raw level. Include user interface for extracting relevant performance measures in real time and historically.Through regional cooperation, Portland State University is the regional center for collecting, coordinating and disseminating variable sources of transportation data and derived performance measures.Data can be mined for operations, planning, management and research purposes for the transportation system
4
Regional ITS PartnershipsData IntegrationTransPort Technical Advisory Committee
Oregon Department of Transportation City of PortlandTriMet Metro (OR)Regional Transportation Commission (WA)Washington State Department of TransportationCities (bi-state)Counties (bi-state)C-TranPort of PortlandPortland State University
Monthly coordination meetingsVoluntary project funding integrationSubcommittee Structure
DataITS ArchitectureCommunications
5
75 CCTV cameras 18 variable message signs 118 ramp meters436 inductive loop detectors24 hour/day incident response with 11 vehiclesDigital archives of incident logsAVL Archives of COMET movementsExtensive fiber optic communications system
Traffic Management SystemPortland Region
6
Traveler InformationPortland Region
Variable Message Signs
Traffic Cameras
Traffic Reports
www.tripcheck.com
7
Integrating ITS Data Into Corridor PlanningMetro Highway 217 Corridor Study
Available archived loop detector data along key travel corridor.Possible to incorporate updated speed/travel time information into trip distribution step of Metro’s travel demand modelBackground
Metro developing corridor study for Highway 217 corridor improvementsEMME/2 travel demand modelTrip Distribution step relies on “theoretical” and “default” values
Opportunity for linking ITS data to regional transportation planning efforts.
8
Supplement theoretical and default values in the trip distribution step with empirical data.Improve Bureau of Public Roads (BPR) volume/travel time functions.BPR does not take into account regional variations and dynamic changes for a particular facilityFacility characteristics and driver behavior have changed significantly over the 40 years since BPR functions were created.Recent developments in the transportation system such as ramp metering and other ITS technologies may have altered highway performance.
Integrating ITS Data Into Corridor PlanningMetro Highway 217 Corridor Study
9
Integrating ITS Data Into Corridor PlanningMetro Highway 217 Corridor Study
Study AreaRamp metering39 detectors at 9 locationsEstimated segment capacity from loop detector data
CountOccupancyQueue discharge
Created function relating V/C ratio to travel time
10
oblique 1524
-11000
-10800
-10600
-10400
-10200
-10000
-9800
-9600
-9400
-9200
-9000
2174
Integrating ITS Data Into Corridor PlanningMetro Highway 217 Corridor Study
Oblique Plot of Flow at Detector 1524
Maximum Flow 2170 vph
Time
11
Integrating ITS Data Into Corridor PlanningMetro Highway 217 Corridor Study
Highway 217 Volume/Delay Curve
12
Regional Performance Measures Metro Performance Report 2004
Metro Performance Report – reports on progress of region including transportation system.
PSU ITS Lab generated performance measures as indicator of possible future ITS based reporting.
Sample performance data prepared in 2004:
Average Speed Map for the regional highway systemCongestion frequency charts for key corridors
13
Regional Performance Measures Average Speed Map
14
Regional Performance Measures Congestion Frequency
0
10
20
30
40
50
60
70
80
90
100
06:0
0
06:3
0
07:0
0
07:3
0
08:0
0
08:3
0
09:0
0
09:3
0
10:0
0
10:3
0
11:0
0
11:3
0
12:0
0
12:3
0
13:0
0
13:3
0
14:0
0
14:3
0
15:0
0
15:3
0
16:0
0
16:3
0
17:0
0
17:3
0
18:0
0
18:3
0
19:0
0
19:3
0
20:0
0
20:3
0
21:0
0
21:3
0
Percent of Reported Speeds < 30mph (2001)WB I-84 Between I-205 and I-5
Time
Per
cent
15
Video Imaging Processing Vehicle Classification
Regional need for truck count data on an ongoing basis.Live feed from 75 CCTV cameras into ITS Lab.Using Autoscope to extract vehicle classification data.Developing statistical sampling plan:
SpatialTemporal
Challenge is to properly re-orient cameras.Collaborating with University of Washington.
16
Video Imaging Processing Vehicle Classification
0
20
40
60
80
100
120
140
1 16 31 46 61 76 91 106 121 136 151 166 181 196 211 226 241 256 271 286
5 Minutes Unit
Cou
nts
(Veh
icle
s/5m
inut
es)
Total Counts
Truck Counts
Testing loop only algorithm to extract truck count estimates.5 minute intervals.Uncongestedconditions.Wang-Nihanalgorithm.Developing sampling plan. Collaborating with University of Washington.
17
Freeway Incident Data IntegrationIncident Management Program Assessment
Low
Medium
High
18
215 208 236 269 222 234 186 242 195304 293 257
789 764803 803 917
714919 892
745
937 1009
774
497445
425 462
621
444
585 514
423
547538
492
0
200
400
600
800
1000
1200
1400
1600
1800
2000
Janua
ryFeb
ruary
March
April
May
June
July
Augus
tSep
tember
October
Novem
berDec
ember
Month
Num
ber o
f Inc
iden
ts
Crash Stall OtherN=18920
1501 153414641417
1760
1392
16901648
1363
1788 1840
1523 Mean1576
Freeway Incident Data IntegrationIncident Management Program Assessment
Year 2001 Incident Inventory
19
6550
79
144
50
101
36 43 35
174 181194
150 158 157172
133150
199
160
112
66
130125
0
50
100
150
200
250
January
February
March
April
May
June
July
August
September
October
Novembe
rDece
mber
Month
Num
ber o
f Cra
shes
0
5
10
15
20
25
Num
ber o
f Wet
Day
s
Crashes on Wet DaysCrashes on Dry DaysWet Days1152 Crashes on Wet Days
1712 Crashes on Dry Days113 Wet days
Freeway Incident Data IntegrationIncident Management Program Assessment
Impact of Weather on Incident Frequency
20
Ongoing Incidents 1 Day
12:00AM
2:00AM
4:00AM
6:00AM
8:00AM
10:00AM
12:00PM
2:00PM
4:00PM
6:00PM
8:00PM
10:00PM
12:00AM
Time of Day
1
11
21
31
41
51
61
71
81In
cide
nt C
ount
Incident Time and Duration on November 18th 2002
N=83
0
2
4
6
8
10
12:00AM
1:00 AM 2:00 AM 3:00 AM 4:00 AM 5:00 AM 6:00 AM 7:00 AM 8:00 AM 9:00 AM 10:00AM
11:00AM
12:00PM
1:00 PM 2:00 PM 3:00 PM 4:00 PM 5:00 PM 6:00 PM 7:00 PM 8:00 PM 9:00 PM 10:00PM
11:00PM
Time
Num
ber o
f Inc
iden
ts
Incidents Scheduled IR Vehicles
21
Year 2001 Average Ongoing Incidents
0.00
1.00
2.00
3.00
4.00
5.00
1:00
2:00
3:00
4:00
5:00
6:00
7:00
8:00
9:00
10:00
11:00
12:00
13:00
14:00
15:00
16:00
17:00
18:00
19:00
20:00
21:00
22:00
23:00
Time
Num
ber o
f Inc
iden
ts/IR
Veh
icle
s
Sunday Monday TuesdayWednesday Thursday FridaySaturday IR Vehicles Weekday IR Vehicles Weekend
Freeway Incident Data IntegrationIncident Management Program Assessment
22
Using Bus AVL Systems and Loop Detector Data to Characterize Corridor Performance
TriMet Express Bus Routes on Interstate 5Route 95X morning peak service between Sherwood and Downtown Portland Route 96X provides morning and evening peak only service betweenSherwood and Downtown PortlandThree week I-5 experiment
Loop detector dataExpress bus AVL data (pseudo stops on freeway)
Geo-coded data from Tri-Met’s automatic vehicle location (AVL) system was used to build trip trajectories.Trajectories were overlaid onto contour plots of speed data fromODOT’s inductive loop detectors on Northbound I-5 CorridorMerging of two data sources to effectively achieve travel time estimation and validation.
23
I-5 Freeway Corridor PerformanceBus AVL and Loop Detector Data
24
I-5 Northbound, November 7, 2002
I-5 Freeway Corridor PerformanceLoop Detector Data
25
I-5 Northbound, November 7, 2002
I-5 Freeway Corridor PerformanceBus AVL Data
26
I-5 Northbound, November 7, 2002
I-5 Freeway Corridor PerformanceBus AVL and Loop Detector Data
27
I-5 Freeway Corridor PerformanceBus AVL and Loop Detector Data
0.20.40.40.50.60.60.20.2Variance
7.68.313.513.69.59.17.97.5Mean
LoopBusLoopBusLoopBusLoopBus
Nov 14 2002Nov 13 2002Nov. 7 2002Nov. 6 2002
Northbound Corridor Travel Times (min)
28
Acknowledgments
Andrew Byrd, B.S., Computer ScienceThareth Yin, M.S., Civil & Environmental EngineeringMichael Rose, Master of Urban & Regional Planning
National Science FoundationOregon Department of Transportation City of PortlandTriMetPortland State UniversityOregon Engineering and Technology Industry Council
29
For More InformationComments and Feedback Welcome
Thank You!
http://www.its.pdx.edu