INTERNATIONAL HYDROGRAPHIC ORGANIZATION

MARINE PROTECTED AREA PRODUCT SPECIFICATION

IHO Publication S-122

Appendix A
Data Classification and Encoding Guide

Edition 1.0.0 – January 2019

Published by the
International Hydrographic Organization
4b quai Antoine 1er
Principauté de Monaco
Tel: (377) 93.10.81.00
Fax: (377) 93.10.81.40
E-mail: [email protected]
Web: www.iho.int
 ii Data Classification and Encoding Guide

© Copyright International Hydrographic Organization 2019

This work is copyright. Apart from any use permitted in accordance with the Berne
Convention for the Protection of Literary and Artistic Works (1886), and except in
the circumstances described below, no part may be translated, reproduced by any
process, adapted, communicated or commercially exploited without prior written
permission from the International Hydrographic Organization Secretariat (IHO
Secretariat). Copyright in some of the material in this publication may be owned
by another party and permission for the translation and/or reproduction of that
material must be obtained from the owner.
This document or partial material from this document may be translated,
reproduced or distributed for general information, on no more than a cost recovery
basis. Copies may not be sold or distributed for profit or gain without prior written
agreement of the IHO Secretariat acting for the IHO and any other copyright
holders.
In the event that this document or partial material from this document is
reproduced, translated or distributed under the terms described above, the
following statements are to be included:

“Material from IHO publication [reference to extract: Title, Edition] is

reproduced with the permission of the International Hydrographic
Organization Secretariat (IHO Secretariat) (Permission No ……./…) acting for
the International Hydrographic Organization (IHO), which does not accept
responsibility for the correctness of the material as reproduced: in case of
doubt, the IHO’s authentic text shall prevail. The incorporation of material
sourced from IHO shall not be construed as constituting an endorsement by
IHO of this product.”

“This [document/publication] is a translation of IHO [document/publication]

[name]. The IHO has not checked this translation and therefore takes no
responsibility for its accuracy. In case of doubt the source version of [name] in
[language] should be consulted.”
The IHO Logo or other identifiers shall not be used in any derived product
without prior written permission from the IHO Secretariat.

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide iii

Document Control

Versio Version Type Date Approved Signed Off Role

n By By
0.0.0 Editing Committee Draft 26.06.2012 SNPWG SNPWG Chair
0.0.1 Editing Draft 2014 SNPWG SNPWG Chair
0.3.4 New NPUBS text content 2014
model,
0.3.8 Again, text content model 23.12.2014 SNPWG Chair
0.3.9 Editorial 21.01.2015 SNPWG Chair
0.4.0 Content restructure; 03.02.2014 SNPWG Chair
some sub-clauses added;
Revision of tables uses
from S-101
0.5.0 Certain empty 13.03.2015 SNPWG Chair
paragraphs have been
filled with text
Additional comments
placed elsewhere
0.6.0 Remove of context 30.10.2015 NIPWG Chair
features
Added WRECKS and
OBSTRN
(out for WG review)
0.7.0 Incorporation of the 30.12.2015 NIPWG Chair
group’s view
0.7.1 Consideration of 01.02.2016 NIPWG Chair
feedback
0.7.2 Amendments according 28.08.2016 NIPWG Chair,
to comments made at
NIPWG2
0.7.3 Further clarifications 01.09.2016 NIPWG Chair
0.7.4 Out for NIPW review 01.01.2017 NIPWG Chair
0.7.5 Collected comments ??.03.17 NIPWG Chair
0.7.6 Comments incorporated 31.03.17 EM
and revisions for March
RMM
2017 package
1.0.0 Harmonization with S-123 04.05.2017 RMM
Draft 2
1.0.0 Updates arising from 27-07-2017 RMM
Draft 3 NIPWG review
1.0.0 Release Candidate 1 21-08-2017 RMM
RC1

S-122 Appendix A January 2019 Edition 1.0.0

 iv Data Classification and Encoding Guide

Page intentionally left blank

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide v

TABLE OF CONTENTS
1 OVERVIEW ............................................................................................................................................... 1
1.1 PREFACE ................................................................................................................................................... 1
1.2 S-122 APPENDIX A - DATA CLASSIFICATION AND ENCODING GUIDE – METADATA .................................................. 1
1.3 TERMS AND DEFINITIONS .............................................................................................................................. 2
1.4 ABBREVIATIONS.......................................................................................................................................... 4
1.5 USE OF LANGUAGE ...................................................................................................................................... 4
1.6 MAINTENANCE........................................................................................................................................... 5
2 GENERAL .................................................................................................................................................. 6
2.1 INTRODUCTION .......................................................................................................................................... 6
2.2 DESCRIPTIVE CHARACTERISTICS ...................................................................................................................... 6
2.2.1 Feature .............................................................................................................................................. 6
2.2.1.1 Geographic feature class .......................................................................................................................... 6
2.2.1.2 Meta feature class .................................................................................................................................... 6
2.2.1.3 Charted background feature .................................................................................................................... 6
2.2.2 Information type................................................................................................................................ 6
2.3 SPATIAL CHARACTERISTICS ............................................................................................................................ 7
2.3.1 Spatial primitives ............................................................................................................................... 7
2.3.2 Capture density guideline .................................................................................................................. 7
2.4 ATTRIBUTES ............................................................................................................................................... 7
2.4.1 Simple attribute types ....................................................................................................................... 7
2.4.2 Mandatory attributes ........................................................................................................................ 8
2.4.3 Conditional attributes........................................................................................................................ 9
2.4.4 Missing attribute values .................................................................................................................... 9
2.4.5 Multiplicity......................................................................................................................................... 9
2.4.6 Spatial attribute types ....................................................................................................................... 9
2.4.6.1 Quality of spatial attributes ...................................................................................................................... 9
2.4.7 Portrayal feature attributes ............................................................................................................ 10
2.4.8 Textual information ......................................................................................................................... 10
2.4.8.1 Specialized information types for common kinds of textual information .............................................. 11
2.4.8.2 Textual information attributes ............................................................................................................... 11
2.4.8.3 Languages ............................................................................................................................................... 11
2.4.8.4 Minimal use of generalized text attributes ............................................................................................ 11
2.4.8.5 Short textual information ....................................................................................................................... 11
2.4.8.6 Complex or lengthy textual information ................................................................................................ 12
2.4.9 Attributes referencing external files ................................................................................................ 12
2.4.9.1 Predefined derived types ....................................................................................................................... 12
2.4.9.2 Reference to textual files ........................................................................................................................ 13
2.4.9.3 Reference to external sources ................................................................................................................ 13
2.4.9.4 Reference to graphics ............................................................................................................................. 13
2.4.10 Dates ........................................................................................................................................... 13
2.4.10.1 Complete Dates (Informative) ................................................................................................................ 14
2.4.10.2 Truncated Dates (Informative) ............................................................................................................... 14
2.4.10.3 Start and end of ranges .......................................................................................................................... 14
2.4.10.4 Schedules................................................................................................................................................ 15
2.4.11 Times ........................................................................................................................................... 16
2.4.12 Combination of date schedules and times .................................................................................. 16
2.4.13 Graphic information .................................................................................................................... 16
2.4.13.1 Bearing information................................................................................................................................ 16
2.5 ASSOCIATIONS ......................................................................................................................................... 16
2.5.1 Introduction ..................................................................................................................................... 16
2.5.2 Association names ........................................................................................................................... 17
2.5.3 Association roles .............................................................................................................................. 17
2.5.4 Association classes .......................................................................................................................... 17
2.5.4.1 Permission Type ..................................................................................................................................... 17
2.5.4.2 Inclusion Type ......................................................................................................................................... 18
2.5.5 Use of various associations ............................................................................................................. 19
2.5.5.1 General ................................................................................................................................................... 19

S-122 Appendix A January 2019 Edition 1.0.0

 vi Data Classification and Encoding Guide

2.5.5.2 Generic association for uncategorized additional information .............................................................. 19

2.5.5.3 Associations to Restrictions, Recommendation, Regulations and Nautical Information ........................ 19
2.5.5.4 Conventional Association ....................................................................................................................... 19
2.5.6 Where to Encode Associations ........................................................................................................ 19
2.6 DATASETS ............................................................................................................................................... 19
2.6.1 Types of Datasets ............................................................................................................................ 19
2.6.2 Overlay data sets ............................................................................................................................. 20
2.6.3 Data coverage ................................................................................................................................. 20
2.6.4 Discovery metadata ........................................................................................................................ 20
2.6.5 Dataset header metadata ............................................................................................................... 21
2.6.6 Dataset units ................................................................................................................................... 21
2.6.7 Dataset Coverage ............................................................................................................................ 21
2.6.8 Dataset Feature Object Identifiers .................................................................................................. 21
2.6.9 180° Meridian of Longitude ............................................................................................................. 21
2.7 GEOGRAPHIC NAMES ................................................................................................................................. 21
2.7.1 Feature names ................................................................................................................................. 21
2.7.2 Text placement ................................................................................................................................ 22
2.8 SCALE POLICY ........................................................................................................................................... 22
2.9 MASKING ................................................................................................................................................ 23
2.9.1 Surface features crossing MPA cell boundaries ............................................................................... 23
2.9.2 “Linear” surface features................................................................................................................. 24
3 DESCRIPTION OF TABLE FORMAT FOR FEATURE AND INFORMATION TYPES .......................................... 24
4 METADATA FEATURES ........................................................................................................................... 26
4.1 INTRODUCTION ........................................................................................................................................ 26
4.2 MANDATORY META FEATURES ..................................................................................................................... 26
4.3 DATA COVERAGE META FEATURE.................................................................................................................. 27
4.3.1 Coverage.......................................................................................................................................... 27
4.4 QUALITY OF NON-BATHYMETRIC DATA .......................................................................................................... 28
4.4.1 Quality of positions, distances, or directions ................................................................................... 29
4.4.2 Source as a quality indicator ........................................................................................................... 29
5 GEO FEATURES ....................................................................................................................................... 30
5.1 FEATURETYPE .......................................................................................................................................... 30
5.1.1 Geographic features in general ....................................................................................................... 32
5.1.2 Restrictions, regulations, etc., related to geographic features ....................................................... 32
5.1.3 Restrictions, regulations, etc., that depend on vessel characteristics ............................................. 32
5.2 MARINE PROTECTED AREA ......................................................................................................................... 32
5.2.1 Protected area categories ............................................................................................................... 34
5.2.2 Restrictions and regulations for protected areas ............................................................................ 35
5.3 VESSEL TRAFFIC SERVICE AREA .................................................................................................................... 35
5.3.1 Vessel traffic services ...................................................................................................................... 36
5.4 RESTRICTED AREA NAVIGATIONAL................................................................................................................ 36
5.4.1 Restricted areas in general .............................................................................................................. 38
5.4.1.1 Nature reserves (see S-4 – B-437.3) ....................................................................................................... 38
5.4.1.2 Speed limits (see S-4 – B-430.2) ............................................................................................................. 38
5.4.1.3 Areas to be avoided (see S-4 – B-435.7) ................................................................................................. 38
5.4.1.4 Environmentally Sensitive Sea Areas (see S-4 – B-437) .......................................................................... 38
5.5 RESTRICTED AREA REGULATORY .................................................................................................................. 38
5.5.1 Restricted areas in general .............................................................................................................. 40
5.5.1.1 Nature reserves (see S-4 – B-437.3) ....................................................................................................... 41
5.5.1.2 Speed limits (see S-4 – B-430.2) ............................................................................................................. 41
5.5.1.3 Anchoring restricted (see S-4 – B-431.4) ................................................................................................ 41
5.5.1.4 Environmentally Sensitive Sea Areas (see S-4 – B-437) .......................................................................... 41
6 CARTOGRAPHIC FEATURES .................................................................................................................... 41
6.1 TEXT PLACEMENT ..................................................................................................................................... 41
6.1.1 Text Placement ................................................................................................................................ 42

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide vii

7 INFORMATION TYPES............................................................................................................................. 42
7.1 INFORMATIONTYPE ................................................................................................................................... 43
7.1.1 Information types in general ........................................................................................................... 44
7.2 ABSTRACTRXN ......................................................................................................................................... 44
7.2.1 Abstract supertype for information from textual sources ............................................................... 47
7.3 AUTHORITY ............................................................................................................................................. 48
7.4 SHIP REPORT ........................................................................................................................................... 50
7.5 CONTACT DETAILS .................................................................................................................................... 52
7.5.1 Use of complex attributes ............................................................................................................... 55
7.5.2 Encoding additional or special instructions for communication...................................................... 55
7.5.2.1 Special communication preferences ...................................................................................................... 55
7.5.2.2 Special schedules or supplementary information about schedules ....................................................... 55
7.6 SERVICE HOURS ....................................................................................................................................... 55
7.6.1 Seasonal variations in service hours ................................................................................................ 56
7.7 NON STANDARD WORKING DAY.................................................................................................................. 57
7.7.1 Exceptions to usual workdays ......................................................................................................... 57
7.8 APPLICABILITY .......................................................................................................................................... 58
7.9 REGULATIONS .......................................................................................................................................... 62
7.9.1 Regulations information type .......................................................................................................... 63
7.10 RESTRICTIONS .......................................................................................................................................... 63
7.10.1 Restrictions information type ...................................................................................................... 64
7.11 RECOMMENDATIONS ................................................................................................................................. 64
7.11.1 Recommendations information type .......................................................................................... 65
7.12 NAUTICAL INFORMATION ........................................................................................................................... 65
7.12.1 General nautical information ...................................................................................................... 66
7.13 SPATIAL QUALITY...................................................................................................................................... 66
7.13.1 Spatial quality ............................................................................................................................. 67
7.14 SPATIAL QUALITY POINTS ........................................................................................................................... 67
7.14.1 Spatial quality for points ............................................................................................................. 68
8 ASSOCIATION CLASSES ........................................................................................................................... 68
8.1 PERMISSION TYPE ..................................................................................................................................... 68
8.2 INCLUSION TYPE ....................................................................................................................................... 69
9 GEO FEATURE ATTRIBUTE AND ENUMERATE DESCRIPTIONS ................................................................. 69
10 ASSOCIATIONS ....................................................................................................................................... 69
10.1 ASSOCIATION NAMES ................................................................................................................................ 69
10.2 ASSOCIATION ROLES ................................................................................................................................. 69
11 META FEATURE AND SPATIAL ATTRIBUTE AND ENUMERATE DESCRIPTIONS ......................................... 70
12 COMPLEX ATTRIBUTES ........................................................................................................................... 70
13 ECDIS SYSTEM (PORTRAYAL) ATTRIBUTES .............................................................................................. 70
13.1 ECDIS SYSTEM (PORTRAYAL) ATTRIBUTES DERIVED FROM S-101 (VERSION 1.0).................................................. 70
14 UPDATING (SEE S-4 – B-600) .................................................................................................................. 70

S-122 Appendix A January 2019 Edition 1.0.0

 viii Data Classification and Encoding Guide

Page intentionally left blank

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 1

Overview
Preface
The “Data Classification and Encoding Guide” has been developed to provide consistent,
standardized instructions for encoding S-100 compliant Marine Protected Area (MPA) (S-122)
data.
The purpose of the Data Classification and Encoding Guide is to facilitate S-122 encoding to
meet IHO standards for the proper display of Marine Protected Area information in an ECDIS
and other electronic charting displays. This document describes how to encode information
that the modeller considers relevant to an MPA. The content of an MPA product is at the
discretion of the producing authority provided that the conventions described within this
document are followed. A “producing authority” is a Hydrographic Office (HO) or other
organization authorized by a government, to produce definitive nautical information.
The entire S-100 Universal Hydrographic Data Model, including the S-122 MPA Product
Specification, is available at the following web site, http://www.iho.int.
S-122 Appendix A - Data Classification and Encoding Guide – Metadata
Note: This information uniquely identifies this Data Classification and Encoding Guide to the
Product Specification and provides information about its creation and maintenance.

Metadata Content
Title: The International Hydrographic Organization Marine Protected
Area Product Specification, Data Classification and Encoding
Guide
Version: 1.0.0
Date: January 2019
Language: English
Classification: Unclassified
Contact: International Hydrographic Organization
4 Quai Antione 1er
B.P. 445
MC 98011 MONACO CEDEX
Telephone: +377 93 10 81 00
Fax: +377 93 10 81 40
URL: www.iho.int
Identifier: S-122 Appendix A Data Classification and Encoding Guide
Maintenance: Changes to S-122 Appendix A; Data Classification and Encoding
Guide are coordinated by the IHO Nautical Information Provision
Working Group (NIPWG) and must be made available via the IHO
web site.
Table 0-1 MPA product specification metadata

S-122 Appendix A January 2019 Edition 1.0.0

 2 Data Classification and Encoding Guide

Terms and definitions

This list is identical with the list in the main body of this product specification.

Term Definition
aggregation special form of association that specifies a whole-part
relationship between the aggregate (whole) and a component
(see composition)
application manipulation and processing of data in support of user
requirements (ISO 19101)
application schema conceptual schema for data required by one or more
applications (ISO 19101)
association semantic relationship between two or more classifiers that
specifies connections among their instances
NOTE: A binary association is an association among exactly two
classifiers (including the possibility of an association from a
classifier to itself)
attribute named property of an entity
NOTE: Describes the geometrical, topological, thematic, or other
characteristic of an entity
boundary set that represents the limit of an entity (ISO 19107)
composition special form of association that specifies a “strong
aggregation”. In a composition association, if a container object
is deleted then all of the objects it contains are deleted as well.
conceptual model model that defines concepts of a universe of discourse (ISO
19101)
conceptual schema formal description of a conceptual model (ISO 19101)
coverage feature that acts as a function to return values from its range for
any direct position within its spatial, temporal or spatiotemporal
domain (ISO 19123)
EXAMPLE Raster image, polygon overlay, digital elevation
matrix.
curve 1-dimensional geometric primitive, representing the continuous
image of a line
NOTE: The boundary of a curve is the set of points at either
end of the curve. If the curve is a cycle, the two ends are
identical, and the curve (if topologically closed) is considered to
not have a boundary. The first point is called the start point, and
the last point is the end point. Connectivity of the curve is
guaranteed by the “continuous image of a line”
data product dataset or dataset series that conforms to a data product
specification
data product specification detailed description of a dataset or dataset series together with
additional information that will enable it to be created, supplied to
and used by another party
NOTE: A data product specification provides a description of the
universe of discourse and a specification for mapping the
universe of discourse to a dataset. It may be used for production,
sales, end-use or other purpose.
dataset identifiable collection of data (ISO 19115)

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 3

NOTE: A dataset may be a smaller grouping of data which,

though limited by some constraint such as spatial extent or
feature type, is located physically within a larger dataset.
Theoretically, a dataset may be as small as a single feature
contained within a larger dataset. A hardcopy map or chart may
be considered a dataset.
dataset series collection of datasets sharing the same product specification
(ISO 19115)
domain well-defined set (ISO/TS 19103)
NOTE: Well-defined means that the definition is both necessary
and sufficient, as everything that satisfies the definition is in the
set and everything that does not satisfy the definition is
necessarily outside the set.
end point last point of a curve (ISO 19107)
enumeration a fixed list which contains valid identifiers of named literal values.
Attributes of an enumerated type may only take values from this
list.
feature abstraction of real world phenomena (ISO 19101)
NOTE: A feature may occur as a type or an instance. Feature
type or feature instance shall be used when only one is meant.
EXAMPLE: The feature instance named “Turning Torso Tower”
may be classified with other phenomena into a feature type
“tower”.
feature association relationship that links instances of one feature type with
instances of the same or a different feature type (ISO19110)
NOTE 1; A feature association may occur as a type or an
instance. Feature association type or feature association instance
is used when only one is meant.
NOTE 2: Feature associations include aggregation of features.
feature attribute characteristic of a feature (ISO 19101)
NOTE 1: A feature attribute may occur as a type or an instance.
Feature attribute type or feature attribute instance is used when
only one is meant.
NOTE 2: A feature attribute type has a name, a data type and a
domain associated to it. A feature attribute for a feature instance
has an attribute value taken from the domain.
geographic data data with implicit or explicit reference to a location relative to the
Earth (ISO 19109)
NOTE: Geographic information is also used as a term for
information concerning phenomena implicitly or explicitly
associated with a location relative to the Earth.
geometric primitive geometric object representing a single, connected, homogeneous
element of geometry
NOTE: Geometric primitives are non-decomposed objects that
present information about geometric configuration. They include
points, curves, surface
maximum display scale the largest value of the ratio of the linear dimensions of features
of a dataset presented in the display and the actual dimensions
of the features represented (largest scale) of the scale range of
the dataset

S-122 Appendix A January 2019 Edition 1.0.0

 4 Data Classification and Encoding Guide

metadata data about data (ISO 19115)

minimum display scale the smallest value of the ratio of the linear dimensions of features
of a dataset presented in the display and the actual dimensions
of the features represented (smallest scale) of the scale range of
the dataset
model abstraction of some aspects of reality (ISO 19109)
point 0-dimensional geometric primitive, representing a position
NOTE: The boundary of a point is the empty set
portrayal presentation of information to humans (ISO 19117)
quality totality of characteristics of a product that bear on its ability to
satisfy stated and implied needs (ISO 19101)
set unordered collection of related items (objects or values) with no
repetition (ISO 19107)
start point first point of a curve (ISO 19107)
surface connected 2-dimensional geometric primitive, representing the
continuous image of a region of a plane
NOTE: The boundary of a surface is the set of oriented, closed
curves that delineate the limits of the surface
universe of discourse view of the real or hypothetical world that includes everything of
interest (ISO 19101)
Table 0-2 List of terms and definitions

Abbreviations
Abbreviation Description
DCEG Data Classification and Encoding Guide
ECDIS Electronic Chart Display and Information System
ENC Electronic Navigational Chart
GML Geography Markup Language
HO Hydrographic Office
IHO International Hydrographic Organization
IMO International Maritime Organization
ISO International Organization for Standardization
MPA Marine Protected Area
RENC Regional ENC co-ordinating centre
UML Unified Modelling Language
URL Universal Resource Locator
XML eXtensible Markup Language
Table 0-3 List of abbreviations

Use of language
Within this document:
“Must” indicates a mandatory requirement;
“Should” indicates an optional requirement, that is the recommended process to be
followed, but is not mandatory;

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 5

“May” means “allowed to” or “could possibly”, and is not mandatory, or recommended.
Maintenance
Changes to the Data Classification and Encoding Guide must occur in accordance with the S-
122 MPA Product Specification clause 6.1.8

S-122 Appendix A January 2019 Edition 1.0.0

 6 Data Classification and Encoding Guide

General
Introduction
This S-122 Data Classification and Encoding Guide (DCEG) contains rules and guidance for
converting data describing the real world into data products that conform to the S-122
specification.
The S-122 specification contains an application schema (UML model) describing the
conceptual domain model in terms of classes and relationships, and a Feature Catalogue (see
S-122 Annex B) that specifies the data model, i.e., specifies the data model types and
associations corresponding to the various classes and relationships in the application schema.
To simplify the DCEG text, the various data model types will be provided without the suffixes
“class”, “type” or “instance”; e.g. the term “feature” should be understood as “feature class” or
“feature type” or “feature instance” as best fits the immediate context in which it is used (and
where there might be confusion, it is written out in full as feature class/type/instance).The
model defines real world entities as a combination of descriptive and spatial characteristics (S-
122 MPA Product Specification clause 4.4).
This section of the DCEG contains general information needed to understand the encoding
rules and describes fundamental common rules and constraints. It also describes datasets and
metadata. The data model object types used within S-122 and their encoding rules and
guidelines are defined in detail in subsequent sections of this document.
Within this document the features, information types, associations and attributes appear in
bold text.
Descriptive characteristics
Feature
A feature contains descriptive attributes that characterize real world entities.
The word ‘feature’ as used in the ISO 191xx series and in S-100 based product specifications
has two distinct but related senses – ‘feature type’ and ‘feature instance’. A feature instance
is a single occurrence of the feature and is represented as an object in a dataset.
The location of a feature instance on the Earth’s surface is indicated by a relationship to one
or more spatial primitive instances. A feature instance may exist without referencing a spatial
primitive instance.
Geographic feature class
Geographic (Geo) feature types carry the descriptive characteristics of a real world entity
which is provided by a spatial primitive instance.
Meta feature class
Meta feature type contains information about other features.
Charted background feature
The MPA product would mostly be visualized as an overlay of an ENC or other GIS
applications. Consequently, all necessary descriptive and spatial characteristics to provide a
charted background should be provided by the underlying application.
Information type
An information type has no geometry and therefore is not associated to any spatial primitives
to indicate its location.
An information type may have attributes and can be associated with features or other
information types in order to carry information particular to these associated features or
information types.

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 7

Spatial characteristics
Spatial primitives
The allowable spatial primitive for each feature is defined in the Feature Catalogue. Allowable
spatial primitives are point, curve and surface.
Within this document, allowable spatial primitives are included in the description of each
feature. For easy reference, Table 0-1 below summarises the allowable spatial primitives for
each feature. In the table, abbreviations are as follows: point (P), curve (C) and surface (S).
Feature P C S
Marine Protected Area X X
Restricted Area Navigational X
Restricted Area Regulatory X
Traffic Control Service X
Table 0-1 Features permitted for MPA and their spatial primitives

Capture density guideline

The MPA capture density will follow the recommendation of the S-101 (ENC) DCEG, that
states curves and surface boundaries should not be encoded at a point density greater than
0.3 mm at permitted display scale.
A curve consists of one or more curve segments. Each curve segment is defined as a
loxodromic line on WGS84, or as an arc or circle. Long lines may need to have additional
coordinates inserted to cater for the effects of projection change.
The presentation of line styles may be affected by curve length. Therefore, the encoder must
be aware that splitting a curve into numerous small curves may result in poor symbolization.
Attributes
Attributes may be simple type or complex type. Complex (C) attributes are aggregates of other
attributes that can be simple type or complex type attributes. Simple (S) attributes are
assigned to one of the types collected at clause 0.
The binding of attributes to a feature, the binding of attributes to attributes to construct complex
attributes, and attribute multiplicity are all defined in the Feature Catalogue.
Within this document, the allowable attributes are included in the description of each feature,
as well as the allowable values for enumeration type attributes.
Simple attribute types
Each simple attribute (S) is assigned to one of attribute types in Table 0-2 (in alphabetic order):
Abbre- Attribute Description
viation type
BO Boolean A value representing binary logic. The value can be either True or False. The
default state for Boolean type attributes (i.e. where the attribute is not
populated for the feature) is False.
CL Code List A type of flexible enumeration (see “EN” below). A code list type is a list of
literals which may be extended only in conformance with specified rules.
Attributes of a code list type may take values from the list or other values which
are defined according to the rules. The rules should be part of the specification
of the individual codelist type. A code list could either be closed (fixed) or open
(extensible).
A code list type has the following properties:
1. A description of the code list type,
2. The URI where the list could be found, and
3. An encoding instruction.

S-122 Appendix A January 2019 Edition 1.0.0

 8 Data Classification and Encoding Guide

DA Date A date provides values for year, month and day according to the Gregorian
Calendar.
Example: 19980918 (YYYYMMDD)
DT Date and A DateTime is a combination of a date and a time type.
Time
Example: 19850412T101530 (YYYYMMDDThhmmss)
EN Enumer- A fixed list of valid identifiers of named literal values. Attributes of an
ation enumerated type may only take values from this list.
IN Integer A signed integer number. The representation of an integer is encapsulation
and usage dependent.
Integer attribute values must not be padded by non-significant zeroes. For
example, for a number of 19, the value populated for the attribute must be 19
and not 019.
Examples: 29, -65547
RE Real A signed real (floating point) number consisting of a mantissa and an
exponent. The representation of a real is encapsulation and usage
dependent.
Real attribute values must not be padded by non-significant zeroes. For
example, for a signal period of 2.5 seconds, the value populated for the
attribute signal period must be 2.5 and not 02.50.
Examples: 23.501, -0.0001234, -23.0, 3.141296
TD Trun- One or more significant components of the modelling date are omitted.
cated
Example: – – – –02– – (Year and date not encoded)
Date
The exact format depends on the encoding.
A GML dataset would use a GML built-in type and encode it as <gMonth>--
02<gMonth>.
An 8211 data format based dataset would truncated encode the date as – – –
–02– –.
TE Free text A CharacterString is an arbitrary-length sequence of characters including
accents and special characters from a repertoire of one of the adopted
character sets.
TI Time A time is given by an hour, minute and second. Time zone according to UTC
is optional. Character encoding of a time is a string that follows the local time
Example: 183059 or 183059+0100 or 183059Z
Table 0-2 Simple attribute types
Mandatory attributes
Some attributes are mandatory and must be populated for a given feature. There are some
reasons why attribute values may be considered mandatory:
They are fundamental to the definition of a marine protected area;
They are required to support the correct portrayal of a feature instance;
Certain features make no logical sense without specific attributes;
Some attributes are required for safety of navigation.
Within this document, mandatory attributes are those with a multiplicity of 1,1 or 1,n (n>1) or
1,*. The attribute multiplicity is identified in the description of each feature class.
For easy reference, the Table 0-3 summarises the mandatory attributes for each feature.
Feature Mandatory Attributes
Marine Protected Area categoryOfMarineProtectedArea jurisdiction

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 9

Feature Mandatory Attributes

Restricted Area Navigational none
Restricted Area Regulatory none
Vessel Traffic Service Area categoryOfVesselTrafficService
Table 0-3 Mandatory attributes for MPA feature classes
Conditional attributes
The MPA feature classes or information types do not contain conditional attributes.
Complex attributes which are assigned to MPA feature classes or information types have at
least one sub-attribute which is mandatory (or conditionally mandatory). Mandatory sub-
attributes of complex attributes have not been included in the Table 0-3. Where the sub-
attribute of a complex attribute is conditional, this is indicated in the Remarks section for the
relevant feature class entries in chapter0.
Missing attribute values
Where a value of a mandatory attribute is not known, the attribute must be populated with an
empty (null) value.
Where the value of a non-mandatory attribute is not known, the attribute must not be used.
Multiplicity
In order to control the number of allowed attribute values or sub-attribute instances within a
complex attribute, S-100 uses the concept of multiplicity. This defines lower and upper limits
for the number of values, whether the order of the instances is significant and if an attribute is
mandatory. Common examples are shown in theTable 0-4:
Format: MinOccurs, MaxOccurs (a * indicates that infinite instances are possible, the
term(ordered) indicates that the order of the provided instances is significant)
Multiplicity Explanation
0,1 or 0..1 An instance is not required; if provided there must only be one instance.
1,1 or 1..1 An instance is required and there must only be one instance.
0,* An instance is not required and there can be an infinite number of
or 0..1 instances.
1,* or 1..* An instance is required and there can be an infinite number of instances.
1,* (ordered) An instance is required and there can be an infinite number of instances,
the order of which is significant.
2,2 or 2..2 Two instances are required and there must be no more than two.
Table 0-4 Multiplicity of attributes
Spatial attribute types
Spatial attribute types must contain a referenced geometry and may be associated with spatial
quality attributes. Each spatial attribute instance must be referenced by a feature instance or
another spatial attribute instance.
Quality of spatial attributes
The quality of spatial attributes in S-122 is described in a Quality of Non-Bathymetric Data
meta-feature. This meta-feature defines areas within which uniform assessment exists for the
quality. It is described in detail later in this document.
If the spatial quality attributes for an individual instance of a spatial primitive differ from the
quality indicated in the overlying Quality of Non-Bathymetric Data meta-feature, the quality
attributes for that instance are carried in an information class called Spatial Quality. Only
points and curves can be associated with Spatial Quality. S-122 does not use multi-points.
Currently, no use case for associating surfaces with spatial quality attributes is known,
therefore this is prohibited. Vertical uncertainty is prohibited for curves as this dimension is
not supported by curves.

S-122 Appendix A January 2019 Edition 1.0.0

 10 Data Classification and Encoding Guide

Note: S-122 does not make use of the S-101 Quality of Bathymetric Data meta- feature since
depth range uncertainties are not needed. The Quality of Non-Bathymetric Data meta-
feature has all the quality attributes needed by S-122.

Figure 1 Spatial quality information

Portrayal feature attributes
MPAs will be used within ECDIS where ENC data is displayed based on the rules defined
within the S-101 Portrayal Catalogue. While most ECDIS portrayal is based on attributes
describing the instance of a particular feature in the real world, certain feature attributes are
used in portrayal rules to provide additional functionality in the ECDIS. Table 0-5 provides a
list of attributes which have been adopted from the S-101 (ENC) product specification and
which have specific influence on the MPA portrayal.
Attribute Effects on portrayal
displayName This Boolean attribute determines if the text for a name should
be displayed. If not populated the default rules provided in the
portrayal catalogue will be used.
information Population of this complex attribute will result in the display of
the magenta information symbol to highlight additional
information to the user.
pictorialRepresentation The population of this Text attribute will result in the display of
the magenta information symbol to highlight additional
information to the user.
textContent The population of this complex attribute will result in the
display of the magenta information symbol to highlight
additional information to the user.
Table 0-5 Attributes which have effects on portrayal

Note: Since S-122 data is scale-independent, the S-101 attribute scaleMinimum is superfluous
and not used in S-122 datasets.
Textual information
Textual information may provide additional information essential to understand the presence
of the MPA and other features of an S-122 product. This information may also provide legal
information pertaining to the S-122 product features.

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 11

The methods to provide textual information vary from the simple provision of short text, to the
more structured provision of extensive text. The length of the text determines the method and
the attribute selection, see section 0.
Specialized information types for common kinds of textual information
The information types Restrictions, Recommendation, Regulations, NauticalInformation
must be used to encode text information when the DCEG allows them to be associated to the
feature or information type and the information is of the appropriate kind (a restriction,
regulation, etc.).
In exceptional circumstances and only if the use of the information types Restrictions,
Recommendation, Regulations is not sufficient, NauticalInformation can be used to encode
additional textual information associated to a feature or a group of features.
In some cases, there may be a specialized attribute that is specifically intended for the data in
question. If an appropriate specialized attribute is available, it must be used in preference to
information or textContent. For example, feature names will generally be encoded in the
name sub-attribute of complex attribute featureName, instead of information->text.
Textual information attributes
Textual information which is not appropriate for any of the Text-type attribute (or sub-attribute)
allowed for the feature/information type should be encoded using either information or
textContent complex attributes. Generally, either information or textContent is allowed, but
not both.
Languages
Complex attribute information defines a language sub-attribute for specifying the language
in which the text or referenced file is encoded.
The exchange language for textual information should be English; therefore it is not required
to populate the sub-attribute language for an English version of textual information.
Languages other than English may be used as a supplementary option, for which language
must be populated with an appropriate value to indicate the language.
When a national language is used in the textual attributes, the English translation must also
exist.
Minimal use of generalized text attributes
The complex attributes information and textContent must not be used when it is possible to
encode the information by means of any other attribute. The population of these attributes
provides symbols on an ECDIS screen. Therefore producers should carefully consider use of
these attributes as the symbol may contribute significantly to ECDIS screen clutter and text
attributes should be populated only when the content conveys useful information.
Short textual information
The text sub-attribute of complex attribute information should generally be used for short
notes or to transfer information which cannot be encoded by other attributes, or to give brief
information about a feature. The use of the complex attribute information as a stand-alone
complex attribute is intentionally limited to the information types ContactDetails,
Applicability, NonStandardWorkingDay and ServiceHours, which do not need the
additional attributes defined in textContent. The reason for the limited use of information as
a stand-alone complex attribute is to provide a structured and harmonised approach to textual
information within the S-122 product data sets.
The text populated in text must not exceed 300 characters. Character strings contained in text
sub-attributes must be UTF-8 character encoding.

S-122 Appendix A January 2019 Edition 1.0.0

 12 Data Classification and Encoding Guide

If the text sub-attribute of information is populated, the headline, fileReference, and

fileLocator sub-attributes must not be populated.
Complex or lengthy textual information
More complex encodings of text may use either information or textContent. The feature
catalogue and the feature/information type definitions in this DCEG indicate whether
information or textContent is allowed.
The complex attribute textContent also has information as a complex sub-attribute. If a short
note must be encoded in a feature or information type which has only textContent as an
attribute, it should be encoded as textContent->information->text.
Complex text information, such as text longer than 300 characters, formatted text, or HTML
extracts from shipping regulations, must be encoded in a file named in either
information->fileReference or textContent->information->fileReference. The construction
textContent->information->fileReference should be used if the feature/information type
provides textContent as complex attribute.
The complex attribute information defines an optional sub-attribute headline which may be
used for a short title not exceeding 60 characters. The content should be short but informative
– if the textual information is divided into sections, the most relevant section header from the
referenced content may be a good choice for headline.
The complex attribute textContent defines an optional sub-attribute categoryOfText for
indicating whether the text is the full text from the source, an extract from the source, or a
summary prepared by the encoder. Populating categoryOfText is recommended whenever
the textual information is taken or summarized from a law or regulation.
If it is considered necessary to include a description of the source of the textual information,
the sub-attribute sourceIndication of textContent must be used. Encoding a description of
the source is strongly recommended for textual information whose source is considered
information the end-user must have, e.g., because the date of issue must be conveyed or
because it cites official regulations which are frequently updated.
COMMENT: Some government documents are frequently updated, e.g., the U.S. Electronic
Code of Federal Regulations, which is currently updated every working day even though a
particular section may be stable for years.
Attributes referencing external files

Predefined derived types

Table 0-6 presents the following predefined derived types which are described in S-100 (§ 1-
4.6 in Edition 3.0.0):

Name Description Derived from

A uniform resource identifier which character encoding shall follow
URI CharacterString
the syntax rules as defined in RFC 3986.
EXAMPLE http://registry.iho.int
A uniform resource locator (URL) is a URI that provides a means of
URL URI
locating the resource by describing its primary access mechanism
(RFC 3986).
EXAMPLE http://registry.iho.int
A persistent, location-independent, resource identifier that follows
URN URI
the syntax and semantics for URNs specified in RFC 2141.
EXAMPLE urn:iho:s101:1:0:0:AnchorageArea
Table 0-6 Predefined derived types

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 13

Reference to textual files

The information types Restrictions, Recommendation, Regulations, NauticalInformation
should be used to encode textual information.
The files referenced by textContent, sub-complex attribute information and its sub attribute
fileReference must be *.TXT, *.HTM or *.XML files, and may contain formatted text. It is up
to the Producing Authority to determine the most suitable means of encoding a particular piece
of text. Files must only use UTF-8 character encoding even when the sub-attribute language
is populated with a language other than English.
If it is necessary to indicate a specific section within a large text file, this may be done by
encoding the location in the fileLocator sub-attribute of information, as described in the
tableTable 0-7.
Format File extension Content of fileLocator
Text TXT The offset of the start of the section relative to the beginning of the file
(the first character in the file has offset 0).
HTML HTM The HTML fragment identifier, i.e., the value of the HTML name or id
attribute of the target (as defined in the relevant HTML specification).
XML XML The XML fragment identifier as defined in the relevant specification, e.g.,
the value of an xml:id attribute.
Table 0-7 Locators for external files
Reference to external sources
References to Internet sources should be encoded using the onlineResource sub-attribute of
textContent. Encoders should be aware that systems may not be able to access the Internet,
so onlineResource should be used only for non-essential information.
Only sources that can be certified as secure should be provided.
Reference to graphics
If it is required to indicate a graphic, the complex attribute graphic must be used. The sub-
attribute pictorialRepresentation must be used to indicate the file name (without the path) of
the external graphical file. Graphic files that form part of the MPA product must be content
with the characteristics collected in Table 0-8.
Characteristics Values
Recommended Resolution: 96 DPI
Minimum Size x,y: 200,200 pixels
Maximum Size x,y: 800,800 pixels
Bit Depth: 8 Bit Indexed Colour
Compression: LZW
Format: Tiff 6.0
File size Minimum, consider that 10 Mb is the maximum
allowable size of an MPA dataset
Table 0-8 Graphics Characteristics

Additional information about the graphic file may be encoded in other sub-attributes of attribute
graphic, as described in Section 0.
Dates
Dates may be complete or truncated values. The definition of the attribute will indicate if it must
take a complete value (type Date or DA) or is allowed to take a truncated value (type

S-122 Appendix A January 2019 Edition 1.0.0

 14 Data Classification and Encoding Guide

S100_TruncatedDate or TD). Complete and truncated dates are different value types (see S-
100 § 1-2 Table 1-2; also Table 0-9 of this DCEG).
For attributes that use the complete date type (type Date or DA), all their components (year,
month, and day) must be specified.
For attributes that use the truncated date type (type S100_TruncatedDate or TD), zero, one,
or two of the year/month/day components may be omitted. If the year component is included,
it must be specified using exactly 4 digits.
Complete Dates (Informative)
Complete date values must be encoded in conformance with the Date format as specified in
S-100 Ed. 2.0.0 (§§ 1-4.5.2) which is the same as the DA format in Table 0-2in this document.
The data values have to be provided in accordance with the Gregorian Calendar starting with
four digits for the year, two digits for the month and two digits for the day.
Example: The date 18 September 2010 is encoded as follows:
In the ISO 8211 format: 20100918
In the GML format: <date>2010-09-18</date>
Truncated Dates (Informative)
In Truncated Dates one or more components (year, month, or day) of the date is not specified.
Truncated date values must be encoded in conformance with the S100_TruncatedDate format
or equivalent as specified in S-100 Ed. 3.0.0 (§§ 1-4.5.2 and 3-9) which is the same as the TD
format in Table 2-2 in this document. If encoding attributes which can take truncated date
values (e.g., fixedDateRange, periodicDateRange, reportedDate) and no specific year,
month or day is required, the values must be encoded in conformance with the truncated date
format as specified in S-100 (§§ 1-4.5.2 and 3-9 in Edition 3.0.0) which define a default format
(for ISO 8211) but also allow the use of built-in types.
To encode partial dates in the GML and ISO 8211 data formats:

Description ISO 8211 GML

No specific year, same – – – –MMDD <gMonthDay>– –MM–DD</gMonthDay>
day each year
No specific year, same – – – –MM– – <gMonth>– –MM</gMonth>
month each year
No specific day YYYYMM– – <gYearMonth>>YYYY–MM </gYearMonth>
No specific month and YYYY– – – – <gYear>YYYY</gYear>
no specific day
Table 0-9 Date encoding in GML and ISO 8211 data formats

Note: YYYY = calendar year; MM = month; DD = day.

The dashes (–) indicating that the year, month or date which is not specified must be included
in the encoding (with no space between the dashes).
Start and end of ranges
In accordance with S-100 Ed. 2.0.0 § 3-8, the start and end instants of a range or period are
included in the range or period.
EXAMPLE 1: If the beginning of a date range is encoded as the complete date 01 January
2016, the period begins at 00:00:00 on 1 January 2016, and the whole of New Year’s Day is
included in the period. If the end of the date range is encoded as 01 January 2016, the period
ends at 24:00:00 on 1 January 2016, i.e., again the whole of New Year’s Day is included in the
period.

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 15

EXAMPLE 2: If the beginning of a period is encoded in truncated date format as – – – –01–

– (i.e., year and day not specified), the period begins at 00:00:00 on 1 January each year. If
the end of the period is encoded as – – – –01– –, the period ends at 24:00:00 on 31 January
each year.
Note 1) Particular care should be taken if the start or end date is 28 or 29 February. S-100 Ed.
2.0.0 § 3-8 explains the implications for end of February. For example, the truncated date – –
– –02– – will be interpreted as 29 February in leap years and 28 February in non-leap years,
while – –– –0228will be interpreted as 28 February in every year.
Note 2) In accordance with ISO practice, 00:00:00 means midnight at the start of a day and
24:00:00 means midnight at the end of a day.
Schedules
Weekly service schedules of a feature can be comprehensively described by using the
information types ServiceHours and NonStandardWorkingDay.
EXAMPLE:A feature service is available under normal operation status 24 hours/day on
Monday and Wednesday and from 08:00 to 16:00 LT from Thursday to Saturday. The service
is not available on public holidays and the 5 of August of each year.
ServiceHours
scheduleByDoW
categoryOfSchedule =1 (normal operation)
tmIntervalsByDoW
dayOfWeek =1(Monday), 3(Wednesday)
dayOfWeekRanges =0 (false)
timeReference = 2 (LT)
tmIntervalsByDoW
dayOfWeek =4(Thursday), 6(Saturday)
dayOfWeekRanges =1 (true)
timeReference = 2 (LT)
timeOfDayStart = 080000
timeOfDayEnd = 160000
NonStandardWorkingDay
fixedDate = – – – – 0805 (5 August)
variableDate = public holidays

If the days of week are known but the hours of availability are unknown, there is no time
attribute and the timeReference attribute must be nilled as described in section 2.4.4.
To encode two or more periods within the same day, repeat the timeOfDayStart and
timeOfDayEnd attributes. If one of the times is not known, it may be nilled as described in
section 2.4.4.
For example, to encode open hours of 8 a.m. to 12 noon and 1 p.m. to 5 p.m. on Thursdays
and Saturdays:
tmIntervalsByDoW
dayOfWeek =4(Thursday), 6(Saturday)

S-122 Appendix A January 2019 Edition 1.0.0

 16 Data Classification and Encoding Guide

dayOfWeekRanges =1 (true)
timeReference = 2 (LT)
timeOfDayStart = 080000
timeOfDayStart = 130000
timeOfDayEnd = 120000
timeOfDayEnd = 170000
The order of repeated timeOfDayStart and timeOfDayEnd attributes is significant, since
intervals are specified by matching them pairwise in order.
Times
If it is required to provide information of the start time and end time of an active period of a
feature, it must be encoded using the attributes timeOfDayStart and timeOfDayEnd. The
order has significance.
Combination of date schedules and times
Schedule information can also include time of day. The complex attribute tmIntervalsByDoW
also includes timeOfDayStart and timeOfDayEnd attributes to encode the daily start and end
times of service. Complete instructions on how to encode schedules are described in section
0.
Graphic information
A graphic file should be appropriate for the purpose and should supplement the information in
terms of navigational relevance. Preferably, the graphic should provide perspective relevant
to the view of the mariner. Graphics should be such that all the information in the graphic is
legible in the application display.
Graphic information must be encoded using the complex attribute graphic. The simple sub-
attribute pictureInformation should be used to provide credits to the picture creator, copyright
owner etc.
The source date can either be of a complete date (see chapter 0) or truncated date (see
chapter 0) type.
Assuming that graphic information provides a coastal view, mariners are interested in knowing
from which point on sea that graphic has been taken. The complex attribute
bearingInformation (see chapter 0) provides all necessary information.
Bearing information
The most accurate information should be provided if it is necessary to indicate a position from
where a picture has been taken. information is a sub-complex attribute of
bearingInformation and should be used to specify that no bearing information can be
provided whenever such is the case. The sub-attributes sectorBearing and orientation can
be used to describe a certain level of inaccuracy in the position determination.
Associations
Introduction
An association expresses a relationship between two classes - features, information types, or
a feature and an information type. Objects in the dataset (instances of feature/information
types) are related only if the link between them is encoded in the dataset.

EXAMPLE: An Authority information type provides the responsible authority information to

the Marine Protected Area feature. An association named protectedAreaAuthorityis used
to relate the two classes; roles are used to convey the meaning of the relationship.

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 17

Figure 2 Information association relating a feature to an information type

An association end may have a multiplicity which describes how many instances the feature
or information type instance at the other end is allowed to are to link to. In the figure, any single
instance of Marine Protected Area may link to any number of Authority instances.
Association names
The association name is normally provided by the UML diagram at the middle of the connection
line/arrow between the two involved classes and can be obtained from the feature and
information type tables provided in this document).
Association names may be omitted in the UML diagrams for the following reasons:
a) the association is defined by an association class, see 0 (the name of the association class
is used);
b) to avoid cluttering the diagram – however, the name is always documented in the
feature/information type tables.
Association roles
Either or both association ends can have a name (role). In Figure 2 the roles are
theMarineProtectedArea and responsibleAuthority. This association expresses the
relationship that a Marine Protected Area may have any number of responsible Authorit(ies),
and an Authority may be responsible for any number of Marine Protected Areas.
Roles may be also omitted from the diagram to reduce clutter – again, the role name is
documented in the feature/information type tables.
Note: Instead of documenting every single role, Product Specifications may describe rules for
defining default roles.
Association classes
Association classes allow relationships to be characterized by one or more attributes. The
attributes of the association class belong to the association itself, not to any of the features or
information types it connects. An association class is both an association and a class. Within
an S-122 product the association classes Permission Type and Inclusion Type may be used
for relating vessel classes to feature and information types.
Permission Type
This association class specifies the relationship of the vessel class to a feature, e.g., whether
access to a feature (or use of a facility) is prohibited or permitted for a specified class of vessel.
The class of vessel is described by the simple and complex attributes of the information type
Applicability such as length, cargo, etc. The attributes of the association class describe the
nature of the relationship, i.e., whether access to an area is permitted or prohibited, or whether
use of a vessel traffic service is required or recommended.

S-122 Appendix A January 2019 Edition 1.0.0

 18 Data Classification and Encoding Guide

Figure 3 Association class for permission of vessel types in participating

EXAMPLE: An association between an Applicability instance with attribute

categoryOfDangerousOrHazardousCargo = Class 3 and an instance of feature
VesselTrafficServiceArea, with Permission Type’s attribute categoryOfRelationship =
required, means that vessels carrying flammable liquids (hazardous cargo type class 3 in the
IMDG Code) must participate in the traffic control represented by the
VesselTrafficServiceArea.
Inclusion Type
This association class defines whether a specified customer (class of vessels, as described by
Applicability) is excluded or included from a particular regulation, recommendation, etc.
Again, the attributes of the association class describe the nature of the relationship; in this
case whether the vessel is included or excluded from the regulation, etc.

Figure 4 Association class for inclusion of vessel types in regulations

EXAMPLE: An association between an Applicability instance with attribute

categoryOfDangerousOrHazardousCargo = Class 3, with Inclusion Type’s attribute
membership = included, and an association of a Regulation instance to the same Inclusion
Type, means that the information provided by the Regulation (a sub-type of AbstractRXN)
applies to vessels carrying flammable liquids (hazardous cargo type class 3 in the IMDG
Code).

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 19

Note (1) Since AbstractRXN is an abstract type, it cannot have direct instances in the dataset.
Only instances of its (non-abstract) sub-types can be used.
Note (2) Specific tools may use different presentations in their user interfaces, e.g., as two
associations (as described in the text of the example), or one association with an association
class also shown (as shown in Figure 2).
Use of various associations

General
In general, associations must be encoded whenever the relationship is useful for navigation,
monitoring, voyage or route planning, or reporting purposes, or any other purpose for which
the dataset is intended. The multiplicity lower bound of “0” at an association end means only
that the absence of a link to the relevant instance does not invalidate the dataset. The encoding
instructions for individual feature and information types describe what associations are allowed
and whether they are required or optional.
Generic association for uncategorized additional information
Unless other associations are specified, information types are associated to the relevant
features using the association name additionalInformation and the role names provides and
providedBy.
Associations to Restrictions, Recommendation, Regulations and Nautical Information
The Restrictions, Recommendation, Regulations, Nautical Information are associated to
the relevant features using the association name associatedRxN (inherited from their
common abstract super-type). The roles at the ends of this association are appliesInLocation
and theRxN (the Restriction, Regulation etc.).
If the regulation applies only to a specific class, or if it mentions an exempt class, an additional
association to an Applicability object is encoded using the InclusionType association class.
Conventional Association
Certain features and information types may be permitted or required to have associations to
other feature or information types. The allowed or mandatory associations for a
feature/information type are listed in the documentation for individual types (Chapters 4–7
Definitions of the associations and roles are given in Chapter 10 (Associations).
Where to Encode Associations
The presentation and management of associations will be determined by the user interface of
the encoding software tools. Since S-100 edition 3.0.0 permits feature-information associations
to be encoded only from the geographic feature to the information type and not vice versa, the
information-to-feature link might be unavailable or treated differently from the feature-to-
information link.

Datasets
Types of Datasets
A dataset is a grouping of features, attributes, geometry and metadata which comprises a
specific coverage.
The following types of MPA dataset may be produced and contained within an exchange set:
Dataset Explanations
New dataset: Data for an area different (in coverage and/or
extent) to existing datasets.
New Edition of a dataset: A re-issue plus new information which has not
been previously distributed by Updates. Each New

S-122 Appendix A January 2019 Edition 1.0.0

 20 Data Classification and Encoding Guide

Edition of a dataset must have the same name as

the dataset that it replaces and should have the
same spatial extents. .
Table 0-10 MPA dataset types

Overlay data sets

S-122 datasets are intended to be used together with S-101 ENC (or similar data products)
which will act as a base layer. The base layer is expected to provide navigational and visual
context. Generally, an overlay dataset like S-122 does not provide “skin of the earth” coverage
and there will be large areas with no data coverage because the S-122 application schema
does not include any feature for designating a region as “other”, or “not a protected area” (i.e.,
there is no S-122 feature equivalent to the S-101 Unsurveyed Area). Further, an overlay
dataset does not include features that provide auxiliary information such as bathymetry within
a protected area or navigational marks that may have been installed to indicate the limits of a
protected area.
Data coverage
An MPA dataset can contain more than one Data Coverage (see clause 4.3). The data
boundary is defined by the extent of the Data Coverage meta features. Data must only be
present within Data Coverage meta features.
When a feature extends across datasets of overlapping scale ranges, its geometry must be
split at the boundaries of the Data Coverage features and its complete attribute description
must be repeated in each dataset.
An MPA Update dataset must not change the extent of the data coverage for the base MPA
Product. Where the extent of the data coverage for a base MPA Product is to be changed,
this must be done by issuing a New Dataset.
Discovery metadata
Discovery metadata is intended to allow applications to find out important information about
datasets and accompanying support files to be examined without accessing the data itself (or
without reading the support file). Discovery metadata includes, but is not limited to:
 information identifying the product specification and encoding format;
 edition and version numbers, production/release date, and other details of data creation
and updating;
 data coverage of the dataset;
 summary descriptions of content, purpose, use, and limitations;
 identification and contact information for the producer and distributor of the dataset.
S-122 uses the same components of discovery metadata as S-100. The mandatory
components for discovery metadata are defined in S-100 Edition 3.0.0 Appendix 4A-D and
consist of:
1) Exchange catalogue – a single exchange catalogue for an exchange set. (Subsets of
exchange sets are not envisaged.) The elements are defined in S-100 App. 4A § D-2.2
(S100_ExchangeCatalogue).
2) Dataset discovery metadata for each dataset in the exchange set. Elements are
defined in S-100 App. 4A § D-2.6 (S100_DatasetDiscoveryMetaData). Additional
elements have been defined in the main specification.
3) Support file discovery metadata for each support file in the exchange set. Elements are
defined in S-100 App. 4A § D-2.11 (S100_SupportFileDiscoveryMetaData).
Discovery metadata is generally encoded separately from the dataset itself so as to allow
applications to read it without processing the dataset itself (i.e., decrypt, decompress, or load
the dataset). The encoding format should be easily machine-readable and therefore may be
different from the dataset, e.g., the discovery data may be in XML while the data is encoded
as GML 3.2.1 format.

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 21

The content and structure of discovery metadata for this product specification is defined in
XML format defined by an XML schema available from www.iho.int or the S-100 schema
distribution site, provisionally https://github.com/IHO-S100WG.
Dataset header metadata
Dataset header metadata contains structural and discovery metadata that apply to the whole
dataset and are encoded in the dataset file. The elements are described in S-100 clauses 10b-
9.6.1 and 10b-9.6.2.
Dataset units
The depth, height and positional uncertainty units in a dataset must be metres.
Dataset Coverage
MPA datasets are spatially limited.
In areas which include neighbouring producer nations, producing agencies should co-operate
to agree on dataset boundaries and ensure no data overlap. Where possible, adjoining nations
should agree on common data boundaries within a technical arrangement based on
cartographic convenience and benefit to the mariner.
If an MPA extends outside the product coverage and the adjoining object does not exist, e.g.
due to delay in the production process by the neighbouring HO product, an indication should
be placed at the outer edge of the product.
Dataset Feature Object Identifiers
Each feature and information instance within an MPA must have a unique universal Feature
Object Identifier [FOID]. Where a real-world feature has multiple geometric elements within a
single MPA dataset due to the MPA dataset scheme, the same FOID may be used to identify
multiple instances of the same feature. Features within a dataset may carry multiple
geometries.
Features split across multiple datasets may be identified by the same FOID. Features
repeated in different scale ranges may be identified by the same FOID.
FOID must not be reused, even when a feature has been deleted. However, the same feature
can be deleted and added again later using the same FOID.
180° Meridian of Longitude
Datasets must not cross the 180° meridian of longitude.
Geographic names
Feature names
If it is required to encode an international or national geographic name, it must be done using
complex attribute featureName.
If it is required to encode a geographic name for which there is no existing feature, a specific
MarineProtectedArea, RestrictedArea (either Navigational or Regulatory) or
VesselTrafficServiceArea area feature must be created (see clauses 5.2-5.5). In order to
minimise the data volume, these features should, where possible, use the geometry of existing
features.
Geographic names should be encoded with the complex attribute featureName. The complex
attribute featureName consists of the simple sub-attributes language, name and a
Boolean type to indicate whether that particular name is the displayName or not.
National geographic names can be left in their original national language in a non-English
iteration of the complex attribute featureName (but only if the national language can be
expressed using lexical level 0 or 1), or transliterated or transcribed and used in an English
iteration of the complex attribute featureName, in which case the national name should be
populated in an additional iteration of the featureName.

S-122 Appendix A January 2019 Edition 1.0.0

 22 Data Classification and Encoding Guide

All area and point features within an MPA product should be encoded using featureName if a
name is available.
A group of protected areas associated with the same name should be encoded as spatial
attributes of the same MPA feature (so there would be only one MPA feature with
multiple spatial attributes for location).
Named features listed in Hydrographic Office’s Sailing Directions that may assist in
navigation should be encoded using feature name on the relevant feature.
In all instances, if the exact extent of the feature to be named is known, a feature must be
created. If the exact extent is not known, or the area is too small, an existing or specifically
encoded point feature should be used to encode the geographic name.
Text placement
The cartographic feature TextPlacement is used specifically to place text cartographically.
The properties of the TextPlacement feature are described as follows:
Geometry (point) – the point location of the centre of the text string.
Text type – the attribute (or class) which is to be placed.
Flip bearing – the angle forming a semi-circle within which the text can be placed.
The TextPlacement feature is associated to the feature which carries the text being placed.
The attribute textType determines which text string is to be displayed if more than one is
present. The TextPlacement feature ensures that as an MPA screen rotates from “north up”
(e.g. if display is set to “course up”) text can remain readable, or clear other important charted
information.
Scale policy
MPA data must be compiled in the best applicable scale. The use of the data itself is "scale
independent". That means that the data can be used at any scale. S-100 allows the
association of multiple spatial attributes to a single feature instance. Each of these spatial
attributes can in principle be qualified by maximum and minimum scales.
maximumDisplayScale and minimumDisplayScale define the range of display scales
within which a particular feature will be portrayed on the display if these scale
minimum/maximum functions are enabled in the ECDIS or another GIS device. A geo feature
with one or more spatial attributes can utilize the scale minimum and scale maximum
attributes on the link to the spatial object. There are essentially two ways in which these
attributes may be used.

1. A producer may decide to use only a scale minimum value. This option is employed when
the data producer wishes to turn off the display of a feature above certain scales. This is
particularly useful in areas with high data density, and when it is expected that the data will
be used at larger scales where data clutter might become an issue. Features are therefore
encoded with an applicable value, which represent the scale at which the producer wishes to
turn off the feature.

2. A producer may decide to provide several pairs of scale minimum and scale maximum
values. This decision may be based on the fact that for one particular feature different spatial
instances in different scale ranges should be provided to supply this particular feature with
more detailed geographic representation at larger scales.
An example can be a Marine Protected Area which has two spatial objects associated, first
one with only scale minimum value encoded at 21999, and the second spatial object encoded
with scale maximum at 22000 and scale minimum encoded with 999999. These values would
enable the use of a highly detailed geometry at larger scales than 22000, and a less detailed
geometry at scales of 22000 and less, while the Marine Protected Area would be turned off at
scales of 999999 and less.

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 23

A similar strategy can be followed to enable boundaries to conform to a scale-dependent

geometry such as a coastline. Conformance at different scales can achieved by using
minimum/maximum scales on spatial attributes to indicate which particular geometry should
be used at a given scale.

Authorities should cooperate at the regional or RENC level to determine a recommended

scale range at which the portrayal of the MPA information is suitable and consistent.

Scale
NULL (only allowed on minimum
display scale where the maximum
display scale = 10,000,000)
1:10,000,000
1:3,500,000
1:1,500,000
1:700,000
1:350,000
1:180,000
1:90,000
1:45,000
1:22,000
1:12,000
1:8,000
1:4,000
1:3,000
1:2,000
1:1,000
Table 0-11 Minimum display and maximum display scales

Masking
To improve the look and feel of the display of MPAs in ECDIS for the mariner certain features,
or certain edges of features, should be masked.
Surface features crossing MPA cell boundaries
When a single feature of type surface crosses the boundaries of adjoining MPA products, mask
the edge where it shares the geometry of the boundary in each MPA:

Figure 5 Surface feature crossing MPA products boundaries

S-122 Appendix A January 2019 Edition 1.0.0

 24 Data Classification and Encoding Guide

This allows the features to be displayed as a single feature of type surface rather than being
divided at the MPA product boundary and having the representation of two separate features.
NOTE: Some production software will automatically truncate (mask) features at the cell
boundary.
NOTE: Occasionally an edge of the boundary of an area actually coincides with the MPA
product boundary. Where this occurs and the production system applies automatic truncation
(masking) of this edge, the compiler must “unmask” that edge so as to avoid the appearance
of the area to be “open ended”.

Where features of type surface extend beyond the entire limit of data coverage for the MPA
product (see clause 4.3), all edges of these area features should be masked.

Figure 6 Surface features extending beyond the entire limit of data

coverage

The following table lists those features of type surface that should have edges masked where
the boundary of the area crosses or extends beyond the MPA product limit or the area of data
coverage of the MPA product.
Feature Type Comment
Marine Protected Area
Restricted Area Navigational
Restricted Area Regulatory
Vessel Traffic Service Area
Table 0-12 Features of which edges have to be masked when crossing the MPA product boundary

“Linear” surface features

If it is required to encode a linear feature when the only allowable primitive for the relevant
feature type is surface (e.g. a “linear” Marine Protected Area (see clause 5.2)), a “very narrow
surface” should be encoded. The suggested extent is 0.3mm wide at viewing scales (keeping
in mind that S-100 permits different spatial attributes at different scales.) An edge of this
surface should correspond to the position of the line. All other edges should be masked.

Figure 7 “Linear” Marine Protected Area

Description of table format for feature and information types

X.X Clause heading

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 25

IHO Definition: FEATURE: Definition. (Authority for definition).

S-122[Geo Feature/Information Type]: Feature (S-57 Acronym) S-122 feature and corresponding S-57
acronym (if applicable)

Primitives: Allowable geometric primitive(s) [Point, Curve, Surface]

Real World Paper Chart Symbol ECDIS Symbol

Example if real world Example(s) of paper chart Example(s) of proposed ECDIS
instance(s) of the Feature. equivalent symbology for the symbology for the Feature.
Feature (if applicable).

Allowable Encoding
S-122 Attribute S-57 Acronym Type Multiplicity
Value
Category of beer 1 : ale EN 1,1
2 : lager
3 : porter
4 : stout
5 : pilsener
6 : bock beer
7 : wheat beer
This section lists the allowable This section lists the This section lists the Attribute Multiplicity
attributes for the S-101 feature. corresponding S-57 allowable encoding values for type describes the
Attributes are listed in attribute acronym. A blank S-101 (for enumerate (E) (see “cardinality” of
clause
alphabetical order. Sub- cell indicates no Type attributes only). the attribute in
X.X).
attributes (Type prefix (S)) of corresponding S-57 Further information about the regard to the
complex (Type C) attributes are acronym. attribute is available in feature. If
listed in alphabetical order and Section XX. “(ordered)” is
indented directly under the entry included, the
for the complex attribute (see order of the
below for example). instances
matters. See
clause X.X.
Fixed date range C 0,1

Date end (DATEND) (S) DA 0,1

Date start (DATSTA) (S) DA 0,1

Feature/information associations
Type Association Class Role Mult. Class Role Mult.
Name
Aggr Name of the Feature or At “this” Feature or Role At “other” end
Information At “this” Information
Asso Association end end name x..y
Type at Type(s) at “other”
Comp “this” end x..y end

INT 1 Reference:The INT 1 location(s) of the Feature – by INT1 Section and Section Number (if applicable).
X.X.X Sub-clause heading(s) (see S-4 – B-YYY.Y)

S-122 Appendix A January 2019 Edition 1.0.0

 26 Data Classification and Encoding Guide

Introductory remarks. Includes information regarding the real world entity/situation requiring the encoding of the
Feature in the ENC, and where required nautical cartographic principles relevant to the Feature to aid the
compiler in determining encoding requirements.
Specific instructions to encode the feature.
Remarks:
 Additional encoding guidance relevant to the feature.
X.X.X.X Sub-sub-clause heading(s) (see S-4 – B-CCC.C)
Clauses related to specific encoding scenarios for the Feature (if required).
Remarks:
 Additional encoding guidance relevant to the scenario (if required).
Distinction: List of features in the Product Specification distinct from the Feature.

Remarks:
S-122 Attribute: Indentation of attributes indicates sub-attributes of complex attributes.
Complex attributes may also be sub-attributes of complex attributes, which is indicated
by further indentation of the attribute name in the tables.
S-122 Attribute: Attributes shown in grey text are ECDIS “system” attributes which are
not visible to the encoder, but are populated by the ENC production system in order to
assist with portrayal of ENC data in ECDIS.
S-57 Acronym: S-57 attribute acronyms shown in italic style text have been re-modelled
from S-57.
Allowable Encoding Value: For (EN) type attributes, the enumerates listed are only those
allowable for the particular occurrence of the attribute relevant to the feature. Allowable
values may vary for the attribute depending on the feature to which the attribute is bound.
Such bindings are defined in the S-122 Feature Catalogue. The full list of enumerates
that may be assigned to an attribute in S-122 can be found in the Simple Attributes
section of the printed feature catalogue document.
Type: The prefix (C) indicates that the attribute is a complex attribute. Complex
attributes are aggregates of other attributes that can be simple type or complex type (see
Product Specification main document). The prefix (S) indicates that the attribute is a
sub-attribute of a complex attribute. Complex attributes that are sub-attributes of a
complex attribute, and their sub-attributes, are indicated by indentation of the attribute
name in the S-122 Attribute column.
Association ends and multiplicities: A lower bound of 0 in the multiplicity at any end of an
association indicates only that the association is not mandatory for any particular
instance of the feature at the other end (i.e., it is not mandatory for an instance of “that”
feature type to have an association to a feature of “this” type). A lower bound of “1”
means that if an instance of “that” type exists, it must be associated to a instance of “this”
type. If the association is actually encoded then it amounts to saying that “this
relationship exists between these two instances” and there must be an appropriate
feature instance at both ends. Associations that are not mandatory should be encoded if
and only if they convey useful information.

Metadata Features
Introduction
The maximum use must be made of meta features to reduce the attribution on individual
features. In a base dataset (see S-122 MPA Product Specification main document clause 10),
some meta features are mandatory.
Mandatory meta features
The mandatory meta features are given in the following list:

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 27

DataCoverage: One or more DataCoverage features shall cover the dataset.

QualityOfNonBathymetricData: One or more QualityOfNonBathymetricData features shall
cover the dataset.
Data coverage meta feature
Data Coverage: In order to assist in data discovery, the meta feature Data Coverage must be
used to provide the area of coverage of the S-122 dataset. This means that Data Coverage
expresses where the presence or absence of S-122 geographic features is asserted. Unlike
S-101 datasets, there is no ‘skin of the earth’ principle in S-122 and there may be regions
covered by a Data Coverage but where no geographic S-122 feature is present.
.
IHO Definition: COVERAGE. A geographical area that describes the coverage and extent of spatial types.
(Adapted from S-57 Edition 3.1, Appendix A – Chapter 1, Page 1.210, November 2000).

S-122 Metadata Feature: Data Coverage (M_COVR)

Primitives: Surface

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding

S-122 Attribute Type Multiplicity
Acronym Value
Maximum display scale maximum display scale < IN 1,1
minimum display scale
Minimum display scale minimum display scale > IN 1,1
maximum display scale

INT 1 Reference:
Coverage
The meta feature Data Coverage encodes the area covered by the dataset. This feature is also used to provide
the ECDIS with the scale information necessary for the determination of dataset loading and unloading in relation
to the user selected viewing scale in the ECDIS. There must be a minimum of one Data Coverage feature in a
dataset. Data Coverage features must cover at least the extent of the spatial types in the dataset, and must not
overlap.

The use of S-122 data is scale-independent (see clause 2.8) and minimum display scale will normally be (null)
and maximum display scale 1000 (the extreme values in the table of scales in the S-101 ENC, see Table 2-11).
Should a producer need to encode different maximum and minimum display scales from the extreme (i.e., create
scale-dependent datasets), the values of maximum and minimum display scales should be harmonized with
base layer S-101 datasets (see the S-101 DCEG clause 3.4.1).

Given that S-122 data will overlay ENC and possibly other datasets, the conditions described in S-101 clause
3.4.1 for displaying overscale warnings and setting the viewing scale may be overridden by interoperability
constraints or the presence of higher-priority datasets. The specification of such behaviour is out of scope for
this document (the S-100 interoperability specification should address it for ECDIS).
Remarks:
 This meta feature is intended to support an indication of coverage.
 Where a dataset consists of only one Data Coverage feature, the value for the maximum display scale
populated in the dataset discovery metadata must be the same as the value populated for maximum
display scale on the Data Coverage.
Distinction: None

S-122 Appendix A January 2019 Edition 1.0.0

 28 Data Classification and Encoding Guide

Quality of non-bathymetric data

IHO Definition: QUALITY OF NON-BATHYMETRIC DATA. An area within which the best estimate of the overall
uncertainty of the data is uniform. The overall uncertainty takes into account for example the source accuracy,
chart scale, digitising accuracy etc. (Adapted from S-57 Edition 3.1, Appendix A – Chapter 1, Page 1.208,
November 2000).

S-122 Metadata Feature: Quality of non-bathymetric data (M_ACCY)

Primitives: Surface

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding

S-122 Attribute Type Multiplicity
Acronym Value
Information C 0,*
File locator TE 0,1
File reference TE 0,1
Headline TE 0,1
language ISO 639-3 TE 0,1
Text TE 0,1
Category of temporal variation 1 : event EN 1,1
2 : likely to change
4 : unlikely to change
5 : unassessed
Data assessment 1 : assessed EN 1,1
2 : oceanic
3 : unassessed
Horizontal distance uncertainty (HORACC) RE 0,1
Direction uncertainty RE 0,1
Horizontal Positional uncertainty (POSACC) C 0,1
Uncertainty fixed RE 1,1
Uncertainty variable RE 0,1
Source indication C 0,1
Category of authority (all values) EN 0,1
country TE 0,1
Reported date TD 0,1
source TE 0,1
Source type (all values) EN 0,1
Feature name C 0,1
Display name BO 0,1
Language TE 0,1
Name TE 1,1
Survey date range C 0,1

Date end (SUREND) ISO 8601:2004 TD 1,1

Date start (SURSTA) ISO 8601:2004 TD 1,1

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 29

INT 1 Reference:
Quality of positions, distances, or directions
The meta feature Quality of Non-bathymetric Data may be used to provide an indication of the overall
uncertainty of position, distance, or direction for all non-bathymetric features. It must not be used to provide the
uncertainty of bathymetric information (which is not part of the S-122 data model as currently defined anyway).
The positional, distance, and direction uncertainty attributes give quantitative information, as compared to the
S-101 attribute quality of position which gives qualitative information.
Positional uncertainty on the Quality of Non-bathymetric Data applies to non-bathymetric data situated
within the area, while positional uncertainty on the associated spatial types qualifies the location of the Quality
of Non-bathymetric Data feature itself.
Source as a quality indicator
If the source from which encoded data or information are derived is expected to be a factor for mariner
assessment of data, the source indication attribute of Quality of Non-bathymetric Data may be used to
provide an indication of the source.
Remarks:
 No remarks.
Distinction: Quality of bathymetric data; quality of survey.

S-122 Appendix A January 2019 Edition 1.0.0

 30 Data Classification and Encoding Guide

Geo Features
This section describes abstract as well as non-abstract types. The abstract type FeatureType
cannot be used directly, but defines attributes inherited by its sub-types. The encoding remarks
in the description of FeatureType apply to its sub-types but may be overridden by remarks in
the sub-type.
FeatureType

IHO Definition: FEATURE TYPE: Generalized feature type which carries all the common attributes.

S-122 Geo Feature: FeatureType (Abstract)

Primitives: None

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding Multip

S-122 Attribute Type
Acronym Value licity
Fixed date range C 0,1

Date end (DATEND) TD 0,1

Date start (DATSTA) TD 0,1

Periodic date range C 0,*

Date end (PEREND) ISO 8601: 2004 TD 1,1

Date start (PERSTA) ISO 8601: 2004 TD 1,1
Feature name C 0,*
Display name (S) BO 0,1
Language ISO 639-3 (S) TE 0,1
Name (OBJNAM) (S) TE 1,1
(NOBJNM)
Source Indication (SORIND) (S) TE 0,1
Source Type 0,1
Source (S)TE 0,1

Reported Date TD 0,1

Country ISO3166-1-alpha2 TE 0,1

Category of Authority (CATAUT) EN 0,1

Feature name C 0,*

Display name (S) BO 0,1
Language ISO 639-3 (S) TE 0,1
Name (OBJNAM) (S) TE 1,1
(NOBJNM)
Text Content C 0,*
Category of Text 1: Abstract or summary EN 0,1
2: Extract
3: Full text

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 31

Information C 0,*
File Locator S (TE) 0,1
File Reference (TXTDSC) S (TE) 0,1
(NTXTDS)
Headline S (TE) 0,1
Language ISO 639-3 (S) TE 0,1
Text (INFORM) (S) TE 1,1
(NINFOM)
Online Resource C 0,1
Linkage ISO 19115-1:2014 URL 1,1
Protocol ISO 19115 (S) TE 0,1
Application Profile ISO 19115 (S) TE 0,1
Name of Resource ISO 19115 (S) TE 0,1
Online Description ISO 19115 (adapted) (S) TE 0,1
Online function 1: download EN 0,1
2: information
3: offline access
4: order
5: search
6: complete metadata
7: browse graphic
8: upload
9: email service
10: browsing
11: file access
Protocol Request ISO 19115 (S) TE 0,1
Source Indication (SORIND) (S) TE 0,1
Source Type (all values) EN 0,1
Source (S)TE 0,1
Reported Date TD 0,1
Country ISO3166-1-alpha2 0,1
Category of Authority (CATAUT) (all values) EN 0,1
Feature name C 0,*
Display name (S) BO 0,1
Language ISO 639-3 (S) TE 0,1
Name (OBJNAM) (S) TE 1,1
(NOBJNM)
Information associations
Type Association Name Class Role Mult. Class Role Mult.
Asso additionalInformation (any informationP 1..* Nautical providesInformation 0..*
subtype rovidedFor Information
of
FeatureT
ype)
Asso associatedRxN (any appliesInLoc 1..* Any subtype of theRXN 0..*
subtype ation AbstractRxN
of

S-122 Appendix A January 2019 Edition 1.0.0

 32 Data Classification and Encoding Guide

FeatureT
ype)
Asso PermissionType (any vslLocation 0..* Applicability permission 0..*
(association class) subtype
of
FeatureT
ype)
Feature Associations
Asso Text Association (any identifies 1..1 Text Placement positions 0..1
subtype)

INT 1 Reference:
Geographic features in general
Where a complex attribute has all its sub-attributes optional (e.g., multiplicity 0..1 or 0..*), at least one of the sub-
attributes must be populated.
The featureName attribute in complex attribute sourceIndication is intended for the name of the source.
The additionalInformation association to a NauticalInfomation object can be used to attach an additional
chunk of information to an information type, and there is no applicable specific information type or association.
This should be used sparingly if at all.
Restrictions, regulations, etc., related to geographic features
Navigation and other activities in areas can be limited by regulations/restrictions and recommendations. That
information is usually provided by relevant authorities. If the feature has specific attributes to encode such
information (such as a restriction attribute), those attributes must be used wherever possible; if the specific
attributes are insufficient, an appropriate Restrictions, Regulations, Recommendations, or
NauticalInformation information type can be associated to the feature using an associatedRxN association.
Restrictions, regulations, etc., that depend on vessel characteristics
Information that is conditional on vessel characteristics may be encoded using the PermissionType association
to an information type that defines the set of vessels to which the conditions apply. (See sections 2.5, 7.8, and
8.1 of this DCEG and section 6.2 of the S-122 Product Specification for more information about coding such
conditions.)
Remarks:
 No remarks.
Distinction:

Marine Protected Area

IHO Definition: MARINE PROTECTED AREA: Any area of the intertidal or sub tidal terrain, together with its
overlying water and associated flora, fauna, historical and cultural features, which has been reserved by law or
other effective means to protect part or all of the enclosed environment. (IUCN – The World Conservation Union.
1998. Resolution 17.38 of the 17th General Assembly of the IUCN. Gland, Switzerland and Cambridge, UK.).

S-122 Geo Feature: MarineProtectedArea

Supertype: FeatureType

Primitives: Curve, Surface

Real World Paper Chart Symbol ECDIS Symbol

.

S-57 Allowable Encoding Multip

S-122 Attribute Type
Acronym Value licity
Category of Marine Protected Area 1 : IUCN Category Ia CL 1,1

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 33

2 : IUCN Category Ib
3 : IUCN Category II
4 : IUCN Category III
5 : IUCN Category IV
6 : IUCN Category V
7 : IUCN Category VI
Category of restrictions 4: nature reserve EN 0,*
(CATREA)
5: bird sanctuary
6: game reserve
7: seal sanctuary
10: historic wreck area
20: research area
22: fish sanctuary
23: ecological reserve
27: Environmentally Sensitive
Sea Area (ESSA)
28: Particularly Sensitive Sea
Area (PSSA)
31: Coral Sanctuary
32: Recreation area
Jurisdiction 1: international EN 1,1
(JRSDTN)
2: national
2: national sub-division
Restriction 1: anchoring prohibited EN 0,*
(RESTRN)
2: anchoring restricted
3: fishing prohibited
4: fishing restricted
5: trawling prohibited
6: trawling restricted
7: entry prohibited
8: entry restricted
9: dredging prohibited
10: dredging restricted
11: diving prohibited
12: diving restricted
13: no wake
14: area to be avoided
15: construction prohibited
16: discharging prohibited
17: discharging restricted
18: industrial or mineral
exploration/ development
prohibited
19: industrial or mineral
exploration/ development
restricted
20: drilling prohibited
21: drilling restricted
22: removal of historical
artifacts prohibited
23: cargo transhipment
(lightering) prohibited
24: dragging prohibited
25: stopping prohibited
26: landing prohibited

S-122 Appendix A January 2019 Edition 1.0.0

 34 Data Classification and Encoding Guide

27: speed restricted

Status 1: permanent EN 0,*
(STATUS)
2: occasional
3: recommended
4: not in use
5: periodic/intermittent
6: reserved
7: temporary
8: private
9: mandatory
13: historic
14: public
16 : watched
17: un-watched
Inherited attributes:
Fixed date range C 0,1

Periodic date range C 0,*

Feature name C 0,*

Text Content C 0,*
Source Indication (SORIND) C 0,1

Information associations
Type Association Name Class Role Mult. Class Role Mult.
Assoc protectedAreaAuthority MarineProt theMarine 0..* Authority responsibleAuthority 0,*
iation ectedArea Protected
Area
Asso additionalInformation MarineProt informatio 1..* Nautical providesInformation 0..*
(inher ectedArea nProvided Information
ited) For

Asso associatedRxN MarineProt appliesInL 1..* Any subtype of theRxN 0..*

(inher ectedArea ocation AbstractRxN
ited)
Asso PermissionType MarineProt vslLocatio 0..* Applicability permission 0..*
(inher (association class) ectedArea n
ited)
Feature Associations
Asso Text Association (any identifies 1..1 Text Placement positions 0..1
(inher subtype)
ited)

INT 1 Reference: nil

Protected area categories
The Marine Protected Area categoryOfMarineProtectedArea attribute is an open enumeration codelist whose
‘standard’ values are specified by the IUCN categorization. National or other categorizations may be used for
‘additional’ values by agreement, but must be discussed with the S-122 project specification team before use.
Producers must not use local categorizations unilaterally, without discussion.
If the value cannot be provided the categoryOfMarineProtectedArea attribute has to set to "unknown".

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 35

Restrictions and regulations for protected areas

Navigation within Marine Protected areas can be limited by regulations/restrictions and recommendations. That
information is usually provided by relevant authorities. If the restriction attribute suffices to encode such
information, it must be used; otherwise an appropriate Restrictions, Regulations, Recommendations, or
NauticalInformation information type can be associated to the MarineProtectedArea.
Information that is conditional on vessel characteristics may be encoded using the PermissionType association
to an information type that defines the set of vessels to which the conditions apply. (See Section 6.2 of the S-
122 Product Specification and sections 2.5 and 7.8 of this DCEG for more information about coding such
conditions.)
Remarks:
nil
Distinction: Caution area; Marine farm/culture; Military practice area; Restricted area

Vessel Traffic Service Area

IHO Definition: VESSEL TRAFFIC SERVICE AREA: The area of any service implemented by a relevant
authority primarily designed to improve safety and efficiency of traffic flow and the protection of the environment.
It may range from simple information messages, to extensive organisation of the traffic involving national or
regional schemes. (IHO Dictionary – S-32)

S-122 Geo Feature: VesselTrafficServiceArea

SuperType: FeatureType

Primitives:Surface

Real World Paper Chart Symbol ECDIS Symbol

.

S-57 Allowable Encoding

S-122 Attribute Type Multiplicity
Acronym Value
Category of vessel traffic service 1 : Information Service EN 0,1
2 : Traffic Organisation
Service
3 : Navigational Assistance
Service
4 : Ship Reporting Service
5: Local Port Service
Inherited attributes
Fixed date range C 0,1

Periodic date range C 0,*

Feature name C 0,*

Text Content C 0,*

Source Indication (SORIND) C 0,1

Information associations
Type Association
Class Role Mult. Features Role Mult.
Name
Assoc VesselTraf
controlAut
srvControl ficService controlledService 0,1 Authority 0,1
hority
Area

S-122 Appendix A January 2019 Edition 1.0.0

 36 Data Classification and Encoding Guide

Assoc trafficServRept VesselTraf reptForLocation 0,* Ship Report reptForTra 0,*

ficService fficServ
Area
Asso additionalInform VesselTraf informationProvid 1..* Nautical providesIn 0..*
(inherite ation ficService edFor Information formation
d) Area

Asso associatedRxN VesselTraf appliesInLocation 1..* Any subtype of theRxN 0..*

(inherite ficService AbstractRxN
d) Area

Asso PermissionType VesselTraf vslLocation 0..* Applicability permissio 0..*

(inherite (association ficService n
d) class) Area

Feature Associations
Asso Text Association (any identifies 1..1 Text Placement positions 0..1
(inherite subtype)
d)

INT 1 Reference: nil

Vessel traffic services
Traffic control and other vessel traffic service areas are encoded in S-122 datasets only when they are related
to protected area information in some way, for example if it is necessary to provide information about reporting
entry into and departure from a protected area.
Remarks:
The area geometry presents where the service is provided.
Remarks:
nil
Distinction:

Restricted Area Navigational

IHO Definition: RESTRICTED AREA NAVIGATIONAL:A specified area on land or water designated by an
appropriate authority within which access or navigation is restricted in accordance with certain specified
conditions.(Adapted from IHO Dictionary – S-32). A navigational restricted area is an area where the restrictions
have a direct impact on the navigation of a vessel in the area.
S-122 Geo Feature: Restricted Area (RESARE)
Supertype: FeatureType

Primitives:Surface

Real World Paper Chart Symbol ECDIS Symbol

.

S-57 Allowable Encoding

S-122 Attribute Type Multiplicity
Acronym Value
Category of restricted area 4: nature reserve EN 0,*
(CATREA)
5: bird sanctuary
6: game reserve
7: seal sanctuary
10: historic wreck area
20: research area

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 37

22: fish sanctuary

23: ecological reserve
27: Environmentally Sensitive
Sea Area (ESSA)
28: Particularly Sensitive Sea
Area (PSSA)
31: Coral Sanctuary
32: recreation area
Restriction 1 : anchoring prohibited EN 0,*
(RESTRN)
2 : anchoring restricted
7 : entry prohibited
8 : entry restricted
13 : no wake
14 : area to be avoided
25 : stopping prohibited
26 : landing prohibited
27 : speed restricted
Status 1 : permanent EN 0,*
(STATUS)
2 : occasional
3 : recommended
4: not in use
5 : periodic/intermittent
6 : reserved
7: temporary
8: private
9 : mandatory
13: historic
14: public
16 : watched
17 : un-watched
Inherited attributes
Fixed date range C 0,1

Periodic date range C 0,*

Feature name C 0,*

Text Content C 0,*

Source Indication (SORIND) C 0,1

Information associations
Type Association Name Class Role Mult. Class Role Multiplicity
Asso additionalInformation Restrict informationProvided 1..* Nautical provid 0..*
(inherited) edArea For Information esInfor
Navigati mation
onal
Asso associatedRxN Restrict appliesInLocation 1..* Any subtype theRx 0..*
(inherited) edArea of N
Navigati AbstractRxN
onal
Asso PermissionType Restrict vslLocation 0..* Applicability permis 0..*
(inherited) (association class) edArea sion
Navigati
onal

S-122 Appendix A January 2019 Edition 1.0.0

 38 Data Classification and Encoding Guide

Feature Associations
Asso Text Association (any identifies 1..1 Text positio 0..1
(inherited) subtype Placement ns
)

INT 1 Reference:L 3, 5.2; M 29.1, N 2.1-2, 20-22, 25, 26, 31, 34, 63
Restricted areas in general
(see S-4 – B-431.4; B-435.7; B-435.11; B-437.1-7; B-439.2-4; B-445.9; B-448; B-448.1 and B-449.5)
There are many types of areas within which certain activities are discouraged or prohibited, or from which certain
classes of vessels are excluded. The general term for all areas in which certain aspects of navigation may be
restricted or prohibited by regulations is “Restricted Area”, or equivalent. The word “prohibited”, or its equivalent,
may appear in terms relating to activities which are contrary to the regulations, e.g. “Anchoring Prohibited”, “Entry
Prohibited”.
If it is required to encode a restricted area, it must be done using the feature Restricted Area or Marine
Protected Areas.
Restricted Area Navigational should be encoded in S-122 datasets only when they are one of the listed
categories or otherwise related to marine protected areas, environmental, or wildlife protection.
Remarks:
 The attribute category of restricted area is used to describe the type of area, while the attribute restriction
describes the restrictions.
 An associated instance of the information types Restrictions, Regulations, Recommendations and
Nautical Information, complex attributes text content sub-attribute information or solely attribute
information may be used to provide an additional explanation about the restriction, where required.

Nature reserves (see S-4 – B-437.3)

If it is required to encode a marine nature reserve area with navigational restrictions, it must be done using a
Restricted Area feature, with attribute category of restricted area = 4 (nature reserve).

Speed limits (see S-4 – B-430.2)

Speed is often limited inside MPAs in order to protect the species that inhabit the area. If it is required to encode
this restriction, it must be done using a Restricted Area Navigational feature, with the attribute restriction =
27 (speed restricted), with the speed limit and its unit of measurement encoded using an associated instance of
the information type Regulations(see clause 7.9),

Areas to be avoided (see S-4 – B-435.7)

If it is required to encode an IMO designated Area to be Avoided, it must be done using a Restricted Area
Navigational feature, with attribute restriction = 14 (area to be avoided).

Environmentally Sensitive Sea Areas (see S-4 – B-437)

If it is required to encode an Environmentally Sensitive Sea Area with navigational restrictions, it must be done
using a Restricted Area Navigational feature, with attribute category of restricted area = 27 (ESSA) or 28
(PSSA).
An Environmentally Sensitive Sea Area that is shown on the source as a point symbol should be encoded using
a small surface Restricted Area Navigational feature.

Distinction: Marine Protected Area; Restricted Area Regulatory

Remarks:
nil

Restricted Area Regulatory

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 39

IHO Definition: RESTRICTED AREA REGULATORY: A specified area on land or water designated by an
appropriate authority within which access or navigation is restricted in accordance with certain specified
conditions.(Adapted from IHO Dictionary – S-32).
A regulatory restricted area is an area where the restrictions have no direct impact on the navigation of a vessel
in the area, but impact on the activities that can take place within the area.
S-122 Geo Feature: Restricted Area Regulatory (RESARE)
Supertype: FeatureType

Primitives:Surface

Real World Paper Chart Symbol ECDIS Symbol

.

S-57 Allowable Encoding

S-122 Attribute Type Multiplicity
Acronym Value
Category of restricted area 4: nature reserve EN 0,*
(CATREA)
5: bird sanctuary
6: game reserve
7: seal sanctuary
10: historic wreck area
20: research area
22: fish sanctuary
23: ecological reserve
27: Environmentally Sensitive
Sea Area (ESSA)
28: Particularly Sensitive Sea
Area (PSSA)
31: Coral Sanctuary
32: recreation area
Restriction 3 : fishing prohibited EN 0,*
(RESTRN)
4 : fishing restricted
5 : trawling prohibited
6 : trawling restricted
9 : dredging prohibited
10 : dredging restricted
11 : diving prohibited
12 : diving restricted
15 : construction prohibited
16 : discharging prohibited
17 : discharging restricted
18 : industrial or mineral
exploration/development
prohibited
19 : industrial or mineral
exploration/development
restricted
20 : drilling prohibited
21 : drilling restricted
22 : removal of historical
artefacts prohibited
23 : cargo transhipment
(lightening) prohibited
24 : dragging prohibited
28 : swimming prohibited

S-122 Appendix A January 2019 Edition 1.0.0

 40 Data Classification and Encoding Guide

Status 1 : permanent EN 0,*

(STATUS)
2 : occasional
3 : recommended
4: not in use
5 : periodic/intermittent
6 : reserved
7: temporary
8: private
9 : mandatory
13: historic
14: public
16 : watched
17 : un-watched
Inherited attributes
Fixed date range C 0,1

Periodic date range C 0,*

Feature name C 0,*

Text Content C 0,*

Source Indication (SORIND) C 0,1

Information associations
Type Association Name Class Role Mult. Class Role Multiplicity
Asso additionalInformation Restrict informationProvided 1..* Nautical provid 0..*
(inherited) edArea For Information esInfor
Regulat mation
ory
Asso associatedRxN Restrict appliesInLocation 1..* Any subtype theRx 0..*
(inherited) edArea of N
Regulat AbstractRxN
ory
Asso PermissionType Restrict vslLocation 0..* Applicability permis 0..*
(inherited) (association class) edArea sion
Regulat
ory
Feature Associations
Asso Text Association (any identifies 1..1 Text positio 0..1
(inherited) subtype Placement ns
)

INT 1 Reference: L 3, 5.2; M 29.1, N 2.1-2, 20-22, 25, 26, 31, 34, 63
Restricted areas in general
(see S-4 – B-431.4; B-435.7; B-435.11; B-437.1-7; B-439.2-4; B-445.9; B-448; B-448.1 and B-449.5)
There are many types of areas within which certain activities are discouraged or prohibited, or from which certain
classes of vessels are excluded. The general term for all areas in which certain aspects of navigation may be
restricted or prohibited by regulations is “Restricted Area”, or equivalent. The word “prohibited”, or its equivalent,
may appear in terms relating to activities which are contrary to the regulations, e.g. “Anchoring Prohibited”, “Entry
Prohibited”.
If it is required to encode a restricted area where regulations apply to non-navigational activities, it must be done
using the feature Restricted Area Regulatory or Marine Protected Areas.

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 41

Restricted Area Regulatory should be encoded in S-122 datasets only when they are one of the listed categories
or otherwise related to marine protected areas, environmental, or wildlife protection.
Remarks:
 The attribute category of restricted area is used to describe the type of area, while the attribute
restriction describes the restrictions.
 An associated instance of the information types Restrictions, Regulations, Recommendations and
Nautical Information, complex attributes text content sub-attribute information or solely attribute
information may be used to provide an additional explanation about the restriction, where required.

Nature reserves (see S-4 – B-437.3)

If it is required to encode a marine nature reserve area where restrictions on non-navigational activities apply, it
must be done using a Restricted Area Regulatory feature, with attribute category of restricted area = 4
(nature reserve).

Speed limits (see S-4 – B-430.2)

Speed is often limited inside MPAs in order to protect the species that inhabit the area. If it is required to encode
this restriction, it must be done using a Restricted Area Regulatory feature, with the attribute restriction = 27
(speed restricted), with the speed limit and its unit of measurement encoded using an associated instance of the
information type Regulations (see clause 7.9).

Anchoring restricted (see S-4 – B-431.4)

If it is required to encode a restricted anchoring area, it must be done using a Restricted Area Regulatory
feature or using other features with the attribute restriction, where restriction = 1 (anchoring prohibited) or 2
(anchoring restricted). Additional information about the restriction should be encoded using an associated
instance of the information class Nautical Information, complex attribute information.

Environmentally Sensitive Sea Areas (see S-4 – B-437)

If it is required to encode an Environmentally Sensitive Sea Area where non-navigational restrictions apply, it
must be done using a Restricted Area Regulatory feature, with attribute category of restricted area = 27
(ESSA) or 28 (PSSA).
An Environmentally Sensitive Sea Area that is shown on the source as a point symbol should be encoded using
a small surface Restricted Area Regulatory feature.

Distinction: Marine Protected Area; Restricted Area Navigational

Remarks:
nil

Cartographic Features
This product specification uses the TextPlacement cartographic features derived from S-101
(version 1.0). The structure of the feature and its usage are the same as in S-101 but the
feature specification in S-122 omits elements which are not relevant to marine protected areas,
for example, ‘light characteristic’ is omitted as a listed value for the attribute text type.
Text Placement
IHO Definition: TEXT PLACEMENT. The Text Placement feature is used in association with the Feature Name
attribute or a light description to optimise text positioning in ECDIS..

S-122 Appendix A January 2019 Edition 1.0.0

 42 Data Classification and Encoding Guide

S-122 Cartographic Feature: Text Placement

Primitives: Point

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding Multip

S-122 Attribute Type
Acronym Value licity
Flip bearing RE 0,1
Scale minimum IN 0,1
Text justification 1 : left EN 1,1
2 : centred
3 : right
Text TE 0,1

Text type 1: Feature name EN 0,1

Information associations
Type Association Name Class Role Mult. Class Role Mult.
Asso Text Association Text positions 0,1 All Geo identifies 1,1
Placement Features

Text Placement
If it is required to place text on an MPA to improve clarity of display, it must be done using the cartographic
feature Text Placement. The Text Placement feature must associated with the relevant geo feature using the
association Text Association.
Remarks:
 The Text Placement feature is used by the ECDIS to position the associated text, which has been
populated using an attribute(s) for the related feature. This attribute is identified by populating the
attribute text type. Alternatively, the text to be displayed may be encoded using the attribute text.
 Only one of the attributes text or text type are allowable for each instance of Text Placement.
 Text Placement should only be associated with features of type point, and used in areas where it is
important that text clear navigationally relevant areas, for example shipping channels and dredged
areas.
Distinction:

Information Types
This section describes abstract as well as non-abstract types. The two abstract types
InformationType and AbstractRxN cannot be used directly, but define attributes inherited by
their sub-types. The encoding remarks apply to their sub-types but may be overridden by
remarks in the sub-type.

See Clause 6.2 (Application Schema) of the S-122 product specification for general guidance
on which combinations of types should be used to encode concepts likely to be encountered
in source material.

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 43

InformationType

IHO Definition: INFORMATIONTYPE. Generalized information type which carries all the common attributes

S-122 Information Type: InformationType (Abstract)

Primitives: None

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding Multip

S-122 Attribute Type
Acronym Value licity
Fixed date range C 0,1

Date end (DATEND) TD 0,1

Date start (DATSTA) TD 0,1

Periodic date range C 0,*

Date end (PEREND) ISO 8601: 2004 TD 1,1

Date start (PERSTA) ISO 8601: 2004 TD 1,1
Feature name C 0,*
Display name (S) BO 0,1
Language ISO 639-3 (S) TE 0,1
Name (OBJNAM) (S) TE 1,1
(NOBJNM)
Source Indication (SORIND) C 0,1
Source Type (all values) EN 0,1
Source (S)TE 0,1

Reported Date TD 0,1

Country ISO3166-1-alpha2 TE 0,1

Category of Authority (CATAUT) (all values) EN 0,1

Feature name C 0,*

Display name (S) BO 0,1
Language ISO 639-3 (S) TE 0,1
Name (OBJNAM) (S) TE 1,1
(NOBJNM)
Information associations
Type Association Name Class Role Mult. Class Role Mult.
Asso additionalInformation (any informationP 0,* Nautical providesInformation 0,*
subtype rovidedFor Information
of
Informati
onType)

INT 1 Reference:

S-122 Appendix A January 2019 Edition 1.0.0

 44 Data Classification and Encoding Guide

Information types in general

Where a complex attribute has all its sub-attributes optional (e.g., multiplicity 0..1 or 0..*), at least one of the sub-
attributes must be populated.
The featureName attribute of an instance of an information type can be used for a short title that is either a
proper name (if such is relevant) or which describes the instance. For example, the featureName attribute of an
Authority information type can be the name of a government agency; the featureName attribute of a
ShipReport can be a short descriptive title of the report.
FeatureName attributes of information types should not duplicate the geographic feature name of an associated
feature, but should pertain to the information instance itself.
The featureName attribute should be populated only if the value conveys useful information to the end user.
Some examples of such situations are:
 providing the name of an organisation, such as the name of an Authority.
 distinguishing between instances – if multiple instances of the same information type are associated to
the same feature type (or another information type), the different instances may be given descriptive
names to make it easier for the mariner to distinguish their content.
Some information instances are associated to multiple features, in which case its name should be general
enough to be relevant to all the features.
For example, if naming Regulations instances describing fishing regulations for protected areas, consider
whether (for example) there is a general regulation applicable to all protected areas in a jurisdiction and an
exceptional regulations object associated to a single area or a subset of areas in the jurisdiction. In this situation,
the general regulations may be encoded with the name “General fishing regulations for Marine Conservation
Areas” and associated to several MPA features, while a specific MPA feature can also have a specific regulation
whose name is “Special fishing regulations for (named area)”.
The featureName attribute in complex attribute sourceIndication is intended for the name of the source.
The additionalInformation association to a NauticalInfomation object can be used to attach an additional
chunk of information to an information type, and there is no applicable specific information type or association.
This should be used sparingly if at all.
Remarks:
 No remarks.
Distinction:

AbstractRxN
IHO Definition: ABSTRACTRXN. An abstract superclass for information types that encode rules,
recommendations, and general information in text or graphic form.
Remark: Subtypes of AbstractRxN carry the same attributes, but differ in the nature of information they encode.
There are currently four such subtypes: Regulations, Restrictions, Recommendations, and
NauticalInformation.

S-122 Information Type: AbstractRxN (Abstract)

Supertype: InformationType

Primitives: None

Real World Paper Chart Symbol ECDIS Symbol

Allowable Encoding Multiplici

S-122 Attribute S-57 Acronym Type
Value ty
Category of Authority 1 : customs EN 0,1
2 : border control
3 : police

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 45

4 : port
5 : immigration
6 : health
7 : coast guard
8: agricultural
9: military
10: private company
11: maritime police
12: environmental
13: fishery
14: finance
15: maritime
Text Content C 0,*
Category of Text 1: Abstract or summary EN 0,1
2: Extract
3: Full text
Information C 0,*
Language ISO 639-3 (S) TE 0,1
Text (INFORM) (S) TE 0,1
(NINFOM)
File Reference (TXTDSC) S (TE) 0,1
(NTXTDS)
File Locator S (TE) 0,1
Headline S (TE) 0,1
Source indication C 0,1
Source Type (all values) EN 0,1
Source (S)TE 0,1
Reported Date TD 0,1
Country ISO3166-1-alpha2 TE 0,1
Category of Authority (CATAUT) (all values) EN 0,1
Feature name C 0,*
Display name (S) BO 0,1
Language ISO 639-3 (S) TE 0,1
Name (OBJNAM) (S) TE 1,1
(NOBJNM)
Online resource C 0,1
Linkage ISO 19115-1:2014 URL 1,1
Protocol ISO 19115 (S) TE 0,1
Application Profile ISO 19115 (S) TE 0,1
Name of Resource ISO 19115 (S) TE 0,1
Description ISO 19115 (S) TE 0,1
Online function 1: download EN 0,1
2: information
3: offline access
4: order
5: search
6: complete metadata

S-122 Appendix A January 2019 Edition 1.0.0

 46 Data Classification and Encoding Guide

7: browse graphic
8: upload
9: email service
10: browsing
11: file access
Protocol Request ISO 19115 (S) TE 0,1
Graphic C 0,*

Pictorial representation (PICREP) TE 0,1

Picture Caption TE 0,1

Source Date S(DA) 0,1
Picture Information TE 0,1
Bearing Information C 0,1
Cardinal Direction 1: N EN 0,1
2: NNE
3: NE
4: ENE
5: E
6: ESE
7: SE
8: SSE
9: S
10: SSW
11: SW
12: WSW
13: W
14: WNW
15: NW
16: NNW
Distance RE 0,1
Information C 0,*
Language ISO 639-3 (S) TE 0,1
Text (INFORM) (S) TE 1,1
(NINFOM)
Orientation (ORIENT) C 0,1
Orientation Uncertainty RE 0,1
Orientation Value R
Sector Bearing RE 0,2
ordered
rxnCode C 0,*
categoryOfRxN 1: navigation CL 0,1
2: communication
3: environmental
protection
4: wildlife protection
5: security
6: customs
7: cargo operation
8: refuge
9: health

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 47

10: natural resources or

exploitation
11: port
12: finance
13: agriculture
Action or activity 1: navigating with a pilot CL 0,1
2: entering port
3: leaving port
4: berthing
5: slipping
6: anchoring
7: weighing anchor
8: transiting
9: overtaking
10: reporting
11: working cargo
12: landing
13: diving
14: fishing
15: discharging
overboard
16: passing
Headline TE 0,1
Inherited attributes
Fixed date range C 0,1
Periodic date range C 0,1
Feature name C 0,*
Source Indication (SORIND) C 0,1

Information associations
Type Association Name Class Role Mult. Class Role Mult.
Asso InclusionType Subtypes of theApplica 0..* Applicability isApplicableTo 0,*
(association class) AbstractRxN bleRxN
Asso associatedRxN Subtypes of theRxN 0..* Subtypes of appliesInLocation 1..*
AbstractRxN FeatureType
Asso relatedOrganisation Subtypes of theInforma 0..* Authority theOrganisation 0..*
AbstractRxN tion

INT 1 Reference:
Abstract supertype for information from textual sources
AbstractRxN is the supertype of the four types intended primarily for encoding information from regulatory or
other text sources. The attributes categoryOfRxN and actionOrActivity should be encoded wherever possible
in order to allow software to classify the content according to the type of regulation (categoryOfRxN) and its
effects on common maritime activities by both commercial and recreational vessels.
At least one of the attributes textContent and graphic must be populated.
Subtypes of AbstractRxN must not be associated to NauticalInformation, since this leads to chains of
information types which have little or no meaning in reality.
Remarks:
 Association associatedRxN is with a geographic feature. While an association from geographic feature to
information type can be encoded in the geographic feature instance, the reverse association from the

S-122 Appendix A January 2019 Edition 1.0.0

 48 Data Classification and Encoding Guide

information type to the geographic feature may be omitted from the information type instance or encoded
using the generic inverse association invInformationAssociation instead of the named role.
Distinction:

Authority
IHO Definition: AUTHORITY. A person or organisation having political or administrative power and control.
(Oxford Dictionary of English).

S-122 Information Type: Authority

Supertype: InformationType

Primitives: None

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding Multip

S-122 Attribute Type
Acronym Value licity
Category of Authority 1 : customs EN 0,1
2 : border control
3 : police
4 : port
5 : immigration
6 : health
7 : coast guard
8: agricultural
9: military
10: private company
11: maritime police
12: environmental
13: fishery
14: finance
15: maritime
Text Content C 0,1
Category of Text 1: Abstract or summary EN 0,1
2: Extract
3: Full text
Information C 0,*
Language ISO 639-3 (S) TE 0,1
Text (INFORM) (S) TE 0,1
(NINFOM)
File Reference (TXTDSC) S (TE) 0,1
(NTXTDS)
File Locator S (TE) 0,1
Headline S (TE) 0,1
Source Indication (SORIND) (S) TE 0,1
Source Type 0,1
Source (S)TE 0,1

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 49

Reported Date TD 0,1

Country ISO3166-1-alpha2 0,1

Category of Authority (CATAUT) EN 0,1

Feature name C 0,*

Display name (S) BO 0,1
Language ISO 639-3 (S) TE 0,1
Name (OBJNAM) (S) TE 1,1
(NOBJNM)
Online Resource C 0,1
Linkage ISO 19115-1:2014 URL
Protocol ISO 19115 (S) TE 0,1
Application Profile ISO 19115 (S) TE 0,1
Name of Resource ISO 19115 (S) TE 0,1
Description ISO 19115 (S) TE 0,1
Online function 1: download EN 0,1
2: information
3: offline access
4: order
5: search
6: complete metadata
7: browse graphic
8: upload
9: email service
10: browsing
11: file access
Protocol Request ISO 19115 (S) TE 0,1
Inherited attributes
Fixed date range C 0,1
Periodic date range C 0,1
Feature name C 0,*
Source Indication (SORIND) C 0,1
Information associations
Type Association Name Class Role Mult Class Role Mult
Assoc srvControl Authority controlAutho 0..1 VesselTraffic controlledService 0..1
rity ServiceArea
Assoc authorityContact Authority theAuthority 0..* Contact theContactDetail 0,*
Details s
Assoc protectedAreaAuthority Authority responsibleA 0..* MarineProtect theMarineProtect 0,*
uthority edArea edArea
Assoc authorityHours Authority theAuthority 0..* Service Hours theServiceHours 0,*
_srvHrs
Assoc relatedOrganisation Authority theOrganisat 0..* Subtypes of theInformation 0..*
ion AbstractRxN
Assoc reptAuthority Authority reportTo 0..* ShipReport theShipReport 0..*
Asso additionalInformation Any informationP 0,* Nautical providesInformati 0,*
(inherited) information rovidedFor Information on
type

S-122 Appendix A January 2019 Edition 1.0.0

 50 Data Classification and Encoding Guide

INT 1 Reference:
Remarks:
 Associations protectedAreaAuthority and srvControl are with geographic features. While an association from
geographic feature to information type can be encoded in the geographic feature instance, the reverse
association from the information type to the geographic feature may be omitted from the information type
instance or encoded using the generic inverse association invInformationAssociation instead of the named
role.

Distinction:

Ship Report
IHO Definition: SHIP REPORT. This describes how a ship should report to a maritime authority, including when
to report, what to report and whether the format conforms to the IMO standard.

S-122 Information Type: Ship Report

Primitives:None

Real World Paper Chart Symbol ECDIS Symbol

Allowable Encoding
S-122 Attribute S-57 Acronym Type Multiplicity
Value
Category of Ship Report 1 : Sailing Plan EN 1,*
2 : position report
3 : deviation report
4 : final report
5 : dangerous goods report
6 : harmful substances report
7 : marine pollutants report
8 : any other report
IMO Format for Reporting True (Yes) BO 1,1

False (No)
Text Content C 0,*
Category of Text 1: Abstract or summary EN 0,1
2: Extract
3: Full text
Information C 0,*
Language ISO 639-3 (S) TE 0,1
Text (INFORM) (S) TE 0,1
(NINFOM)
File Reference (TXTDSC) S (TE) 0,1
(NTXTDS)
File Locator S (TE) 0,1
Headline S (TE) 0,1
Source Indication (SORIND) (S) TE 0,1
Source Type 0,1

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 51

Source (S)TE 0,1

Reported Date TD 0,1

Country ISO3166-1-alpha2 0,1

Category of Authority (CATAUT) EN 0,1

Feature name C 0,*

Display name (S) BO 0,1
Language ISO 639-3 (S) TE 0,1
Name (OBJNAM) (S) TE 1,1
(NOBJNM)
Online Resource C 0,1
Linkage ISO 19115-1:2014 URL 1,1
Protocol ISO 19115 (S) TE 0,1
Application Profile ISO 19115 (S) TE 0,1
Name of Resource ISO 19115 (S) TE 0,1
Description ISO 19115 (S) TE 0,1
Online function 1: download EN 0,1
2: information
3: offline access
4: order
5: search
6: complete metadata
7: browse graphic
8: upload
9: email service
10: browsing
11: file access
Protocol Request ISO 19115 (S) TE 0,1
Notice Time C 1,*

Notice Time Hours RE 0,* (ordered)

Notice Time Text TE 0,1

Operation 1: largest value EN 0,1

2: smallest value
Inherited attributes

Fixed date range C 0,1

Periodic date range C 0,1

Feature name C 0,*

Source Indication (SORIND) C 0,1

Information associations
Type Association Name Class Role Mult. Class Role Multiplicity
Assoc reptAuthority ShipReport theShipR 0..* Authority reportTo 0..*
eport

S-122 Appendix A January 2019 Edition 1.0.0

 52 Data Classification and Encoding Guide

Assoc trafficServRept ShipReport reptForTr 0..* VesselTr reptForL 0..*

afficServ afficServi ocation
ceArea
Assoc reportReqmt ShipReport theShipR 0..* Applicabil mustBeFi 0,*
eport ity ledBy
Asso additionalInformation Any informati 0,* Nautical providesI 0,*
(inherited) information onProvid Informati nformatio
type edFor on n

INT 1 Reference:
Remarks:
 textContent is used to describe non-standard ship reports. The associated Information Object Applicability
indicates characteristics of vessels which use this report.
 Association trafficServRept is with a geographic feature. While an association from geographic feature to
information type can be encoded in the geographic feature instance, the reverse association from the
information type to the geographic feature may be omitted from the information type instance or encoded
using the generic inverse association invInformationAssociation instead of the named role.
 Distinction:

Contact Details
IHO Definition: CONTACT DETAILS. Information on how to reach a person or organisation by postal, internet,
telephone, telex and radio systems.

S-122 Information Type: Contact Details

Primitives: None

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding

S-122 Attribute Type Multiplicity
Acronym Value
Call name (CALNAM) S(TE) 0,1

Call sign (CALSGN) 0,1

CommunicationChannel (COMCHA) TE 0..*

Maritime Mobile Service Identity (MMSI) I 0,1

Code
Category Of Communication Preference 1: preferred calling EN 0,1
(categoryOfCommPref) 2: preferred working
3: alternate calling
4: alternate working
Contact Instructions S(TE) 0,1

Contact Address C 0,*

Delivery Point S(TE) 0,*

City Name S(TE) 0,1

Administrative Division S(TE) 0,1

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 53

Country S(TE) 0,1

Postal Code S(TE) 0,1

Frequency pair C 0,1

Frequency shore station transmits I 0,*

Frequency shore station receives I 0,*

Contact Instructions S(TE) 0,*

Online Resource C 0,*

Linkage ISO 19115:2014 S(URL) 1,1

Protocol ISO 19115:2014 S(TE) 0,1

Application Profile ISO 19115:2014 S(TE) 0,1

Name of Resource ISO 19115:2014 S(TE) 0,1

Description ISO 19115:2014 S(TE) 0,1

Online function ISO 19115:2014 E(CL) 0,1

Protocol Request ISO 19115:2014 S(TE) 0,1

Telecommunications C 0,*

Category Of Communication Preference 1: preferred calling E 0,1

(categoryOfCommPref) 2: preferred working
3: alternate calling
4: alternate working
Telecommunication Identifier S(TE) 1,1

Telecommunication Carrier S(TE) 0,1

(telcomCarrier)
Contact Instructions S(TE) 0,1

Telecommunication Service 1: voice E(CL) 0,*

2: facsimile
3: SMS
4: data
5: streamedData
6: telex
7: telegraph
8: email
Schedule by day of week C 1,*

Category of schedule 1: normal operation EN 1,1

2: closure
3: unmanned operation
Time intervals by day of week C 1,*

Day of the Week 1: monday EN 0,7 (ordered)

2: tuesday
3: wednesday
4: thursday
5: friday
6: saturday
7: sunday

S-122 Appendix A January 2019 Edition 1.0.0

 54 Data Classification and Encoding Guide

dayOfWeekIsRange BO 0,1

timeReference 1: local time EN 1,1

2: UTC
timeOfDayStart TI 0,* (ordered)

timeOfDayEnd C 0,* (ordered)

Radiocommunications C 0..*

Category Of Communication Preference 1: preferred calling E 0,1

(categoryOfCommPref) 2: preferred working
3: alternate calling
4: alternate working
Communication channel TX 0,*

Contact instructions TX 0,1

Frequency pair C 0,*

Frequency shore station receives IN 0,*

Frequency shore station transmits IN 0,*

Time intervals by Day of Week C 0,*

(tmIntervalsByDoW)
Day of week 1: monday EN 0,7
2: tuesday
3: wednesday
4: thursday
5: friday
6: saturday
7: sunday
Day of week is range BO 0,1

Time reference 1: localTime EN 1,1

2: UTC
Time of day start TI 0,*

Time of day end TI 0,*

Inherited attributes

Fixed date range C 0,1

Periodic date range C 0,1

Feature name C 0,*

Source Indication (SORIND) C 0,1

Information associations
Type Association Name Class Role Mult. Class Role Mult.
Assoc authorityContact Contact Details theConta 0,* Authority theAutho 0..*
ctDetails rity
Asso Additional Information Any informati 0,* Nautical providesI 0,*
(inherited) information onProvid Informati nformatio
type edFor on n

INT 1 Reference:
Remarks:

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 55

 No remarks.
Use of complex attributes
Certain attributes, e.g., communicationChannel, are available inside other complex attributes as well as
directly in the feature type. The complex attributes should be used only when necessary. For example, if the
only available information is VHF communication channels and frequency pairs used (without any information
about schedules, special instructions, etc.), the complex attributes telecommunications and
radiocommunications need not be encoded – the available information can be encoded in attributes bound
directly to the feature (in ContactDetails.communicationChannel and ContactDetails.frequencyPair).
Encoding additional or special instructions for communication
Feature type ContactDetails and its complex attributes telecommunications and radiocommunications all
have the text attribute contactInstructions as an attribute or sub-attribute. This attribute should be used for
instructions which cannot be encoded using the other, more specific, attributes.
The attribute contactInstructions should contain only instructions that supplement the more specific attributes.
The portions of contact information which can be encoded in more specific attributes should be encoded using
those attributes.
Between feature type ContactDetails and its complex attributes telecommunications and
radiocommunications, contactInstructions is available in three places (as well as in frequencyPair). Use
the one at the same level as the attributes supplemented or explained by the intended content of
contactInstructions:
 If the intent is to supplement information encoded in complex attribute telecommunications, use
telecommunications.contactInstructions. Similarly for radiocommunications and frequencyPair.
 If the intent is to supplement an attribute bound directly to feature ContactDetails (e.g.,
ContactDetails.comunicationChannel, ContactDetails.categoryOfCommPref, or
ContactDetails.contactAddress), use ContactDetails.contactInstructions.

Special communication preferences

Communication preferences other than the listed values of categoryOfCommPref can be encoded in
contactInstructions. For example, if the preferred method of contact is always e-mail, it can be encoded in
telecommunications complex attribute with contactInstructions = “Preferred method of contact” (and its co-
attributes telecommunicationIdentifier and telecommunicationService populated with appropriate values).
The rule about using the contactInstructions attribute at the same level continues to apply.

Special schedules or supplementary information about schedules

Information about availability or times that cannot be encoded in the scheduleByDoW complex attribute may
be encoded as text in contactInstructions. The rule about using the contactInstructions attribute at the same
level continues to apply.

Distinction:

Service Hours
IHO Definition: SERVICE HOURS The time when a service is available and known exceptions.

S-122 Information Type: Service Hours

Primitives:None

Real World Paper Chart Symbol ECDIS Symbol

Allowable Encoding
S-122 Attribute S-57 Acronym Type Multiplicity
Value

S-122 Appendix A January 2019 Edition 1.0.0

 56 Data Classification and Encoding Guide

Schedule by day of week C 1,*

Category of schedule 1: normal operation EN 1,1

2: closure
3: unmanned operation
Time intervals by day of week C 1,*

Day of the Week 1: monday EN 0,7 (ordered)

2: tuesday
3: wednesday
4: thursday
5: friday
6: saturday
7: sunday
dayOfWeekIsRange BO 0,1
timeReference 1: local time EN 1,1
2: UTC
timeOfDayStart TI 0,* (ordered)
timeOfDayEnd C 0,* (ordered)
Information C 0,*
Language ISO 639-3 (S) TE 0,1
Text (INFORM) (S) TE 0,1
(NINFOM)
File Reference (TXTDSC) S (TE) 0,1
(NTXTDS)
File Locator S (TE) 0,1
Headline S (TE) 0,1
Inherited attributes
Fixed date range C 0,1
Periodic date range C 0,1
Feature name C 0,*
Source Indication (SORIND) C 0,1
Information associations
Type Association Name Class Role Mult. Class Role Mult.
Assoc exceptionalWorkday ServiceHours theServic 0..* NonStand partialWo 0..*
eHours_n ardWorkd rkingDay
sdy ay
Assoc authorityHours Service Hours theServic 0,* Authority theAuthor 0..*
eHours ity_srvHrs
Asso Additional Information Any informatio 0,* Nautical providesI 0,*
(inherited) information nProvided Informatio nformatio
type For n n

INT 1 Reference:
Seasonal variations in service hours
Seasonal variations in service hours can be encoded using multiple ServiceHours instances with appropriate
periodicDateRange values.
Remarks:
 No remarks.

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 57

Distinction:

Non Standard Working Day

IHO Definition: NON STANDARD WORKING DAY Days when many services are not available. Often days of
festivity or recreation when normal working hours are limited, esp. a national or religious festival, etc.

S-122 Information Type: Non Standard Working Day

Primitives:None

Real World Paper Chart Symbol ECDIS Symbol

Allowable Encoding
S-122 Attribute S-57 Acronym Type Multiplicity
Value
Fixed Date TD 0,*

Variable Date S(TE) 0,*

Information C 0,*
Language ISO 639-3 (S) TE 0,1
Text (INFORM) (S) TE 0,1
(NINFOM)
File Reference (TXTDSC) S (TE) 0,1
(NTXTDS)
File Locator S (TE) 0,1
Headline S (TE) 0,1
Inherited attributes
Fixed date range C 0,1
Periodic date range C 0,1
Feature name C 0,*
Source Indication (SORIND) C 0,1
Information associations
Type Association Name Class Role Mult. Class Role Mult.
Assoc exceptionalWorkday NonStandard partialWo 0..* Hours theServic 0..*
Workday rkingDay eHours_
nsdy
Asso Additional Information Any informati 0,* Nautical providesI 0,*
(inherited) information onProvid Informati nformatio
type edFor on n

INT 1 Reference:
Exceptions to usual workdays
This information type is used to indicate days that are exceptions to a usual weekly office opening schedule or
service availability schedule. It should be used to indicate holidays or similar exceptions to the normal weekly
schedule described by an associated ServiceHours instance.
NonStandardWorkingDay should not be used to indicate days of the week when the office is normally closed
or the service is normally unavailable. Regular weekly schedules can be described by ServiceHours alone.

S-122 Appendix A January 2019 Edition 1.0.0

 58 Data Classification and Encoding Guide

The attribute periodicDateRange of NonStandardWorkingDay can be used in the event that service hours
are the same but the variation in holidays or partial working days is seasonal – e.g., if an office is closed on
“second Saturdays” only in December. To encode working hours that vary seasonally, encode multiple instances
of ServiceHours instead, each with the appropriate periodicDateRange.
Attribute periodicDateRange should not be encoded if fixedDate or variableDate provide enough information
to determine the day.
EXAMPLE: If the variableDate is “U.S. Thanksgiving” periodicDateRange need not be encoded (the formula
for determining the date of the Thanksgiving holiday is fixed as “the fourth Thursday in November” for the
foreseeable future. (This information may be encoded as part the variableDate, thus: “U.S. Thanksgiving - fourth
Thursday in November”.)
Remarks:
 No remarks.
Distinction:

Applicability
IHO Definition: APPLICABILITY Describes the relationship between vessel characteristics and: (i) the
applicability of an associated information object or feature to the vessel; or, (ii) the use of a facility, place, or
service by the vessel; or, (iii) passage of the vessel through an area.

S-122 Information Type: Applicability

Primitives:None

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding

S-122 Attribute Type Multiplicity
Acronym Value
Ballast (BALAST) 1=Yes 0=No BO 0,1

Category of Cargo 1 : bulk EN 0,*

(CATCGO) 2 : container
3 : general
4 : liquid
5 : passenger
6 : livestock
7 : dangerous or hazardous
Category of Dangerous or Hazardous Cargo 1: IMDG Code Class 1 Div. EN 0,*
(CATDHC) 1.1
2: IMDG Code Class 1 Div.
1.2
3: IMDG Code Class 1 Div.
1.3
4: IMDG Code Class 1 Div.
1.4
5: IMDG Code Class 1 Div.
1.5
6: IMDG Code Class 1 Div.
1.6
7: IMDG Code Class 2.1
8: IMDG Code Class 2.2
9: IMDG Code Class 2.3
10: IMDG Code Class 3

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 59

11: IMDG Code Class 4.1

12: IMDG Code Class 4.2
13: IMDG Code Class 4.3
14: IMDG Code Class 5.1
15: IMDG Code Class 5.2
16: IMDG Code Class 6.1
17: IMDG Code Class 6.2
18: IMDG Code Class 7
19: IMDG Code Class 8
20: IMDG Code Class 9
21: Harmful Substances in
packaged form
Category of Vessel Registry 1: domestic EN 0,1
(CATRGY) 2: foreign

Category of Vessel 1: general cargo vessel EN 0,1

(CATVSL) 2: container carrier (CL)
3: tanker
4: bulk carrier
5: passenger vessel
6: roll-on roll-off
7: refrigerated cargo vessel
8: fishing vessel
9: service
10: warship
11: towed or pushed
composite unit
12: tug and tow
13: light recreational
14: semi-submersible
offshore installation
15: jack-up exploration or
project installation
16: livestock carrier
17: sport fishing
Thickness of Ice Capability IN 0,1
(ICECAP)
Logical Connectives 1: logical conjunction EN 0,1
(LOGCON) 2: logical disjunction

Vessel Performance TE 0,1

(PRFMNC)
Vessels Measurements C 0,*
(VSLMSM)
Comparison Operator 1: greater than EN 1,1
(COMPOP) 2: greater than or equal to
3: less than
4: less than or equal to
5: equal to
6: not equal to
Vessels Characteristics 1: length overall EN 1,1
(VSLCAR) 2: length at waterline
3: breadth
4: draught

S-122 Appendix A January 2019 Edition 1.0.0

 60 Data Classification and Encoding Guide

5: height
6: displacement tonnage
7: displacement tonnage,
light
8: displacement tonnage,
loaded
9: deadweight tonnage
10: gross tonnage
11: net tonnage
12: Panama Canal/Universal
Measurement System
net tonnage
13: Suez Canal net tonnage
14: Suez Canal gross
tonnage
Vessels CharacteristicsValue RE 1,1
(VSLVAL)
Vessels CharacteristicsUnits 1: metre EN 1,1
(VSLUNT) 2: foot
3: metric ton
4: ton
5: short ton
6: gross ton
7: net ton
8: Panama Canal/Universal
Measurement System net
tonnage
9: Suez Canal Net Tonnage
10: none
11: cubic metres
12: Suez Canal Gross
Tonnage
Information C 0,*
Language ISO 639-3 (S) TE 0,1
Text (INFORM) (S) TE 0,1
(NINFOM)
File Reference (TXTDSC) S (TE) 0,1
(NTXTDS)
File Locator S (TE) 0,1
Headline S (TE) 0,1
Inherited attributes
Fixed date range C 0,1
Periodic date range C 0,1
Feature name C 0,*
Source Indication (SORIND) C 0,1
Information associations
Type Association Name Class Role Mult. Class Role Mult.
Asso reportReqmt Applicability mustBeFi 0..* ShipReport theShipR 0,*
ledBy eport

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 61

Asso class PermissionType Applicability permissio 0..* Any subtype vslLocati 0,*
(Association class) n of on
FeatureType
Asso class InclusionType Applicability isApplica 0..* Any subtype theApplic 0,*
(Association class) bleTo of ableRXN
AbstractRXN
Asso Additional Any information informati 0,* Nautical providesI 0,*
(inherited) Information type onProvid Information nformatio
edFor n

INT 1 Reference:
(Most of the attribute acronyms in this table are referenced in the examples below, and not defined in S-57.)
Remarks:
 Vessel characteristics are specified as follows. Absent attributes or null values are ignored.
ballast (BALAST): The vessel is ballasted as described by this attribute.
vessels measurements (VSLMSM): The vessel or cargo matches the attribute value condition given by the
Comparison Operator and Characteristics Value sub-attributes (for multi-valued attributes, matches at least
one of the values).
ice capability (ICECAP), vessel performance (PRFMNC) attributes: The vessel meets or exceeds the
specified requirement (vessel’s ice-thickness rating, and performance characteristic, e.g., special
equipment).
logical connectives (LOGCON) states whether “all” or “at least one” of the specifications must be met.
categoryOfRelationShip (CATREL) in PermissionType indicates the relationship between vessels satisfying
the conditions described by Applicability and the associated feature (whether they are required, permitted,
prohibited, etc., from transit or use of the feature).
membership (MBRSHP) in InclusionType indicates the relationship between vessels satisfying the
conditions described by Applicability and the associated information object (whether they are included or
excluded from the scope of the associated regulation, restriction, recommendation, or general information).
The enumeration attributes have the significances indicated by their allowed value sets.
Example 1:
An Applicability with attributes:
VSLMSM [VSLCAR=length, VSLUNT=metre, COMPOP=greater than, VSLVAL=50]
CATVSL=3 (tanker)
LOGCON=1 (and)
CATREL=5 (required)
associated to a Pilot Boarding Place object:
Means: Tankers with LOA > 50.0 m must use the Pilot Boarding Place
Example 2:
PRFMNC="Vessels with thrusters"
MBRSHP=2 (excluded);
associated to a Regulations object:
Vessels with thrusters are exempted from the regulation.
Example 3:
With repeated VSLMSM:
VSLMSM [VSLCAR=length, VSLUNT=metre, COMPOP=(>), VSLVAL=50]
VSLMSM [VSLCAR=length, VSLUNT=metre, COMPOP=(<), VSLVAL=90]
CATDHC=19 (IMDG Code Class 8)

S-122 Appendix A January 2019 Edition 1.0.0

 62 Data Classification and Encoding Guide

LOGCON=1 (and)
MBRSHP=1 (included);
associated with Regulations:
The regulation applies to vessels with LOA greater than 50.0 m. and less than 90.0 m. carrying IMDG Class
8 cargo (corrosive substances).
 Multiple values of Category of Cargo and of Category of Dangerous Or Hazardous Cargo should be
treated as “inclusive OR” (i.e., if Category of Cargo=1 and 2, then it means vessels with either bulk or
container cargo or both).
 Conditions which cannot be encoded using the more specific attributes may be encoded in information.text.
Using the information.fileReference attribute to point to a text file describing the condition is an allowed
alternative, but encoding a short summary of the condition in information.text is recommended if there are
other conditions encoded in other attributes of this instance of Applicability.
 Associations PermissionType and InclusionType are association classes and encoded as described in ISO
19136-2 and S-100 10b-8.3. This should be handled by the production tools and transparent to the encoder.
Distinction:

Regulations
IHO Definition: REGULATIONS Regulations for a related area or facility.

S-122 Information Type: Regulations

Supertype: AbstractRxN

Primitives:None

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding

S-122 Attribute Type Multiplicity
Acronym Value
Inherited attributes
Fixed date range C 0,1
Periodic date range C 0,1
Feature name C 0,*
Source Indication (SORIND) C 0,1
Category of Authority EN 0,1
Text Content C 0,*
Graphic C 0,*

rxnCode C 0,*

Information associations
Role Type Association Name Class Role Mult. Class Role Multiplicity
Asso InclusionType Subtypes of theApplic 0..* Applicability isApplica 0,*
(inherited) (association class) AbstractRxN ableRxN bleTo

Asso associatedRxN Subtypes of theRxN 0..* Subtypes of appliesIn 1..*

(inherited) AbstractRxN FeatureType Location

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 63

Asso relatedOrganisation Subtypes of theInform 0..* Authority theOrgan 0..*

(inherited) AbstractRxN ation isation

INT 1 Reference: --
Regulations information type
The Regulations information type is intended to be used for official rules, laws, and similar source material, i.e.,
sources that have the force of law or are mandated by a controlling authority. They will generally originate from
some kind of administration or authority, including port authorities.
See the encoding remarks in super-type AbstractRxN for constraints on attributes and associations.
Remarks:
 Association associatedRxN is with a geographic feature. While an association from geographic feature to
information type can be encoded in the geographic feature instance, the reverse association from the
information type to the geographic feature may be omitted from the information type instance or encoded
using the generic inverse association invInformationAssociation instead of the named role.
Distinction: Nautical Information, Recommendations, Restrictions

Restrictions
IHO Definition: RESTRICTIONS Restrictions for a related area or facility.

S-122 Information Type: Restrictions

Supertype: AbstractRxN

Primitives:None

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding

S-122 Attribute Type Multiplicity
Acronym Value
Inherited attributes
Fixed date range C 0,1
Periodic date range C 0,1
Feature name C 0,*
Source Indication (SORIND) C 0,1
Category of Authority EN 0,1
Text Content C 0,*
Graphic C 0,*

rxnCode C 0,*

Information associations
Role Type Association Name Class Role Mult. Class Role Multiplicity
Asso InclusionType Subtypes of theApplic 0..* Applicability isApplica 0..*
(inherited) (association class) AbstractRxN ableRxN bleTo

Asso associatedRxN Subtypes of theRxN 0..* Subtypes of appliesIn 1..*

(inherited) AbstractRxN FeatureType Location
Asso relatedOrganisation Subtypes of theInform 0..* Authority theOrgan 0..*
(inherited) AbstractRxN ation isation

S-122 Appendix A January 2019 Edition 1.0.0

 64 Data Classification and Encoding Guide

INT 1 Reference: --
Restrictions information type
Restrictions is intended for restrictions that constrain the activities of vessels temporarily with or without the
legal force, or for longer terms without the force of law; they may be issued by a local authority such as a port
captain or US Coast Guard district.
See the encoding remarks in super-type AbstractRxN for constraints on attributes and associations.
Remarks:
 Association associatedRxN is with a geographic feature. While an association from geographic feature to
information type can be encoded in the geographic feature instance, the reverse association from the
information type to the geographic feature may be omitted from the information type instance or encoded
using the generic inverse association invInformationAssociation instead of the named role.
Distinction:Nautical Information, Recommendations, Regulations

Recommendations
IHO Definition: RECOMENDATIONS Recommendations for a related area or facility.

S-122 Information Type: Recommendations

Supertype: AbstractRxN

Primitives:None

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding

S-122 Attribute Type Multiplicity
Acronym Value
Inherited attributes
Fixed date range C 0,1
Periodic date range C 0,1
Feature name C 0,*
Source Indication (SORIND) C 0,1
Category of Authority EN 0,1
Text Content C 0,*
Graphic C 0,*

rxnCode C 0,*

Information associations
Role Type Association Name Class Role Mult. Class Role Multiplicity
Asso InclusionType Subtypes of theApplic 0..* Applicability isApplica 0,*
(inherited) (association class) AbstractRxN ableRxN bleTo

Asso associatedRxN Subtypes of theRxN 0..* Subtypes of appliesIn 1..*

(inherited) AbstractRxN FeatureType Location
Asso relatedOrganisation Subtypes of theInform 0..* Authority theOrgan 0..*
(inherited) AbstractRxN ation isation

INT 1 Reference: --

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 65

Recommendations information type

Recommendations is intended for practices that are recommended but do not have the force of regulations.
See the encoding remarks in super-type AbstractRxN for constraints on attributes and associations.
Remarks:
 Association associatedRxN is with a geographic feature. While an association from geographic feature to
information type can be encoded in the geographic feature instance, the reverse association from the
information type to the geographic feature may be omitted from the information type instance or encoded
using the generic inverse association invInformationAssociation instead of the named role.
Distinction:Nautical Information, Recommendations, Restrictions

Nautical Information
IHO Definition: NAUTICAL INFORMATION Nautical information about a related area or facility.

S-122 Information Type: Nautical information

Supertype: AbstractRxN

Primitives:None

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding

S-122 Attribute Type Multiplicity
Acronym Value
Inherited attributes
Fixed date range C 0,1
Periodic date range C 0,1
Feature name C 0,*
Source Indication (SORIND) C 0,1
Category of Authority EN 0,1
Text Content C 0,*
Graphic C 0,*

rxnCode C 0,*

Information associations
Role Type Association Name Class Role Mult. Class Role Multiplicity
Asso additionalInformation Nautical providesIn 0,* (any subtype informati 0,*
Information formation of onProvid
InformationTy edFor
pe)
Asso additionalInformation Nautical providesIn 0..* (any subtype informati 1..*
Information formation of onProvid
FeatureType) edFor
Asso InclusionType Subtypes of theApplic 0..* Applicability isApplica 0,*
(inherited) (association class) AbstractRxN ableRxN bleTo

Asso associatedRxN Subtypes of theRxN 0..* Subtypes of appliesIn 1..*

(inherited) AbstractRxN FeatureType Location

S-122 Appendix A January 2019 Edition 1.0.0

 66 Data Classification and Encoding Guide

Asso relatedOrganisation Subtypes of theInform 0..* Authority theOrgan 0..*

(inherited) AbstractRxN ation isation

INT 1 Reference: --
General nautical information
Nautical information is intended for material that is largely informative in nature, of which does not fit into the
category of regulation, recommendation, or restriction.
See the encoding remarks in super-type AbstractRxN for constraints on attributes and associations.
Remarks:
 Association additionalInformation may be with a geographic feature or an information type. Association
associatedRxN is with a geographic feature. While an association from geographic feature to information
type can be encoded in the geographic feature instance, the reverse association from the information type
to the geographic feature may be omitted from the information type instance or encoded using the generic
inverse association invInformationAssociation instead of the named role.
Distinction:Regulations, Recommendations, Restrictions

Spatial Quality
IHO Definition: SPATIAL QUALITY (Definition required.)

S-123 Information Feature: SpatialQuality

Primitives: None

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding

S-123 Attribute Type Multiplicity
Acronym Value
Category of temporal variation 1 : extreme event EN 0,1
2 : likely to change
4 : unlikely to change
5 : unassessed
Quality of horizontal measurement 1 : surveyed EN 0,1
2 : unsurveyed
3 : inadequately surveyed
4 : approximate
5 : position doubtful
6 : unreliable
7 : reported (not surveyed)
8 : reported (not confirmed)
9 : estimated
10 : precisely known
11 : calculated
Horizontal positional uncertainty C 0,1
Uncertainty fixed RE 1,1
Uncertainty variable RE 0,1
Information associations
Role Type Association Name Class Role Mult. Class Role Multiplicity

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 67

Asso Curve spatial definedF

Spatial Association Spatial Quality defines 0,1 1,*
types or

INT 1 Reference:
Spatial quality
Spatial attribute types may be associated with spatial quality attributes. Such an association provides quality
information for the referencing spatial primitive.
Spatial quality attributes are carried in the information class Spatial Quality. Only curves can be associated with
Spatial Quality (points can be associated with its subtype SpatialQualityPoints). Currently no use case for
associating surfaces with spatial quality attributes is known, therefore this is prohibited. Vertical uncertainty is
prohibited for curves as this dimension is not supported by curves.
Each instance of SpatialQuality must be associated to the geometry to which the information applies using the
association spatialAssociation (see clause 2.4.6.1). Note that the association is from the feature’s geometry
(spatial primitive).
Remarks: The specification of Spatial Quality in this edition is based on the DQWG model of data quality which
is still to be integrated into S-101.
Distinction: Quality of Non-bathymetric data; Spatial Quality Points

Spatial Quality Points

IHO Definition: SPATIAL QUALITY POINTS (Definition required)

S-123 Information Feature: SpatialQualityPoints

Supertype: SpatialQuality

Primitives: None

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding

S-123 Attribute Type Multiplicity
Acronym Value
Inherited attributes
Category of temporal variation 1 : extreme event EN 0,1
2 : likely to change
4 : unlikely to change
5 : unassessed
Quality of horizontal measurement 1 : surveyed EN 0,1
2 : unsurveyed
3 : inadequately surveyed
4 : approximate
5 : position doubtful
6 : unreliable
7 : reported (not surveyed)
8 : reported (not confirmed)
9 : estimated
10 : precisely known
11 : calculated
Horizontal positional uncertainty C 0,1
Uncertainty fixed RE 1,1

S-122 Appendix A January 2019 Edition 1.0.0

 68 Data Classification and Encoding Guide

Uncertainty variable RE 0,1

Information associations
Role Type Association Name Class Role Mult. Class Role Multiplicity
Asso Point spatial definedF
Spatial Association Spatial Quality defines 0,1 1,*
types or

INT 1 Reference: --
Spatial quality for points
SpatialQualityPoints is a subtype of SpatialQuality which can be associated to point spatial objects.
Each instance of SpatialQualityPoints must be associated to the geometry to which the information applies
using the association spatialAssociation (see clause 2.4.6.1). Note that the association is from the feature’s
geometry (spatial primitive).
Remarks: The specification of SpatialQualityPoints in this edition is based on the DQWG model of data quality
which is still to be integrated into S-101.
Distinction: Spatial Quality; Quality of Non-bathymetric Data

Association Classes
Permission Type
IHO Definition: PERMISSION TYPE Association class for associations describing whether the subsets of
vessels determined by the ship characteristics specified in Applicability may (or must, etc.) transit, enter, or
use a feature.

S-122 Information Type: Permission Type

Primitives:None

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding

S-122 Attribute Type Multiplicity
Acronym Value
Category of Relationship 1: prohibited EN 0,1
2: not recommended
3: permitted
4: recommended
5: required
6: not required
Information associations
Type Association Name Class Role Mult. Class Role Mult.
Asso PermissionType PermissionType 1..1 Applicability
vslLocation permission 1..1
(association class)
Asso PermissionType PermissionType permission 1..1 Subtypes of vslLocatio 1..1
(association class) FeatureType n

INT 1 Reference:
Remarks:
The GML format implements and used association classes in accordance with ISO 19136-2. The association
class is implemented as an information type instance with information associations to and from the two classes

S-122 Appendix A January 2019 Edition 1.0.0

 Data Classification and Encoding Guide 69

linked by the association, as listed above. A generic inverse association must be used if it is necessary to encode
a reverse link to a feature instance.
Distinction:

Inclusion Type
IHO Definition: INCLUSION TYPE Association class specifying the relationship between the subset of vessels
described by an Applicability data object and a regulation (restriction, recommendation, or nautical information).

S-122 Information Type: Inclusion Type

Primitives:None

Real World Paper Chart Symbol ECDIS Symbol

S-57 Allowable Encoding

S-122 Attribute Type Multiplicity
Acronym Value
Membership 1: included EN 0,1

2: excluded
Information associations
Type Association Name Class Role Mult Class Role Mult
Assoc InclusionType InclusionType theApplicabl 1..1 Applicability isApplicableT 1..1
(association class) eRxN o
Assoc InclusionType InclusionType isApplicable 1..1 Subtypes of theApplicable 1..1
(association class) To AbstractRxN RxN

INT 1 Reference:
Remarks:
The GML format implements and uses association classes in accordance with ISO 19136-2. The association
class is implemented as an information type instance with information associations to and from the two classes
linked by the association, as listed above. A generic inverse association must be used if it is necessary to encode
a reverse link to a feature instance.
Distinction:

Geo Feature Attribute and Enumerate Descriptions

[See the Simple attributes and Complex attributes sections in Appendix C – Feature
Catalogue.]

Associations
Association names
[See the Information Associations and Feature Associations section in Appendix C – feature
Catalogue.]
Association Roles
[See the Roles sections in Appendix C – Feature Catalogue.]

S-122 Appendix A January 2019 Edition 1.0.0

 70 Data Classification and Encoding Guide

Meta Feature and Spatial Attribute and Enumerate Descriptions

[See the Simple attributes and Complex attributes sections Appendix C – Feature Catalogue.]

Complex Attributes
[See the Complex attributes section in Appendix C – Feature Catalogue.]

ECDIS System (Portrayal) Attributes

ECDIS System (Portrayal) Attributes derived from S-101 (version 1.0)
Portrayal attributes are not used in this edition of S-122 Marine Protected Areas Product
Specification.

Updating (see S-4 – B-600)

Update datasets are described in the main S-122 product specification.

S-122 Appendix A January 2019 Edition 1.0.0