ASTM E2259-2003a(2018) Standard Guide for Archiving and Retrieving Intelligent Transportation Systems-Generated Data.pdf

1、Designation: E2259 03a (Reapproved 2018)Standard Guide forArchiving and Retrieving Intelligent Transportation Systems-Generated Data1This standard is issued under the fixed designation E2259; the number immediately following the designation indicates the year oforiginal adoption or, in the case of r

2、evision, the year of last revision. A number in parentheses indicates the year of last reapproval. Asuperscript epsilon () indicates an editorial change since the last revision or reapproval.INTRODUCTIONThis guide has been developed within the framework of developing standards of ASTMInternational a

3、nd thus the format, structure, as well as the review, balloting, and approval processesconform to those specified by ASTM International. These processes may differ in their particularsfrom those used by other standards development organizations associated with developing ITSstandards. However, their

4、 general intent is the samethat of having a representative group ofinterested and knowledgeable stakeholders develop standards that can be used by a wide variety ofpublic and private organizations in developing Archived Data Management Systems (ADMS), whichcan be used to facilitate data sharing and

5、interoperability among systems.This guide has been prepared with various ITS data stakeholder groups in mind, that is, data users,ADMS policy makers,ADMS developers, andADMS administrators. To data users andADMS policymakers, it can provide a general understanding about technical approaches to archi

6、ving and retrievingITS-generated data. For the ADMS developer group, which includes data application softwaredevelopers, this guide can be a bench-marking reference against which existing ADMS could befurther refined or improved with broader perspective. Further, it is also intended to bring greater

7、awareness and consistency in the use and understanding of concepts and use of terminology by theADMS developers. Finally, the ADMS administrators, whose main function includes collecting,archiving, managing, and distributing ITS data, can find practical guidance and approaches from thisguide for eff

8、ectively operating their ADMS.It should be noted that there is a subtle distinction in the use of the acronym ADMS throughout thisguide. When it is being used in the context of the National ITS Architecture, the S stands for asubsystem of the National ITS Architecture. When the acronym ADMS is being

9、 used in the contextof an archived data management system in general, or a particular deployment of one, then the S standsfor system. It is also noted that Appendix X1 to this guide presents relationships of the guide to severalother activities and standards.This guide follows the intent of all guid

10、es prepared within the ASTM International framework. Inparticular, it suggests approaches, offers an organized collection of information, or proposes series ofoptions or instructions that give direction without recommending a specific course of action. Guidesare also intended to increase awareness o

11、f potential users of the standards of the available techniquesin the subject area, while at the same time providing information from which subsequent practices canbe derived. This document, however, cannot replace a broad-based education or pertinent experienceand should be used in conjunction with

12、professional judgment. Not all aspects of this guide may beapplicable in all circumstances. This guide is not intended to represent or replace the standard of careby which one judges the adequacy of a given professional service, nor should this document be appliedwithout consideration of the many un

13、ique aspects of a project. The word standard in the title of thisdocument means only that the document has been approved through the ASTM Internationalconsensus process.Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United StatesThis international

14、 standard 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.1

15、1. Scope1.1 This guide covers desired approaches to be consideredand followed in planning, developing, and operating specificADMS for the archiving and retrieval of Intelligent Transpor-tation Systems-generated data. The scope of this guide antici-pates incremental or modular implementation of an AD

16、MS,which over time and with a series of investment of resourceswill approach or exceed desired practice. However, it isrecognized that programmatic constraints of time and budgetresources do not always allow practitioners to follow a moredesirable course of action, and that during interim periods th

17、eability to implement a particular fully functioning system maybe less than desired.1.2 The desired approaches described in this guide arefoundational and are not intended to be all-inclusive. Users ofthis guide are allowed, and indeed encouraged, to exceed thedesired practices in one or more of sev

18、eral ways. An exampleof one way is that to address and satisfy the particular needsand requirements of some of the intended users and stakehold-ers for a particular implementation may necessitate exceedingthe desired practice. Another example is that some implemen-tations may want to foster innovati

19、ons and research into newmethods and procedures related to the overall implementationof a particular ITS activity. Part of that may be the recognitionthat specialized archiving or retrieval processes, or both, wouldfacilitate such innovations or research, or both.Athird exampleis that some organizat

20、ions may simply have more resources toinvest in activities such as archiving and retrieval systems andmay choose to have more quantities or higher quality of dataand information available to their planning or operations unitsto use in their day-to-day activities.1.3 This international standard was d

21、eveloped in accor-dance with internationally recognized principles on standard-ization established in the Decision on Principles for theDevelopment of International Standards, Guides and Recom-mendations issued by the World Trade Organization TechnicalBarriers to Trade (TBT) Committee.2. Referenced

22、Documents2.1 ASTM Standards:2E867 Terminology Relating to Vehicle-Pavement Systems2.2 IEEE Standard:3IEEE 1489 Standard for Data Dictionaries for IntelligentTransportation Systems3. Terminology3.1 Definitions:3.1.1 The ASTM publication of the Committee on Defini-tions; Terminology E867 maintains a c

23、omplete list of termi-nology some of which are applicable to this guide and byconvention are not repeated here.3.2 Definitions of 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 sp

24、eeds from lane-by-lane detectors thatare parts of 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, nthe resultant set of aggregated dataassociated with an aggregating process.3.2.3 archive, nthe or

25、ganized collection of data and infor-mation derived from selected ITS-generated data flows andother data sources.3.2.4 archived data administrator, nthe person who isresponsible for the day-to-day operations and long-term man-agement of an ADMS.3.2.5 archived data management subsystem (ADMS), nasubs

26、ystem of the National ITS Architecture that provides ameans for several organizations to collect, store, andsubsequently, analyze and retrieve data from ITS data sources,usually by way of one or more ITS centers.3.2.6 archived data management system, (ADMS), nthis isa system that is a specific imple

27、mentation of an ADMS withinthe context of a local, regional, or statewide ITS architecture.3.2.7 archived 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.8 archive structure

28、metadata, ndescriptive data aboutthe structure of the data archive itself and of the data andinformation in the archive that facilitate use of the archive.3.2.9 archiving, vcollecting and actively managing origi-nal source and other data with the intent of saving the data aswell as associated metada

29、ta.3.2.10 data, na quantitative or qualitative representationthat is observed, measured, collected, or gathered that charac-terizes some static or dynamic attribute of the physical world orthe use of it by individuals or groups of people and that issuitable for communication, interpretation, or proc

30、essing byhumans or machines.3.2.11 database, na collection of related data, typicallyorganized in a computerized recordkeeping system that is partof a system whose purpose is to maintain the data andinformation derived from it so it can be made available for use.3.2.11.1 DiscussionIn addition, as no

31、ted by Smith (1),4itshould (1) represent some aspect of the real world,organization, or enterprise; (2) that is logically related and hasinherent meaning; and (3) be designed, built, and populated fora specific purpose.1This guide is under the jurisdiction of ASTM Committee E17 and is the directresp

32、onsibility of Subcommittee E17.52 on Traffic Monitoring.Current edition approved Sept. 1, 2018. Published September 2018. Originallyapproved in 2003. Last previous edition approved in 2011 as E2259 03a (2011).DOI: 10.1520/E2259-03AR18.2For referenced ASTM standards, visit the ASTM website, www.astm.

33、org, orcontact ASTM Customer Service at serviceastm.org. For Annual Book of ASTMStandards volume information, refer to the standards Document Summary page onthe ASTM website.3Available from Institute of Electrical and Electronic Engineers, Inc., 345 E. 7thSt., New York, NY 10017.4The boldface number

34、s in parenthesis refer to the list of references at the end ofthe standard.E2259 03a (2018)23.2.12 database management system (DMBS), na set ofprograms that manipulate and maintain a database whileproviding independence from an application.3.2.13 data collection system metadata, ndata about thecondi

35、tions and procedures under which original source datawere observed, surveyed, measured, gathered, or collected, aswell as about the equipment that was used.3.2.14 data dictionary, nan information construct thatdescribes the particular data stored in a database, typically interms of a common set of a

36、ttributes that includes the meaning,concept, and use; see IEEE 1489.3.2.15 data element, na data item that is a basic buildingblock of a data dictionary that is a formal representation ofsome single unit of information of interest with a singularinstance value at any point in time about some entity

37、ofinterest.3.2.16 data logging, vto capture a stream of near-real-time data as it passes through a transportation managementcenter.3.2.17 data mart, na National ITS Architecture marketpackage in which an archiving system collects and archivesoperational data from one organizational source; it is ana

38、logousto a library whose collection is acquired from a singlepublisher.3.2.18 data quality, nthe fitness of data for all purposesthat require it. Examples of data quality measures includeaccuracy, completeness, coverage, and timeliness.3.2.19 data sources, nthe systems that provide data.3.2.19.1 Dis

39、cussionTraffic count data can be retrievedfrom traffic management centers, or air temperature data can beretrieved from surface transportation weather service provid-ers.3.2.20 data warehouse, na National ITS Architecturemarket package in which physically distributed data sources(1) contribute to a

40、central clearinghouse, where each datasource is locally managed, and (2) exchange multipletransportation-related data; it is analogous to a library whosecollection is acquired from multiple publishers.3.2.21 equipment package, nthe building blocks of ITSsubsystems that perform a specific function.3.

41、2.22 erroneous data, none or more pieces of data in adata set that has incorrect values due to a variety of reasonssuch as improper functioning of the data collection device,miscommunications, or shortcomings in subsequent processingprograms.3.2.23 expired data, nthe status assigned to a set of data

42、,summary statistics, or information that is no longer current orvalid and needs to be replaced.3.2.24 imputation, nthe act of putting onto a data setestimated values for that data to fill in for missing values or toreplace erroneous values.3.2.25 information, nthe result of processing one or morepie

43、ces of data to produce a meaningful and useful statistic orindicator for users.3.2.26 integration, nthe result of blending compatibledata sources into a composite data set has a unity or wholenessfor purposes of analysis, summarization, and retrieval ofspecific data or information.3.2.27 intelligent

44、 transportation systems (ITS), nsystemsthat apply modern sensing, communication, computing,analysis, or display technologies, or a combination thereof, toone or more aspects of the operations, management, and use oftransportation systems.3.2.28 log file, na usually freeform set of text or data, orbo

45、th, that sequentially lists or enumerates events, many ofwhich may be independent, while some may be chained orinterrelated3.2.29 market package, na service-oriented perspective tothe National ITS Architecture, including subsystems (withapplicable equipment packages) and architecture flows.3.2.29.1

46、DiscussionThe market packages relevant toADUS are ITS Data Mart, ITS Data Warehouse, and ITSVirtual Data Warehouse.3.2.30 metadata, nloosely has been defined as data aboutdata but is more tightly defined as the detailed description ofinstance data, including the format and characteristics ofinstance

47、 data, where “instance data” is defined by Tannenbaum(2) as “that which is input into a receiving tool, application,database, or simple processing engine.”3.2.30.1 DiscussionThree categories of metadata are de-fined in this guide as: (1) archive structure metadata, (2)processing documentation metada

48、ta, and (3) data collectionsystem metadata.3.2.31 missing data, none or more fields in a data recordthat has no valid values due to a variety of reasons such asimproper functioning of the data collection device, failedcommunications, or shortcomings in subsequent processingprograms.3.2.32 national I

49、TS architecture, na document preparedthrough the sponsorship of the U.S. DOT that provides acommon structure for the design of intelligent transportationsystems, giving a framework around which multiple designapproaches can be developed by defining: (1) the functions thatmust be performed to implement a given user service, (2) thephysical entities or subsystems where these functions reside,(3) the interfaces/information flows between the physicalsubsystems, and (4) the communication requirements for theinformation flows.3.2.33 near-real-time data