|
|
(42 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. |
| | | |
− | The SNPWG Wiki administration is trying to provide the files in a convenient way; but we can not guarantee to fit all requirements.
| + | 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: <br> |
| + | * S-128, Catalogue of Nautical Products Edition 1.x |
| + | * S-131, Marine Harbour Infrastructure Edition 1.0.0 |
| | | |
− | ==UML Models==
| + | 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 |
| | | |
− | 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.
| + | == Overlapping/Mixed Datasets == |
| | | |
− | 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.
| + | 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]] |
− | | |
− | '''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===
| |
− | | |
− | [[User:Rmm|raphael]] 19:49, 7 October 2010 (UTC): MPA application schema in Enterprise architect format, for the SNPWG13 MPA product specification work can be downloaded here: [[Image:MPA_application_schema.zip]].
| |
− | | |
− | [[User:DavidAcland|DavidAcland]]: 14:50, 29 November 2010 (UTC) A slightly later version of the MPA application schema is shown here as a JPEG:<br>
| |
− | [[User:Jens|jens]] 12:05, 4 March 2011 (UTC) The image below shows that latest development status
| |
− | [[Image:MPA Domain Objects.jpg]]
| |
− | | |
− | ==Data Capture and Encoding Guide (DCEG)==
| |
− | | |
− | ===MPA DCEG===
| |
− | | |
− | The current status can be downloaded here [[Image:DCEG.doc]]
| |
− | | |
− | ==more==
| |
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