[gdal-dev] Possible bug in Intersects() method in 2.2.1

I believe there may be a bug in how Intersects() evaluates point against polygon boundary. I went on lengths about it here , but long story short if you Intersects() a point with a polygon boundary, it returns

Re: [gdal-dev] Countour polygons instead of lines

I too have run into this problem in the past, though I believe, if you are to use gdal_contour you have access to the underlying DEM/TIN/LAS, and if you have that it's much easier just converting it directly to polygons (using the technique Jamie posted, or similar ones). It could be a gdal_contour

Re: [gdal-dev] Countour polygons instead of lines

In cases of cliffs and such (i.e. sudden drops in altitude), traditional photogrammetric softwares like PCI and Erdas work with break lines, as in, you literally draw a line along edges you want computed discontinuously. That is not really practical to do in command-line GDAL, though you could impo

Re: [gdal-dev] OGC announces a new standard that improves the way information is referenced to the earth

I too took that understanding from the text, Ari. I'll read the specs later, but since they mention a lot Big Data and the raster <> vector integration, I imagine it is akin to a geometry collection, but encompassing a wider range of data types, and arranged in a pyramid/r-tree -esque environment f

[gdal-dev] Can't import ptrcreate from _gdal module

I'm trying to work with a tool that, in one of its functions, uses a set of _gdal methods regarding pointers (e.g. ptrcreate, ptradd, ptrvalue, etc.), but when I try to import the function it returns me: AttributeError: 'module' object has no attribute 'ptrcreate' Doing a dir(_gdal) returns me a

[gdal-dev] Standardization of Bounding Box structure

In OGR, the GetGeometry() method from the Geometry class returns a bounding box in the (xmin, xmax, ymin, ymax) structure. However, the SetSpatialFilterRect() method from the Layer class expects a bounding box in the (xmin, ymin, xmax, ymax) structure. This is a problem that can be worked around, b

[gdal-dev] Disk space problems when creating in-mem VRT

I'm trying to warp a pretty big raster (120601 x 162961) into a reprojected VRT. I can do that just fine when writing the VRT to disk, it finishes processing in about 15 seconds and generates a meager 3KB file. However, when trying to do the same with an in-memory VRT, it accuses unavailability of

[gdal-dev] Installing multiple GDAL versions in Windows?

How would I go about having multiple GDAL installs in a Windows environment? Specifically regarding setting the system variables GDAL_DATA and GDAL_DRIVER_PATH. Even if I append the value with "gdal_1_path;gdal_2_path;gdal_3_path" etc., only the first one is recognized. ___

[gdal-dev] Problem while building JPEG12

Not entirely sure this question should be posted here, but given that the wiki gives instructions on how to do it, and at least part of the code was written by Frank, I'm taking a leap. Sorry if it's the wrong place. So, the wiki states that building for 12-bits is just a matter of defining BITS_I

[gdal-dev] Problem building GDAL with GEOS on Cygwin

Hello list, I'm trying to build GDAL 2.3 on Cygwin, and have been running amok with the GEOS option. I present the correct path for the geos_config file during ./configure, it does not throw any error, but after configuration is done, GEOS support is marked as "no". And, sure enough, while the scri

[gdal-dev] Problems creating a VSI File on Windows

Hello list, I am trying to create a VSI File on Memory, in a W10 system, but am unsure how to proceed with path style. > VSIFILE* Mem = VSIFileFromMemBuffer("path", (GByte*) NewImg, (vsi_l_offset) (XSize * YSize), FALSE); > GDALDataset* DS = (GDALDataset*) GDALOpen("path", GA_ReadOnly); When doi