[gdal-dev] Wrong interpretation of DIMENSION features in GDAL DXF driver

2017-01-13 Thread Nikolai Bezdna
I’ve found a bug in DXF driver: when reading features of type DIMENSION this driver translates them to multilinestrings, which is ok, but then puts unnecessary leading lines and rotates the main line (with arrows) to a horizontal state, which is really a wrong representation. Here are two screen

Re: [gdal-dev] C++11 timeline

2017-01-13 Thread Greg Troxel
Jürgen E. Fischer writes: > On Fri, 13. Jan 2017 at 06:42:26 +1000, Nyall Dawson wrote: >> FYI - the upcoming QGIS 3.0 release has a hard c++11 requirement. Not >> sure how much that affects things, but certainly projects which >> utilise GDAL are already switching to c++11. > > We're not using

Re: [gdal-dev] Usage of GDAL_FILENAME_IS_UTF8 config option

2017-01-13 Thread Ray Gardener
Just to add a small note regarding OS X (and iOS) and UTF-8 filenames: The HFS+ filesystem stores accented characters in decomposed form, which can differ from the filename given to an API that creates the file such as fopen(..., "wb"). Applications that store a filename (e.g. into a preferenc

[gdal-dev] PostGIS with more than one geometry column per table | R-Trees

2017-01-13 Thread Alexander . Berdnikow
Hi, sorry, there is a half copy of this post in the forum already, which was not accepted by the maillist. I translated a Table (Feature) of a PostGIS Database to a GeoPackage with GDAL. The Feature has two Linestring Geometries in the PostGIS DB. One geometry with exact positions of the net

Re: [gdal-dev] 2.1.3 next week ?

2017-01-13 Thread Jeff McKenna
+1 for 2.1.3 release -jeff -- Jeff McKenna MapServer Consulting and Training Services http://www.gatewaygeomatics.com/ On 2017-01-12 4:08 AM, Even Rouault wrote: Hi, I'm considering issuing a release candidate for 2.1.3 end of next week. Anything that should be in it that isn't already

Re: [gdal-dev] C++11 timeline

2017-01-13 Thread Damian Dixon
Hi, We are actively using GDAL on WIndows, Linux and Android to deal with GIS data reading gaps. Currently we are constrained to using 'gcc 4.7' on Linux, which gives us a lot of C++11 that we currently want to use. On Windows we have switched to Visual Studio 2015. On Android we will probably

Re: [gdal-dev] C++11 timeline

2017-01-13 Thread Jürgen E . Fischer
Hi, On Fri, 13. Jan 2017 at 06:42:26 +1000, Nyall Dawson wrote: > FYI - the upcoming QGIS 3.0 release has a hard c++11 requirement. Not > sure how much that affects things, but certainly projects which > utilise GDAL are already switching to c++11. We're not using the C++ API - so that shouldn't