[gdal-dev] SetSpatialFilter and Spatial Index

2016-06-14 Thread Tomer
Hi, If I use the function SetSpatialFilter on a layer of a shp file with spatial index(.qix), will the function use the index to decide which features are suitable? Thanks, Tomer -- View this message in context: http://osgeo-org.1560.x6.nabble.com/SetSpatialFilter-and-Spatial-Index-tp5271637.

Re: [gdal-dev] libtool numbering policy

2016-06-14 Thread Greg Troxel
Even Rouault writes: >> Would you expect a C++ ABI change every release? > > Except for bugfixes releases, in practice yes for the yearly "feature" > release > ("feature" meaning here a change of major or minor in the "GDAL > major.minor.micro" scheme), as adding a new capability / virtual m

Re: [gdal-dev] Programmatic creation of VRT

2016-06-14 Thread Even Rouault
Le mardi 14 juin 2016 17:27:01, Julien Michel a écrit : > Dear all, > > Quick question about VRT programmatic creation. I have a list of files > corresponding to different tiles of an image and I am writing some code > to generate a mosaic VRT. For now I do it by directly writing XML to > iostream

Re: [gdal-dev] libtool numbering policy

2016-06-14 Thread Bas Couwenberg
On 2016-06-14 16:46, Even Rouault wrote: Le mardi 14 juin 2016 16:33:04, Bas Couwenberg a écrit : On 2016-06-14 15:51, Even Rouault wrote: > Le mardi 14 juin 2016 12:13:49, Bas Couwenberg a écrit : >> In Debian we mark the libgdal C++ symbols and add a dependency on the >> version specific virtu

[gdal-dev] Programmatic creation of VRT

2016-06-14 Thread Julien Michel
Dear all, Quick question about VRT programmatic creation. I have a list of files corresponding to different tiles of an image and I am writing some code to generate a mosaic VRT. For now I do it by directly writing XML to iostream but I saw that there is actually an API to do this in GDAL. Th

Re: [gdal-dev] libtool numbering policy

2016-06-14 Thread Even Rouault
Le mardi 14 juin 2016 16:33:04, Bas Couwenberg a écrit : > On 2016-06-14 15:51, Even Rouault wrote: > > Le mardi 14 juin 2016 12:13:49, Bas Couwenberg a écrit : > >> In Debian we mark the libgdal C++ symbols and add a dependency on the > >> version specific virtual ABI package provided by the libgd

Re: [gdal-dev] libtool numbering policy

2016-06-14 Thread Bas Couwenberg
On 2016-06-14 15:51, Even Rouault wrote: Le mardi 14 juin 2016 12:13:49, Bas Couwenberg a écrit : In Debian we mark the libgdal C++ symbols and add a dependency on the version specific virtual ABI package provided by the libgdal20 package to all packages that use any of the C++ symbols. Most rev

Re: [gdal-dev] libtool numbering policy

2016-06-14 Thread Even Rouault
Le mardi 14 juin 2016 16:02:14, Ari Jolma a écrit : > 14.06.2016, 16:51, Even Rouault kirjoitti: > > Side remark: I'm surprised to not see QGIS listed in the C API only > > users. I've never seen use of the GDAL C++ API in it. > > At least heatmap.cpp seems to include gdal_priv.h > > I don't have

Re: [gdal-dev] libtool numbering policy

2016-06-14 Thread Even Rouault
Le mardi 14 juin 2016 14:16:51, Greg Troxel a écrit : > Even Rouault writes: > > A ticket ( https://trac.osgeo.org/gdal/ticket/6542 ) has been raised > > about libtool SONAME having not changed between GDAL 2.0.X and GDAL > > 2.1.0 due to incrementing both LIBGDAL_CURRENT and LIBGDAL_AGE . > > Thi

Re: [gdal-dev] libtool numbering policy

2016-06-14 Thread Ari Jolma
14.06.2016, 16:51, Even Rouault kirjoitti: Side remark: I'm surprised to not see QGIS listed in the C API only users. I've never seen use of the GDAL C++ API in it. At least heatmap.cpp seems to include gdal_priv.h I don't have deeper knowledge why. Ari Same for Fiona & RasterIO

Re: [gdal-dev] libtool numbering policy

2016-06-14 Thread Even Rouault
Le mardi 14 juin 2016 12:13:49, Bas Couwenberg a écrit : > On 2016-06-14 11:29, Even Rouault wrote: > > A ticket ( https://trac.osgeo.org/gdal/ticket/6542 ) has been raised > > about > > libtool SONAME having not changed between GDAL 2.0.X and GDAL 2.1.0 due > > to > > incrementing both LIBGDAL_CUR

Re: [gdal-dev] libtool numbering policy

2016-06-14 Thread Greg Troxel
Even Rouault writes: > A ticket ( https://trac.osgeo.org/gdal/ticket/6542 ) has been raised about > libtool SONAME having not changed between GDAL 2.0.X and GDAL 2.1.0 due to > incrementing both LIBGDAL_CURRENT and LIBGDAL_AGE . > This was raised also in https://trac.osgeo.org/gdal/ticket/4543

Re: [gdal-dev] libtool numbering policy

2016-06-14 Thread Bas Couwenberg
On 2016-06-14 11:29, Even Rouault wrote: A ticket ( https://trac.osgeo.org/gdal/ticket/6542 ) has been raised about libtool SONAME having not changed between GDAL 2.0.X and GDAL 2.1.0 due to incrementing both LIBGDAL_CURRENT and LIBGDAL_AGE . This was raised also in https://trac.osgeo.org/gdal/

[gdal-dev] libtool numbering policy

2016-06-14 Thread Even Rouault
Hi, A ticket ( https://trac.osgeo.org/gdal/ticket/6542 ) has been raised about libtool SONAME having not changed between GDAL 2.0.X and GDAL 2.1.0 due to incrementing both LIBGDAL_CURRENT and LIBGDAL_AGE . This was raised also in https://trac.osgeo.org/gdal/ticket/4543 Our, more or less implici