1、SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirelyvoluntary, and its applicability and suitability for any particular use, including any patent infringement arising therefro
2、m, is the sole responsibility of the user.”SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions.TO PLACE A DOCUMENT ORDER: (724) 776-4970 FAX: (724) 776-0790SAE WEB ADDRESS http:/www.s
3、ae.orgCopyright 2000 Society of Automotive Engineers, Inc.All rights reserved. Printed in U.S.A.SURFACEVEHICLE400 Commonwealth Drive, Warrendale, PA 15096-0001INFORMATIONREPORTJ2373ISSUEDAPR2000Issued 2000-04Stakeholders Workshop Information ReportForewordThis SAE Information Report describes result
4、s of three workshops at which Public Sector participantsdiscussed concepts and requirements for ITS Referencing Datums. The Intelligent Transportation Systems (ITS)Datum concept, developed by Oak Ridge National Laboratory (ORNL), has been advanced and promoted throughtechnical R it isextracted from
5、the ORNL document “Intelligent Transportation Systems Datum Public Sector RequirementsWorkshop Report, August 24, 1998, C. Goodwin, F. Latham, D. Siegel and S. Gordon,” for a project sponsored bythe U.S. Federal Highway Administration (FHWA). DISCLAIMER: Any opinions or recommendations contained int
6、his report reflect the opinions of the authors and not necessarily those of the SAE Map Database Committee.TABLE OF CONTENTS1. Scope . 32. References . 32.1 Applicable Documents 42.2 Related Publications. 43. Definitions. 54. Introduction. 85. Problem Statement. 86. Project History 97. Interoperabil
7、ity Proposals. 107.1 A Common DataBase. 107.2 Interoperability Standards 107.3 Spatial Data Interoperability TestBed. 11SAE J2373 Issued APR2000-2-8. Related Activities 128.1 NCHRP Linear Referencing Programs .128.2 NSDI Framework Transportation Identification Standard .128.3 USGS128.4 International
8、 Standardization Activities.138.5 Public and Private Roles in ITS Datum Creation and Use139. Current Project Goal .1410. Next Steps 1511. Strawman ITS Datum Design Decisions.1611.1 ITS Datum Issue - Topological enforcement 1611.2 ITS Datum Issue - Node Density 1711.3 ITS Datum Issue: Node Replacemen
9、t Rules 1811.4 ITS Datum Issue: Node and Link IDs .1911.5 ITS Datum Issue: Road Names and Aliases 2012. Workshop Summary .2012.1 Summary of Requirements .2012.2 Technical Requirements .2112.3 Lane requirements2212.4 Other Requirements .2213. Outstanding Issues .23Appendix A Deploying ITS Map Databas
10、e Interoperability Standards.24A.1 Introduction .24A.2 Workshop Structure 25A.3 Workshop Objectives25A.4 Workshop Format .25A.5 Presentations25A.6 Open Comments.32A.7 Breakout Sessions33A.8 Technical Questions: 33A.9 Institutional Questions: .33A.10 Technical Group .34A.11 Institutional Group.35Appe
11、ndix B Public Sector ITS Datum Requirements Workshop I38B.1 Introduction .38B.2 Proceedings of the Breakout Group for GIS-T and Planning40B.3 Problem definition .40B.4 Proceedings of the Breakout Group for Transit 41B.5 Transit Analysis - Ridership Forecasting 43B.6 Transit Analysis - Market Analysi
12、s43B.7 Facilities and Land Management43B.8 Customer Information Services 44B.9 Scheduling 44B.10 Dispatch and Monitoring .45B.11 Information Exchange With Other Agencies.45B.12 Proceedings of the Breakout Group for Public Safety Highway Incident46B.13 Proceedings of the Breakout Group on Technical I
13、ssues.47SAE J2373 Issued APR2000-3-B.14 Administration .51B.15 Budgeting52B.16 Edits52B.17 Quality Hierarchy 52Appendix C Public Sector ITS Datum Requirements Workshop II.53C.1 Introduction .53C.2 State Issues Breakout Group55C.3 Technical Issues Breakout Group.56C.4 Transit Breakout Group 58C.5 Inc
14、ident Management/Emergency Management Breakout Group59C.6 Federal Breakout Group .60Figure 1 - ITS Datum Recommended Practices and Tools as a Foundation Specification for Federal Activities.15Figure 2 - Inserting new nodes17Figure 3 - ITS Datum nodes at Road Centerline Intersections .19Figure B1 - T
15、opology enforced 50Figure B2 - Topology not enforced 50Figure B3 - Hierarchical Development.51Table B1 - Comparison of Treatment of Structure .491. ScopeThis SAE Information Report describes requirements gathering workshops for Public Sector use ofITS Referencing Datums.2. References2.1 Applicable P
16、ublicationsThe following standards contain provisions which are referenced in thisInformation Report. At the time of publication, the editions indicated were valid. 2.1.1 SAE PUBLICATIONSAvailable from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.SAE J1746ISP-Vehicle Location Referencing S
17、tandardSAE J2374Location Referencing Message Specification2.1.2 INTELLIGENT TRANSPORTATION SOCIETY (ITS) OF AMERICA DOCUMENTSAvailable from ITS America, 400Virginia Avenue, SW, Suite 800, Washington, DC 20024-2730, U.S. National Architecture Programdocuments on world-wide web, http:/www.itsa.org/arc
18、hdocs/national.html Intellligent Transportation Systems Datam Public Sector Requirements Workshop Report, August 24,1998, C. Goodwin, F. Latham, D. Siegel, and S. Gordon 2.2 Related PublicationsThe following publications are provided for information purposes only and are not arequired part of this d
19、ocument.2.2.1 FEDERAL HIGHWAY ADMINISTRATION DOCUMENTSAvailable from U.S. DOT, FHWA, Office of Safety andTraffic Operations, ITS Research Division, HSR 10, 6300 Georgetown Pike, McLean, VA 22101.Task B: Spatial Data Interoperability Protocol For ITS Project Location Reference Message ProtocolPrelimi
20、nary Specification, February 29, 1996, Goodwin, C., Siegel, D. and Gordon, S.Task B: Spatial Data Interoperability Protocol For ITS Project Location Reference MessageSpecification: Final Design, June 28, 1996, Goodwin, C., Siegel, D. and Gordon, S.Task B: Spatial Data Interoperability Protocol for I
21、TS Project Location Reference Message Specification:Revision A, September 18, 1996, Goodwin, C., Siegel, D. and Gordon, S.SAE J2373 Issued APR2000-4-Task B: Spatial Data Interoperability Protocol for ITS Project Location Reference Message Specification:Revision B (MDI), May 22, 1997, Goodwin, C., Si
22、egel, D. and Gordon, S.Task C: Spatial Data Interoperability Protocol For ITS Project The ITS Datum Preliminary Data Structureand Content, February 25, 1996, Goodwin, C., Siegel, D. and Gordon, S.Task C: Spatial Data Interoperability Protocol For ITS Project ITS Datum Final Design Report, June 28,19
23、96, Goodwin, C., Siegel, D. and Gordon, S.Task A3: Nationwide Map Database and Location Referencing System Project Functional Requirementsfor National Map Databases for ITS, December 31, 1994, Goodwin, C., Xiong, D. and Gordon, S.Task B3: Nationwide Map Database and Location Referencing System Proje
24、ct Technical Requirementsfor National Map Databases for ITS, July 31, 1995, Goodwin, C., Gordon, S.Task F1: Nationwide Map Database and Location Referencing System Project Recommendation forLocation Referencing for ITS, December 31, 1994, Goodwin, C., Xiong, D. and Gordon, S.2.2.2 NATIONAL INSTITUTE
25、 OF SCIENCE AND TECHNOLOGY (NIST) DOCUMENTAvailable from NIST, FIPS PUB 173,U.S. Government Printing Office, National Technical Information Service U.S. Department of Commerce,Springfield VA 22161FIPS PUB 173 - Spatial Data Transfer Standard (SDTS), 19922.2.3 INTELLIGENT TRANSPORTATION SOCIETY (ITS)
26、 OF AMERICA DOCUMENTSAvailable from ITS America, 400Virginia Avenue, SW, Suite 800, Washington, DC 20024-2730U.S. National Architecture Program documents on world-wide web - http:/www.itsa.org/archdocs/national.html2.2.4 TRANSPORTATION RESEARCH BOARD PUBLICATIONAvailable from Transportation Research
27、 Board, 2101Constitution Ave, NW, Washington, DC 20418Transportation Research Circular 412 Primer on Intelligent Vehicle Highway Systems, 1993.2.2.5 OTHER PUBLICATIONSCherveny, Kevin, 1997, “Technical Response to ITS Datum Prototype Final Design Report,” Memorandumdated April 1, 1997, 6ppFletcher, D
28、avid, Espinoza, John, Mackoy, R.D., Gordon, Stephen, Spear, Bruce, and Vonderohe, Alan;“The Case for a Unified Linear Reference System; Proceedings, Enterprise Location ReferencingSystems: Policies, Procedures and Standards for Implementation Workshop;” Salt Lake City, Utah;July 1996Goodwin, Cecil W
29、. H., Dave Siegel, Stephen R. Gordon, and Demin Xiong; “Recommendation for LocationReferencing for ITS Needs,” Task F1: Nationwide Map Database and Location Referencing SystemProject, United States Department of Transportation, Federal Highway Administration Office of Safetyand Traffic Operations, I
30、TS Research Division, Contract DTFH61-91-Y-30066, Draft, June 30, 1995,78 ppGoodwin, Cecil W. H., David Siegel, and Stephen R. Gordon; “Location Reference Message Specification:Final Design,” Task B: Spatial Data Interoperability Protocol For ITS Project, United StatesDepartment of Transportation, F
31、ederal Highway Administration Office of Safety and Traffic Operations,ITS Research Division, Contract 61-94-Y-00001, Draft, June 28, 1996, 40 ppGordon, Stephen R., Cecil W.H. Goodwin, and Demin Xiong, 1994; “Final Report on Status of Spatial/MapDatabases,” Report by Oak Ridge National Laboratory for
32、 U.S.DOT, FHWA, Office of Safety andTraffic Operations IVHS Research Division project Nationwide Map Database and LocationReferencing System, June, 1994. 133 ppHaas, R. P., J.W. Lau, C.W. Goodwin, S.R. Gordon; “Location Referencing Message Specification TestReport” Version 1.0, July 23, 1998SAE J237
33、3 Issued APR2000-5-Lerner-Lam, Eva, W. Todd Smith, Joseph R. Francica, and Ajay Rathi; “Digital Map and Spatial DatabaseRequirements for ATMS,” in “Surface Transportation: Mobility, Technology, and Society,” Proceedingsof the IVHS America 1993 Annual Meeting, Washington, D.C., April 14-17, 1993, pp.
34、 560-568Siegel, David, Cecil W. H. Goodwin, and Stephen R. Gordon; “ITS Datum Final Design Report”, Task C:Spatial Data Interoperability Protocol For ITS Project, United States Department of Transportation,Federal Highway Administration Office of Safety and Traffic Operations, ITS Research Division,
35、Contract 61-94-Y-00001, Review Draft, June 28, 1996, 38 ppUTEERC (The University of Tennessee Energy, Environment, and Resources Center), ALK AssociatesInc., Oak Ridge National Laboratory, and Viggen Corporation; “Meeting National ITS Spatial DataNeeds”, Task C2: Nationwide Map Database and Location
36、 Referencing System Project, United StatesDepartment of Transportation, Federal Highway Administration Office of Safety and Traffic Operations,ITS Research Division, Contract DTFH61-91-Y-30066, Review Draft Final Report, September 29,1995, 119 ppVITAL (Vehicle Intelligence Testing “Results of a Work
37、shop on a Generic Data Model for Linear ReferencingSystems;” National Cooperative Highway Research Program Project 20-27(2): Development ofSystem and Application Architectures for Geographic Information Systems in Transportation, 1995Vonderohe, Alan and Hepworth, Todd; “A Methodology for Design of a
38、 Linear Referencing System forSurface Transportation;” Sandia National Laboratories Project AT-4567, December 19963. Definitions3.1 AltitudeElevation above or below a reference datum, as defined in FIPSPUB 70-1(NIST, 1992); the z-valuein a spatial address. 3.2 AVLAutomatic Vehicle Location by use of
39、 technologies such as GPS.3.3 BandwidthThe portion (frequency range) of the electromagnetic spectrum available to a communicationschannel.3.4 CoordinatesPairs of numbers expressing horizontal distances along orthogonal axes; alternatively, tripletsof numbers measuring horizontal and vertical distanc
40、es. 3.5 DatumA set of parameters and control points used to accurately define the three-dimensional shape of theEarth (e.g., as an ellipsoid). The corresponding datum is the basis for a planar coordinate system. 3.6 DMIDistance Measuring Instrument. A device that measures as-driven distance along a
41、roadway,performing the function of a precise vehicle odometer.3.7 Geodetic DatumA mathematical model of the Earths shape. A geometric set of five quantities whichserves as a locational reference or base for other quantities. The five quantities are the latitude and longitudeof an initial point, the
42、azimuth of a line from this point and two constants necessary to define the terrestrialspheroid. 3.8 GISGeographic Information System. A computer-based system for the storage, retrieval, display, andanalysis of spatial data.3.9 GIS-TGeographic Information Systems in TransportationSAE J2373 Issued AP
43、R2000-6-3.10 GPSGlobal Position System. A positioning system that relies on TDOA (time-distance of arrival)measurement of signals from GPS satellites to determine geographic location and other dynamic parametersfor a receiver.3.11 ILOCIntersection Location. A proposed European method of location ref
44、erencing that specifies anintersection location based on geographic coordinates and ancillary roadway information.3.12 Information Service Provider (ISP)In the context of the LRMS, a public or private entity which may beresponsible for gathering, fusing, analyzing, and/or reporting transportation re
45、lated information to users,including vehicles and non-mobile users.3.13 InterpolationA mathematical or geometric method of determining the value of a variable between two pointswith known values.3.14 IntersectionIn GDF, a complex feature, made up of a set of features such as Road Elements andJunctio
46、ns. An intersection may be a simple junction of two roads, or may consist of more than two roads andentrance and exit ramps. Intersections may be planar (topologically connected in the same plane) or non-planar (not topologically connected), such as a flyover. 3.15 IOMIntersection Object Model. An I
47、TS Datum term referring to a complex object model of an intersection,similar to a GDF complex intersection feature.3.16 ISOInternational Standards Organization.3.17 ISO APIThe ISO Application Programming Interface standard for data access to ITS databases.3.18 ISO GDFThe ISO Geographic Data File sta
48、ndard for exchange of ITS databases.3.19 ISO PSFThe ISO Physical Storage Format standard for storage of ITS databases on physical media.3.20 ITS DatumA set of well-known and located ground control points on transportation networks.3.21 ITS User ServicesThe classification of ITS user applications int
49、o 31 categories, such as IncidentManagement (IM).3.22 JunctionIn GDF, a feature that bounds road elements (or ferry connections). A road element is alwaysbounded by exactly two junctions. A junction feature represents the physical connection between adjoiningroad elements.3.23 Linear datumA set of well-known and located points used to register linear referencing networks to oneanother.3.24 LinkA topological connection between two nodes. A link may contain additional intermediate coordinates(shape points) to better repres
