Re: [gdal-dev] Getting the points from multipoints datatype

On 1 March 2017 at 17:26, Ahmed Tolba wrote: > Hi All, > > I’m trying to get the multi points out of a geometry, how would I retrieve > the points ? > > // Variable initialised to contain Geometry point data for the field at the > current index of i > >

Re: [gdal-dev] Adding more stuff to Python bindings

On mercredi 1 mars 2017 19:56:30 CET Alexander Bruy wrote: > nly > in C API. Are there any instructions about how to proceed? As I > understand, I need to add function declaration to the > swing/include/Operations.i Yes, in Operations.i, for things that are typically in gdal_alg.h . For other

[gdal-dev] Adding more stuff to Python bindings

Hi devs, I want to add to Python bindings some functions which currently are available only in C API. Are there any instructions about how to proceed? As I understand, I need to add function declaration to the swing/include/Operations.i and also add missed type definitions somewhere. Is this

[gdal-dev] Getting the points from multipoints datatype

Hi All, I'm trying to get the multi points out of a geometry, how would I retrieve the points ? // Variable initialised to contain Geometry point data for the field at the current index of i OGRGeometry *Geometry = Feature->GetGeometryRef();

Re: [gdal-dev] ENVI Rotation Bug Fix

Even, I already do direct tests with jp2kakdataset_test.cc with bazel and it works great. I can directly probe the methods without worrying about any other mechanism getting between the test and the class. e.g. I can directly mess with Identify, Open and any helpers. I can also do things like

Re: [gdal-dev] ENVI Rotation Bug Fix

Kurt, I don't think the ENVIDataset class is exported (and that's a good thing), so direct testing of the class might only be possible if you build without --with-hide-internal-symbols. Why can't you test through the public GDAL API instead of directly depnding on implementation details ?

Re: [gdal-dev] ENVI Rotation Bug Fix

Warning... I did a cleanup pass and split out the class definitions into a header to allow direct C++ testing. https://trac.osgeo.org/gdal/changeset/37530 https://trac.osgeo.org/gdal/changeset/37514 https://trac.osgeo.org/gdal/changeset/37510 I haven't written that testing yet, but it will be

Re: [gdal-dev] FW: Don't we have any ideas for GSoC 2017?

On mercredi 1 mars 2017 11:43:12 CET Rahkonen Jukka (MML) wrote: > Forwarding to the list because Jordan's trial was not successful. Sounds a good idea. I think potential students should be more pro-active in proposing and developing their own ideas. Regarding "indexing on VRT files", I guess

Re: [gdal-dev] FW: Don't we have any ideas for GSoC 2017?

Hi all, What would you devs think of a project to add to the interpolation algorithms in gdal_grid, e.g. TPS. It's something I do now with R, but it would nice to have this native in Gdal. If you think this is a good idea, I could try to set up something from the University of Amsterdam

[gdal-dev] FW: Don't we have any ideas for GSoC 2017?

Forwarding to the list because Jordan's trial was not successful. Jordan Bess wrote: Re: [gdal-dev] Don't we have any ideas for GSoC 2017? Vector tiles! Mbtiles or folder of pbf It would be great if OGR supported creation of vector tiles in protocol buff format Get Outlook for

Re: [gdal-dev] ENVI Rotation Bug Fix

Hi Taylor, M_PI is defined pretty much everywhere. The only compiler that you have to jump through hoops to get it is Visual Studio where you have to define '#define _USE_MATH_DEFINES'. As Even has mentioned it's also defined in the GDAL portability header. The main reason the use of atan