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.
Not really an issue to be resolved per se (so happy for this to be deleted/moved) but following on from last week's PT discussions about "contouring" portrayal, I have captured a couple of screen shots from Sea IQ of some trial S-102 data from Port of Melbourne. This data is generated as "shoal biased" pixels at 20 metre resolution, with SeaIQ defining the contour and go/no-go zones based on specified safety depth of 16.2 m. Point being that the derived contour, when viewed in raster mode, does trace around the pixel boundaries:
When viewed in vector mode, contouring behaviour does depend on whether the "Interpoloate contour line" option is toggled on/off:
Not really an issue to be resolved per se (so happy for this to be deleted/moved) but following on from last week's PT discussions about "contouring" portrayal, I have captured a couple of screen shots from Sea IQ of some trial S-102 data from Port of Melbourne. This data is generated as "shoal biased" pixels at 20 metre resolution, with SeaIQ defining the contour and go/no-go zones based on specified safety depth of 16.2 m. Point being that the derived contour, when viewed in raster mode, does trace around the pixel boundaries:
When viewed in vector mode, contouring behaviour does depend on whether the "Interpoloate contour line" option is toggled on/off:
![SeaIQ_20metre_screen_capture4](https://github.com/iho-ohi/S-102-Product-Specification/assets/130008223/48784600-6d7f-48c6-8cea-35f1ee86bb0a)