• About
  • Connected Vehicle
  • Architecture
  • Approach
  • Viewpoints
  • Security
• Applications
• Views
  • Enterprise
  • Functional
  • Physical
  • Communications
• Standards
  • CV Standards
  • CV Standards Plan
• Resources
  • Databases
  • Diagrams
  • Documents
  • Presentations
  • Tools
  • Training
• Glossary
  • Acronyms
• Contact Us

1.1.1.1: Process Traffic Sensor Data

This process shall be responsible for collecting traffic sensor data. This data shall include traffic parameters such as speed, volume, and occupancy, as well as video images of the traffic. The process shall collect pedestrian images and pedestrian sensor data. The process shall collect reversible lane, multimodal crossing and high occupancy vehicle (HOV)/high occupancy toll (HOT) lane sensor data. Where any of the data is provided in analog form, the process shall be responsible for converting it into digital form and calibrating. The converted data shall be sent to other processes for distribution, further analysis and storage. The process shall accept inputs to control the sensors and return operational status (state of the sensor device, configuration, and fault data) to the controlling process.

This process is associated with the ITS Roadway Equipment physical object.

This process is associated with the following application objects:

• Roadway Basic Surveillance
• Roadway Infrastructure Restriction Warning
• Roadway Pedestrian Crossing Safety
• Roadway Signal Control
• Roadway Speed Monitoring and Warning
• Roadway Traffic Gap Assist

This process is associated with the following data flows:

• dynamic_lane_sensor_data - Out
• dynamic_lane_sensor_data_to_roadway - Out
• f_other_rw_fc_control_to_traffic_sensor - In
• f_other_rw_ic_control_to_traffic_sensor - In
• fmmc-crossing_close_duration - In
• fmmc-crossing_close_time - In
• fp-pedestrian_data - In
• fp-pedestrian_images - In
• hov_lane_data_input - Out
• hov_sensor_data - Out
• hov_sensor_equip_status_for_m_and_c - Out
• hov_sensor_status - Out
• incident_analysis_data - Out
• infrastructure_sensor_control - In
• local_sensor_data_for_highways - Out
• local_sensor_data_for_intersection - Out
• local_sensor_data_for_roads - Out
• local_sensor_data_for_warning - Out
• multimodal_crossing_sensor_data - Out
• multimodal_crossing_sensor_equip_status_for_m_and_c - Out
• multimodal_crossing_sensor_status - Out
• pedestrian_demand_for_intersection - Out
• pedestrian_demand_for_roadside - Out
• pedestrian_sensor_data - Out
• pedestrian_sensor_equip_status_for_m_and_c - Out
• pedestrian_sensor_status - Out
• pedestrian_sensor_status_for_roadside - Out
• reversible_lane_sensor_data - Out
• reversible_lane_sensor_equip_status_for_m_and_c - Out
• reversible_lane_sensor_status - Out
• sensor_configuration_data - In
• speed_data_for_m_and_c_speed_monitoring - Out
• speed_data_for_traffic_speed_monitoring - Out
• t_other_rw_pedestrian_sensor_data - Out
• t_other_rw_sensor_to_fc - Out
• t_other_rw_sensor_to_ic - Out
• traffic_data_for_vehicle_sensors - Out
• traffic_sensor_data - Out
• traffic_sensor_data_archive_input - Out
• traffic_sensor_data_for_automated_lane_changing - Out
• traffic_sensor_data_for_road_use_payment - Out
• traffic_sensor_data_for_variable_speed_limits - Out
• traffic_sensor_equip_status_for_m_and_c - Out
• traffic_sensor_status - Out
• traffic_sensor_status_for_archive_manager - Out
• traffic_video_image - Out
• traffic_video_image_for_display - Out
• vehicle_characteristics_data - Out
• vehicle_occupants_detected - In