1.1 本规范描述了智能交通系统（ITS）生成的交通监测数据的存档数据管理系统的数据元素和模式，包括传统交通监测数据、直接从ITS系统收集的数据以及探测车的行驶时间数据。它建立了数据元素的名称、它们的相互关系以及它们的过程定义。这些程序定义包括数据收集工具和方法以及计算交通统计的推荐程序。 1.2 本规范主要供归档数据管理系统（ADMS）开发人员和管理员使用。它也可供需要了解ADMS内容的交通运营和规划利益相关者使用。ITS系统存在于各种政府级别，并且归档在此类系统中的数据将可供各级政府和私营部门使用，从而使本规范适用于各级政府和私人部门。 1.3 许多用户可能希望开发集成的存档交通数据管理系统，该系统包括ITS生成的数据和从传统交通监控程序收集的数据。后一种使用需要数据元素的超集，以满足传统交通监控程序的铰接性质。本规范将描述适用于ITS生成的交通数据的一组基本数据元素，以及常规交通监控程序所需的附加数据元素。在以下讨论中，ITS生成数据的系统规范将被称为“基本系统”，ITS加上传统交通监测数据的规范将被表示为“扩展系统”。探测车的行驶时间数据存储在单独的表中，这些表可以通过道路连接标识符进行链接。 1.4 本规范适用于ITS收集并存储在ADMS中的交通数据。同样，本规范也可用于ADMS中收集和存储的其他类型的历史和监控交通数据，包括旅行- 探测车的时间数据。 1.5 本规范未涉及“近实时”交通数据的应用，如自动交通信息系统（ATIS）。在许多情况下，要归档的交通数据将由实时系统提供，但这些系统被视为数据源，而不是数据存储库。 1.6 本规范规定了存档交通数据管理系统的逻辑数据结构。 1.7 为这些系统指定了元数据要求。为本规范中定义的元素提供了实际的元数据。占位符包括特定于给定安装的元数据元素。所有元数据规范都遵循实践的要求 E2468 . 1.8 本规范假定存在质量检查数据。应用的质量检查至少应为AASHTO交通数据程序指南中规定的质量检查 ( 1. ) , 2. 如适用。 由于对ITS生成的交通数据进行了质量检查，因此应予以使用。所有使用的检查都应在存档的元数据中指定。 1.9 假设存储在档案中的汇总统计数据是由“馈送”档案的软件以标准方式计算的。这些标准计算应为AASHTO交通数据程序指南中规定的计算 ( 1. ) 这些计算方法的任何例外情况都应在存档的元数据中定义。 1.10 本规范假定存在道路网络数据库，但未规定该数据库的性质。交通量和行驶时间测量都发生在道路网络上，但该网络的规范不在本规范的范围内。本规范中定义的实体将指定“链接位置”或“链接描述”实体，该实体将包含未指定道路网络实体的外键。 1.11 本规范假设存在一个位置- 参照系统，并且没有指定位置参照的标准。 1.12 以英寸磅为单位的数值应视为标准。括号中给出的值是国际单位制的数学转换，仅供参考，不被视为标准。 1.13 本标准并不旨在解决与其使用相关的所有安全问题（如有）。本标准的使用者有责任在使用前制定适当的安全、健康和环境实践，并确定监管限制的适用性。 1.14 本国际标准是根据世界贸易组织技术性贸易壁垒委员会发布的《关于制定国际标准、指南和建议的原则的决定》中确立的国际公认的标准化原则制定的。

1.1 This specification describes data elements and schema for an archived data management system for intelligent transportation system (ITS)-generated traffic monitoring data, including conventional traffic monitoring data, data collected directly from ITS systems, and travel-time data from probe vehicles. It establishes the names of the data elements, their interrelationships, and their procedural definitions. These procedural definitions include data collection instrumentation and methodology as well as recommended procedures for calculating traffic statistics. 1.2 This specification is intended for primary use by archived data management system (ADMS) developers and administrators. It also can be used by traffic operations and planning stakeholders who need to understand the contents of the ADMS. ITS systems exist across a variety of governmental levels, and the data archived in such a system would be available to all levels of government and the private sector, making this specification applicable to all levels of government and the private sector. 1.3 Many users might wish to develop integrated archived traffic data management systems that include both ITS-generated data and data collected from conventional traffic-monitoring programs. The latter use requires a superset of data elements to meet the articulated nature of a conventional traffic-monitoring program. This specification will describe a basic set of data elements applicable to ITS-generated traffic data and the additional data elements required for conventional traffic-monitoring programs. In the following discussion, the specification for the system for ITS-generated data will be referred to as the “basic system,” and the one for ITS plus conventional traffic-monitoring data will be denoted the “extended system.” Travel-time data from probe vehicles are stored in separate tables that can be linked through the roadway link identifiers. 1.4 This specification is applicable to traffic data collected by ITS and stored in an ADMS. Similarly, this specification also can be used with other types of historical and monitored traffic data collected and stored in an ADMS, including travel-time data from probe vehicles. 1.5 The applications of “near-real-time” traffic data, such as an automated transit information system (ATIS), are not addressed in this specification. In many cases, traffic data to be archived will be provided by a real-time system, but these systems are considered data sources rather than data repositories. 1.6 This specification specifies a logical data structure for an archived traffic data management system. 1.7 Metadata requirements are specified for these systems. Actual metadata are provided for the elements defined in this specification. Placeholders are included for the metadata elements that are specific to a given installation. All metadata specifications follow the requirements of Practice E2468 . 1.8 This specification assumes the existence of quality-checked data. The quality checks to be applied should be, at a minimum, those specified in the AASHTO Guidelines for Traffic Data Programs ( 1 ) , 2 where applicable. As quality checks are developed for ITS-generated traffic data, they should be used. All checks used should be specified in the metadata for the archive. 1.9 The summary statistics stored in the archive are assumed to have been calculated in a standard way by the software that “feeds” the archive. These standard calculations should be those specified in the AASHTO Guidelines for Traffic Data Programs ( 1 ) . Any exceptions to these computational methods should be defined in the metadata for the archive. 1.10 This specification assumes the existence of a road network database but does not specify the nature of this database. Both traffic and travel-time measurements occur on a road network, but the specification of that network is outside the scope of this specification. The entities defined in this specification will specify a “link location” or “link description” entity that will contain foreign keys to an unspecified road network entity. 1.11 This specification assumes the existence of a location-referencing system and does not specify a standard for location referencing. 1.12 The values stated in inch-pound units are to be regarded as standard. The values given in parentheses are mathematical conversions to SI units that are provided for information only and are not considered standard. 1.13 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use. 1.14 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.