[gdal-dev] RFC: int bFoo -> bool bFoo (simple case)

Hi all The large arrays on the stack RFC discussion was impressive. Here is a second RFC. I tried to use the experience of the first to improve this one. Thoughts on the simplest case of int bFoo to bool bFoo? https://goo.gl/hdzhXD I figure we need to discuss a bunch more of these before cons

Re: [gdal-dev] Starting a discussion on style and coding guidelines

https://docs.google.com/document/d/1O1B7LY13L532kXcYcB2EdO65m5LOCsqaqn5R9iJfSPU/pub The optimized stack .o is 1248 bytes and the on the heap vector is 1600 bytes with gcc 4.8. The cost of either is pretty small. So, if there are 100 of these in gdal, we are talking about 30-60K of extra object f

Re: [gdal-dev] Reading the same OSM data in multiple threads

Damian, > > I'm trying to speed up processing of OSM data by opening an OSM file into > multiple datasets in multiple threads. One dataset per thread. Each thread > is processing a separate section of data, basically tiling the data. > > I've however run into a scaling issue with the amount of m

Re: [gdal-dev] Reading the same OSM data in multiple threads

On Wed, 1 Jun 2016, Damian Dixon wrote: Hi, I'm trying to speed up processing of OSM data by opening an OSM file into multiple datasets in multiple threads. One dataset per thread. Each thread is processing a separate section of data, basically tiling the data. I've however run into a scaling

[gdal-dev] Reading the same OSM data in multiple threads

Hi, I'm trying to speed up processing of OSM data by opening an OSM file into multiple datasets in multiple threads. One dataset per thread. Each thread is processing a separate section of data, basically tiling the data. I've however run into a scaling issue with the amount of memory allocated p