The S57 file we used to test with each language and it is read correctly in C#
& python, our c++ project is the problem. The S57 is the one generated in
"\gdal-3.4.1\autotest\ogr\data\s57" when we built gdal. But [ here is a link ](
https://drive.google.com/file/d/1AGCHEQMWHvs6IJgDW45KJvK6gm-r_
I’m an S57 expert. Send me the data - I’ll take a look, there’s a lot of leeway
with S57 and sometimes it trips up GDAL. I had issues with AML data before
which is similar…
Jonathan.
Sent from my iPhone
> On 27 Jan 2022, at 10:44, Momtchil Momtchev wrote:
>
>
>
>
> Your code looks O
Hi, Thx!, now is a lot more clear!, I have a shape with this CRS:
Coordinate Reference System:
User input: WGS 84 / UTM zone 19S
wkt:
PROJCRS["WGS 84 / UTM zone 19S",
BASEGEOGCRS["WGS 84",
DATUM["World Geodetic System 1984",
ELLIPSOID["WGS 84",6378137,298.257223563,
Hi,
The GDAL and OGR DODS drivers were announced to be planned for removal
for 3.5. Someone jumped yesterday in
https://github.com/OSGeo/gdal/issues/5173 to ask to keep them (or maybe
just one of the raster of vector one, but they didn't specify which one
they use).
To what extent is that s
Your code looks OK, can you send me the file too?
On 27/01/2022 03:34, dtho...@pivotmaritime.com wrote:
Here is the C++ code we have written to read the test s57 file.
https://pastebin.com/seXrkgmB
We feel that it is some setup stuff we have missed but can't find any
clear information.
