Hi,
I'm using GDAL since 2012 and one of the first things I've read is this:
https://trac.osgeo.org/gdal/wiki/GdalOgrInPython
The first mention of the deprecation of this import was added 13 years
ago. To quote from there:
"
Additionally, there are five compatibility modules that are include
Hi,
I call OSRImportFromProj4 with
"+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0
+k=1.0 +units=m +nadgrids=@null +towgs84=0,0,0,0,0,0,0 +wktext +no_defs"
and with the returned handle i get the major and minor axis (
OSRGetSemiMajor/OSRGetSemiMinor). I would expect the b
Do your shapefiles include a code page file (*.cpg)? If not, maybe that
would help.
On Wed, Nov 4, 2020 at 2:57 AM Aneta Muslić wrote:
> Hello,
>
> I am using gdal version 2.4.4 in my c# app.
> As a part of my project I am creating pdf with gdal_translate command.
> GDAL translate command is
> *
Hi,
As noted in https://github.com/OSGeo/gdal/issues/3149, the old way of
importing the Python bindings with "import gdal" instead of "from osgeo import
gdal" was accidentally broken in 3.2.0 . The old way has been officially
deprecated for many years.
Any opinion if we should just acknowledge
Hi:
I tried to use gdal with java in window 10,and I installed gdal from the
pre-built binary from “https://www.gisinternals.com/“.
Then I set the required environment variables by following this topic:
https://docs.geoserver.org/stable/en/user/data/raster/gdal.html
After that, I tried to validate
