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

2018-08-30 Thread Mike
I can't get to it right now, but the new date would be found in the update file. So this would only occur on cells with updates. If I open an update file (.001+) in a text editor, I see the date on the second line. I'm just using the first cell found @ www.charts.noaa.gov/ENCs/ENCsIndv.shtml (US1A

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

2018-08-30 Thread kusala nine
ah - the situation you're describing is subtly different. That's when you have two 8211 fields concatenated together, so e.g the DSID/DSSI are concatenated into a single 8211 record at the head of a standard S-57 ENC. What I'm talking about is when a single 8211 field has repeating subfield groups

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

2018-08-30 Thread Even Rouault
On jeudi 30 août 2018 07:29:12 CEST Mike wrote: > 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_UA

Re: [gdal-dev] PG driver: apply custom sql files together with loading data in one transaction

2018-08-30 Thread Even Rouault
On jeudi 30 août 2018 11:44:10 CEST Martin Landa wrote: > Hi, > > I have a Python application which loads data into PostGIS DB using > GDAL Python API. Input files are processed in one transaction (done on > datasource level). After loading data there some custom SQL files > applied (currently imp

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

2018-08-30 Thread 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

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

2018-08-30 Thread kusala nine
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

[gdal-dev] PG driver: apply custom sql files together with loading data in one transaction

2018-08-30 Thread Martin Landa
Hi, I have a Python application which loads data into PostGIS DB using GDAL Python API. Input files are processed in one transaction (done on datasource level). After loading data there some custom SQL files applied (currently implemented using psycopg2). There is a request to perform loading data