Notices to Skippers (NtS) were being implemented in various European countries based on Commission Regulation 416/2007/EC of the European Parliament and of the Council concerning the technical specifications for Notices to Skippers as referred to in Article 5 of RIS directive 2005/44/EC. The NtS standard is in the continuous process of enhancement, a major step forward was the release of the NtS Web Service facilitating exchange of NtS messages between authorities as well as between authorities and NtS users as well as NtS XSD 4.0 streamlining the encoding of NtS messages.
The NtS Encoding Guide explains the applicability of the four NtS message types as well as codes to be used in case of certain events. It provides NtS editors with NtS message filling instructions, thus allows nationally and internationally harmonised encoding of NtS messages.
Considering increased use of the NtS web service, NtS messages shall be further harmonised to ensure proper display of content on third party systems. Uniform encoding of messages is also a prerequisite for consideration of messages in voyage planning applications. The NtS Encoding Guide version 1.0 applies to NtS XSD 4.0 and the NtS Web Service WSDL 2.0.4.0.
The NtS Encoding Guide for editors is intended for personnel editing (and publishing) NtS messages including step-by-step creation instructions for the proper message types as well as explanation of codes. The encoding guide for editors also includes relevant information for application developers.
The NtS Encoding Guide for developers includes guidelines for NtS application implementation explaining logic, processes and auto/default values.
An NtS message consists of the following:
the identification section,
section defining the applicable object(s) or fairway section(s) the message is related to,
one or more of the following sections according to the message type:
limitation(s) for the Fairway and traffic related message,
measurement(s) for the Water level related message,
ice condition(s) for the Ice related message,
weather report(s) for the Weather related message.
The identification section is mandatory and includes general information about the message originator, sender, date issue, country and original language and is provided together with one of the four different NtS message section types:
Fairway and traffic related section: a ‘Fairway and Traffic related Message’ (FTM) is usually created by NtS editors following the NtS Encoding Guide for editors. It is related to stretches of waterways (defined by its begin and end ISRS Location Codes and/or objects on the waterway defined by their respective ISRS Location Code. [go to chapter 6]
Water level related section: a ‘Water Related Message’ (WRM) facilitates provision of information on current and predicted water levels as well as other information. Usually WRM are created automatically (and periodically) based on sensor measurements or infrastructure status not requiring NtS editor interaction. The water related message section contains information for an object (e.g. gauge station) or a fairway section (e.g. least sounded depth for a stretch, applicable regime at a waterway section). The object is identified by its ISRS Location Code, the fairway section is defined by its begin- and end-ISRS Location Codes. [go to chapter 3]
Ice related section: an ‘ICE Message’ (ICEM) contains information about the ice conditions for a fairway stretch defined by its begin- and end-ISRS Location Codes. [go to chapter 4]
Weather related section: a ‘WEather Related Message’ (WERM) enables provision of information on current as well as forecasted weather situations on a waterway stretch defined by its begin- and end-ISRS Location Codes. [go to chapter 5]
In addition, the ISRS Location Code (International Ship Reporting Standard) is used to define the applicable object(s) or fairway section(s) the message is related to.
The ISRS location code is defined in point 4.3 of the Annex to this Regulation.
Water level information is very important for voyage planning as well as safety. At the moment there is no common standard of referencing water level information. The values of gauges are referring to different sea-levels or to special reference points. To provide a proper reference, the respective ‘reference_code’ shall always be provided together with the value. WRM may be used to provide the following information:
Water level (including predictions),
Least sounded depth (including predictions),
Vertical clearance (including predictions),
Discharge (including predictions),
Barrage status,
Regime.
Clarifications for translations in the spreadsheet ‘reference_code’ are provided in chapter 7.11.
Usually WRM are created and published automatically based on information received from sensor equipment or information received from infrastructure (e.g. predictions, barrage status). There may be different triggers for WRM publication, e.g. periodically or when certain values are reached.
In NtS XSD 4.0 the NtS number is optional within WRM messages. If it is provided every number has to be unique (Organisation/Year/Number/Serial) per message type and it is up to the organisation providing the WRM to ensure unique numbers (it is not required to have consecutive numbers).
The date_start of validity_period has to be filled with present date (date_issue) and the date_end of validity_period has to be filled with the next day after date_issue.
To provide changes in e.g. water level in a user-friendly way the difference to a previous comparative measurement may be provided in the WRM difference section. Besides the change in the value (e.g. - 5 [cm]) also the time difference to the comparative measurement has to be provided.
In case of predictions the ‘measure_date’ is the date/time the prediction is valid for.
Water level predictions always include a factor of uncertainty. Usually models with different parameters (e.g. weather forecast) are calculated leading to different predicted water level values. To enable provision of a minimum and maximum predicted value e.g. visualisation of a water level prediction confidence interval, two additional optional data fields are included in the WRM ‘measure’ section.
An illustration of water level prediction confidence interval is given in the following figure:
Two elements are available in the NtS XSD:
<value_min> lowest value of confidence interval
<value_max> highest value of confidence interval
Besides predicted water levels the confidence interval may also be used to state the uncertainty of published least sounded depth and vertical clearance information.
The confidence interval value_min and value_max enable provision of WRM value confidence interval via standardised NtS WRM Message to use it in graphs. The raw data itself shall not be displayed to IWT users (e.g. in code format).
The measure_code ‘NOM’ must not be used. In case there is no measurement for a certain type of WRM the value elements have to be omitted if a message should be sent anyhow.
Ice Messages depend on local observation and assessment and will usually be generated manually (in case of automatic generation the rules for manual creation have to be followed, see NtS Encoding Guide for editors).
The ICEM is published for a certain fairway_section defined by its begin and end ISRS Location Codes and contains the ice_condition at a certain measurement date.
The validity of the ICEM starts at the date of publication (automatically set by the NtS application). In order to avoid ICEM being displayed to users that are not valid any more, the validity date_end has to be filled automatically by the NtS application with the day after publication (unless it is ensured by national processes that messages will get a validity date end as soon as the information included in the message is not up-to-date any more).
In the NtS Encoding Guide for editors it is described under which circumstances an NtS editor creates a new ICEM or updates an existing ICEM. The following processes apply:
NtS applications may offer NtS editors:
to use existing notices as draft upon creation of new ICEM (e.g. if ice conditions are similar to the existing notice); and/or
to use notice templates for certain situations.
The content (e.g. time of measurement or respective ice conditions) has to be entered by the editor in line with chapter 6 of the NtS Encoding Guide for editors. The date and time of measurement could also be set by the application according to national definitions.
When an NtS editor/publishers triggers the publish action:
it is checked if all mandatory content is provided in line with the NtS XSD (if not go back to (2));
the nts_number is generated by the NtS application:
the ‘organisation’ is filled with the name or code of the responsible organisation depending on the role of the publishing user;
the ‘year’ is filled with the current year;
the next available ‘number’ is assigned;
the ‘serial number’ 0 is assigned;
‘date_issue’ is automatically filled with the actual date/time of publish action;
‘validity_period’ — ‘date_start’ is automatically filled with the actual date of publication;
‘validity_period’ — ‘date_end’ is automatically filled with the next day after the date of publication (unless it is ensured by national processes that messages will get a validity date end as soon as the information included in the message is not up-to-date any more).
The respective published message has to be selected to be updated in the ICEM editor tool. The original ICEM has to be copied or altered in the DB (depending on national processes). Expired ICEM (which passed the validity_date_end) cannot be updated any more, if this is the case NtS editors have to create a new ICEM.
The content (e.g. time of measurement or respective ice conditions) has to be altered by the editor in line with chapter 6 of the NtS Encoding Guide for editors. The date and time of measurement could also be altered by the application according to national definitions.
When an NtS editor/publisher triggers the publish action:
it is checked if all mandatory content is provided in line with the NtS XSD (if not, go back to (2));
the nts_number is generated by the NtS application:
the ‘organisation’ stays unchanged;
the ‘year’ stays unchanged;
the ‘number’ stays unchanged;
the ‘serial number’ is incremented (increased by 1);
‘date_issue’ is automatically filled with the actual date/time of publish action;
‘validity_period’ — ‘date_start’ is automatically filled with the actual date of publication;
‘validity_period’ — ‘date_end’ is automatically filled with the next day after the date of publication (unless it is ensured by national processes that messages will get a validity date end as soon as the information included in the message is not up-to-date any more).
Usually WERM are created and published automatically based on information received from sensor equipment or information received from infrastructure. The date_start of validity_period has to be filled with present date (date_issue) and the date_end of validity_period has to be filled with the next day after date_issue.
The fairway section in WERM is indicated as a stretch between two points on the fairway, i.e. area of applicability of the weather station (gauge).
Date and time of measurement/forecast have to be provided even if it is not mandatory in WERM messages.
In case of forecasts the ‘measure date’ is the date/time the forecast is valid for.
In NtS XSD 4.0 the NtS number is optional within WERM messages. If it is provided every number has to be unique (Organisation/Year/Number/Serial) per message type and it is up to the organisation providing the WERM to ensure unique numbers (it is not required to have consecutive numbers).
The wind speed in ‘weather_category_code’ (values 0 to 12) shall be provided in line with the Beaufort scale published by the World Meteorological Organization in its Manual on Marine Meteorological Services ‘WMO-No 558’.
The visibility in ‘weather_category_code’ (values 13 to 22) shall be provided as defined in the following table:
Value, meaning | Visibility | Additional information
13, thick fog | below 50 metres |
14, dense fog | below 100 metres |
15, moderate fog | below 200 metres |
16, fog | below 1000 metres | Fog consists of water droplets.
17, mist | from 1 km to 4 km | Mist consists of water droplets. Mist is used in case of ‘dry fog’, this phenomenon usually takes place before sunrise.
18, haze | from 1 km to 4 km | Haze consists of dry particles.
19, light haze | from 4 km to 10 km |
20, clear | from 10 km to 20 km |
21, very clear | no limitation of visibility |
22, no fog | | ‘no fog’ is used to state that there is no fog depending on national/local requirements.
In the NtS Encoding Guide for editors it is described under which circumstances an NtS editor creates a new FTM or updates an existing FTM. The following processes apply:
NtS applications may offer NtS editors to:
use existing notices as draft upon creation of new FTM; and/or
use notice templates for certain situations.
The content (e.g. time of validity, limitations) has to be entered by the editor in line with chapters 3 and 4 of the NtS Encoding Guide for editors.
When an NtS editor/publisher triggers the publish action:
it is checked if all mandatory content is provided in line with the NtS XSD (if not go back to (2));
the nts_number is generated by the NtS application:
the ‘organisation’ is filled with the name or code of the responsible organisation depending on the role of the publishing user:
the ‘year’ is filled with the current year;
the next available ‘number’ is assigned, in case a dedicated number was entered by the NtS editor or an application process in step 2 it is taken over (given that (Organisation/Year/Number/Serial) is unique as explained in chapter 15.1;
the ‘serial number’ 0 is assigned;
‘date _issue’ is automatically filled with the actual date/time of publish action
The respective published message has to be selected to be updated in the FTM editor tool, the original FTM has to be copied or altered in the DB (depending on national processes).
Expired FTM (which passed the validity_date_end) cannot be updated any more, if this is the case NtS editor has to create a new FTM.
The subject code ‘Notice withdrawn’ is only used if:
present date is before the validity_date_start. In case only the content of the field ‘additional information in national language’ may be altered, the coded content of the message (step 2) has to stay unchanged;
the validity period already started and the new end date for all limitations is in the past. The end date of the limitation has to be set to the correct time.
If a notice is withdrawn the validity period date end always has to be set to date of withdrawal.
The content (e.g. time of validity, limitations) has to be altered by the editor in line with chapters 3 and 4 of the NtS Encoding Guide for editors.
When an NtS editor/publisher triggers the publish action:
it is checked if all mandatory content is provided in line with the NtS XSD (if not go back to (2));
the nts_number is generated by the NtS application:
the ‘organisation’ stays unchanged;
the ‘year’ stays unchanged;
the ‘number’ stays unchanged;
the ‘serial number’ is incremented (increased by 1);
‘date_issue’ is automatically filled with the actual date/time of publish action
FTM with subject code ‘Notice withdrawn’ shall not be considered for voyage planning (any more).
A waterway related FTM contains information about one or several stretches of waterway. A waterway stretch is defined in the ‘fairway_section’ part by its begin and end ISRS Location Codes.
An object related FTM contains information about one or several specific objects on the waterway. An object is defined in the ‘object’ part by its ISRS Location Code.
One FTM has to refer
to one or several fairway sections, or
to one or several objects on one or several fairway sections.
Different limitations have different impact on navigation. In order to allow display of the most severe limitation e.g. in an FTM list overview, the following order shall be considered starting with the most severe limitation having Rank 1:
Rank | Value | Meaning (EN)
1 | OBSTRU | blockage
2 | PAROBS | partial obstruction
3 | NOSERV | no service
4 | SERVIC | changed service
5 | VESDRA | vessel draught
6 | VESBRE | vessel breadth
7 | CONBRE | convoy breadth
8 | VESLEN | vessel length
9 | CONLEN | convoy length
10 | CLEHEI | clearance height
11 | VESHEI | vessel air draught
12 | AVALEN | available length
13 | CLEWID | clearance width
14 | AVADEP | available depth
15 | LEADEP | least depth sounded
16 | DELAY | delay
17 | ALTER | alternate traffic direction
18 | TURNIN | no turning
19 | PASSIN | no passing
20 | OVRTAK | no overtaking
21 | NOBERT | no berthing
22 | NOMOOR | no mooring
23 | ANCHOR | no anchoring
24 | SPEED | speed limit
25 | WAVWAS | no wash of waves
26 | NOSHORE | not allowed to go ashore
27 | MINPWR | minimum power
28 | CAUTIO | special caution
29 | NOLIM | no limitation
Limitations with the same limitation periods should be grouped/listed together/combined for display to keep it reader-friendly.
NtS editor tools should provide a function for editors to avoid re-typing of limitation periods.
All limitations have to include a limitation period with an interval code in order to allow proper calculations within voyage planning applications. To ease the work of NtS editors the following functions may be implemented:
The NtS editor tool may provide a function to copy already entered limitations to avoid re-typing of the limitation period by the NtS editor.
The NtS editor tools may provide a function to select more than one limitation code for a specific limitation period and automatically create the required limitation sections based on the information entered by the NtS editor.
‘Monday to Friday except public holidays’: The value ‘holidays’ is very difficult for voyage planning applications. A list of holidays for each country is needed for proper calculation. If no such list is available the respective limitations will be assigned to the public holidays nevertheless.
‘with the exception of’: must not be used; Interrupted intervals have to be given as separate limitation periods within the same limitation, therefore this code shall not be displayed/available to notice editors.
Logic and display of information applicable in case of interval code ‘continuous’:
<date_start>2015-04-01+01</date_start>
<date_end>2015-06-30+02</date_end>
<time_start>06:00:00</time_start>
<time_end>10:00:00</time_end>
<interval_code>CON</interval_code>
If the interval_code is continuous the start_time belongs to the start_date and the end_time belongs to the end_date e.g. from 1 April 06:00 to 30 June 10:00
Logic and display of information applicable in case of any other interval code than ‘continuous’:
<date_start>2015-04-01+01</date_start>
<date_end>2015-06-30+02</date_end>
<time_start>06:00:00</time_start>
<time_end>10:00:00</time_end>
<interval_code>WRK</interval_code>
If the interval_code has another value the start_time and end_time belongs to this interval_code e.g. from 1 April to 30 June Monday to Friday from 06:00 to 10:00
The limitation time end always has to be filled in the last version of a message.
The following is to be considered:
The table ‘GUI_labels’ provided in the NtS Reference Tables shall be considered when building NtS applications (search masks, e-mail subscription form, display of messages).
The date_end cannot be before date_start.
Codes that have been disabled (are not to be used any more) via NtS change requests (see comments in the NtS XSD) shall not be displayed to NtS editors upon creation of new messages. The codes are still included in the NtS XSD enumerations for backwards compatibility.
Every number (Organisation/Year/Number/Serial) has to be unique per message type. That means that messages of different types can have the same NtS Number.
For users the message numbers are only relevant for FTM and ICEM, for all other message types display of the message number can be skipped depending on national requirements.
To users the message number shall be displayed in the following format ‘Message Type/Country/Organisation/Year/Number/Serial’ (it can be shortened depending on applied filters if no information gets lost).
The element ‘from’ in the identification section is filled with the name of the national system that provides the message (e.g. ELWIS, DoRIS, SLOVRIS, FLARIS).
The element ‘originator’ is the organisation which enters the messages into the national systems.
The element ‘source’ is the authority for which the FTM are published.
The element ‘organisation’ within the nts_number section is the name of the organisation assigning the nts_number (NtS Provider).
Elements that would contain only standard or default values shall be omitted if they are conditional, they lead to message overhead with no added value.
Following elements are concerned:
Target Group: target_group_code ALL with direction_code ALL (if there are no other specific target groups within the message),
position_code: AL,
reason_code: OTHER.
FTM and ICEM
For FTM and ICEM the value of date_issue element is the actual date and time of publishing. In case of updated messages date_issue is the date and time when the update was published.
WRM and WERM
For WRM and WERM the value of date_issue element is the date and time of the processing request, because there can be several measurements with different issuing time stamps within one W(E)RM message.
Date and time shall always be provided in local time including time zone information within the NtS XML messages.
The only exceptions from this provision are the ‘time_start’ and the ‘time_end’ within the ‘limitation_period’ section. This is because in the limitation section an interval can be applied. If date start and date end have different time regimes (e.g. CEST and CET) this would result in a change of the time zone information within this interval. This change cannot be expressed via a single limitation period. Instead of creating different limitation periods for each time change only a single limitation period without time zone information is used to reduce overhead in message processing and transmission.
As a general rule seconds have to be provided in (date)/time fields but shall not be displayed to NtS users. Minutes are sufficient for NtS granularity.
Decimals in numeric fields are indicated with a . (period). No thousand separators are used.