1、Designation: E2665 08 (Reapproved 2017)Standard 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
2、 last revision. A number 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-por
3、tation system (ITS)-generated 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 pr
4、o-cedural definitions include data collection 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 traffi
5、c operations andplanning stakeholders who 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 level
6、s of governmentand the private sector.1.3 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 articula
7、ted nature of a conventionaltraffic-monitoring 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 sy
8、stem for ITS-generated data will bereferred to 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
9、 specification is applicable to traffic data collectedby 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
10、-time” traffic data, such asan automated transit information 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 spe
11、cifies a logical data structure for anarchived traffic data 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 instal
12、lation. All metadataspecifications 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 aminimum, those specified in the AASHTO Guidelines forTraffic Data Programs (1),2where applicable. As qual
13、itychecks are developed for ITS-generated traffic data, theyshould be 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 standa
14、rd calculationsshould be those specified in the AASHTO Guidelines forTraffic 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 t
15、hisdatabase. Both traffic and travel-time measurements occur on aroad network, 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 un
16、specified roadnetwork entity.1This specification is under the jurisdiction ofASTM Committee E17 on Vehicle- Pavement Systems and is the direct responsibility of Subcommittee E17.52 onTraffic Monitoring.Current edition approved Jan. 1, 2017. Published January 2017. Originallyapproved in 2008. Last pr
17、evious edition approved in 2008 as E2665 08. DOI:10.1520/E2665-08R17.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 StatesThis international sta
18、ndard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for theDevelopment of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.11.11
19、 This specification assumes the existence of a location-referencing system and does not specify a standard for locationreferencing.1.12 The values stated in inch-pound units are to be re-garded as standard. The values given in parentheses aremathematical conversions to SI units that are provided for
20、information only and are not considered standard.1.13 This standard does not purport to address all of thesafety concerns, if any, associated with its use. It is theresponsibility of the user of this standard to establish appro-priate safety and health practices and determine the applica-bility of r
21、egulatory limitations prior to use.2. Referenced Documents2.1 ASTM Standards:3E867 Terminology Relating to Vehicle-Pavement SystemsE2259 Guide forArchiving and Retrieving Intelligent Trans-portation Systems-Generated DataE2468 Practice for Metadata to Support Archived DataManagement Systems2.2 IEEE
22、Standard:4IEEE 1489 Standard for Data Dictionaries for IntelligentTransportation Systems2.3 ITE Standard:5TM 1.03 Standard for Functional Level Traffic ManagementData Dictionary (TMDD)2.4 ISO Standard:6ISO 14817 Transport Information and Control SystemsRequirements for an ITS/TICS Central Data Regis
23、try andITS/TICS Data Dictionaries2.5 NTCIP Standards:7NTCIP 1206 Object Definitions for Data CollectionNTCIP 1209 Data Element Definitions for TransportationSensor Systems (TSS)3. Terminology3.1 DefinitionsFor definitions relating to vehicle-pavement systems, see Terminology E867.3.2 Definitions of
24、Terms Specific to This Standard:3.2.1 aggregate, vto process or combine like items into acategory, for example, adding together 30-s traffic volumecounts or averaging speeds from lane-by-lane detectors that areparts of the traffic data-counting station to be the total trafficvolume or average speed
25、at that traffic-counting station for a5-min time period.3.2.2 aggregation, nresultant set of aggregated data asso-ciated with an aggregating process.3.2.3 archived data management subsystem, nsubsystemof the National ITS architecture that provides a means forseveral organizations to collect, store,
26、and subsequently, ana-lyze and retrieve data from ITS data sources, usually by way ofone or more ITS centers.3.2.4 archived data management system, nspecific imple-mentation of an archived data management subsystem withinthe context of a local, regional, or statewide ITS architecture.3.2.5 archived
27、data user service (ADUS), none of the ITSuser services that defines the scope of the National ITSarchitecture with regard to archiving and retrieving ITS-generated data.3.2.6 attribute, ndefined property or characteristic; subsetof an entity.3.2.6.1 DiscussionIn common terms, an attribute is typi-ca
28、lly a column in a relational database or a property in anobject-oriented environment.3.2.7 compound element, ngroup or combination ofgroups of metadata elements.3.2.7.1 DiscussionAll compound elements are describedby metadata elements either directly or through intermediatecompound elements. Compoun
29、d elements represent higher-level concepts that cannot be represented by individual meta-data elements.3.2.8 data, nquantitative or qualitative representation thatis observed, measured, collected, or gathered that characterizessome static or dynamic attribute of the physical world or theuse of it by
30、 individuals or groups of people and is suitable forcommunication, interpretation, or processing by humans ormachines.3.2.9 data dictionary, ninformation construct that de-scribes the particular data stored in a database typically interms of a common set of attributes that include the meaning,concep
31、t, and use; see IEEE 1489.3.2.10 data element, ndata item that is a basic buildingblock of a data dictionary which is a formal representation ofsome single unit of information of interest with a singularinstance value at any time about some entity of interest.3.2.11 data quality, nfitness of data fo
32、r all purposes thatrequire them.3.2.11.1 DiscussionExamples of data quality measuresinclude accuracy, completeness, coverage, and timeliness.3.2.12 data set, nlogical collection of data that supports auser function and could include one or more data tables, files,or sources.3.2.13 database, ncollect
33、ion of related data typically or-ganized in a computerized record-keeping system that is part ofa system whose purpose is to maintain the data and informationderived from it so it can be made available for use.3.2.14 entity, nexisting or real thing.3.2.14.1 DiscussionIn relation to a database, an en
34、tity is asingle person, place, or thing about which data can be stored.3For referenced ASTM standards, visit the ASTM website, www.astm.org, orcontact ASTM Customer Service at serviceastm.org. For Annual Book of ASTMStandards volume information, refer to the standards Document Summary page onthe AST
35、M website.4Available from IEEE, Publications Office, 10662 LosVaqueros Circle, P.O. Box3014, Los Alamitos, CA 90720-1264.5Available from the Institute of Transportation Engineers, 1099 14th St., NW,Suite 300 West, Washington, DC 20005-3438.6Available from American National Standards Institute (ANSI)
36、, 25 W. 43rd St.,4th Floor, New York, NY 10036, http:/www.ansi.org.7Available from the National Transportation Communications for ITS Protocol(NTCIP), www.ntcip.org.E2665 08 (2017)2In common terms, an entity can be represented by one or moretables in a relational database or an object in an object-o
37、rientedenvironment.3.2.15 expired data, nstatus assigned to a set of data,summary statistics, or information that is no longer current orvalid and needs to be replaced.3.2.16 imputation, nact of putting onto a data set esti-mated values for that data to fill in for missing values or replaceerroneous
38、 values.3.2.17 integration, nresult of blending compatible datasources into a composite data set has a unity or wholeness forpurposes of analysis, summarization, and retrieval of specificdata or information.3.2.18 intelligent transportation systems (ITS), nsystemsthat apply modern sensing, communica
39、tion, computing,analysis, or display technologies, or a combination thereof, toone or more aspects of the operations, management, and use oftransportation systems.3.2.19 market package, nservice-oriented perspective tothe National ITS architecture including subsystems (withapplicable equipment packa
40、ges) and architecture flows.3.2.20 metadata, ndata about data, or more precisely,definitional and descriptive data that provide information aboutor documentation of other data managed within an applicationor environment.3.2.21 metadata element, nlogically primitive item ofmetadata that forms the bas
41、ic building block for this metadataspecification.3.2.22 missing data, none or more fields in a data recordthat have no valid values because of a variety of reasons suchas improper functioning of the data collection device, failedcommunications, or shortcomings in subsequent processingprograms.3.2.23
42、 National ITS architecture, ndocument preparedthrough the sponsorship of the U.S. Department of Transpor-tation (DOT) that provides a common structure for the designof intelligent transportation systems giving a frameworkaround which multiple design approaches can be developed bydefining: (a) the fu
43、nctions that shall be performed to implementa given user service; (b) the physical entities or subsystems inwhich these functions reside; (c) the interfaces/informationflows between the physical subsystems; and (d) the communi-cation requirements for the information flows.3.2.24 near-real-time data,
44、 ndata that is collected,processed, aggregated very close in time, usually withinseconds or just a few minutes, to the actual time period orinstance when the phenomenon being measured or observedactually occurred.3.2.25 original source data, ndata as received by a centerthat is a source for an archi
45、ve.3.2.26 probe vehicle, nvehicle equipped with equipmentthat allows detection of the vehicle in time and space.3.2.27 quality control, nsystem or process for obtaining,maintaining, and verifying a desired level of quality in a dataset, process, or service by careful planning and design, the useof p
46、roper equipment, continued inspections, and taking correc-tive actions where and when required.3.2.28 resolution, nlevel of spatial or temporal detail oradministrative classification at which a particular data elementis collected, archived retrieved, or both, from an ADMS; thatis, lane-by-lane versu
47、s detector station or intersection ap-proach; a 20-s versus a 15-min time period; or a particularnamed city versus the generic term of city.3.2.29 spot speed, nspeed measured by roadway detectiondevices as vehicles traverse a short longitudinal length ofhighway.3.2.30 stakeholder, nperson, party, or
48、 private or publicagency or organization that is interested in one or more aspectsof how ITS-generated data is collected, archived, analyzed, orretrieved from an existing or proposed ADMS.3.2.31 storage media, nsystems upon which the archive ordata set, summaries, or displays extracted from it are k
49、ept foruse by the ADMS or for distribution to various users orstakeholders.3.2.32 terminators, nfunctions that basically take placeoutside of the National ITS architecture but that interfere withone or more subsystems of the National ITS architecture bysharing data or information or both with them.3.2.33 traffc management center (TMC), nlocationequipped with roadway surveillance technology that is used todetect traffic problems and implement traffic control strategies.3.2.34 transformed data, nvalues created by combiningdata with other data
