Rahkonen and develoeprs,
We have used GeoPackage format, it is performing well. We have one more
issue, can you suggest us
We are using VRT file as input to GDALVectorTranslate in C++. Till 18 or 19
level, we are getting tiles. When we request for multiple 20th level tiles,
we have big area feat
@Even or Developers,
Please confirm on -
"GDAL has methods for creating temporary attribute indexes so that we would
not need to convert GeoJSON physically into some other format."
Do we need to convert GeoJSON to some other format for better performance?
Regards,
Rajesh
--
Sent from: http
Hi,
I guess that the slowest part is not VRT but your SQL
SELECT * FROM "features" WHERE LegendEntryName
IN("V_XX_AR","V_XX_LB","V_DOCIND_PT","V_XX_ML") because GeoJSON does not
support attribute indexes. I would have a try by converting GeoJSON into
GeoPackage or any other database format. R
Developers,
We are using VRT file (located in physical disk) as input to
GDALVectorTranslate in C++. This VRT file pointing JSON file, which is
little bigger size. How to improve the performance?
const char *pszFilename = "C:\\Test\\MVT.vrt";
hSrcDS = (GDALDatasetH *)GDALOpenEx(pszFilename, GDA
