I have a lot of geotiffs which are quite large at times (meaning they have
quite a bit of unnecessary white space between) and I would like to run a
batch script to just do a simple compression on them as I believe that they
are not compressed because the files that just contain a lot of white spac
Hello,
I saw that gdal2tiles.py had been improved and is now multithreading (see
https://github.com/OSGeo/gdal/pull/201 ). Will be there the same improvements
for gdal_retile.py in the roadmap of gdal?
https://github.com/OSGeo/gdal/blob/master/gdal/swig/python/scripts/gdal_retile.py
_
i download the gdal from osgeo4w,and i write a demo to open mbtiles file,my
code is below
QString uri = "c:/test.mbtiles";
CPLErrorRest();
GDALDatasetH hDS = GDALOpen(uri.toUtf8().constData(),GA_ReadOnly);
if(!hDS)
{
...
}
the CPLGetLastErrorMsg() shows the error "C:/test.mbt
That was it. Thanks! I had not tried putting the shapefile as an option.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Hi,
If we want to keep up with our yearly release cycle, it is time considering
it. Unless someone volunteers to take the stick, I'd be willing to issue a
2.3.0beta1 for April 20th (the release/2.3 branch wil be forked at that time
to receive needed fixes and master will be labelled 2.4.0dev).
On mardi 3 avril 2018 08:40:10 CEST Andreas Oxenstierna wrote:
> Dear list
>
> How is OGR vector data compressed in PDF output from gdal_translate?
> Is the STREAM_COMPRESS option used?
Andreas,
Yes, vector geometries are deflate-compressed by default. I've just made the
doc clearer about this
Hi Ari,
> When fields are added to a layer, the field definition that is stored in
> the layer definition is created as a clone of the provided field definition.
>
> Neither field definitions nor geometry field definitions set the ignored
> flag of the clone.
>
> Is this a feature and not a bug?
When fields are added to a layer, the field definition that is stored in
the layer definition is created as a clone of the provided field definition.
Neither field definitions nor geometry field definitions set the ignored
flag of the clone.
Is this a feature and not a bug?
I was already mak
Here's a snippet of the code I use:
using (var ds = GDAL.Open(input, Access.GA_ReadOnly))
{
if (ds == null)
{
throw new Exception("Can't open GDAL dataset: " + input);
}
var options = new[]
{
"-of", "vrt",
"-overwrite",
