ASTM E2259-2003a Standard Guide for Archiving and Retrieving ITS-Generated Data《归档和检索ITS生成数据的标准指南》.pdf

《ASTM E2259-2003a Standard Guide for Archiving and Retrieving ITS-Generated Data《归档和检索ITS生成数据的标准指南》.pdf》由会员分享，可在线阅读，更多相关《ASTM E2259-2003a Standard Guide for Archiving and Retrieving ITS-Generated Data《归档和检索ITS生成数据的标准指南》.pdf（21页珍藏版）》请在麦多课文档分享上搜索。

1、Designation: E 2259 03aStandard Guide forArchiving and Retrieving Intelligent Transportation Systems-Generated Data1This standard is issued under the fixed designation E 2259; the number immediately following the designation indicates the year oforiginal adoption or, in the case of revision, the yea

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

3、mat, 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 general intent

4、 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 developing Archived Data Management Systems (ADMS), which can be usedto facilitate data sharing and interoperabilit

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

6、rievingITS-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 greaterawareness an

7、d 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 effectively ope

8、rating 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 used in the

9、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 prepared w

10、ithin 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 potential u

11、sers 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 professional

12、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 unique aspects

13、of a project. The word Standard in the title of thisdocument means only that the document has been approved through the ASTM Internationalconsensus process.1. Scope1.1 This guide covers desired approaches to be consideredand followed in planning, developing, and operating specificADMS for the archiv

14、ing and retrieval of Intelligent Transpor-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 is1Copyright ASTM Internati

15、onal, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.recognized that programmatic constraints of time and budgetresources do not always allow practitioners to follow a moredesirable course of action and that during interim periods theability to implement a partic

16、ular 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 several ways. An exampleof one wa

17、y 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 innovations and research into newmetho

18、ds 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. A third exampleis that some organizations may simply have more re

19、sources 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.2. Referenced Documents2.1 ASTM Standards:2E 867 Terminology Rela

20、ting 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 E 867 maintains a complete list of termi-nology some of which are ap

21、plicable to this guide and byconvention are not repeated here.3.2 Definitions of Terms Specific to This Standard:3.3 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 thatare parts of t

22、raffic data counting station to be the total trafficvolume or average speed at that traffic counting station for a5-min time period.3.4 aggregation, nthe resultant set of aggregated dataassociated with an aggregating process.3.5 archive, nthe organized collection of data and infor-mation derived fro

23、m selected ITS-generated data flows andother data sources.3.6 archive structure 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.7 archived data administrator, nthe person who isresponsible fo

24、r the day-to-day operations and long-term man-agement of an ADMS.3.8 archived data management subsystem (ADMS), nasubsystem of the National ITS Architecture that provides ameans for several organizations to collect, store, and subse-quently, analyze and retrieve data from ITS data sources,usually by

25、 way of one or more ITS centers.3.9 archived data management system, (ADMS), nthis is asystem that is a specific implementation of an ADMS withinthe context of a local, regional, or statewide ITS architecture.3.10 archived data user service, (ADUS), none of the ITSuser services that defines the scop

26、e of the National ITSArchitecture with regard to archiving and retrieving ITS-generated data.3.11 archiving, vcollecting and actively managing origi-nal source and other data with the intent of saving the data aswell as associated metadata.3.12 data, na quantitative or qualitative representationthat

27、 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 processing byhumans or machines.3.13 data collection system metadata,

28、 ndata about theconditions and procedures under which original source datawere observed, surveyed, measured, gathered, or collected, aswell as about the equipment that was used.3.14 data dictionary, nan information construct that de-scribes the particular data stored in a database typically interms

29、of a common set of attributes that include the meaning,concept, and use; see IEEE 1489.3.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 a

30、bout some entity ofinterest.3.16 data logging, vto capture a stream of near-real-timedata as it passes through a transportation management center.3.17 data mart, na National ITS Architecture marketpackage in which an archiving system collects and archivesoperational data from one organizational sour

31、ce; it is analogousto a library whose collection is acquired from a singlepublisher.3.18 data quality, nthe fitness of data for all purposes thatrequire it. Examples of data quality measures include accuracy,completeness, coverage, and timeliness.3.19 data sources, nthe systems that provide data.3.1

32、9.1 DiscussionTraffic count data can be retrieved fromtraffic management centers or air temperature data can beretrieved from surface transportation weather service provid-ers.3.20 data warehouse, na National ITS Architecture mar-ket package in which physically distributed data sources (a)contribute

33、 to a central clearinghouse, where each data source is1This guide is under the jurisdiction of ASTM Committee E17 on Vehicle-Pavement Systems and is the direct responsibility of Subcommittee E17.54 onArchived Data User Service.Current edition approved July 10, 2003. Published November 2003. Original

34、lyapproved in 2003. Last previous edition approved in 2003 as E 2259 - 03.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

35、ASTM website.3Available from Institute of Electrical and Electronic Engineers, Inc., 345 E. 7thSt., New York, NY 10017.E 2259 03a2locally managed and (b) exchange multiple transportation-related data; it is analogous to a library whose collection isacquired from multiple publishers.3.21 database, na

36、 collection of related data typicallyorganized 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.21.1 DiscussionIn addition, as noted by Smith (1)4,itshould (a) represent some asp

37、ect of the real world, organiza-tion, or enterprise, (b) that is logically related and has inherentmeaning and (c) be designed, built, and populated for a specificpurpose.3.22 database management system (DMBS), na set ofprograms that manipulate and maintain a database whileproviding independence fro

38、m an application.3.23 equipment package, nthe building blocks of ITSsubsystems that perform a specific function.3.24 erroneous data, none or more pieces of data in a dataset that has incorrect values due to a variety of reasons such asimproper functioning of the data collection device, miscom-munica

39、tions, or shortcomings in subsequent processing pro-grams.3.25 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.26 imputation, nthe act of putting onto a data setestimated values for that data to fill

40、in for missing values or toreplace erroneous values.3.27 information, nthe result of processing one or morepieces of data to produce a meaningful and useful statistic orindicator for users.3.28 integration, nthe result of blending compatible datasources into a composite data set has a unity or whole

41、ness forpurposes of analysis, summarization, and retrieval of specificdata or information.3.29 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,

42、 management, and use oftransportation systems.3.30 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.31 market package, na service-oriented perspective tothe National IT

43、S Architecture, including subsystems (withapplicable equipment packages) and architecture flows.3.31.1 DiscussionThe market packages relevant to ADUSare ITS Data Mart, ITS Data Warehouse, and ITS Virtual DataWarehouse.3.32 metadata, nloosely has been defined as data aboutdata but is more tightly def

44、ined as the detailed 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.32.1 DiscussionThree categories of metadata a

45、re de-fined in this guide as (a) archive structure metadata (b)processing documentation metadata and (c) data collectionsystem metadata.3.33 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 devic

46、e, failedcommunications, or shortcomings in subsequent processingprograms.3.34 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 designapp

47、roaches can be 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 sub-systems and (d) the communication requirements for theinfor

48、mation flows.3.35 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.36 original source data, ndata as received by

49、 a centerthat is a source for an archive.3.37 persistence history, ndocumentation of one or moremodifications made to a set of data that can be used to traceback the specific procedures that were applied and when thatwas done and that becomes part of the processing documenta-tion metadata.3.38 processing documentation metadata, ninformationthat describes the processes applied to data from originalsource data through to storage in an ADMS.3.39 quality control, na system or process for obtaining,maintaining, and verifying a desired level of quali