1 / 30

Experience Implementing PORTAL: Portland Transportation Archive Listing

Experience Implementing PORTAL: Portland Transportation Archive Listing. Andrew M. Byrd Andy Delcambre Steve Hansen Portland State University TransNow 2 nd Annual Conference Portland, Oregon  November 19, 2004. Outline. What is PORTAL?

adam-williamson
Download Presentation

Experience Implementing PORTAL: Portland Transportation Archive Listing

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. Experience Implementing PORTAL: Portland Transportation Archive Listing Andrew M. Byrd Andy Delcambre Steve Hansen Portland State University TransNow 2nd Annual Conference Portland, Oregon  November 19, 2004

  2. Outline • What is PORTAL? • National ITS Architecture and Archived Data User Service (ADUS) • PORTAL (the Portland Transportation Archive Listing) • Describe Architecture • Describe Database Processing and Storage • PORTAL Applications • Next Steps

  3. IntroductionGuiding Principles “Data are too valuable to only use once.”

  4. IntroductionGuiding Principles “Management of the transportation system cannot be done without knowledge of its performance.”

  5. Archived Data User Service (ADUS) ITS Architecture 1999 • USDOT Vision for ADUS: “Improve transportation decisions through the archiving and sharing of ITS generated data.” • Principles of ADUS to Achieve Vision • All ITS deployments should consider data archiving • Archive data to maximize integration with other data sources and systems • Archive data in a way that eases retrieval for those with access • Provide information that is integral to transportation practice

  6. Archived Data User Service (ADUS) Implementing a Successful Data Archive A Few Examples of Existing Systems • California PeMS - only statewide system • Puget Sound (WSDOT/TRAC) - started small and successfully expanded • San Antonio, TX TransGuide, Datalink system Cooperation with Various Agencies • Oregon Department of Transportation • Metro (Portland’s regional planning agency) • The City of Portland • TriMet (Portland’s regional transit agency)

  7. Portland Transportation Archive Listing (PORTAL)PSU Designated as Regional Archive Center • Through regional cooperation, Portland State University is the regional center for collecting, coordinating and disseminating variable sources of transportation data and derived performance measures.

  8. PORTAL Architecture Regional ITS Data Sources • 77 CCTV Cameras • 18 Variable Message Signs (VMS) • 436 Inductive Loop Detectors • 118 Ramp Meters • Weather data stations • TriMet Automatic Vehicle Location (AVL) System and Bus Dispatch System (BDS) • Extensive Fiber Optics Network

  9. PORTAL Architecture Inductive Loop Detectors • Most commonly used data source • Work like a large metal detector • Controllers provide three data fields: volume (count), speed (average), and occupancy (% time a vehicle is over the sensor) • This data is aggregated at the loop controllers to 20 second resolution • Most frequently found at entrance ramps – one original use was for the automated control of ramp metering.

  10. HOV Lane Inductive Loop Sensors (detectors) Station Station Station Ramp PORTAL Architecture Inductive Loop Detectors

  11. PORTAL Architecture Inductive Loop Detectors • The loop detector system was put into place by ODOT - our portion of the project does not install or maintain sensors at their Transportation Management Operations Center • Loop detector data is used by ODOT for real-time operations – a minute to minute view of the regional transportation network • We are archiving the high resolution data that ODOT and others collect but do not retain after immediate use

  12. PORTAL Architecture Fiber Optic Data Connection Rich Johnson, City of Portland

  13. PORTAL Architecture Data Flows

  14. PORTAL Architecture Database and Web Servers • We are retaining the data in a PostgreSQL database • Data is gathered every 20 seconds and inserted into the database • Every night, the preceding day’s 20 second data is aggregated to 5 minute and 1 hour resolution • Additional analysis is performed on the original three fields - we calculate VMT, VHT, delay, and travel time

  15. PORTAL Architecture Database and Web Servers • VMT = segment length * volume • Travel time = segment length / speed • VHT = travel time * volume • Delay = travel time – free flow travel time (60 mph)

  16. PORTAL Architecture Database and Web Servers • Database Back End • SQL relational database • 200 MB per day of raw data • 75 GB per year • High capacity disk array • 5 MB compressed for download • Off-site backup server • Daily backups • Uninterruptible power • Web-based interface • Easily accessible • User-friendly • PHP language

  17. PORTAL Architecture Database and Web Servers • Users have the ability to: • sample raw data • store data permanently in accordance to their specifications • use aggregate data at desired resolutions • Outputs • onscreen table • plotted on relevant graphs • downloaded on comma separated value (CSV) format for permanent offline storage

  18. Data Analysis and VisualizationHomepage

  19. Data Analysis and VisualizationContour Plots: Speed

  20. Data Analysis and VisualizationTime Series Plots: Volume

  21. Data Analysis and VisualizationGrouped Data Plots: Speed

  22. ApplicationsTravel Demand Modeling • Metro (the Portland regional Metropolitan Planning Organization) uses a typical four-step computer modeling process to predict future transportation needs • The final step of modeling (trip assignment) requires a function relating volume to delay for finding equilibrium on the highway network • Capacity information and volume-delay relationships for segments of Oregon Highway 217 west of Portland established from archived loop data

  23. ApplicationsTravel Demand Modeling

  24. ApplicationsTravel Demand Modeling

  25. ApplicationsPerformance Measures • Archived data have also been used to produce regional performance measures, allowing better understanding of the transportation network • Average speed maps show visually the average velocity of vehicles at different points on the highway system during peak periods • Congestion frequency charts show how often congestion occurs at each time of day at different points in the transportation network

  26. ApplicationsRegional Peak Period Speed Map

  27. ApplicationsCongestion Frequency Charts Congestion frequency on I-5 South at Barbur Boulevard Percent of time congestion occurs Time of day

  28. Next StepsExpanding Archive Functionality • Data from: • TriMet • Washington State DOT • City of Portland • ODOT WIM Data • Additional processing tools and performance measures

  29. Acknowledgments • National Science Foundation • Oregon Department of Transportation • City of Portland • TriMet • Portland State University • Oregon Engineering and Technology Industry Council

  30. FeedbackYour Opinions and Suggestions Please let us know what you think about existing or future: • Data sources • Performance measures • Data visualizations and summaries Contact us: bertini@pdx.edu http://portal.its.pdx.edu Sign up for an account!

More Related