1. Introduction
Light detection and ranging (LiDAR) systems are currently common tools to acquire three-dimensional (3-D) surface information. This technology integrates a laser scanner, a Global Positioning System (GPS), and an inertial navigation system (INS) and thus can effectively obtain 3-D surface models. Different platforms, such as aircraft and land-based vehicles can be equipped with LiDAR systems, which can be generally classified into two categories: airborne and terrestrial. Airborne LiDAR acquires data from the air to the ground to obtain the 3-D points on building rooftops and object surfaces, while terrestrial LiDAR usually acquires the 3-D points on building façades and object surfaces. Because terrestrial LiDAR cannot easily acquire 3-D points from building roofs, airborne LiDAR can be incorporated to provide building roof information. Hence, the integration of airborne LiDAR and terrestrial LiDAR is needed to form a complete dataset for 3-D buildings.
Point cloud registration is a procedure to eliminate the inconsistency between different point clouds acquired from different platforms. Point cloud data acquired by different platforms have different characteristics according to scanning distance, scanning rate, and scanning direction. For example, the scanning distance and beam divergence angle of airborne LiDAR is larger than ground-based LiDAR and, consequently, the point density of airborne LiDAR is lower than ground-based LiDAR. In addition, the scan direction of airborne LiDAR and mobile LiDAR are different, and the acquired 3-D points partially overlap on the object surface. Because the scanning range of airborne LiDAR is longer than ground-based LiDAR, the scanning area of airborne LiDAR is usually larger than ground-based LiDAR. Hence, the registration of airborne and mobile LiDAR is a challenging topic in data co-registration.
Data registration is a procedure to transform a dataset from its own coordinate system to another system. It can be classified into 2-D data and 3-D data registration. For example, image registration is the most common 2-D data registration, and 3-D point cloud registration is one of the 3-D data registrations. The 3-D data registration includes three types of control features: control point, control line, and control surface.
The control points represent a set of 3-D point features in different datasets. This feature is widely used in registration because the control point is the basic control feature. Iterative Closest Point (ICP) [
1,
2,
3,
4] is acquired through point features. The ICP algorithm selects the two closest points as a conjugate pair and then calculates the transformation parameters to minimize the mean square error iteratively until the distance between the point pair is less than the threshold. Rusinkiewicz and Levoy [
5] analyzed the original ICP and improved the performance and precision; the new ICP can register more complex models. The registration precision indicates the geometrical difference between two systems. Barnea and Filin [
6] transferred the 3-D point clouds to 2-D panoramic range images and extracted the registration key points to improve the computational time of conjugate points selection.
The second control feature, control line, is a linear feature consisting of a set of 3-D line features in different datasets. This type of line feature mainly occurs in man-made objects such as buildings. Linear features cannot be extracted directly from a LiDAR point cloud and are usually intersected by two planes. The reliable linear features can be used as control entities to calculate the transformation parameters. Habib
et al. [
7] used line features to register LiDAR point clouds and image data. For the image, the control lines were extracted manually; for the LiDAR point cloud, the line features were intersected by two near planes. Jaw and Chuang [
8] also proposed a line-based method to register terrestrial LiDAR point cloud scanned from different stations.
The third control feature, control surface, is suitable for LiDAR registration because the LiDAR systems provide an abundance of 3-D surface features. Rosenholm and Torlegard [
9] used digital elevation models (DEM) as reference data in absolute orientation of the stereo model from stereopairs. Gruen and Akca [
10] used least squares 3-D surface matching (LS3D) to minimize the 3-D distance between the reference data and model data. Akca [
11] also used LS3D to register point clouds by their geometry and spectrum characteristics. This LS3D method has been applied to many applications, such as surface registration for land deformation [
12].
Multi-strips or multi-stations LiDAR registration is a standard process before delivering LiDAR data [
13]. LiDAR systems are available on several different platforms, such as airborne LiDAR systems (ALS), terrestrial static LiDAR systems, and terrestrial mobile LiDAR systems. In this study, the terrestrial LiDAR system (TLS) and mobile LiDAR system (MLS) refer to terrestrial static and mobile LiDAR systems, respectively. The registration of LiDAR data can be classified into four categories: registration of multi-strip ALS, registration of multi-station TLS, registration of multi-strip MLS, and registration of different platforms.
Multi-strip ALS not only enlarges acquisition areas but also improves the point density in the overlapped area. The registration of ALS includes two mathematics models: system-driven models and data-driven methods [
14]. The system-driven approach considers the physical sensor model of ALS and usually requires the trajectories of ALS. In the contrast, the data-driven approach does not require physical orientation parameters; it minimizes the Euclidean distance and models the discrepancy between strips using actual LiDAR points. The geometric features of ALS registration can be a signalized target, control line, or control surface. To avoid the effect of irregular points caused by trees, one possibility is to use ground points to calculate the transformation coefficients. In addition, LiDAR intensity can be also be integrated in registration.
The registration of multi-stations TLS combines the partially scanned objects to obtain a complete scene. Because the platform of TLS is fixed during scanning, the point clouds of TLS are treated as a rigid body, and the 3-D similarity transformation model is usually adopted in the registration of TLS. The registration of TLS can be classified into two categories: Range-based registration and image-based registration. Similar to ALS, range-based registration uses 3-D points to extract geometric features, including signalized target and non-signalized natural targets. Signalized targets such as spherical targets are suitable for an area without man-made objects, and non-signalized natural targets such as control lines and control planes can be extracted from man-made objects. The image-based registration interpolates the 3-D points into a panorama image using the LiDAR intensity. The feature points can then be extracted for registration by image processing techniques such as Scale-Invariant Feature Transform (SIFT) and Speeded Up Robust Features (SURF).
The mobile terrestrial LiDAR systems collect and perform mapping from a moving vehicle on a road. The aim of MLS registration is to register the LiDAR points from different trajectories; therefore, to obtain larger street sections, MLS usually acquires data from direct and reverse lanes using a scanning mechanism similar to ALS. MLS uses an odometer, GPS, and INS to determine the position and orientation of LiDAR sensors for direct georeferencing; however, the GPS condition in urban corridors usually affects the positioning accuracy of MLS. To compare the contribution of GPS positioning error to the overall accuracy between ALS and MLS, the scanning distance of MLS (range < 200 m) is shorter than ALS (range > 1000 m); consequently, the effect of GPS on MLS is much larger than on ALS systems.
Because ALS and TLS acquire data from different viewpoints, the integration of these systems is beneficial to obtain complete data for several applications. Several researchers have investigated possible ALS and TLS registration methods. In work by Böhm and Haala [
15], who used ICP methods, TLS provided the geometric information of vertical walls while ALS provided the geometric information of roof-tops for city modelling. Gressin
et al. [
4] also applied ICP in multi-platform LiDAR registration and integrated different types of point features into the tie points selection, including point features for registration such as eigenvalues, eigenvectores, dimensionality features, and entropy from neighborhood points. Von Hansen
et al. [
16] extracted the linear features from the building boundaries and then applied control lines. Boulaassal
et al. [
17] extracted the 3-D vectors of buildings from ALS, TLS, and MLS separately and then registered all the extracted 3-D vectors by linear feature for a detailed 3-D building model; they combined the vector data rather than point clouds. Cheng
et al. [
18] extracted the 3-D building corners from the intersection of 3-D building boundaries from ALS and TLS and then applied the 3-D building corners. Wu
et al. [
19] combined the control lines and planes extracted from buildings for the registration of ALS and TLS.
Most previous studies focused on ALS and TLS registration; relatively few discussed the registration of ALS and MLS. The challenge of ALS and MLS registration is to obtain reliable control entities from these two different systems. Because ALS and MLS acquire an abundance of 3-D surface points, the 3-D surface features such as road and wall surfaces can be utilized in ALS and MLS registration.
The airborne and terrestrial mobile LiDAR systems acquire data efficiently. The objective of this study was to co-register the point clouds acquired by airborne LiDAR and terrestrial mobile LiDAR and use these complementary data to improve the point coverage in urban areas. The point clouds scanned from two platforms can be located at difference coordinate systems, and the point clouds must first be registered to remove the error between the point cloud data from the two platforms. This study proposes a scheme to register airborne and terrestrial point clouds by surface features and discusses the effect between different point densities.
The terrestrial mobile data use an odometer, GPS, and INS to determine the position and orientation of LiDAR sensors for direct georeferencing; however, the GPS condition in urban corridors usually affects the positioning accuracy for terrestrial mobile LiDAR. Because the GPS condition of airborne LiDAR is better than mobile LiDAR, we assumed that the airborne LiDAR have been georeferenced to a world coordinate system. The terrestrial mobile LiDAR is then transformed to the coordinate system of airborne LiDAR to improve the accuracy of mobile LiDAR in urban corridors.
3. Experimental Results
The test data include airborne LiDAR and terrestrial mobile LiDAR data. The test area is about 190 m by 900 m. The airborne point cloud data were scanned by Optech ALTM30/70 using 7 flightlines. The total number of points is 2,774,371, and the average point density is about 15 points/m
2. The terrestrial mobile LiDAR was scanned by Optech Lynx, and the length of the road is about 900 m. The MLS data include the two different trajectories, left-to-right and right-to-left. The total number of points is about 79,170,000, and the average point spacing in the horizontal plane is about 5 cm.
Figure 4 shows the ALS digital surface model (DSM), MLS DSM, and reference orthophoto of test area. Only the overlapped are used in registration.
Figure 5 compares the profiles of ALS and MLS in the test area. The buildings beside the road and trees along streets in the urban corridor cause GPS signal occlusion, which significantly degrades the navigation performance; therefore, the MLS data need post-processing (
i.e., point registration) to obtain precise locations. The parameters used are listed in
Table 1.
Figure 4.
Test data: (a) ALS colored by elevation, (b) MLS colored by elevation, (c) reference orthophoto.
Figure 4.
Test data: (a) ALS colored by elevation, (b) MLS colored by elevation, (c) reference orthophoto.
Figure 5.
Profiles of ALS and corrected MLS data: (a) profile of ALS colored by elevation, (b) profile of MLS colored by elevation.
Figure 5.
Profiles of ALS and corrected MLS data: (a) profile of ALS colored by elevation, (b) profile of MLS colored by elevation.
Table 1.
The parameters setting and descriptions.
Table 1.
The parameters setting and descriptions.
Parameter | Descriptions | Parameter Setting |
---|
Voxel size | The voxel size is a parameter to structuralize irregular points to regular 3-D voxels. This parameter is related to point density. A lower point density needs larger voxel size to aggregate more points in a 3-D voxel. | 1 m |
Number of point in a voxel | This parameter defines the minimum number of point in a voxel. If the number of point is larger than this threshold, these points are used to calculate the plane equation. Any 3 points can determine a plane, so we used more than 3 points in a voxel to determine the plane parameters. | 5 points |
λk | When λk is smaller than a predefined threshold, the points in the voxel is considered as a plane. We observed the data set to define this empirical parameter. | 0.2 |
Intersection angle | If the intersection angle of two planes is smaller than the angle threshold, these two planes are treated as a conjugate plane pair. We observed the data set to define this empirical parameter. | Fifteen degrees for the first 3 iterations. After 3 iterations, this parameter is 2 × std (intersection angle of plane pair after registration). (see Section 2.2) |
Distance | If the Euclidean distance of mean points between two planes is smaller than the distance threshold, these two planes are treated as a conjugate plane pair. This parameter is defined by voxel size and pre-alignment quality. | One meter for the first 3 iterations. After 3 iterations, this parameter is 2 × std (distance of plane pair after registration). (see Section 2.2) |
Maximum iteration | The matching process terminates when the iteration number exceeds predefined maximum number of iteration. For good data configuration, the convergence of LS3D is relatively faster than ICP approach. | 20 |
Stopping criterion | The matching process meets the optimal solution when the corrections of transformation parameters are smaller than the predefined thresholds. The small thresholds are selected to ensure the quality. | |dtx| < 0.001 m; |dty| < 0.001 m; |dtz| < 0.001 m |S| < 0.0001; |dω| < 0.001 deg; |dφ| < 0.001 deg; |dκ| < 0.001 deg |
The experiments in this study used both simulation and real data to analyze the performance of point registration. The validation experiments were carried out in three parts. First, the 3-D points with different point densities and standard errors were simulated; second, the relative accuracy between forward and reverse of MLS data was examined; and third, the errors between MLS and ALS from the proposed methods were checked.
3.1. Simulation Data Registration
First, we used a simulation dataset to verify the precision of registration at different densities. The registration precision indicates the geometrical difference between two systems. In this experiment, the point-density ratio indicated the ratio between target points and search points and was used to simulate different point densities between LiDAR system 1 and system 2. We simulated 3-D points distributed on a prismatic building model shaped like a 50 m × 50 m × 50 m box. The point densities of simulated system 1 were 100, 90, 80, 70, 60, 50, 40, 30, 20, 10 points/m
2, while the point density of simulated system 2 was 100 points/m
2; therefore, the point-density ratios were 1/1, 1/2, 1/3, 1/4, 1/5, 1/6, 1/7, 1/8, 1/9, 1/10. The noise levels (random error) of simulated point were 0.10 m and 0.05 m for system 1 and 2, respectively. The 3-D transformation parameters were predefined using the maximum transformation parameters (tx, ty, tz, omega, phi, kappa) in
Table 1. One hundred data sets are simulated for each point-density ratio. After the data simulation, we used LS3D to solve the transformation parameters and applied the parameters to the simulated system 2 data. Every transformed point can be compared with the original point. We used the differences along X, Y, and Z axes as a precision index (
Figure 6). The simulation results indicate that accuracy of registration improved as the density increased. The distance error may preserve 5 cm precision when the point-density ratio is reduced to 1/10.
Figure 6.
Simulation results: (a) Position difference along X-axis. (b) Position difference along Y-axis. (c) Position difference along Z-axis. (d) Distance between transformed point and original point.
Figure 6.
Simulation results: (a) Position difference along X-axis. (b) Position difference along Y-axis. (c) Position difference along Z-axis. (d) Distance between transformed point and original point.
3.2. Terrestrial Mobile LiDARs Registration
Because the points of MLS number about 79 million, we reduced the points to accelerate the computation by using a 1 m 2D grid to remove the nonoverlapped points. We apply initial translation (tx, ty, tz) in point reduction. It can avoid large difference between ALS and MLS. Besides, we use 2D grid to accelerate the process of point reduction. In other words, all the MLS points are projected to 2D horizontal plane and elevation is not considered in this stage. If the points from both trajectories appeared in same cell, then that cell was marked as an overlapped cell and all the points in this overlapped cell were preserved for registration. The grid size was estimated by the inconsistency of points from two different trajectories. The smaller grid size may remove the overlapped points incorrectly due to the problem of direct georeferencing. After the nonoverlapped point reduction, the number of points was reduced to 44 million, and the compression rate was about 44%.
To obtain high point density in urban environments in this study, the maximum vehicle speed of MLS was <60 km/hr, and arbitrary lane-changing was not allowed, resulting in a continuous and smooth driving path. Considering the road length and data volume, we split the data into several road segments. In addition, the error behaviors for certain road segments were considered to be systematic errors, and a 3-D similarity transformation was considered to compensate the geometric inconsistency between two road segments. The length of the road section was 25 m, with a 3 m overlap. Each trajectory had 36 segments, and the total number of road segments was 72 in this stage. We used the forward trajectory (from left to right) as reference data. The registration coefficients converted the points from reverse trajectory to reference data. Because the LS3D algorithm requires initial transformation parameters, we manually measured three registration points in the first segment and calculated the initial transformation parameters. The precise registration transformation parameters were then determined by LS3D algorithm. We assumed that the actual road path was continuous and smooth; hence, the initial parameters for the next road segment could be obtained from the previous road segment, and therefore only three registration points were needed to begin the TLS data registration.
The accuracy assessments in this section include three parts: analysis of derived transformation parameters, point distance between road marks from two trajectories, and visualization of MLS data before and after registration.
For these road segments, we calculated 36 sets of transformation parameters (
Table 2). The scale coefficient is very close to 1. It is ranged from 0.9998 to 1.0004. To compare the translation and rotation parameters, the standard deviation of translation parameters (
i.e., 12.6 cm to 40.2 cm) was much larger than rotation angles (
i.e., 1.7 cm to 3.5 cm). In addition, the error in vertical direction was also larger than horizontal direction. The error in vertical direction was larger than 1 m when the GPS solution was not available, similar to error behavior in an urban corridor [
27]. In other words, the rotation angles were more consistent than the translation parameters. This phenomenon is referred to as the positioning errors of GPS outage.
Figure 7 plots the translation parameters at different road sections and indicates the continuity of translation parameters trajectories.
Table 2.
The summary of transformation parameters for MLS/MLS registration.
Table 2.
The summary of transformation parameters for MLS/MLS registration.
| tx (m) | ty (m) | tz (m) | Omega | Phi | Kappa |
---|
Mean | 0.689 | 0.267 | −1.639 | 0.003deg (0.1cm@25m) | −0.001deg (0.04cm@25m) | 0.043deg (1.9cm@25m) |
Std | 0.247 | 0.126 | 0.402 | 0.080deg (3.5cm@25m) | 0.038deg (1.7cm@25m) | 0.057deg (2.5cm@25m) |
Min | 0.200 | 0.030 | −2.457 | −0.130deg (−5.7cm@25m) | −0.088deg (−3.8cm@25m) | −0.090deg(−3.9cm@25m) |
Max | 0.984 | 0.417 | −1.148 | 0.195deg (8.5cm@25m) | 0.087deg (3.8cm@25m) | 0.198 deg(8.6cm@25m) |
Figure 7.
The translations in X/Y/Z directions (MLS/MLS registration).
Figure 7.
The translations in X/Y/Z directions (MLS/MLS registration).
To evaluate the accuracy of registration, we manually measured 36 well-defined points to compare the point distance before and after registration. Because the point spacing of MLS is about 5 cm, we could identify the corner point of the road marks from the LiDAR intensity. We use lines intersection to determine the corner of road mark.
Figure 8 is an example of a check-point located on a marked pedestrian “zebra” crossing. The total number of independent check-points (CP) is 36. The error vectors of check point before and after registration are shown as
Figure 9.
Figure 8.
Illustration of independent check-point between trajectories: (a) check point in reference strip, (b) check point in registered strip.
Figure 8.
Illustration of independent check-point between trajectories: (a) check point in reference strip, (b) check point in registered strip.
Figure 9.
Error vectors of check points before and after registration
Figure 9.
Error vectors of check points before and after registration
Table 3. shows the results of check points before and after registration. The mean errors before registration ranged from −1.634 m to 0.719 m. The mean error in vertical direction is larger than horizontal directions. After the registration, the mean errors were significantly reduced to 0.002 m to 0.025 m. The standard deviations of check point before registration ranged from 0.114 m to 0.401 m and fell to <5 cm after registration.
Table 3.
Statistics of the independent check points.
Table 3.
Statistics of the independent check points.
| Max (m) | Min (m) | Mean (m) | Std (m) |
---|
dY | Before | 1.017 | 0.295 | 0.719 | 0.228 |
After | 0.042 | 0.000 | 0.025 | 0.043 |
dX | Before | 0.460 | 0.073 | 0.293 | 0.114 |
After | 0.056 | 0.003 | 0.024 | 0.043 |
dZ | Before | 2.469 | 1.159 | -1.634 | 0.401 |
After | 0.069 | 0.000 | 0.002 | 0.028 |
After the numerical analysis, we also selected some profiles to visually compare MLS before and after registration.
Figure 10 shows three profiles of the road point cloud before and after registration. The width of the profile is 1.5 m, and the different colors indicate points from different trajectories. In the figure, the discrepancy was removed after registration.
Figure 10.
Profiles of MLS before and after registration: (a) profile A, (b) profile B, (c) profile C.
Figure 10.
Profiles of MLS before and after registration: (a) profile A, (b) profile B, (c) profile C.
3.3. Airborne LiDAR and Terrestrial Mobile LiDAR Registration
Once the MLS data from different trajectories were well co-registered, we performed the LS3D registration for ALS and MLS data. The spacing of voxel for ALS and MLS was 1 m. The total number of points should be more than 5 points for normal angle calculation; the number of voxel for ALS and MLS were 40,907 and 218,212 respectively. The registration features included surfaces of roads, walls, and other objects. We use elevation and azimuth angles to discuss the distribution of normal vector. The elevation angle is a vertical angle from horizontal plane to normal vector; the azimuth angle is a horizontal angle from north to horizontal projected normal vector. Elevation and azimuth angles of normal vectors (
Figure 11) show that the elevation angles of the road and roof points were mostly close to 90 degrees, while the elevation angles of the walls were mostly close 0 degrees. The number of normal vectors from the road and roofs were larger than the normal vectors from walls (
Figure 11a), and the total number of elevation angles <10 degrees was 768 (about 2%). These are important control elements for registration. The MLS contain more normal vectors from roads and walls (
Figure 11b), and the azimuths of the normal vectors are distributed on different directions (
Figure 11c,d). Therefore, the controlling capability of control surfaces is well-distributed to cover all directions.
Figure 11.
Histogram of elevation and azimuth angles: (a) elevation angles of ALS, (b) elevation angles of MLS, (c) azimuth angles of ALS, (d) azimuth angles of MLS.
Figure 11.
Histogram of elevation and azimuth angles: (a) elevation angles of ALS, (b) elevation angles of MLS, (c) azimuth angles of ALS, (d) azimuth angles of MLS.
The statistics of transformation parameters for ALS/MLS registration is shown as
Table 4. The mean errors in translation parameters were ranged from −0.885m to −0.220m. It was larger than the rotation parameters. It means the errors were mostly conducted by GPS positioning error. The standard deviation of translation parameters (3.6 cm to 9 cm) was also larger than rotation angles (
i.e., 0.75~3.5 cm).
Figure 12 shows the translation at different distances.
Figure 12.
The translations in X/Y/Z directions (ALS/MLS registration).
Figure 12.
The translations in X/Y/Z directions (ALS/MLS registration).
Table 4.
The summary of transformation parameters for ALS/MLS registration.
Table 4.
The summary of transformation parameters for ALS/MLS registration.
| tx (m) | ty (m) | tz (m) | Omega | Phi | Kappa |
---|
Mean | −0.333 | −0.220 | −0.885 | 0.001 deg (0.1cm@25m) | −0.008 deg (0.4cm@25m) | 0.011 deg (0.5cm@25m) |
Std | 0.076 | 0.036 | 0.088 | 0.016 deg (0.75cm@25m) | 0.025 deg (1.1cm@25m) | 0.080 deg (3.5cm@25m) |
Min | −0.480 | −0.328 | −0.980 | −0.041 deg (−1.8cm@25m) | −0.038 deg (−1.6cm@25m) | −0.154 deg (−6.7cm@25m) |
Max | −0.199 | −0.156 | −0.667 | 0.0335 deg (1.4cm@25m) | 0.077 deg (3.3cm@25m) | 0.218 deg (9.5cm@25m) |
The accuracy assessments included two parts: plane distance between surfaces from ALS and MLS, and visualization of ALS and MLS data before and after registration. Because measuring check-points between ALS and MLS is difficult, we used the check plane in the accuracy assessment of ALS and MLS registration. We manually selected the 74 conjugate planes from ALS and MLS; a least squares plane fitting was then applied to estimate the optimal plane equation. The perpendicular distance between two planes was calculated as the quality index of ALS and MLS registration (
Table 5). The data registration improved the mean error datum of ALS and MLS. In addition, the precision of registration was improved from 0.847 m between ALS and MLS from −0.979 m to −0.02 m. The mean error was mainly caused by the GPS/IMU signals and different to 0.033 m. A comparison of the error vectors of perpendicular distance between plane before and after registration shows that the systematic error was compensated by LS3D after registration (
Figure 13). Hence, the LS3D was able to automatically improve the consistency between ALS and MLS.
Figure 13.
Error vectors of plane distance before and after registration.
Figure 13.
Error vectors of plane distance before and after registration.
Table 5.
The statistic of the check planes.
Table 5.
The statistic of the check planes.
| Before Registration | After Registration |
---|
Mean (m) | −0.979 | −0.020 |
Std (m) | 0.847 | 0.033 |
Max (m) | 0.929 | 0.068 |
Min (m) | 0.581 | −0.045 |
Because the conjugate planes were mostly located on road surfaces, we selected some profiles to evaluate the continuity of walls. Three profiles of the road point cloud before and after registration (
Figure 14) show that the width of the profile is 1.5 m, and different colors indicate points from ALS and MLS. The discrepancy was removed after registration, indicating that the continuity between the building roof and wall was improved after registration.
Figure 14.
The profiles of the airborne LiDAR and terrestrial mobile LiDAR point cloud: (a) profile A, (b) profile B, (c) profile C.
Figure 14.
The profiles of the airborne LiDAR and terrestrial mobile LiDAR point cloud: (a) profile A, (b) profile B, (c) profile C.
Figure 15.
The results of ALS and MLS registration: (a) ALS only (colored by height), (b) registration of ALS and MLS (colored by height).
Figure 15.
The results of ALS and MLS registration: (a) ALS only (colored by height), (b) registration of ALS and MLS (colored by height).
The perspective view of registration results (
Figure 15a,b) shows that the proposed method worked well for the registration of ALS and MLS. In addition, the combination of ALS and MLS may provide a more complete scene in urban environments. For example, the MLS may improve the wall features for ALS.