[gdal-dev] GDAL memory management

Hi, I have been working with C/C++ and GDAL with GEOS for some time now and I have a question about GDAL memory management. I wonder if there are any memory management options or tips to control allocations and deallocations in the library since we are noticing performance problems as our data in

[gdal-dev] VRT file and CSV source with strange name: "Failed to open datasource"

Hi, I have this source CSV that I would like to manage via VRT file ogrinfo --debug ON CSV:"/vsicurl_streaming/https://docs.google.com/spreadsheets/d/e/2PACX-1vTwuYdMYS7vKJnTETwycLEGPFG2pwhxIlPMeChXuluRLjApQwhzEy_gUgsw_9lVRrAmGhAHWEj9LDV7/pub?gid=0&single=true&output=csv"; "pub?gid=0&single=true&o

Re: [gdal-dev] Clarifying AxisMappingStrategy for SpatialReference read from GeoJSON in gdal > 3

On mardi 28 avril 2020 16:24:32 CEST Yann-Sebastien Tremblay-Johnston wrote: > Hi, > > Tested using conda gdal 3.0.4 and gdal bundled with QGIS (3.0.4) > > From the documented changes in gdal > 3 with respect to honouring > coordinate order i.e. lat/lon order for EPSG:4326, I would expect that wh