http://www.legislation.gov.uk/id/eur/2018/2032/contents

1.GENERAL PROVISIONS 1.1.Definitions 1.2.Primary functions and performance requirements for Notices to Skippers (NtS)...2.PROVISION OF NOTICES TO SKIPPERS 3.NTS MESSAGE TYPES 4.STRUCTURE OF NTS AND ENCODING OF NTS MESSAGES 4.1.General structure Figure 1Notice to Skippers message structure 4.1.1.Identification section 4.1.2.Fairway and traffic related message 4.1.3.Water related message 4.1.4.Ice related message 4.1.5.Weather related message 4.2.Explanation of XML tags and code values in the NtS...4.3.Identification of fairway sections and objects in NtS messages 4.4.Rules for encoding of NtS messages

A.NOTICES TO SKIPPERS ENCODING GUIDE FOR EDITORS

Abbreviations: 1.Background, structure and purpose of NtS Encoding Guides 2.Selection of the NtS message type 3.FTM basic considerations, steps towards publication of an FTM 3.1.Is there a need to publish information via NtS FTM...3.2.Does a valid FTM already exist related to the current...3.2.1.Yes: 3.2.2.No: 3.3.The geographical range of validity is to be set 3.3.1.In case the FTM is related to a specific stretch...3.3.2.In case the FTM is related to a specific object...3.3.3.Combination of object- and fairway-related information is possible within one...3.3.4.Although the coordinates are conditional they shall be provided to...3.4.Content of the FTM is to be entered 3.5.The target group(s) concerning the type of vessels and affected...3.5.1.In case the message is valid for all crafts (all...3.5.2.In case the whole message is valid for specific target...3.5.3.In case there are different target groups applicable to different...3.5.4.In case exemptions from limitations are granted to individual vessels...3.6.The communication section is to be entered if applicable 3.7.The limitation section is to be entered if applicable 3.8.The start date of the validity of the message is...3.9.The message can be published 4.FTM explanation of codes 4.1.Subject_code: 4.2.Reason_code 4.3.Limitation_code: 4.4.Limitation interval_code: Definition of use of interval codes: 4.5.Indication_code: 4.5.1.If absolute dimensions or references are known they have to...4.5.2.reduced by → this is a relative value 4.5.3.maximum → this is an absolute value 4.5.4.minimum → this is an absolute value 4.5.5.If the dimension indicating a limitation refers to a geographical...4.5.6.If the dimension indicating a limitation refers to a dimension...4.6.Position_code (objects): 4.7.Position_code (fairways/waterways): 4.8.Position_code (limitations): 4.8.1.Wherever possible the Position_code shall refer to the side of...4.8.2.The Position_code shall direct the attention of the skipper to...4.8.3.If necessary, more precise position information should preferably be given...4.8.4.For sections where the usual position indication by fairway side...4.9.Target_group_code (see chapter 3.5) 4.10.Reporting_code 4.10.1.The Reporting_code shall, as a general rule, only be used...4.10.2.A routine reiteration of publicly available communication data (e.g. telephone...4.10.3.Generally applicable means of communication according to official regulation (e.g....4.11.Communication_code 4.12.Type_code: 5.WRM basic considerations 6.ICEM basic considerations, steps towards publication of an ICEM 6.1.Is there a need to publish information via NtS ICEM?...6.2.Does a valid ICEM already exist for the affected stretch...6.2.1.Yes: 6.2.2.No: 6.3.However information about ice condition not hindering navigation may be...6.4.One ICEM is always valid for one single stretch of...6.5.Measurement time is to be entered. The respective ice conditions...6.5.1.Ice_condition_code 6.5.2.Ice_accessibility_code 6.5.3.Ice_classification_code 6.5.4.Ice_situation_code (the ice situation code should always be provided to...6.6.The ICEM can be published. Ice messages will be valid...7.WERM basic considerations 8.Rules for certain elements 8.1.Rules for the element ‘name’ related to objects 8.2.Rules for the element ‘name’ related to fairways 8.3.Rules for the elements ‘value’ and ‘unit’ within limitations

B.NOTICES TO SKIPPERS ENCODING GUIDE FOR APPLICATION DEVELOPERS

1.Background & Structure 1.1.Purpose of NtS Encoding Guide 1.1.1.NtS Encoding Guide for editors 1.1.2.NtS Encoding Guide for application developers (this document) 2.NtS messages and sections Figure 2Visualisation of the NtS message structure: mandatory element (1), mandatory...3.WRM basic considerations 3.1.Filling of nts_number section in the WRM 3.2.Filling of WRM including predictions Figure 3Visualisation of water level prediction confidence interval: most probable value...(The x-axis shows the time; the y-axis shows the water...4.ICEM processes 4.1.New ICEM 4.2.Update of an existing ICEM 5.WERM basic considerations 5.1.Filling of nts_number section in the WERM 5.2.Filling of WERM ‘weather_category_code’ 6.FTM processes 6.1.New FTM 6.2.Update/withdrawal of an existing FTM 6.3.Waterway and/or object related FTM 6.4.Automatic ordering of limitation codes 6.5.Handling of limitation period 7.General implementation rules 7.1.Filling of the ‘number_section’ 7.2.Filling of elements ‘from’, ‘originator’, ‘organisation’ and ‘source’ 7.3.Omission of elements 7.4.Automatic filling of date_issue 7.5.Handling of time zone information in NtS messages 7.6.Handling of Seconds in NtS messages 7.7.Format of decimals in NtS messages 7.8.Units to be used in NtS messages 7.9.Rules for the elements ‘name’, ‘position_code’ and ‘type_code’ Table 1Matching ‘RIS Index function_code’ — ‘NtS type_code’ 7.10.Rules for the element ‘fairway_name’ 7.11.Clarifications for translations in the spreadsheet ‘reference_code’ 7.12.Recommendation for the element ‘coordinate’ 7.13.Handling of target groups 7.14.Display of valid messages at a given time 7.15.Optional functions to increase user friendliness of NtS editor tools...8.NtS XML Message Structure 9.NtS Web Service 9.1.Objective 9.2.Basic Principles and constraints 9.2.1.Web standards 9.2.2.Interaction model and encoding method for NtS WS 9.3.General specifications and recommendations 9.3.1.Specification: Version information 9.3.2.Specification: Structure of namespaces 9.3.3.Recommendation: Use of namespaces 9.3.4.Recommendation: Use of namespace prefixes 9.3.5.Specification: Use of ISRS Location Codes Invalid ISRS Location Code queries Case 1: No ids element in request Valid query without ids parameter Case 2: One id element in request Valid query with one id parameter Matching and not matching messages for one id parameterCase 3: Two id elements in request Valid query with two id parameters Matching and not matching messages for two id parameters Combination: Multiple ids elements in request Valid query with multiple ids elements 9.4.NtS Message Service (implementation specification) 9.4.1.Request 9.4.2.Response 9.5.Generation of services and clients Glossary

Appendix C

Appendix D

Commission Implementing Regulation (EU) 2018/2032

of 20 November 2018

amending Commission Regulation (EC) No 416/2007 concerning the technical specifications for Notices to Skippers

THE EUROPEAN COMMISSION,

Having regard to the Treaty on the Functioning of the European Union,

Having regard to Directive 2005/44/EC of the European Parliament and of the Council of 7 September 2005 on harmonised river information services (RIS) on inland waterways in the Community1, and in particular Article 5, paragraph 1, point (c), thereof,

Whereas:

(1)

Commission Regulation (EC) No 416/20072 should be updated, further refined and clarified taking into account the technological progress and experience gained from the application of Regulation (EC) No 416/2007.

(2)

The technical specifications for Notices to Skippers should be based on the technical principles set out in Annex II to Directive 2005/44/EC.

(3)

In order to improve safety of navigation, Notices to Skippers should be extended to include a new type of message dedicated to weather-related notices.

(4)

The reference tables related to gauges should be eliminated from the Annex to Regulation (EC) No 416/2007, because the reference data contained therein, such as reference values for low and high water level, are dynamic. Such data should be included and maintained in the European Reference Data Management System operated by the Commission.

(5)

There is a need to improve the consistency of editing and application development in order to create services with a higher level of interoperability. Therefore, Encoding Guides for editors and application developers should be included in the technical specifications as Appendix A and B to the Annex.

(6)

Data exchange between the authorities is recommended according to Regulation (EC) No 416/2007. In order to improve such data exchange, specifications related to the data exchange should be set out in Appendix D to the Annex in order to allow Member States make their systems interoperable.

(7)

In order to ensure that Member States are able to encode Notices to Skippers messages in a consistent and interoperable manner, the Reference tables included in Appendix E should be improved. For this purpose, new codes should be defined in a new Reference table containing harmonised search interface labels for the graphical user interface. Moreover, new tags, values and codes should be added to existing Reference tables and redundant items should be removed.

(8)

The revised technical specifications should ensure that the reference tables in Appendix E are also available electronically in the European Reference Data Management System operated by the European Commission.

(9)

In accordance with Article 12(2) of Directive 2005/44/EC, in order to comply with Article 4 of this Directive, Member States should take the necessary measures to implement the requirements laid down in this Regulation not later than 30 months after its entry into force.

(10)

Regulation (EC) No 416/2007 should therefore be amended accordingly.

(11)

The measures provided for in this Regulation are in accordance with the opinion of the Committee referred to in Article 11 of Directive 2005/44/EC,

HAS ADOPTED THIS REGULATION: