Re: [gdal-dev] RFC68: C++11 compilation mode - Call for vote on adoption

2017-09-08 Thread Andrew C Aitchison
On Fri, 8 Sep 2017, Even Rouault wrote: If you look at Linux platforms that have not a default C++11-ready compiler (ie gcc < 4.8) and are still security maintained, I don't think there are that many. In Ubuntu world, 12.04 is no longer security maintained since April or May this year. And 14.

Re: [gdal-dev] RFC68: C++11 compilation mode - Call for vote on adoption

2017-09-08 Thread Howard Butler
> On Sep 8, 2017, at 3:29 PM, Even Rouault wrote: > > If people really need to have recent GDAL on old platforms, they can use > backported toolchains, hire developers to backport the features they need to > older branches, etc... +1 for C++11 Howard ___

Re: [gdal-dev] RFC68: C++11 compilation mode - Call for vote on adoption

2017-09-08 Thread Even Rouault
Daniel, > It's not clear to me that the benefits of the C++11 requirement justify > the potential trouble for those who have to support platforms with older > compilers. I can understand your concerns, and I would personnaly have been fine with sticking with oldish C++ as well, but we must also

Re: [gdal-dev] RFC68: C++11 compilation mode - Call for vote on adoption

2017-09-08 Thread Daniel Morissette
On 2017-09-06 12:14 PM, Kurt Schwehr wrote: Now that Tamas has added the msvc2015/2-17SDK's, I'd like to call a vote by the PSC on RFC68: C++11 compilation mode. The draft is here: https://trac.osgeo.org/gdal/wiki/rfc68_cplusplus11 -Kurt +0 It's not clear to me that the benefits of the C

Re: [gdal-dev] Cloud Optimised GeoTiff format

2017-09-08 Thread daunnc
Clear, great! Sounds a bit sad though. My dreams faced with reality. At least it's definitely obvious how COG should be formed in a perfect world. Thanks again! -- Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html ___ gdal-dev ma

Re: [gdal-dev] Cloud Optimised GeoTiff format

2017-09-08 Thread Even Rouault
On vendredi 8 septembre 2017 09:35:33 CEST daunnc wrote: > Haha, awesome! > > A bit more context: I think that it could be a great thing to query TIFFs > directly (for instance) from AWS landsat bucket, and they already have > generated .ovr files which can be used, probably an additional extra qu

Re: [gdal-dev] Cloud Optimised GeoTiff format

2017-09-08 Thread daunnc
Haha, awesome! A bit more context: I think that it could be a great thing to query TIFFs directly (for instance) from AWS landsat bucket, and they already have generated .ovr files which can be used, probably an additional extra query would be not that bad. I didn't check segments ordering yet in

Re: [gdal-dev] Cloud Optimised GeoTiff format

2017-09-08 Thread Even Rouault
On vendredi 8 septembre 2017 08:50:36 CEST daunnc wrote: > Hi again! > > According to the validate_cloud_optimized_geotiff.py script, overviews can't > be stored in a separate .ovr files. Are there any reasons why it was done? Because as the dictator of the cloud optimized geotiff spec, I decided

[gdal-dev] Cloud Optimised GeoTiff format

2017-09-08 Thread daunnc
Hi again! According to the validate_cloud_optimized_geotiff.py script, overviews can't be stored in a separate .ovr files. Are there any reasons why it was done? Can in theory there be any problems related to overviews storage in a separate .ovr file? Thanks a lot in advance. -- Sent from: h

Re: [gdal-dev] RFC68: C++11 compilation mode - Call for vote on adoption

2017-09-08 Thread Jeff McKenna
On 2017-09-08 9:43 AM, jratike80 wrote: Kurt Schwehr-2 wrote Now that Tamas has added the msvc2015/2-17SDK's, I'd like to call a vote by the PSC on RFC68: C++11 compilation mode. MS4W binaries for GDAL based on MSVC 2015 have been out there since almost a year now; although the current stab

Re: [gdal-dev] RFC68: C++11 compilation mode - Call for vote on adoption

2017-09-08 Thread jratike80
Kurt Schwehr-2 wrote > Now that Tamas has added the msvc2015/2-17SDK's, I'd like to call a vote > by > the PSC on RFC68: C++11 compilation mode. +1 -Jukka Rahkonen- -- Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html ___ gdal-de

Re: [gdal-dev] RFC68: C++11 compilation mode - Call for vote on adoption

2017-09-08 Thread Even Rouault
On mercredi 6 septembre 2017 11:46:03 CEST Kurt Schwehr wrote: > Joaquim, > > Please give it another go at explaining what this use case is and the > issues with it. I didn't follow your comments about the need for VS2013. > If users are on a legacy compiler (w.r.t. to C++11), can they not be ser

Re: [gdal-dev] fix build with poppler 0.58.0

2017-09-08 Thread Even Rouault
David, Funny, because while you were sending this email, I was just working on this!, since someone else reported the issue in https://trac.osgeo.org/gdal/ticket/7033 Thanks for the patch. I've committed a changeset that is a bit a mix of your and my work (see ticket). Note that your original

[gdal-dev] fix build with poppler 0.58.0

2017-09-08 Thread David Tardon
Hi, As a part of update of poppler to 0.59.0 in Fedora, I patched all depending packages to build with the new Object API. You can find the patch for gdal here: https://src.fedoraproject.org/rpms/gdal/blob/f17cd7bb3ffb6e141cb0335393bee9a571f85b5b/f/0001-ad +apt-to-poppler-0.58.patch . Disclaimer:

Re: [gdal-dev] OpenEx not found - gdal_edit.py

2017-09-08 Thread Even Rouault
On vendredi 8 septembre 2017 02:13:42 CEST Asmita Amol Wankhede wrote: > Enviroment /OS - > > Ubuntu 16.04 - gdal 2.1.2 already installed with Python2.7 used to build > GDAL. > > VERSIONS - > > gdal 2.1.2 when installed bundled with the code : > '--with-python=%s ' > where s% is gdal_env['pytho

[gdal-dev] OpenEx not found - gdal_edit.py

2017-09-08 Thread Asmita Amol Wankhede
Enviroment /OS - Ubuntu 16.04 - gdal 2.1.2 already installed with Python2.7 used to build GDAL. VERSIONS - gdal 2.1.2 when installed bundled with the code : '--with-python=%s ' where s% is gdal_env['python_bin'], ISSUE- Trying to execute gdal_edit.py (or gdal2tiles.py, gdal_retile.py etc.) , f