1.6.0 - Fast on large projects, and failures you can see - Faster on large projects: the Optical Schematic View, the list of latent elements, the route correction check, Generate terminal slacks, placing a slack, FiberQ's own snapping in the placement tools, the undo record after every placement and Lay cable now use spatial indexes and batched reads instead of scanning every feature. On an 88,622-feature test city (QGIS 3.44) the schematic view opens in 11.3 s instead of 16 min 39 s. Benchmark, method and limits: https://github.com/vukovicvl/fiberq/blob/v1.6.0/docs/performance.md - Failures are reported instead of hidden: Save all, Auto-save, Export layer, the BOM export, Import points, Import route, Merge routes, Change route type, Change element type, Delete selected, Undo and Redo, and Lay cable say when a write failed, and why. An unreadable relations, latent-elements or colour-catalogue entry is reported, and its text is kept in the project. - Unhandled Python errors fixed in route correction, the schematic view's Center button, Import points and Import route, the BOM export to a locked or read-only file, and the slack tools on pre-1.0 projects. On QGIS 4, clicking an element with a picture now opens the picture. - Also: lengths follow geometry edits, the placement tools follow QGIS's snapping settings, validation settings are stored in the project, and many smaller fixes. - Changed: the "Check (health check)" button is gone (Validate project covers it). The BOM measures lengths on the ground, so its figures differ from 1.5.0's. Merge routes, Change route type, Change element type, Lay cable and Undo no longer save your other unsaved edits. Save all and turning Auto-save on ask before writing over a table that no layer of the project uses. Route correction's Correct moves a route end only onto a pole, manhole, joint closure or element within 5 m. - After upgrading from 1.5.0 without restarting QGIS, restart it once. - Full list: https://github.com/vukovicvl/fiberq/releases/tag/v1.6.0 The spatial indexing and batching, their benchmark, the failure reporting and the crash fixes were developed with support from the NLnet NGI0 Commons Fund. Everything else in this release, including the fixes made during its release testing, was not funded by it.
yes
vukovicvl
2026-11-08T18:03:44.640514+00:00
3.22.0
4.99.0
None
no
Plugin Tags