ITS Element: NOACA Regional Transportation Data Archive

Send Your Comments

Description: Traffic counts and accident report data (available from website). Also links to transit data.
Status: Existing
Stakeholder: NOACA
Mapping: Archived Data Management Subsystem
Other Archives

Interfaces:

City of Cleveland Signal Control System
GCRTA Communications Center
Geauga County Transit Operations
Hopkins International Airport and Burke Lakefront Airport
Laketran Operations Center
LCT Bus Operations Center
Medina County Transit Operations Center
ODOT District 12 Freeway Management Center
ODOT District 3 Office
Regional Airport
Market Packages: AD2 - ITS Data Warehouse - NOACA Regional Transportation Data Archive
Functional Requirements:

ITS Data Repository

  • For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a Financial Institution.
  • The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the collection of archived data and may include descriptions of the schema or structure of the data, a description of the contents of the data
  • The center shall collect data to be archived from one or more data sources.
  • The center shall include capabilities for archive to archive coordination.
  • The center shall include capabilities for error notification on the incoming archived data.
  • The center shall include capabilities for performing quality checks on the incoming archived data.
  • The center shall perform quality checks on received data.
  • The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations, aggregations, or transformations applied to the data before it is stored in the archive.
  • The center shall respond to requests from the administrator interface function to maintain the archive data.
  • The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users.
  • The center shall support a broad range of archived data management implementations, ranging from simple data marts that collect a focused set of data and serve a particular user community to large-scale data warehouses that collect, integrate, and summari
  • When data or a catalog of data is received from the archive, the center shall generate the requested data product for the users systems.

Government Reporting Systems Support

  • The center shall provide data from an ITS archive to federal, state, or local government reporting systems.
  • The center shall provide the applicable meta-data for any ITS archived data to satisfy government reporting system requests. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection o
  • The center shall provide the capability to format data from an ITS archive suitable for input into government reports.
  • The center shall provide the capability to select data from an ITS archive for use in government reports.
  • The center shall support requests for ITS archived data from Government Reporting Systems.

On-Line Analysis and Mining

  • For archive analysis and data mining products requiring financial payment the center shall process the financial requests and manage an interface to a Financial Institution.
  • The center shall provide the capability to perform activities such as data mining, data fusion, summarizations, aggregations, and recreation from archive data. This may include multidimensional analysis, selective summarization and expansion of data deta
  • The center shall receive the user’s systems requests and develop the request to retrieve the data from the archive.
  • The center shall respond to users systems requests for a catalog of the archived data analysis products available.
  • The center shall support the interface with Archive Data User Systems for requests for analysis of the archive data.

Traffic and Roadside Data Archival

  • The center shall collect environmental sensor information that from roadside devices.
  • The center shall collect traffic sensor information from roadside devices.
  • The center shall manage the collection of archive data directly from collection equipment located at the roadside.
  • The center shall record the status about the imported traffic and roadside data.
  • The center shall respond to requests from the Archive Data Administer to input the parameters that control the collection process.
  • The center shall send the request for data and control parameters to the field equipment where the information is collected and returned.
  • The center shall use the status information to adjust the collection of traffic and roadside data.

Last updated: 03-17-10