search

iho-ohi / S-102-Product-Specification

It is opened to develop S-102 Bathymetric Surface Product Specification. The contents of this repository are not offical publication in force, therefore please check the final version on the IHO website.
Other
29 stars 12 forks source link

Question on Exchange Set Extensions #130

Open hasel001 opened 1 week ago

hasel001 commented 1 week ago

Brian Flick (GeoNavTech) approached me during a coffee break at S-100WG9 and ask for help finding answers about S-102 exchange sets. Below the asterisks is a quote from his email to me (with introductory material removed and the reference to an attached file modified to be a linked file, as XSD attachments are unsupported by this vehicle).

Any questions, comments, or suggestions are welcome. I will share a link to this issue with him, and hopefully he will join in the conversation here. Thanks in advance for all your help!

After downloading the Canada Sea trials data, I saw an Extension to the S100 ExchangeCatalog xsd called out in the S111 data.

s111 extension callout

My coworker informed me of datasets for S-102 that contain a similar extension to the S-100 exchange catalog within NOAA produced datasets. These are apparently found in the AWS buckets and conformant to S-102 2.1.0 (https://noaa-s102-pds.s3.amazonaws.com/index.html#ed2.1.0/national_bathymetric_source/).

I was able to find this file among some S-102 sources from the past, but I don’t know if I should expect to have to build support for exchange sets built using the extension definitions from this xsd http://www.iho.int/s102/2.0/xc ...

Please find the reference xsd linked here, which defines an extension to S100_DatasetDiscoveryMetadata called griddingMethod. Do you know how this might be used, or any pertinent details about why it matters to have this extension xsd built into an OEM system?

Also, please excuse my brevity on this matter, if there is any more information I can provide, I’ll be happy to get what information is necessary for you to forward to who might have the information I seek. Basically, do I need to build these extension exchange catalog xsds into an OEM system, or will they be phased out as S-100 reaches maturity?

Thank you so much!

-Brian

RohdeBSH commented 1 week ago

Hi,

This applies to the S-102 ed 2.1.0. The Attritbut “griddingMethod” was a special case within the ExchangeSet. However, this attribute no longer exists since ed 2.2.0. The S100_DatasetDiscoveryMetadata section of the ExchangeSet is based on the S-100. The S-102 only restricts the use of certain attributes in their multipicity or value range. In general, an ExchangeSet from editon 2.2.0 can therefore be validated without additional XSD files. Mapping these additional restrictions of the S-102 in the ExchangeSet with a new XSD file was a corresponding proposal from Primar during the S100WG9 meeting (see Issue #132 ).

In my opinion, the development work for the S-102 prior to Edition 3.0.0 should be discontinued. Everyone should only take care of edition 3.0.0, because this will be the productive edition for 01.01.2026. Everything else just wastes valuable resources. This applies in particular to Edition 2.1.0, as this is still based on S-100 ed. 4.0.0 and this is not permitted for the launch of S-1XX products.

Example ExchangeSet without signatures and signing: ExchangeSet_BalticSea-e-Nav-Project_20241113T065002.zip