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.
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." qgis 3.22
Then came the trouble. The LiDAR .LAS file loaded, but the point cloud looked like angry confetti. He opened the —a vast library of algorithms that had saved his skin more times than he could count. He searched for "Noise filter." Nothing worked. The council wanted a clean Digital Elevation Model (DEM) by noon. In the cluttered geography department of a mid-sized
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. QGIS 3
But the legend was ugly. He dug into , changed the font to a clean sans-serif, and used the Attribute Table to manually rename the flood risk categories from "High_Prob" to "Zone 3: Frequent Flooding." Much better.
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.
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.