CEN TS 16157-3-2011 Intelligent transport systems - DATEX II data exchange specifications for traffic management and information - Part 3 Situation Publication《智能交通系统 DATEX II数据交换规.pdf

《CEN TS 16157-3-2011 Intelligent transport systems - DATEX II data exchange specifications for traffic management and information - Part 3 Situation Publication《智能交通系统 DATEX II数据交换规.pdf》由会员分享，可在线阅读，更多相关《CEN TS 16157-3-2011 Intelligent transport systems - DATEX II data exchange specifications for traffic management and information - Part 3 Situation Publication《智能交通系统 DATEX II数据交换规.pdf（274页珍藏版）》请在麦多课文档分享上搜索。

1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationDD CEN/TS 16157-3:2011Intelligent transport systems DATEX II data exchangespecifications for trafficmanagement and informationPart 3: Situation PublicationDD CEN/TS 16157-3:2011

2、DRAFT FOR DEVELOPMENTNational forewordThis Draft for Development is the UK implementation of CEN/TS16157-3:2011. DD ENV 13106:2000 and DD ENV 13777:2000 werewithdrawn in 2007 as ENV 13106:2000 and ENV 13777:2000 expiredwithout producing an EN standard.DATEX II is founded on a single UML model which

3、is madeavailable in a useable format to all through the website, http:/www.datex2.eu/.This publication is not to be regarded as a British Standard.It is being issued in the Draft for Development series of publicationsand is of a provisional nature. It should be applied on thisprovisional basis, so t

4、hat information and experience of its practicalapplication can be obtained.Comments arising from the use of this Draft for Developmentare requested so that UK experience can be reported to theinternational organization responsible for its conversion toan international standard. A review of this publ

5、ication willbe initiated not later than 3 years after its publication by theinternational organization so that a decision can be taken on itsstatus. Notification of the start of the review period will be made inan announcement in the appropriate issue of Update Standards.According to the replies rec

6、eived by the end of the review period,the responsible BSI Committee will decide whether to support theconversion into an international Standard, to extend the life of theTechnical Specification or to withdraw it. Comments should be sentto the Secretary of the responsible BSI Technical Committee at B

7、ritishStandards House, 389 Chiswick High Road, London W4 4AL.The UK participation in its preparation was entrusted to TechnicalCommittee EPL/278, Road transport informatics.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purp

8、ort to include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. BSI 2011ISBN 978 0 580 72444 2ICS 35.240.60Compliance with a British Standard cannot confer immunity fromlegal obligations.This Draft for Development was published under the authority ofthe St

9、andards Policy and Strategy Committee on 31 October 2011.Amendments issued since publicationDate Text affectedDD CEN/TS 16157-3:2011TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/TS 16157-3 October 2011 ICS 35.240.60 Supersedes ENV 13106:2000, ENV 13777:2000English Versi

10、on Intelligent transport systems - DATEX II data exchange specifications for traffic management and information - Part 3: Situation Publication Systmes de transport intelligents - Spcifications DATEX II dchange de donnes pour la gestion du trafic et linformation routire - Partie 3: Publication de si

11、tuations Intelligente Transportsysteme - DATEX II Datenaustausch Spezifikationen fr Verkehrsmanagement und Informationen - Teil 3: Situationsverffentlichungen This Technical Specification (CEN/TS) was approved by CEN on 10 April 2011 for provisional application. The period of validity of this CEN/TS

12、 is limited initially to three years. After two years the members of CEN will be requested to submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard. CEN members are required to announce the existence of this CEN/TS in the same way as for an

13、EN and to make the CEN/TS available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached. CEN members are the nationa

14、l standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerlan

15、d and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG Management Centre: Avenue Marnix 17, B-1000 Brussels 2011 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN/T

16、S 16157-3:2011: EDD CEN/TS 16157-3:2011CEN/TS 16157-3:2011 (E) 2 Contents Page Introduction .71 Scope 82 Conformance 83 Normative references 94 Terms and definitions .95 Symbols and abbreviations . 106 UML notation . 117 The Situation Publication model . 117.1 Overview of the Situation Publication m

17、odel 117.2 The “SituationPublication” package. 117.2.1 Overview of the “SituationPublication” package 117.2.2 Semantics of the “SituationPublication” package 127.3 The “SituationRecord” package 137.3.1 Overview of the “SituationRecord” package . 137.3.2 Semantics of the “SituationRecord” package . 1

18、47.4 The “Impact” package 167.4.1 Overview of the “Impact” package . 167.4.2 Semantics of the “Impact” package . 177.5 The “Validity” package . 187.5.1 Overview of “Validity” package . 187.5.2 Semantics of the “Validity” package 207.6 The “TimePeriodOfDay” package . 217.6.1 Overview of the “TimePeri

19、odOfDay” package . 217.6.2 Semantics of the “TimePeriodOfDay” package . 217.7 The “NonRoadEventInformation” package 227.7.1 Overview of the “NonRoadEventInformation” package . 227.7.2 Semantics of the “NonRoadEventInformation” package . 227.8 The “TrafficElement” package 237.8.1 Overview of the “Tra

20、fficElement” package 237.8.2 Semantics of the “TrafficElement” package 247.9 The “Conditions” package . 257.9.1 Overview of the “Conditions” package 257.9.2 Semantics of the “Conditions” package 257.10 The “WeatherRelated” package 267.10.1 Overview of the “WeatherRelated” package 267.10.2 Semantics

21、of the “WeatherRelated” package 277.11 The “Humidity” package 277.11.1 Overview of the “Humidity” package . 277.11.2 Semantics of the “Humidity” package 277.12 The “Temperature” package 287.12.1 Overview of the “Temperature” package . 287.12.2 Semantics of the “Temperature” package . 287.13 The “Vis

22、ibility” package . 297.13.1 Overview of the “Visibility” package 297.13.2 Semantics of the “Visibility” package 297.14 The “Wind” package . 307.14.1 Overview of the “Wind” package 307.14.2 Semantics of the “Wind” package 30DD CEN/TS 16157-3:2011CEN/TS 16157-3:2011 (E) 3 7.15 The “Pollution” package

23、. 317.15.1 Overview of the “Pollution” package 317.15.2 Semantics of the “Pollution” package 317.16 The “PrecipitationDetail” package 327.16.1 Overview of the “PrecipitationDetail” package 327.16.2 Semantics of the “PrecipitationDetail” package 327.17 The “RoadSurfaceConditionMeasurements” package 3

24、37.17.1 Overview of the “RoadSurfaceConditionMeasurements” package . 337.17.2 Semantics of the “RoadSurfaceConditionMeasurements” package . 337.18 The “Accident” package . 347.18.1 Overview of the “Accident” package 347.18.2 Semantics of the “Accident” package 357.19 The “Obstruction” package 367.19

25、.1 Overview of the “Obstruction” package . 367.19.2 Semantics of the “Obstruction” package . 377.20 The “Activity” package . 387.20.1 Overview of the “Activity” package . 387.20.2 Semantics of the “Activity” package . 397.21 The “Vehicle” package 407.21.1 Overview of the “Vehicle” package . 407.21.2

26、 Semantics of the “Vehicle” package . 417.22 The “VehicleCharacteristics” package . 427.22.1 Overview of the “VehicleCharacteristics” package . 427.22.2 Semantics of the “VehicleCharacteristics” package . 437.23 The “OperatorAction” package 437.23.1 Overview of the “OperatorAction” package . 437.23.

27、2 Semantics of the “OperatorAction” package . 447.24 The “Roadworks” package . 457.24.1 Overview of the “Roadworks” package 457.24.2 Semantics of the “Roadworks” package 467.25 The “NetworkManagement” package 477.25.1 Overview of the “NetworkManagement” package . 477.25.2 Semantics of the “NetworkMa

28、nagement” package . 48Annex A (normative) Data Dictionary 51A.1 Overview . 51A.2 Data Dictionary for “SituationPublication“ . 52A.2.1 “Accident“ package . 52A.2.2 “Activity“ package . 53A.2.3 “Conditions“ package . 54A.2.4 “DataValue“ package 55A.2.5 “Humidity“ package 60A.2.6 “Impact“ package 61A.2

29、.7 “NetworkManagement“ package . 63A.2.8 “NonRoadEventInformation“ package 67A.2.9 “Obstruction“ package . 70A.2.10 “OperatorAction“ package . 72A.2.11 “Pollution“ package 73A.2.12 “PrecipitationDetail“ package 73A.2.13 “ReusableClasses“ package 75A.2.14 “RoadSurfaceConditionMeasurements“ package .

30、79A.2.15 “Roadworks“ package 80A.2.16 “SituationPublication“ package . 82A.2.17 “SituationRecord“ package 83A.2.18 “Temperature“ package 86A.2.19 “TimePeriodOfDay“ package . 87A.2.20 “TrafficElement“ package . 88A.2.21 “Validity“ package . 90A.2.22 “Vehicle“ package . 93A.2.23 “VehicleCharacteristic

31、s“ package . 96DD CEN/TS 16157-3:2011CEN/TS 16157-3:2011 (E) 4 A.2.24 “Visibility“ package 98A.2.25 “WeatherRelated“ package 99A.2.26 “Wind“ package 99A.3 Data Dictionary of for “SituationPublication“ . 101A.3.1 The “AngleInDegrees“ . 101A.3.2 The “AxlesPerHour“ . 101A.3.3 The “ConcentrationKilogram

32、sPerCubicMetre“ . 101A.3.4 The “ConcentrationMicrogramsPerCubicMetre“ 101A.3.5 The “ConcentrationVehiclesPerKilometre“ . 101A.3.6 The “CubicMetres“ . 101A.3.7 The “IntensityKilogramsPerSquareMetre“ 101A.3.8 The “IntensityMillimetresPerHour“ . 102A.3.9 The “KilometresPerHour“ 102A.3.10 The “MetresAsF

33、loat“ 102A.3.11 The “MetresAsNonNegativeInteger“ 102A.3.12 The “PassengerCarUnitsPerHour“ . 102A.3.13 The “Percentage“ . 102A.3.14 The “Seconds“ 102A.3.15 The “TemperatureCelsius“ 102A.3.16 The “Tonnes“ 102A.3.17 The “VehiclesPerHour“ 103A.4 Data Dictionary of for “SituationPublication“ . 103A.4.1 T

34、he “AbnormalTrafficTypeEnum“ 103A.4.2 The “AccidentCauseEnum“ 104A.4.3 The “AccidentTypeEnum“ 105A.4.4 The “AnimalPresenceTypeEnum“ . 108A.4.5 The “AreaOfInterestEnum“ . 109A.4.6 The “AuthorityOperationTypeEnum“ 110A.4.7 The “CarParkConfigurationEnum“ 112A.4.8 The “CarParkStatusEnum“ . 113A.4.9 The

35、“CauseTypeEnum“ . 114A.4.10 The “CommentTypeEnum“ . 116A.4.11 The “ComparisonOperatorEnum“ 117A.4.12 The “ComplianceOptionEnum“ 117A.4.13 The “ComputationMethodEnum“ . 118A.4.14 The “ConfidentialityValueEnum“ . 118A.4.15 The “ConstructionWorkTypeEnum“ 119A.4.16 The “CountryEnum“ 120A.4.17 The “Dange

36、rousGoodsRegulationsEnum“ . 122A.4.18 The “DayEnum“ . 123A.4.19 The “DelayBandEnum“ . 123A.4.20 The “DelaysTypeEnum“ 124A.4.21 The “DirectionCompassEnum“ 125A.4.22 The “DirectionEnum“ 126A.4.23 The “DisturbanceActivityTypeEnum“ . 127A.4.24 The “DrivingConditionTypeEnum“ 129A.4.25 The “EnvironmentalO

37、bstructionTypeEnum“ 130A.4.26 The “EquipmentOrSystemFaultTypeEnum“ . 131A.4.27 The “EquipmentOrSystemTypeEnum“ 132A.4.28 The “FuelTypeEnum“ 133A.4.29 The “GeneralInstructionToRoadUsersTypeEnum“ 134A.4.30 The “GeneralNetworkManagementTypeEnum“ 136A.4.31 The “InformationStatusEnum“ . 137A.4.32 The “In

38、frastructureDamageTypeEnum“ 138A.4.33 The “InjuryStatusTypeEnum“ . 139A.4.34 The “InvolvementRolesEnum“ . 140A.4.35 The “LoadTypeEnum“ . 141A.4.36 The “MaintenanceVehicleActionsEnum“ 143A.4.37 The “MobilityEnum“ 143DD CEN/TS 16157-3:2011CEN/TS 16157-3:2011 (E) 5 A.4.38 The “MonthOfYearEnum“ 144A.4.3

39、9 The “NonWeatherRelatedRoadConditionTypeEnum“ 145A.4.40 The “ObstructionTypeEnum“ 146A.4.41 The “OperatorActionOriginEnum“ . 148A.4.42 The “OperatorActionStatusEnum“ . 149A.4.43 The “PersonCategoryEnum“ . 150A.4.44 The “PlacesEnum“ . 151A.4.45 The “PollutantTypeEnum“ . 153A.4.46 The “PoorEnvironmen

40、tTypeEnum“ 154A.4.47 The “PrecipitationTypeEnum“ 157A.4.48 The “ProbabilityOfOccurrenceEnum“ 157A.4.49 The “PublicEventTypeEnum“ . 158A.4.50 The “RelativeTrafficFlowEnum“ . 161A.4.51 The “ReroutingManagementTypeEnum“ . 162A.4.52 The “RoadMaintenanceTypeEnum“ . 163A.4.53 The “RoadOperatorServiceDisru

41、ptionTypeEnum“ . 164A.4.54 The “RoadOrCarriagewayOrLaneManagementTypeEnum“ . 165A.4.55 The “RoadsideAssistanceTypeEnum“ . 167A.4.56 The “RoadsideServiceDisruptionTypeEnum“ . 168A.4.57 The “RoadworksDurationEnum“ 170A.4.58 The “RoadworksScaleEnum“ 170A.4.59 The “SeverityEnum“ . 171A.4.60 The “SourceT

42、ypeEnum“ 172A.4.61 The “SpeedManagementTypeEnum“ . 174A.4.62 The “SubjectTypeOfWorksEnum“ 175A.4.63 The “TrafficConstrictionTypeEnum“ 176A.4.64 The “TrafficFlowCharacteristicsEnum“ . 177A.4.65 The “TrafficStatusEnum“. 177A.4.66 The “TrafficTrendTypeEnum“ . 178A.4.67 The “TrafficTypeEnum“ . 179A.4.68

43、 The “TransitServiceInformationEnum“ 180A.4.69 The “TransitServiceTypeEnum“ . 182A.4.70 The “UrgencyEnum“ 182A.4.71 The “UrlLinkTypeEnum“ 183A.4.72 The “ValidityStatusEnum“ . 183A.4.73 The “VehicleEquipmentEnum“ . 184A.4.74 The “VehicleObstructionTypeEnum“ . 185A.4.75 The “VehicleStatusEnum“ . 187A.

44、4.76 The “VehicleTypeEnum“ 188A.4.77 The “VehicleUsageEnum“ . 190A.4.78 The “WeatherRelatedRoadConditionTypeEnum“ . 191A.4.79 The “WeekOfMonthEnum“ 193A.4.80 The “WinterEquipmentManagementTypeEnum“ 193Annex B (normative) Referenced XML Schema for “SituationPublication” 194B.1 Overview . 194B.2 Schem

45、a . 194Annex C (informative) Examples of Situation Publications In XML . 258C.1 Example Traffic Element . 258C.2 Example Operator Action . 261C.3 Example NonRoadEventInformation . 267Bibliography 270DD CEN/TS 16157-3:2011CEN/TS 16157-3:2011 (E) 6 Foreword This document (CEN/TS 16157-3:2011) has been

46、 prepared by Technical Committee CEN/TC 278 “Road transport and traffic telematics”, the secretariat of which is held by NEN. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN and/or CENELEC shall not be held responsible for ide

47、ntifying any or all such patent rights. This document supersedes ENV 13106:2000, ENV 13777:2000. As a user of the standard, attention is drawn to the resources of www.datex2.eu. This web site contains related software tools and software resources that aid the implementation of CEN/TS 16157 DATEX II. According to the CE