This may be a similar problem to what was mentioned here:
#6721: Simplifing use of gdalwarp with cutline with non-georeferenced
rasters
https://trac.osgeo.org/gdal/ticket/6721
(which has not been reacted to)
There the gal was to use gdalwarp, together with a cutline, to cut out a
portion of the
On mardi 29 novembre 2016 16:02:23 CET Tim Waters wrote:
> Hello,
>
> I'm seeing an error running GDAL 1.11.3 on Ubuntu 16.04LTS and 2.10.
> There was no error and it worked fine with GDAL 1.10.1 on Ubuntu
> 14.04LTS.
>
> I see the error running gdal_rasterize utility and also in python.
>
>
Hello,
I'm seeing an error running GDAL 1.11.3 on Ubuntu 16.04LTS and 2.10.
There was no error and it worked fine with GDAL 1.10.1 on Ubuntu
14.04LTS.
I see the error running gdal_rasterize utility and also in python.
gdal_rasterize -i -burn 17 -b 1 -b 2 -b 3 clipping.gml -l features
I want to use GDALDataset::ExecuteSQL() to get a layer containing feature
attributes selected by the user, and the geometry of the feature.
When I did this in GDAL 1.11.x, I automatically got the geometry, but now I
don't.
If I get the OGRFeatureDefn for the layer, and then get the
With a little help GDAL picks up correct extent. Removing the erroneous
WGS84BoundingBox hint from GetCapabilities made it.
I consider that there is a bug in the WMTS server which is advertising invalid
bounding box but I don't really know GDAL should do.
I am not good at reading the code from
Thanks for letting me know Even.
I've raised a ticket here: https://trac.osgeo.org/gdal/ticket/6733
First ticket I've done so wasn't sure about some of the fields, have left as
defaults.
If anything further is required please let me know.
Rob
DISCLAIMER: The information contained in this
