ASTM E2259-2003a(2011) Standard Guide for Archiving and Retrieving ITS-Generated Data《智能运输系统产生数据的存档和重新获取的标准指南》.pdf

《ASTM E2259-2003a(2011) Standard Guide for Archiving and Retrieving ITS-Generated Data《智能运输系统产生数据的存档和重新获取的标准指南》.pdf》由会员分享，可在线阅读，更多相关《ASTM E2259-2003a(2011) Standard Guide for Archiving and Retrieving ITS-Generated Data《智能运输系统产生数据的存档和重新获取的标准指南》.pdf（21页珍藏版）》请在麦多课文档分享上搜索。

1、Designation: E2259 03a (Reapproved 2011)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 of interestedand knowledgeable stakeholders develop standards that can be used by a wide variety of public andprivate organizations in developingArchived Data Management Systems (ADMS), which can be usedto facilitate data sharing and i

5、nteroperability 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 archiv

6、ing 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 greatera

7、wareness 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 effe

8、ctively 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 u

9、sed in the contextof an Archived Data Management System in general, or a particular deployment of one, then the Sstands for System. It is also noted that Appendix X1 to this guide presents relationships of the guideto several other activities and standards.This guide follows the intent of all guides

10、 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 of

11、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 pr

12、ofessional 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 uniq

13、ue 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.1This guide is under the jurisdiction of ASTM Committee E17 Current edition approved June 1, 2011. Published July 2011. Originally ap

14、proved1Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.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 Tr

15、anspor-tation Systems-generated data. The scope of this guide antici-pates incremental or modular implementation of an ADMS,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 budgetr

16、esources do not always allow practitioners to follow a moredesirable course of action and that during interim periods theability 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 al

17、l-inclusive. Users ofthis guide are allowed, and indeed encouraged, to exceed thedesired practices in one or more of several 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

18、may necessitate exceedingthe desired practice. Another example is that some implemen-tations may want to foster innovations 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

19、retrieval processes, or both, wouldfacilitate such innovations or research, or both.Athird exampleis that some organizations 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 av

20、ailable to their planning or operations unitsto use in their day-to-day activities.2. Referenced 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 Defini

21、tions:3.1.1 The ASTM publication of the Committee on Defini-tions; Terminology E867 maintains a complete 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 l

22、ike items into acategory; for example, adding together 30-s traffic volumecounts, or averaging speeds 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, n

23、the resultant set of aggregated dataassociated with an aggregating process.3.2.3 archive, nthe organized collection of data and in-formation derived from selected ITS-generated data flows andother data sources.3.2.4 archive structure metadata, ndescriptive data aboutthe structure of the data archive

24、 itself and of the data andinformation in the archive that facilitate use of the archive.3.2.5 archived data administrator, nthe person who isresponsible for the day-to-day operations and long-term man-agement of an ADMS.3.2.6 archived data management subsystem (ADMS), nasubsystem of the National IT

25、S Architecture that provides ameans for several organizations to collect, store, and subse-quently, analyze and retrieve data from ITS data sources,usually by way of one or more ITS centers.3.2.7 archived data management system, (ADMS), nthisis a system that is a specific implementation of an ADMSwi

26、thin the context of a local, regional, or statewide ITSarchitecture.3.2.8 archived data user service, (ADUS), none of theITS user services that defines the scope of the National ITSArchitecture with regard to archiving and retrieving ITS-generated data.3.2.9 archiving, vcollecting and actively manag

27、ing origi-nal source and other data with the intent of saving the data aswell as associated metadata.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

28、 by individuals or groups of people and that issuitable for communication, interpretation, or processing byhumans or machines.3.2.11 data collection system metadata, ndata about theconditions and procedures under which original source datawere observed, surveyed, measured, gathered, or collected, as

29、well as about the equipment that was used.3.2.12 data dictionary, nan information construct thatdescribes 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.13 data element, na data item that is a basi

30、c 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 ofinterest.3.2.14 data logging, vto capture a stream of near-real-time data as it passes through a transportation ma

31、nagementcenter.3.2.15 data mart, na National ITS Architecture marketpackage in which an archiving system collects and archivesoperational data from one organizational source; it is analogousto a library whose collection is acquired from a singlepublisher.in 2003. Last previous edition approved in 20

32、03 as E2259 - 03a. DOI: 10.1520/E2259-03A(2011).2For 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 ASTM website.3Available fr

33、om Institute of Electrical and Electronic Engineers, Inc., 345 E. 7thSt., New York, NY 10017.E2259 03a (2011)23.2.16 data quality, nthe fitness of data for all purposesthat require it. Examples of data quality measures includeaccuracy, completeness, coverage, and timeliness.3.2.17 data sources, nthe

34、 systems that provide data.3.2.17.1 DiscussionTraffic count data can be retrievedfrom traffic management centers or air temperature data can beretrieved from surface transportation weather service provid-ers.3.2.18 data warehouse, na National ITS Architecturemarket package in which physically distri

35、buted data sources(a) contribute to a central clearinghouse, where each datasource is locally managed and (b) exchange multipletransportation-related data; it is analogous to a library whosecollection is acquired from multiple publishers.3.2.19 database, na collection of related data typicallyorgani

36、zed in a computerized record keeping 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.19.1 DiscussionIn addition, as noted by Smith (1)4,itshould (a) represent some aspect of the real world, organiza-tion, or

37、enterprise, (b) that is logically related and has inherentmeaning and (c) be designed, built, and populated for a specificpurpose.3.2.20 database management system (DMBS), na set ofprograms that manipulate and maintain a database whileproviding independence from an application.3.2.21 equipment packa

38、ge, nthe building blocks of ITSsubsystems that perform a specific function.3.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

39、processingprograms.3.2.23 expired data, nthe status assigned to a set of data,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

40、erroneous values.3.2.25 information, nthe result of processing one or morepieces 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, s

41、ummarization, and retrieval ofspecific data or information.3.2.27 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, and use oftransp

42、ortation systems.3.2.28 log file, na usually free form set of text or data, orboth, 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

43、 subsystems (withapplicable equipment packages) and architecture flows.3.2.29.1 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

44、description ofinstance data, including the format and characteristics ofinstance 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

45、 guide as (a) archive structure metadata (b)processing documentation metadata and (c) 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, failedcommunic

46、ations, or shortcomings in subsequent processingprograms.3.2.32 National ITS 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

47、developed by defining: (a) the functions thatmust be performed to implement a given user service (b) thephysical entities or subsystems where these functions reside (c)the interfaces/information flows between the physical subsys-tems and (d) the communication requirements for the informa-tion flows.

48、3.2.33 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 time period or instancewhen the phenomenon being measured or observed actuallyoccurred.3.2.34 original source data, ndata as received by a center

49、that is a source for an archive.3.2.35 persistence history, ndocumentation of one ormore modifications made to a set of data that can be used totrace back the specific procedures that were applied and whenthat was done and that becomes part of the processingdocumentation metadata.3.2.36 processing documentation metadata, ninformationthat describes the processes applied to data from originalsource data through to storage in an ADMS.3.2.37 quality control, na system or process for obtaining,maintaining, and verifying a desired level of quality i