transit_route_number
This data flow is used within the Manage Transit function and contains the number of a regular transit route. This is stored so that the route number may be the same as that seen by travelers, e.g. 141A, or N177, etc.
Sub Data Flows
- Primitive Element
Parent Data Flows
- billing_for_fares_needed
- current_transit_routes_use
- fare_collection_roadside_violation_information
- fare_collection_vehicle_violation_information
- fare_violation_information
- get_fare_violator_payment_image
- request_vehicle_fare_payment
- transit_data_request
- transit_fare_data_for_emissions
- transit_fare_details
- transit_fare_direct_details
- transit_fares
- transit_probe_data_for_traffic
- transit_route_fare_data
- transit_route_operational_data
- transit_route_segment_identity
- transit_routes_data
- transit_schedule_data
- transit_schedule_updates
- transit_services_for_eta
- transit_services_for_eta_request
- transit_services_for_output
- transit_stop_locations
- transit_vehicle_advisory_eta
- transit_vehicle_arrival_times
- transit_vehicle_assignment_data
- transit_vehicle_assignment_for_operations
- transit_vehicle_assignment_for_vehicle
- transit_vehicle_deviation_update
- transit_vehicle_eta
- transit_vehicle_eta_for_advisory
- transit_vehicle_passenger_data
- transit_vehicle_passenger_loading
- transit_vehicle_passenger_loading_for_crash_notification
- transit_vehicle_running_times
- transit_vehicle_schedule_deviations
- transit_vehicle_user_data
- traveler_roadside_processed_fare_data
- traveler_transaction_record
Associated PSpecs/Terminators
- None