[gdal-dev] Building GDAL using MSBuild

I have a quick question: does anyone know if anyone has attempted to build GDAL using MSBuild. I am planning on writing an MSBuild script for GDAL so it can more easily be built in Jenkins. Thanks, Nigel [http://www.1spatial.com/signatures/1SpatialLogo_Small.jpg]

Re: [gdal-dev] jpeg2000/jasper error compiling gdal 2.1 from git release branch

Awesome, patch works as expected and gdal builds against the latest jasper. Thanks a lot. diff --git a/frmts/jpeg2000/jpeg2000_vsil_io.cpp b/frmts/jpeg2000/jpeg2000_vsil_io.cpp index 74f1e64..3a948d0 100644 --- a/frmts/jpeg2000/jpeg2000_vsil_io.cpp +++ b/frmts/jpeg2000/jpeg2000_vsil_io.cpp

Re: [gdal-dev] jpeg2000/jasper error compiling gdal 2.1 from git release branch

On mercredi 7 décembre 2016 11:19:11 CET Donovan Cameron wrote: > On 07/12/16 10:41 AM, Even Rouault wrote: > > You could as well replace the JAS_CAST(uchar *, buf); by > > JAS_CAST(unsigned char*, buf) > > Thanks Even, that's helpful. > > Whereabouts would I try to make this patch? Not sure

Re: [gdal-dev] jpeg2000/jasper error compiling gdal 2.1 from git release branch

On 07/12/16 10:41 AM, Even Rouault wrote: You could as well replace the JAS_CAST(uchar *, buf); by JAS_CAST(unsigned char*, buf) Thanks Even, that's helpful. Whereabouts would I try to make this patch? Not sure what file to look for to do this. Sorry! -- Kind regards, Donovan

Re: [gdal-dev] jpeg2000/jasper error compiling gdal 2.1 from git release branch

Downgrading jasper to 1.900.5 results in a successful build. On 07/12/16 10:22 AM, Donovan Cameron wrote: Morning Everyone! Jasper was update in Arch Linux today and trying to build gdal 2.1 from the git 2.1 release branch (r36743) the compile fails with a jpeg2000 + jasper error: make

[gdal-dev] jpeg2000/jasper error compiling gdal 2.1 from git release branch

Morning Everyone! Jasper was update in Arch Linux today and trying to build gdal 2.1 from the git 2.1 release branch (r36743) the compile fails with a jpeg2000 + jasper error: make -C jpeg2000 install-obj make[2]: Entering directory '/tmp/makepkg/gdal-filegdb/src/gdal-2.1/frmts/jpeg2000'

Re: [gdal-dev] [gdal 2.1] ecw 5.2.1

On mercredi 7 décembre 2016 14:31:33 CET Vincent BERNAT wrote: > Thanks for reply Jeff :) > > There are lots of things about ecw 2.3.3 which is compiling for me. > But not the 5.2.1 with gcc 5.1.0 > > my problem is about link... > > In the 2.3.3 i had : > - libNCSEcwC.so > - libNCSEcw.so > -

Re: [gdal-dev] [gdal 2.1] ecw 5.2.1

Thanks for reply Jeff :) There are lots of things about ecw 2.3.3 which is compiling for me. But not the 5.2.1 with gcc 5.1.0 my problem is about link... In the 2.3.3 i had : - libNCSEcwC.so - libNCSEcw.so - libNCSCnet.so - libNCSCUtil.so but in ECW 5.2.1, i only got : - libNCSEcw.so -

Re: [gdal-dev] [gdal 2.1] ecw 5.2.1

Thanks for reply Jeff :) There are lots of things about ecw 2.3.3 which is compiling for me. But not the 5.2.1 with gcc 5.1.0 it's about link... In the 2.3.3 i had : - libNCSEcwC.so - libNCSEcwC.so - libNCSEcwC.so De : gdal-dev

Re: [gdal-dev] [gdal 2.1] ecw 5.2.1

Hi Vincent, You might also review the BuildHints wiki page, that we all try to keep uptodate, for ECW at https://trac.osgeo.org/gdal/wiki/ECW And if you notice something missing (like a tip for CentOS users) please definitely edit that wiki page and add it. Hopefully this helps a little.

[gdal-dev] [gdal 2.1] ecw 5.2.1

Hi all, I work with gdal-2.1.0 on CentOS I would like to compil with ECW 5.2.1 so i add in the configure : --with-ecw=/usr/local/hexagon but i get the following message when compiling : libgdal.so : undefined reference to 'NCS::CView::SetTransformList (...) libgdal.so : undefined reference

Re: [gdal-dev] GDAL and ElasticSearch 5.0

On lundi 21 novembre 2016 17:26:45 CET Even Rouault wrote: > Hi, > > I've just tested and confirm that ES 5.0 isn't compatible of current driver. > I've created https://trac.osgeo.org/gdal/ticket/6724 to track this. I've just committed into trunk support for ES 5.0 Even -- Spatialys -

Re: [gdal-dev] Call for discussion on RFC 64: Triangle, Polyhedral surface and TIN

Hi, Perhaps some problem with markup, the WKT dows show in Nabble http://osgeo-org.1560.x6.nabble.com/gdal-dev-Call-for-discussion-on-RFC-64-Triangle-Polyhedral-surface-and-TIN-tc5298840.html MULTIPOLYGON ((( 553 352, 327 363, 442 486, 553 352 )), (( 327 363, 553 352, 422 186, 327 363 )))

Re: [gdal-dev] Call for discussion on RFC 64: Triangle, Polyhedral surface and TIN

On mercredi 7 décembre 2016 02:01:54 CET jratike80 wrote: > Even Rouault-2 wrote > > > Hi, > > > > This is a call to discuss the proposed RFC 64: Triangle, Polyhedral > > surface and TIN > > > > https://trac.osgeo.org/gdal/wiki/rfc64_triangle_polyhedralsurface_tin > > > > ~ > > I am

Re: [gdal-dev] Call for discussion on RFC 64: Triangle, Polyhedral surface and TIN

> Thanks Even, I was thinking of preserving an indexed mesh, with (for > example) a constrained triangulation. Simple features will ingest this, but > once it comes back out vertex de-duplication would be enough to restore the > indexing. You'd need some record of vertex identity after they are

Re: [gdal-dev] Call for discussion on RFC 64: Triangle, Polyhedral surface and TIN

On Wed, 7 Dec 2016 at 07:41 Even Rouault wrote: > On mardi 6 décembre 2016 20:31:57 CET Michael Sumner wrote: > > > Thanks Even, > > > > > > Does a TriangulatedSurface consist of separate Triangles, all with each > > > three vertices stored explicitly? I.e. is there

Re: [gdal-dev] Call for discussion on RFC 64: Triangle, Polyhedral surface and TIN

Even Rouault-2 wrote > Hi, > > This is a call to discuss the proposed RFC 64: Triangle, Polyhedral > surface and TIN > > https://trac.osgeo.org/gdal/wiki/rfc64_triangle_polyhedralsurface_tin > > ~ I am wondering this part: "GEOS methods are still used in some cases, but with the