ITS Element: City of Santa Fe Traffic Counts Program

Send Your Comments

Description: The traffic count division of the City of Santa Fe who is responsible for collecting all traffic sensor and flow information from the City's ITS field devices.
Status: Existing
Stakeholder: City of Santa Fe
Mapping: Archived Data Management Subsystem
Other Archives

Interfaces:

City of Santa Fe Traffic Operations Section
NMDOT Traffic Count Collection Section
Project Private Consultants
Santa Fe County Traffic Count Section
Santa Fe MPO Archive
Santa Fe MPO Field Devices
Market Packages: AD1 - ITS Data Mart - Santa Fe MPO
AD1 - ITS Data Mart - City of Santa Fe Traffic Counts
Functional Requirements:

ITS Data Repository

  • The center shall collect data to be archived from one or more data sources.
  • 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; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).
  • 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 include capabilities for performing quality checks on the incoming archived data.
  • The center shall include capabilities for error notification on the incoming archived data.
  • The center shall include capabilities for archive to archive coordination.
  • 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 summarize transportation data from multiple sources and serve a broad array of users within a region.
  • 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.
  • When data or a catalog of data is received from the archive, the center shall generate the requested data product for the users systems.
  • For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a Financial Institution.

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 capability to select data from an ITS archive for use in government reports.
  • The center shall provide the capability to format data from an ITS archive suitable for input into government reports.
  • The center shall support requests for ITS archived data from 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 of the data.

Traffic and Roadside Data Archival

  • The center shall manage the collection of archive data directly from collection equipment located at the roadside.
  • The center shall collect traffic sensor information from roadside devices.
  • 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 record the status about the imported traffic and roadside data.
  • The center shall use the status information to adjust the collection of traffic and roadside data.

Last updated: 12-29-11