[gdal-dev] undefined reference to `json_object_new_array linking with libgdal.a

Dear all, I am trying to compile a programme on Ubuntu 20.04 that links with libgdal.a. The compiler fails with this message: /usr/bin/ld: /usr/lib/libgdal.a(ogrfeature.o): in function `OGRFeature::GetFieldAsSerializedJSon(int) const': (.text+0x3861): undefined reference to `json_object_new_arr

Re: [gdal-dev] undefined reference to `json_object_new_array linking with libgdal.a

Luí­s, normally GDAL builds out-of-the-box regarding libjson-c on Ubuntu. You have 2 possibilities, install libjson-c-dev, or let GDAL use its internal copy of libjson-c. In your linking attempts, this should be rather -ljson-c than -ljson, but normally you shouldn't have to do that. Even --

[gdal-dev] Appropriate place to store CEP50 in Geotiff

Hi, I am inquiring to know if there is an appropriate place to put a CEP50 (circular error probability 50%) measurement in a geotiff. Thanks in advance, Isaac ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gd

Re: [gdal-dev] How to destroy/free VSIMEM in C++

Right, this implementation is for MVT. Objective is to get the /18/66027/96262.mvt file We are passing the VRT file as input. Output is vsimem. Options are - {"-dsco", "TILE_EXTENSION=mvt", "-dsco", "COMPRESS=NO", "-dsco", "MINZOOM=18", "-dsco", "MAXZOOM=18"} Once we have multiple files in

Re: [gdal-dev] How to destroy/free VSIMEM in C++

On mardi 21 juillet 2020 04:19:54 CEST MRRAJESH wrote: > Developers, > Below is the GDALVectorTranslate C++ code. I am clearing the vsibuf with > VSIUnlink. But still memory is not vanished. Do we need to call any other > methods? I suspect you use the MVT driver here ? In which case it will outpu

[gdal-dev] How to destroy/free VSIMEM in C++

Developers, Below is the GDALVectorTranslate C++ code. I am clearing the vsibuf with VSIUnlink. But still memory is not vanished. Do we need to call any other methods? try { . vsibufPath = string("/vsimem/mvt-") + GetUUID();