Example of use at mountain relief modified by mining and agriculture
Lidar (light radar) is a technique providing a very precise surface scanning. Airborne laser scanning generates a dense point cloud (several points per square metre) representing reflections of light ray. It contains reflections as from the vegetation as from the surface under it. Vegetation and building reflections may be filtered to get relief data only and create a digital elevation model (DEM) of relief. It is usually a raster and each pixel value represents the relief elevation. This raster may be further processed for better visualisation of relief shapes:
- Hillshade raster – grayscale 3D visualisation,
- Slope raster – colour represents the rate of change of elevation,
- Aspect raster – colour represents the downslope direction.
Surface irregularities cause by human activities are clearly recognizable in the high-resolution DEM obtained from Lidar.
My hometown was found in the Middle Ages after discovering a rich silver ore. Old mines were reused after second world war to get uranium. The massive mining activities caused significant changes of relief. Some valleys were filled with mining deposits. Agriculture in mountains was also present. Fields at slopes were divided with little retaining walls and embankments.
Mapping these features may be useful for more purposes. Scientists and some tourists going away from tracks want to avoid demanding walking over mining deposits, which usually consist of rock blocks and are often overgrown with trees and shrubs. Geologists and mineral collectors would appreciate the presence of these features in map to locate old mines and spoil heaps. These mines are an important part of local history and the map would tell more about them to visitors and historians. Tourists get better image about the extent of spoil heaps. Some line relief features like embankments are good for orientation. Moreover, map with such features looks much more attractive.
Spoil heaps covered with vegetation are difficultly mappable from aerial images. Mapping with GPS in mountain terrain would be very demanding. GPS signal under steep slopes and vegetation is less accurate. Spoil heaps in mountain relief are characterized by change of the downslope direction and are well recognizable in the slope raster as in the hillshade raster. Spoil heaps are mapped with polygon and tagged as man_made=spoil_heap or landuse=landfill (I'm not sure which one is better).
Embankments, retaining walls, cliffs and edges of spoil heap terraces are characterized by abrupt change of surface inclination and thus they are well recognizable in the slope raster. Sometimes it is not clear from the slope raster, what is the downslope direction and which one is the upper edge of the slope and the mapping may be confused. I recommend checking all created features with the hillshade or aspect raster.
Line representing embankments (man_made=embankment), retaining walls (barrier=retaining _wall) and cliffs (natural=cliff) should be placed to the upper edge of the slope and the right side of the line should always face downslope. When mapping these features from DEM, you should always know which one is present. In case of old agricultural retaining walls in my hometown, most of them are ruined and can be marked as embankments. Edges between spoil heap terraces and downslopes are marked as embankments as well. Roads and tracks at slopes are mostly placed over embankments. Slope raster is very suitable for mapping roads and tracks as well, especially if the track is covered by vegetation, not visible in the aerial map and the GPS signal was not accurate.
I checked my mapped features in field and must say, that this method is very reliable and accurate, because I made no mistakes. However, I know the area very well and was always sure which features I mapped.
I suppose that getting DEMs from Lidar in most countries is not so easy because it is not available for free. Sometimes it's available as WMS and JOSM allows to add a WMS layer. Always make sure that the provider license is compatible with OSM and you have permission to load the derived data to OSM.