incident_location
This data flow is used within the Manage Traffic function and contains the location at which an incident will take place (for planned events) or is taking place (for current incidents). The location will be defined in terms of map coordinates to enable it to be referenced spatially within the geographic area served by the local TMC. The data flow consists of the following data item which is defined in its own DDE:
location_identity
Sub Data Flows
Parent Data Flows
- current_conditions
- current_incident_details
- current_incidents_data_output
- current_incidents_data_request
- current_incidents_data_update
- current_incidents_new_data
- emergency_vehicle_incident_details
- fets-incident_information
- fm-incident_details
- fm-incident_information
- foem-incident_details
- foisp-incident_data
- fotic-incident_data
- fotm-current_event_data
- fro-rail_incident_information
- historical_incident_details
- identified_emergency_details
- incident_alert_details
- incident_details
- incident_details_from_media
- incident_info_for_emerg
- incident_info_for_traffic
- incident_info_from_emerg
- incident_info_from_traffic
- incident_information
- incident_response_clear
- incident_response_log
- incident_response_log_from_traffic
- incident_response_log_output
- incident_status_update
- m_and_c_view_of_road_network
- operations_incident_data_updates
- planned_event_details
- planned_events_data_output
- planned_events_new_data
- pollution_incident
- possible_detected_incidents
- possible_incidents
- possible_incidents_data_output
- request_planned_events_data
- toem-incident_details
- toisp-incident_data
- totic-incident_data
- totm-current_event_data
- transit_emergency_data
- transit_incident_details
- transit_incident_information
- tro-incident_information
- undefined_incident_response
Associated PSpecs
- None