Open alvarosanuy opened 1 month ago
Based on this, we propose that those data producers not willing to see their S-102 datasets automatically loaded in ECDIS (e.g. only at mariners' request) leave the displayScale attribute values Empty. This action would leave the S-102 dataset without the minimum necessary information to allow the loading/unloading/rendering algorithm (refer to C-7) handle its display based on MSVS only. Its loading will require mariners' action.
In the absence of explicit attribution, a mapping could be provided from the approximateGridResolution to a min/max/opt display scale.
I think it's reasonable to require that any S-102 dataset has minDS and maxDS set in order to be correctly portrayed and used on the ECDIS. It should be a required validation test and we could expect the ECDIS to reject for display any datasets which don't have them set. So, we should make sure these go into the critical checks in S-158:102 (I suppose?).
Over and above this I think this question essentially revolves around whether the installed S-102 is considered as, basically, an ENC (i.e it's always loaded regardless) or whether it is an overlay which is discretionary. Currently all non S-101 datasets are "overlays" but I can see the point being made here. It would be an exception for the ECDIS OEM though to do this (not helped by S-100 not classifying product specs as "charts", "overlays" etc..)
I will try and schedule a discussion on this between interested parties and take it from there. It could be something which comes in in a phase 2 edition of the document? So maybe start with all non "chart" PSs as overlays and progress from there? I think more implementers (and ECDIS users) should probably be consulted on this.
So maybe start with all non "chart" PSs as overlays and progress from there?
Happy with that as a starting point. We submitted a paper to ENCWG9 and it has also been added to the S100WG9 agenda by Yong.
Should we define 'Chart layers' in S-98? It would refer to S-101 & S-102 (For Navigation) only.
Use case for consideration
In Australia, S-102 datasets will be created to be the 'S-100 equivalent' to our S-57 HDbENC. There will not be an' S-101 version' of our S-57 HDbENC.
Accordingly, and to retain consistent operational functionalities in a DF environment, the AHO would like to see that, Official S-102 navigational products ('notForNavigation=False') that have their minDS and maxDS populated (refer to Note: below) are:
Automatically Loaded/Unloaded/Rendered in harmony with S-101. This means using Display Scales as triggers (refer to C-7).
S-102 WLA over S-101 is activated by default (not at mariner's request) when the dataset is loaded in accordance with the encoded Display scales and the MSVS. We understand that the creation of the safety contour from the bathymetric grid data (S-102) based on the value set by the user is to be automatically triggered once an official, for navigation, S-102 datasets is loaded by the ECDIS.
The AHO is of the opinion that, the adjustment of S-102 depth values by S-104 should continue to be triggered 'at mariner's request' only.
Note: It is important to highlight that S-102 PS 3.0.0 does not have any of the DataCoverage Display Scale attributes set as mandatory (although it is strongly encouraged that Product Specifications mandate the use of one or more of the displayScale provided as part of S100_DataCoverage). Based on this, we propose that those data producers not willing to see their S-102 datasets automatically loaded in ECDIS (e.g. only at mariners' request) leave the displayScale attribute values Empty. This action would leave the S-102 dataset without the minimum necessary information to allow the loading/unloading/rendering algorithm (refer to C-7) handle its display based on MSVS only. Its loading will require mariners' action.
The topic is initially raised with the S-98 PT as we see the concept as an inter-product harmonization issue. (impacts C-4 & C-7). Having said this, we understand the topic will need discussions at the S-102PT level as well, mainly because they would need to update their DCEG to explain the practical implication of populating displayScales, or not. Additionally, we plan to raise the topic for discussion at the upcoming ENCWG meeting.
As always, data producers are responsible for ensuring their S-xx portfolio is complementary and is designed in a way the information provided by each S-100 layer enriches instead of conflicting/confusing mariners' navigational experience.