[gdal-dev] #include tiffio.h in gtiff/libgeotiff/

The file frmts/gtiff/libgeotiff/xtiffio.h #include's "tiffio.h", which is in frmts/gtiff/libtiff. However, when compiling in this directory frmts/gtiff/libtiff is not included. In my Linux Mint the compiler picks up tiffio.h from /usr/include/x86_64-linux-gnu/ but when I compile in freebsd I g

Re: [gdal-dev] Use of C++ iterators in API

On 11 April 2018 at 14:40, Even Rouault wrote: > On mercredi 11 avril 2018 05:10:53 CEST Kurt Schwehr wrote: >> The auto&& is really confusing. > > A experimentally working alternative with miminal use of '&' is > > for( auto poLayer: poDS->GetLayers() ) <-- this is a plain OGRLayer* IMHO, i

Re: [gdal-dev] Use of C++ iterators in API

On Wed, Apr 11, 2018 at 8:40 AM, Even Rouault wrote: > On mercredi 11 avril 2018 05:10:53 CEST Kurt Schwehr wrote: > > The auto&& is really confusing. > > A experimentally working alternative with miminal use of '&' is > > for( auto poLayer: poDS->GetLayers() ) <-- this is a plain OGRLayer*

Re: [gdal-dev] Use of C++ iterators in API

On mercredi 11 avril 2018 05:10:53 CEST Kurt Schwehr wrote: > The auto&& is really confusing. A experimentally working alternative with miminal use of '&' is for( auto poLayer: poDS->GetLayers() ) <-- this is a plain OGRLayer* { for( auto& poFeature: *poLayer ) <-- this is a uni

Re: [gdal-dev] Use of C++ iterators in API

The auto&& is really confusing. -kurt On Tue, Apr 10, 2018 at 2:41 PM, Mateusz Loskot wrote: > On 10 April 2018 at 23:06, Even Rouault > wrote: > > On mardi 10 avril 2018 22:34:56 CEST Mateusz Loskot wrote: > >> On 10 April 2018 at 22:06, Even Rouault > wrote: > >> > > >> > Just wanted to adv

Re: [gdal-dev] GDALProgressFunc in RasterIO not called

On mercredi 11 avril 2018 02:03:27 CEST r.boeters wrote: > I'm using GDALDataset::RasterIO(..) > > to read WMS/WMTS/ECW. So not per band, nor per block. > > I want to be able to terminate this process, so I thought I c

[gdal-dev] GDALProgressFunc in RasterIO not called

I'm using GDALDataset::RasterIO(..) to read WMS/WMTS/ECW. So not per band, nor per block. I want to be able to terminate this process, so I thought I could pass a GDALProgressFunc function to get intermediate status u

Re: [gdal-dev] GDALProgressFunc in RasterIO not called

I'm so sorry, the code got lost The GDALProgressFunc is defined as this: int gdalProgressFunc(double dfComplete, const char *pszMessage, void *pProgressArg) { NLogger::LogMessage(Fasc(), NLogger::Info, "gdalProgressFunc called"); return 1; } Partial code where I'm reading the data (read