Upd - Qgis 3.22

He sent the email to the council and leaned back. Outside, rain began to fall on the real river valley. But inside his digital one, the waters had finally receded.

Alistair had started the day with a fresh cup of black coffee and a prayer. He launched QGIS 3.22—codenamed "Białowieża" by its developers, after Europe’s last primeval forest. The splash screen glowed, promising a stable, long-term release. “Don’t fail me now, old friend,” he muttered. qgis 3.22

Emboldened, he added the plugin to show population density along the floodplain. He used the Print Layout designer—a feature he’d once despised but now respected like a trusted compass. He added a north arrow, a scale bar, and a legend. He set the map grid to 500-meter intervals. The council loved grids. He sent the email to the council and leaned back

In the cluttered geography department of a mid-sized university, Professor Alistair Finch was a man on the edge. His deadline loomed: a high-stakes flood risk map for the regional council, due by 5 PM. His weapon of choice? QGIS 3.22. His nemesis? A dataset of 15,000 corrupted LiDAR points that refused to play nice. Alistair had started the day with a fresh

At 4:15 PM, he exported the map as a PDF and a GeoPackage, just in case. He hit and gave it a final name: "Final_Flood_Risk_2026.qgz."

His fingers flew. He right-clicked the layer, went to , and opened the Symbology tab. He changed the point size to 0.2 and colored by intensity. Still a mess. He remembered a trick from a conference: use the CloudOptimized Point Cloud format. But 3.22 didn’t handle that natively—yet.

First, he dragged in the base layers: a messy shapefile of the river basin and a satellite image from the QuickMapServices plugin. The satellite view was crisp, a patchwork of green fields and serpentine streams. He set the project CRS to EPSG:3857, the standard for web mapping, then quickly corrected it to a local projected system—EPSG:27700 for the UK’s Ordnance Survey. Accuracy was everything.