S-57 Edition 3.1 Encoding Bulletins

Bulletins de codage de l’édition 3.1 de la S-57

S-57 Edition 3.1 Encoding Bulletins: S-57 is the IHO standard for the exchange of digital hydrographic data.  It has been used almost exclusively for encoding Electronic Navigational Charts (ENCs).  However there is a need for S-57 to support additional requirements, which has prompted the IHO to develop the S-100 (IHO Universal Hydrographic Data Model) which will eventually supersede S-57.  It is anticipated however that S-57 Edition 3.1 will continue to be used to produce ENCs for the foreseeable future.

In 2000, as S-57 Edition 3.1 was being widely used in both production and navigation systems, the IHO froze the contents of Edition 3.1 and no further changes could be made to it.  As increasing numbers of hydrographic organizations began to encode ENC data, it was recognised that variations in the way different producers encode data may lead to inconsistencies.  Furthermore unanticipated issues that affect how the ENCs are displayed or used by an ECDIS may arise, and may need to be addressed by changing the way in which the ENC data are encoded.

Because Edition 3.1 was frozen, changes could not be made to the actual standard to address such issues.  In order to promulgate IHO approved changes in encoding guidance, "Encoding Bulletins" are developed to communicate how data producers may modify their encoding practices to address those issues that affect the use of ENC data in ECDIS.  Each Bulletin explains a particular ENC/ECDIS issue; recommended procedures for addressing the issue; and the consequences of not following the recommended procedures. It should be noted that the procedures described in these Bulletins are not compulsory; however it is strongly recommended that data producers follow them wherever possible to ensure the consistency of ENC production worldwide.

In 2010, the IHO approved the “unfreezing” of S-57 Appendix B.1, Annex A – Use of the Object Catalogue for ENC (UOC).  This was done in order to transfer new and revised ENC encoding guidance incorporated in these Encoding Bulletins, and in other IHO publications, into the authoritative IHO ENC encoding guidance document.  Encoding Bulletins that have been transferred into the UOC will maintain their reference in the Encoding Bulletins list, and the guidance included in each Bulletin will be replaced with the appropriate UOC clause references.  Future new or revised ENC encoding guidance will be added as new Encoding Bulletins, which will subsequently be incorporated in future New Editions of the UOC as required.

These Bulletins have resulted from proposals brought to the attention of the Transfer Standard Maintenance and Application Development Working Group (TSMADWG). New bulletins must be approved by the TSMADWG.
 

 

Bulletins de codage de l’édition 3.1 de la S-57 : la S-57 est la norme de l’OHI pour l’échange des données hydrographiques numériques. Elle est utilisée pratiquement exclusivement pour le codage des cartes électroniques de navigation (ENC). La S-57 doit néanmoins répondre à des besoins supplémentaires, ce qui a conduit l’OHI à développer la S-100 (Modèle universel de données hydrographiques de l’OHI) qui remplacera en fin de compte la S-57. Il est toutefois escompté que l’édition 3.1 de la S-57 continuera d’être utilisée pour produire les ENC dans les années à venir.

En 2000, étant donné que l’édition 3.1 de la S-57 était largement utilisée dans les systèmes de production et de navigation, l’OHI a « gelé » le contenu de l’édition 3.1 et aucun autre changement n’a pu y être apporté. A mesure qu’un nombre croissant d’organismes hydrographiques ont commencé à coder les données des ENC, on a constaté que les diverses façons dont les différents producteurs codent les données peuvent aboutir à certaines incohérences. Par ailleurs, des problèmes imprévus affectant la manière dont les ENC sont affichées ou utilisées par les ECDIS peuvent survenir et devoir être résolus en modifiant la façon de coder les données des ENC.

En raison du gel de l’édition 3.1, il n’a pas été possible d’apporter de changements à la norme actuelle pour résoudre ces problèmes. Afin de diffuser les modifications des directives de codage approuvées par l’OHI, des « bulletins de codage » sont élaborés pour décrire comment les producteurs de données peuvent modifier leurs pratiques de codage afin de résoudre les problèmes qui affectent l’utilisation des données des ENC dans les ECDIS. Chaque bulletin explique un problème spécifique lié aux ENC et aux ECDIS ; les procédures recommandées pour régler le problème et les conséquences de ne pas suivre les procédures recommandées. Il convient de noter que les procédures décrites dans ces bulletins ne sont pas obligatoires ; il est néanmoins vivement recommandé aux producteurs de données de les suivre, chaque fois que possible, afin d’assurer la cohérence de la production des ENC à l’échelle mondiale.

En 2010, l’OHI a approuvé le « dégel » de l’Annexe A – Utilisation du catalogue des objets pour les ENC (UOC) de l’Appendice B.1 à la S-57. Ceci a été fait dans le but de transférer les directives de codage des ENC nouvelles et révisées, incorporées dans ces bulletins de codage et dans d’autres publications de l’OHI, vers un document officiel contenant les directives de codage des ENC de l’OHI. Les bulletins de codage qui ont été transférés dans l’UOC conserveront leur référence dans la liste des bulletins de codage et les directives incluses dans chaque bulletin seront remplacées par un renvoi aux clauses appropriées de l’UOC. Les directives de codage des ENC nouvelles ou révisées seront ajoutées en tant que nouveaux bulletins de codage, lesquels seront ensuite incorporés dans les futures nouvelles éditions de l’UOC, selon qu’il convient.

Ces bulletins résultent de propositions portées à l’attention du groupe de travail sur la maintenance et le développement d’applications de la norme de transfert (TSMAD ). Les nouveaux bulletins doivent être approuvés par le TSMAD conformément à son mandat .

 

INDEX


ENC Product Specification (ENC PS), including Use of the Object Catalogue (UOC)

 1. UOC clause 10.1.1 Navigational lines and recommended tracks; 10.2.2 Deep Water Route Centrelines; and 10.2.4 Recommended Routes [Updated – Feb 2012]

 1.a UOC Clause 10.1.1 Navigational lines (NAVLNE) and recommended tracks (RECTRC)  SUPERSEDED
 
1.b UOC Clause 10.2.2.2 Deep Water Route Centerlines (DWRTCL)  SUPERSEDED
 
1.c  UOC Clause 10.2.4 Recommended Route Centerline (RCRTCL)   SUPERSEDED
 2. UOC Clause 6.2.1 - Wrecks SUPERSEDED
 3. UOC Clause 6.2.2 – Obstructions and foul areas SUPERSEDED
 
4. UOC Clause 4.8.5 – Dams (DAMCON)
 5. UOC Clause 11.9.1 - Fishing facilities (FSHFAC)
 6. UOC table 6.2 Wrecks
 7. UOC table 6.3 Obstructions
 8. UOC Clause 6.6 Caution areas [Updated – October 2011]
 9. UOC Clause 12.8.6.5 Directional lights (LIGHTS) [Feb 2007]
10. UOC Clauses 4.6.6.2 Floating Docks (FLODOC) [Feb 2007]
11. UOC Clauses 4.6.7.3 Pontoons (PONTON) [Feb 2007]
12. UOC Clause 4.1 Land Area (LNDARE) [Feb 2007]
13. UOC Clause 4.8.14 Built-up areas (BUAARE)
SUPERSEDED
14. UOC Clause 12.1.2 Relationships [Feb 2007]
15. UOC Clause 11.2 Maritime jurisdiction areas [Jan 2008]
16. UOC Clause 11.2 Maritime jurisdiction areas: Disputed claims [Jan 2008]
17. Automatic Identification System (AIS) in ENC [Updated – October 2011]
18. ENC PS Clause 2.2 Cells: 180º Meridian of Longitude [Jan 2008]
19. UOC Clause 12.4.1 Buoys: Emergency Wreck Marking Buoy [Jan 2008]
20. ENC PS Clause 5.6 File naming: Use of _ (underscore) [Jan 2008]
21. External text files in national language [Jan 2008]
22. ENC PS Clause 5.4.1 Content of the exchange set [April 2008]
23. UOC Clause 5.4.1 Geo object depth areas [December 2008]
24. UOC Clause 2.1.5.1 Seasonal objects and Clause 2.6.1 Issuing updates in advance [Updated - March 2012]
25. UOC Clause 10.2.1 Traffic separation schemes [Updated - May 2010]
26. UOC Clause 12.8.6.1 Sector lights [April 2009]
27. UOC Clause 5.3 Soundings [April 2009]
28. ENC PS Clause 3.5.7 New attribute values in Edition 3.1 [June 2009]
29. ENC PS Clause 3.3 Objects permitted for use in ENC and their geometric primitives [Updated - May 2010]
30. UOC Clause 12.8.7 Various special types of lights [June 2009]
31. ENC PS Clause 5.7 Updating and UOC Clause 2.6 Updating [June 2009]
32. UOC Clause 6.2.1 Wrecks [June 2009]
33. ENC Product Specification Clause 3.1 Feature Object Identifiers [May 2010]
34. UOC Clause 12.1.2 Relationships [Updated – October 2011]

35. UOC Clause 6.2.2 Obstructions, foul areas and foul ground [October 2011]

36. UOC Clause 11.7.4 Offshore production areas [October 2011]

37. UOC Clause 1.1.1 References within S-57 to other IHO publications [October 2011]

38. UOC Clause 5.5 Dredged areas [October 2011]

39. UOC Clause 6.6 Caution areas [October 2011]

40. UOC Clauses 10.2.2.1 Deep water route parts; 10.2.3 Traffic separation scheme systems; and 10.2.6 Two-way routes [October 2011]

41. UOC Clause 15 Collection objects [October 2011]

42. UOC Clause 9.2.1 Anchorage Areas [May 2012]

43. UOC Clauses 6.1.2 Rocks which may cover; 6.2.1 Wrecks; and 6.2.2 Obstructions, foul areas and foul ground [May 2012]

44. UOC Clause 3.1.1 Magnetic variation [May 2012]

45. UOC Clause 5.8 Areas with inadequate depth information [May 2012]

46. UOC Section 2 Cartographic framework [May 2012]

47. UOC Clause 4.7.11 Vegetation [May 2012]

48. UOC Clause 2.8.1 Wide blank area [May 2012]

49. UOC Clause 2.3 Textual information  [August 2012]

50. UOC clause 4.8.20 Views and sketches, viewpoints [August 2012]

51. UOC section 4 Topography [August 2012]

52. UOC clause 2.7 Multiple objects [August 2012]

53. UOC Clause 12.8.1 Description of lights [October 2012]

 

Maintenance Document
 MD8 revision to 1.Co.10

 

Use of the Object Catalogue - Appendix B.1, Annex A - Encoding Bulletins (EB)

 

EB1 - UOC Clauses 10.1.1 Navigational lines and recommended tracks; 10.2.2.2 Deep water route centrelines; and 10.2.4 Recommended routes

Please note this Encoding Bulletin SUPERSEDES EB1a, EB1b and EB1c below.

Revised encoding guidance regarding the resultant direction of line geometry for one way recommended tracks, deep water route centrelines and recommended route centrelines  has been included in UOC Edition 3.1.0 (October 2012) – Clauses 10.1.1, 10.2.2.2 and 10.2.4.

 

<Back to Index>

 

 EB1a - UOC Clause 10.1.1 Navigational lines (NAVLNE) and recommended tracks (RECTRC)

Please note that item EB1a, EB1b and EB1c have been SUPERSEDED by EB1 above

The third bullet point of clause 10.1.1 of Edition 2.1 (April 2002) of the Use of the Object Catalogue (S-57 Appendix B1, Annex A) states: "When the traffic flow is one way, the direction of digitising of an object of type line should be the same as the direction of the traffic flow".

The use of the word 'should' in this sentence means that the advice is only recommended and not mandatory. However, if this rule is not followed and navigation lines and recommended tracks are digitised in the opposite direction, the direction arrows shown on ECDIS displays will show the direction of traffic flow incorrectly.

Encoders are strongly advised, therefore, to follow this rule and digitise such lines in the direction of the traffic flow thereby avoiding possible ECDIS display problems.

 

<Back to Index>

 

EB1b - UOC Clause 10.2.2.2 Deep Water Route Centerline (DWRTCL)

As per 1.a above, the first remark, in clause 10.2.2.2 needs to have its obligation changed from "should" to "must" i.e. "When the traffic flow is one way (attribute TRAFIC = 3), the direction of digitising should must be the same as the direction of traffic flow, thereby avoiding possible ECDIS display problems."

This is required as the S-52 Presentation Library (Edition 3.3) actually calculates the bearing of the digitised line and displays the bearing text based on this calculation. (The PL does NOT use the attribute ORIENT to display this text).

 

<Back to Index>

 

EB1c - UOC Clause 10.2.4 Recommended Route Centerline (RCRTCL)

As per 1.a above the first remark, in clause 10.2.4 needs to have it's obligation changed from "should" to "must" i.e. "When the traffic flow is one way (attribute TRAFIC = 3), the direction of digitising should must be the same as the direction of traffic flow, thereby avoiding possible ECDIS display problems."

This is required as the S-52 Presentation Library (Edition 3.3) actually calculates the bearing of the digitised line and displays the bearing text based on this calculation. (The PL does NOT use the attribute ORIENT to display this text).

 

<Back to Index>

 

EB2 -UOC Clause 6.2.1 - Wrecks

Please note that this item has been SUPERSEDED as the result of changes made to the Conditional Symbology Procedure for displaying this object class in ECDIS.

 

<Back to Index>

 

EB3 - UOC Clause 6.2.2 – Obstructions and foul areas

Please note that this item has been SUPERSEDED as the result of changes made to the Conditional Symbology Procedure for displaying this object class in ECDIS.

 

<Back to Index>

 

EB4 - UOC Clause 4.8.5 – Dams (DAMCON)

Revised encoding guidance regarding a dam that has its seaward edge coincident with the coastline was included in UOC Edition 3.0.0 (October 2011) – Clause 4.8.5.

 

<Back to Index>

 

EB5 - UOC Clause 11.9.1 - Fishing facilities

New encoding guidance regarding fishing facilities located in deep water was included in UOC Edition 3.0.0 (October 2011) – Clause 11.9,1.

 

<Back to Index>

 

EB6 - UOC table 6.2 Wrecks

Revised encoding guidance regarding the population of the attribute QUASOU on WRECKS objects was included in UOC Edition 3.0.0 (October 2011) – Clause 6.2.1.

 

<Back to Index>

 

EB7 - UOC table 6.3 Obstructions

Revised encoding guidance regarding the population of the attribute QUASOU on OBSTRN objects was included in UOC Edition 3.0.0 (October 2011) – Clause 6.2.2.

 

EB8 - UOC Clause 6.6 Caution areas

New encoding guidance regarding lines demarcating collision regulation areas was included in UOC Edition 3.0.0 (October 2011) – Clause 11.13.5.

 

<Back to Index>

 

 

EB9 - UOC Clause 12.8.6.5 Directional lights (LIGHTS)

Revised encoding guidance regarding the orientation of directional and moiré effect lights was included in UOC Edition 3.0.0 (October 2011) – Clauses 12.8.6.5 and 12.8.6.6.

 

<Back to Index>

 

EB10 - UOC Clauses 4.6.6.2 Floating Docks (FLODOC)

Revised encoding guidance regarding temporal attribution for floating docks was included in UOC Edition 3.0.0 (October 2011) – Clause 4.6.2.2.

<Back to Index>

 

EB11 - UOC Clauses 4.6.7.3 Pontoons (PONTON)

Revised encoding guidance regarding temporal attribution for pontoons was included in UOC Edition 3.0.0 (October 2011) – Clause 4.6.7.3.

 

<Back to Index>

 

EB12 - UOC Clause 4.1 Land Area (LNDARE)

Revised encoding guidance regarding portrayal of names for land areas was included in UOC Edition 3.0.0 (October 2011) – Clause 4.7.1.

 

<Back to Index>

 

EB13 - UOC Clause 4.8.14 Built-up areas (BUAARE)

Please note that this item has been SUPERSEDED as the result of changes made to the IHO Presentation Library Look-Up Tables for displaying this object class in ECDIS.

 

<Back to Index>

 

EB14 - UOC Clause 12.1.2 Relationships

Revised encoding guidance regarding the role of the object class DAYMAR in a master to slave relationship was included in UOC Edition 3.0.0 (October 2011) – Clause 12.1.2.

 

<Back to Index>

 

EB15 - UOC Clause 11.2 Maritime jurisdiction areas

New guidance regarding the encoding of “linear” maritime jurisdiction areas was included in UOC Edition 3.0.0 (October 2011) – Clause 11.2.

 

EB16 - UOC Clause 11.2 Maritime jurisdiction areas: Disputed claims

New guidance regarding the encoding of overlapping Territorial Sea and Exclusive Economic Zone areas due to the areas being in dispute between two or more Coastal States was included in UOC Edition 3.0.0 (October 2011) – Clause 11.2.4.

 

<Back to Index>

 

EB 17 - Automatic Identification System (AIS) in ENC

New guidance regarding the encoding of AIS used as aids to navigation was included in UOC Edition 3.0.0 (October 2011) – Clause 12.14.1.

 

<Back to Index>

 

EB18 - ENC PS Clause 2.2 Cells: 180º Meridian of Longitude

New guidance regarding the production of ENC cells that may span the 180° Meridian of Longitude was included in UOC Edition 3.0.0 (October 2011) – Clause 2.1.8.2.

 

<Back to Index>

 

EB19 - UOC Clause 12.4.1 Buoys: Emergency Wreck Marking Buoy

New guidance regarding the encoding of IALA emergency wreck marking buoys was included in UOC Edition 3.0.0 (October 2011) – Clause 12.4.1.1.

 

<Back to Index>

 

EB20 - ENC PS Clause 5.6 File naming: Use of _ (underscore)

Clause 5.6 of edition 2.0 (November 2000) of the ENC Product Specification (S-57 Appendix B.1) is not prescriptive as to the characters allowed for ENC data set file naming, resulting in some ECDIS rejecting ENC files containing the _ (underscore) character in the file name. The S-57 Maintenance Document MD8 (March 2002) lists both a Clarification (1.Cl.37) and a Correction (1.Co.32) explaining the allowable character format to be as described in ISO 9660, level 1. The existence of both a Clarification and a Correction in MD8 has resulted in confusion as to whether the _ (underscore) character is allowable in S-57 Edition 3.1 file names.

Encoders should note, therefore, that ENC data set file names must be composed from the upper case alphanumeric characters A to Z and the digits 0 to 9 only. The use of any other character, such as _ (underscore) is prohibited.

[Jan 2008]

 

<Back to Index>

 

EB21 - External text files in national language

New guidance regarding the character encoding used for external text files in national language (referenced by NTXTDS) was included in UOC Edition 3.0.0 (October 2011) – Clause 2.3.

 

<Back to Index>

 

EB22 - ENC PS Clause 5.4.1 Content of the exchange set

Revised guidance regarding the formats to be used for text and picture files was included in UOC Edition 3.0.0 (October 2011) – Clauses 2.3 and 4.8.20.

 

<Back to Index>

 

EB23 - UOC Clause 5.4.1 Geo object depth areas

Revised guidance regarding the encoding of DEPARE objects of type line was included in UOC Edition 3.0.0 (October 2011) – Clause 5.4.1.

 

<Back to Index>

 

EB24 - UOC Clause 2.1.5.1 Seasonal objects and Clause 2.6.1 Issuing updates in advance

NOTE: The guidance included in this Encoding Bulletin applies only when it is required to indicate seasonality, or to issue update information in advance, and the temporal attributes introduced for some navigational aid equipment objects in S-57 Supplement No. 2 are not available on the ENC production system used by the Producing Authority.

Clause 2.1.5.1 of Edition 2.1 (April 2002) of the Use of the Object Catalogue for ENC (S-57 Appendix B.1, Annex A) provides guidance on the use of the attributes PEREND and PERSTA for the encoding of seasonal objects in ENC. Clause 2.6.1 of the Use of the Object Catalogue for ENC provides guidance on the provision of advance update information, including the use of the attributes DATEND and DATSTA.

New tests introduced in Edition 3 (2008) of International Electrotechnical Commission document IEC 61174 - Marine Navigation and Radio communication Equipment and Systems – Electronic Chart Display and Information Systems (ECDIS) – Operational Performance Requirements, Methods of Testing and Required Test Results, have resulted in the implementation of the use of these time varying attributes by ECDIS manufacturers in their ECDIS systems.


S-57 Appendix A, Chapter 1 – IHO Object Catalogue (November 2000) contains the list of allowable attributes for S-57 Object Classes. For some navigational aid equipment objects the following time varying attributes are not included in the allowable list: 

FOGSIG – PEREND, PERSTA;

RADSTA – PEREND, PERSTA;

RETRFL – DATEND, DATSTA, PEREND, PERSTA;

RTPBCN – PEREND, PERSTA;

TOPMAR – DATEND, DATSTA, PEREND, PERSTA.


Encoders are therefore advised that where a seasonal or periodic navigation aid contains at least one of the equipment objects FOGSIG, RADSTA, RETRFL, RTPBCN or TOPMAR, the time varying attributes PEREND and PERSTA should not be populated for any object comprising the navigation aid. To indicate seasonality for such navigation aids to the mariner, the attributes STATUS = 5 (periodic/intermittent) and INFORM containing details of the period should be populated.


Where a navigation aid contains one of the equipment objects RETRFL or TOPMAR, advance update information should not be issued. Therefore the attributes DATSTA or DATEND should not be populated for any object comprising the navigation aid. An update applying the temporal change to the navigation aid should be issued as close as possible to the date of the change.


Alternatively, if time varying attributes DATSTA and/or DATEND have been populated for components of a navigation aid that contains at least one of the equipment objects RETRFL or TOPMAR, a separate update applying the temporal change to these equipment objects should be issued as close as possible to the date of the change.


[Updated - March 2012]

 

<Back to Index>

 

EB25 - UOC Clause 10.2.1 Traffic separation schemes

New encoding guidance regarding advance notification of changes to traffic separation schemes was included in UOC Edition 3.0.0 (October 2011) – Clause 2.6.1.1.

 

<Back to Index>

 

EB26 - UOC Clause 12.8.6.1 Sector lights

New guidance regarding the encoding of oscillating light sectors was included in UOC Edition 3.0.0 (October 2011) – Clause 12.8.6.1.

 

<Back to Index>

 

EB27 - UOC Clause 5.3 Soundings

Revised encoding guidance regarding the population of the attribute EXPSOU on SOUNDG objects was included in UOC Edition 3.0.0 (October 2011) – Clauses 5.3 and 5.5.

 

<Back to Index>

 

EB28 - ENC PS Clause 3.5.7 New attribute values in Edition 3.1

Revised encoding guidance regarding the population of the attribute INFORM to describe the meaning for attribute values which appeared for the first time in S-57 Edition 3.1 was included in UOC Edition 3.0.0 (October 2011) – Clause 1.1.

 

<Back to Index>

 

EB29 - ENC PS Clause 3.3 Objects permitted for use in ENC and their geometric primitives

New guidance regarding features for which the encoding combination of object class and geometric primitive results in no display of the feature in ECDIS was included in UOC Edition 3.0.0 (October 2011) – Clauses 2.5; 4.6.6.6; 4.7.4; 4.7.7.1; 4.7.7.2; 4.7.11; 4.8.3; 4.8.5; 4.8.8; 4.8.10; 4.8.12; 4.8.13 and 11.6.1.

 

<Back to Index>

 

EB30 - UOC Clause 12.8.7 Various special types of lights

New guidance regarding the encoding of strip lights serving the purpose of an aid to navigation was included in UOC Edition 3.0.0 (October 2011) – Clause 12.8.7.

 

<Back to Index>

 

EB31 - ENC PS Clause 5.7 Updating and UOC Clause 2.6 Updating

New guidance regarding changing the area of data coverage of a published ENC cell and the maximum recommended file size for an ENC Update (ER) cell was included in UOC Edition 3.0.0 (October 2011) – Clause 2.6.

 

<Back to Index>

 

EB32 - UOC Clause 6.2.1 Wrecks

Revised encoding guidance regarding the population of attributes for WRECKS objects to aid in enhanced ECDIS portrayal was included in UOC Edition 3.0.0 (October 2011) – Clause 6.2.1.

 

<Back to Index>

  

EB33 - ENC PS Clause 3.1 Feature Object Identifiers

New encoding guidance regarding the population of the Feature Object Identifier (FOID) field was included in UOC Edition 3.0.0 (October 2011) – Clause 2.1.8.1.

 

<Back to Index>

  

EB34 - UOC Clause 12.1.2 Relationships

Revised guidance regarding the encoding of master to slave relationships for navigational aids, and the encoding of navigational aid base structures (on land or in the water) where the nature of the base structure is unknown, was included in UOC Edition 3.0.0 (October 2011) – Clause 12.1.2.

 

<Back to Index>

 

EB35 - UOC Clause 6.2.2 Obstructions, foul area and foul ground

New encoding guidance regarding the distinction between areas considered to be “foul areas” and areas considered to be “foul ground” was included in UOC Edition 3.0.0 (October 2011) – Clause 6.2.2.

 

<Back to Index>

 

EB36 - UOC Clause 11.7.4 Offshore production areas

New guidance regarding the encoding of offshore wind turbines and wind farms, wave energy devices, underwater turbines, and wave or current farms was included in UOC Edition 3.0.0 (October 2011) – Clause 11.7.4.

 

<Back to Index>

 

EB37 - UOC Clause 1.1.1 References within S-57 to other IHO publications

New advice regarding outdated references to IHO publications within S-57 documentation was included in UOC Edition 3.0.0 (October 2011) – Clause 1.1.1.

 

<Back to Index>

 

EB38 - UOC Clause 5.5 Dredged areas

Revised guidance regarding the encoding of the date of dredging for dredged areas was included in UOC Edition 3.0.0 (October 2011) – Clause 5.5.

 

<Back to Index>

 

 

 

EB39 - UOC Clause 6.6 Caution areas

New encoding guidance regarding the avoidance of the overuse of CTNARE and the geographic extent of encoded CTNAREs was included in UOC Edition 3.0.0 (October 2011) – Clauses 2.5 and 6.6.

 

 

 

<Back to Index>

 

 

EB40 - UOC Clauses 10.2.2.1 Deep water route parts; 10.2.3 Traffic separation scheme systems; and 10.2.6 Two-way routes

New guidance regarding the encoding of relationships between deep water routes, traffic separation schemes and two-way routes, and other routeing measures was included in UOC Edition 3.0.0 (October 2011) – Clauses 10.2.2.1; 10.2.3 and 10.2.6.

<Back to Index>
 

EB41 - UOC Clause 15 Collection objects

Revised guidance regarding the encoding of navigationally relevant information on C_AGGR and C_ASSO objects was included in UOC Edition 3.0.0 (October 2011) – Clause 15.

 

<Back to Index>

EB42 - UOC Clause 9.2.1 Anchorage Areas

New guidance regarding the encoding of anchorages such that the name displays in ECDIS has been included in UOC Edition 3.1.0 (October 2012) – Clause 9.2.1.

 

<Back to Index>

EB43 - UOC Clauses 6.1.2 Rocks which may cover; 6.2.1 Wrecks; and 6.2.2 Obstructions, foul areas and foul ground

New guidance regarding the encoding of the attribute EXPSOU on underwater rocks, wrecks and obstructions so as to improve ECDIS display has been included in UOC Edition 3.1.0 (October 2012) – Clauses 6.1.2, 6.2.1 and 6.2.2.

 

<Back to Index>

EB44 - UOC Clause 3.1.1 Magnetic variation

New guidance regarding the encoding magnetic variation information as areas in ENCs has been included in UOC Edition 3.1.0 (October 2012) – Clause 3.1.1.

 

<Back to Index>

EB45 - UOC Clause 5.8 Areas with inadequate depth information

New guidance regarding the encoding of bathymetry where source data is limited to satellite imagery has been included in UOC Edition 3.1.0 (October 2012) – Clause 5.8.1.1.

 

<Back to Index>

EB46 UOC Section 2 Cartographic framework

New guidance regarding the encoding of features in their true position where they may be displaced on the paper chart for cartographic reasons has been included in UOC Edition 3.1.0 (October 2012) – Clause 2.7.

 

<Back to Index>

 

EB47 UOC Clause 4.7.11 Vegetation

New guidance regarding the encoding of mangroves in the intertidal area has been included in UOC Edition 3.1.0 (October 2012) – Clause 4.7.11.

 

<Back to Index>

 

EB48 - UOC Clause 2.8.1 Wide blank area

New guidance regarding the spatial extent of the M_COVR objects comprising an ENC data set has been included in UOC Edition 3.1.0 (October 2012) – Clause 2.8.1.

 

<Back to Index>

 

EB49 - UOC clause 2.3 Textual information

New guidance clarifying the use of the attributes INFORM, NNFOM, TXTDSC and NTXTDS has been included in UOC Edition 3.1.0 (October 2012) – Clause 2.3.

 

<Back to Index>

 

EB50 - UOC clause 4.8.20 Views and sketches, viewpoints

  • New guidance regarding the recommended format and content of the associated picture files referenced by the attribute PICREP has been included in UOC Edition 3.1.0 (October 2012) – Clause 4.8.20. 

 

 

 

EB51 - UOC section 4 Topography

New guidance regarding the recommended level of topographic depiction for ENCs has been included in UOC Edition 3.1.0 (October 2012) – Clause 4.

 

<Back to Index>

 

EB52 - UOC clause 2.7 Multiple objects

New guidance clarifying the requirement to indicate multiple objects where they have been generalised to a single object on the source has been included in UOC Edition 3.1.0 (October 2012) – Clause 2.7.

 

<Back to Index>

 

EB53 - UOC Clause 12.8.1 Description of lights

Clause 12.8.1 of Edition 3.0.0 (October 2011) of the Use of the Object Catalogue for ENC (S-57 Appendix B1, Annex A) provides guidance for the encoding of lights, including the population of the attributes SECTR1 and SECTR2.  It is stated that the attributes SECTR1 and SECTR2 are “only for sector lights”.

In some cases lights that are visible all-round (omni-directional) have been encoded as LIGHTS objects with attributes SECTR1 = 0 and SECTR2 = 360. It has been reported that in some ECDIS LIGHTS objects which have been encoded in this way symbolize as a single dashed line, with no light flare or coloured “halo” to indicate that the light is visible all-round. This may result in screen clutter in some ECDIS display modes and could potentially confuse the mariner.

Encoders are advised, that the attributes SECTR1 and SECTR2 must not be populated for lights that are visible all-round (omni-directional).

 

<Back to Index>

 

EB54 - UOC Clause 12.14.1 AIS equipped aids to navigation
(Also included as Portrayal Bulletin 10 - Portrayal of virtual AIS aids to navigation)

This combined Encoding Bulletin (EB) and Presentation Bulletin (PB) provides guidance on the correct encoding and portrayal of Virtual AIS Aids to Navigation.

Clause 12.14.1 of the Use of the Object Catalogue for ENC (S-57 Appendix B1, Annex A) provides guidance for the encoding of Automatic Identification System (AIS) broadcast messages used as aids to navigation, including a statement that it is currently not possible to encode Virtual AIS Aids to Navigation in ENC.

Given that AIS technology is increasingly being used for Aids to Navigation purposes, the IHO Hydrographic Services and Standards Committee (HSSC) considers that there is now a requirement to implement an interim solution to enable the encoding of Virtual AIS Aids to Navigation in ENC. Accordingly, the HSSC has approved the use of the NEWOBJ object class, introduced through S-57 Edition 3.1, Supplement No.1, to enable the encoding of Virtual AIS Aids to Navigation in ENC.


Encoders are advised, therefore, that in order to encode Virtual AIS Aids to Navigation information in ENC, the following encoding specification must be applied:

If it is required to encode a Virtual AIS Aid to Navigation, it must be done using the object class NEWOBJ;

Geo object: New object (NEWOBJ) (P)
Attributes: CLSNAM CLFDEF DATEND DATSTA INFORM NINFOM NOBJNM
OBJNAM TXTDSC NTXTDS SORIND SORDAT SYMINS
The following table shows the combinations for the mandatory attributes CLSDEF, CLSNAM and SYMINS that must be populated, according to the purpose of the Virtual AIS Aid to Navigation and the corresponding portrayal for each encoding:

 

Purpose of
Virtual Aid

CLSDEF

CLSNAM

SYMINS

PORTRAYAL

North Cardinal

A Virtual object which indicates navigable water lies northwards

Virtual AtoN, North Cardinal

SY(BRTHNO01);SY(BCNCAR01);TX('V-AIS',3,2,2,'15110',2,0,CHMGD,11)

East Cardinal

A Virtual object which indicates navigable water lies eastwards

Virtual AtoN, East Cardinal

SY(BRTHNO01);SY(BCNCAR02);TX('V-AIS',3,2,2,'15110',2,0,CHMGD,11)

South Cardinal

A Virtual object which indicates navigable water lies southwards

Virtual AtoN, South Cardinal

SY(BRTHNO01);SY(BCNCAR03);TX('V-AIS',3,2,2,'15110',2,0,CHMGD,11)

West Cardinal

A Virtual object which indicates navigable water lies westwards

Virtual AtoN, West Cardinal

SY(BRTHNO01);SY(BCNCAR04);TX('V-AIS',3,2,2,'15110',2,0,CHMGD,11)

Port lateral
(IALA A)

A Virtual object marking the port side of a channel

Virtual AtoN, Port Lateral

SY(BRTHNO01);SY(BOYLAT24);TX('V-AIS',3,2,2,'15110',2,0,CHMGD,11)

Starboard Lateral
(IALA A)

A Virtual object marking the starboard side of a channel

Virtual AtoN, Starboard Lateral

SY(BRTHNO01);SY(BOYLAT13);TX('V-AIS',3,2,2,'15110',2,0,CHMGD,11)

Port lateral
(IALA B)

A Virtual object marking the port side of a channel

Virtual AtoN, Port Lateral

SY(BRTHNO01);SY(BOYLAT23);TX('V-AIS',3,2,2,'15110',2,0,CHMGD,11)

Starboard Lateral
(IALA B)

A Virtual object marking the starboard side of a channel

Virtual AtoN, Starboard Lateral

SY(BRTHNO01);SY(BOYLAT14);TX('V-AIS',3,2,2,'15110',2,0,CHMGD,11)

Isolated Danger

A Virtual object marking an isolated danger

Virtual AtoN, Isolated Danger

SY(BRTHNO01);SY(BCNISD21);TX('V-AIS',3,2,2,'15110',2,0,CHMGD,11)

Safe Water

A Virtual object marking safe water

Virtual AtoN, Safe Water

SY(BRTHNO01);SY(BOYSAW12);TX('V-AIS',3,2,2,'15110',2,0,CHMGD,11)

Special Purpose

A Virtual object used to mark an area or feature referred to in nautical documents

Virtual AtoN, Special Purpose

SY(BRTHNO01);SY(BOYSPP11);TX('V-AIS',3,2,2,'15110',2,0,CHMGD,11)

Emergency Wreck Marking

A Virtual object marking a wreck

Virtual AtoN, Wreck Marking

SY(BRTHNO01);SY(BOYSPP11);TX('V-AIS',3,2,2,'15110',2,0,CHMGD,11)


For reasons of backward compatibility the mandatory attribute INFORM must contain the values of CLSNAM and CLSDEF for the object.
Where known the attribute OBJNAM should be populated with the MMSI number of the Virtual AIS Aid to Navigation, in addition to its individual name, e.g. Nab Rock, MMSI 995031014.

Virtual AIS Aids to Navigation should only be encoded where it is known that the Virtual Aid is intended to be permanent, or deployed for a specified fixed period. Where it is known that a Virtual AIS Aid to Navigation is moved or withdrawn on a regular basis and/or at short notice, such that implementing these changes through the application of ENC Updates is impractical, the Virtual Aid should not be encoded.

A new validation check for this New Object will be included in the next version of S-58. Until validation tools have implemented the new version, encoders must consider appropriate validation measures when using the New Object as the correct encoding of the SYMINS attribute is critical to ensuring a correct display in ECDIS.

 

Portrayal Guidance for the NEWOBJ object class is provided in S-52 Edition 6, Section 8.3.3.11. The portrayal of virtual AIS Aids to Navigation in ECDIS is accomplished by encoded symbolization through the population of the SYMINS attribute as specified in the table above. The correct ECDIS display for each of the 12 NEWOBJ encodings is the symbol shown in the far right column. Each is a superimposition of the magenta circle from the berth number symbol (BRTHNO01) by a simplified symbol for a fixed aid as indicated. The symbols must be drawn in the listed order. That is, the magenta circle must be drawn first and the mark drawn over it. The magenta text, “V-AIS” must also be displayed. Note that OBJNAM, if encoded, will not be displayed and must be obtained through a pick report.

<Back to Index>

 

S-57 Maintenance Document 8

1. MD8 revision to Correction 1.Co.10

Correction 1.Co.10 was added to MD1 in November 1997. The correction added two extra items to table A.7. It also appears to have somehow changed the truncated escape sequence for lexical level 2 in the last line from “”%/A” to “%/@”. This correction should be corrected – i.e. the last line should read Lexical level 2 - “%/A”
 

 

 

S-57 Maintenance Document 8

1. MD8 revision to Correction 1.Co.10

Correction 1.Co.10 was added to MD1 in November 1997. The correction added two extra items to table A.7. It also appears to have somehow changed the truncated escape sequence for lexical level 2 in the last line from “”%/A” to “%/@”. This correction should be corrected – i.e. the last line should read Lexical level 2 - “%/A”
 

 

<Back to Index>

Updated: May 2013