Hi,
To sum up a few scattered discussions from the beginning of the year, my
intent is to tag a GDAL 2.2.0beta1 release on 14th April. The 2.2 branch
will be created from that to stabilize it, and trunk will be then 2.3dev. A RC
should likely be produced end of April if things go well.
Does th
On jeudi 30 mars 2017 16:51:49 CEST Mateusz Loskot wrote:
> On 30 March 2017 at 16:48, Even Rouault wrote:
> > On jeudi 30 mars 2017 07:34:35 CEST Kurt Schwehr wrote:
> >> At one point, I had a autoconf configure setup that was pretty minimal.
> >>
> >> While it built, it was not so much fun to w
On 30 March 2017 at 16:48, Even Rouault wrote:
> On jeudi 30 mars 2017 07:34:35 CEST Kurt Schwehr wrote:
>
>> At one point, I had a autoconf configure setup that was pretty minimal.
>
>> While it built, it was not so much fun to work with. Here are some
>
>> remnants of notes that might constitut
On jeudi 30 mars 2017 07:34:35 CEST Kurt Schwehr wrote:
> At one point, I had a autoconf configure setup that was pretty minimal.
> While it built, it was not so much fun to work with. Here are some
> remnants of notes that might constitute the beginnings of a
> sourceme-minimal.sh. More will lik
Some possibly useful notes...
I use bazel for a restricted build. Here are a few key files/directories
that I've found to be in surprising places that are hard or impossible to
go without:
frmts/gtiff/
frmts/hfa/hfa_overviews.cpp
frmts/iso8211/
frmts/mem/memdataset.cpp
frmts/pds/nasakeywordhandl
On jeudi 30 mars 2017 12:59:09 CEST Vautour, André (INT) wrote:
> Hi all,
>
> We recently updated from 1.11.x to 2.1.3.
>
> Previously, GDAL had the ODrCDeleteDataSource capability, which the
> OGRMemDriver did not handle in its TestCapability implementation. So, in
> effect, the memory driver di
Hi all,
We recently updated from 1.11.x to 2.1.3.
Previously, GDAL had the ODrCDeleteDataSource capability, which the
OGRMemDriver did not handle in its TestCapability implementation. So, in
effect, the memory driver did not support deletion, which makes sense to me.
>From what I can tell, tha
Hi Gane,
You can try to use Cmake build of GDAL
(https://github.com/nextgis-borsch/lib_gdal).
It can be configured via CMake-gui or command line.
This is an example of minimal static build of GDAL -
https://github.com/nextgis/nextgis_datastore/blob/master/cmake/extlib.cmake#L94-L175
Best r
Hi Gane,
it might be slightly heretic, but I succeeded in a similar task by using
GDAL version 1.11. In that version there seem to be much less
interdependencies between the dlls under Windows, and I guess it will be
the same under Unix.
I found out by starting the projects without any GDAL-dl
Dear All,
I'm using postgres database with OGR.
I have altered the database encoding to WIN1250 by using that statement ALTER
DATABASE tinyows SET client_encoding=WIN1250;
OGR still can't read the fields, and I got an assertion that the characters
don't lie in the range -1, 255
CPLValueType CPLG
10 matches
Mail list logo
