IHO Nautical Information Processing Working Group - User contributions [en]

Main Page

2024-06-23T23:55:57Z

Rmm:

This wiki is being used to support NIPWG work, including project teams and task groups. Non NIPWG members e.g. other IHO working group members, marine experts, OEM personnel may contribute to this Wiki if authorised by the NIPWG Chair or Vice Chair.

'''You must be registered and logged in to edit pages. You may apply for an account by sending email to the NIPWG Chair requesting an account and including your preferred user name.''' User names should be three or more letters and numbers, beginning with a letter, and conform to the requirements described for [https://www.mediawiki.org/wiki/Account_creation_user_experience/Usernames Mediawiki usernames]. Having received the login details, it is strongly recommended to provide contact details at your user page; refer to [[Special:Listusers|users list pages]] where your account is listed.

The following product specifications are under the remit of NIPWG:

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0"
!ProdSpec number and link to IHO registry (if available)!!Abstract!!Scope!!Link to Product Specification specific discussion page!!Best practices for data production
|-
|[https://registry.iho.int/document/list.do?product_ID=S-122 S-122](Marine Protected Area)||A Marine Protected Area (MPA) is a protected area whose boundaries include an area of the ocean. They include areas of the intertidal or sub-tidal terrain, together with their overlying water and associated flora, fauna, historical and cultural features, which have been reserved by law or other effective means to protect part or all of, the enclosed environment. For example, MPAs may be established to protect fish species, rare habitat area, or entire ecosystems.
MPAs can range from, simple declarations to protect a resource, to areas that are extensively regulated. The degree to which environmental regulations affect shipping varies according to whether MPAs are located in territorial waters, exclusive economic zones, or high seas. These limits are regulated by the law of the sea. Most MPAs are located in the territorial waters of coastal states, where enforcement can be ensured. MPAs can also however be established in a state's exclusive economic zone and even within international waters. For example in 1999, Italy, France and Monaco jointly established a cetacean sanctuary in the Ligurian Sea named the Pelagos Sanctuary for Mediterranean Marine Mammals. This sanctuary includes both national and international waters.
||Datasets conforming to this specification will contain all relevant MPA information for the area of coverage. Additionally there will be relevant metadata data quality, production authority, data sources and publication date.
||[[NIPWG_S-122_marine_protected_areas|Marine Protected Areas discussions]]
||[[S-122_MPA_Best_Practices|Experiences and best practices discussion]]
|-
|[https://registry.iho.int/document/list.do?product_ID=S-123# S-123 1.0.0] (Marine Radio Services)||Radio services describe the availability and reliability of radio stations and services offering navigational warnings and weather forecasts. This includes their service areas, services offered and instructions for contacting or utilizing these services.
||Datasets conforming to this specification will contain all relevant maritime radio service information for the area of coverage. Additionally, there will be relevant metadata data quality, production authority, data sources and publication date.
||[[http://wp12183585.server-he.de/npubwiki/wiki/index.php/NIPWG_S-123_marine_radio_services Marine Radio Services discussions]]
||[[S-123_MRS_Best_Practices|Experiences and best practices discussion]]
|-
|S-125 (Marine Aids to Navigation)|| Product specification is under development by IALA on behalf of NIPWG||Product specification is under development by IALA on behalf of NIPWG
||[[NIPWG_S-125_marine_aids_to_navigation|Marine Aids to Navigation discussions]]
||[[S-125_Marine_AToN_Best_Practices|Experiences and best practices discussion]]
|-
|S-126 (Marine Physical Environment)||The Marine Physical Environment Product Specification provides historical information on the climate of an area, specifically the weather conditions (temperature, pressure, humidity, etc.) or oceanic phenomenon (currents, sea levels, water characteristics, etc.), of a region.
Functionally, it is expected to aid in the identification of landmarks, entrances, hazards, and points of interest along a marked path – enriching the visuals shown on the nautical chart, as well as to help in decision making on how (and when) best to approach the desired port.
The product specification contains the information used to understand both the dynamic environmental conditions that surround the mariner but also descriptions of the environment that cannot be rendered on a 2D chart without cognitive overload from symbols and chart clutter. It is also intended to aid the user in filtering and presenting the data only when necessary.
The primary users would be the ship itself and the shipping company to use historical data for voyage planning (route, navigation safety, etc.) and to familiarize themselves with an area before entry. Secondary users would be academia and other researchers.
The expected functionality would be Route Planning Mode (planning) use.
||The overall scope of the specification (at the historical level) can be two-fold
1. Wide area—Covers ocean basin or other geographic feature.
2. Small area—Covers individual ports.
||[[http://wp12183585.server-he.de/npubwiki/wiki/index.php/NIPWG_S-126_envrm_cndtn Physical Environment discussions]]
|| None as yet
|-
|[https://registry.iho.int/document/list.do?product_ID=S-127 S-127] (Marine Traffic Management)||Marine Traffic Management (MTM) datasets describe the availability and reliability of vessel traffic services, pilotage, routing measures, and ship reporting systems. This includes their service areas, services offered, and instructions for contacting or utilizing these services. MTM is intended to be a supplement to ENC, and therefore does not describe the geographic information in detail equal to ENC, rather it is shown as a simplified geometry to indicate location, and to be a means of geolocating more regulatory information than the typical ENC.||Datasets conforming to this specification will contain all relevant MTM information for the area of coverage. Additionally, there will be relevant metadata data quality, production authority, data sources, and publication date.
||[[http://wp12183585.server-he.de/npubwiki/wiki/index.php/NIPWG_S-127_traffic_management_discussions Traffic Management Discussions]]
||[[S-127_MTM_Best_Practices|Experiences and best practices discussion]]
|-
|[https://registry.iho.int/productspec/view.do?idx=192&product_ID=S-128 S-128] (Catalogue of Nautical Products)||Catalogue of Nautical Products (CNP) datasets describe the availability and reliability of paper chart, ENC, S-100 based nautical products, application for navigational purpose, online service and e-Navigation services. This includes their issue date, publication status, producing agency, source indication. CNP is intended to exchange status of nautical products and to be a supplement to ENC, and therefore does not describe the geographic information in detail equal to ENC, rather it is shown as a coverage of nautical products.||Datasets conforming to this specification will contain catalogue of all relevant nautical products information for the area of coverage such as paper chart, ENC, Nautical publication, S-100 based nautical products and e-Navigation services.
||[[NIPWG_S-128_catalogue_of_nautical_products|Catalogue of Nautical Products discussions]]
||[[S-128_CNP_Best_Practices|Experiences and best practices discussion]]
|-
|[https://registry.iho.int/testbed/view.do?idx=193&product_ID=S-131 S-131] (Marine Harbour Infrastructure)||The Marine Harbour Infrastructure product intended use is to raise situational awareness before approaching a harbour.
Knowing a priori the layout of the berths as well as the services offered for berthing procedure and alongside is important in the berth-to-berth route planning process for an efficient harbour call.
Knowing all the services they need while at port are available and accessible as well as having a smooth transition into their berthing position.
The data will be able to be filtered according to needs to help reduce the cognitive burden on the mariner and presented in a way that is compact, organised and easily accessible.
This information is also useful for shipping companies, brokers and other in the industry to optimize their planning.
||The Marine Harbour Infrastructure describes relevant and data on harbour infrastructure, facilities and services in a harmonised form.
The main source of the data is information from harbour masters.
||[[http://wp12183585.server-he.de/npubwiki/wiki/index.php/NIPWG_S-1xx_hrb_infrstrctr Harbour Infrastructure discussions]]
||[[S-131_MHI_Best_Practices|Experiences and best practices discussion]]
|}

'''''The main functions of the wiki will be explained at the [[Help:Contents|Help pages.]] '''''

S-131 MHI Best Practices

2024-06-20T00:43:30Z

Rmm:

== Limitation by Vessels Characteristics and Cargo ==
(Source - S-131 Edition 1.0.0 DCEG)

=== Capturing the application of a regulation, recommendation, etc. to specified kinds of vessels ===
This will generally be modeled by an InclusionType relationship between the abstract supertype AbstractRxN (as the superclass for Regulations, Restrictions, Recommendations, and NauticalInformation information type classes) and the Applicability class.

[[File:S131_12_4.png|center|Typical modeling for application of regulation, etc. to vessels specified by dimensions, cargo, etc.]]

Encoders may find it easiest to capture the application of a regulation (recommendation , etc.) to a class or set of vessels in three phases:
# Encode the operative part of the regulation (the part that describes what the vessels subject to the regulation must or must not do), creating an instance of Regulations (or Recommendations, etc., as appropriate). Descriptions of what kinds of vessels are subject to the regulation must be excluded from the content of the Regulation instance.
# Create an Applicability information type and encode the description of what kinds of vessels are subject to (or exempted from) the regulation.
# Link the two using an InclusionType with membership=included if the vessels described by Applicability are subject to the regulation, or membership=excluded if they are explicitly exempted from the regulation.
It is not necessary to create separate instances of the regulation for inclusion and exclusion.

=== Capturing the permissibility or otherwise of a geographic feature for specified kinds of vessels ===
Encoders may find it easiest to capture the permissibility of a feature to specified kinds of vessels in three phases.
# Create the geographic feature if it does not already exist.
# Create an Applicability information type and encode the description of what kinds of vessels are required to use the geographic feature.
# Link the two using a PemissionType with categoryOfRelationship = required.
For the other relationships (prohibited, not recommended, etc.) steps 2 and 3 should be modified accordingly (i.e., if use by certain kinds of vessels is “not recommended” encode the description of that kind of vessels in an Applicability and create a linking PermissionType with categoryOfRelationship = not recommended).
It is not necessary to create a separate instance of the geographic feature for each type of relationship.

=== Constructing the Applicability information type ===
Where the source material describes complex conditions, encoders may find it useful to write out the conditions in structured language with grouping parentheses, for example, as “(condition A) AND (condition B) AND (condition C)”, or draw diagrams, before encoding Applicability and its associations.

Note that the model limitation on mixing logical connectives means some forms of conditions which use “nesting” cannot be encoded in a single Applicability instance and multiple instances must be created.

EXAMPLE: The complex condition “(condition A) AND ((condition B) OR (condition C))” must be encoded as two Applicability instances, one with “(condition A) AND (condition B)” and the other with “(condition A) AND (condition C)”.

{| class="wikitable" style="margin:auto"
|+ Example of conversion of complex condition to multiple simple conditions
|-
! Complex condition !! Encode as
|-
| (condition A) AND ((condition B) OR (condition C))
| Applicability 1: (condition A) AND (condition B) Applicability 2: (condition A) AND (condition C)
|-
|}

Data producers may contact NIPWG with questions about encoding complex conditions.

As a last resort, conditions may be written as phrases in natural language and encoded in the information attribute. It is acceptable for an Applicability to have only the information attribute populated.

== Textual Regulations and Notes ==
(Source - S-131 Edition 1.0.0 DCEG)

=== Use of appropriate information type ===
The appropriate information type from Regulations, Restrictions, Recommendations, and NauticalInformation should be used depending on the nature of information to be encoded.
# Regulations 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.
# 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.
# Recommendations is intended for encoding suggestions, limitations, or preferred procedures that are not mandatory.
# NauticalInformation is intended for material that is largely informative in nature, of which does not fit into the category of regulation, recommendation, or restriction.

=== Content ===
The content of the regulation (or recommendation, restriction, or note) should be encoded using the textContent attribute. Text content should be compact and accessible to the expected audience, and include pertinent information, in summary form if necessary. Generally, avoid including the entire text of regulations where it is complex in structure or unncessarily legalistic or verbose. Instead, condense long regulations or notes into a summary, include exceptions not covered by the summary, and include a reference where the full details can be obtained. References should be accessible to mariners, so they can obtain the complete text.

Textual content may be supplemented by one or more diagrams or sketches using the graphic attribute.

=== Classification ===
The classification attributes categoryOfRxN and actionOrActivity codelists in the rxnCode complex attribute should be populated wherever possible, in order to facilitate mariner identification of information relevant to particular route planning or navigation tasks.
# Being open enumeration codelists, these attributes allow for additional categories not listed among their standard values. For example, an “under repair” activity might be encoded in the actionOrActivity attribute (as “other: underRepair”).
# Note that such extra values will merely be displayed and not processed (for example, the user interface will not use extra values to choose symbols or filter instances of Regulations, whereas it may apply filters to the standard values and/or them in portrayal).

=== Titles and headlines ===
The headline attribute of rxNCode should be used to encode brief topic headings describing the textual content of the Regulations object. Topic headings in the source material may be suitable either as-is or being adapted for use in the intended application context (for example, being shortened for readability on an ECDIS screen or auxiliary display).
# The headline attribute of the textContent/information attribute may also be used to provide sub-heads but must not duplicate the content of rxNCode/headline.
# Where multiple headline attributes are encoded in the same instance of rxNCode complex attribute, they must be ordered as follows:
## If the headline values are derived from a source material (such as the published legal text of a government regulation), the ordering must conform to the hierarchy in the source, for example, section headings must precede sub-section headings. It is not necessary to include the entire hierarchy of headings for the portion that is actually encoded in the textContent co-attribute.
## If the headline values are not derived from a source text, the ordering should be from general to specific.

== Schedules ==

Operating schedules and business hours of organizations are encoded by associating a ServiceHours instance to an Authority. Partial work schedules on holidays or other special days are encoded by associating a NonstandardWorkingDay instance to the ServiceHours instance.

Similarly, operating schedules for a facility are encoded by associating a ServiceHours to the geographic feature instance representing the facility, and associating a NonstandardWorkingDay to the ServiceHours to encode partial working days.

To encode 26-hour operation, omit the times of day. Alternatively, midnight to midnight can be encoded (00:00:00 to 24:00:00).

Seasonal variations in service hours can be encoded using multiple Service Hours instances with appropriate periodicDateRange values.

If the schedule is complex, it may help to put in tabular form before attempting to encode it. The following tabular structure is suggested - encoders may adapt it as convenient.

{| class="wikitable" style="margin:auto"
|-
!colspan=4|Normal operations
|-
! Operations !! Days !! Time !! Notes
|-
| Normal / closed / unmanned / other: ... || (Days of week) || (Times of day) || (additional information)
|-
| Normal || Mon || 11:00 to 15:00 || Banker's hours every Monday
|-
| Normal || Tue - Thu || 05:00 to 17:00 || ''(info for encoder - when dayOfWeekIsRange = true)''
|-
| Normal || Fri, Sun || 06:00 to 10:00 || ''(info for encoder - when dayOfWeekIsRange = false)''
|-
| ... || ... || ... || ...
|-
!colspan=4|Exceptions
|-
| || days of exceptional schedules (fixed and floating public holidays, etc.) || || (information about operation on specified special day)
|-
| || ... || || ...
|}

Simpler schedules may be expressible in phrases:
* Normal operation: (date range) DoW-DoW, hh:mm-hh:mm, (additional information/link)
* Exceptions: (fixed/variable dates), (additional information/link)

The S-131 DCEG contains an example, similar to the example below:

: '''ServiceHours'''
:: scheduleByDayOfWeek
::: categoryOfSchedule =1 (normal operation)
::: timeIntervalsByDayofWeek
:::: dayOfWeek =2(Monday), 4(Wednesday)
:::: dayOfWeekIsRange =0 (false)
::: timeIntervalsByDayofWeek
:::: dayOfWeek =5(Thursday), 7(Saturday)
:::: dayOfWeekIsRange =1 (true)
:::: timeOfDayStart = 08:00:00
:::: timeOfDayEnd = 16:00:00

: '''NonStandardWorkingDay'''
:: dateFixed = ''(December 26) as'' <kbd><gMonthDay>--12-26</gMonthDay></kbd>
:: dateVariable = "Last Monday in May" ''(without quotes)''
:: information.text = “By pre-arrangement” ''(without quotes)''

'''Interpretation''': A 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 available by pre-arrangement on the last Monday in May and the 26th of December of each year when they fall on days which would otherwise be normal working days.

== Contact Information ==

The ContactDetails information type provides several attributes for encoding different types of contact information.

The name of the contact (for example, the name of the agency, pilot service, office, etc.) should be encoded in the ''featureName'' attribute, which is inherited from InformationType.

To encode contact information in different languages, separate instances of ContactDetails may be created.

Contact information can be associated to an Authority or to any S-131 geographic feature.

{| class="wikitable" style="margin:auto"
|+ Associations to ContactDetails
|-
| Type to which ContactDetails is associated || Purpose of association || Association Name || Encoder Note
|-
| Authority information type || contact information for the authority || AuthorityContact || Use when providing contact data for an organization in general, not limited to any specific purpose (the organization may of course be limited to a particular activity, e.g., pilot services)
|-
| Any subtype of OrganizationContactArea (i.e., any geographic feature) || contact information particular to the service provided at a location || ServiceContact || Use when further information about the controlling authority is not available or if the contact is specific to the feature (e.g., where requests for a particular type of service should be submitted). As a feature/info association, this link will be encoded in the feature type and reference the ContactDetails instance.
|-
|}

== Meta features ==

The following meta-features are mandatory in S-131 Edition 1.0.0:
* DataCoverage
* QualityOfNonBathymetricData
* SoundingDatum
* VerticalDatumOfData

=== Data Coverage ===
DataCoverage expresses where the presence or absence of S-131 geographic features is asserted. Unlike S-101 datasets, there is no 'skin of the earth' principle in S-131 and there may be regions covered by a DataCoverage but where no geographic S-131 feature is present.

# There must be a minimum of one DataCoverage feature in a dataset.
# DataCoverage features must cover at least the total extent of all geographic features in the dataset.
# DataCoverage features in the same dataset must not overlap one another.
# If the cell must include distant areas that are not part of the port area, such areas will generally be excluded from the DataCoverage feature(s). However, consistent with rule (1) above, if a geographic feature outside the legal port area is included in the dataset (such as a remote anchorage or pilot boarding place), the DataCoverage must be extended (or another DataCoverage created) to include such remote features.
# Attributes:
#* The mandatory attribute maximumDisplayScale is used to indicate the largest intended viewing scale for the data.
#* The mandatory attribute minimumDisplayScale is used to indicate the smallest intended viewing scale for the data.
#* The values of maximum and minimum display scales should be harmonized with comparable base layer S-101 datasets. This serves to harmonize the loading strategy of S-131 port information with that for the underlying ENCs. However, use of the same values as S-101 datasets is not mandatory in S-131.
# Given that S-131 data will overlay ENC and possibly other datasets, the conditions described in the S-101 DCEG “Data Coverage” clause for displaying overscale warnings and setting the viewing scale may be overridden by interoperability constraints or the presence of higher-priority datasets. This should be addressed in the S-100 interoperability specification (note that as of June 2024, the interoperability does not include S-131 among its covered products).
# Typically, only a single DataCoverage feature should be used in a dataset. However, if the maximum display scale is different for discrete areas within a single MHI dataset, this must be indicated by encoding separate, non-overlapping DataCoverage features, each having a different value populated for maximumDisplayScale.
#* Avoid excessive use of multiple DataCoverage features having different values of maximumDisplayScale.
#* Where different values of maximumDisplayScale are used, this should be restricted only to data compiled in order to achieve the intended navigational purpose of the entire dataset.
#* Datasets must have the same value for minimumDisplayScale for all DataCoverage features in the dataset.
# Where a dataset consists of only one DataCoverage 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 DataCoverage.
# For any DataCoverage feature, maximum display scale < minimum display scale.
# S-131 does not use the NULL value, which is permitted in S-101 for minimumDisplayScale when maximumDisplayScale=10,000,000. An appropriate greater value may be used instead.

=== Quality of Non-Bathymetric Data ===
The meta feature QualityOfNonBathymetricData may be used to provide an indication of the overall uncertainty of position for all non-bathymetric features (in S-131, this is all geographic features).

Horizontal and vertical uncertainties that apply to the majority of features are encoded as attributes of one or more QualityOfNonBathymetricData features.

Cartographers should ensure that quality is indicated over the whole coverage, i.e., the spatial union of all QoBD features should be identical to the spatial union of all DataCoverage features in the dataset. (Typically, there would be one DataCoverage and one QualityOfNonBathymetricData feature, with the same extents.)

Exceptional horizontal and vertical uncertainties are encoded in a SpatialAccuracy information type associated to particular spatial primitives.

The attributes horizontalPositionUncertainty, horizontalDistanceUncertainty and horizontalPositionUncertainty apply to all positions within the extent of the Quality of Non-Bathymetric Data features. These attributes may not be bound to specific feature instances unless the binding is included in the feature catalogue and GML schema. Spatial uncertainty for individual geographic features may be indicated by associating a SpatialQuality information type to the spatial primitive(s) encoding the location or boundary for the individual feature instance.

=== Sounding Datum and Vertical Datum ===

There must be only one SoundingDatum feature in an S-131 dataset, providing the datum for all
depth values encoded in any feature. Given the relatively small extent of S-131 datasets and the
importance of uniform datums in the same port, it is not anticipated that depths in different features
will be referred to different datums; however, if this is the case in the sources, values must be
converted to the same datum before encoding in the dataset.

There must be only one VerticalDatumOfData feature in an S-131 dataset, providing the datum for
all elevation values encoded in any feature. Given the relatively small extent of S-131 datasets and
the importance of uniform datums in the same port, it is not anticipated that elevations in different
features will be referred to different datums; however, if this is the case in the sources, values must
be converted to the same datum before encoding in the dataset.

== Feature Names ==

All area and point features within an MHI product should be encoded using the attribute featureName, if a name is available.

See the S-131 DCEG for more details about feature names.

The modeling and interpretation of featureName attributes has changed significantly in the current (June 2024) S-101 (ENC) specification and S-98 Annex C, after S-131 Edition 1.0.0 was published in 2023. However, the S-131 Edition 1.0.0 encoding and interpretation remain as described in S-131 Edition 1.0.0 until IHO release a revised edition of S-131. Given the significance of feature names in datasets, data producers:
* should populate feature names in S-131 1.0.0 datasets, where names are reasonably expected, e.g., berth numbers,
* should populate the language attribute of featureName (unless it is a "universal" name, such as a berth number), and
* should not encode multiple featureNames in the same language for a single feature of info type instance.

== Text Placement ==

See the S-131 DCEG for more details about the use of text placement.

The modeling and interpretation of text placment has changed significantly in the S-101 (ENC) specification and S-98 Annex C after S-131 Edition 1.0.0 was published in 2023. However, the S-131 Edition 1.0.0 encoding and interpretation remain as described in S-131 Edition 1.0.0 until IHO release a revised edition of S-131. To avoid the need for implementation efforts in different directions at this point of time, it is recommended that data producers
* avoid the use of TextPlacement in S-131 Edition 1.0.0 datasets.

S-131 MHI Best Practices

2024-06-20T00:41:27Z

Rmm: meta features, names, and text placement

== Limitation by Vessels Characteristics and Cargo ==
(Source - S-131 Edition 1.0.0 DCEG)

=== Capturing the application of a regulation, recommendation, etc. to specified kinds of vessels ===
This will generally be modeled by an InclusionType relationship between the abstract supertype AbstractRxN (as the superclass for Regulations, Restrictions, Recommendations, and NauticalInformation information type classes) and the Applicability class.

[[File:S131_12_4.png|center|Typical modeling for application of regulation, etc. to vessels specified by dimensions, cargo, etc.]]

Encoders may find it easiest to capture the application of a regulation (recommendation , etc.) to a class or set of vessels in three phases:
# Encode the operative part of the regulation (the part that describes what the vessels subject to the regulation must or must not do), creating an instance of Regulations (or Recommendations, etc., as appropriate). Descriptions of what kinds of vessels are subject to the regulation must be excluded from the content of the Regulation instance.
# Create an Applicability information type and encode the description of what kinds of vessels are subject to (or exempted from) the regulation.
# Link the two using an InclusionType with membership=included if the vessels described by Applicability are subject to the regulation, or membership=excluded if they are explicitly exempted from the regulation.
It is not necessary to create separate instances of the regulation for inclusion and exclusion.

=== Capturing the permissibility or otherwise of a geographic feature for specified kinds of vessels ===
Encoders may find it easiest to capture the permissibility of a feature to specified kinds of vessels in three phases.
# Create the geographic feature if it does not already exist.
# Create an Applicability information type and encode the description of what kinds of vessels are required to use the geographic feature.
# Link the two using a PemissionType with categoryOfRelationship = required.
For the other relationships (prohibited, not recommended, etc.) steps 2 and 3 should be modified accordingly (i.e., if use by certain kinds of vessels is “not recommended” encode the description of that kind of vessels in an Applicability and create a linking PermissionType with categoryOfRelationship = not recommended).
It is not necessary to create a separate instance of the geographic feature for each type of relationship.

=== Constructing the Applicability information type ===
Where the source material describes complex conditions, encoders may find it useful to write out the conditions in structured language with grouping parentheses, for example, as “(condition A) AND (condition B) AND (condition C)”, or draw diagrams, before encoding Applicability and its associations.

Note that the model limitation on mixing logical connectives means some forms of conditions which use “nesting” cannot be encoded in a single Applicability instance and multiple instances must be created.

EXAMPLE: The complex condition “(condition A) AND ((condition B) OR (condition C))” must be encoded as two Applicability instances, one with “(condition A) AND (condition B)” and the other with “(condition A) AND (condition C)”.

{| class="wikitable" style="margin:auto"
|+ Example of conversion of complex condition to multiple simple conditions
|-
! Complex condition !! Encode as
|-
| (condition A) AND ((condition B) OR (condition C))
| Applicability 1: (condition A) AND (condition B) Applicability 2: (condition A) AND (condition C)
|-
|}

Data producers may contact NIPWG with questions about encoding complex conditions.

As a last resort, conditions may be written as phrases in natural language and encoded in the information attribute. It is acceptable for an Applicability to have only the information attribute populated.

== Textual Regulations and Notes ==
(Source - S-131 Edition 1.0.0 DCEG)

=== Use of appropriate information type ===
The appropriate information type from Regulations, Restrictions, Recommendations, and NauticalInformation should be used depending on the nature of information to be encoded.
# Regulations 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.
# 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.
# Recommendations is intended for encoding suggestions, limitations, or preferred procedures that are not mandatory.
# NauticalInformation is intended for material that is largely informative in nature, of which does not fit into the category of regulation, recommendation, or restriction.

=== Content ===
The content of the regulation (or recommendation, restriction, or note) should be encoded using the textContent attribute. Text content should be compact and accessible to the expected audience, and include pertinent information, in summary form if necessary. Generally, avoid including the entire text of regulations where it is complex in structure or unncessarily legalistic or verbose. Instead, condense long regulations or notes into a summary, include exceptions not covered by the summary, and include a reference where the full details can be obtained. References should be accessible to mariners, so they can obtain the complete text.

Textual content may be supplemented by one or more diagrams or sketches using the graphic attribute.

=== Classification ===
The classification attributes categoryOfRxN and actionOrActivity codelists in the rxnCode complex attribute should be populated wherever possible, in order to facilitate mariner identification of information relevant to particular route planning or navigation tasks.
# Being open enumeration codelists, these attributes allow for additional categories not listed among their standard values. For example, an “under repair” activity might be encoded in the actionOrActivity attribute (as “other: underRepair”).
# Note that such extra values will merely be displayed and not processed (for example, the user interface will not use extra values to choose symbols or filter instances of Regulations, whereas it may apply filters to the standard values and/or them in portrayal).

=== Titles and headlines ===
The headline attribute of rxNCode should be used to encode brief topic headings describing the textual content of the Regulations object. Topic headings in the source material may be suitable either as-is or being adapted for use in the intended application context (for example, being shortened for readability on an ECDIS screen or auxiliary display).
# The headline attribute of the textContent/information attribute may also be used to provide sub-heads but must not duplicate the content of rxNCode/headline.
# Where multiple headline attributes are encoded in the same instance of rxNCode complex attribute, they must be ordered as follows:
## If the headline values are derived from a source material (such as the published legal text of a government regulation), the ordering must conform to the hierarchy in the source, for example, section headings must precede sub-section headings. It is not necessary to include the entire hierarchy of headings for the portion that is actually encoded in the textContent co-attribute.
## If the headline values are not derived from a source text, the ordering should be from general to specific.

== Schedules ==

Operating schedules and business hours of organizations are encoded by associating a ServiceHours instance to an Authority. Partial work schedules on holidays or other special days are encoded by associating a NonstandardWorkingDay instance to the ServiceHours instance.

Similarly, operating schedules for a facility are encoded by associating a ServiceHours to the geographic feature instance representing the facility, and associating a NonstandardWorkingDay to the ServiceHours to encode partial working days.

To encode 26-hour operation, omit the times of day. Alternatively, midnight to midnight can be encoded (00:00:00 to 24:00:00).

Seasonal variations in service hours can be encoded using multiple Service Hours instances with appropriate periodicDateRange values.

If the schedule is complex, it may help to put in tabular form before attempting to encode it. The following tabular structure is suggested - encoders may adapt it as convenient.

{| class="wikitable" style="margin:auto"
|-
!colspan=4|Normal operations
|-
! Operations !! Days !! Time !! Notes
|-
| Normal / closed / unmanned / other: ... || (Days of week) || (Times of day) || (additional information)
|-
| Normal || Mon || 11:00 to 15:00 || Banker's hours every Monday
|-
| Normal || Tue - Thu || 05:00 to 17:00 || ''(info for encoder - when dayOfWeekIsRange = true)''
|-
| Normal || Fri, Sun || 06:00 to 10:00 || ''(info for encoder - when dayOfWeekIsRange = false)''
|-
| ... || ... || ... || ...
|-
!colspan=4|Exceptions
|-
| || days of exceptional schedules (fixed and floating public holidays, etc.) || || (information about operation on specified special day)
|-
| || ... || || ...
|}

Simpler schedules may be expressible in phrases:
* Normal operation: (date range) DoW-DoW, hh:mm-hh:mm, (additional information/link)
* Exceptions: (fixed/variable dates), (additional information/link)

The S-131 DCEG contains an example, similar to the example below:

: '''ServiceHours'''
:: scheduleByDayOfWeek
::: categoryOfSchedule =1 (normal operation)
::: timeIntervalsByDayofWeek
:::: dayOfWeek =2(Monday), 4(Wednesday)
:::: dayOfWeekIsRange =0 (false)
::: timeIntervalsByDayofWeek
:::: dayOfWeek =5(Thursday), 7(Saturday)
:::: dayOfWeekIsRange =1 (true)
:::: timeOfDayStart = 08:00:00
:::: timeOfDayEnd = 16:00:00

: '''NonStandardWorkingDay'''
:: dateFixed = ''(December 26) as'' <kbd><gMonthDay>--12-26</gMonthDay></kbd>
:: dateVariable = "Last Monday in May" ''(without quotes)''
:: information.text = “By pre-arrangement” ''(without quotes)''

'''Interpretation''': A 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 available by pre-arrangement on the last Monday in May and the 26th of December of each year when they fall on days which would otherwise be normal working days.

== Contact Information ==

The ContactDetails information type provides several attributes for encoding different types of contact information.

The name of the contact (for example, the name of the agency, pilot service, office, etc.) should be encoded in the ''featureName'' attribute, which is inherited from InformationType.

To encode contact information in different languages, separate instances of ContactDetails may be created.

Contact information can be associated to an Authority or to any S-131 geographic feature.

{| class="wikitable" style="margin:auto"
|+ Associations to ContactDetails
|-
| Type to which ContactDetails is associated || Purpose of association || Association Name || Encoder Note
|-
| Authority information type || contact information for the authority || AuthorityContact || Use when providing contact data for an organization in general, not limited to any specific purpose (the organization may of course be limited to a particular activity, e.g., pilot services)
|-
| Any subtype of OrganizationContactArea (i.e., any geographic feature) || contact information particular to the service provided at a location || ServiceContact || Use when further information about the controlling authority is not available or if the contact is specific to the feature (e.g., where requests for a particular type of service should be submitted). As a feature/info association, this link will be encoded in the feature type and reference the ContactDetails instance.
|-
|}

== Meta features ==

The following meta-features are mandatory in S-131 Edition 1.0.0:
* DataCoverage
* QualityOfNonBathymetricData
* SoundingDatum
* VerticalDatumOfData

=== Data Coverage ===
DataCoverage expresses where the presence or absence of S-131 geographic features is asserted. Unlike S-101 datasets, there is no 'skin of the earth' principle in S-131 and there may be regions covered by a DataCoverage but where no geographic S-131 feature is present.

# There must be a minimum of one DataCoverage feature in a dataset.
# DataCoverage features must cover at least the total extent of all geographic features in the dataset.
# DataCoverage features in the same dataset must not overlap one another.
# If the cell must include distant areas that are not part of the port area, such areas will generally be excluded from the DataCoverage feature(s). However, consistent with rule (1) above, if a geographic feature outside the legal port area is included in the dataset (such as a remote anchorage or pilot boarding place), the DataCoverage must be extended (or another DataCoverage created) to include such remote features.
# Attributes:
#* The mandatory attribute maximumDisplayScale is used to indicate the largest intended viewing scale for the data.
#* The mandatory attribute minimumDisplayScale is used to indicate the smallest intended viewing scale for the data.
#* The values of maximum and minimum display scales should be harmonized with comparable base layer S-101 datasets. This serves to harmonize the loading strategy of S-131 port information with that for the underlying ENCs. However, use of the same values as S-101 datasets is not mandatory in S-131.
# Given that S-131 data will overlay ENC and possibly other datasets, the conditions described in the S-101 DCEG “Data Coverage” clause for displaying overscale warnings and setting the viewing scale may be overridden by interoperability constraints or the presence of higher-priority datasets. This should be addressed in the S-100 interoperability specification (note that as of June 2024, the interoperability does not include S-131 among its covered products).
# Typically, only a single DataCoverage feature should be used in a dataset. However, if the maximum display scale is different for discrete areas within a single MHI dataset, this must be indicated by encoding separate, non-overlapping DataCoverage features, each having a different value populated for maximumDisplayScale.
#* Avoid excessive use of multiple DataCoverage features having different values of maximumDisplayScale.
#* Where different values of maximumDisplayScale are used, this should be restricted only to data compiled in order to achieve the intended navigational purpose of the entire dataset.
#* Datasets must have the same value for minimumDisplayScale for all DataCoverage features in the dataset.
# Where a dataset consists of only one DataCoverage 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 DataCoverage.
# For any DataCoverage feature, maximum display scale < minimum display scale.
# S-131 does not use the NULL value, which is permitted in S-101 for minimumDisplayScale when maximumDisplayScale=10,000,000. An appropriate greater value may be used instead.

=== Quality of Non-Bathymetric Data ===
The meta feature QualityOfNonBathymetricData may be used to provide an indication of the overall uncertainty of position for all non-bathymetric features (in S-131, this is all geographic features).

Horizontal and vertical uncertainties that apply to the majority of features are encoded as attributes of one or more QualityOfNonBathymetricData features.

Cartographers should ensure that quality is indicated over the whole coverage, i.e., the spatial union of all QoBD features should be identical to the spatial union of all DataCoverage features in the dataset. (Typically, there would be one DataCoverage and one QualityOfNonBathymetricData feature, with the same extents.)

Exceptional horizontal and vertical uncertainties are encoded in a SpatialAccuracy information type associated to particular spatial primitives.

The attributes horizontalPositionUncertainty, horizontalDistanceUncertainty and horizontalPositionUncertainty apply to all positions within the extent of the Quality of Non-Bathymetric Data features. These attributes may not be bound to specific feature instances unless the binding is included in the feature catalogue and GML schema. Spatial uncertainty for individual geographic features may be indicated by associating a SpatialQuality information type to the spatial primitive(s) encoding the location or boundary for the individual feature instance.

=== Sounding Datum and Vertical Datum ===

There must be only one SoundingDatum feature in an S-131 dataset, providing the datum for all
depth values encoded in any feature. Given the relatively small extent of S-131 datasets and the
importance of uniform datums in the same port, it is not anticipated that depths in different features
will be referred to different datums; however, if this is the case in the sources, values must be
converted to the same datum before encoding in the dataset.

There must be only one VerticalDatumOfData feature in an S-131 dataset, providing the datum for
all elevation values encoded in any feature. Given the relatively small extent of S-131 datasets and
the importance of uniform datums in the same port, it is not anticipated that elevations in different
features will be referred to different datums; however, if this is the case in the sources, values must
be converted to the same datum before encoding in the dataset.

== Feature Names ==

All area and point features within an MHI product should be encoded using the attribute featureName, if a name is available.

See the S-131 DCEG for more details about feature names.

The modeling and interpretation of featureName attributes has changed significantly in the current (June 2024) S-101 (ENC) specification and S-98 Annex C, after S-131 Edition 1.0.0 was published in 2023. However, the S-131 Edition 1.0.0 encoding and interpretation remain as described in S-131 Edition 1.0.0 until IHO release a revised edition of S-131. Given the significance of feature names in datasets, data producers:
* should populate feature names in S-131 1.0.0 datasets, where names are reasonably expected, e.g., berth numbers,
* should populate the language attribute of featureName (unless it is a "universal" name, such as a berth number), and
* should not encode multiple featureNames in the same language for a single feature of info type instance.

== Text Placement ==

See the S-131 DCEG for more details about the use of text placement.

The modeling and interpretation of text placment has changed significantly in the S-101 (ENC) specification and S-98 Annex C after S-131 Edition 1.0.0 was published in 2023. However, the S-131 Ed.tion 1.0.0 encoding and interpretation remain as described in S-131 Edition 1.0.0 until IHO release a revised edition of S-131. To avoid the need for implementation efforts in different directions at this point of time, it is recommended that data producers
* avoid the use of TextPlacement in S-131 Edition 1.0.0 datasets.

S-131 MHI Best Practices

2024-06-19T23:25:23Z

Rmm: Contact information

Talk:S-131 MHI Best Practices

2024-06-19T22:49:00Z

Rmm: new page

== Purpose ==
This "discussion" page should be used for dicussions about the content of the MHI Best Practices page, for example:
* Clarifications and re-drafting of existing content.
* Additional topics which should also be addressed on the MHI Best Practices page.

S-131 MHI Best Practices

2024-06-18T07:13:00Z

Rmm: Schedules

S-131 MHI Best Practices

2024-06-18T00:17:06Z

Rmm: information about textual regulations and notes

Help:Contents

2024-01-18T22:13:48Z

Rmm:

Although I'm not a wiki expert and currently I'm not intending to become one, pls find below some helpful information for your convenience.
Have fun
Jens

=='''How do I edit a page?'''==
* This is the most important part. '''You have to use the edit link''' on top to modify the page content. The discussion tab works similar.
* To edit a page, simply click the edit link that appears on each page. A form will appear, containing the existing markup. When you have finished making modifications, click the Save button to commit your changes.

=='''How do I create a new page?'''==
* Create a link to the page on another page, then click on the red link which appears

=='''How do I create a link to a new page?'''==
* Embed the term you intend to be as a link in brackets like this <nowiki>[[link ]]</nowiki> or this <nowiki>[[link | Text ]]</nowiki>

=='''How do I mark terms or links in bold?'''==
* Either use the formatting button on top of the "edit" area or place three ' ' ' before and after the text or link.

=='''How do I combine links and bold?'''==
* Use following combination three <nowiki>' ' '</nowiki> followed by <nowiki>[[ and than close the area with the ]]</nowiki> followed by <nowiki>' ' '</nowiki>.
* The order of symbols is important, otherwise the result is not sufficient. However, use the edit link at each page and browse for further formatting examples.

=='''How do I upload the current version of the associated files?'''==
* Follow the link at bottom at the [[SNPWG]] page and replace the current version in the page which will appear when the link opens. Don't get nervous that it is called IMAGE; it is the folder where the uploads will be stored. An instruction is written at spreadsheet page in detail.

=='''That UML diagram is too small, how do I enlarge it?'''==
* The picture on the page may be a preview. Try clicking on the preview to enlarge it.
* If clicking on the image takes you to a "File:..." page with the same image still blurred, it may still be a preview though at a different resolution. Try clicking again or look for links below the preview on the "File:.." page linking to larger size versions.
* Still blurred? Your browser may be fitting it within the browser window. Try using whatever method your browser provides to display reduced-size images at full size.

=='''How do I create a time stamp associated with my sign in name'''==
* Add easily 4 ~ at the place underneath your comments or contributions.

=='''How do I create the confirmation table underneath each entry'''==
* Quit easy, copy and paste from other pages where the table exist or copy this at when being in edit mode

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
!David!!Ricardo!!Rolando!!Jens
|- style="background:white; color:black"
|DA Y/N
|RF Y/N
|RR Y/N
|JSF Y/N
|}

==''' How do I provide my contact details?'''==
* Simply refer to the users page link. You can find it on the right top of each page.

==''' Some more Wiki syntax'''==
* ''Italic text'' can be written by using the editing buttons on top or like <nowiki>' 'this' '</nowiki>.
* enumerated lists with one intentation like this

# item 1
## item
## item
# item 2
## item
## item

can be styled using one or two <nowiki># </nowiki>

* list style using dots like this

* item
** item
** item
** item
* item
** item

can be styled using one or two <nowiki>* </nowiki>

==''' Where can I find more information about navigation and editing?'''==
See the [https://www.mediawiki.org/wiki/Help:Contents MediaWiki help pages].

==''' Can I edit any page I want?'''==
Please do not edit the "Main Page", "FCD" and individual object type pages (the pages specifying the names and definitions or feature types, information types, and attributes) without prior arrangement. If you have comments on any of these pages, add them to the corresponding "discussions" pages (accessible via the "Discussion" tab on each page). If you start or resume a discussion, to facilitate timely responses, please also bring your discussion to the attention of the appropriate NIPWG members, who may not be monitoring the Wiki at that time.

If you have questions about whether you can or should edit any particular page on this Wiki, ask the NIPWG Chair and/or site maintainer.

=='''How to handle the sample dataset'''==
Important is to use '''only''' the current version of the file which can easily be found when clicking on the link. Don't wonder why it is headed with "Image:...". That is wiki syntax and will not be replaced by other terms. 
The text underneath the '''Warning''' can be amended by editing the page. The default setting is, that the text is a copy of the last comment in the file history section. As stated above, it can easily be amended. If intending to do some work please declare here that the file is under construction by you. That is important to avoid file conflicts. 
A click on the file file opens an external application, usually MS word, and the file can be edited. '''I strongly suggest to check "Track changes".''' It is an incredible help for other editors. 
When finished the work the file should be saved somewhere on your computer with a name at your choice. It is time to upload the next current version now. With a click a new window offers to browse for the file which will be the next current version. You see, it doesn't matter which name you have given to that file when saving it on your computer. The new version will get the wiki file name. The wiki needs only to know which file it should place. You should write a little comment stating what you have done in brief. 
After uploading the new version you can find the current version on top of the file history and your comment is now below the '''Warning''' section. That indicates to other that the file is not longer blocked. 
I hope it was of some help. Have fun. Jens

----

Help:Contents

2024-01-18T21:56:07Z

Rmm:

Although I'm not a wiki expert and currently I'm not intending to become one, pls find below some helpful information for your convenience.
Have fun
Jens

=='''How do I edit a page?'''==
* This is the most important part. '''You have to use the edit link''' on top to modify the page content. The discussion tab works similar.
* To edit a page, simply click the edit link that appears on each page. A form will appear, containing the existing markup. When you have finished making modifications, click the Save button to commit your changes.

=='''How do I create a new page?'''==
* Create a link to the page on another page, then click on the red link which appears

=='''How do I create a link to a new page?'''==
* Embed the term you intend to be as a link in brackets like this <nowiki>[[link ]]</nowiki> or this <nowiki>[[link | Text ]]</nowiki>

=='''How do I mark terms or links in bold?'''==
* Either use the formatting button on top of the "edit" area or place three ' ' ' before and after the text or link.

=='''How do I combine links and bold?'''==
* Use following combination three <nowiki>' ' '</nowiki> followed by <nowiki>[[ and than close the area with the ]]</nowiki> followed by <nowiki>' ' '</nowiki>.
* The order of symbols is important, otherwise the result is not sufficient. However, use the edit link at each page and browse for further formatting examples.

=='''How do I upload the current version of the associated files?'''==
* Follow the link at bottom at the [[SNPWG]] page and replace the current version in the page which will appear when the link opens. Don't get nervous that it is called IMAGE; it is the folder where the uploads will be stored. An instruction is written at spreadsheet page in detail.

=='''That UML diagram is too small, how do I enlarge it?'''==
* The picture on the page may be a preview. Try clicking on the preview to enlarge it.
* If clicking on the image takes you to a "File:..." page with the same image still blurred, it may still be a preview though at a different resolution. Try clicking again or look for links below the preview on the "File:.." page linking to larger size versions.

=='''How do I create a time stamp associated with my sign in name'''==
* Add easily 4 ~ at the place underneath your comments or contributions.

=='''How do I create the confirmation table underneath each entry'''==
* Quit easy, copy and paste from other pages where the table exist or copy this at when being in edit mode

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
!David!!Ricardo!!Rolando!!Jens
|- style="background:white; color:black"
|DA Y/N
|RF Y/N
|RR Y/N
|JSF Y/N
|}

==''' How do I provide my contact details?'''==
* Simply refer to the users page link. You can find it on the right top of each page.

==''' Some more Wiki syntax'''==
* ''Italic text'' can be written by using the editing buttons on top or like <nowiki>' 'this' '</nowiki>.
* enumerated lists with one intentation like this

# item 1
## item
## item
# item 2
## item
## item

can be styled using one or two <nowiki># </nowiki>

* list style using dots like this

* item
** item
** item
** item
* item
** item

can be styled using one or two <nowiki>* </nowiki>

==''' Where can I find more information about navigation and editing?'''==
See the [https://www.mediawiki.org/wiki/Help:Contents MediaWiki help pages].

==''' Can I edit any page I want?'''==
Please do not edit the "Main Page", "FCD" and individual object type pages (the pages specifying the names and definitions or feature types, information types, and attributes) without prior arrangement. If you have comments on any of these pages, add them to the corresponding "discussions" pages (accessible via the "Discussion" tab on each page). If you start or resume a discussion, to facilitate timely responses, please also bring your discussion to the attention of the appropriate NIPWG members, who may not be monitoring the Wiki at that time.

If you have questions about whether you can or should edit any particular page on this Wiki, ask the NIPWG Chair and/or site maintainer.

=='''How to handle the sample dataset'''==
Important is to use '''only''' the current version of the file which can easily be found when clicking on the link. Don't wonder why it is headed with "Image:...". That is wiki syntax and will not be replaced by other terms. 
The text underneath the '''Warning''' can be amended by editing the page. The default setting is, that the text is a copy of the last comment in the file history section. As stated above, it can easily be amended. If intending to do some work please declare here that the file is under construction by you. That is important to avoid file conflicts. 
A click on the file file opens an external application, usually MS word, and the file can be edited. '''I strongly suggest to check "Track changes".''' It is an incredible help for other editors. 
When finished the work the file should be saved somewhere on your computer with a name at your choice. It is time to upload the next current version now. With a click a new window offers to browse for the file which will be the next current version. You see, it doesn't matter which name you have given to that file when saving it on your computer. The new version will get the wiki file name. The wiki needs only to know which file it should place. You should write a little comment stating what you have done in brief. 
After uploading the new version you can find the current version on top of the file history and your comment is now below the '''Warning''' section. That indicates to other that the file is not longer blocked. 
I hope it was of some help. Have fun. Jens

----

NIPWG S-128 catalogue of nautical products

2024-01-18T21:39:52Z

Rmm:

'''Feedback'''

'''Diagrams'''

Class model (updated after 16 January VTC)
[[File:S-128_CLASS_v1.2.0.png|alt UML diagram of S-128 classes|thumb|upright|center|S-128 1.2.0 model (click to enlarge)]]

'''Other discussions'''

'''Meeting records'''
* VTC 01 [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG%20VTC%202023/NIPWG_2023_1st%20S-128%20Dedicated%20VTC_%20Minutes.docx Minutes]
* VTC 02 [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG%20VTC%202023/NIPWG_2023_2nd%20S-128%20Dedicated%20VTC_%20Minutes.pdf Minutes]

'''Summary of decisions'''

File:S-128 CLASS v1.2.0.png

2024-01-18T21:09:38Z

Rmm: 5th S-128 VTC

== Summary ==
5th S-128 VTC

File:Speed Restriction Sample.pdf

2023-12-06T04:19:18Z

Rmm:

File:S127TG Speed Limits Examples.pdf

2023-12-06T04:18:47Z

Rmm:

NIPWG S-127 traffic management discussions

2023-12-06T04:18:04Z

Rmm:

'''Marine Traffic Management Discussion'''

The following sources are available:

The [[File:Traffic_management_test_data-sample.docx|Traffic Management Test date sample]] maintained by Mike (NGA).

The [[File:Order on places of refuge and plans hereon.pdf|Danish Places of Refuge example]] provided by Allan (GS)T.

[[User:Rmm|raphael]] ([[User talk:Rmm|talk]]) 06:07, 10 August 2020 (CEST): A summary of the email discussion during May-July 2020 has been added in the Discussion tab.

'''Feedback on S-123 Marine Radio Services Edition 1.0.0'''

The following documents contain feedback received on S-123 1.0.0.
* Feedback template UNH [[Media:S-127-UNH-2022.docx|Link]]
* Combined comments [[Media:S-127_combined_comments.docx|Link]]
* Port services rename request [[Media:S-127_portServicesRenameRequest.pdf|Link]]
* Continued Expansion of Marine Traffic Management (S-127) Test Data Set [[Media:S-127-Expansion.docx|Link]]
* Proposals on Adding Hydrometeorological Conditions [[Media:Proposals_Adding_HydrometeorologicalConditions.docx|Link]] and comments on proposal [[Media:Comments_HydrometeorologicalConditions.docx|Link]]

'''Other Input to S-127 1.x discussions'''
* Speed restrictions in Gulf of St. Lawrence [[Media:S127_Input_CCG.pdf|CCG Paper]]
* Speed limit consolidation [[Media:Speed_Limit_Consolidation.pdf|NGA paper]], tabulated examples [[Media:S127TG_Speed_Limits_Examples.pdf|Tabulation as PDF file]]
* Speed restriction sample (GML printout) [[Media:Speed_Restriction_Sample.pdf|FI sample]]

'''Summary of decisions'''

Decisions and actions (as of June 7, 2023): [[Media:S-127_CombinedComments_Outcome.docx|Link]] (.docx file)

File:Speed Limit Consolidation.pdf

2023-12-06T04:14:35Z

Rmm:

NIPWG S-127 traffic management discussions

2023-12-06T04:14:12Z

Rmm:

'''Marine Traffic Management Discussion'''

The following sources are available:

The [[File:Traffic_management_test_data-sample.docx|Traffic Management Test date sample]] maintained by Mike (NGA).

The [[File:Order on places of refuge and plans hereon.pdf|Danish Places of Refuge example]] provided by Allan (GS)T.

[[User:Rmm|raphael]] ([[User talk:Rmm|talk]]) 06:07, 10 August 2020 (CEST): A summary of the email discussion during May-July 2020 has been added in the Discussion tab.

'''Feedback on S-123 Marine Radio Services Edition 1.0.0'''

The following documents contain feedback received on S-123 1.0.0.
* Feedback template UNH [[Media:S-127-UNH-2022.docx|Link]]
* Combined comments [[Media:S-127_combined_comments.docx|Link]]
* Port services rename request [[Media:S-127_portServicesRenameRequest.pdf|Link]]
* Continued Expansion of Marine Traffic Management (S-127) Test Data Set [[Media:S-127-Expansion.docx|Link]]
* Proposals on Adding Hydrometeorological Conditions [[Media:Proposals_Adding_HydrometeorologicalConditions.docx|Link]] and comments on proposal [[Media:Comments_HydrometeorologicalConditions.docx|Link]]

'''Other Input to S-127 1.x discussions'''
* Speed restrictions in Gulf of St. Lawrence [[Media:S127_Input_CCG.pdf|CCG Paper]]
* Speed limit consolidation [[Media:Speed_Limit_Consolidation.pdf|NGA paper]], tabulated examples [[Media:S127TG_Speed_Limits_Examples|Tabulation as PDF file]]
* Speed restriction sample (GML printout) [[Media:Speed_Restriction_Sample.pdf|FI sample]]

'''Summary of decisions'''

Decisions and actions (as of June 7, 2023): [[Media:S-127_CombinedComments_Outcome.docx|Link]] (.docx file)

File:S127 Input CCG.pdf

2023-12-06T04:11:20Z

Rmm:

NIPWG S-128 catalogue of nautical products

2023-12-06T03:52:30Z

Rmm:

'''Feedback'''

'''Diagrams'''

'''Other discussions'''

'''Meeting records'''
* VTC 01 [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG%20VTC%202023/NIPWG_2023_1st%20S-128%20Dedicated%20VTC_%20Minutes.docx Minutes]
* VTC 02 [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG%20VTC%202023/NIPWG_2023_2nd%20S-128%20Dedicated%20VTC_%20Minutes.pdf Minutes]

'''Summary of decisions'''

File:S123TG19 Nov-2023 Minutes.pdf

2023-12-06T03:44:35Z

Rmm: Draft

== Summary ==
Draft

NIPWG S-123 marine radio services

2023-12-06T03:44:07Z

Rmm:

This page is the work record of the NIPWG sub-working group for defining updates to S-123 (Marine Radio Services) Edition 1.0.0. It contains the collected feedback received on Edition 1.0.0 and the sub-WG's decisions about updates. Discussions about particular issues should take place on the discussion page (click the ''discussion'' tab at the top).

'''Feedback on S-123 Marine Radio Services Edition 1.0.0'''

The following documents contain feedback received on S-123 1.0.0.
*Cumulative list of comments received as of 2022-01-14: [http://wp12183585.server-he.de/npubwiki/wiki/images/9/9b/S-123_comment_list_cumulative.docx Comments list as of 2022-01-14] (.docx file)
*Proposal to add Tides and Water Flow Forecasting Services: [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG8/NIPWG8_2021_49.4%20%20Proposal%20to%20Add%20Tides%20and%20Water%20Flow%20Forecasting%20Services%20to%20the%20S-123.doc NIPWG8-49.4] (now merged into cumulative list)
*Report on Creation of Canadian S-123 datasets: [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG%20VTC%202021/NIPWG_VTC_2021_6-2-1_CCG%20Report%20on%20Feedback%20to%20S-123%20edition%201.0.0.pdf NIPWG VTC 2021-6.2.1], [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG8/NIPWG8_2021_49.2_EN_CCG%20Report%20on%20S-123%20data%20creation.docx NIPWG8-49.2] (now merged into the cumulative list)
*Maritime Assistance Services and Rescue Services: [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG%20VTC%202021/NIPWG_VTC_2021_6-2-2_DE_MAS_Rescue_Services_Considerations.pdf NIPWG VTC 2021-6.2.2] (now merged into the cumulative list)
*Report on creation of S-123 for German waters: [https://legacy.iho.int/mtg_docs/com_wg/NIPWG/NIPWG7/NIPWG7_2019_20.1b_EN_Creation%20of%20S-123%20for%20German%20waters.pdf NIPWG7-20.1b] (now merged into the cumulative list)

New feedback should be submitted to Elena Armanino or Bridget Gagné using the comments form (see the ''Cumulative list...'' link above). Addresses can be obtained from the NIPWG membership list on the IHO NIPWG page.

'''Diagrams''': [http://wp12183585.server-he.de/npubwiki/S123HTML/index.htm Link]

'''Other documents'''
* MRCC, Coast Guard Station, control center, radio station - Examples: [[:File:MRCC_CGStation_ControlCenter_RadioStation.docx|Link]]
* Complex attribute ''radiocommunications'' modeling issues: [[:File:RadiocommunicationsModelingIssues.docx|Link]]
* Response from UKHO about radio station types (circulated by email on April 26)
* Samples from Germany (May 6, 2022): [[:File:S123_NAVTEX.pdf|NAVTEX]], [[:File:S123_VTS_Warnemünde.pdf|VTS Warnemünde]]
* CCG RAMN Examples
** Maritime Mobile Safety and Communication Frequencies MF/HF Available at MCTS Centres [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part1-eng.html#tab11 Link]
** Maritime Mobile Safety and Communication Frequencies VHF [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part1-eng.html#tab12 Link]
** Example: Sydney MCTS Centre [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part2-eng.html#2111 Link]
*** List of associated radio stations and ship/shore communications [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part2-eng.html#tab223 Link]
*** List of broadcasts [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part2-eng.html#tab224 Link]
** Transmitting Sites where NAVTEX Service is Available [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part4-eng.html#tab414 Link]
** Weather and Forecast
*** Maritimes Region: Text Format [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part5-eng.html#tab542 Link]
*** Maritimes Region: NAVTEX Format [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part5-eng.html#tab543 Link]
** DGPS: St. Lawrence River and Atlantic Coast [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part4-eng.html#4281 Link]
** Example: Radio Facsimile Stations [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part5-eng.html#tab568 Link]
* ALRS examples
** Marine Radio Stations/GMDSS [[:File:Example_Marine_Radio_Stations.pdf | Link]];
** Radio Weather Services and Navigational Warnings (MSI); [[:File:Example_Radio_Weather_Services_and_Navigational_Warnings.pdf | Link]]
** service details retrieved from ITU's publication/database [[:File:Example_PENANG_RADIO_Document_08_05_2022.pdf | Link]], [[:File:Example_GUANGZHOU_RADIO_Document_08_05_2022_updated20170619.pdf|Link]]
** Format for AIS stations and DGNSS/DGPS radio beacons [[:File:Example_Automatic_Identification_System_(AIS)_and_Radio_Beacon_DGNSS.pdf | Link]]
* New definitions Areas A1 - A4 [[:File:New_definition_Areas_A1-A4.PNG | Link]]
* Halifax Coast Guard Radio [[:File:HALIFAX_COAST_GUARD_RADIO_Document_26_05_2022.pdf | Link]]
* ITU Canada CP notes [[:File:ITU_Canada_CP_notes.pdf | Link]]
* Sample data prepared by NIPWG for S-123 Edition 1.0.0: [[:File:NIPWG03_2016_26.1.1_EN_S-123_ProdSpec_Radio_Services_Sample_data_sets_v1.pdf|Link]]
* Radiocommunications remodeling - 1 [[:File:Radiocommunications_Remodeling_SJC.pdf|Link]]
* Radiocommunications remodeling - 2 [[:File:RadioServiceAreas-Examples-Remodeling-RM.pdf|Link]]
* NIPWG use case for overlapping data draft [[:File:NIPWG_use_case_for_overlapping_data_draft.docx|Link]] and [http://wp12183585.server-he.de/npubwiki/wiki/index.php/SNPWG2 Discussion space]
* GMDSS remodeling [[:File:GMDSS-Remodeling-1.pdf|Slide deck 1]], [[:File:GMDSS-Remodeling-2.pdf|Slide deck 2]]

'''Meeting records'''
* Minutes:
**Final minutes, December 8, 2021 VTC: [[Media:S123TG1_Dec-2021_Minutes_Final.pdf|Link]] (PDF file).
**Final minutes, January 19, 2022 VTC: [[Media:S123TG2_Jan-2022_Minutes_Final.pdf|Link]] (PDF file).
**Final minutes, February 15, 2022 VTC: [[Media:S123TG3_Feb-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, March 16, 2022 VTC: [[Media:S123TG4_Mar-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, April 19, 2022 VTC: [[Media:S123TG5_Apr-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, May 25, 2022 VTC: [[Media:S123TG6_May-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, June 15, 2022 VTC: [[Media:S123TG7_June-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, July 14, 2022 VTC: [[Media:S123TG8_July-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, August 4, 2022 VTC: [[Media:S123TG9_Aug-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, October 13, 2022 VTC: [[Media:S123TG10_Oct-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, November 8, 2022 VTC: [[Media:S123TG11_Nov-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, January 12, 2023 VTC: [[Media:S123TG12_Jan-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, February 9, 2023 VTC: [[Media:S123TG13_Feb-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, March 23, 2023 VTC: [[Media:S123TG14_Mar-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, May 25, 2023 VTC: [[Media:S123TG15_May-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, July 25, 2023 VTC: [[Media:S123TG16_July-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, August 24, 2023 VTC: [[Media:S123TG17_Aug-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, October 19, 2023 VTC: [[Media:S123TG18_Oct-2023_Minutes.pdf|Link]] (PDF file).
**Draft minutes, November 30, 2023 VTC: [[Media:S123TG19_Nov-2023_Minutes.pdf|Link]] (PDF file).

'''Summary of decisions'''

Decisions and actions (as of November 30, 2023): [[Media:Feedback_collected_S-123_TG-comments.docx|Link]] (.docx file)

File:S123TG18 Oct-2023 Minutes.pdf

2023-12-06T03:41:29Z

Rmm: Rmm uploaded a new version of File:S123TG18 Oct-2023 Minutes.pdf

== Summary ==
Draft

File:Feedback collected S-123 TG-comments.docx

2023-12-06T03:39:53Z

Rmm: Rmm uploaded a new version of File:Feedback collected S-123 TG-comments.docx

Most recent version of collected feedback with S-123 TG comments

File:S131 12 4.png

2023-12-06T03:35:55Z

Rmm:

S-131 MHI Best Practices

2023-12-06T03:35:02Z

Rmm: Limitation by vessel characteristics and cargo, Applicability

NIPWG S-123 marine radio services

2023-11-28T02:03:19Z

Rmm:

This page is the work record of the NIPWG sub-working group for defining updates to S-123 (Marine Radio Services) Edition 1.0.0. It contains the collected feedback received on Edition 1.0.0 and the sub-WG's decisions about updates. Discussions about particular issues should take place on the discussion page (click the ''discussion'' tab at the top).

'''Feedback on S-123 Marine Radio Services Edition 1.0.0'''

The following documents contain feedback received on S-123 1.0.0.
*Cumulative list of comments received as of 2022-01-14: [http://wp12183585.server-he.de/npubwiki/wiki/images/9/9b/S-123_comment_list_cumulative.docx Comments list as of 2022-01-14] (.docx file)
*Proposal to add Tides and Water Flow Forecasting Services: [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG8/NIPWG8_2021_49.4%20%20Proposal%20to%20Add%20Tides%20and%20Water%20Flow%20Forecasting%20Services%20to%20the%20S-123.doc NIPWG8-49.4] (now merged into cumulative list)
*Report on Creation of Canadian S-123 datasets: [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG%20VTC%202021/NIPWG_VTC_2021_6-2-1_CCG%20Report%20on%20Feedback%20to%20S-123%20edition%201.0.0.pdf NIPWG VTC 2021-6.2.1], [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG8/NIPWG8_2021_49.2_EN_CCG%20Report%20on%20S-123%20data%20creation.docx NIPWG8-49.2] (now merged into the cumulative list)
*Maritime Assistance Services and Rescue Services: [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG%20VTC%202021/NIPWG_VTC_2021_6-2-2_DE_MAS_Rescue_Services_Considerations.pdf NIPWG VTC 2021-6.2.2] (now merged into the cumulative list)
*Report on creation of S-123 for German waters: [https://legacy.iho.int/mtg_docs/com_wg/NIPWG/NIPWG7/NIPWG7_2019_20.1b_EN_Creation%20of%20S-123%20for%20German%20waters.pdf NIPWG7-20.1b] (now merged into the cumulative list)

New feedback should be submitted to Elena Armanino or Bridget Gagné using the comments form (see the ''Cumulative list...'' link above). Addresses can be obtained from the NIPWG membership list on the IHO NIPWG page.

'''Diagrams''': [http://wp12183585.server-he.de/npubwiki/S123HTML/index.htm Link]

'''Other documents'''
* MRCC, Coast Guard Station, control center, radio station - Examples: [[:File:MRCC_CGStation_ControlCenter_RadioStation.docx|Link]]
* Complex attribute ''radiocommunications'' modeling issues: [[:File:RadiocommunicationsModelingIssues.docx|Link]]
* Response from UKHO about radio station types (circulated by email on April 26)
* Samples from Germany (May 6, 2022): [[:File:S123_NAVTEX.pdf|NAVTEX]], [[:File:S123_VTS_Warnemünde.pdf|VTS Warnemünde]]
* CCG RAMN Examples
** Maritime Mobile Safety and Communication Frequencies MF/HF Available at MCTS Centres [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part1-eng.html#tab11 Link]
** Maritime Mobile Safety and Communication Frequencies VHF [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part1-eng.html#tab12 Link]
** Example: Sydney MCTS Centre [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part2-eng.html#2111 Link]
*** List of associated radio stations and ship/shore communications [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part2-eng.html#tab223 Link]
*** List of broadcasts [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part2-eng.html#tab224 Link]
** Transmitting Sites where NAVTEX Service is Available [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part4-eng.html#tab414 Link]
** Weather and Forecast
*** Maritimes Region: Text Format [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part5-eng.html#tab542 Link]
*** Maritimes Region: NAVTEX Format [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part5-eng.html#tab543 Link]
** DGPS: St. Lawrence River and Atlantic Coast [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part4-eng.html#4281 Link]
** Example: Radio Facsimile Stations [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part5-eng.html#tab568 Link]
* ALRS examples
** Marine Radio Stations/GMDSS [[:File:Example_Marine_Radio_Stations.pdf | Link]];
** Radio Weather Services and Navigational Warnings (MSI); [[:File:Example_Radio_Weather_Services_and_Navigational_Warnings.pdf | Link]]
** service details retrieved from ITU's publication/database [[:File:Example_PENANG_RADIO_Document_08_05_2022.pdf | Link]], [[:File:Example_GUANGZHOU_RADIO_Document_08_05_2022_updated20170619.pdf|Link]]
** Format for AIS stations and DGNSS/DGPS radio beacons [[:File:Example_Automatic_Identification_System_(AIS)_and_Radio_Beacon_DGNSS.pdf | Link]]
* New definitions Areas A1 - A4 [[:File:New_definition_Areas_A1-A4.PNG | Link]]
* Halifax Coast Guard Radio [[:File:HALIFAX_COAST_GUARD_RADIO_Document_26_05_2022.pdf | Link]]
* ITU Canada CP notes [[:File:ITU_Canada_CP_notes.pdf | Link]]
* Sample data prepared by NIPWG for S-123 Edition 1.0.0: [[:File:NIPWG03_2016_26.1.1_EN_S-123_ProdSpec_Radio_Services_Sample_data_sets_v1.pdf|Link]]
* Radiocommunications remodeling - 1 [[:File:Radiocommunications_Remodeling_SJC.pdf|Link]]
* Radiocommunications remodeling - 2 [[:File:RadioServiceAreas-Examples-Remodeling-RM.pdf|Link]]
* NIPWG use case for overlapping data draft [[:File:NIPWG_use_case_for_overlapping_data_draft.docx|Link]] and [http://wp12183585.server-he.de/npubwiki/wiki/index.php/SNPWG2 Discussion space]
* GMDSS remodeling [[:File:GMDSS-Remodeling-1.pdf|Slide deck 1]], [[:File:GMDSS-Remodeling-2.pdf|Slide deck 2]]

'''Meeting records'''
* Minutes:
**Final minutes, December 8, 2021 VTC: [[Media:S123TG1_Dec-2021_Minutes_Final.pdf|Link]] (PDF file).
**Final minutes, January 19, 2022 VTC: [[Media:S123TG2_Jan-2022_Minutes_Final.pdf|Link]] (PDF file).
**Final minutes, February 15, 2022 VTC: [[Media:S123TG3_Feb-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, March 16, 2022 VTC: [[Media:S123TG4_Mar-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, April 19, 2022 VTC: [[Media:S123TG5_Apr-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, May 25, 2022 VTC: [[Media:S123TG6_May-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, June 15, 2022 VTC: [[Media:S123TG7_June-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, July 14, 2022 VTC: [[Media:S123TG8_July-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, August 4, 2022 VTC: [[Media:S123TG9_Aug-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, October 13, 2022 VTC: [[Media:S123TG10_Oct-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, November 8, 2022 VTC: [[Media:S123TG11_Nov-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, January 12, 2023 VTC: [[Media:S123TG12_Jan-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, February 9, 2023 VTC: [[Media:S123TG13_Feb-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, March 23, 2023 VTC: [[Media:S123TG14_Mar-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, May 25, 2023 VTC: [[Media:S123TG15_May-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, July 25, 2023 VTC: [[Media:S123TG16_July-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, August 24, 2023 VTC: [[Media:S123TG17_Aug-2023_Minutes.pdf|Link]] (PDF file).
**Draft minutes, October 19, 2023 VTC: [[Media:S123TG18_Oct-2023_Minutes.pdf|Link]] (PDF file).

'''Summary of decisions'''

Decisions and actions (as of October 19, 2023): [[Media:Feedback_collected_S-123_TG-comments.docx|Link]] (.docx file)

File:S123TG18 Oct-2023 Minutes.pdf

2023-11-28T02:01:14Z

Rmm: Draft

== Summary ==
Draft

File:S123TG17 Aug-2023 Minutes.pdf

2023-11-28T02:00:37Z

Rmm: Rmm uploaded a new version of File:S123TG17 Aug-2023 Minutes.pdf

== Summary ==
Draft

File:Feedback collected S-123 TG-comments.docx

2023-11-28T01:59:31Z

Rmm: Rmm uploaded a new version of File:Feedback collected S-123 TG-comments.docx

Most recent version of collected feedback with S-123 TG comments

File:Feedback collected S-123 TG-comments.docx

2023-10-16T05:52:37Z

Rmm: Rmm uploaded a new version of File:Feedback collected S-123 TG-comments.docx

Most recent version of collected feedback with S-123 TG comments

File:S123TG17 Aug-2023 Minutes.pdf

2023-10-16T05:50:29Z

Rmm: Draft

== Summary ==
Draft

File:S123TG16 July-2023 Minutes.pdf

2023-10-16T05:49:04Z

Rmm: Rmm uploaded a new version of File:S123TG16 July-2023 Minutes.pdf

== Summary ==
Draft minutes

NIPWG S-123 marine radio services

2023-10-16T05:46:13Z

Rmm:

This page is the work record of the NIPWG sub-working group for defining updates to S-123 (Marine Radio Services) Edition 1.0.0. It contains the collected feedback received on Edition 1.0.0 and the sub-WG's decisions about updates. Discussions about particular issues should take place on the discussion page (click the ''discussion'' tab at the top).

'''Feedback on S-123 Marine Radio Services Edition 1.0.0'''

The following documents contain feedback received on S-123 1.0.0.
*Cumulative list of comments received as of 2022-01-14: [http://wp12183585.server-he.de/npubwiki/wiki/images/9/9b/S-123_comment_list_cumulative.docx Comments list as of 2022-01-14] (.docx file)
*Proposal to add Tides and Water Flow Forecasting Services: [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG8/NIPWG8_2021_49.4%20%20Proposal%20to%20Add%20Tides%20and%20Water%20Flow%20Forecasting%20Services%20to%20the%20S-123.doc NIPWG8-49.4] (now merged into cumulative list)
*Report on Creation of Canadian S-123 datasets: [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG%20VTC%202021/NIPWG_VTC_2021_6-2-1_CCG%20Report%20on%20Feedback%20to%20S-123%20edition%201.0.0.pdf NIPWG VTC 2021-6.2.1], [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG8/NIPWG8_2021_49.2_EN_CCG%20Report%20on%20S-123%20data%20creation.docx NIPWG8-49.2] (now merged into the cumulative list)
*Maritime Assistance Services and Rescue Services: [https://iho.int/uploads/user/Services%20and%20Standards/NIPWG/NIPWG%20VTC%202021/NIPWG_VTC_2021_6-2-2_DE_MAS_Rescue_Services_Considerations.pdf NIPWG VTC 2021-6.2.2] (now merged into the cumulative list)
*Report on creation of S-123 for German waters: [https://legacy.iho.int/mtg_docs/com_wg/NIPWG/NIPWG7/NIPWG7_2019_20.1b_EN_Creation%20of%20S-123%20for%20German%20waters.pdf NIPWG7-20.1b] (now merged into the cumulative list)

New feedback should be submitted to Elena Armanino or Bridget Gagné using the comments form (see the ''Cumulative list...'' link above). Addresses can be obtained from the NIPWG membership list on the IHO NIPWG page.

'''Diagrams''': [http://wp12183585.server-he.de/npubwiki/S123HTML/index.htm Link]

'''Other documents'''
* MRCC, Coast Guard Station, control center, radio station - Examples: [[:File:MRCC_CGStation_ControlCenter_RadioStation.docx|Link]]
* Complex attribute ''radiocommunications'' modeling issues: [[:File:RadiocommunicationsModelingIssues.docx|Link]]
* Response from UKHO about radio station types (circulated by email on April 26)
* Samples from Germany (May 6, 2022): [[:File:S123_NAVTEX.pdf|NAVTEX]], [[:File:S123_VTS_Warnemünde.pdf|VTS Warnemünde]]
* CCG RAMN Examples
** Maritime Mobile Safety and Communication Frequencies MF/HF Available at MCTS Centres [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part1-eng.html#tab11 Link]
** Maritime Mobile Safety and Communication Frequencies VHF [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part1-eng.html#tab12 Link]
** Example: Sydney MCTS Centre [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part2-eng.html#2111 Link]
*** List of associated radio stations and ship/shore communications [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part2-eng.html#tab223 Link]
*** List of broadcasts [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part2-eng.html#tab224 Link]
** Transmitting Sites where NAVTEX Service is Available [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part4-eng.html#tab414 Link]
** Weather and Forecast
*** Maritimes Region: Text Format [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part5-eng.html#tab542 Link]
*** Maritimes Region: NAVTEX Format [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part5-eng.html#tab543 Link]
** DGPS: St. Lawrence River and Atlantic Coast [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part4-eng.html#4281 Link]
** Example: Radio Facsimile Stations [https://www.ccg-gcc.gc.ca/publications/mcts-sctm/ramn-arnm/part5-eng.html#tab568 Link]
* ALRS examples
** Marine Radio Stations/GMDSS [[:File:Example_Marine_Radio_Stations.pdf | Link]];
** Radio Weather Services and Navigational Warnings (MSI); [[:File:Example_Radio_Weather_Services_and_Navigational_Warnings.pdf | Link]]
** service details retrieved from ITU's publication/database [[:File:Example_PENANG_RADIO_Document_08_05_2022.pdf | Link]], [[:File:Example_GUANGZHOU_RADIO_Document_08_05_2022_updated20170619.pdf|Link]]
** Format for AIS stations and DGNSS/DGPS radio beacons [[:File:Example_Automatic_Identification_System_(AIS)_and_Radio_Beacon_DGNSS.pdf | Link]]
* New definitions Areas A1 - A4 [[:File:New_definition_Areas_A1-A4.PNG | Link]]
* Halifax Coast Guard Radio [[:File:HALIFAX_COAST_GUARD_RADIO_Document_26_05_2022.pdf | Link]]
* ITU Canada CP notes [[:File:ITU_Canada_CP_notes.pdf | Link]]
* Sample data prepared by NIPWG for S-123 Edition 1.0.0: [[:File:NIPWG03_2016_26.1.1_EN_S-123_ProdSpec_Radio_Services_Sample_data_sets_v1.pdf|Link]]
* Radiocommunications remodeling - 1 [[:File:Radiocommunications_Remodeling_SJC.pdf|Link]]
* Radiocommunications remodeling - 2 [[:File:RadioServiceAreas-Examples-Remodeling-RM.pdf|Link]]
* NIPWG use case for overlapping data draft [[:File:NIPWG_use_case_for_overlapping_data_draft.docx|Link]] and [http://wp12183585.server-he.de/npubwiki/wiki/index.php/SNPWG2 Discussion space]
* GMDSS remodeling [[:File:GMDSS-Remodeling-1.pdf|Slide deck 1]], [[:File:GMDSS-Remodeling-2.pdf|Slide deck 2]]

'''Meeting records'''
* Minutes:
**Final minutes, December 8, 2021 VTC: [[Media:S123TG1_Dec-2021_Minutes_Final.pdf|Link]] (PDF file).
**Final minutes, January 19, 2022 VTC: [[Media:S123TG2_Jan-2022_Minutes_Final.pdf|Link]] (PDF file).
**Final minutes, February 15, 2022 VTC: [[Media:S123TG3_Feb-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, March 16, 2022 VTC: [[Media:S123TG4_Mar-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, April 19, 2022 VTC: [[Media:S123TG5_Apr-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, May 25, 2022 VTC: [[Media:S123TG6_May-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, June 15, 2022 VTC: [[Media:S123TG7_June-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, July 14, 2022 VTC: [[Media:S123TG8_July-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, August 4, 2022 VTC: [[Media:S123TG9_Aug-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, October 13, 2022 VTC: [[Media:S123TG10_Oct-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, November 8, 2022 VTC: [[Media:S123TG11_Nov-2022_Minutes.pdf|Link]] (PDF file).
**Final minutes, January 12, 2023 VTC: [[Media:S123TG12_Jan-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, February 9, 2023 VTC: [[Media:S123TG13_Feb-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, March 23, 2023 VTC: [[Media:S123TG14_Mar-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, May 25, 2023 VTC: [[Media:S123TG15_May-2023_Minutes.pdf|Link]] (PDF file).
**Final minutes, July 25, 2023 VTC: [[Media:S123TG16_July-2023_Minutes.pdf|Link]] (PDF file).
**Draft minutes, August 24, 2023 VTC: [[Media:S123TG17_Aug-2023_Minutes.pdf|Link]] (PDF file).

'''Summary of decisions'''

Decisions and actions (as of August 24, 2023): [[Media:Feedback_collected_S-123_TG-comments.docx|Link]] (.docx file)

Sitesupport-url

2023-10-03T05:42:03Z

Rmm:

For information on how to navigate this Wiki and edit pages, see the links in the Help section of the navigation menu on the left.

To request a user account (needed in order to edit pages) email your request to the NIPWG chair and Wiki admin. Include your requested Wiki user name in the email.

Please do not edit the "Main Page", "FCD" and individual object type pages (the pages specifying the names and definitions or feature types, information types, and attributes) without prior arrangement. If you have comments on any of these pages, add them to the corresponding "discussions" pages (accessible via the "Discussion" tab on each page). If you start or resume a discussion, to facilitate timely responses, please also bring your discussion to the attention of the appropriate NIPWG members, who may not be monitoring the Wiki at that time.

The NIPWG Chair is Eivind Mong. The Wiki admin for this Wiki is Raphael Malyankar. Email addresses for both can be found via the [https://iho.int/en/nipwg NIPWG page] on the IHO web site.

Sitesupport-url

2023-10-03T05:39:55Z

Rmm:

Help:Contents

2023-10-03T05:37:27Z

Rmm:

Although I'm not a wiki expert and currently I'm not intending to become one, pls find below some helpful information for your convenience.
Have fun
Jens

=='''How do I edit a page?'''==
* This is the most important part. '''You have to use the edit link''' on top to modify the page content. The discussion tab works similar.
* To edit a page, simply click the edit link that appears on each page. A form will appear, containing the existing markup. When you have finished making modifications, click the Save button to commit your changes.

=='''How do I create a new page?'''==
* Create a link to the page on another page, then click on the red link which appears

=='''How do I create a link to a new page?'''==
* Embed the term you intend to be as a link in brackets like this <nowiki>[[link ]]</nowiki> or this <nowiki>[[link | Text ]]</nowiki>

=='''How do I mark terms or links in bold?'''==
* Either use the formatting button on top of the "edit" area or place three ' ' ' before and after the text or link.

=='''How do I combine links and bold?'''==
* Use following combination three <nowiki>' ' '</nowiki> followed by <nowiki>[[ and than close the area with the ]]</nowiki> followed by <nowiki>' ' '</nowiki>.
* The order of symbols is important, otherwise the result is not sufficient. However, use the edit link at each page and browse for further formatting examples.

=='''How do I upload the current version of the associated files?'''==
* Follow the link at bottom at the [[SNPWG]] page and replace the current version in the page which will appear when the link opens. Don't get nervous that it is called IMAGE; it is the folder where the uploads will be stored. An instruction is written at spreadsheet page in detail.

=='''How do I create a time stamp associated with my sign in name'''==
* Add easily 4 ~ at the place underneath your comments or contributions.

=='''How do I create the confirmation table underneath each entry'''==
* Quit easy, copy and paste from other pages where the table exist or copy this at when being in edit mode

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
!David!!Ricardo!!Rolando!!Jens
|- style="background:white; color:black"
|DA Y/N
|RF Y/N
|RR Y/N
|JSF Y/N
|}

==''' How do I provide my contact details?'''==
* Simply refer to the users page link. You can find it on the right top of each page.

==''' Some more Wiki syntax'''==
* ''Italic text'' can be written by using the editing buttons on top or like <nowiki>' 'this' '</nowiki>.
* enumerated lists with one intentation like this

# item 1
## item
## item
# item 2
## item
## item

can be styled using one or two <nowiki># </nowiki>

* list style using dots like this

* item
** item
** item
** item
* item
** item

can be styled using one or two <nowiki>* </nowiki>

==''' Where can I find more information about navigation and editing?'''==
See the [https://www.mediawiki.org/wiki/Help:Contents MediaWiki help pages].

==''' Can I edit any page I want?'''==
Please do not edit the "Main Page", "FCD" and individual object type pages (the pages specifying the names and definitions or feature types, information types, and attributes) without prior arrangement. If you have comments on any of these pages, add them to the corresponding "discussions" pages (accessible via the "Discussion" tab on each page). If you start or resume a discussion, to facilitate timely responses, please also bring your discussion to the attention of the appropriate NIPWG members, who may not be monitoring the Wiki at that time.

If you have questions about whether you can or should edit any particular page on this Wiki, ask the NIPWG Chair and/or site maintainer.

=='''How to handle the sample dataset'''==
Important is to use '''only''' the current version of the file which can easily be found when clicking on the link. Don't wonder why it is headed with "Image:...". That is wiki syntax and will not be replaced by other terms. 
The text underneath the '''Warning''' can be amended by editing the page. The default setting is, that the text is a copy of the last comment in the file history section. As stated above, it can easily be amended. If intending to do some work please declare here that the file is under construction by you. That is important to avoid file conflicts. 
A click on the file file opens an external application, usually MS word, and the file can be edited. '''I strongly suggest to check "Track changes".''' It is an incredible help for other editors. 
When finished the work the file should be saved somewhere on your computer with a name at your choice. It is time to upload the next current version now. With a click a new window offers to browse for the file which will be the next current version. You see, it doesn't matter which name you have given to that file when saving it on your computer. The new version will get the wiki file name. The wiki needs only to know which file it should place. You should write a little comment stating what you have done in brief. 
After uploading the new version you can find the current version on top of the file history and your comment is now below the '''Warning''' section. That indicates to other that the file is not longer blocked. 
I hope it was of some help. Have fun. Jens

----

Sitesupport-url

2023-10-03T05:30:11Z

Rmm: Site support information

For information on how to navigate this Wiki and edit pages, see the links in the Help section of the navigation menu on the left.

To request a user account (needed in order to edit pages) email your request to Eivind with a cc to Raphael. Include your requested Wiki user name in the email.

Please do not edit the "Main Page", "FCD" and individual object type pages (the pages specifying the names and definitions or feature types, information types, and attributes) without prior arrangement. If you have comments on any of these pages, add them to the corresponding "discussions" pages (accessible via the "Discussion" tab on each page). If you start or resume a discussion, to facilitate timely responses, please also bring your discussion to the attention of the appropriate NIPWG members, who may not be monitoring the Wiki at that time.

MediaWiki:Sidebar

2023-10-02T17:06:42Z

Rmm:

SDs/S-100 Gap Analysis

2023-10-02T16:55:47Z

Rmm: Created page with "[Add content here.]"

[Add content here.]

MediaWiki:Sidebar

2023-10-02T16:55:08Z

Rmm:

Help:Contents

2023-10-02T16:44:01Z

Rmm:

Although I'm not a wiki expert and currently I'm not intending to become one, pls find below some helpful information for your convenience.
Have fun
Jens

=='''How do I edit a page?'''==
* This is the most important part. '''You have to use the edit link''' on top to modify the page content. The discussion tab works similar.
* To edit a page, simply click the edit link that appears on each page. A form will appear, containing the existing markup. When you have finished making modifications, click the Save button to commit your changes.

=='''How do I create a new page?'''==
* Create a link to the page on another page, then click on the red link which appears

=='''How do I create a link to a new page?'''==
* Embed the term you intend to be as a link in brackets like this <nowiki>[[link ]]</nowiki> or this <nowiki>[[link | Text ]]</nowiki>

=='''How do I mark terms or links in bold?'''==
* Either use the formatting button on top of the "edit" area or place three ' ' ' before and after the text or link.

=='''How do I combine links and bold?'''==
* Use following combination three <nowiki>' ' '</nowiki> followed by <nowiki>[[ and than close the area with the ]]</nowiki> followed by <nowiki>' ' '</nowiki>.
* The order of symbols is important, otherwise the result is not sufficient. However, use the edit link at each page and browse for further formatting examples.

=='''How do I upload the current version of the associated files?'''==
* Follow the link at bottom at the [[SNPWG]] page and replace the current version in the page which will appear when the link opens. Don't get nervous that it is called IMAGE; it is the folder where the uploads will be stored. An instruction is written at spreadsheet page in detail.

=='''How do I create a time stamp associated with my sign in name'''==
* Add easily 4 ~ at the place underneath your comments or contributions.

=='''How do I create the confirmation table underneath each entry'''==
* Quit easy, copy and paste from other pages where the table exist or copy this at when being in edit mode

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
!David!!Ricardo!!Rolando!!Jens
|- style="background:white; color:black"
|DA Y/N
|RF Y/N
|RR Y/N
|JSF Y/N
|}

==''' How do I provide my contact details?'''==
* Simply refer to the users page link. You can find it on the right top of each page.

==''' Some more Wiki syntax'''==
* ''Italic text'' can be written by using the editing buttons on top or like <nowiki>' 'this' '</nowiki>.
* enumerated lists with one intentation like this

# item 1
## item
## item
# item 2
## item
## item

can be styled using one or two <nowiki># </nowiki>

* list style using dots like this

* item
** item
** item
** item
* item
** item

can be styled using one or two <nowiki>* </nowiki>

==''' Where can I find more information about navigation and editing?'''==
See the [https://www.mediawiki.org/wiki/Help:Contents MediaWiki help pages].

=='''How to handle the sample dataset'''==
Important is to use '''only''' the current version of the file which can easily be found when clicking on the link. Don't wonder why it is headed with "Image:...". That is wiki syntax and will not be replaced by other terms. 
The text underneath the '''Warning''' can be amended by editing the page. The default setting is, that the text is a copy of the last comment in the file history section. As stated above, it can easily be amended. If intending to do some work please declare here that the file is under construction by you. That is important to avoid file conflicts. 
A click on the file file opens an external application, usually MS word, and the file can be edited. '''I strongly suggest to check "Track changes".''' It is an incredible help for other editors. 
When finished the work the file should be saved somewhere on your computer with a name at your choice. It is time to upload the next current version now. With a click a new window offers to browse for the file which will be the next current version. You see, it doesn't matter which name you have given to that file when saving it on your computer. The new version will get the wiki file name. The wiki needs only to know which file it should place. You should write a little comment stating what you have done in brief. 
After uploading the new version you can find the current version on top of the file history and your comment is now below the '''Warning''' section. That indicates to other that the file is not longer blocked. 
I hope it was of some help. Have fun. Jens

----

Help:Contents

2023-10-02T16:34:46Z

Rmm:

Although I'm not a wiki expert and currently I'm not intending to become one, pls find below some helpful information for your convenience.
Have fun
Jens

=='''How do I edit a page?'''==
* This is the most important part. '''You have to use the edit link''' on top to modify the page content. The discussion tab works similar.
* To edit a page, simply click the edit link that appears on each page. A form will appear, containing the existing markup. When you have finished making modifications, click the Save button to commit your changes.

=='''How do I create a new page?'''==
* Create a link to the page on another page, then click on the red link which appears

=='''How do I create a link to a new page?'''==
* Embed the term you intend to be as a link in brackets like this <nowiki>[[link ]]</nowiki> or this <nowiki>[[link | Text ]]</nowiki>

=='''How do I mark terms or links in bold?'''==
* Either use the formatting button on top of the "edit" area or place three ' ' ' before and after the text or link.

=='''How do I combine links and bold?'''==
* Use following combination three <nowiki>' ' '</nowiki> followed by <nowiki>[[ and than close the area with the ]]</nowiki> followed by <nowiki>' ' '</nowiki>.
* The order of symbols is important, otherwise the result is not sufficient. However, use the edit link at each page and browse for further formatting examples.

=='''How do I upload the current version of the associated files?'''==
* Follow the link at bottom at the [[SNPWG]] page and replace the current version in the page which will appear when the link opens. Don't get nervous that it is called IMAGE; it is the folder where the uploads will be stored. An instruction is written at spreadsheet page in detail.

=='''How do I create a time stamp associated with my sign in name'''==
* Add easily 4 ~ at the place underneath your comments or contributions.

=='''How do I create the confirmation table underneath each entry'''==
* Quit easy, copy and paste from other pages where the table exist or copy this at when being in edit mode

{| style="background:#ccc99; color:black;" border="1" cellpadding="5" cellspacing="0" align="left"
!David!!Ricardo!!Rolando!!Jens
|- style="background:white; color:black"
|DA Y/N
|RF Y/N
|RR Y/N
|JSF Y/N
|}

==''' How do I provide my contact details?'''==
* Simply refer to the users page link. You can find it on the right top of each page.

==''' Some more Wiki syntax'''==
* ''Italic text'' can be written by using the editing buttons on top or like <nowiki>' 'this' '</nowiki>.
* enumerated lists with one intentation like this

# item 1
## item
## item
# item 2
## item
## item

can be styled using one or two <nowiki># </nowiki>

* list style using dots like this

* item
** item
** item
** item
* item
** item

can be styled using one or two <nowiki>* </nowiki>

=='''How to handle the sample dataset'''==
Important is to use '''only''' the current version of the file which can easily be found when clicking on the link. Don't wonder why it is headed with "Image:...". That is wiki syntax and will not be replaced by other terms. 
The text underneath the '''Warning''' can be amended by editing the page. The default setting is, that the text is a copy of the last comment in the file history section. As stated above, it can easily be amended. If intending to do some work please declare here that the file is under construction by you. That is important to avoid file conflicts. 
A click on the file file opens an external application, usually MS word, and the file can be edited. '''I strongly suggest to check "Track changes".''' It is an incredible help for other editors. 
When finished the work the file should be saved somewhere on your computer with a name at your choice. It is time to upload the next current version now. With a click a new window offers to browse for the file which will be the next current version. You see, it doesn't matter which name you have given to that file when saving it on your computer. The new version will get the wiki file name. The wiki needs only to know which file it should place. You should write a little comment stating what you have done in brief. 
After uploading the new version you can find the current version on top of the file history and your comment is now below the '''Warning''' section. That indicates to other that the file is not longer blocked. 
I hope it was of some help. Have fun. Jens

----

IHO Nautical Information Processing Working Group:Privacy policy

2023-10-02T03:16:31Z

Rmm: Created page with "The NIPWG Wiki is hosted by HostEurope and the HostEurope web site [https://www.hosteurope.de/Dokumente/ privacy policy] applies. The following additional information also app..."

The NIPWG Wiki is hosted by HostEurope and the HostEurope web site [https://www.hosteurope.de/Dokumente/ privacy policy] applies. The following additional information also applies.

A Wiki user account is necessary in order to edit pages on this Wiki. Creation of a Wiki user account requires that you supply a user name and password. The user name need not be your real name. Provision of an email address and real name is optional. The information you supply in creating or updating a Wiki user account will be recorded and used as login credentials. Contributions or edits you make will be displayed to readers along with your user name or real name. To request a Wiki user account or to delete your Wiki user account and credentials, send a request to the NIPWG Chair (name and contact information can be obtained from the [https://iho.int/en/nipwg IHO NIPWG site].

Wiki user accounts are not needed to view its content. The content of this Wiki may be viewed by anyone.

File:S131 IHOLab 2023JUN28 Minutes.pdf

2023-08-09T21:21:35Z

Rmm:

NIPWG S-131 Harbour Infrastructure

2023-08-09T21:20:01Z

Rmm:

== IHO-Lab Project ==

'''IHO-Lab S-131 project team meeting records'''
* Minutes:
**Minutes, June 28, 2023 VTC: [[Media:S131_IHOLab_2023JUN28_Minutes.pdf|Link]] (PDF file).

== S-131 Product Specification ==
'''Latest news'''

S-131 Edition 1.0.0 has been approved by HSSC and Edition 1.0.0, along with associated artifacts (FC, PC, schema, sample datasets) can be obtained from the [https://registry.iho.int/productspec/list.do IHO GI Registry] or the schema server (pre-publication, on the staging server at https://staging.s100dev.net).

Comments received on the final draft circulated to NIPWG, and their adjudications, are available: [[Media:S131_1_0_0_Comments-20230408.pdf|Link]].

''' Feature Catalogue'''

The feature catalogue is available from the IHO GI Registry (link above).

'''GML schemas'''

GML schemas are currently available from the staging schema server https://staging.s100dev.net for the current schema (will also be available the the schemas.s100dev.net at a later date).

'''Sample datasets'''

See the schema server for sample datasets and a sample exchange catalogue (https://staging.s100dev.net - pre-publication).

'''Current Model'''
Link to be added.

For older version(s) see ''Older Models'' later on this page.

== Discussion/background material for Edition 1.0.0 ==
'''Sources'''

The following sources are available:

The [[:File:Description of S-xxx Harbour Infrastructure.docx|Hrbr Infrstrctr Description]] as provided to HSSC.

An Excel spreadsheet based on the scope discussion SNPWG had back in the year 2005 [[:File:Hrbr Infrstrctr based on scope version 1.2 2005_07_22 and PortCDM information.xlsx|Hrbr Infrstrctr Scope]]. This information is enhanced with advice on other international bodies activities, such as IMO FAL or PortCDM.

Additional reference materials are the latest version of the [http://wp12183585.server-he.de/npubwiki/wiki/images/archive/7/73/20210607044314%21Port_Information_Manual.pdf Port Information Manual (3.03 only nautical data)] and [[:File:Port Information Manual.pdf|Port Information Manual (3.02 Core document)]], issued by the International Harbour Master Association (IHMA), and the comments provided by [[:File:Response to IHMA on Port Manual 1.4.5_clean.docx|NIPWG7]] on this Manual. It shoud be noted that the IHMA is working on a revision of the Manual taking into account the NIPWG7 comments. The IHMA Response paper can be found here [[:File:PIM Revision NIPWG7 Paper.docx|IHMA Response on NIPWG comments on PIM version 007]]

A clean Excel spreadsheet where your contributions and comments will be collected. It is intended to keep this spreadsheet up-to-date to ensure that always the current status is available.
The first entries have been made in this spreadsheet as an example. [[:File:Hrbr Infrstrctr_Clean table.xlsx|Hrbr Infrstrctr Clean]]

'''Split of S-131 features in logical groups and respective excel spreadsheets.'''
*Port/Harbour Layout Features [[:File:Port_Harbour_Layout_Features.xlsx|Port_Harbour_Layout_Features]]
** [[:File:S-131-PortHarbour_Layout_v3.pdf| 5/6/21 updated Port/Harbour Layout UML v3]]
*Port/Harbour Physical Infrastructure Features [[:File:Port_Harbour_Physical_Infrstructure_Features.xlsx|Port_Harbour_Physical_Infrastructure_Features]]
*Port/Harbour non-Physical Infrastructure Features [[:File:Port_Harbour_non.Physical_Infrstructure_Features.xlsx|Port_Harbour_non_Physical_Infrastructure_Features]]

'''Update of S-131 features from NIPWG feedback and merged excel spreadsheets - in Word document form (for easy reading)'''

Please note: This is NOT meant to be a comprehensive well-formed document! It is a living, breathing evolving one meant only to be the common collection place for additions to the UML data model. ''(Note: As of August 2021, these Word focuments are somewhat out of date - see the HTML diagrams link that follows.)''
*Port/Harbour Layout Features [[:File:S-131-Layout.docx|Port_Harbour_Layout_Features_doc]]
** [[:File:Layout-feedback-Updates_v2.pdf| 5/6/21 suggested updates to Port/Harbour Layout UML]] from Port_Harbour_Layout_Features_doc feedback

*Port/Harbour Physical Infrastructure Features [[:File:S-131-PhysicalInfrastructure.docx|Port_Harbour_Physical_Infrastructure_Features_doc]]
*Port/Harbour Services [[:File:S-131_Harbour_Services.docx|Port_Harbour_Services_doc]]

'''Older Models'''
[http://wp12183585.server-he.de/npubwiki/S131Model20221030/index.htm Diagrams] for the October 30 version of the model (obsolete after December 2022).

Original (September 2021) (obsolete)

[http://18.132.248.81/f61367edc6ef9ffa928d25168cf47245/v9/ Link] to diagrams for Version 0.1 of the model (broken?).

<gallery mode="traditional" caption="Diagrams from 0.1 model (2021)" widths=200px>
File:1.0_Realisations_from_S-100_-_Generic_Features.png|Realisations from S-100 - Generic Features
File:1.1_Features_and_Information_Types.png|Features and Information Types
File:1.2_Relationships.png|Relationships
File:2._Physical_Infrastructure.png|Physical Infrastructure
File:7_Text_Handling.png|Text Handling
File:8_Available_Services.png|Services
File:9_Restrictions.png|Restrictions
File:91_WaterwayArea.png|WaterwayArea
File:Notes.png|Notes
</gallery>

Version 0.1 (January 2022) (obsolete)

[http://wp12183585.server-he.de/npubwiki/S131Model/index.htm Link] to diagrams for Version 0.2 of the model (14 January 2022). ''This model is now obsolete. A new version will be posted soon.''
 (The landing page will show just the logo and a table of contents on the left, use the TOC to navigate to diagrams or individual elements.)

[[:File:S-131-Model-0.2-WorkingNotes.pdf|Notes on revisions to v. 0.1]]

'''Marine Harbour Infrastructure Background Material'''

* NO has kindly provided the data element collection of their NO Coast Pilot. The entries can be used as reference and for completeness check. [[File:NO_port_data_prod_spec.pdf]]
* Sample from Greenland Harbour Pilot ([[:File:Greenlandharbourpilot.xlsx]]) and link to site https://www.gronlandskehavnelods.dk/?&lang=ENG
* List of potential topics [[:File:Harbour_Infrastructure_Topic_List.docx]]
* S-211 Port Call Message Format product specification https://www.ipcdmc.org/standards-and-guidelines
* Taiwan Port Net Extract providing berth position information [[:File:Berth_MooringFacilities_BerthPosition_TaiwanPortNet.pdf|Taiwan Port Net]]
* Individual contributions to the clean table are available here: [[:File:Hrbr_Infrstrctr_Table_Combined_Contribs.xlsx|Harbour Infrastructure Contributions]]. (Information received as of 22 July should all have been merged into the main clean table, let me know if anything is missing).
* Data model master data exchange; Proof Of Concept document for exchanging data between port and HO (only pages 6-11) [[:File:Data_model_master_Extract_20210520.pdf|Data model extract]]
* Port Information Manual 3.06 (3 pages): Replaces the May 20 extract from the 3.05 version. [[:File:Port_Information_Manual_3.06_Extract_20210602.pdf|Port Information Manual extract]]
* Port Information Guide [[:File:Port_Information_Guide.pdf|Port Information Guide]]
* Different aspects of water level from PIANC publication Report No. 121 – 2014 [[:File:S131_depth_discussion.pdf|S131 depth discussion]]

Talk:NIPWG S-1xx hrb infrstrctr

2023-08-09T20:30:53Z

Rmm: Rmm moved page Talk:NIPWG S-1xx hrb infrstrctr to Talk:NIPWG S-131 Harbour Infrastructure: Replace S-1xx with assigned number

#REDIRECT [[Talk:NIPWG S-131 Harbour Infrastructure]]

Talk:NIPWG S-131 Harbour Infrastructure

2023-08-09T20:30:53Z

Rmm: Rmm moved page Talk:NIPWG S-1xx hrb infrstrctr to Talk:NIPWG S-131 Harbour Infrastructure: Replace S-1xx with assigned number

[[User:Jens|jens]] ([[User talk:Jens|talk]]) 13:45, 14 September 2020 (CEST)
Folllowing background information has been provided by the IHMA

Attributes to the feature “port” can be copied from the IMO publication “Blu Code” (Code of Practice for the Safe Loading and Unloading of Bulk Carriers) 2011 Edition, Appendix 1, approved at the 87th session of IMO MSC:

Recommended contents of port and terminal information books”; the following list only contains the recommend contents of the port information book (and which has also been used to draft the PIM)

1. Location of the port and the terminal
2. Details of port administration
3. Radio communication procedures and frequencies
4. Arrival information requirements
5. Port health, immigration, quarantine and customs regulations and procedures
6. Relevant charts and nautical publications
7. Pilotage requirements
8. Towage and tug assistance
9. Berthing and anchorage facilities
10. Port emergency procedures
11. Significant weather features
12. Availability of fresh water, provisions, bunkers and lubricants
13. The maximum size of ship the port can accept
14. Maximum permissible draught and minimum depth of water in navigation channels
15. Water density of the port
16. Maximum permissible air draught
17. Requirements for ship’s draught and trim for navigation in the waterways
18. Tidal and current information , as it affects ship movements
19. Restrictions or conditions on the discharge of ballast water
20. Statutory requirements regarding loading and cargo declaration
21. Information on waste reception facilities in the port

Items 13) to 17) only make sense if provided per section of the port (so per fairway, turning basin, basin, or berthing pocket)

NIPWG S-1xx hrb infrstrctr

2023-08-09T20:30:53Z

Rmm: Rmm moved page NIPWG S-1xx hrb infrstrctr to NIPWG S-131 Harbour Infrastructure: Replace S-1xx with assigned number

#REDIRECT [[NIPWG S-131 Harbour Infrastructure]]

NIPWG S-131 Harbour Infrastructure

2023-08-09T20:30:53Z

Rmm: Rmm moved page NIPWG S-1xx hrb infrstrctr to NIPWG S-131 Harbour Infrastructure: Replace S-1xx with assigned number

'''Latest news'''

S-131 Edition 1.0.0 has been submitted to HSSC and the draft, along with associated artifacts (FC, PC, schema, sample datasets) can be obtained from the "TEST BED" section of the IHO GI registry or the schema server (pre-publication, on the staging server at https://staging.s100dev.net).

Comments received on the final draft circulated to NIPWG, and their adjudications, are available: [[Media:S131_1_0_0_Comments-20230408.pdf|Link]].

''' Feature Catalogue'''

October 30 work-in-progress draft of S-131 Feature Catalogue (Obsolete - see the IHO GI registry for the latest FC).

'''GML schemas'''

October 30 work-in-progress draft of S-131 GML schema (Obsolete - see the staging schema server https://staging.s100dev.net for the current schema.)

'''Sample datasets'''

See the schema server for sample datasets and a sample exchange catalogue (https://staging.s100dev.net - pre-publication).

'''Current Model'''
Link to be added.

For older version(s) see ''Older Models'' later on this page.

'''S-131 Marine Harbour Infrastructure'''

The following sources are available:

The [[:File:Description of S-xxx Harbour Infrastructure.docx|Hrbr Infrstrctr Description]] as provided to HSSC.

An Excel spreadsheet based on the scope discussion SNPWG had back in the year 2005 [[:File:Hrbr Infrstrctr based on scope version 1.2 2005_07_22 and PortCDM information.xlsx|Hrbr Infrstrctr Scope]]. This information is enhanced with advice on other international bodies activities, such as IMO FAL or PortCDM.

Additional reference materials are the latest version of the [http://wp12183585.server-he.de/npubwiki/wiki/images/archive/7/73/20210607044314%21Port_Information_Manual.pdf Port Information Manual (3.03 only nautical data)] and [[:File:Port Information Manual.pdf|Port Information Manual (3.02 Core document)]], issued by the International Harbour Master Association (IHMA), and the comments provided by [[:File:Response to IHMA on Port Manual 1.4.5_clean.docx|NIPWG7]] on this Manual. It shoud be noted that the IHMA is working on a revision of the Manual taking into account the NIPWG7 comments. The IHMA Response paper can be found here [[:File:PIM Revision NIPWG7 Paper.docx|IHMA Response on NIPWG comments on PIM version 007]]

A clean Excel spreadsheet where your contributions and comments will be collected. It is intended to keep this spreadsheet up-to-date to ensure that always the current status is available.
The first entries have been made in this spreadsheet as an example. [[:File:Hrbr Infrstrctr_Clean table.xlsx|Hrbr Infrstrctr Clean]]

'''Split of S-131 features in logical groups and respective excel spreadsheets.'''
*Port/Harbour Layout Features [[:File:Port_Harbour_Layout_Features.xlsx|Port_Harbour_Layout_Features]]
** [[:File:S-131-PortHarbour_Layout_v3.pdf| 5/6/21 updated Port/Harbour Layout UML v3]]
*Port/Harbour Physical Infrastructure Features [[:File:Port_Harbour_Physical_Infrstructure_Features.xlsx|Port_Harbour_Physical_Infrastructure_Features]]
*Port/Harbour non-Physical Infrastructure Features [[:File:Port_Harbour_non.Physical_Infrstructure_Features.xlsx|Port_Harbour_non_Physical_Infrastructure_Features]]

'''Update of S-131 features from NIPWG feedback and merged excel spreadsheets - in Word document form (for easy reading)'''

Please note: This is NOT meant to be a comprehensive well-formed document! It is a living, breathing evolving one meant only to be the common collection place for additions to the UML data model. ''(Note: As of August 2021, these Word focuments are somewhat out of date - see the HTML diagrams link that follows.)''
*Port/Harbour Layout Features [[:File:S-131-Layout.docx|Port_Harbour_Layout_Features_doc]]
** [[:File:Layout-feedback-Updates_v2.pdf| 5/6/21 suggested updates to Port/Harbour Layout UML]] from Port_Harbour_Layout_Features_doc feedback

*Port/Harbour Physical Infrastructure Features [[:File:S-131-PhysicalInfrastructure.docx|Port_Harbour_Physical_Infrastructure_Features_doc]]
*Port/Harbour Services [[:File:S-131_Harbour_Services.docx|Port_Harbour_Services_doc]]

'''Older Models'''
[http://wp12183585.server-he.de/npubwiki/S131Model20221030/index.htm Diagrams] for the October 30 version of the model (obsolete after December 2022).

Original (September 2021) (obsolete)

[http://18.132.248.81/f61367edc6ef9ffa928d25168cf47245/v9/ Link] to diagrams for Version 0.1 of the model (broken?).

<gallery mode="traditional" caption="Diagrams from 0.1 model (2021)" widths=200px>
File:1.0_Realisations_from_S-100_-_Generic_Features.png|Realisations from S-100 - Generic Features
File:1.1_Features_and_Information_Types.png|Features and Information Types
File:1.2_Relationships.png|Relationships
File:2._Physical_Infrastructure.png|Physical Infrastructure
File:7_Text_Handling.png|Text Handling
File:8_Available_Services.png|Services
File:9_Restrictions.png|Restrictions
File:91_WaterwayArea.png|WaterwayArea
File:Notes.png|Notes
</gallery>

Version 0.1 (January 2022) (obsolete)

[http://wp12183585.server-he.de/npubwiki/S131Model/index.htm Link] to diagrams for Version 0.2 of the model (14 January 2022). ''This model is now obsolete. A new version will be posted soon.''
 (The landing page will show just the logo and a table of contents on the left, use the TOC to navigate to diagrams or individual elements.)

[[:File:S-131-Model-0.2-WorkingNotes.pdf|Notes on revisions to v. 0.1]]

'''Marine Harbour Infrastructure Background Material'''

* NO has kindly provided the data element collection of their NO Coast Pilot. The entries can be used as reference and for completeness check. [[File:NO_port_data_prod_spec.pdf]]
* Sample from Greenland Harbour Pilot ([[:File:Greenlandharbourpilot.xlsx]]) and link to site https://www.gronlandskehavnelods.dk/?&lang=ENG
* List of potential topics [[:File:Harbour_Infrastructure_Topic_List.docx]]
* S-211 Port Call Message Format product specification https://www.ipcdmc.org/standards-and-guidelines
* Taiwan Port Net Extract providing berth position information [[:File:Berth_MooringFacilities_BerthPosition_TaiwanPortNet.pdf|Taiwan Port Net]]
* Individual contributions to the clean table are available here: [[:File:Hrbr_Infrstrctr_Table_Combined_Contribs.xlsx|Harbour Infrastructure Contributions]]. (Information received as of 22 July should all have been merged into the main clean table, let me know if anything is missing).
* Data model master data exchange; Proof Of Concept document for exchanging data between port and HO (only pages 6-11) [[:File:Data_model_master_Extract_20210520.pdf|Data model extract]]
* Port Information Manual 3.06 (3 pages): Replaces the May 20 extract from the 3.05 version. [[:File:Port_Information_Manual_3.06_Extract_20210602.pdf|Port Information Manual extract]]
* Port Information Guide [[:File:Port_Information_Guide.pdf|Port Information Guide]]
* Different aspects of water level from PIANC publication Report No. 121 – 2014 [[:File:S131_depth_discussion.pdf|S131 depth discussion]]

File:S123TG15 May-2023 Minutes.pdf

2023-08-09T20:15:44Z

Rmm: Rmm uploaded a new version of File:S123TG15 May-2023 Minutes.pdf

== Summary ==
Draft

File:S123TG16 July-2023 Minutes.pdf

2023-08-09T20:13:24Z

Rmm: Draft minutes

== Summary ==
Draft minutes