The vcpkg port of the library was still at 2.0.0 until roughly a month ago. That means our vcpkg-reliant CI builds shouldn't be impacted.
On Tue, Sep 16, 2025, 7:39 AM Nyall Dawson via QGIS-Developer < qgis-developer@lists.osgeo.org> wrote: > > > On Tue, 16 Sept 2025 at 10:37, Nyall Dawson <nyall.daw...@gmail.com> > wrote: > >> Hi list, >> >> While tracking down the failures from >> https://github.com/qgis/QGIS/pull/63180, it's revealed that using QGIS >> with libspatialindex >= 2.0 gives completely misleading results for nearest >> neighbour geometry searches. >> >> The root cause is an optimisation from the upstream library ( >> https://github.com/libspatialindex/libspatialindex/commit/6fe9ff769243579ed74f7f27409dd1dda6591634) >> that breaks how downstream clients could previously implement custom >> nearest neighbour comparators. From my research I don't think this is >> fixable in QGIS, and will need an upstream fix. >> > > Sorry -- to clarify, that should have been >= 2.1 . 2.0 did not include > the offending commit. > > Nyall > > > _______________________________________________ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
