170 likes | 286 Views
PennDOT’s Traffic Data System Redesign. Greg Ulp , GeoDecisions. TDS Project Background. What is PennDOT’s Traffic Data System (TDS) 100 in-pavement counters (24/7 continuous counts) Polling of counters is done each night to collect 24 hours of data 45,000 temporary count locations
E N D
PennDOT’s Traffic Data System Redesign Greg Ulp, GeoDecisions
TDS Project Background • What is PennDOT’s Traffic Data System (TDS) • 100 in-pavement counters (24/7 continuous counts) • Polling of counters is done each night to collect 24 hours of data • 45,000 temporary count locations • 20,000,000 records of data each month • 9 different applications used to manage the data • Data consumed by several other systems within the DOT • Project Objectives • Produce a Integrated Custom/Flexible Solution • Web-based (internal and external components) • Limited Maintenance Costs • Data Challenges • Data Migration • Amount of data being collected • Impact on existing systems
TDS Device File Manager • Device File Manager • ETL GUI • File Definition Editor • I/O Map Editor
TDS File Definition Editor • Allows user to define input stream from counter
TDS I/O Map Editor • Allows user to map data from the counter to the database
TDS I/O Rule Manager • Rule Manger • Define edits/flags for invalid data • Rules are applied while counter data is imported into database
TDS Rule Editor • Define flags for invalid data
TDS Continuous Data Analysis System (CoDAS) • Used by Traffic Analysts to verify data • Flags pinpoint possible data issues
TDS Traffic Monitoring System (TMS) • Used to manage all 45,000 traffic site locations
TDS Technologies • ASP.net • HTML 5 • Javascript • Angular JS • Crystal Reports • Nhibernate • Oracle • Oracle Partitioning for archiving
Questions Greg Ulp Senior Project Manager GeoDecisions gulp@geodecisions.com