Home

Statewide

District 1

District 2

District 3

District 4&6

District 5

District 7:

 by Stakeholder

 by Entity

Turnpike
 

 Send Your 

 Comments



Traffic Data Collection Equipment Package

Description:

 This equipment package collects and stores traffic information that is collected in the course of traffic operations performed by the Traffic Management Subsystem. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region.

 

Included in:

 Citrus County Traffic Control Center
Clearwater PWD Systems
FDOT D7 Regional Transportation Management Center
Hernando County Traffic Control Center
Hillsborough County Traffic Control Center
Pasco County Traffic Control Center
Pinellas County Traffic Control Center
Plant City Traffic Control Center
St. Petersburg Traffic Control Center
Tampa Traffic Control Center
Turnpike Operations Center (Turkey Lake)

Processes:
1.1.4.7Manage Traffic Archive Data
  

User Service Requirements (fully or partially addressed):

7.0Information Management
7.1Archived Data Function
7.1.0ITS shall provide an Archived Data Function to control the archiving and distribution of ITS data. The Archived Data User Service provides the Historical Data Archive Repositories and controls the archiving functionality for all ITS data with five major functions: 1) the Operational Data Control function to manage operations data integrity; 2) the Data Import and Verification function to acquire historical data from the Operational Data Control function; 3) the Automatic Data Historical Archive function for permanently archiving the data; 4) the Data Warehouse Distribution function, which integrates the planning, safety, operations, and research communities into ITS and processes data products for these communities; and 5) the ITS Community Interface which provides the ITS common interface to all ITS users for data products specification and retrieval. ADUS helps achieve the ITS information goal of unambiguous interchange and reuse of data and information throughout all functional areas.
7.1.3The Archived Data Function shall include a Data Import and Verification (DIV) function to acquire historical data from the Operational Data Control function.
7.1.3.1DIV shall be capable of importing selected ITS Operational data from the ITS Operational Repositories.
7.1.3.1.1DIV shall be capable of importing ITS Freeway Operations data to include:
7.1.3.1.1(a)Freeway traffic flow surveillance data.
7.1.3.1.1(b)Ramp meter preemptions.
7.1.3.1.1(c)Ramp meter operational data.
7.1.3.1.1(d)Freeway visual and video surveillance data.
7.1.3.1.1(e)Traffic Management Center generated freeway flow metrics.
7.1.3.1.2DIV shall be capable of importing ITS Electronic Toll Collection data.
7.1.3.1.3DIV shall be capable of importing ITS Arterial data to include:
7.1.3.1.3(e)Arterial traffic flow surveillance data.
7.1.3.1.5DIV shall be capable of importing ITS Incident Management data to include:
7.1.3.1.5(e)Construction and work zone identification.
7.1.3.1.5(g)Video surveillance data
7.1.3.1.8DIV shall be capable of importing ITS Vehicle and Traveler data to include:
7.1.3.1.8(b)VMS message set data.
7.1.3.1.9DIV shall be capable of importing data on ITS Physical Characteristics of Transportation Infrastructure to include:
7.1.3.1.9(a)Roadway network attributes.
  
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture. Consult the National ITS Architecture web site for more information.

This page was last updated on 12-15-2000 using Web Spinner Technology.