Le jeudi 02 juin 2016 20:50:20, Jose Gomez-Dans a écrit :
> Hello,
>
> I have just installed GDAL 2.1.0 on some test systems. I mostly use the
> Python bindings and the shell tools in Unix (e.g. gdalinfo and so on, with
> a slant on GDAL, but also use OGR from time to time). Are the changes in
> t
Hello,
I have just installed GDAL 2.1.0 on some test systems. I mostly use the
Python bindings and the shell tools in Unix (e.g. gdalinfo and so on, with
a slant on GDAL, but also use OGR from time to time). Are the changes in
the Python bindings and/or tools going from 1.11.x to 2.1 documented
so
Thanks for the reply's.
We are doing a lot of processing of the data and need to retain that data
in a vector format.
For now we are disabling the multi-threading for OSM data and bumping up
the memory allowed to be allocated by a significant amount.
We will probably go with converting OSM to Sp
Le jeudi 02 juin 2016 00:46:06, Kurt Schwehr a écrit :
> https://docs.google.com/document/d/1O1B7LY13L532kXcYcB2EdO65m5LOCsqaqn5R9iJ
> fSPU/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
>
On 2 June 2016 at 00:59, Kurt Schwehr wrote:
> 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
Re
>
> Thoughts on the simplest case of int bFoo to bool bFoo?
>
> https://goo.gl/hdzhXD
Looks good to me
You could perhaps have made it a bit more compact for readability (dropping
e.g. alternatives and the historic remark about bool not being supported by
ancient C++ compilers) and start with
