Thank you Laurentiu, “*They exist for safety reasons (so you don't modify a dataset by mistake), not as an optimization.” *
This is what I’m looking for. 😊 All the best, Michal Kowalczuk W dniu czw., 16 sty 2025 o 10:11 Laurențiu Nicola via gdal-dev < gdal-dev@lists.osgeo.org> napisał(a): > Hi Michał, > > Without knowing a lot about the underlying implementation, I would expect > those flags to make no difference in performance. > They exist for safety reasons (so you don't modify a dataset by mistake), > not as an optimization. > > > As for the docs, that seems expected. The documentation can't list all the > things that a flag does not do. > > Laurentiu > > On Thu, Jan 16, 2025, at 09:16, Michał Kowalczuk via gdal-dev wrote: > > Any thoughts? :-) > > ---------- Forwarded message --------- > Od: *Michał Kowalczuk* <michkowalc...@gmail.com> > Date: wt., 14 sty 2025 o 12:41 > Subject: GDAL open flags > To: <gdal-dev@lists.osgeo.org> > > > Hi gdal-group! > > Does GDAL_OF_READONLY / GDAL_OF_UPDATE have any impact on performance, > especially when reading common vector files (shp, gpkg, gml)? There is no > recommendation on this in docs. > > Best regards, > Michał Kowalczuk > > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev > > > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
