1、Designation:E266508Standard Specification forArchiving ITS-Generated Traffic Monitoring Data1This standard is issued under the fixed designation E2665;the number immediately following the designation indicates the year oforiginal adoption or,in the case of revision,the year of last revision.A number
2、 in parentheses indicates the year of last reapproval.Asuperscript epsilon()indicates an editorial change since the last revision or reapproval.1.Scope1.1 This specification describes data elements and schemafor an archived data management system for intelligent trans-portation system(ITS)-generated
3、 traffic monitoring data,in-cluding conventional traffic monitoring data,data collecteddirectly from ITS systems,and travel-time data from probevehicles.It establishes the names of the data elements,theirinterrelationships,and their procedural definitions.These pro-cedural definitions include data c
4、ollection instrumentation andmethodology as well as recommended procedures for calculat-ing traffic statistics.1.2 This specification is intended for primary use by ar-chived data management system(ADMS)developers andadministrators.It also can be used by traffic operations andplanning stakeholders w
5、ho need to understand the contents oftheADMS.ITS systems exist across a variety of governmentallevels,and the data archived in such a system would beavailable to all levels of government and the private sector,making this specification applicable to all levels of governmentand the private sector.1.3
6、 Many users might wish to develop integrated archivedtraffic data management systems that include both ITS-generated data and data collected from conventional traffic-monitoring programs.The latter use requires a superset of dataelements to meet the articulated nature of a conventionaltraffic-monito
7、ring program.This specification will describe abasic set of data elements applicable to ITS-generated trafficdata and the additional data elements required for conventionaltraffic-monitoring programs.In the following discussion,thespecification for the system for ITS-generated data will bereferred t
8、o as the“basic system,”and the one for ITS plusconventional traffic-monitoring data will be denoted the“ex-tended system.”Travel-time data from probe vehicles arestored in separate tables that can be linked through the roadwaylink identifiers.1.4 This specification is applicable to traffic data coll
9、ectedby ITS and stored in an ADMS.Similarly,this specificationalso can be used with other types of historical and monitoredtraffic data collected and stored in an ADMS,includingtravel-time data from probe vehicles.1.5 The applications of“near-real-time”traffic data,such asan automated transit inform
10、ation system(ATIS),are notaddressed in this specification.In many cases,traffic data to bearchived will be provided by a real-time system,but thesesystems are considered data sources rather than data reposito-ries.1.6 This specification specifies a logical data structure for anarchived traffic data
11、management system.1.7 Metadata requirements are specified for these systems.Actual metadata are provided for the elements defined in thisspecification.Placeholders are included for the metadata ele-ments that are specific to a given installation.All metadataspecifications follow the requirements of
12、Practice E2468.1.8 This specification assumes the existence of quality-checked data.The quality checks to be applied should be,at aminimum,those specified in the AASHTO Guidelines forTraffic Data Programs(1),2where applicable.As qualitychecks are developed for ITS-generated traffic data,theyshould b
13、e used.All checks used should be specified in themetadata for the archive.1.9 The summary statistics stored in the archive are as-sumed to have been calculated in a standard way by thesoftware that“feeds”the archive.These standard calculationsshould be those specified in the AASHTO Guidelines forTra
14、ffic Data Programs(1).Any exceptions to these computa-tional methods should be defined in the metadata for thearchive.1.10 This specification assumes the existence of a roadnetwork database but does not specify the nature of thisdatabase.Both traffic and travel-time measurements occur on aroad netwo
15、rk,but the specification of that network is outsidethe scope of this specification.The entities defined in thisspecification will specify a“link location”or“link description”entity that will contain foreign keys to an unspecified roadnetwork entity.1This specification is under the jurisdiction ofAST
16、M Committee E17 on Vehicle-Pavement Systems and is the direct responsibility of Subcommittee E17.52 onTraffic Monitoring.Current edition approved Dec.1,2008.Published January 2009.DOI:10.1520/E2665-08.2The boldface numbers in parentheses refer to the list of references at the end ofthis standard.Copyright ASTM International,100 Barr Harbor Drive,PO Box C700,West Conshohocken,PA 19428-2959.United States1 1.11 This specification assumes the existence of a location-referencing system and does not s
