Qgis: 3.22

At 11:47 AM, a beautiful, shaded relief map appeared. The noise was gone. The algorithm had intelligently interpolated the gaps. He let out a breath he didn’t know he was holding.

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. qgis 3.22

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." At 11:47 AM, a beautiful, shaded relief map appeared

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. He let out a breath he didn’t know he was holding

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.