Hello, I would like to ask:
When I use GDAL 2.3.3 with proj4_4.9.3, I can convert the coordinate from
EPSG:4326 to EPSG:4326+5773(egm96_15.gtx) correctly with elevation value.
But when I use GDAL 3.0.0 with proj4_6.1.0, the elevation value of
coordinate unchange (Proj.db and egm file are found). Th
Thank you for your reply. PROJ version 5.2 builds successfully and never
pestered me for sqlite, so I don't think that would be the problem.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html
___
gdal-dev mailing list
gdal-dev@lis
Craig,
Notice that the recipe I gave you to build sqlite3 builds a dynamic lib, not a
static one. Might that be the cause?
Joaquim
|>-Original Message-
|>From: gdal-dev On Behalf Of CDelancy
|>Sent: Thursday, May 30, 2019 4:16 PM
|>To: gdal-dev@lists.osgeo.org
|>Subject: [gdal-dev] I c
I can't seem to get GDAL to statically link to PROJ when building.
In the nmake.opt file I changed PROJ_INCLUDE to point to my local copy of
the proj source and PROJ_LIBRARY to the exact path of the static lib I built
from Proj source, while uncommenting both lines.
Still, when I try to use ogr c
On jeudi 30 mai 2019 16:27:41 CEST Even Rouault wrote:
> On jeudi 30 mai 2019 10:17:35 CEST Andrew Bell wrote:
> > On Thu, May 30, 2019 at 5:06 AM Even Rouault
> >
> > wrote:
> > > On mercredi 29 mai 2019 20:38:02 CEST Andrew Bell wrote:
> > > > In earlier GDAL versions I could call
> > > >
> >
On jeudi 30 mai 2019 10:17:35 CEST Andrew Bell wrote:
> On Thu, May 30, 2019 at 5:06 AM Even Rouault
>
> wrote:
> > On mercredi 29 mai 2019 20:38:02 CEST Andrew Bell wrote:
> > > In earlier GDAL versions I could call
> > >
> > > SetFromUserInput("EPSG:4326+4326");
> > >
> > > without error. I
On Thu, May 30, 2019 at 5:06 AM Even Rouault
wrote:
> On mercredi 29 mai 2019 20:38:02 CEST Andrew Bell wrote:
> > In earlier GDAL versions I could call
> >
> > SetFromUserInput("EPSG:4326+4326");
> >
> > without error. I now get the following error:
> >
> > (Error) GDAL failure (1) SetCompoundC
>
> I find "STRILE" slightly jarring when reading the spec because it is a
> non-word with no obvious meaning. It's also distractingly close to
> "sterile". What would you think about "BLOCK" or "CHUNK"?
Ah, that's lingo used in libtiff, but BLOCK sounds good. Will change to that.
> Older versio
On mercredi 29 mai 2019 20:38:02 CEST Andrew Bell wrote:
> In earlier GDAL versions I could call
>
> SetFromUserInput("EPSG:4326+4326");
>
> without error. I now get the following error:
>
> (Error) GDAL failure (1) SetCompoundCS() fails, vertical component is not
> VERT_CS.
>
> Was this a fai
