1、Designation: E 2665 08Standard Specification forArchiving ITS-Generated Traffic Monitoring Data1This standard is issued under the fixed designation E 2665; the number immediately following the designation indicates the year oforiginal adoption or, in the case of revision, the year of last revision.
2、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-portation system (I
3、TS)-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 pro-cedural defini
4、tions 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 traffic operations and
5、planning stakeholders who need to understand the contents ofthe ADMS. 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 government
6、and 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 articulated nature of a
7、 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 system for ITS-ge
8、nerated 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 specification
9、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-time” traffic
10、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 specifies a logica
11、l 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 installation. All met
12、adataspecifications follow the requirements of Practice E 2468.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
13、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 standard calculation
14、sshould 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 thisdatabase. B
15、oth 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 unspecified road
16、network entity.1.11 This specification assumes the existence of a location-referencing system and does not specify a standard for locationreferencing.1This specification is under the jurisdiction ofASTM Committee E17 on Vehicle- Pavement Systems and is the direct responsibility of Subcommittee E17.5
17、4 onArchived Data User Service.Current edition approved Dec. 1, 2008. Published January 2009.2The boldface numbers in parentheses refer to the list of references at the end ofthis standard.1Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United Sta
18、tes.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 forinformation only and are not considered standard.1.13 This standard does not purport to address all of thesafety concerns, if a
19、ny, 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 regulatory limitations prior to use.2. Referenced Documents2.1 ASTM Standards:3E 867 Terminology Relating to Vehicle-Pavement Sy
20、stemsE 2259 Guide for Archiving and Retrieving IntelligentTransportation Systems-Generated DataE 2468 Practice for Metadata to Support Archived DataManagement Systems2.2 IEEE Standard:4IEEE 1489 Standard for Data Dictionaries for IntelligentTransportation Systems2.3 ITE Standard:5TM 1.03 Standard fo
21、r Functional Level Traffic ManagementData Dictionary (TMDD)2.4 ISO Standard:6ISO 14817 Transport Information and Control SystemsRequirements for an ITS/TICS Central Data Registry andITS/TICS Data Dictionaries2.5 NTCIP Standards:7NTCIP 1206 Object Definitions for Data CollectionNTCIP 1209 Data Elemen
22、t Definitions for TransportationSensor Systems (TSS)3. Terminology3.1 DefinitionsFor definitions relating to vehicle-pavement systems, see Terminology E 867.3.2 Definitions of Terms Specific to This Standard:3.2.1 aggregate, vto process or combine like items into acategory, for example, adding toget
23、her 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 at that traffic-counting station for a5-min time period.3.2.2 aggregation, nresultant set of aggregated data asso-ciated wit
24、h an aggregating process.3.2.3 archived data management subsystem, nsubsystemof the National ITS architecture that provides a means forseveral organizations to collect, store, and subsequently, ana-lyze and retrieve data from ITS data sources, usually by way ofone or more ITS centers.3.2.4 archived
25、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 data user service (ADUS), none of the ITSuser services that defines the scope of the National ITSarchitecture with regard to
26、 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-cally a column in a relational database or a property in anobject-oriented environment.3.2.7 compound element, ngroup or combi
27、nation ofgroups of metadata elements.3.2.7.1 DiscussionAll compound elements are describedby metadata elements either directly or through intermediatecompound elements. Compound elements represent higher-level concepts that cannot be represented by individual meta-data elements.3.2.8 data, nquantita
28、tive or qualitative representation thatis observed, measured, collected, or gathered that characterizessome static or dynamic attribute of the physical world or theuse of it by individuals or groups of people and is suitable forcommunication, interpretation, or processing by humans ormachines.3.2.9
29、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,concept, and use; see IEEE 1489.3.2.10 data element, ndata item that is a basic buildingblock of a data dictionary which is a form
30、al 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 for all purposes thatrequire them.3.2.11.1 DiscussionExamples of data quality measuresinclude accuracy, completeness, coverage
31、, 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, ncollection of related data typicallyorganized in a computerized record-keeping system that is partof a system whose purpose is to m
32、aintain the data andinformation derived 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 entity is asingle person, place, or thing about which data can be stored.In common terms, an entity can be represented by one or
33、 moretables in a relational database or an object in an object-orientedenvironment.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
34、 for that data to fill in for missing values or replaceerroneous values.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 AS
35、TM website.4Available from IEEE, Publications Office, 10662 Los Vaqueros Circle, P.O.Box 3014, 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 (ANS
36、I), 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.E26650823.2.17 integration, nresult of blending compatible datasources into a composite data set has a unity or wholeness forpurposes
37、 of analysis, summarization, and retrieval of specificdata or information.3.2.18 intelligent transportation systems (ITS), nsystemsthat apply modern sensing, communication, computing, analy-sis, or display technologies, or a combination thereof, to one ormore aspects of the operations, management, a
38、nd use oftransportation systems.3.2.19 market package, nservice-oriented perspective tothe National ITS architecture including subsystems (withapplicable equipment packages) and architecture flows.3.2.20 metadata, ndata about data, or more precisely,definitional and descriptive data that provide inf
39、ormation aboutor documentation of other data managed within an applicationor environment.3.2.21 metadata element, nlogically primitive item ofmetadata that forms the basic building block for this metadataspecification.3.2.22 missing data, none or more fields in a data recordthat have no valid values
40、 because of a variety of reasons suchas improper functioning of the data collection device, failedcommunications, or shortcomings in subsequent processingprograms.3.2.23 National ITS architecture, ndocument preparedthrough the sponsorship of the U.S. Department of Transpor-tation (DOT) that provides
41、 a common structure for the designof intelligent transportation systems giving a frameworkaround which multiple design approaches can be developed bydefining: (a) the functions that shall be performed to implementa given user service; (b) the physical entities or subsystems inwhich these functions r
42、eside; (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, ndata that is collected, pro-cessed, aggregated very close in time, usually within secondsor just a few minutes, to the actual tim
43、e period or instancewhen the phenomenon being measured or observed actuallyoccurred.3.2.25 original source data, ndata as received by a centerthat is a source for an archive.3.2.26 probe vehicle, nvehicle equipped with equipmentthat allows detection of the vehicle in time and space.3.2.27 quality co
44、ntrol, 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 proper equipment, continued inspections, and taking correc-tive actions where and when required.3.2.28 resolution, nlevel of spati
45、al or temporal detail oradministrative classification at which a particular data elementis collected, archived retrieved, or both, from an ADMS; thatis, lane-by-lane versus detector station or intersection ap-proach; a 20-s versus a 15-min time period; or a particularnamed city versus the generic te
46、rm 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 private or publicagency or organization that is interested in one or more aspectsof how ITS-generated data is collected, archive
47、d, analyzed, orretrieved from an existing or proposed ADMS.3.2.31 storage media, nsystems upon which the archiveor data set, summaries, or displays extracted from it are keptfor use by the ADMS or for distribution to various users orstakeholders.3.2.32 terminators, nfunctions that basically take pla
48、ceoutside 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 proble
49、ms and implement traffic control strategies.3.2.34 transformed data, nvalues created by combiningdata with other data or subjected to a methodology or math-ematical process such as logarithmic transformation, averag-ing; for example, annual average daily traffic, average speed bysegment, congestion indices, or equivalent single-axle loads.3.3 Acronyms:3.3.1 AADTannual average daily traffic3.3.2 AASHTOAmerican Association of State Highwayand Transportation Officials3.3.3 AAWDTaverage annual weekday traffic3.3.4 AAWETaverage annual weekend tr
