HI Gdal,
Just wanted to follow this up.
Cheers,
Ian
From: Ian Reese
Sent: Monday, 12 March 2018 6:55 p.m.
To: gdal-dev@lists.osgeo.org
Subject: gdal_merge.py
Hi Gdal,
I am having some issues with gdal_merge.py.
When I merge two tifs together, the original nodata value is converted to 0, no
Hi Nicol,
I've been through the same problem.
Actually, I was helping someone that had that problem.
If I remember correctly, the SDK that you download from the site doesn't have
some needed components to build the GDAL driver.
You would need to register ($?) with that company to get the full
On Mon, Mar 26, 2018 at 10:51 PM, Kristian Evers wrote:
>
>
> On 26 Mar 2018, at 21:21, Markus Metz
> wrote:
>
> There is an important difference between the PROJ4 and the PROJ5+
> API/syntax:
>
> The old PROJ4 API uses latlong WGS84 as pivot datum
Hello List,
I am trying to compile GDAL 2.2.4 with TeighaFileConverter_4.3.2.0 (htt
ps://www.opendesign.com/guestfiles/teigha_file_converter).
The configure parameters are:
--with-teigha=/usr/bin/TeighaFileConverter_4.3.2.0 --with-teigha-
plt=Linux
Unfortunately the make command fails with:
In
I never did resolve this issue, but using the python libraries instead worked
out fine.
-s
From: Beale, Steven [mailto:steven.be...@woodplc.com]
Sent: Wednesday, March 21, 2018 3:39 PM
To: Zachary Flamig ; Steven Beale
Cc:
On mardi 27 mars 2018 15:11:31 CEST Raphael Das Gupta wrote:
> https://gis.stackexchange.com/q/274775/51574
If you use latest GDAL 2.2.4, you don't even need to add -setci to gdalwarp
The fact that the resulting raster doesn't display well by default with QGIS
2.18 (actually I also find it to be
Heya GDALers
Is someone here able to answer
https://gis.stackexchange.com/q/274775/51574 ? (I didn't get any answers
on GIS Stack Exchange, yet. If more information is needed, please let me
know here or on Stack Exchange.)
Is my approach (i.e. aiming to preserve color interpretation) even the
On 27/03/18 22:00, Even Rouault wrote:
> Ah that was apparently your actual need rather than limiting the number of
> drivers per-se. Do you have profiled where time was lost if you find opening
> too slow ? The identification logic of drivers is supposed to operate fast
> (extension based, or
On mardi 27 mars 2018 21:51:46 CEST Ben Elliston wrote:
> On 27/03/18 21:49, Even Rouault wrote:
> > Hum why would you need to call GDALAllRegister() if you already manually
> > registered some of them ?
>
> Because reordering the driver list by placing commonly used drivers at
> the head of the
On 27/03/18 21:49, Even Rouault wrote:
> Hum why would you need to call GDALAllRegister() if you already manually
> registered some of them ?
Because reordering the driver list by placing commonly used drivers at
the head of the list makes a significant difference in the time taken to
open
On mardi 27 mars 2018 21:09:41 CEST Ben Elliston wrote:
> Hi Even
>
> On 08/03/18 23:34, Even Rouault wrote:
> > If you use GDAL as a library from your own code (C/C++), you can also
> > directly call the GDALRegister_() / OGRRegister() functions you
> > are interested in, instead of
Hi Even
On 08/03/18 23:34, Even Rouault wrote:
> If you use GDAL as a library from your own code (C/C++), you can also
> directly call the GDALRegister_() / OGRRegister() functions you
> are interested in, instead of GDALAllRegister()
This is ideal, as it allows a handful of drivers to
12 matches
Mail list logo