We're Shadowmark Maps, a small UK LiDAR map app. The mods OK'd this post. Everything below uses free data, QGIS and a free plugin, so you can follow it without our app.
The image is Maiden Castle hillfort in Dorset: three layers made from one free 1 m terrain model, blended in QGIS. We used QGIS 4.2.3 with the Relief Visualization Toolbox (RVT) plugin 1.0.1. The menus below are named as in the QGIS 3.40 user manual, so they should match a 3.x install too.
Image description: a greyscale overhead relief map of Maiden Castle. Several rings of banks and ditches enclose a long oval interior, with entrances at the east and west ends and flat fields all round.
1. Get the data (free, Open Government Licence)
Go to the Defra Survey Data Download and open the Download tab. Click Draw Polygon, draw a small polygon over Maiden Castle (OS grid SY 669 884), then click Get available tiles.
Pick the LIDAR Composite DTM, 1 m resolution (2022 composite). The 5 km tile covering that spot should be SY68NE (E 365000-370000, N 85000-90000). It arrives as a GeoTIFF in EPSG:27700 (British National Grid).
If a button has been renamed, the dataset page linked at the end describes the product and its licence. Once the tile is loaded, Layer Properties > Information shows its resolution and CRS.
2. Load it and clip it
Layer > Add Layer > Add Raster Layer, and add the GeoTIFF. Check the project CRS is EPSG:27700.
Optional, but it makes step 5 fast: Raster > Extraction > Clip Raster by Extent. Clipping extent 366000,367800,87850,88950 [EPSG:27700]. Save the result as the DTM you use below.
The clip is 200 m bigger than the step 7 frame on every side, so edge effects from the slope and sky-view windows fall outside the final picture.
3. Hillshade (Raster > Analysis > Hillshade)
Input layer: your DTM. Band 1. Z factor 1.0. Scale 1.0. Altitude of the light 45 degrees.
Tick Compute edges and Multidirectional shading. Leave Combined shading and Zevenbergen&Thorne unticked.
With Multidirectional ticked, QGIS doesn't pass the azimuth on to GDAL, so leave that box alone. A single light direction can hide ditches that run parallel to it, which is why we went multidirectional.
4. Slope (Raster > Analysis > Slope)
Input layer: your DTM. Band 1. Ratio of vertical units to horizontal 1.0.
Leave the "percent instead of degrees" box unticked, so you get degrees. Tick Compute edges.
5. Sky-view factor (free RVT plugin)
Plugins > Manage and Install Plugins, search "Relief Visualization Toolbox", install.
Processing Toolbox > Relief visualization toolbox > RVT Sky-view factor.
Input DEM: your DTM. Vertical exaggeration factor 1. Search radius 10 pixels. Number of search directions 16. Level of noise removal: no removal. "Save as 8bit raster" unticked. Those are the defaults in plugin 1.0.1, so you should only need to pick the input.
6. Stack and style the layers (View > Panels > Layer Styling)
Order in the Layers panel, top to bottom: Slope, Sky-view factor, Hillshade.
For each layer, set Symbology > Render type to Singleband gray and Contrast enhancement to "Stretch to MinMax". Then open Min / Max Value Settings, pick User defined and type the Min and Max below. Blending mode is under Layer Rendering, and Global opacity is on the Transparency tab.
Hillshade: Color gradient Black to white. Min 0, Max 255. Blending mode Normal. Opacity 100%.
Sky-view factor: Black to white. Min 0.75, Max 1.0. Blending mode Multiply. Opacity 70%.
Slope: White to black (flat is white, steep is dark). Min 0, Max 45. Blending mode Multiply. Opacity 30%.
Multiply darkens the hillshade wherever the sky is hidden (ditches, hollows) and wherever the ground is steep (rampart faces). That makes the banks and ditches much less dependent on the light direction. Some directional shading from the hillshade is still in the blend, though, so it isn't perfectly even.
For the sky-view stretch, the plugin's own terrain presets use 0.7 to 1.0 for general terrain, 0.9 to 1.0 for flat ground and 0.55 to 1.0 for steep ground. We used 0.75, a little tighter than the general preset, so the banks get a bit more contrast.
7. Frame and export it
Project CRS EPSG:27700. Our map extent was E 366200, N 88050 to E 367600, N 88750, which is 1400 x 700 m.
In Project > Import/Export > Export Map to Image, type those four values into the extent boxes (west 366200, east 367600, south 88050, north 88750). Then set the output size to 1400 x 700 pixels, so you get one pixel per metre. The extent alone doesn't fix the pixel size. Before you save, check the extent boxes still show the same values, because changing the size or resolution can nudge them.
How we made the image
We didn't click through the dialogs for the final render. We ran the same QGIS algorithms from the command line instead:
Steps 3 to 5 ran through qgis_process.
The step 2 clip used gdal_translate -projwin, which does the same job as Clip Raster by Extent.
A short PyQGIS script applied the step 6 styling and exported the PNG at the step 7 extent and size.
These notes and the script were drafted with an AI assistant, then checked against the files that made the image and against the QGIS and RVT documentation and source. If you follow the menus and something comes out different, tell us your QGIS version and the step. We'd like to know where these steps are unclear.
LiDAR: © Environment Agency copyright and/or database right 2022. All rights reserved. That's the attribution statement on the dataset page, which gives the licence as the Open Government Licence v3.0. Contains Environment Agency information © Environment Agency and/or database right.