Note that the same logic should be applied to the spatial features, if
these are handled (i.e. RETURN_PRIMITIVES=ON).
And for feature-feature links, i.e. RETURN_LINKAGES=ON
Thank you all for your explanations.
I'm sad that this is a mistake in the doc :-) because as you pointed out S57
spec has no GUID definition. With the combination of the LNAM + DSNM, it
allowed to have one that would be convenient in a PostGIS database that
contains many S-57 charts.
On my fork of GDAL I add this attribute DSNM (as defined in the previous
documentation), and since the DSNM field is mandatory in the S57 spec I did
not detect any problem. (Tested with several S57 source US, UK, ES, HR, ... )
In case it would be helpful, I could make a PR.
-- loïc
On 3 May 2020, at 12:49, Even Rouault <[email protected]> wrote:
On dimanche 3 mai 2020 09:54:22 CEST kusala nine wrote:
DSNM is dataset name. I'ts defined in the DSID which only occurs in the
first field/subfield group in the dataset - not sure what the driver does
in respect of it.
Right. The driver doc was incorrect. I've just fixed it per
https://github.com/OSGeo/gdal/commit/c0722aed716e01fa3ab0ccc20fb911369baa3721
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
--
Best Regards
Andreas Oxenstierna
T-Kartor Geospatial AB
Olof Mohlins väg 12 Kristianstad
mobile: +46 733 206831
mailto: [email protected]
http://www.t-kartor.com
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
