Re: [gdal-dev] Native library load failed while using gdal maven dependency - UnsatisfiedLinkError

2016-02-10 Thread ssaniev
So the solution for using gdal bindings in java was to install the proper version which came with all the dll's and simply using the jar from the maven repo. I installed core gdal installer in windows, and set my environment variables, and gdal jar started to work correctly in my maven project.

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Ari Jolma
10.02.2016, 15:21, Kurt Schwehr kirjoitti: One request: #define OGR_G_NOT_EMPTY_POINT 0x1 #define OGR_G_3D 0x2 #define OGR_G_MEASURED 0x4 #define OGR_G_IGNORE_MEASURED 0x8 Can you make these a static const int or static const unsigned int member of the OGRGeometry class? #defines make life

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Ari Jolma
I've started a wiki page for the status of the drivers regarding measured geometries: https://trac.osgeo.org/gdal/wiki/MeasuredGeometriesInDrivers Ari 10.02.2016, 15:05, Even Rouault kirjoitti: Le mercredi 10 février 2016 13:53:28, Peter Halls a écrit : Types on page 2). PointZ A PointZ

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Kurt Schwehr
OGRGeometry::OGR_G_NOT_EMPTY_POINT On Wed, Feb 10, 2016 at 7:34 AM, Ari Jolma wrote: > > 10.02.2016, 15:21, Kurt Schwehr kirjoitti: > >> >> One request: >> >> #define OGR_G_NOT_EMPTY_POINT 0x1 >> #define OGR_G_3D 0x2 >> #define OGR_G_MEASURED 0x4 >> #define

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Mike Toews
On 11 February 2016 at 01:31, Even Rouault wrote: > Le mercredi 10 février 2016 13:05:20, Peter Halls a écrit : >> ESRI handle this in a non-intuitive way: XYM is supported, but Z >> always has a Measure, so is XYZM! The formal definition is here: >>

Re: [gdal-dev] NetCDF+HDF5 and threadsafety

2016-02-10 Thread William Kyngesburye
Finally got a chance to test this. With HDF5 built with thread safety, without HL (of course, no NetCDF4), the multireadtest has no problems on a HDF5 file. The opposite - no thread safety + HL and NetCDF4, I get a bunch of "pointer being freed was not allocated" errors. If I force HL +

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Ari Jolma
One more issue came up. Shapefiles, which have Z will also have M, at least a placeholder for it. Having shapefiles as XYZM always in that case may be problematic. It is possible to use the open options SHPT=type to override the default. We could have Z => XYZ as default for backwards

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Even Rouault
Le mercredi 10 février 2016 12:26:59, Ari Jolma a écrit : > One more issue came up. > > Shapefiles, which have Z will also have M, at least a placeholder for it. > > Having shapefiles as XYZM always in that case may be problematic. Small precision for those not necessarily familiar with the

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Even Rouault
Le mercredi 10 février 2016 13:05:20, Peter Halls a écrit : > Ari, et al, > > ESRI handle this in a non-intuitive way: XYM is supported, but Z > always has a Measure, so is XYZM! The formal definition is here: > https://www.*esri*.com/library/whitepapers/pdfs/*shapefile*.pdf (1998) >

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Even Rouault
Le mercredi 10 février 2016 13:22:49, Ari Jolma a écrit : > 10.02.2016, 13:55, Even Rouault kirjoitti: > > Le mercredi 10 février 2016 12:26:59, Ari Jolma a écrit : > >> One more issue came up. > >> > >> Shapefiles, which have Z will also have M, at least a placeholder for > >> it. > >> > >>

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Jukka Rahkonen
Ari Jolma gmail.com> writes: > > > One more issue came up. > Shapefiles, which have Z will also have M, at least a placeholder > for it. > Having shapefiles as XYZM always in that case may be problematic. > It is possible to use the open options SHPT=type to override the >

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Peter Halls
Ari, et al, ESRI handle this in a non-intuitive way: XYM is supported, but Z always has a Measure, so is XYZM! The formal definition is here: https://www.*esri*.com/library/whitepapers/pdfs/*shapefile*.pdf (1998) Shape Types having Z are defined on pp19ff where it states:

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Ari Jolma
10.02.2016, 13:55, Even Rouault kirjoitti: Le mercredi 10 février 2016 12:26:59, Ari Jolma a écrit : One more issue came up. Shapefiles, which have Z will also have M, at least a placeholder for it. Having shapefiles as XYZM always in that case may be problematic. Small precision for those

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Peter Halls
> Types on page 2). > PointZ > A PointZ consists of a triplet of double-precision coordinates in the order > X, Y, Z plus a measure" > > I had misinterpreted their meaning of "optional" here and submitted a > documentation query to ESRI on being told I was wrong. The response was > that M being

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Even Rouault
Le mercredi 10 février 2016 13:53:28, Peter Halls a écrit : > > Types on page 2). > > PointZ > > A PointZ consists of a triplet of double-precision coordinates in the > > order > > > X, Y, Z plus a measure" > > > > I had misinterpreted their meaning of "optional" here and submitted a > >

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Kurt Schwehr
I'm +0. Neither for nor against. One request: #define OGR_G_NOT_EMPTY_POINT 0x1 #define OGR_G_3D 0x2 #define OGR_G_MEASURED 0x4 #define OGR_G_IGNORE_MEASURED 0x8 Can you make these a static const int or static const unsigned int member of the OGRGeometry class? #defines make life more

Re: [gdal-dev] RFC 61: Call for vote on adoption

2016-02-10 Thread Mike Toews
On 11 February 2016 at 02:05, Even Rouault wrote: > Would someone looking at this discussion and having access to ESRI software be > willing to generate tiny (meaning just one single shape, with the smallest > number of vertices) shapefiles of type PointZ, ArcZ,