{"id":380896,"date":"2024-10-20T03:08:59","date_gmt":"2024-10-20T03:08:59","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-63173-12021\/"},"modified":"2024-10-26T05:42:10","modified_gmt":"2024-10-26T05:42:10","slug":"bs-en-iec-63173-12021","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-63173-12021\/","title":{"rendered":"BS EN IEC 63173-1:2021"},"content":{"rendered":"
This part of IEC 63173 specifies an S-100 compliant product specification for route plan intended for exchange of information. It specifies the content, structure, and metadata needed for creating fully S-100 compliant route plan information and its portrayal within an S-100-based application. The IHO manages all numbers for S-100 compliant product specifications and has assigned S-421 for this route plan IEC standard. This document specifies only a data format for the route plan exchange. This document does not specify a data format of vessel monitoring and logging information. This information can be provided by other mechanisms or be specified in other standards. The format of the route plan exchange includes some limited vessel static information. When more static information is required, it can be obtained by other methods such as AIS.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
5<\/td>\n | Annex ZA (normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 1 Scope 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 4 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 5 General description 5.1 General data product description 5.2 Data product specification metadata Tables Table 1 \u2013 Informal description of the data product Table 2 \u2013 Data product specification metadata <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 5.3 Product specification maintenance 5.4 Specification scopes 5.5 Dataset identification 6 Data content and structure 6.1 General Table 3 \u2013 Route plan product specification scope Table 4 \u2013 Dataset identification <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 6.2 Application schema <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | Figures Figure 1 \u2013 Route plan application schema <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 6.4 Geometry 6.5 Coordinate reference systems 7 Feature catalogue 7.1 General Table 5 \u2013 Route plan coordinate reference systems <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 7.2 Feature types 7.2.1 Geographic 7.2.2 Meta 7.2.3 Route 7.2.4 RouteActionPoints <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 7.2.5 RouteActionPoint <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | Table 6 \u2013 Route object attributes Table 7 \u2013 RouteActionPoints object attributes <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | Table 8 \u2013 RouteActionPoint object attributes <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | Table 9 \u2013 Definition of RouteActionPointRequiredAction Table 10 \u2013 RouteWaypoints object attributes <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 7.2.6 RouteWaypoints 7.2.7 RouteWaypoint <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | Figure 2 \u2013 RouteWaypointID usage examples: Delete Figure 3 \u2013 RouteWaypointID usage examples: Insert <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Table 11 \u2013 RouteWaypoint object attributes <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 7.2.8 RouteWaypointLeg Figure 4 \u2013 RouteWaypointLegDistance between WP2 and WP3 Figure 5 \u2013 RouteWaypointLeg parameters belonging to WP3 <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Figure 6 \u2013 Under-keel clearance example <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | Figure 7 \u2013 RouteWaypointLeg limits example <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Table 12 \u2013 RouteWaypointLeg object attributes <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 7.3 Information types 7.3.1 General 7.3.2 RouteSchedules 7.3.3 RouteSchedule <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Table 13 \u2013 RouteSchedules object attributes Table 14 \u2013 RouteScheduleManual object attributes Table 15 \u2013 RouteScheduleCalculated object attributes Table 16 \u2013 RouteScheduleRecommended object attributes <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Table 17 \u2013 RouteSchedule object attributes <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 7.3.4 RouteScheduleManual\/RouteScheduleCalculated\/RouteScheduleRecommended 7.3.5 RouteScheduleElement 7.3.6 RouteInfo <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure 8 \u2013 State diagram for route status from ship perspective Figure 9 \u2013 State diagram of route status from shore perspective <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Table 18 \u2013 RouteScheduleElement object attributes <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Table 19 \u2013 RouteInfo object attributes <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Table 20 \u2013 Definition of RouteInfoStatus <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Table 21 \u2013 Type of ship <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 7.4 Association roles of feature catalogue Table 22 \u2013 Roles of the route plan <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 7.5 Associations of feature catalogue 7.5.1 General 7.5.2 Feature association 7.5.3 Information association Table 23 \u2013 Feature association for route plan <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 7.6 Attributes 7.6.1 General 7.6.2 Simple attribute types Table 24 \u2013 Information association for route plan <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 7.6.3 Complex attributes Table 25 \u2013 Simple attribute types <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 7.6.4 Spatial attribute types 7.7 Binding 7.7.1 General 7.7.2 Feature binding Table 26 \u2013 RouteExtensions attributes Table 27 \u2013 Spatial attributes <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 7.7.3 Information binding Table 28 \u2013 Feature binding for the route plan <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 8 Data type and structure of transmission format 9 Maintenance 9.1 Feature and portrayal catalogue management 9.1.1 Feature catalogue management 9.1.2 Portrayal catalogue management Table 29 \u2013 Information binding for the route plan <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 9.2 Data source 9.3 Production process 10 Portrayal 10.1 General 10.2 Portrayal catalogue Table 30 \u2013 Information binding for the route plan portrayal catalogue <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 11 Data product delivery 11.1 General 11.2 Single XML file <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 11.3 Compressed data container 11.4 S-100-compliant exchange set 11.4.1 General 11.4.2 Exchange set Figure 10 \u2013 S-100 exchange set structure <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 11.4.3 Dataset 11.4.4 Exchange catalogue 11.4.5 Digital signature 11.4.6 Encryption <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 11.4.7 Metadata Figure 11 \u2013 Realization of the exchange set classes <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Figure 12 \u2013 Route exchange set catalogue Figure 13 \u2013 Route exchange set <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Figure 14 \u2013 Route exchange set \u2013 Example of class details <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 12 Test methods and expected results 12.1 General Table 31 \u2013 Dataset metadata <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | 12.2 Test data 12.2.1 Test material 12.2.2 Minimum generic test data <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | 12.2.3 Basic generic test data <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 12.2.4 Full generic test data <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 12.3 Route plan test 12.3.1 General 12.3.2 Minimum generic route plan test <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 12.3.3 Basic generic route plan test <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | 12.3.4 Full generic route plan test <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Annex A (normative)Examples of use cases for route A.1 General A.2 Route cross check A.2.1 Description <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | A.2.2 Information exchange diagram Figure A.1 \u2013 Route cross check example <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | A.2.3 State transition diagram Figure A.2 \u2013 Interaction diagram <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | A.2.4 Required objects and attributes and their usage Figure A.3 \u2013 State transition diagram for the route plan onboard Figure A.4 \u2013 State transition diagram for the route plan onshore <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Table A.1 \u2013 Objects and attributes used by route cross check <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | A.2.5 Test methods and expected results Table A.2 \u2013 Test procedures for route cross check <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | A.3 Flow management A.3.1 Description <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | A.3.2 Information exchange diagram Figure A.5 \u2013 Flow management example <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | A.3.3 State transition diagram Figure A.6 \u2013 Data interaction diagram <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Figure A.7 \u2013 State transition diagram for the route plan onboard Figure A.8 \u2013 State transition diagram for the route plan onshore <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | A.3.4 Required objects and attributes and their usage <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Table A.3 \u2013 Objects and attributes used by flow management <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | A.3.5 Test methods and expected results Table A.4 \u2013 Test procedures for flow management <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | A.4 Enhanced monitoring A.4.1 Description <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | A.4.2 Information exchange diagram Figure A.9 \u2013 Enhanced monitoring example <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | A.4.3 State transition diagram Figure A.10 \u2013 Information exchange diagram Figure A.11 \u2013 State transition diagram for the route plan onboard <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | A.4.4 Required objects and attributes and their usage Figure A.12 \u2013 State transition diagram for the route plan onshore <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Table A.5 \u2013 Objects and attributes used by enhanced monitoring <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | A.4.5 Test methods and expected results Table A.6 \u2013 Test procedures for enhanced monitoring <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | A.5 Ice navigation A.5.1 Description <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | A.5.2 Information exchange diagram Figure A.13 \u2013 Ice navigation example <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | A.5.3 State transition diagram ship side Figure A.14 \u2013 Interaction diagram on request Figure A.15 \u2013 State transition diagram for a ship <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | A.5.4 Shore side A.5.5 Required objects and attributes and their usage Figure A.16 \u2013 State transition diagram for a shore <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | Table A.7 \u2013 Objects and attributes used by ice navigation <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | A.5.6 Test methods and expected results Table A.8 \u2013 Test procedures for ice navigation <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | A.6 Under keel clearance management A.6.1 Description <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Figure A.17 \u2013 Example of UKCM area Figure A.18 \u2013 Example of portrayal of S-421 part of UKCM <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | A.6.2 Information exchange diagram Figure A.19 \u2013 Example of portrayal of S-129 overlay part of UKCM <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | A.6.3 State transition diagram Figure A.20 \u2013 Information exchange diagram <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | Figure A.21 \u2013 State transition diagram of UKCM for a ship <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | Figure A.22 \u2013 State transition diagram of UKCM for a shore <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | A.6.4 Required objects and attributes and their usage <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | Table A.9 \u2013 Objects and attributes used by UKCM <\/td>\n<\/tr>\n | ||||||
125<\/td>\n | A.6.5 Test methods and expected results Table A.10 \u2013 Test procedures for UKCM <\/td>\n<\/tr>\n | ||||||
128<\/td>\n | A.7 Fleet route planning A.7.1 Description A.7.2 Information exchange diagram <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | A.7.3 State transition diagram Figure A.23 \u2013 Information sequence diagram <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | Figure A.24 \u2013 State transition diagram for a ship Figure A.25 \u2013 State transition diagram for a shore <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | A.7.4 Required objects and attributes and their usage <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | Table A.11 \u2013 Objects and attributes used by fleet route planning <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | A.7.5 Test methods and expected results Table A.12 \u2013 Test procedures for fleet route planning <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | A.8 Chart management A.8.1 Description <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | A.8.2 Information exchange diagram A.8.3 State transition diagram Figure A.26 \u2013 Interaction diagram <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | A.8.4 Functional requirement A.8.5 Required objects and attributes and their usage <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | Table A.13 \u2013 Objects and attributes used by chart management <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | A.8.6 Test methods and expected results Table A.14 \u2013 Test procedures for chart management <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | A.9 Route optimization A.9.1 Description Figure A.27 \u2013 Route optimization example <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | A.9.2 Information exchange diagram Figure A.28 \u2013 Interaction diagram on request <\/td>\n<\/tr>\n | ||||||
143<\/td>\n | A.9.3 State transition diagram Figure A.29 \u2013 State transition diagram for a ship <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | A.9.4 Required objects and attributes and their usage Figure A.30 \u2013 State transition diagram for a shore <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | Table A.15 \u2013 Objects and attributes used by route optimization <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | A.9.5 Test methods and expected results Table A.16 \u2013 Test procedures for route optimization <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | A.10 Port call synchronization A.10.1 Description <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | A.10.2 Information exchange diagram <\/td>\n<\/tr>\n | ||||||
152<\/td>\n | Figure A.31 \u2013 Interaction diagram <\/td>\n<\/tr>\n | ||||||
153<\/td>\n | A.10.3 State transition diagram <\/td>\n<\/tr>\n | ||||||
154<\/td>\n | Figure A.32 \u2013 State transition diagram for a ship <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | A.10.4 Required objects and attributes and their usage Figure A.33 \u2013 State transition diagram for shore <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | Table A.17 \u2013 Objects and attributes used by port call synchronization <\/td>\n<\/tr>\n | ||||||
158<\/td>\n | A.10.5 Test methods and expected results Table A.18 \u2013 Test procedures for port call synchronization <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | A.11 Reference route A.11.1 Description <\/td>\n<\/tr>\n | ||||||
160<\/td>\n | A.11.2 Information exchange diagram Figure A.34 \u2013 Example of reference routes <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | A.11.3 State transition diagram Figure A.35 \u2013 Data interaction diagram <\/td>\n<\/tr>\n | ||||||
162<\/td>\n | Figure A.36 \u2013 State transition diagram for a ship requesting a reference route <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | A.11.4 Required objects and attributes and their usage Figure A.37 \u2013 State transition diagram for a shore center providing a reference route <\/td>\n<\/tr>\n | ||||||
164<\/td>\n | Table A.19 \u2013 Objects and attributes used by reference route <\/td>\n<\/tr>\n | ||||||
168<\/td>\n | A.11.5 Test methods and expected results Table A.20 \u2013 Test procedures for reference route <\/td>\n<\/tr>\n | ||||||
169<\/td>\n | A.12 Search and rescue A.12.1 Description <\/td>\n<\/tr>\n | ||||||
170<\/td>\n | A.12.2 Information exchange diagram Figure A.38 \u2013 A search and rescue example Figure A.39 \u2013 Interaction diagram <\/td>\n<\/tr>\n | ||||||
171<\/td>\n | A.12.3 State transition diagram Figure A.40 \u2013 State transition diagram for a ship <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | A.12.4 Required objects and attributes and their usage Figure A.41 \u2013 State transition diagram for shore <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | Table A.21 \u2013 Objects and attributes used by Search and Rescue <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | A.12.5 Test methods and expected results Table A.22 \u2013 Test procedures for Search and Rescue <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | A.13 Summary of objects and attributes used by service scenarios Table A.23 \u2013 Objects and attributes used by service scenarios as seen from the ship <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | Annex B (normative)Data classification and encoding guide B.1 General B.1.1 Overview B.1.2 Descriptive characteristics <\/td>\n<\/tr>\n | ||||||
184<\/td>\n | B.1.3 Spatial characteristics B.2 Attributes B.2.1 General Table B.1 \u2013 Feature types <\/td>\n<\/tr>\n | ||||||
185<\/td>\n | B.2.2 Simple attribute types with acronym Table B.2 \u2013 Simple attribute types <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | B.2.3 Mandatory attributes by schema <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | B.2.4 Missing attribute values Table B.3 \u2013 Mandatory attribute types <\/td>\n<\/tr>\n | ||||||
188<\/td>\n | B.2.5 Multiplicity B.2.6 Spatial attribute types B.2.7 Textual information B.2.8 Attributes referencing external files Table B.4 \u2013 Multiplicity <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | B.2.9 Dates Table B.5 \u2013 Predefined derived types Table B.6 \u2013 File format <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | B.3 Associations B.3.1 General Figure B.1 \u2013 Association routeInfoComposition Table B.7 \u2013 Truncated dates <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | B.3.2 Association names B.3.3 Association roles B.3.4 Use of various associations B.4 Datasets B.5 Metadata B.5.1 General Table B.8 \u2013 Dataset types <\/td>\n<\/tr>\n | ||||||
192<\/td>\n | B.5.2 Dataset metadata Figure B.2 \u2013 Metadata packages <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | Table B.9 \u2013 Metadata for route plan <\/td>\n<\/tr>\n | ||||||
194<\/td>\n | B.5.3 Support file metadata <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | B.5.4 Exchange set metadata B.5.5 Catalogue file metadata Table B.10 \u2013 Support files for route plan <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | B.6 Description of table format for feature and information formats Table B.11 \u2013 File metadata for route plan <\/td>\n<\/tr>\n | ||||||
197<\/td>\n | Table B.12 \u2013 Example of table format for feature <\/td>\n<\/tr>\n | ||||||
198<\/td>\n | B.7 Feature types B.7.1 Feature type in general B.7.2 Route Table B.13 \u2013 General feature types <\/td>\n<\/tr>\n | ||||||
199<\/td>\n | Table B.14 \u2013 Table format for Route <\/td>\n<\/tr>\n | ||||||
200<\/td>\n | B.7.3 RouteActionPoints B.7.4 RouteActionPoint Table B.15 \u2013 Table format for RouteActionPoints <\/td>\n<\/tr>\n | ||||||
201<\/td>\n | Table B.16 \u2013 Table format for RouteActionPoint <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | B.7.5 RouteWaypoints Table B.17 \u2013 Table format for RouteWayPoints <\/td>\n<\/tr>\n | ||||||
203<\/td>\n | B.7.6 RouteWaypoint B.7.7 RouteWaypointLeg Table B.18 \u2013 Table format for RouteWaypoint <\/td>\n<\/tr>\n | ||||||
204<\/td>\n | Table B.19 \u2013 Table format for RouteWaypointLeg <\/td>\n<\/tr>\n | ||||||
205<\/td>\n | B.8 Information types B.8.1 InformationType in general Table B.20 \u2013 General information types <\/td>\n<\/tr>\n | ||||||
206<\/td>\n | B.8.2 RouteInfo Table B.21 \u2013 Table format for RouteInfo <\/td>\n<\/tr>\n | ||||||
207<\/td>\n | B.8.3 RouteSchedules Table B.22 \u2013 Table format for RouteSchedules <\/td>\n<\/tr>\n | ||||||
208<\/td>\n | B.8.4 RouteSchedule Table B.23 \u2013 Table format for RouteSchedule <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | B.8.5 RouteScheduleManual Table B.24 \u2013 Table format for RouteScheduleManual <\/td>\n<\/tr>\n | ||||||
210<\/td>\n | B.8.6 RouteScheduleCalculated B.8.7 RouteScheduleRecommend Table B.25 \u2013 Table format for RouteScheduleCalculated <\/td>\n<\/tr>\n | ||||||
211<\/td>\n | B.8.8 RouteScheduleElement Table B.26 \u2013 Table format for RouteScheduleRecommend <\/td>\n<\/tr>\n | ||||||
212<\/td>\n | Table B.27 \u2013 Table format for RouteScheduleElement <\/td>\n<\/tr>\n | ||||||
213<\/td>\n | Annex C (informative)Examples of how to fulfil the requirementsof IMO voyage planning C.1 General C.2 Reference points Figure C.1 \u2013 Example of reference point <\/td>\n<\/tr>\n | ||||||
214<\/td>\n | C.3 Astronomical events Figure C.2 \u2013 Example of presentation of added textual information <\/td>\n<\/tr>\n | ||||||
215<\/td>\n | C.4 Under keel clearance Figure C.3 \u2013 Example of astronomical event <\/td>\n<\/tr>\n | ||||||
216<\/td>\n | C.5 Overhead clearance Figure C.4 \u2013 Example of presentation of added textual information <\/td>\n<\/tr>\n | ||||||
218<\/td>\n | C.6 Regulated areas <\/td>\n<\/tr>\n | ||||||
219<\/td>\n | Figure C.5 \u2013 Example of presentation of added textual information <\/td>\n<\/tr>\n | ||||||
220<\/td>\n | Figure C.6 \u2013 Example of graphical presentation of regulated area <\/td>\n<\/tr>\n | ||||||
221<\/td>\n | Annex D (normative)Route plan feature catalogue and example D.1 Application schema <\/td>\n<\/tr>\n | ||||||
245<\/td>\n | D.2 Example <\/td>\n<\/tr>\n | ||||||
250<\/td>\n | Annex E (informative)Guidelines for GML ID allocation Table E.1 \u2013 Example of GML ID <\/td>\n<\/tr>\n | ||||||
252<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Maritime navigation and radiocommunication equipment and systems. Data interface – S-421 route plan based on S-100<\/b><\/p>\n |