[gdal-dev] ogr2ogr GML GML_INVERT_AXIS_ORDER_IF_LAT_LONG not working

2017-03-21 Thread andye
Folks related to a recent post about updating ogr2ogr. Seems there maybe something else afoot. I'm trying to export a GML3 file. I'm running into what appears to be a known issue with LAT\LONG being swapped based on the projection. The following creates a file which is formatted correctly except

[gdal-dev] Can you update just update the ogr2ogr.exe compiled binary in an existing directory

2017-03-21 Thread andye
I'm using ogr2ogr from one of the "bin" directories of QGIS(Wien). It's complaining about GML3_LONGSRS. Can I get ogr2ogr.exe from GISInternals nightly build and just update the exe? -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Can-you-update-just-update-the-ogr2ogr-exe

Re: [gdal-dev] +/-infinity as an uninitialized marker

2017-03-21 Thread Even Rouault
On mardi 21 mars 2017 16:11:44 CET Mateusz Loskot wrote: > On 21 March 2017 at 15:50, Kurt Schwehr wrote: > > Hey Even, > > > > Probably not a big deal, but I'm curious why you didn't use !isinf(MinX) > > or > > isfinite(MinX) for your recent OGREnvelope patch: > > > > int IsInit() const { retu

Re: [gdal-dev] +/-infinity as an uninitialized marker

2017-03-21 Thread Mateusz Loskot
On 21 March 2017 at 16:09, Even Rouault wrote: > I've considered isinf() but I know we have had issues in some environments > with isinf() being a macro, and thus std::isinf() ending up > std::something_different Yes, indeed. There's been lots of problems, in GEOS too. BTW, one of anti-macro exp

Re: [gdal-dev] +/-infinity as an uninitialized marker

2017-03-21 Thread Mateusz Loskot
On 21 March 2017 at 15:50, Kurt Schwehr wrote: > Hey Even, > > Probably not a big deal, but I'm curious why you didn't use !isinf(MinX) or > isfinite(MinX) for your recent OGREnvelope patch: > > int IsInit() const { return MinX != > std::numeric_limits::infinity(); } Portability wank: it's also

Re: [gdal-dev] +/-infinity as an uninitialized marker

2017-03-21 Thread Even Rouault
On mardi 21 mars 2017 07:50:34 CET Kurt Schwehr wrote: > Hey Even, > > Probably not a big deal, but I'm curious why you didn't use !isinf(MinX) or > isfinite(MinX) for your recent OGREnvelope patch: > > int IsInit() const { return MinX != > std::numeric_limits::infinity(); } > > My only thought

[gdal-dev] +/-infinity as an uninitialized marker

2017-03-21 Thread Kurt Schwehr
Hey Even, Probably not a big deal, but I'm curious why you didn't use !isinf(MinX) or isfinite(MinX) for your recent OGREnvelope patch: int IsInit() const { return MinX != std::numeric_limits::infinity(); } My only thought is that if something goes totally messy and it uses !isinf or isfinite,

[gdal-dev] Selecting from Geometry

2017-03-21 Thread Ahmed Tolba
Hi All, Suppose I have a geom (geometry) that has multipoints, I would like to query for all the points that are within latitude longtitude altitude, is that possible ? what's the sql query for that ? I'm a beginner so excuse me. SELECT * FROM nation WHERE OGR_GEOMETRY='MULTIPOINT' ??? 2) My s

Re: [gdal-dev] Why does OGREnvelope default to valid values when uninitialized?

2017-03-21 Thread Even Rouault
On mardi 21 mars 2017 12:14:52 CET Vautour, André (INT) wrote: > Hi all, > > We've recently updated from GDAL 1.11.x to GDAL 2.1.x and ran into some > failing unit tests. > > I can simplify the failure to: > > OGRPoint aPoint(0.0, 0.0); > OGRPoint anotherPoint(1.0, 1.0); > OGRMultiPoint multiPoi

[gdal-dev] Why does OGREnvelope default to valid values when uninitialized?

2017-03-21 Thread INT
Hi all, We've recently updated from GDAL 1.11.x to GDAL 2.1.x and ran into some failing unit tests. I can simplify the failure to: OGRPoint aPoint(0.0, 0.0); OGRPoint anotherPoint(1.0, 1.0); OGRMultiPoint multiPoint; multiPoint.addGeometry(&aPoint); multiPoint.addGeometry(&anotherPoint); OGREn

Re: [gdal-dev] Help requested: Concurrent read of a GeoTiff

2017-03-21 Thread Grégory Bataille
hum... debugging in the C layers, that'll be interesting... Ok, I'll continue to dig in, thanks --- Gregory Bataille On Tue, Mar 21, 2017 at 8:44 AM, Even Rouault wrote: > On mardi 21 mars 2017 05:51:18 CET Grégory Bataille wrote: > > > Hey Even, > > > > > > reaching out again, because I just

Re: [gdal-dev] small typo - the page of the WMTS driver

2017-03-21 Thread Even Rouault
On mardi 21 mars 2017 01:28:28 CET lucvanlinden wrote: > Hi > > There is a small typo (closing tag of zoomlevel) on the page of the WMTS -- > OGC Web Map Tile Service: > > http://www.gdal.org/frmt_wmts.html > > > int_value > > should be > > int_value > Thanks Luc. Fixed (in svn, website w

[gdal-dev] small typo - the page of the WMTS driver

2017-03-21 Thread lucvanlinden
Hi There is a small typo (closing tag of zoomlevel) on the page of the WMTS -- OGC Web Map Tile Service: http://www.gdal.org/frmt_wmts.html int_value should be int_value Regards Luc -- View this message in context: http://osgeo-org.1560.x6.nabble.com/small-typo-the-page-of-the-WMTS-d

Re: [gdal-dev] Help requested: Concurrent read of a GeoTiff

2017-03-21 Thread Even Rouault
On mardi 21 mars 2017 05:51:18 CET Grégory Bataille wrote: > Hey Even, > > reaching out again, because I just don't know... > > so here is gdal2tiles_parallel strategy (as far as I understand it) > - in each process, open the input file, compute the autowarped vrt (in the > case of the dataset I