Right. I changed the signature and removed the CPLFree() and now in GMT it also
... half works. The middle warnings are print from GMT but the other come from
GDAL and are like those you suppressed in your gdaltransform commit.
So, I should try to catch this type of cases where one can do the
> but raise the error when I change the order of the source and target (i.e.
> create the inverse mapping)
Sure, as that would trigger the non existing reverse operation.
>
> pSrcSRS = "+proj=airy +ellps=WGS84 +units=m"
> pDstSRS = "+proj=latlong +datum=WGS84"
>
> In this case, it even raises
I used the gdaltranslate example because I knew that it would much simpler for
you to test but, as I said first, this issue was raised by a call to GDAL from
GMT.
Looked again into it and what happens is that the
gmt_OGRCoordinateTransformation() call runs fine when
pSrcSRS = "+proj=latlong
On lundi 17 juin 2019 17:14:21 CEST Joaquim Manuel Freire Luís wrote:
> Well, I call it via GMT but that test is in GMT for a while and it used to
> pass.
>
> Anyway, I'll have to investigate this further because I rebuilt GDAL and now
> the gdaltransform works, but when I call it from GMT is
Talking about basics... Most of the SDK we download to build drivers comes with
an INSTALL file (.md or not) and that is what people usually look for when they
decide that they need to download and build a FOSS. But GDAL doesn't have that.
Yes, the information is there, somewhere but it would
Well, I call it via GMT but that test is in GMT for a while and it used to pass.
Anyway, I'll have to investigate this further because I rebuilt GDAL and now
the gdaltransform works, but when I call it from GMT is still fails.
The code is
> used to work before the GDAL3+PROJ6 combo.
That would be surprising: with GDAL 2.4 and PROJ < 6, you also get an error,
but with a different message:
$ gdalinfo --version
GDAL 2.4.1, released 2019/03/15
$ echo 4.897 52.371 | \
gdaltransform -s_srs +proj=longlat -t_srs "+proj=airy
Thanks,
This comes from our GMT tests and used to work before the GDAL3+PROJ6 combo.
And funny that it also half works when I run it from Julia. But not from GMT.
|>-Original Message-
|>From: Even Rouault
|>Sent: Monday, June 17, 2019 5:37 PM
|>To: gdal-dev@lists.osgeo.org
|>Cc:
On lundi 17 juin 2019 16:08:36 CEST Joaquim Manuel Freire Luís wrote:
> Even
>
> I'm seeing this failure with the airy conversion
>
> echo 4.897 52.371 | gdaltransform -s_srs +proj=longlat -t_srs +proj=airy
>
> ERROR 1: PROJ: proj_create: Error -50: malformed pipeline
> ERROR 6: Cannot find
Even
I'm seeing this failure with the airy conversion
echo 4.897 52.371 | gdaltransform -s_srs +proj=longlat -t_srs +proj=airy
ERROR 1: PROJ: proj_create: Error -50: malformed pipeline
ERROR 6: Cannot find coordinate operations from
`PROJCRS["unknown",BASEGEOGCRS["unknown",DATUM["World
On lundi 17 juin 2019 08:16:30 CEST Eli Adam wrote:
> On Mon, Jun 17, 2019 at 5:43 AM Even Rouault
wrote:
> > Hi,
> >
> > this is really great news ! Given my experience with the project, I'm
> > rather far from being representative of someone less familiar with it or
> > with a non- developer
On Mon, Jun 17, 2019 at 5:43 AM Even Rouault wrote:
>
> Hi,
>
> this is really great news ! Given my experience with the project, I'm rather
> far from being representative of someone less familiar with it or with a non-
> developer profile, so thoughts from the broader GDAL community on what
Hi,
this is really great news ! Given my experience with the project, I'm rather
far from being representative of someone less familiar with it or with a non-
developer profile, so thoughts from the broader GDAL community on what they
feel is the most missing would be welcome.
One thing I've
Hello,
I am trying to compile the gdal 2.1.2 and I have problems with the gcc.
Do you know what gcc version is necessary to compile?
Cheers,
Jorge
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
14 matches
Mail list logo
