Interface: Clovis Traffic Operations Center - Fresno Yosemite International Airport
Architecture Flow Definitions
archive requests (Existing) Applicable ITS Standards
A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
archive status (Existing) Applicable ITS Standards
Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
archived data product requests (Existing)
A user-specified request for archived data products (i.e. data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any.
archived data products (Existing)
Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information.
emergency transit schedule information (Existing)
Information on transit schedule and service changes that adapt the service to better meet needs of responders and the general public in an emergency situation, including special service schedules supporting evacuation.
incident information (Existing)
Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
multimodal archive data (Existing) Applicable ITS Standards
Operational information from alternate passenger transportation modes including air, rail transit, taxis, and ferries. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
request transit information (Existing)
Request for transit service information and current transit status.
road network conditions (Existing)
Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
traffic control priority request (Planned)
Request for signal priority at one or more intersections along a particular route.
traffic control priority status (Planned)
Status of signal priority request functions at the roadside (e.g. enabled or disabled).
traffic images (Existing)
High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications.
transit archive data (Existing)
Data used to describe and monitor transit demand, fares, operations, and system performance. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
transit demand management request (Planned)
Request to change the demand for transit facility use through pricing or other mechanisms.
transit demand management response (Planned)
Response to transit demand management change requests indicating level of compliance with request.
transit probe data (Planned)
Aggregate probe data derived from tracking transit vehicles. Data collected could include transit vehicle speeds and travel times for a given link or collection of links.
transit system data (Existing)
Current transit system operations information indicating current transit routes, the level of service on each route, and the progress of individual vehicles along their routes for use in forecasting demand and estimating current transportation network performance.