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
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
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();
