Commission Implementing Regulation (EU) 2018/2032Show full title

1. Introductory Text

2. Article 1. The Annex to Commission Regulation (EC) No 416/2007 is replaced by...

3. Article 2. This Regulation shall enter into force on the day following...

4. Signature

5. 1. ANNEX

      1. 1. GENERAL PROVISIONS

         1. 1.1. Definitions

         2. 1.2. Primary functions and performance requirements for Notices to Skippers (NtS)...

      2. 2. PROVISION OF NOTICES TO SKIPPERS

      3. 3. NTS MESSAGE TYPES

      4. 4. STRUCTURE OF NTS AND ENCODING OF NTS MESSAGES

         1. 4.1. General structure

            1. Figure 1 Notice to Skippers message structure

            2. 4.1.1. Identification section

            3. 4.1.2. Fairway and traffic related message

            4. 4.1.3. Water related message

            5. 4.1.4. Ice related message

            6. 4.1.5. Weather related message

         2. 4.2. Explanation of XML tags and code values in the NtS...

         3. 4.3. Identification of fairway sections and objects in NtS messages

         4. 4.4. Rules for encoding of NtS messages

      5. A.

         NOTICES TO SKIPPERS ENCODING GUIDE FOR EDITORS

         1. Abbreviations:

         2. 1. Background, structure and purpose of NtS Encoding Guides

         3. 2. Selection of the NtS message type

         4. 3. FTM basic considerations, steps towards publication of an FTM

            1. 3.1. Is there a need to publish information via NtS FTM...

            2. 3.2. Does a valid FTM already exist related to the current...

            3. 3.2.1. Yes:

            4. 3.2.2. No:

            5. 3.3. The geographical range of validity is to be set

            6. 3.3.1. In case the FTM is related to a specific stretch...

            7. 3.3.2. In case the FTM is related to a specific object...

            8. 3.3.3. Combination of object- and fairway-related information is possible within one...

            9. 3.3.4. Although the coordinates are conditional they shall be provided to...

            10. 3.4. Content of the FTM is to be entered

            11. 3.5. The target group(s) concerning the type of vessels and affected...

            12. 3.5.1. In case the message is valid for all crafts (all...

            13. 3.5.2. In case the whole message is valid for specific target...

            14. 3.5.3. In case there are different target groups applicable to different...

            15. 3.5.4. In case exemptions from limitations are granted to individual vessels...

            16. 3.6. The communication section is to be entered if applicable

            17. 3.7. The limitation section is to be entered if applicable

            18. 3.8. The start date of the validity of the message is...

            19. 3.9. The message can be published

         5. 4. FTM explanation of codes

            1. 4.1. Subject_code:

            2. 4.2. Reason_code

            3. 4.3. Limitation_code:

            4. 4.4. Limitation interval_code: Definition of use of interval codes:

            5. 4.5. Indication_code:

               1. 4.5.1. If absolute dimensions or references are known they have to...

               2. 4.5.2. reduced by → this is a relative value

               3. 4.5.3. maximum → this is an absolute value

               4. 4.5.4. minimum → this is an absolute value

               5. 4.5.5. If the dimension indicating a limitation refers to a geographical...

               6. 4.5.6. If the dimension indicating a limitation refers to a dimension...

            6. 4.6. Position_code (objects):

            7. 4.7. Position_code (fairways/waterways):

            8. 4.8. Position_code (limitations):

               1. 4.8.1. Wherever possible the Position_code shall refer to the side of...

               2. 4.8.2. The Position_code shall direct the attention of the skipper to...

               3. 4.8.3. If necessary, more precise position information should preferably be given...

               4. 4.8.4. For sections where the usual position indication by fairway side...

            9. 4.9. Target_group_code (see chapter 3.5)

            10. 4.10. Reporting_code

                1. 4.10.1. The Reporting_code shall, as a general rule, only be used...

                2. 4.10.2. A routine reiteration of publicly available communication data (e.g. telephone...

                3. 4.10.3. Generally applicable means of communication according to official regulation (e.g....

            11. 4.11. Communication_code

            12. 4.12. Type_code:

         6. 5. WRM basic considerations

         7. 6. ICEM basic considerations, steps towards publication of an ICEM

            1. 6.1. Is there a need to publish information via NtS ICEM?...

            2. 6.2. Does a valid ICEM already exist for the affected stretch...

            3. 6.2.1. Yes:

            4. 6.2.2. No:

            5. 6.3. However information about ice condition not hindering navigation may be...

            6. 6.4. One ICEM is always valid for one single stretch of...

            7. 6.5. Measurement time is to be entered. The respective ice conditions...

            8. 6.5.1. Ice_condition_code

            9. 6.5.2. Ice_accessibility_code

            10. 6.5.3. Ice_classification_code

            11. 6.5.4. Ice_situation_code (the ice situation code should always be provided to...

            12. 6.6. The ICEM can be published. Ice messages will be valid...

         8. 7. WERM basic considerations

         9. 8. Rules for certain elements

            1. 8.1. Rules for the element ‘name’ related to objects

            2. 8.2. Rules for the element ‘name’ related to fairways

            3. 8.3. Rules for the elements ‘value’ and ‘unit’ within limitations

      6. B.

         NOTICES TO SKIPPERS ENCODING GUIDE FOR APPLICATION DEVELOPERS

         1. 1. Background & Structure

            1. 1.1. Purpose of NtS Encoding Guide

               1. 1.1.1. NtS Encoding Guide for editors

               2. 1.1.2. NtS Encoding Guide for application developers (this document)

         2. 2. NtS messages and sections

            1. Figure 2 Visualisation of the NtS message structure: mandatory element (1), mandatory...

         3. 3. WRM basic considerations

            1. 3.1. Filling of nts_number section in the WRM

            2. 3.2. Filling of WRM including predictions

               1. Figure 3 Visualisation of water level prediction confidence interval: most probable value...(The x-axis shows the time; the y-axis shows the water...

         4. 4. ICEM processes

            1. 4.1. New ICEM

            2. 4.2. Update of an existing ICEM

         5. 5. WERM basic considerations

            1. 5.1. Filling of nts_number section in the WERM

            2. 5.2. Filling of WERM ‘weather_category_code’

         6. 6. FTM processes

            1. 6.1. New FTM

            2. 6.2. Update/withdrawal of an existing FTM

            3. 6.3. Waterway and/or object related FTM

            4. 6.4. Automatic ordering of limitation codes

            5. 6.5. Handling of limitation period

         7. 7. General implementation rules

            1. 7.1. Filling of the ‘number_section’

            2. 7.2. Filling of elements ‘from’, ‘originator’, ‘organisation’ and ‘source’

            3. 7.3. Omission of elements

            4. 7.4. Automatic filling of date_issue

            5. 7.5. Handling of time zone information in NtS messages

            6. 7.6. Handling of Seconds in NtS messages

            7. 7.7. Format of decimals in NtS messages

            8. 7.8. Units to be used in NtS messages

            9. 7.9. Rules for the elements ‘name’, ‘position_code’ and ‘type_code’

               1. Table 1 Matching ‘RIS Index function_code’ — ‘NtS type_code’

            10. 7.10. Rules for the element ‘fairway_name’

            11. 7.11. Clarifications for translations in the spreadsheet ‘reference_code’

            12. 7.12. Recommendation for the element ‘coordinate’

            13. 7.13. Handling of target groups

            14. 7.14. Display of valid messages at a given time

            15. 7.15. Optional functions to increase user friendliness of NtS editor tools...

         8. 8. NtS XML Message Structure

         9. 9. NtS Web Service

            1. 9.1. Objective

            2. 9.2. Basic Principles and constraints

               1. 9.2.1. Web standards

               2. 9.2.2. Interaction model and encoding method for NtS WS

            3. 9.3. General specifications and recommendations

               1. 9.3.1. Specification: Version information

               2. 9.3.2. Specification: Structure of namespaces

               3. 9.3.3. Recommendation: Use of namespaces

               4. 9.3.4. Recommendation: Use of namespace prefixes

               5. 9.3.5. Specification: Use of ISRS Location Codes

                  1. Invalid ISRS Location Code queries

                  2. Case 1: No ids element in request

                  3. Valid query without ids parameter

                  4. Case 2: One id element in request

                  5. Valid query with one id parameter

                  6. Matching and not matching messages for one id parameter Case 3: Two id elements in request

                  7. Valid query with two id parameters

                  8. Matching and not matching messages for two id parameters

                  9. Combination: Multiple ids elements in request

                  10. Valid query with multiple ids elements

            4. 9.4. NtS Message Service (implementation specification)

               1. 9.4.1. Request

               2. 9.4.2. Response

            5. 9.5. Generation of services and clients

         10. Glossary

      7. Appendix C

      8. Appendix D