2Introduction The DCEG is close to finalization This will form the backbone of the S-101 Feature CatalogueThe DCEG defines all the features, attributes, feature attribute combinations and spatial geometries that will go into the Feature Catalogue
3Analysis/DiscussionEven though the portrayal model will be decided on at this meeting, there is still a need to jump start S-101 portrayal.DIPWG can utilize the same approach that TSMAD did for preparing what needs to go into the S-101 Portrayal Catalogue
4Analysis/DiscussionUtilize a Look up Table approach and compare the existing S-52 LUTs to what has changed via the DCEGAn initial draft of this approach was done in June 2012It noted attributes that would need a global rule changeChanged type to booleanBecame part of a complexNoted new features, removed features, changed features
6RecommendationsDIPWG establish a small sub-working group to discuss and document the changes needed for S-101 portrayal based on the S-101 DCEG.It may be possible that the initial work can be completed under contract.
7Action Required of DIPWG The DIPWG is invited to:agree to the formation of a subworking group to develop revised rules for changes that have occurred in the S-101 DCEG.
9IntroductionAs the S-100 portrayal model is finalized – the S-101 component must be fast tracked.Most of the S-101 portrayal is contained within the portrayal catalogue and will be resolved by the newly formed S-101 portrayal subwg (hopefully it passed)
10AnalysisS-101 needs to provide all the necessary information needed for implementation. This includes pieces of S-52 that are still required for S-101Some initial work has been completedWhile most is covered by the portrayal catalogue, there still is a need to describe certain functionality
11Analysis Located in the implementation guidance Tidal Adjustment Physical DisplayUnitsSize of lines symbols and textColoursAbbreviationsOrganization of Display – including viewing groupsDate Dependant featuresDisplay ComponentsTypes of ECDIS SymbolsEtc…
12Recommendation Add this work to the scope of the LUT review group Form a new sub-working group to handle this reviewThis review should be fast tracked and a report submitted at the next TSMAD meetingThese will also have to be documented as a test case
13Action Required of DIPWG The DIPWG is invited to:agree to the formation of a sub-working group or add this as an additional item to the LUT sub-working group.
14Additional Min and Max Spatial Resolutions TSMAD26/DIPWG5 10.3A
15IntroductionFollow up to a United States comment regarding the need for additional resolutions at that lower and upper end of the spatial resolution tableTSMAD agreed in principle – but asked for further analysis on which scales should be added.
16AnalysisUKHO provided the United States with a spreadsheet that contained every cell in their AVCS service and the scale.12,012 cellsCreated a count of every scale to determine data clusters
17Small scale spread of values No. of Cells1717695
18Largest Scale Spread of Values No. of Cells500175010001212503150017180020009322502240052500903000463500353600375083800399964000775
19Recommendationsan additional scale of 10,000,000 to reflect the upper range of spatial resolutions.Add the following to the lower range of values300020001000Anything larger would be an ENC such as a port ENC that is built for a specific purpose and would have a specific product specification.
20Action Required of TSMAD26 The TSMAD is invited to:Agree to adding the following spatial resolutions to S-101: 10,000,000; 3,000; 2,000 and 1,000.
21Multiple DataCoverages in a single dataset for S-101 TSMAD26/DIPWG5 10.4A
22IntroductionNoted an inconsistency between the existing definition of dataCoverage and the data loading and unloading algorithmS-101 allows for multiple dataCoverages in a datasetAlgorithm does not clearly take this rule into account.This may lead to inconsistencies when data containing multiple dataCoverages is loaded into an ECDIS
23AnalysisAt one point S-101 only allowed for a single dataCoverage within a dataset.In the past two years it was amended to be allowed to contain multiple dataCoverages of different scalesUnited States feels that this rule is based on the current principle of paper chart scheming with the concept of insetsCarry over of the meta feature M_CSCL
24S-101 Data Coverage MIN = 4,000 MAX = 22,000 MINDSC = 22,000 MAXDSC = 180,000MIN = 4,000MAX = 22,000MIN = 12,000MAX = 90,000
25Single dataCoverage reasoning It would simplify data loading and unloading of the ENC if the ECDIS only had to worry about a single dataCoverage within the datasetIn S-101 Hydrographic Offices still have to assign the appropriate scale range to the dataset and create a new ENC. It is relatively simple to extract the inset data and create a separate ENC.It will allow S-101 to no longer be tied to paper charts.It would simplify one of the more complicated aspects of an ECDIS where they have to account for embedded M_CSCL features and display them properly.This would align with ISO. The concept of a dataset within a dataset (what is in S-101) is inconsistent with ISO Geographic Information standards, including ISO In having this concept, TSMAD is moving away from the ISO approach and is inconsistent with the goals of S-100 being aligned with ISO.It makes metadata more complex as it is not supported by ISO and therefore S-100 would have to be extended to handle this approach.
26RecommendationThe United States is recommending that TSMAD reconsider its use of multiple dataCoverages within a dataset based on the reasons stated above.Although it would still be feasible to have multiple dataCoverages within the same dataset if they are of the same maximum and minimum display scale
27Action Required of TSMAD and DIPWG The TSMAD and DIPWG is invited to:discuss the United States proposalagree to removing multiple dataCoverages within a dataset for S-101
28Feature and Portrayal Catalogue Management TSMAD26/DIPWG5 10.5A
29IntroductionCurrently there is a lack of guidance on how the updating process of FC and PC’s are to behave on the ECDISIn reality – at any given time there will be ENC data that is built on two or more editions of the S-101 product specificationTSMAD needs to determine how this should be managed
30Analysis (potential scenario) S-101 Product Specification versionFC/PC VersionOEM actionReason for version changeENC dataset version1.0.0YInitial Draft1.0.1NClarification to a definition1.1.0Correction to a definition1.2.0Correction to portrayal1.3.0Correction to DCEG2.0.0New feature added, new portrayal addedAt any given point in time there may be different datasets available that are tied to different versions of the product specification. The main reason is that some hydrographic offices may not need to move to that version of the product specification as the changes do not affect their area of responsibility. The most likely scenario is that at any given time all HO’s will be in a mixed state of product specifications. For example, once a new product specification is introduced the HO will move all new edition publications to that version; however, older data that does not need a new edition will remain on the previous version.As this mixed state will be a reality, S-101 must provide some implementation guidance for the ECDIS on how to treat this issue.
31Option 1ECDIS manages multiple feature and portrayal catalogs in order to correctly portrayal data that was created on different versions of the product specification. The metadata associated with each dataset notates which product specification it is tied toThe IHO should also specify a sunset clause for different editions of product specificationsThere will have to be specific guidance that states OEMs must be able to read valid versions of the product specification feature and portrayal catalogues and ensure that data that is associated with that version must be properly displayed.
32Option 2For each new edition of the product specification, a cumulative feature and portrayal catalog is released. Therefore the ECDIS will only have to manage a single feature catalog and portrayal catalog.
33Option 2: RulesA key principle is each version a feature catalogue is tied to the version of the product specification.A single feature catalogue must be backwards compatible with existing data. Older FC data must load when a newer FC is in use.Data can only be issued conforming to the new catalogue when that catalogue has been published.Data must not load if it conforms to a FC not held by the system
34Option 2: Additions to FC Additions Example – The addition of a new Topmark FeatureA new Topmark is proposed to TSMADTSMAD agree the addition and it’s submitted to the registry and added to a revised Feature Catalogue.The feature catalogue is tested by producers and ECDIS manufacturers.The catalogue is published and made available. (Along with an uptick in the Product Specification)Producers begin to encode the new values.In systems which do not have the latest catalogue datasets conforming to it will not load data conforming to the new catalogue.Data conforming to older catalogues still loads.
35Option 2: Changes to the FC A change can be a complex attribute replacing a simple attribute or the removal of a feature, attribute or feature attribute. The following rules must apply;Changes where data is currently encoded in this way must be additions for example a complex attribute in addition to an existing simple attribute. Existing data can then be deprecated (sunset).Removals must only be made when no ENC data contains these values. TSMAD will manage deprecation of items through the DCEG.
36Option 2: Change example Change Example - A new complex is created for light sectorsA proposal is made to create a complex for light sectors, thus replacing SECTR1 and SECTR2TSMAD agree the addition and it’s submitted to the registry and added to a revised Feature Catalogue.The feature catalogue is tested by producers and ECDIS manufacturers.The catalogue is published and made available. (Along with an uptick in the Product Specification)Producers begin to encode the new values.In systems which do not have the latest catalogue datasets conforming to it will not load data conforming to the new catalogue.Data conforming to older catalogues still loads
37Option 2: Removal Example Removal Example – Values are removed from the feature catalogueAs a result of the creation of a complex attribute the attribute values SECTR1 and SECTR2 are removed from the feature catalogue.TSMAD agree the removal and it’s submitted to the registry and removed from a revised Feature Catalogue.The feature catalogue is tested by producers and ECDIS manufacturers.The catalogue is published and made available. (Along with an uptick in the Product Specification)Producers begin to encode the new values.In systems which do not have the latest catalogue datasets conforming to it will not load data conforming to the new catalogue.Data conforming to older catalogues still loads
38Action required of TSMAD/DIPWG The TSMAD/DIPWG is invited to:discuss the proposed options for FC/PC managementdecide which option should be included in S-101 and subsequently tested
39S-101 Min and Max Display Convertor Values TSMAD26/DIPWG5 10.7A
40IntroductionSub working group formed to refine the mappings of CSCL and M_CSCL for the convertorThis will provide a standard mapping for converted dataThere will be an override function for HO’s that want to better control the mappings
42Analysis Very little concensus Transas pointed out scenarios that should be part of the test bedUser is in the middle of the ocean and he sees several AIS targets (looks at his route, radar overlay, etc.). He zooms in his display and overview cell (the only available) disappears from his screen.User approaching the coast and there are overview cell 1:1,500,000 and approach cell 1:75,000. Their min/max display scales do not overlap that means only one cell in time will be loaded.
43Some QuestionsOne of the concepts that needs to be determined is does the Maximum display scale also represent the data compilation scale? Or does it represent the maximum scale that the data should be used to safely navigate with?
44Action Required of TSMAD note the progress of the working groupdiscuss the question proposed in the conclusion
46S-101 Test Strategy A draft test strategy has been developed Goals of the S-100/S101 Test bedTest processDefect managementForms the guidance for the S-+101 test bed and interactive test processes.NOT to be confused with a TEST PLAN
47IHO Member States Approval Test StrategyTest DevelopmentTest ExecutionDefect ManagementDeliveryTest ObjectivesTest ScheduleResource planningTest PlansTest DataTest CasesDefectsTest ReportsTest MetricsBug TrackingBug FixingBug VerificationHSSC ApprovalIHO Member States Approval
48Test Processes Identify Performance Acceptance Criteria Plan and Design TestsConfigure Test EnvironmentImplement Test DesignExecute TestsAnalyze, Report, and RetestFinalize S-101
49Levels of Testing Sea Trials S-101 Approval Shore Trials Unit TestingFunctional TestingShore TrialsS-101 ApprovalSea Trials
50ConclusionThis is a work in progress and will need to have a small meeting to further refine thisNot sure what the status of the S-101 Test case contract is?Can we move forward without the portrayal requirements?We can let out a follow on contract for that piece of work