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-0001INFORMATIONREPORTJ2372ISSUEDDEC1999Issued 1999-12Field Test Analysis Information ReportForewordThis SAE Information Report describes results
4、of testing of the SAE J1746 ISP-Vehicle Standard.Testing was performed by the Oak Ridge National Laboratory (ORNL) and its contractors, resulting in a documentfrom which this Information Report has been extracted. Location referencing Standards enable the location of anevent or thing to be communica
5、ted from one component of an ITS system to another component in anunambiguous and mutually understandable way. The SAE J1746 ISP-Vehicle Standard was designed for thecommunication of spatial data references between central sites and mobile vehicles on roads. The ORNL testingprogram determined and ch
6、aracterized the ability of the J1746 standard to transfer information between variouscombinations of commonly available public and private sector databases, and makes conclusions andrecommendations concerning error sources in unsuccessful transfers.Testing was performed by the Oak Ridge National Lab
7、oratory and its contractors and reported in the document“Location Referencing Message Specification Test Report, Version 1.01, September 23, 1998, R. Haas, J. Lau, C.Goodwin, and S. Gordon,” for a project sponsored by the U.S. Federal Highway Administration (FHWA). Testswere performed by computer an
8、alysis and corroborated by field tests with a mobile vehicle. TABLE OF CONTENTS1. Scope . 42. References . 42.1 Applicable Documents 42.2 Related Publications. 43. Definitions. 64. Executive Summary 85. Overview 95.1 Overview of Test Results 96. Introduction to the LRMS and LRMS Testing. 106.1 LRMS
9、Overview 116.2 Testing Overview 116.3 Factors that Influence the Effectiveness of an LRMS Profile . 116.4 Test Data 196.5 LRMS Profile Testing 21SAE J2372 Issued DEC1999-2-7. The Cross-Streets Profile .227.1 Description of the Cross-Streets Profile227.2 Using the Cross-Streets Profile 237.3 Failure
10、Modes when Using the Cross-Streets Profile .247.4 The Cross-Streets Profile Testing Protocol.257.5 Preliminary Testing .287.6 Phase I Testing.317.7 Phase II Testing347.8 Summary of Results .34Appendix A Cross-streets Profile Test Results 37A.1 Preliminary Testing - The Data Used in the Cross-Streets
11、 Profile37A.2 Phase I Testing - Using Cross-Streets to Transmit Location References.49A.3 Phase II Testing - Using Coordinates and Cross-Streets to Transmit Location References 58A.4 Introduction .65A.5 The Cross-Streets Profile - Description 65A.6 XSP Problem Scenarios .69A.7 Definitions and Evalua
12、tion Metrics70A.8 Experimental Procedure and Analytical Results.71A.9 Discussion of Results .76A.10 Conclusions and Recommendations 78Appendix B Cross-streets Profile Phase II Test Results - VITAL.79B.1 Introduction .79B.2 Test Dimensions .79B.3 Experimental Design.81B.4 Accuracy of Source Coordinat
13、e Transfer85B.5 Fan-Out.86B.6 Results86B.7 Conclusions 88TABLE OF FIGURESFigure 1 Example Topological Discrepancies.12Figure 2 Example Topological Ambiguities.13Figure 3 Example Coordinate Discrepancies14Figure 4 Example Street Naming Discrepancies 14Figure 5 Example Cross-Streets Ambiguities .15Fig
14、ure 6 Example Coverage Differences 17Figure 7 Example of Differences in Level of Detail .18Figure 8 The Cross Streets Profile22Figure 9 Typical Usage of the Cross-Streets Profile.27Figure A1 The Test Data Set SB-A .38Figure A2 The Test Data Set SF-D .38Figure A3 Area Defined as Santa Barbara City Da
15、ta 39Figure A4 The Cross Streets Profile in a Nutshell.65Figure A5 Topological Error Situation .69Figure A6 Multiple-Intersection Ambiguities 70Figure A7 Processing of Field Test Measurements 72Figure B1 Downtown Santa Barbara.82Figure B2 Name Processing and Coordinate Fallback .85SAE J2372 Issued D
16、EC1999-3-TABLE OF TABLESTable 1 Failure Modes When Transmitting Location Reference Information.12Table 2 Occurrence Frequency of Topological Ambiguities 13Table 3 Occurrence Frequency of Cross-Streets Ambiguities.15Table 4 Data Issues that Impact LRMS Profile Effectiveness16Table 5 Differences in Le
17、vel of Completeness 18Table 6 Other Factors that Influence Profile Effectiveness19Table 7 Data Set Code Names19Table 8 Types of Test Points for LRMS Profile Testing.20Table 9 Possible Sampling and Weighting Techniques for Commercial Data Set Test Points .20Table 10 Some Methodologies for Using the C
18、ross-Streets Profile to Identify a Link .23Table 11 Some Techniques for Modifying Link Matching Methodologies23Table 12 Alternate Uses of the Cross-streets Profile.24Table 13 Failure Modes for Identifying Links Using the Cross-streets Profiles24Table 14 Failure Modes Using Offsets in the Cross-stree
19、ts Profile .25Table A1 Blank Street Names in the Santa Barbara County Data Sets.39Table A2 Types of Nodes.41Table A3 Types of Cross-Street References for Nodes.41Table A4 Types of Cross-Street References for Links.42Table A5 Links with Blank Street Names .43Table A6 Methods of Street Name Normalizat
20、ion Used in the LRMS Testing.43Table A7 Some Translations Used for Commonly Occurring Words .44Table A8 Street Name Matching Using Different Methods of Street Name Normalization 45Table A9 Reasons Why Method 3 Normalized Street Names Do Not Match 46Table A10 Distance Between Nearest Nodes in Test Da
21、ta Sets .47Table A11 Distance Between Matching Nodes in Test Data Sets .48Table A12 Comparison of Cross-Streets Matching Nodes and Closest Nodes .49Table A13 Summary of Test Methods50Table A14 Cross-Street Node Matching, Test Method 1 .50Table A15 Cross-Street Node Matching, Test Method 2 .51Table A
22、16 Cross-Street Link Matching, Test Method 1 .52Table A17 Cross-Street Link Matching for Links with Mixed Results; Test Method 153Table A18 Links That Match to Multiple Links, Test Method 1.54Table A19 Cross-Streets Link Matching, Test Method 1, Street Name Normalization 154Table A20 Cross-Streets L
23、ink Matching, Test Method 1, Street Name Normalization 555Table A21 Cross-Streets Link Matching, Test Method 1, Weighted by Link Length 56Table A22 Cross-Streets Link Matching, Test Method 1, Restricted to Primary Roadways 57Table A23 Cross-Streets Link Matching, Test Method 1, Restricted to Seconda
24、ry Roadways58Table A24 Cross-Streets Link Matching, Test Method 1, Corrected for Valence 2 Nodes 60Table A25 Cross-Streets Link Matching, Test Method 1, Corrected for Valence 2 Nodes and Dead-End Links.61Table A26 Node Point Chart for Advanced Cross-Streets Profile Matching 62Table A27 Link Point Ch
25、art for Advanced Cross-Streets Profile Matching 63Table A28 Result Bins for Advanced Cross-Streets Profile Matching63Table A29 Cross-Streets Link Matching, “Best Methods” 64Table A30 Incidence of Blank Street Names .67Table A31 Street Name Components 67Table A32 Database A Fields 67Table A33 Databas
26、e B/F Fields .68Table A34 Database E Fields 68Table A35 Name Matching Results for Goleta Test Area 73Table A36 Name Matching Results for Entire County of Santa Barbara74Table A37 Transfer Results (Field Tests) 75Table A38 Transfer Results (Lab Tests) 76SAE J2372 Issued DEC1999-4-Table A39 Lab and Fi
27、eld Results Compared .76Table B1 Incidence of Blank Triads .80Table B2 Scoring of Transfers .85Table B3 Result Summary Test Set B (Lab Generated Single Point Transfer)86Table B4 Result Summary, Test Set C (Lab Generated Single Point Transfer) 87Table B5 Generated Points (Single Point Transfer).90Tab
28、le B6 Generated Points (Two Point Independent Transfer) .90Table B7 Generated Points (Two Point Simultaneous Transfer) .90Table B8 Field Data (Single Point Transfer) 91Table B9 Field Data (Two Point Independent Transfer).91Table B10 Field Data (Two Point Simultaneous Transfer).91Table B11 Generated
29、Points (Single Point Transfer 92Table B12 Generated Points (Two Point Transfer) 93Table B13 Field Data (Single Point Transfer) 94Table B14 Field Data (Two Point Transfer)95Table B15 Generated Points (Single Point Transfer, Major Streets Only) .96Table B16 Generated Points (Two Point Transfer, Major
30、Streets Only) 96Table B17 Santa Barbara County, All Streets97Table B18 Santa Barbara County, Major Streets Only 981. ScopeThis SAE Information Report describes results of testing of the SAE J1746 ISP-Vehicle Standard forthe communication of spatial data references between central sites and mobile ve
31、hicles on roads. Testing wasperformed by the Oak Ridge National Laboratory and its contractors, resulting in a document from which thisInformation Report has been extracted. Tests were performed by computer analysis and corroborated by fieldtests with a mobile vehicle. 2. References2.1 Applicable Pu
32、blicationsThe following standards contain provisions which, through references in this text,constitute provisions of this document. At the time of publication, the editions indicated were valid. Allstandards are subject to revision, and parties to agreements based on this docment are encouraged toin
33、vestigate the possibility of applying the most recent editions of each standard listed below.2.1.1 SAE PUBLICATIONSAvailable from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.SAE J1746ISP-Vehicle Location Referencing StandardSAEJ2374Vehicle Location Referencing Message Specification2.2 Rel
34、ated PublicationsThe following publications are provided for information purposes only and are not arequired part of this document.2.2.1 AMERICAN ASSOCIATION OF STATE HIGHWAY AND TRANSPORTATION OFFICIALS (AASHTO) PUBLICATIONSAvailable from AASHTO, Suite 225, 444 N. Capital St. NW, Washington, DC 200
35、0.GIS-T 95Reinterpreting the Location Referencing Problem: A Protocol ApproachProceedings,Geographic Information Systems for Transportation Symposium (GIS-T)Reno, NV, April 3-5, 1995,Goodwin, C., Gordon, S., and Siegel, D.SAE J2372 Issued DEC1999-5-2.2.2 FEDERAL HIGHWAY ADMINISTRATION DOCUMENTSAvail
36、able from U.S. DOT, FHWA, Office of Safety andTraffic Operations, ITS Research Division, HSR 10, 6300 Georgetown Pike, McLean, VA 22101.Task A:Spatial Data Interoperability Protocol For ITS ProjectLocation Reference ProtocolRequirements, December 29, 1995, Goodwin, C., Siegel, D. and Gordon, S. Task
37、B:Spatial Data Interoperability Protocol For ITS ProjectLocation Reference Message ProtocolPreliminary Specification, February 29, 1996, Goodwin, C., Siegel, D. and Gordon, S. Task B: Spatial Data Interoperability Protocol For ITS ProjectLocation Reference Message Specification:Final Design, June 28
38、, 1996, Goodwin, C., Siegel, D. and Gordon,S. Task B: Spatial Data Interoperability Protocol for ITS ProjectLocation Reference Message Specification:Revision A, September 18, 1996, Goodwin, C., Siegel, D. and Gordon,S. Task B: Spatial Data Interoperability Protocol for ITS ProjectLocation Reference
39、Message Specification:Revision B (MDI), May 22, 1997, Goodwin, C., Siegel, D. and Gordon,S. Task B: Spatial Data Interoperability Protocol for ITS ProjectLocation Referencing MessageSpecification Test Report, Version 1.01, September 23, 1998, Haas, R., Lau,J., Goodwin, C. andGordon, S. Task C: Spati
40、al Data Interoperability Protocol For ITS ProjectThe ITS Datum Preliminary Data Structureand Content, February 25, 1996, Goodwin, C., Siegel, D. and Gordon,S.Task C: Spatial Data Interoperability Protocol For ITS ProjectITS Data Final Design Report, June 28,1996, Goodwin, C., Siegel, D. and Gordon,S
41、.Task A3: Nationwide Map Database and Location Referencing System ProjectFunctional 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 ProjectTechnical Requirementsfor National Map
42、Databases for ITS, July 31, 1995, Goodwin, C., Gordon, S.TaskF1:Nationwide Map Database and Location Referencing System ProjectRecommendation forLocation Referencing for ITS, December 31, 1994, Goodwin, C., Xiong, D. and Gordon, S. Task B: Spatial Data Interoperability Protocol for ITS ProjectLocati
43、on Reference Message Specification,Revision B (MDI) , May 22, 1997, Goodwin, C., Siegel, D. and Gordon, S. “Location Referencing for ITS,” White Paper prepared for Oak Ridge National Laboratory and the NationalITS Architecture Program, November, 1995, 18 pp., Goodwin, Cecil W. H.2.2.3 NATIONAL INSTI
44、TUTE 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 173Spatial Data Transfer Standard (SDTS), 19922.2.4 OAK RIDGE NATIONAL LABORATORY DOCUMENTS
45、Related to spatial data interoperability are available on theWorld-Wide Web at: http:/itsdeployment.ed.ornl.gov/spatial.“The Location Reference Message Protocol for ITS Applications,” White Paper prepared for Oak RidgeNational Laboratory project Nationwide Map Database and Location Referencing Syste
46、m, December1994, 19 pp., Goodwin, Cecil W. H. and Xiong, Demin“Reinterpreting the Location Referencing Problem: A Protocol Approach,” in press for Proceedings of GIS-T 95, AASHTO, Reno, April 3-5, 1995, Goodwin, Cecil W. H., Gordon, Stephen R. and Siegel, Dave.”Recommendation for Location Referencin
47、g for ITS Needs,” Task F1: Nationwide Map Database andLocation Referencing System Project, United States Department of Transportation, Federal HighwayAdministration Office of Safety and Traffic Operations, ITS Research Division, Contract DTFH61-91-Y-30066, Draft, June 30, 1995, 78 pp., Goodwin, Ceci
48、l W. H., Siegel, Dave, Gordon, Stephen R., andXiong, Demin 1995”Location Reference Message Protocol Requirements,” Task A: Spatial Data Interoperability Protocol ForITS Project, United States Department of Transportation, Federal Highway Administration Office ofSafety and Traffic Operations, ITS Res
49、earch Division, Contract 61-94-Y-00001, Review Draft,SAE J2372 Issued DEC1999-6-December 29, 1995, 64 pp., Goodwin, Cecil W. H., Siegel, Dave, and Gordon, Stephen R., 1995”Location Reference Message Protocol Preliminary Specification,” Task B: Spatial Data InteroperabilityProtocol For ITS Project, United States Department of Transportation, Federal Highway AdministrationOffice of Safety and Traffic Operations, ITS Research Division, Contract61-94-Y-00001, Review Draft,February 29, 1996, 34 pp., Goodwin, Cecil W. H., Siegel, David and Gordon, Stephen R. 1996”Loc
