again,
André
From: Even Rouault
Sent: April 22, 2022 13:47
To: Vautour, André (INT) ; gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] BAG CRS
External Email
André,
hum ok. it might perhaps be possible that WKT2 could come when extract the
vertical part but I still can't reproduce that t
(INT) a écrit :
Sorry Even,
I should have done more research on my end up front before sending
this. A client told us his WKT 2.0 BAG was created with GDAL. Looking
at it some more, it was the vertical CRS that was WKT 2.0.
Their vertical CRS looked as follows:
VERTCRS["ellipse",VDATUM
011) / UTM zone 10N +
ellipse"],CS[vertical,1],AXIS["ellipsoid height
(h)",up,LENGTHUNIT["metre",1]]]
Cheers,
André
From: Even Rouault
Sent: April 22, 2022 13:22
To: Vautour, André (INT) ; gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] BAG CRS
External Em
Just to be clear, I believe we are talking about the vertical wkt string
provided through the VAR_VERT_WKT creation option. Not the horizontal
coordinate system.
On Fri, Apr 22, 2022 at 12:01 PM Vautour, André (INT) <
andre.vaut...@teledyne.com> wrote:
> Hi all,
>
>
>
> It has just come to my at
André,
I don't confirm this trying:
$ gdal_translate autotest/gcore/data/byte.tif byte.bag
$ gdalinfo byte.bag -mdd xml:BAG | grep PROJCS
PROJCS["NAD27 / UTM zone
11N",GEOGCS["NAD27",DATUM["North_American_Datum_1927",SPHEROID["Clarke
1866",6378206.4,294.978698213898,AUTHORITY["EPS
Hi all,
It has just come to my attention that the BAG driver in GDAL is writing the CRS
with a WKT codeSpace and a WKT 2.0 string as the code. While I am fairly sure
we started that incorrect practice here at CARIS with a WKT 1.0 string, this is
the first time I've seen a WKT 2.0 string written
