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."
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. qgis 3.22
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. At 4:15 PM, he exported the map as
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. But inside his digital one, the waters had finally receded
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.