Regional Architecture Logo
 

Send Your Comments

E-Mail

Roadside Data Collection Equipment Package

Architecture Geographic Scope

Description:

This equipment package collects traffic, road, and environmental conditions information for use in transportation planning, research, and other off-line applications where data quality and completeness take precedence over real-time performance. This equipment package includes the sensors, supporting roadside infrastructure, and communications equipment that collects and transfers information to a center for archival.

 

Included in:

Cameron County Traffic Data Collection System
Hidalgo County Pavement Data Collection System
Hidalgo County Traffic Data Collection System
TxDOT Pharr District Pavement Data Collection System

Processes:

1.1.1.4Manage Data Collection and Monitoring
  

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(c)Ramp meter operational 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.7DIV shall be capable of importing ITS Environmental data to include:
7.1.3.1.7(a)Emission 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(c)Equipment maintenance status
  
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.

Last updated on 07-16-2003 using Ronald C. Ice and Associates Web Spinner Technology.