Difference between revisions of "SNPWG2"

From IHO Nautical Information Processing Working Group
Jump to navigation Jump to search
m
 
(75 intermediate revisions by 3 users not shown)
Line 1: Line 1:
SNPWG has to develop a Product Specification to enable ECDIS manufacturers to build software able to display NPUB information on an ECDIS screen.
+
NIPWG is developing Product Specifications to enable ECDIS manufacturers to build software able to display NPUB information on an ECDIS screen.
Following sub-pages provide discussions on the UML model and the ProdSpec for several NPUB problems.
 
The SNPWG Wiki administration is trying to provide the files in a convenient way; but we can not guarantee to fit all requirements.  
 
  
We started the UML modelling with a number of different UML applications but spotted problems when trying to exchange the files. We decided to use StarUML as the common application. StarUML is freely available and can be downloaded from the StarUML website http://staruml.sourceforge.net/en/.
+
This Wiki attempts to provide the files in a convenient way; but we can not guarantee to fit all requirements.
The file exchange works properly.
 
  
==Scope==
+
'''To add to discussions of the topics on this page click the discussion tab and add your comments under the appropriate subhead.
 +
'''
 +
== Published and in-progress Product Specifications ==
 +
Currently (September 2022), the following Product Specifications are under development: <br>
 +
* S-128, Catalogue of Nautical Products Edition 1.x
 +
* S-131, Marine Harbour Infrastructure Edition 1.0.0
  
xxxxx
+
The following Product Specifications have been published as of September 2022 and are available from the IHO [https://registry.iho.int/ Geospatial Information Registry], Product Specification Register.
 +
* S-122 Edition 1.0.0
 +
* S-123 Edition 1.0.0
 +
* S-127 Edition 1.0.0
 +
* S-128 Edition 1.0.0
  
==Product Specifications==
+
== Overlapping/Mixed Datasets ==
  
===Generals===
+
Note from Teledyne Caris initiating the discussion of the NIPWG use case for overlapping/mixed datasets: [[:File:NIPWG_use_case_for_overlapping_data_draft.docx|Word document]]
 
 
Initially we tried to adapt the S-100 ProdSpec as much as possible. That was good for the learning process.
 
 
However, we have had a discussion resulting that we have to develop a ProdSpec S-10x for NPUBS and it is likely that such a specification can differ from S-100.
 
We also discussed two options of a NPUB ProdSpec
 
# a totally new NPUB ProdSpec starting from scratch
 
# a NPUB ProdSpec using S-57 and charted content as much as possible, adding only those features relevant for nautical information.
 
 
 
The result is to follow the latter option. That avoids some work for us because we do not have to develop the charted content again.
 
How that works can also be seen at the UML models. Only features useful for SNPWG work are copied from S-57. All others remain untouched.
 
 
 
What is currently under discussion? Do we need to build several ProdSpec or can we combine all ProdSpec proposed below into one NPUB ProdSpec. We will see what the future brings?
 
 
 
===Waterways===
 
The waterway ProdSpec is being discussed between Olav and Jens. The files reflecting the discussions are stored here [[Image:Product_Specification_Waterways.doc]]
 
 
 
===Pilotage===
 
xxxxx
 
 
 
===Marine Protected areas===
 
xxxxx
 
 
 
==UML Models==
 
 
 
We propose to display a jpg. file providing a preview of the UML model here or at the sub-pages and a link to the uml file for those who intent to work with UML.
 
 
 
Discussions are to be placed to the discussion page which has a similar structure like this page. The contacts provided are hosting the UML diagrams. It is strongly advised to contact them before trying to amend the attached UML files. The e-mail addresses are to be obtained from the IHO/SNPWG website if not known. We intent to avoid too much duplications of the work done.
 
 
 
'''And now enjoy studying diagrams.'''
 
 
 
 
 
===Product Specification Scope===
 
 
 
[[Image:ProdSpecScope.jpg|thumb|ProdSpecScope]]
 
 
 
 
 
pls contact jens (BSH) if amendments to the diagram are desired
 
 
 
 
 
 
 
 
 
 
 
the UML file is stored and can be downloaded here [[Image:ProdSpecScope.uml]]
 
 
 
===Non Geospacial Scope===
 
[[Image:NonGeospacialScope.jpg|thumb|NonGeospacialScope]]
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
pls contact jens (BSH) if amendments to the diagram are desired
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
the UML file is stored and can be downloaded here  [[Image:NonGeospacialScope.uml]]
 
 
 
===SNPWG Application Schema===
 
 
 
[[Image:SNPWG Application Schema.jpg|thumb|SNPWG Application Schema]]
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
pls contact jens (BSH) if amendments to the diagram are desired
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
the UML file is stored and can be downloaded here [[Image:SNPWG Application Schema.uml]]
 
 
 
===Waterways===
 
[[Image:WaterwayArea Main Diagram.jpg|thumb|WaterwayArea Main Diagram]]
 
 
 
The idea behind the diagram is simple now.
 
A waterway area (for SNPWG interest) contains only non-chartable information. We associate rec/res/reg/natinf to that area. If the rec/res/reg apply for a specified type of vessel the association is using that deviation.
 
 
 
The reason why no SEAARE is involved now is that we intent to avoid having two features with the same name and different spatial. That might cause confusion. 
 
 
 
 
 
 
 
 
 
 
 
[[Image:WaterwayArea Package Diagram.jpg|thumb|WaterwayArea Package Diagram]]
 
 
 
 
 
[[Image:WaterwayArea Classes Collection.jpg|thumb|WaterwayArea Classes Collection]]
 
 
 
 
 
[[Image:WaterwayArea Enumerations Collection.jpg|thumb|WaterwayArea Enumerations Collection]]
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
the UML file is stored and can be downloaded here [[Image:WaterwayPackage.uml]]
 
 
 
====Recommended Tracks package====
 
 
 
[[Image:RecommendedTrackPackage.jpg|thumb|Recommended tracks package]]
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
the UML file is stored and can be downloaded here [[Image:Recommended tracks package.uml]]
 
 
 
===Pilotage===
 
[[Image:PilotageMainDiagram.jpg|thumb|Pilotage Main Diagram]]
 
 
 
[[Image:PilotageEnumDiagram.jpg|thumb|Pilotage Enumeration Diagram]]
 
 
 
 
 
 
 
The UML file for the pilotage model depicts attributes,
 
enumerations, etc. in diagrams separate from the main diagram.
 
Also, there are some omissions and shortcuts in
 
this diagram, for example, ordinary UML enumerations are not quite the
 
correct model for S100 enumeration value lists (doing that correctly
 
in UML will take a lot more effort and complication and at this point
 
of time I am not even sure StarUML can show it properly).  The objects
 
and attributes in this version are Jeppesen proposed updates (as of July
 
16) to those on the Wiki.
 
 
 
[[Image:PilotagePackageDiagram.jpg|thumb|Pilotage Package Diagram]]
 
 
 
[[Image:PilotageClassesCollection.jpg|thumb|Pilotage Classes Collection Diagram]]
 
 
 
[[Image:PilotageComplexTypesDiagram.jpg|thumb|Pilotage Complex Types Diagram]]
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
pls contact raphael or john (Jeppesen) if amendments to the diagram are desired
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
the UML file is stored and can be downloaded here [[Image:PilotageMappingExample10.uml]]
 
 
 
===Marine Protected areas===
 
[[Image:MarineProtectedAreas.jpg|thumb|Marine Protected Areas]]
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
pls contact david (UKHO) if amendments to the diagram are desired
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
the UML file is stored and can be downloaded here [[Image:MPADET.uml]]
 
 
 
==Regulations/Restrictions/Recommendations/Nautical Information==
 
Based on some discussions the non-geospacial scope diagrams above remain unchanged. It seems to be time to discuss the several options developed under new items open for confirmation.
 
The diagrams are ideas and open for discussion. They are limited intentionally to the attributes in focus and didn't described the information objects extensively.
 
 
 
The simple diagram
 
 
 
[[image:Reg_simple.jpg]]
 
 
 
added with CATRXN
 
 
 
[[image:Reg_with_CATRXN.jpg]]
 
 
 
added RXNCOD as a further option
 
 
 
[[image:Reg_with_CATRXN_snd_RXNCOD.jpg]]
 
 
 
relatively simple but with RUBRIC and several ranges of completeness
 
 
 
[[image:Reg_with_different_completeness.jpg]]
 
 
 
 
 
safety was added to CATRXN, but is not been implemented here so far.
 
 
 
 
 
what do you think?
 
 
 
==more==
 

Latest revision as of 04:29, 21 September 2022

NIPWG is developing Product Specifications to enable ECDIS manufacturers to build software able to display NPUB information on an ECDIS screen.

This Wiki attempts to provide the files in a convenient way; but we can not guarantee to fit all requirements.

To add to discussions of the topics on this page click the discussion tab and add your comments under the appropriate subhead.

Published and in-progress Product Specifications

Currently (September 2022), the following Product Specifications are under development:

  • S-128, Catalogue of Nautical Products Edition 1.x
  • S-131, Marine Harbour Infrastructure Edition 1.0.0

The following Product Specifications have been published as of September 2022 and are available from the IHO Geospatial Information Registry, Product Specification Register.

  • S-122 Edition 1.0.0
  • S-123 Edition 1.0.0
  • S-127 Edition 1.0.0
  • S-128 Edition 1.0.0

Overlapping/Mixed Datasets

Note from Teledyne Caris initiating the discussion of the NIPWG use case for overlapping/mixed datasets: Word document