Re: [gdal-dev] Request for advice in unexpected slowdown working with LVBAG

2024-11-10 Thread Even Rouault via gdal-dev
Actually, you might have meant 3.0.3 and 3.5.3. When using 3.0.3, LVBAG files are read through the generic GML driver. When using 3.5.3, they are read with the new LVBAG driver (https://gdal.org/en/latest/drivers/vector/lvbag.html). When reviewing it, I saw that it ran a IsValid() check, even i

Re: [gdal-dev] Request for advice in unexpected slowdown working with LVBAG

2024-11-10 Thread Even Rouault via gdal-dev
Jan, What are those 3.03 and 3.53 versions ? They don't match GDAL official version numbers. I thought you meant 3.0.3 and 3.5.3, but the LVBAG driver is new to 3.2.0, so that can't be it.  Xerces is *not* a required DLL for that driver. It uses Expat. Do you use the AUTOCORRECT_INVALID_DATA=

[gdal-dev] Request for advice in unexpected slowdown working with LVBAG

2024-11-10 Thread Jan Heckman via gdal-dev
My c++ utility-app collects Kadaster BAG data in postgresql tables for use in "populatie service". It has functioned for several years, with a typical runtime of 40 minutes. In the process of rounding this off, I updated the gdal binaries from 3.03 to 3.53, as well as added some threaded workloads