TSMAD25/DIPWG5 9.1B

IntroductionThe 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/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

Analysis/DiscussionUtilize 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 changeChanged type to booleanBecame part of a complex

Noted new features, removed features, changed features

RecommendationsDIPWG 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 DIPWGThe 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.

TSMAD26/DIPWG5 9.5A

IntroductionAs 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)

AnalysisS-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 completedWhile most is covered by the portrayal

catalogue, there still is a need to describe certain functionality

AnalysisLocated 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…

RecommendationAdd this work to the scope of the LUT review

groupOr

Form a new sub-working group to handle this review

This review should be fast tracked and a report submitted at the next TSMAD meetingThese 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

TSMAD26/DIPWG5 10.3A

IntroductionFollow 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.

AnalysisUKHO 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

Small scale spread of valuesScale No. of Cells

3000000 17

3121170 1

3500000 76

3604872 1

3750000 1

4860700 1

7000000 1

10000000 9

20000000 5

Largest Scale Spread of ValuesScale No. of Cells

500 1750 1

1000 121250 31500 171800 12000 932250 22400 52500 903000 463500 353600 33750 83800 33999 64000 775

Recommendationsan additional scale of 10,000,000 to reflect the

upper range of spatial resolutions.Add the following to the lower range of values

300020001000Anything 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 TSMAD26The TSMAD is invited to:

Agree to adding the following spatial resolutions to S-101: 10,000,000; 3,000; 2,000 and 1,000.

TSMAD26/DIPWG5 10.4A

IntroductionNoted 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

AnalysisAt 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 insetsCarry over of the meta feature M_CSCL

MINDSC = 22,000MAXDSC = 180,000

MIN = 12,000MAX = 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 19115. 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 19915 and therefore S-100 would have to be extended to handle this approach.

RecommendationThe 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 DIPWGThe TSMAD and DIPWG is invited to:

discuss the United States proposalagree to removing multiple dataCoverages

within a dataset for S-101

TSMAD26/DIPWG5 10.5A

IntroductionCurrently there is a lack of guidance on how

the updating process of FC and PC’s 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 Version OEM action Reason for version change ENC dataset version

1.0.0 1.0.0 Y Initial Draft 1.0.01.0.1 1.0.1 N Clarification to a

definition1.0.0

1.1.0 1.1.0 N Correction to a definition 1.0.01.2.0 Y Correction to portrayal 1.0.0

1.2.01.3.0 N Correction to DCEG 1.0.0

1.2.01.3.0

2.0.0 Y New feature added, new portrayal added

1.0.01.2.01.3.02.0.0

Option 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.

Option 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.

Option 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

Option 2: Additions to FCAdditions 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.

Option 2: Changes to the FCA 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 exampleChange 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

Option 2: Removal ExampleRemoval 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

Action required of TSMAD/DIPWGThe 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

TSMAD26/DIPWG5 10.7A

IntroductionSub working group formed to refine the

mappings of CSCL and M_CSCL for the convertor

This will provide a standard mapping for converted dataThere will be an override function for HO’s

that want to better control the mappings

Initial Results

IC-ENCS-57 Scale Ranges

(M_CSCL and CSCL)

AUS-57 Scale Ranges

(M_CSCL and CSCL)

USS-101

Maximum Display Scale

AUS-101

Maximum Display Scale

IC-ENCS-101

Maximum Display Scale

USS-101 Minimum Display Scale

AUS-101

Minimum Display Scale

IC-ENCS-101

Minimum Display Scale

1 - 4000 0 – 3,999 1 0 1 12,000 22,000 120004000 - 7999 4,000 – 7,999 4,000 4,000 2000 22,000 22,000 22000

8000 - 11999 8,000 – 11,999 8,000 8,000 4000 45,000 45,000 4500012000 - 21999 12,000 – 21,999 12,000 12,000 8000 90,000 90,000 9000022000 - 44999 22,000 – 44,999 22,000 22,000 12000 90,000 90,000 18000045000 - 89999 45,000 – 89,999 45,000 45,000 22000 180,000 180,000 35000090000 - 179999 90,000 – 179,999 90,000 90,000 45000 350,000 700,000 700000

180000 - 349999 180,000 – 349,999 180,000 180,000

90000700,000

700,000 1500000

350000 - 699999 350,000 – 699,999 350,000 350,000

1800001,500,000

1,500,000 3000000

700000 - 1499999 700,000 – 1,499,999 700,000 700,000

3500003,000,000 3,000,000

10000000

1500000 - 2999999 1,500,000 – 2,999,999 1,500,000 1,500,000

7000003,000,000 3,000,000

20000000

3000000- 3,000,000 - ?????? 3,000,000

3,000,000 15000003,000,000 3,000,000

50000000

AnalysisVery little concensusTransas 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.

Some 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?

Action Required of TSMAD

note the progress of the working groupdiscuss the question proposed in the

conclusion

S-101 Test StrategyA 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 ObjectivesTest Schedule

Resource planning

Test PlansTest DataTest Cases

DefectsTest ReportsTest Metrics

Bug TrackingBug Fixing

Bug Verification

HSSC ApprovalIHO Member

States Approval

ConclusionThis 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