Presentation on theme: "TSMAD25/DIPWG5 9.1B. Introduction The DCEG is close to finalization This will form the backbone of the S-101 Feature Catalogue The DCEG defines all the."— Presentation transcript:
Introduction The DCEG is close to finalization This will form the backbone of the S-101 Feature Catalogue The DCEG defines all the features, attributes, feature attribute combinations and spatial geometries that will go into the Feature Catalogue
Analysis/Discussion Even 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
Analysis/Discussion Utilize a Look up Table approach and compare the existing S-52 LUTs to what has changed via the DCEG An initial draft of this approach was done in June 2012 It noted attributes that would need a global rule change Changed type to boolean Became part of a complex Noted new features, removed features, changed features
Sample document (9.1C)
Recommendations DIPWG 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.
Action 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.
Introduction As 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)
Analysis S-101 needs to provide all the necessary information needed for implementation. This includes pieces of S- 52 that are still required for S-101 Some initial work has been completed While most is covered by the portrayal catalogue, there still is a need to describe certain functionality
Analysis Located in the implementation guidance Tidal Adjustment Physical Display Units Size of lines symbols and text Colours Abbreviations Organization of Display – including viewing groups Date Dependant features Display Components Types of ECDIS Symbols Etc…
Recommendation Add this work to the scope of the LUT review group Or Form a new sub-working group to handle this review This review should be fast tracked and a report submitted at the next TSMAD meeting These will also have to be documented as a test case
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. Action Required of DIPWG
Introduction Follow up to a United States comment regarding the need for additional resolutions at that lower and upper end of the spatial resolution table TSMAD agreed in principle – but asked for further analysis on which scales should be added.
Analysis UKHO provided the United States with a spreadsheet that contained every cell in their AVCS service and the scale. 12,012 cells Created a count of every scale to determine data clusters
Small scale spread of values ScaleNo. of Cells
Largest Scale Spread of Values ScaleNo. of Cells
Recommendations an additional scale of 10,000,000 to reflect the upper range of spatial resolutions. Add the following to the lower range of values Anything larger would be an ENC such as a port ENC that is built for a specific purpose and would have a specific product specification.
Action 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.
Introduction Noted an inconsistency between the existing definition of dataCoverage and the data loading and unloading algorithm S-101 allows for multiple dataCoverages in a dataset Algorithm does not clearly take this rule into account. This may lead to inconsistencies when data containing multiple dataCoverages is loaded into an ECDIS
Analysis At 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 scales United States feels that this rule is based on the current principle of paper chart scheming with the concept of insets Carry over of the meta feature M_CSCL
S-101 Data Coverage MINDSC = 22,000 MAXDSC = 180,000 MIN = 12,000 MAX = 90,000 MIN = 4,000 MAX = 22,000
Single 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 dataset In 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.
Recommendation The 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
Action Required of TSMAD and DIPWG The TSMAD and DIPWG is invited to: discuss the United States proposal agree to removing multiple dataCoverages within a dataset for S-101
Introduction Currently there is a lack of guidance on how the updating process of FC and PCs are to behave on the ECDIS In reality – at any given time there will be ENC data that is built on two or more editions of the S-101 product specification TSMAD needs to determine how this should be managed
Analysis (potential scenario) S-101 Product Specification version FC/PC VersionOEM actionReason for version changeENC dataset version YInitial Draft NClarification to a definition NCorrection to a definition YCorrection to portrayal NCorrection to DCEG YNew feature added, new portrayal added
Option 1 ECDIS 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 to The IHO should also specify a sunset clause for different editions of product specifications There 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.
Option 2 For 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.
Option 2: Rules A 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
Option 2: Additions to FC Additions Example – The addition of a new Topmark Feature A new Topmark is proposed to TSMAD TSMAD agree the addition and its 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.
Option 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.
Option 2: Change example Change Example - A new complex is created for light sectors A proposal is made to create a complex for light sectors, thus replacing SECTR1 and SECTR2 TSMAD agree the addition and its 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
Option 2: Removal Example Removal Example – Values are removed from the feature catalogue As 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 its 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
Action required of TSMAD/DIPWG The TSMAD/DIPWG is invited to: discuss the proposed options for FC/PC management decide which option should be included in S-101 and subsequently tested
Introduction Sub working group formed to refine the mappings of CSCL and M_CSCL for the convertor This will provide a standard mapping for converted data There will be an override function for HOs that want to better control the mappings
Initial Results IC-ENC S-57 Scale Ranges (M_CSCL and CSCL) AU S-57 Scale Ranges (M_CSCL and CSCL) US S-101 Maximum Display Scale AU S-101 Maximum Display Scale IC-ENC S-101 Maximum Display Scale US S-101 Minimum Display Scale AU S-101 Minimum Display Scale IC-ENC S-101 Minimum Display Scale – 3, ,000 22, ,000 – 7,9994, , ,000 – 11,9998, , ,000 – 21,99912, , ,000 – 44,99922, , ,000 – 89,99945, , ,000 – 179,99990, , , ,000 – 349,999180, , ,000 – 699,999350, ,500, ,000 – 1,499,999700, ,000, ,500,000 – 2,999,9991,500, ,000, ,000,000 - ??????3,000, ,000,
Analysis Very little concensus Transas pointed out scenarios that should be part of the test bed User 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.
Some Questions One 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?
Action Required of TSMAD note the progress of the working group discuss the question proposed in the conclusion
S-101 Test Strategy A draft test strategy has been developed Goals of the S-100/S101 Test bed Test process Defect management Forms the guidance for the S-+101 test bed and interactive test processes. NOT to be confused with a TEST PLAN
Test Objectives Test Schedule Resource planning Test Plans Test Data Test Cases Defects Test Reports Test Metrics Bug Tracking Bug Fixing Bug Verification HSSC Approval IHO Member States Approval
Identify Performance Acceptance CriteriaPlan and Design TestsConfigure Test EnvironmentImplement Test DesignExecute TestsAnalyze, Report, and RetestFinalize S-101 Test Processes
Unit Testing Functional Testing Shore Trials S-101 Approval Sea Trials Levels of Testing
Conclusion This is a work in progress and will need to have a small meeting to further refine this Not 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