Study area
The field site is located in the semi-arid Lorca basin, in Southeastern Spain where the Luchena river joins the northern branch of the Puentes reservoir (37∘45’20.62”N, 1∘51’19.99”W). Due to the dry conditions (270 mm annual rainfall, potential evapotranspiration > 900 mm) this area has only limited and partial vegetation cover which allows reconstruction of the actual ground surface (see Fig. 1) (Sanchez-Toribio et al. 2010). The site is a small denudation niche developed in a Holocene to late Pleistocene lacustrine terrace with gypseferous and calcareous lacustrine silts, comparable to the terraces as described in (Baartman et al. 2011). This denudation niche is re-shaped by man-made, almost level, bench terraces which now show extreme forms of gullying, piping and collapsed pipes. These terraces were abandoned around 2000 after cultivation with drip irrigated crops. Some physical and chemical characteristics of the site’s top soil can be found in van der Meulen et al. (2006).
Erosion features in this region have been a topic of interest for a long time. Both long-term erosion (Ruiz-Sinoga and Diaz 2010) and contemporary erosion processes (García-Ruiz et al. 2013; Nadeu et al. 2015) have been under study. Erosion features in natural areas (Díaz and Bermúdez 1988; Martínez-Hernández et al. 2017; Díaz et al. 2007) and in cultivated areas (Romero-Díaz et al. 2017; de-las Heras et al. 2019) have been studied. In addition, much focus has been put on potential measures to prevent erosion in cultivated areas; both in dryland as well as in irrigated areas (Castillo et al. 2007; Calatrava et al. 2011; García-Ruiz et al. 2013; Hooke and Sandercock 2017).
Materials and software
The flights were carried out using a MAVinci Sirius 1 UAS, which is a typical low-weight ready-to-fly system, and the methodology and output that are described in this paper can be considered representative for other contemporary UAS. Ground speed is approximately 50 km/h during flights with low wind speed, with the maximum flight time ranging between 30-60 minutes. The carrying capacity is approximately 0.5 kg with a GPS and inertial measurement unit (IMU). A Panasonic Lumix GX1 16 megapixel camera, which can collect both RAW and JPEG photos (at 0.5 and 1.5 frames per second) was used. In this study only JPEG format images were collected.
Flight planning was carried out with the MAVinci Desktop that is part of the MAVinci UAS. Images were processed with Structure-from-Motion photogrammetry (with Agisoft Photoscan Pro 1.0 software) and further analysis carried out with Python 2.7 and the Geospatial Data Abstraction Layer (GDAL).
Ground control points (GCPs)
Without the use of GCPs the horizontal and vertical accuracy of products derived from the aerial imagery (point cloud, digital elevation models, orthorectified imagery) is similar to the accuracy of the GPS device on board of the UAS, which is in the range of several meters. By re-aligning the SfM point cloud (more info in Section “Flight procedure”) with a limited number of accurate GCPs this accuracy can be improved significantly (Turner et al. 2012), up to several centimeter accuracy.
In total 15 GCPs have been positioned strategically, i.e. well distributed throughout the area to capture the outer regions of the area of interest, as well as the lowest and highest points of the area of interest. Moreover, GCPs have been placed near special areas, such as important breaks-of-slope of the terrace levels near gully systems of interest). The GCPs themselves were simple 80 cm x 80 cm orange textile rectangles, with in the center a black textile square containing a CD disk. The centers of the CD disks were measured with a TOPCON Hiper Pro DGPS (Differential Global Positioning System) that has a horizontal and vertical accuracy of 10 mm. The orange textile combined with the CD made it easy to recognize the GCPs from the aerial imagery and find the exact point of measurement.
Flight procedure
Flight lines were created based on a selected area of interest and a desired Ground Sampling Distance (GSD). The higher the flight altitude (i.e. distance to ground surface), the larger the GSD. A single flight line is constant in heading and elevation (distance to mean sea level) to ensure a stable flight, however, elevation can vary between flight lines to match the landscape’s topography and minimize variations of GSD throughout the data set. Flight lines and camera trigger locations enabled 85% overlap in flight direction and 65% sidelap. After landing, the GPS/ENU logs were copied to the EXIF metadata of the images.
SfM/MVS processing chain
The aerial imagery was processed using Structure-from-Motion (SfM) and MultiView Stereo algorithms (MVS) as implemented in the commercially available software Agisoft Photoscan Professional (v1.0) (AgiSoft 2014). There are freely available alternatives such as VisualSfM V0.5.24 (Wu 2013), Microsoft PhotoSynth for the creation of SfM/MVS point clouds, which then need further processing in software such as ArcGIS V10.6 (commercial) or Meshlab (free). The SfM/MVS processing chain is summarized in Fig. 2.
In general, the processing steps are: 1) Import selected imagery. Selection criteria can be based on camera orientation (roll/pitch/yaw) or blurriness to ensure the processing of high-quality, in-focus, images. We selected imagery with a maximum roll and pitch of 10 degrees; 2) Camera alignment and estimation of interior camera parameters. This step uses the SfM algorithm which is developed specifically for creating 3D models of unstructured photo collections (Brown and Lowe 2005). SfM requires multiple images of an object from different camera positions, where possible with > 70% overlap. Image features are identified in image pairs and used as tie points for 3D reconstruction. The output is a unfiltered point cloud which has an approximate average point spacing of 0.5-1 m (Rosnell and Honkavaara 2012); 3) Manual identification and placement of GCPs in the imagery data; 4) Optimization of interior camera parameters and georeferencing of the sparse point cloud to best fit the GCP coordinates; 5) Generation of a dense point cloud using MVS. MVS revisits the SfM image pairs, reduces noise and generates more points between the tie points (Seitz et al. 2006). Typically for UAS data, the average point cloud spacing is approximately 0.05 m, depending on flight altitude, camera specifications and surface properties; 6) The dense point cloud is used to create a continuous mesh which can be converted to a DSM; and 7) Texture is blended on top of the mesh to create an orthorectified image mosaic of the aerial photos.
Experimental design
Data acquisition
In a single day we undertook three flights over the study area. The flights were labeled based on their direction (A-B) and relative altitude (1-3). The first flight had flight lines in a north-south (N-S) direction at a relatively low altitude (A1), the second flight had flight lines in a southwest-northeast (SW-NE) direction at a medium altitude (B2), and third flight had flight lines in a SW-NE direction at a relatively high altitude (B3).
In order to compare camera altitude and flight direction independently, additional data sets were created. High-resolution images were resampled to a lower resolution in order to replicate higher altitude flights. The images from flight A1 were resampled to match the GSD of higher altitudes 2 and 3, creating the image sets A2* and A3*. Images from flight B2 were resampled to B3* to match the same GSD as flight B3 to see the impact of differences in UAV stability during a flight. For clarity the * indicates the data set has been resampled, instead of original flight imagery. Camera altitude was calculated based on the on-board GPS-measured aircraft elevation and the produced DSM of flight B3:
$$ Alt_{A1} = Alt_{A1} - Z_{DSM} $$
(1)
$$ Alt_{B2} = Alt_{B2} - Z_{DSM} $$
(2)
where AltA1 is the camera altitude (above ground surface), ZA1 is the camera elevation (above mean sea level) and ZDSM is the ground surface elevation. The DSM of flight B3 was selected because this flight had the largest coverage. The ratio of mean camera altitude between A1 and B2 was used to calculate the target GSD of A2*:
$$ R = \frac{\overline{Alt_{A1}}}{\overline{Alt_{B2}}} $$
(3)
$$ GSD_{A2*} = GSD_{A1}.R $$
(4)
where R is the ratio of mean flight altitude of A1 and B2. Here the mean camera altitudes, rather than individual values, were used to preserve the standard deviation of altitude and replicate the increase in elevation for the entire set of flight lines as a whole. The same principle was used to create data sets A3* (based on A1) and B3* (based on B2). The images were resampled (linear interpolation) within the freely available NConvert image processor.Footnote 1
New camera elevations of the resampled images were calculated based on the DSM and (mean) camera elevations:
$$ Z_{A2*} = Z_{A1*} - \overline{Alt_{A1}} + \overline{Alt_{B2}} $$
(5)
where \(\overline {Alt_{A1}}\) and \(\overline {Alt_{B2}}\) are mean camera altitudes of A1 and B2 respectively. These values were stored in the EXIF metadata of the JPEG images for further processing. The same procedure was carried between flight A1 and flight B3 to create the resampled image set A3*. In this way we acquired two data sets with varying GSD in flight direction A and three data sets with varying GSD in flight direction B. See Table 1 for an overview of the analyzed data sets.
Table 1 Overview of the data sets created. Heading A/B refers to direction of the flight lines, i.e. NS and SW – NE, respectively. Altitude 1-3 refers to three mean altitude zones, and F/R refers to “Flight” and “Resampled data set” Tests
The six data sets were used to create and compare the constructed DSMs and orthophotos. The tests focused on: The cell size of the data products, vertical and horizontal accuracy, absolute difference of DSMs, the spatial distribution of deviation between different flight sets, and registration of recognizable features. The cell size of the data products is automatically determined in Agisoft Photoscan based on the average point spacing of the dense point cloud. Moreover, the overall vertical accuracy of the DSM is determined by using absolute vertical deviation from the dGPS measurements,
$$ A_{v} = \frac{\sum\limits_{i=1}^{n} |Z_{DSM_{i}} - Z_{dGPS_{i}}|}{n} $$
(6)
where Av is the average vertical accuracy of the DSM, ZDSM and ZdGPS are the z-values from the DSM and dGPS, respectively, and n is the number of validation GCPs. For the horizontal accuracy of the orthophoto, manual digitization of marker locations in the orthophoto were compared with the dGPS measurements of the marker locations. Similar to the vertical accuracy calculations, average deviation from the dGPS measurements was used as a basis to assess the horizontal accuracy of the orthophoto,
$$ A_{h} = \frac{\sum\limits_{i=1}^{n} |XY_{Ortho_{i}} - XY_{dGPS_{i}}|}{n} $$
(7)
where Ah is the overall horizontal accuracy, XYortho is the (x,y) position of the GCP in the orthomosaic, XYdGPS is the (x,y) position of the GCP as measured by the dGPS, and n is the number of validation GCPs.
Furthermore, the absolute difference of DSMs and the spatial distribution of deviation between different flight sets gives insight in to the reproducibility of the process chain and usability for topographic change detection or landscape monitoring. Preparation of the original data sets was required to match the grid systems (location of grid cell center and cell size) of two DSMs. We used the highest resolution data set as the target grid system, and used GDAL’s reprojection tool to resample the second data set into the same grid system. Subsequently grid cells of the DSMs were subtracted for comparison. Finally, the registration of recognizable features in the data products includes geomorphological entities, such as rills and gullies, and surface objects such as vegetation and infrastructure.