[gdal-dev] Support for S-100 and S-102

[Mike]

The multiple field/subfields - I think gdal already does this for S-57 on
DSID. It just prefixes the subfields with the field name.

However -side note:  it seems the DSID_ISDT (issue date) is incorrect, it
just has the same value as DSID_UADT (update application date).

On Thu, Aug 30, 2018, 4:27 AM kusala nine <kusala9 at googlemail.com> wrote:

> The biggest work item for S-100 compatibility would be an update to the
> GDAL/OGR drivers for iso8211 in order to parse the S-101 iso8211 encoding.
> S-101 is the candidate replacement for S-57 ENC data - so, at some point
> all of NOAA's S-57 marine data will be available as S-101 datasets too.
> There's various improvements in S-101 over the old S-57 standard including
> dynamic feature catalogues and complex attributes on features but the main
> issue is that the iso8211 encoding uses concatenated iso8211 data
> structures (where you can have repeated field/subfields concatenated with
> simple (i.e non-repeating ones)). The current GDAL I believe doesn't parse
> these correctly so can't be used to parse S-101 data. I am invovled with
> the IHO team developing the standard but the main data format/spec and
> encoding are all pretty much done and there are converters/datasets
> available if anyone is able to take on the work - not sure if there's NOAA
> funding for it? It would be a huge step forward in the rollout to have an
> open source parser for this data....
>
> Jonathan.
>
> On 29 August 2018 at 20:41, Even Rouault <even.rouault at spatialys.com>
> wrote:
>
>> All,
>>
>> I've committed in GDAL master various improvements in the BAG driver,
>> around
>> two main directions:
>> - read support for variable resolution BAG, with resampling and
>> interpolation
>> options
>> - creating of (single resolution) BAG files from other GDAL datasets
>>
>> Updated documentation available at https://gdal.org/frmt_bag.html
>>
>> This work has been made possible through NOAA funding.
>>
>> Best regards,
>>
>> Even
>>
>>
>> > I'd be happy to connect anyone with the folks at NOAA, CCOM-JHC, and
>> > elsewhere who have been participating in drafting S-10x.  I only sat in
>> on
>> > a few of the meetings long ago.
>> >
>> > Specs should eventually end up here...
>> > https://www.iho.int/iho_pubs/IHO_Download.htm#S-100
>> >
>> > On Thu, Jul 5, 2018 at 10:43 AM, Even Rouault <
>> even.rouault at spatialys.com>
>> >
>> > wrote:
>> > > Kelly,
>> > >
>> > > > I know GDAL/OGR supports S-57 format, but could not see where it
>> > > > supports
>> > > > S-100.
>> > > >
>> > > > Is there a plan to support the latest IHO S-100 and S-102 standards
>> in
>> > >
>> > > the
>> > >
>> > > > near future?
>> > >
>> > > I'm not aware of anyone working on that currently.
>> > >
>> > > I had difficulties finding concrete documentation about those
>> standards
>> > > (specification and test products). From my quick search, it looks
>> like :
>> > > - S-100 is a conceptual model,
>> > > - S-101 is for ENC encoding, a successor of S-57. Apparently still
>> using
>> > > ISO-8211 for low level encoding.
>> > > - S-102 is bathymetric grid encoding in GeoTIFF or in BAG. So should
>> be
>> > > already handled by GDAL
>> > >
>> > > Even
>> > >
>> > > --
>> > > Spatialys - Geospatial professional services
>> > > http://www.spatialys.com
>> > > _______________________________________________
>> > > gdal-dev mailing list
>> > > gdal-dev at lists.osgeo.org
>> > > https://lists.osgeo.org/mailman/listinfo/gdal-dev
>>
>>
>> --
>> Spatialys - Geospatial professional services
>> http://www.spatialys.com
>> _______________________________________________
>> gdal-dev mailing list
>> gdal-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/gdal-dev
>
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20180830/7a75c2ef/attachment-0001.html>