 |
Element Expanded Functional Requirements: Other Public Transportation Providers Ridership Databases |
|
| Functional Area: 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.
|
|
|
|
|
