<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xml:lang="en" article-type="research-article">
<front>
<journal-meta>
<journal-id journal-id-type="nlm-ta">Sensors</journal-id>
<journal-title>Sensors</journal-title>
<issn pub-type="epub">1424-8220</issn>
<publisher>
<publisher-name>Molecular Diversity Preservation International (MDPI)</publisher-name></publisher></journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.3390/s100908198</article-id>
<article-id pub-id-type="publisher-id">sensors-10-08198</article-id>
<article-categories>
<subj-group>
<subject>Article</subject></subj-group></article-categories>
<title-group>
<article-title>Assessment of Relative Accuracy of AHN-2 Laser Scanning Data Using Planar Features</article-title></title-group>
<contrib-group>
<contrib contrib-type="author">
<name><surname>van der Sande</surname><given-names>Corné</given-names></name></contrib>
<contrib contrib-type="author">
<name><surname>Soudarissanane</surname><given-names>Sylvie</given-names></name></contrib>
<contrib contrib-type="author">
<name><surname>Khoshelham</surname><given-names>Kourosh</given-names></name><xref ref-type="corresp" rid="c1-sensors-10-08198"><sup>*</sup></xref></contrib>
<aff id="af1-sensors-10-08198">Optical and Laser Remote Sensing, Department of Remote Sensing, Delft University of Technology, Kluyverweg 1, 2629HS Delft, The Netherlands; E-Mails: <email>C.J.vanderSande@tudelft.nl</email> (C.S.); <email>S.S.Soudarissanane@tudelft.nl</email> (S.S.)</aff></contrib-group>
<author-notes>
<corresp id="c1-sensors-10-08198">
<label>*</label>Author to whom correspondence should be addressed; E-Mail: <email>K.Khoshelham@tudelft.nl</email>; Tel.: +31-15-2781741; Fax: +31-15-2782348.</corresp></author-notes>
<pub-date pub-type="collection">
<year>2010</year></pub-date>
<pub-date pub-type="epub">
<day>1</day>
<month>9</month>
<year>2010</year></pub-date>
<volume>10</volume>
<issue>9</issue>
<fpage>8198</fpage>
<lpage>8214</lpage>
<history>
<date date-type="received">
<day>20</day>
<month>7</month>
<year>2010</year></date>
<date date-type="rev-recd">
<day>19</day>
<month>8</month>
<year>2010</year></date>
<date date-type="accepted">
<day>20</day>
<month>8</month>
<year>2010</year></date></history>
<permissions>
<copyright-statement>© 2010 by the authors; licensee MDPI, Basel, Switzerland.</copyright-statement>
<copyright-year>2010</copyright-year>
<license>
<p>This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution license (http://creativecommons.org/licenses/by/3.0/).</p></license></permissions>
<abstract>
<p>AHN-2 is the second part of the Actueel Hoogtebestand Nederland project, which concerns the acquisition of high-resolution altimetry data over the entire Netherlands using airborne laser scanning. The accuracy assessment of laser altimetry data usually relies on comparing corresponding tie elements, often points or lines, in the overlapping strips. This paper proposes a new approach to strip adjustment and accuracy assessment of AHN-2 data by using planar features. In the proposed approach a transformation is estimated between two overlapping strips by minimizing the distances between points in one strip and their corresponding planes in the other. The planes and the corresponding points are extracted in an automated segmentation process. The point-to-plane distances are used as observables in an estimation model, whereby the parameters of a transformation between the two strips and their associated quality measures are estimated. We demonstrate the performance of the method for the accuracy assessment of the AHN-2 dataset over Zeeland province of The Netherlands. The results show vertical offsets of up to 4 cm between the overlapping strips, and horizontal offsets ranging from 2 cm to 34 cm.</p></abstract>
<kwd-group>
<kwd>Airborne Laser Scanning</kwd>
<kwd>altimetry</kwd>
<kwd>accuracy assessment</kwd>
<kwd>strip adjustment</kwd>
<kwd>planar features</kwd>
<kwd>least-squares estimation</kwd></kwd-group></article-meta></front>
<body>
<sec sec-type="intro">
<label>1.</label>
<title>Introduction</title>
<p>Airborne Laser Scanning is an active optical range measurement technique that is used for acquiring accurate height data of the ground surface. The advantages of airborne laser scanning include high measurement accuracy, fast acquisition capability, and large spatial coverage. The Netherlands is the first country that was entirely covered by airborne laser altimetry measurements through the Actueel Hoogtebestand Nederland (AHN) project [<xref ref-type="bibr" rid="b1-sensors-10-08198">1</xref>]. The second part of the national laser altimetry project AHN-2 is being carried out since 2007 by several companies, and will be completed in 2012. The new height model has an unprecedented spatial resolution: it has an average density of 10 points per square meter [<xref ref-type="bibr" rid="b2-sensors-10-08198">2</xref>]. This unique high-resolution height model is used in a variety of applications, including water storage determination, subsidence studies, forest volume mapping, monitoring of coastal areas and 3D modeling of urban environments.</p>
<p>The airborne laser scanning measurements are acquired in multiple flight strips, and are independently georeferenced using data from on-board navigation sensors, <italic>i.e.</italic>, Global Navigation Satellite System (GNSS) and Inertial Navigation System (INS). The systematic and random errors introduced by the scanning mechanism as well as the navigation sensors accumulate in the final point cloud. This results in an offset and misalignment between data of overlapping flight strips. The quantification and elimination of the offset and misalignment between the overlapping strips is an important issue in airborne laser scanning, and is commonly referred to as strip adjustment. Moreover, the identification of the offsets and misalignments forms a major part of the accuracy assessment done by the end-user of the data. Therefore, fast and reliable methods for the adjustment of aerial laser strips are of particular interest for both the data providers and the end-users.</p>
<p>The error budget of airborne laser scanning has been a subject of extensive research [<xref ref-type="bibr" rid="b3-sensors-10-08198">3</xref>–<xref ref-type="bibr" rid="b9-sensors-10-08198">9</xref>]. In general, the errors originate from three main sources: (i) individual sensors (scanner, INS, GNSS) and their integration; (ii) properties of the target surface (geometry, reflectance); and (iii) post-processing (filtering, interpolation). Among these, the first source has a major impact on the accuracy of raw height data. The conventional approach to assessing the accuracy of laser strips is based on comparing the height on a number of tie points (corresponding points in two overlapping laser strips) or control points (ground truth measurements). Kilian <italic>et al</italic>. [<xref ref-type="bibr" rid="b6-sensors-10-08198">6</xref>], Crombaghs <italic>et al</italic>. [<xref ref-type="bibr" rid="b10-sensors-10-08198">10</xref>], and Hodgson and Bresnahan [<xref ref-type="bibr" rid="b7-sensors-10-08198">7</xref>] describe the use of tie and control points for the accuracy assessment of airborne laser scanner data. The identification of point features in laser scanner data is however difficult, due to the discrete nature of the data and the limited spatial resolution. To allow the accurate measurement of control points, Csanyi and Toth [<xref ref-type="bibr" rid="b11-sensors-10-08198">11</xref>] designed ground targets of a specific shape suitable for measurement in laser altimetry data. As another source of external measurements, Bretar <italic>et al</italic>. [<xref ref-type="bibr" rid="b12-sensors-10-08198">12</xref>] used a photogrammetrically derived Digital Surface Model (DSM) to perform an adjustment of airborne laser strips.</p>
<p>An alternative approach to assessing the relative accuracy of laser altimetry data is the comparison of corresponding features in overlapping strips. Vosselman [<xref ref-type="bibr" rid="b13-sensors-10-08198">13</xref>,<xref ref-type="bibr" rid="b14-sensors-10-08198">14</xref>] estimated planimetric offsets between the strips using linear features such as ditches and roof ridge lines. The planimetric accuracy of laser altimetry data is generally lower than the altimetric accuracy [<xref ref-type="bibr" rid="b5-sensors-10-08198">5</xref>], but is equally important, particularly in applications where mapping object boundaries is concerned. The use of corresponding linear features for the accuracy assessment has also been reported in a number of recent works [<xref ref-type="bibr" rid="b15-sensors-10-08198">15</xref>–<xref ref-type="bibr" rid="b17-sensors-10-08198">17</xref>]. Other previous works have demonstrated the use of corresponding surfaces for the evaluation of the errors in laser altimetry data. Ressl [<xref ref-type="bibr" rid="b18-sensors-10-08198">18</xref>] presented a non-linear model for accuracy assessment of strip adjustment based on five parameters. Latypov [<xref ref-type="bibr" rid="b19-sensors-10-08198">19</xref>] derived a generalized relative accuracy measure by comparing corresponding surfaces in the overlapping strips. Corresponding planar surfaces have been used for the estimation of vertical offsets between the strips [<xref ref-type="bibr" rid="b20-sensors-10-08198">20</xref>], as well as the system calibration parameters [<xref ref-type="bibr" rid="b21-sensors-10-08198">21</xref>,<xref ref-type="bibr" rid="b22-sensors-10-08198">22</xref>]. Maas [<xref ref-type="bibr" rid="b23-sensors-10-08198">23</xref>] estimated shift parameters between two overlapping or crossing strips by minimizing the distances between points in one strip and a triangulated mesh (TIN) of the other strip. Habib <italic>et al</italic>. [<xref ref-type="bibr" rid="b9-sensors-10-08198">9</xref>,<xref ref-type="bibr" rid="b24-sensors-10-08198">24</xref>] also minimized point-to-TIN distances iteratively, but estimated biases in the laser scanner system components. The drawback of the TIN-based methods is that the triangular patches do not necessarily always represent actual surfaces.</p>
<p>This paper proposes a new approach to strip adjustment and accuracy assessment of airborne laser scanner data by using planar features. The choice of planar features is particularly appropriate for the accuracy assessment of AHN-2 data over the Netherlands, because buildings with gable roof planes are present almost in all parts of the country, and also the high point density of the AHN-2 data is a determining factor in the increased reliability of the extracted planes. The basis of the proposed approach is that by evaluating the adjustment between the corresponding planes in two overlapping strips an estimation of the systematic and random errors in the data can be obtained. In the strip adjustment, a transformation is estimated between the strips by minimizing the distances between points in one strip and their corresponding planes in the other. The advantage of such an estimation model is twofold. First, incorporating a large number of reliable point-to-plane distance observations in a least-squares estimation model improves the precision of the estimated transformation parameters. Second, if two strips cannot be adjusted by only a 3D offset, an affine transformation can be estimated from which possible rotations between the strips can be derived. In addition, the estimation model is linear, which makes it independent of an initial approximation of the transformation parameters.</p>
<p>The paper proceeds with an overview of laser altimetry over the Netherlands and the status of the AHN-2 project in Section 2. Section 3 describes the proposed approach to strip adjustment, including the segmentation method for extracting planar segments, the robust plane fitting and the mathematical model for the estimation of strip adjustment parameters. The results of the accuracy assessment of the AHN-2 data over Zeeland province are presented in Section 4. The paper concludes with some remarks in Section 5.</p></sec>
<sec>
<label>2.</label>
<title>Airborne Laser Altimetry over the Netherlands: The AHN-2 Project</title>
<p>The Actual Height model of the Netherlands (AHN) part 2 is a joint program between the ministry of water management (Rijkswaterstaat) and the 26 water boards conducted in the period from 2007 to 2012. Water boards are the oldest legislative bodies in the Netherlands responsible for monitoring dykes and managing water quantity and quality. The importance of a country-wide height model for these organisations is evident, as the Netherlands is a delta partly below the sea level. During the first phase of the AHN project between 1997 and 2003 the entire Netherlands was laser scanned to make a height model with an altimetric accuracy of 16 cm and a point density varying from 1 point per 16 m<sup>2</sup> to 1 point per 32 m<sup>2</sup>. For the AHN-2 the requirements were tightened to achieve a higher accuracy and an increased point density. <xref ref-type="fig" rid="f1-sensors-10-08198">Figure 1</xref> shows the first height model of the Netherlands, and the acquisition plan of the AHN-2.</p>
<p>While the AHN-2 is coordinated by the Waterschapshuis (the executive body of the Dutch water boards in the area of information and communication technology) the acquisition and quality control of the data are done by private companies. The first acquisition was done by Fugro over Zeeland province in the winter of 2007 using the FLI-MAP 400 laser scanner system mounted on a helicopter [<xref ref-type="bibr" rid="b25-sensors-10-08198">25</xref>]. The FLI-MAP 400 system uses the Multiple Pulse in Air (MPiA) technique, which is the state of the art in airborne laser scanning technology. The MPiA technique allows the laser scanner to operate at a higher pulse frequency (375 KHz in the case of FLI-MAP 400) by emitting a second pulse before the reflection of the first one is received [<xref ref-type="bibr" rid="b26-sensors-10-08198">26</xref>]. The result is a substantial increase in the maximum flying height and the coverage of each laser strip, but also an increased point density on the ground for a given flying height.</p>
<p>The planned specifications of the AHN-2 data include an average density of 10 points per m<sup>2</sup> with 5 cm systematic error in height and 5 cm standard deviation. With such point density an object of 2 m by 2 m size can be correctly identified with a maximum planimetric error of 50 cm. The quality control procedures have been drafted by the Waterschapshuis, and executed by the companies NEO and Geodelta. The quality control consists of more than 40 procedures, including the point density check, the filtering of vegetation, the point distribution and the quality of the strip adjustment.</p>
<p>The quality control procedures are partly revised and modified every year. In 2008 the quality measures were derived by comparing corresponding elements in strip overlaps, but expressed for the entire coverage area. Since 2009 the quality measures are estimated and expressed per individual strip overlaps. The quality control procedures are not based on a standard methodology, and in fact there is a lack of reliable and commonly accepted methods for the quality control of laser altimetry data in practice.</p></sec>
<sec>
<label>3.</label>
<title>Strip Adjustment Using Planar Features</title>
<p>The airborne laser scanner data are normally acquired strip-wise, with across-track overlap, as shown in <xref ref-type="fig" rid="f2-sensors-10-08198">Figure 2</xref>. In an ideal dataset that is completely free of systematic errors corresponding planar features in the overlapping area should match perfectly. In practice, this is often not the case, and the distances between the planar features in the two strips can be used to evaluate the systematic and random errors in the data. The following sections describe the procedure for extracting planar features from laser data and the least-squares model for the estimation of the strip adjustment parameters.</p>
<sec sec-type="methods">
<label>3.1.</label>
<title>Extraction of Planar Features from Aerial Laser Data</title>
<p>Extracting planar features from laser altimetry data is usually done over urban areas where many buildings with planar roofs are available. There are many methods in the literature for detecting buildings and identifying roof planes in aerial laser data, e.g., [<xref ref-type="bibr" rid="b27-sensors-10-08198">27</xref>–<xref ref-type="bibr" rid="b32-sensors-10-08198">32</xref>]. In this study, a region growing segmentation method is used to extract planar features from gabled roofs or dike slopes. The points that belong to each strip in the overlapping area are interpolated into a raster format with a resolution of 50 centimeters using an Inverse Distance Interpolation algorithm based on the weighted average method [<xref ref-type="bibr" rid="b33-sensors-10-08198">33</xref>]. Slope and aspect orientation that best define the terrain in the vicinity of each point are derived. Homogenous regions are created by using a segmentation algorithm performed with the slope and aspect data. The size of the created regions is dependent on a scale parameter, which defines the maximum allowed heterogeneity within the resulting regions. The region-growing segmentation starts with single data points as initial regions, and repeatedly merges them into larger regions as long as a homogeneity criterion holds. The homogeneity criterion is controlled by the scale parameter: larger scale parameters result in larger regions, and smaller parameters in smaller regions [<xref ref-type="bibr" rid="b34-sensors-10-08198">34</xref>,<xref ref-type="bibr" rid="b35-sensors-10-08198">35</xref>]. To avoid overgrown regions, a suitable scale parameter is found experimentally. The segmentation is performed with different scale parameters on a subset of data, and the segmentation results are visually examined. The best scale parameter is selected as one that provides the largest regions which do not overgrow beyond the boundaries of the roofs or dike slopes.</p>
<p>Planar surfaces that represent gabled roofs and dike slopes are selected from the resulting regions by constraining the regions to a minimum area of 6 m<sup>2</sup> and a slope between 15 and 70 degrees. The boundaries of the corresponding regions in the two strips are combined and intersected. These intersected regions are buffered inwards with 25 cm (half the raster pixel size) to make sure that the points that are within the intersection area are part of the plane. These points are selected for the estimation of the plane parameters. As the segmentation is performed on gridded data, the selection criteria are not applied on the points directly. Therefore outliers in the selected point cloud might still be present after the segmentation process.</p></sec>
<sec>
<label>3.2.</label>
<title>Robust Plane Fitting Using RANSAC</title>
<p>The plane parameters are obtained by applying the Principal Component Analysis (PCA) to the selected points [<xref ref-type="bibr" rid="b36-sensors-10-08198">36</xref>]. The principal components are the axes of maximum variation of the data. For a set of points that lie on a plane the last principal component is the axis of minimum variation, which is normal to the plane. The principal components are found by the Singular Value Decomposition (SVD) of the mean-centered points. The eigenvector corresponding to the smallest eigenvalue is the last principal component that is the plane normal. The distance of the plane to the origin of the coordinate system is taken as the median of the dot product of the normal vector and the vector of each individual point.</p>
<p>The segmentation procedure does not necessarily always provide regions of points that are perfectly coplanar. In practice the regions might contain outliers, e.g., points on the walls, trees or the ground surface. To deal with the outlying points a robust plane fitting has to be applied to the points in both strips. Then only those points that are identified by the robust fitting algorithm as inliers are used to obtain the point-to-plane distances. The robust plane fitting is performed using the RANSAC algorithm [<xref ref-type="bibr" rid="b37-sensors-10-08198">37</xref>]. Considering that each random sample should contain three points (minimum to define a plane), and assuming that 50% of the points are outliers, 35 random samples are needed to ensure, with a probability of 99%, that at least one sample is outlier-free [<xref ref-type="bibr" rid="b38-sensors-10-08198">38</xref>]. The relatively small number of the required random samples indicates that the computational cost of the robust plane fitting is easily affordable. <xref ref-type="fig" rid="f3-sensors-10-08198">Figure 3</xref> demonstrates the robust plane fitting using RANSAC.</p></sec>
<sec>
<label>3.3.</label>
<title>Estimation of Strip Adjustment Parameters</title>
<p>The output of the previous step is a set of planes in one strip and their corresponding points in the other strip. The parameters of a transformation between the two overlapping strips are estimated by minimizing the distances between points and their corresponding planes. Let the transformation of a set of points <bold>P</bold> by a transformation <bold>H</bold> be expressed by matrix multiplication <bold>H P</bold>. The condition that the transformed points lie on a plane <bold>Л</bold> is expressed as [<xref ref-type="bibr" rid="b38-sensors-10-08198">38</xref>,<xref ref-type="bibr" rid="b39-sensors-10-08198">39</xref>]:
<disp-formula id="FD1">
<label>(1)</label>
<mml:math display="block">
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>Л</mml:mi></mml:mstyle></mml:mrow>
<mml:mi mathvariant="normal">T</mml:mi></mml:msup>
<mml:mrow>
<mml:mi mathvariant="bold">HP</mml:mi>
<mml:mo>=</mml:mo></mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mn>0</mml:mn></mml:mstyle></mml:mrow></mml:math></disp-formula>where <bold>Л</bold> = (<italic>n<sub>1</sub></italic>, <italic>n<sub>2</sub></italic>, <italic>n<sub>3</sub></italic>, <italic>−d</italic>)<sup>T</sup> represents a plane with normal <bold>n</bold> = (<italic>n</italic><italic><sub>1</sub></italic>, <italic>n<sub>2</sub></italic>, <italic>n<sub>3</sub></italic>)<sup>T</sup> and distance <italic>d</italic> to the origin, <bold>P</bold> = (<italic>x</italic>, <italic>y</italic>, <italic>z</italic>, <italic>1</italic>)<sup>T</sup> denotes the homogenous representation of a point in 3D space. In practice, <bold>H</bold> can be a homogenous similarity transformation:
<disp-formula id="FD2">
<label>(2)</label>
<mml:math display="block">
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>H</mml:mi></mml:mstyle>
<mml:mo>=</mml:mo>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:mtable columnalign="left">
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>R</mml:mi></mml:mstyle></mml:mtd>
<mml:mtd columnalign="left">
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>t</mml:mi></mml:mstyle></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mn>0</mml:mn></mml:mstyle></mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>×</mml:mo>
<mml:mn>3</mml:mn></mml:mrow></mml:msub></mml:mrow></mml:mtd>
<mml:mtd columnalign="left">
<mml:mn>1</mml:mn></mml:mtd></mml:mtr></mml:mtable></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow></mml:mrow></mml:math></disp-formula>in which <bold>R</bold> is a 3D rotation matrix, <bold>t</bold> = (<italic>t</italic><italic><sub>x</sub></italic>, <italic>t<sub>y</sub></italic>, <italic>t<sub>z</sub></italic>)<sup>T</sup> is a translation vector and a scale factor is neglected since laser strips are normally assumed to have identical scales. However, to make the estimation model linear, we ignore the orthogonality of R and assume that <bold>H</bold> is an affine transformation. To estimate the transformation <xref ref-type="disp-formula" rid="FD1">Equation (1)</xref> is rewritten as:
<disp-formula id="FD3">
<label>(3)</label>
<mml:math display="block">
<mml:mrow>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:mtable columnalign="left">
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>1</mml:mn></mml:msub></mml:mrow></mml:mtd>
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>2</mml:mn></mml:msub></mml:mrow></mml:mtd>
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>3</mml:mn></mml:msub></mml:mrow></mml:mtd>
<mml:mtd columnalign="left">
<mml:mrow>
<mml:mo>−</mml:mo>
<mml:mi>d</mml:mi></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:mtable columnalign="left">
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>r</mml:mi></mml:mstyle></mml:mrow>
<mml:mn>1</mml:mn>
<mml:mi mathvariant="normal">T</mml:mi></mml:msubsup></mml:mrow></mml:mtd>
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>x</mml:mi></mml:msub></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>r</mml:mi></mml:mstyle></mml:mrow>
<mml:mn>2</mml:mn>
<mml:mi mathvariant="normal">T</mml:mi></mml:msubsup></mml:mrow></mml:mtd>
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>y</mml:mi></mml:msub></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>r</mml:mi></mml:mstyle></mml:mrow>
<mml:mn>3</mml:mn>
<mml:mi mathvariant="normal">T</mml:mi></mml:msubsup></mml:mrow></mml:mtd>
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>z</mml:mi></mml:msub></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mn>0</mml:mn></mml:mstyle></mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>×</mml:mo>
<mml:mn>3</mml:mn></mml:mrow></mml:msub></mml:mrow></mml:mtd>
<mml:mtd columnalign="left">
<mml:mn>1</mml:mn></mml:mtd></mml:mtr></mml:mtable></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:mtable columnalign="left">
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>p</mml:mi></mml:mstyle></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mn>1</mml:mn></mml:mtd></mml:mtr></mml:mtable></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mo>=</mml:mo>
<mml:mn>0</mml:mn></mml:mrow></mml:math></disp-formula>where <bold>r</bold><sub>1</sub><sup>T</sup>, <bold>r</bold><sub>2</sub><sup>T</sup>, <bold>r</bold><sub>3</sub><sup>T</sup> are the three rows of <bold>R</bold>, and <bold>p</bold> = (<italic>x</italic>, <italic>y</italic>, <italic>z</italic>)<sup>T</sup> is the Euclidian notation of a point in 3D space. For one point on one plane <xref ref-type="disp-formula" rid="FD3">Equation (3)</xref> reduces to:
<disp-formula id="FD4">
<label>(4)</label>
<mml:math display="block">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>1</mml:mn></mml:msub>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>r</mml:mi></mml:mstyle></mml:mrow>
<mml:mn>1</mml:mn>
<mml:mi>T</mml:mi></mml:msubsup>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>p</mml:mi></mml:mstyle>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>x</mml:mi></mml:msub></mml:mrow>
<mml:mo>)</mml:mo></mml:mrow>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>2</mml:mn></mml:msub>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>r</mml:mi></mml:mstyle></mml:mrow>
<mml:mn>2</mml:mn>
<mml:mi>T</mml:mi></mml:msubsup>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>p</mml:mi></mml:mstyle>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>y</mml:mi></mml:msub></mml:mrow>
<mml:mo>)</mml:mo></mml:mrow>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>3</mml:mn></mml:msub>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>r</mml:mi></mml:mstyle></mml:mrow>
<mml:mn>3</mml:mn>
<mml:mi>T</mml:mi></mml:msubsup>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>p</mml:mi></mml:mstyle>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>z</mml:mi></mml:msub></mml:mrow>
<mml:mo>)</mml:mo></mml:mrow>
<mml:mo>=</mml:mo>
<mml:mi>d</mml:mi></mml:mrow></mml:math></disp-formula></p>
<p><xref ref-type="disp-formula" rid="FD4">Equation (4)</xref> is the essential observation equation that basically expresses the condition that the transformed points in one strip rest on their corresponding plane in the other strip. For <italic>m</italic> points corresponding to <italic>k</italic> planes we will have a system of equations as follows:
<disp-formula id="FD5">
<label>(5)</label>
<mml:math display="block">
<mml:mrow>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:mtable>
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>1</mml:mn>
<mml:mn>1</mml:mn></mml:msubsup>
<mml:msup>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>p</mml:mi></mml:mstyle></mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mn>1</mml:mn></mml:mrow>
<mml:mi mathvariant="normal">T</mml:mi></mml:msup></mml:mrow></mml:msup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>2</mml:mn>
<mml:mn>1</mml:mn></mml:msubsup>
<mml:msup>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>p</mml:mi></mml:mstyle></mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mn>1</mml:mn></mml:mrow>
<mml:mi mathvariant="normal">T</mml:mi></mml:msup></mml:mrow></mml:msup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>3</mml:mn>
<mml:mn>1</mml:mn></mml:msubsup>
<mml:msup>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>p</mml:mi></mml:mstyle></mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mn>1</mml:mn></mml:mrow>
<mml:mi mathvariant="normal">T</mml:mi></mml:msup></mml:mrow></mml:msup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>1</mml:mn>
<mml:mn>1</mml:mn></mml:msubsup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>2</mml:mn>
<mml:mn>1</mml:mn></mml:msubsup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>3</mml:mn>
<mml:mn>1</mml:mn></mml:msubsup></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mo>⋮</mml:mo></mml:mtd>
<mml:mtd>
<mml:mo>⋮</mml:mo></mml:mtd>
<mml:mtd>
<mml:mo>⋮</mml:mo></mml:mtd>
<mml:mtd>
<mml:mo>⋮</mml:mo></mml:mtd>
<mml:mtd>
<mml:mo>⋮</mml:mo></mml:mtd>
<mml:mtd>
<mml:mo>⋮</mml:mo></mml:mtd></mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>1</mml:mn>
<mml:mi>k</mml:mi></mml:msubsup>
<mml:msup>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>p</mml:mi></mml:mstyle></mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi>m</mml:mi></mml:mrow>
<mml:mi mathvariant="normal">T</mml:mi></mml:msup></mml:mrow></mml:msup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>2</mml:mn>
<mml:mi>k</mml:mi></mml:msubsup>
<mml:msup>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>p</mml:mi></mml:mstyle></mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi>m</mml:mi></mml:mrow>
<mml:mi mathvariant="normal">T</mml:mi></mml:msup></mml:mrow></mml:msup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>3</mml:mn>
<mml:mi>k</mml:mi></mml:msubsup>
<mml:msup>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>p</mml:mi></mml:mstyle></mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi>m</mml:mi></mml:mrow>
<mml:mi mathvariant="normal">T</mml:mi></mml:msup></mml:mrow></mml:msup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>1</mml:mn>
<mml:mi>k</mml:mi></mml:msubsup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>2</mml:mn>
<mml:mi>k</mml:mi></mml:msubsup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>3</mml:mn>
<mml:mi>k</mml:mi></mml:msubsup></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:mtable columnalign="left">
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>r</mml:mi></mml:mstyle></mml:mrow>
<mml:mn>1</mml:mn></mml:msub></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>r</mml:mi></mml:mstyle></mml:mrow>
<mml:mn>2</mml:mn></mml:msub></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mstyle fontweight="bold" fontstyle="normal">
<mml:mi>r</mml:mi></mml:mstyle></mml:mrow>
<mml:mn>3</mml:mn></mml:msub></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>x</mml:mi></mml:msub></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>y</mml:mi></mml:msub></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>z</mml:mi></mml:msub></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mo>=</mml:mo>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:mtable columnalign="left">
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi>d</mml:mi></mml:mrow>
<mml:mn>1</mml:mn></mml:msup></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mo>⋮</mml:mo></mml:mtd></mml:mtr>
<mml:mtr columnalign="left">
<mml:mtd columnalign="left">
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi>d</mml:mi></mml:mrow>
<mml:mi>k</mml:mi></mml:msup></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow></mml:mrow></mml:math></disp-formula>where superscripts denote the point and plane numbers. The system of <xref ref-type="disp-formula" rid="FD5">Equation (5)</xref> is of the form AX = L for which the least-squares solution that minimizes the norm of the squared distances between the transformed points and their corresponding planes, <italic>i.e.</italic>, ||AX − L||, is given in <xref ref-type="disp-formula" rid="FD6">Equation (6)</xref>:
<disp-formula id="FD6">
<label>(6)</label>
<mml:math display="block">
<mml:mrow>
<mml:mi mathvariant="bold">X</mml:mi>
<mml:mo>=</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false" mathvariant="bold">(</mml:mo>
<mml:msup>
<mml:mi mathvariant="bold">A</mml:mi>
<mml:mi mathvariant="bold">T</mml:mi></mml:msup>
<mml:mi mathvariant="bold">WA</mml:mi>
<mml:mo stretchy="false" mathvariant="bold">)</mml:mo></mml:mrow>
<mml:mrow>
<mml:mo mathvariant="bold">−</mml:mo>
<mml:mn mathvariant="bold">1</mml:mn></mml:mrow></mml:msup>
<mml:msup>
<mml:mi mathvariant="bold">A</mml:mi>
<mml:mi mathvariant="bold">T</mml:mi></mml:msup>
<mml:mi mathvariant="bold">WL</mml:mi></mml:mrow></mml:math></disp-formula>where <bold>W</bold> is a weight matrix. In this paper, the same weight is applied to each observable based on the assumption that all observables have the same precision.</p>
<p>A special case of the strip adjustment model as described above occurs when we expect the transformation between the strips to be only a translation vector. In such a case, the estimation model given in <xref ref-type="disp-formula" rid="FD4">Equation (4)</xref> reduces to:
<disp-formula id="FD7">
<label>(7)</label>
<mml:math display="block">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>1</mml:mn></mml:msub>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>x</mml:mi>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>x</mml:mi></mml:msub>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>2</mml:mn></mml:msub>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>y</mml:mi>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>y</mml:mi></mml:msub>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>3</mml:mn></mml:msub>
<mml:mo stretchy="false">(</mml:mo>
<mml:mi>z</mml:mi>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>z</mml:mi></mml:msub>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>=</mml:mo>
<mml:mi>d</mml:mi></mml:mrow></mml:math></disp-formula>which basically expresses that the translated points lie on the plane. The system of equations with <italic>m</italic> points and <italic>k</italic> planes becomes:
<disp-formula id="FD8">
<label>(8)</label>
<mml:math display="block">
<mml:mrow>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:mtable>
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>1</mml:mn>
<mml:mn>1</mml:mn></mml:msubsup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>2</mml:mn>
<mml:mn>1</mml:mn></mml:msubsup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>3</mml:mn>
<mml:mn>1</mml:mn></mml:msubsup></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mo>⋮</mml:mo></mml:mtd>
<mml:mtd>
<mml:mo>⋮</mml:mo></mml:mtd>
<mml:mtd>
<mml:mo>⋮</mml:mo></mml:mtd></mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>1</mml:mn>
<mml:mi>k</mml:mi></mml:msubsup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>2</mml:mn>
<mml:mi>k</mml:mi></mml:msubsup></mml:mrow></mml:mtd>
<mml:mtd>
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>3</mml:mn>
<mml:mi>k</mml:mi></mml:msubsup></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:mtable>
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>x</mml:mi></mml:msub></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>y</mml:mi></mml:msub></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>t</mml:mi></mml:mrow>
<mml:mi>z</mml:mi></mml:msub></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow>
<mml:mo>=</mml:mo>
<mml:mrow>
<mml:mo>[</mml:mo>
<mml:mrow>
<mml:mtable>
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi>d</mml:mi></mml:mrow>
<mml:mn>1</mml:mn></mml:msup>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>1</mml:mn>
<mml:mn>1</mml:mn></mml:msubsup>
<mml:msup>
<mml:mrow>
<mml:mi>x</mml:mi></mml:mrow>
<mml:mn>1</mml:mn></mml:msup>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>2</mml:mn>
<mml:mn>1</mml:mn></mml:msubsup>
<mml:msup>
<mml:mrow>
<mml:mi>y</mml:mi></mml:mrow>
<mml:mn>1</mml:mn></mml:msup>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>3</mml:mn>
<mml:mn>1</mml:mn></mml:msubsup>
<mml:msup>
<mml:mrow>
<mml:mi>z</mml:mi></mml:mrow>
<mml:mn>1</mml:mn></mml:msup></mml:mrow></mml:mtd></mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mo>⋮</mml:mo></mml:mtd></mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi>d</mml:mi></mml:mrow>
<mml:mi>k</mml:mi></mml:msup>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>1</mml:mn>
<mml:mi>k</mml:mi></mml:msubsup>
<mml:msup>
<mml:mrow>
<mml:mi>x</mml:mi></mml:mrow>
<mml:mi>m</mml:mi></mml:msup>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>2</mml:mn>
<mml:mi>k</mml:mi></mml:msubsup>
<mml:msup>
<mml:mrow>
<mml:mi>y</mml:mi></mml:mrow>
<mml:mi>m</mml:mi></mml:msup>
<mml:mo>−</mml:mo>
<mml:msubsup>
<mml:mrow>
<mml:mi>n</mml:mi></mml:mrow>
<mml:mn>3</mml:mn>
<mml:mi>k</mml:mi></mml:msubsup>
<mml:msup>
<mml:mrow>
<mml:mi>z</mml:mi></mml:mrow>
<mml:mi>m</mml:mi></mml:msup></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:mrow>
<mml:mo>]</mml:mo></mml:mrow></mml:mrow></mml:math></disp-formula>for which a solution that minimizes the distances between the translated points and their corresponding planes can be obtained similar to the general case as given in <xref ref-type="disp-formula" rid="FD6">Equation (6)</xref>.</p>
<p>It is worth noting that to obtain a solution for the estimation models derived above the design matrices in <xref ref-type="disp-formula" rid="FD5">Equations (5)</xref> and <xref ref-type="disp-formula" rid="FD8">(8)</xref> have to be of full rank. This requires a minimum of 12 points and 3 non-parallel planes to estimate the affine transformation in <xref ref-type="disp-formula" rid="FD5">Equation (5)</xref>, and a minimum of 3 points and 3 non-parallel planes to estimate the translation vector in <xref ref-type="disp-formula" rid="FD8">Equation (8)</xref>. In practice, this is not an issue since usually a large number of point-to-plane distances are available.</p>
<p>The precision of the observables as well as the estimated transformation parameters are derived from the residual vector <bold>v</bold> that actually contains the remaining point-to-plane distances after the adjustment:
<disp-formula id="FD9">
<label>(9)</label>
<mml:math display="block">
<mml:mrow>
<mml:mi mathvariant="bold">v</mml:mi>
<mml:mo>=</mml:mo>
<mml:mi mathvariant="bold">AX</mml:mi>
<mml:mo>−</mml:mo>
<mml:mi mathvariant="bold">L</mml:mi></mml:mrow></mml:math></disp-formula></p>
<p>The reference variance obtained from the residual vector <bold>v</bold> is an indication of the precision of the observables, or the random error of individual points:
<disp-formula id="FD10">
<label>(10)</label>
<mml:math display="block">
<mml:mrow>
<mml:msubsup>
<mml:mrow>
<mml:mi>σ</mml:mi></mml:mrow>
<mml:mn>0</mml:mn>
<mml:mn>2</mml:mn></mml:msubsup>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msup>
<mml:mi mathvariant="bold">v</mml:mi>
<mml:mi mathvariant="bold">T</mml:mi></mml:msup>
<mml:mi> </mml:mi>
<mml:mi> </mml:mi>
<mml:mi mathvariant="bold">W</mml:mi>
<mml:mi> </mml:mi>
<mml:mi> </mml:mi>
<mml:mi mathvariant="bold">v</mml:mi></mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
<mml:mo>−</mml:mo>
<mml:mi>u</mml:mi></mml:mrow></mml:mfrac></mml:mrow></mml:math></disp-formula>where <italic>u</italic> is the number of unknown parameters in the adjustment. The precision of the estimated transformation parameters is then obtained by:
<disp-formula id="FD11">
<label>(11)</label>
<mml:math display="block">
<mml:mrow>
<mml:msub>
<mml:mo mathvariant="bold">Σ</mml:mo>
<mml:mrow>
<mml:mi mathvariant="bold">xx</mml:mi></mml:mrow></mml:msub>
<mml:mo>=</mml:mo>
<mml:msubsup>
<mml:mi>σ</mml:mi>
<mml:mn>0</mml:mn>
<mml:mn>2</mml:mn></mml:msubsup>
<mml:msup>
<mml:mrow>
<mml:mo stretchy="false" mathvariant="bold">(</mml:mo>
<mml:msup>
<mml:mi mathvariant="bold">A</mml:mi>
<mml:mi mathvariant="bold">T</mml:mi></mml:msup>
<mml:mo> </mml:mo>
<mml:mi mathvariant="bold">W</mml:mi>
<mml:mo> </mml:mo>
<mml:mi mathvariant="bold">A</mml:mi>
<mml:mo stretchy="false" mathvariant="bold">)</mml:mo></mml:mrow>
<mml:mrow>
<mml:mo mathvariant="bold">−</mml:mo>
<mml:mn mathvariant="bold">1</mml:mn></mml:mrow></mml:msup></mml:mrow></mml:math></disp-formula></p></sec></sec>
<sec sec-type="methods|results">
<label>4.</label>
<title>Results of Accuracy Assessment of AHN-2 Data</title>
<sec sec-type="methods">
<label>4.1.</label>
<title>Description of Dataset</title>
<p>The strip adjustment method as described above was employed to assess the accuracy of the pilot AHN-2 dataset acquired by Fugro-Inpark over Zeeland province in 2007. The area consists of a crop land with large farm buildings and several urban areas, of which the city of Flushing is the largest. The data were acquired by the helicopter-mounted FLI-MAP 400 laser scanner from an altitude of 375 meters. The data consists of the forward-, nadir- and backward-looking scan lines. From this dataset, 15 strips were selected, resulting in 13 overlaps, as shown in <xref ref-type="fig" rid="f4-sensors-10-08198">Figure 4</xref>. <xref ref-type="table" rid="t1-sensors-10-08198">Table 1</xref> lists the overlaps and their corresponding strips, number of points and width of each overlap. The overlap areas are of different sizes. Within each overlap also the numbers of points belonging to each strip are slightly different, which is due to the difference in the scanning geometry, the topography and the type of objects present in the overlap area.</p></sec>
<sec>
<label>4.2.</label>
<title>Evaluation of Segmentation</title>
<p>To evaluate the performance of the segmentation procedure strip overlap o12 was segmented with different scale parameters. The resulting roof regions were examined and compared with building boundaries from an existing large scale base map and with aerial images of the area. The result is shown in <xref ref-type="fig" rid="f5-sensors-10-08198">Figure 5</xref>. Scale parameters 10 and 15 provide the most reliable roof segments. Scale parameter 15 provides more segments that are also larger in size; therefore, it is chosen as the optimal scale parameter.</p>
<p><xref ref-type="fig" rid="f6-sensors-10-08198">Figure 6</xref> shows an example of roof segments created by using three different scale parameters. The segments are shown in yellow outlines. The building on the left has a dormer on the right roof side. It can be seen that by using scale parameter 20 one of the created segments is overgrown and contains points on the dormer. In contrast, scale parameter 15 provides homogeneous segments within the roof boundaries. The irregularity in the shape of the segments is due to the intersection of the segments in the two strips and the applied inwards buffering.</p></sec>
<sec sec-type="results">
<label>4.3.</label>
<title>Accuracy Assessment Results</title>
<p>The point-to-plane distances were derived for each strip overlap from the segmentation results. For every region in one strip plane parameters were computed using the robust plane fitting method. Then, distances between this plane and the inlying points in the corresponding region in the other strip were obtained and entered as observables in the estimation model. Two transformations were estimated for each pair of overlapping strips: a 3D translation only and a full affine transformation.</p>
<p>The mean and standard deviation of the point-to-plane distances before and after the adjustment were computed. Assuming that the data are not contaminated by gross errors (outliers), the mean before the adjustment indicates systematic error in the data. After the adjustment, the mean is expected to be very small, and the standard deviation indicates the random error of the observables and the precision of the estimated parameters. <xref ref-type="fig" rid="f7-sensors-10-08198">Figure 7</xref> shows the mean of the point-to-plane distances before and after the adjustment. Before the adjustment the mean ranges from −3 cm to 2 cm. Adjustment with only a translation reduces the mean in all overlaps, except for overlap o2 (although here the mean is only −1 cm). Adjustment with a full transformation further reduces the mean to values below ±5 mm. <xref ref-type="fig" rid="f8-sensors-10-08198">Figure 8</xref> shows the standard deviation of the point-to-plane distances before and after the adjustment. Before the adjustment the standard deviations range from 3 cm to 11 cm. These become smaller after the translation (2 cm to 8 cm), and are the smallest after the full transformation where the largest standard deviation is 5 cm.</p>
<p><xref ref-type="fig" rid="f9-sensors-10-08198">Figure 9</xref> and <xref ref-type="fig" rid="f10-sensors-10-08198">Figure 10</xref> show the estimated horizontal offsets respectively in x and y direction together with their precision for all strip overlaps. These values are compared to those obtained by a line-based method [<xref ref-type="bibr" rid="b40-sensors-10-08198">40</xref>], which provides only 2D translation parameters. The precision of the estimated parameters is remarkably better in all overlaps when point-to-plane distances are used. Both T<sub>x</sub> and T<sub>y</sub> are estimated with a precision better than 1 mm. In most of the overlaps, the estimated horizontal offsets are in agreement with those obtained by the line-based method. The discrepancies are in overlaps o6 (T<sub>x</sub>), o7 (T<sub>y</sub>) and o9 (both T<sub>x</sub> and T<sub>y</sub>), where differences from 10 cm to 20 cm can be observed. In the case of overlap o9, the precision of both T<sub>x</sub> and T<sub>y</sub> estimated from the line correspondences is very low, whereas the offsets estimated from the point-to-plane distances using both adjustment models are more precise and very close in magnitude. In fact, both T<sub>x</sub> and T<sub>y</sub> estimated from point-to-plane distances are within the range of uncertainty of the offsets estimated by the line-based method. In overlap o6 also the T<sub>x</sub> values estimated by the plane-based method using both adjustment models are very close and more precise than that estimated by the line-based method. The disagreement in T<sub>y</sub> corresponding to overlap o7 may be due to the presence of a small rotation between the strips. Note that the mean and standard deviation of the point-to-plane distances after the adjustment with a translation only and those after the full affine transformation have the largest discrepancy in overlap o7 (see <xref ref-type="fig" rid="f7-sensors-10-08198">Figure 7</xref> and <xref ref-type="fig" rid="f8-sensors-10-08198">Figure 8</xref>).</p>
<p><xref ref-type="fig" rid="f11-sensors-10-08198">Figure 11</xref> shows the vertical offsets T<sub>z</sub> estimated from the point-to-plane distances for all overlaps. Here the bars representing the precision of the offsets are magnified by a factor of 10. It can be seen that the vertical offsets resulting from the two transformation models are very close. A difference of about 1 cm can be observed in overlap o7, which again might imply the presence of a small rotation between the strips. The precision of the estimated vertical offsets is better than 2 mm.</p></sec></sec>
<sec sec-type="conclusions">
<label>5.</label>
<title>Conclusions</title>
<p>We have presented a method for the adjustment and accuracy assessment of airborne laser altimetry strips using planar features. The choice of planar features is particularly appropriate for the accuracy assessment of AHN-2 data over the Netherlands, because buildings with gable roof planes are present almost in all parts of the country, and also the high point density of the AHN-2 data is a determining factor in the increased reliability of the extracted planes. The method is based on estimating a transformation between two overlapping strips by minimizing the distances between points in one strip and their corresponding planes in the other. The accuracy assessment of the AHN-2 laser dataset over Zeeland, the Netherlands, was carried out using the proposed plane-based method, and the results were compared with those of a previously-used line-based method. The results show vertical offsets of up to 4 cm between the overlapping strips, and horizontal offsets ranging from 2 cm to 34 cm.</p>
<p>In comparison with the line-based methods, the use of planar features in strip adjustment leads to a more precise estimation of the transformation parameters. The performance of the plane-based methods is, however, dependent on the reliability of the extracted planes. Despite careful selection of the segmentation parameters we found many segments that contained outliers. The robust plane fitting using RANSAC proved very effective in removing these outlying points. In conclusion, for the plane-based strip adjustment method to be used in practice for the quality control of laser altimetry data robust and reliable plane extraction algorithms are of great importance.</p></sec></body>
<back>
<ack>
<p>The authors would like to thank the AHN steering committee for providing the dataset and ancillary data of Zeeland.</p></ack>
<ref-list>
<title>References</title>
<ref id="b1-sensors-10-08198"><label>1.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Wouters</surname><given-names>W</given-names></name><name><surname>Bollweg</surname><given-names>A</given-names></name></person-group><article-title>A Detailed Elevation Model Using Airborne Laser Altimetry</article-title><source>Geodetic Info Mag</source><year>1998</year><volume>9</volume><fpage>6</fpage><lpage>9</lpage></citation></ref>
<ref id="b2-sensors-10-08198"><label>2.</label><citation citation-type="web"><source>Actualisatie van het AHN</source><publisher-name>Waterschapshuis</publisher-name><publisher-loc>Utrecht, The Netherlands</publisher-loc><comment>Available online: <ext-link xlink:href="http://www.ahn.nl/actualisatie_van_het" ext-link-type="uri">http://www.ahn.nl/actualisatie_van_het</ext-link> (accessed on 23 June 2010).</comment></citation></ref>
<ref id="b3-sensors-10-08198"><label>3.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Huising</surname><given-names>EJ</given-names></name><name><surname>Gomes Pereira</surname><given-names>LM</given-names></name></person-group><article-title>Errors and Accuracy Estimates of Laser Data Acquired by Various Laser Scanning Systems for Topographic Applications</article-title><source>ISPRS J. Photogramm</source><year>1998</year><volume>53</volume><fpage>245</fpage><lpage>261</lpage><pub-id pub-id-type="doi">10.1016/S0924-2716(98)00013-6</pub-id></citation></ref>
<ref id="b4-sensors-10-08198"><label>4.</label><citation citation-type="book"><person-group person-group-type="author"><name><surname>Schenk</surname><given-names>T</given-names></name></person-group><source>Modeling and Analyzing Systematic Errors in Airborne Laser Scanners</source><comment>Technical Notes in Photogrammetry No 19</comment><publisher-name>The Ohio State University</publisher-name><publisher-loc>Columbus, OH, USA</publisher-loc><year>2001</year></citation></ref>
<ref id="b5-sensors-10-08198"><label>5.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Baltsavias</surname><given-names>E</given-names></name></person-group><article-title>Airborne Laser Scanning: Basic Relations and Formulas</article-title><source>ISPRS J. Photogramm</source><year>1999</year><volume>54</volume><fpage>199</fpage><lpage>214</lpage><pub-id pub-id-type="doi">10.1016/S0924-2716(99)00015-5</pub-id></citation></ref>
<ref id="b6-sensors-10-08198"><label>6.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Kilian</surname><given-names>J</given-names></name><name><surname>Haala</surname><given-names>N</given-names></name><name><surname>Englich</surname><given-names>M</given-names></name></person-group><article-title>Capture and Evaluation of Airborne Laser Scanner Data</article-title><conf-name>Proceedings of International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences</conf-name><conf-loc>Vienna, Austria</conf-loc><conf-date>12–18 July 1996</conf-date><fpage>383</fpage><lpage>388</lpage></citation></ref>
<ref id="b7-sensors-10-08198"><label>7.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Hodgson</surname><given-names>ME</given-names></name><name><surname>Bresnahan</surname><given-names>P</given-names></name></person-group><article-title>Accuracy of Airborne Lidar-Derived Elevation: Empirical Assessment and Error Budget</article-title><source>Photogramm. Eng. Remote Sensing</source><year>2004</year><volume>70</volume><fpage>331</fpage><lpage>339</lpage></citation></ref>
<ref id="b8-sensors-10-08198"><label>8.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Triglav-Cekada</surname><given-names>M</given-names></name><name><surname>Crosilla</surname><given-names>F</given-names></name><name><surname>Kosmatin-Fras</surname><given-names>M</given-names></name></person-group><article-title>A Simplified Analytical Model for A-Priori Lidar Point-Positioning Error Estimation and a Review of Lidar Error Sources</article-title><source>Photogramm. Eng. Remote Sensing</source><year>2009</year><volume>75</volume><fpage>1425</fpage><lpage>1439</lpage></citation></ref>
<ref id="b9-sensors-10-08198"><label>9.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Habib</surname><given-names>A</given-names></name><name><surname>Bang</surname><given-names>K</given-names></name><name><surname>Kersting</surname><given-names>A</given-names></name><name><surname>Lee</surname><given-names>D-C</given-names></name></person-group><article-title>Error Budget of Lidar Systems and Quality Control of the Derived Data</article-title><source>Photogramm. Eng. Remote Sensing</source><year>2009</year><volume>75</volume><fpage>1093</fpage><lpage>1108</lpage></citation></ref>
<ref id="b10-sensors-10-08198"><label>10.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Crombaghs</surname><given-names>MJE</given-names></name><name><surname>Brugelmann</surname><given-names>R</given-names></name><name><surname>de Min</surname><given-names>EJ</given-names></name></person-group><article-title>On the Adjustment of Overlapping Strips of Laser Altimeter Height Data</article-title><conf-name>Proceedings of International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences</conf-name><conf-loc>Amsterdam, The Netherlands</conf-loc><conf-date>16–22 July 2000</conf-date><fpage>230</fpage><lpage>237</lpage></citation></ref>
<ref id="b11-sensors-10-08198"><label>11.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Csanyi</surname><given-names>N</given-names></name><name><surname>Toth</surname><given-names>CK</given-names></name></person-group><article-title>Improvement of Lidar Data Accuracy Using Lidar-Specific Ground Targets</article-title><source>Photogramm. Eng. Remote Sensing</source><year>2007</year><volume>73</volume><fpage>385</fpage><lpage>396</lpage></citation></ref>
<ref id="b12-sensors-10-08198"><label>12.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Bretar</surname><given-names>F</given-names></name><name><surname>Pierrot-Deseilligny</surname><given-names>M</given-names></name><name><surname>Roux</surname><given-names>M</given-names></name></person-group><article-title>Solving the Strip Adjustment Problem of 3D Airborne Lidar Data</article-title><conf-name>Proceedings of International Geoscience and Remote Sensing Symposium</conf-name><conf-loc>Anchorage, AK, USA</conf-loc><conf-date>20–24 September 2004</conf-date><fpage>4734</fpage><lpage>4737</lpage></citation></ref>
<ref id="b13-sensors-10-08198"><label>13.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Vosselman</surname><given-names>G</given-names></name></person-group><article-title>Analysis of Planimetric Accuracy of Airborne Laser Scanning Surveys</article-title><conf-name>Proceedings of International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences</conf-name><conf-loc>Beijing, China</conf-loc><conf-date>3–11 July 2008</conf-date><fpage>99</fpage><lpage>104</lpage></citation></ref>
<ref id="b14-sensors-10-08198"><label>14.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Vosselman</surname><given-names>G</given-names></name></person-group><article-title>On the Estimation of Planimetric Offsets in Laser Altimetry Data</article-title><conf-name>Proceedings of International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences</conf-name><conf-loc>Graz, Austria</conf-loc><conf-date>9–13 September 2002</conf-date><fpage>375</fpage><lpage>380</lpage></citation></ref>
<ref id="b15-sensors-10-08198"><label>15.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Lee</surname><given-names>J</given-names></name><name><surname>Yu</surname><given-names>KJ</given-names></name><name><surname>Kim</surname><given-names>Y</given-names></name><name><surname>Habib</surname><given-names>AF</given-names></name></person-group><article-title>Adjustment of Discrepancies between LIDAR Data Strips Using Linear Features</article-title><source>IEEE Geosci. Remote Sens. Lett</source><year>2007</year><volume>4</volume><fpage>475</fpage><lpage>479</lpage><pub-id pub-id-type="doi">10.1109/LGRS.2007.898079</pub-id></citation></ref>
<ref id="b16-sensors-10-08198"><label>16.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Habib</surname><given-names>AF</given-names></name><name><surname>Kersting</surname><given-names>AP</given-names></name><name><surname>Ruifang</surname><given-names>Z</given-names></name><name><surname>Al Durgham</surname><given-names>M</given-names></name><name><surname>Kim</surname><given-names>C</given-names></name><name><surname>Lee</surname><given-names>DC</given-names></name></person-group><article-title>LIDAR Strip Adjustment Using Conjugate Linear Features in Overlapping Strips</article-title><conf-name>Proceedings of International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences</conf-name><conf-loc>Beijing, China</conf-loc><conf-date>3–11 July 2008</conf-date><fpage>385</fpage><lpage>390</lpage></citation></ref>
<ref id="b17-sensors-10-08198"><label>17.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Rentsch</surname><given-names>M</given-names></name><name><surname>Krzystek</surname><given-names>P</given-names></name></person-group><article-title>LiDAR Strip Adjustment using Automatically Reconstructed Roof Shapes</article-title><conf-name>Proceedings of International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences</conf-name><conf-loc>Hannover, Germany</conf-loc><conf-date>2–5 June 2009</conf-date><fpage>158</fpage><lpage>164</lpage></citation></ref>
<ref id="b18-sensors-10-08198"><label>18.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Ressl</surname><given-names>C</given-names></name><name><surname>Mandlburgera</surname><given-names>G</given-names></name><name><surname>Pfeifer</surname><given-names>N</given-names></name></person-group><article-title>Investigating Adjustment of Airborne Laser Scanning Strips without Usage of GNSS/IMU Trajectory Data</article-title><conf-name>Proceedings of ISPRS Workshop, “Laser scanning 2009”</conf-name><conf-loc>Paris, France</conf-loc><conf-date>1–2 September 2009</conf-date><fpage>195</fpage><lpage>200</lpage></citation></ref>
<ref id="b19-sensors-10-08198"><label>19.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Latypov</surname><given-names>D</given-names></name></person-group><article-title>Estimating Relative Lidar Accuracy Information from Overlapping Flight Lines</article-title><source>ISPRS J. Photogramm. Remote Sensing</source><year>2002</year><volume>56</volume><fpage>236</fpage><lpage>245</lpage><pub-id pub-id-type="doi">10.1016/S0924-2716(02)00047-3</pub-id></citation></ref>
<ref id="b20-sensors-10-08198"><label>20.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Pfeifer</surname><given-names>N</given-names></name><name><surname>Oude Elberink</surname><given-names>S</given-names></name><name><surname>Filin</surname><given-names>S</given-names></name></person-group><article-title>Automatic Tie Elements Detection for Laser Scanner Strip Adjustment</article-title><conf-name>Proceedings of International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences</conf-name><conf-loc>Enschede, the Netherlands</conf-loc><conf-date>12–14 September 2005</conf-date></citation></ref>
<ref id="b21-sensors-10-08198"><label>21.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Filin</surname><given-names>S</given-names></name></person-group><article-title>Recovery of Systematic Biases in Laser Altimetry Data Using Natural Surfaces</article-title><source>Photogramm. Eng. Remote Sensing</source><year>2003</year><volume>69</volume><fpage>1235</fpage><lpage>1242</lpage></citation></ref>
<ref id="b22-sensors-10-08198"><label>22.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Kager</surname><given-names>H</given-names></name></person-group><article-title>Discrepancies between Overlapping Laser Scanner Strips-Simultaneous Fitting of Aerial Laser Scanner Strips</article-title><conf-name>Proceedings of International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences</conf-name><conf-loc>Istanbul, Turkey</conf-loc><conf-date>12–23 July 2004</conf-date><fpage>555</fpage><lpage>560</lpage></citation></ref>
<ref id="b23-sensors-10-08198"><label>23.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Maas</surname><given-names>HG</given-names></name></person-group><article-title>Methods for Measuring Height and Planimetry Discrepancies in Airborne Laserscanner Data</article-title><source>Photogramm. Eng. Remote Sensing</source><year>2002</year><volume>68</volume><fpage>933</fpage><lpage>940</lpage></citation></ref>
<ref id="b24-sensors-10-08198"><label>24.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Habib</surname><given-names>A</given-names></name><name><surname>Kersting</surname><given-names>AP</given-names></name><name><surname>Bang</surname><given-names>KI</given-names></name><name><surname>Lee</surname><given-names>DC</given-names></name></person-group><article-title>Alternative Methodologies for the Internal Quality Control of Parallel LiDAR Strips</article-title><source>IEEE Trans. Geosci. Remote Sens</source><year>2010</year><volume>48</volume><fpage>221</fpage><lpage>236</lpage><pub-id pub-id-type="doi">10.1109/TGRS.2009.2026424</pub-id></citation></ref>
<ref id="b25-sensors-10-08198"><label>25.</label><citation citation-type="book"><person-group person-group-type="author"><collab>Inwinning AHN-2 met nieuw FLI-MAP 400-systeem</collab></person-group><source>Fugro Info juni 2008</source><publisher-name>Fugro Nederland</publisher-name><publisher-loc>Amsterdam, the Netherlands</publisher-loc><year>2008</year></citation></ref>
<ref id="b26-sensors-10-08198"><label>26.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Roth</surname><given-names>RB</given-names></name><name><surname>Thompson</surname><given-names>J</given-names></name></person-group><article-title>Practical Application of Multiple Pulse in Air (MPIA) Lidar in Large-Area Surveys</article-title><conf-name>Proceedings of International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences</conf-name><conf-loc>Beijing, China</conf-loc><conf-date>3–11 July 2008</conf-date><fpage>183</fpage><lpage>188</lpage></citation></ref>
<ref id="b27-sensors-10-08198"><label>27.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Khoshelham</surname><given-names>K</given-names></name><name><surname>Li</surname><given-names>ZL</given-names></name><name><surname>King</surname><given-names>B</given-names></name></person-group><article-title>A Split-and-Merge Technique for Automated Reconstruction of Roof Planes</article-title><source>Photogramm. Eng. Remote Sensing</source><year>2005</year><volume>71</volume><fpage>855</fpage><lpage>862</lpage></citation></ref>
<ref id="b28-sensors-10-08198"><label>28.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Khoshelham</surname><given-names>K</given-names></name><name><surname>Nardinocchi</surname><given-names>C</given-names></name><name><surname>Frontoni</surname><given-names>E</given-names></name><name><surname>Mancini</surname><given-names>A</given-names></name><name><surname>Zingaretti</surname><given-names>P</given-names></name></person-group><article-title>Performance Evaluation of Automated Approaches to Building Detection in multi-Source Aerial Data</article-title><source>ISPRS J. Photogramm. Remote Sensing</source><year>2010</year><volume>65</volume><fpage>123</fpage><lpage>133</lpage><pub-id pub-id-type="doi">10.1016/j.isprsjprs.2009.09.005</pub-id></citation></ref>
<ref id="b29-sensors-10-08198"><label>29.</label><citation citation-type="book"><person-group person-group-type="author"><name><surname>Nardinocchi</surname><given-names>C</given-names></name><name><surname>Forlani</surname><given-names>G</given-names></name></person-group><article-title>Building Detection and Roof Extraction in Laser Scanning Data</article-title><source>Automatic Extraction of Man-Made Objects from Aerial and Space Images</source><person-group person-group-type="editor"><name><surname>Gruen</surname><given-names>A</given-names></name><name><surname>Baltsavias</surname><given-names>EP</given-names></name><name><surname>van Gool</surname><given-names>L</given-names></name></person-group><publisher-name>Balkema</publisher-name><publisher-loc>Lisse, The Netherlands</publisher-loc><year>2001</year><fpage>319</fpage><lpage>330</lpage></citation></ref>
<ref id="b30-sensors-10-08198"><label>30.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Rottensteiner</surname><given-names>F</given-names></name><name><surname>Trinder</surname><given-names>J</given-names></name><name><surname>Clode</surname><given-names>S</given-names></name><name><surname>Kubik</surname><given-names>K</given-names></name></person-group><article-title>Building Detection by Fusion of Airborne Laser Scanner Data and multi-Spectral Images: Performance Evaluation and Sensitivity Analysis</article-title><source>ISPRS J. Photogramm. Remote Sensing</source><year>2007</year><volume>62</volume><fpage>135</fpage><lpage>149</lpage><pub-id pub-id-type="doi">10.1016/j.isprsjprs.2007.03.001</pub-id></citation></ref>
<ref id="b31-sensors-10-08198"><label>31.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Vosselman</surname><given-names>G</given-names></name><name><surname>Gorte</surname><given-names>BG</given-names></name><name><surname>Sithole</surname><given-names>G</given-names></name><name><surname>Rabbani Shah</surname><given-names>T</given-names></name></person-group><article-title>Recognising Structure in Laser Scanner Point Cloud</article-title><conf-name>Proceedings of International Archives of Photogrammetry, Remote Sensing and Spatial Information Sciences</conf-name><conf-loc>Freiburg, Germany</conf-loc><conf-date>3–6 October 2004</conf-date><fpage>33</fpage><lpage>38</lpage></citation></ref>
<ref id="b32-sensors-10-08198"><label>32.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Weidner</surname><given-names>U</given-names></name><name><surname>Forstner</surname><given-names>W</given-names></name></person-group><article-title>Towards Automatic Building Extraction from High Resolution Digital Elevation Models</article-title><source>ISPRS J. Photogramm. Remote Sensing</source><year>1995</year><volume>50</volume><fpage>38</fpage><lpage>49</lpage></citation></ref>
<ref id="b33-sensors-10-08198"><label>33.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Weber</surname><given-names>D</given-names></name><name><surname>Englund</surname><given-names>E</given-names></name></person-group><article-title>Evaluation and Comparison of Spatial Interpolators II</article-title><source>Math. Geol</source><year>1994</year><volume>26</volume><fpage>589</fpage><lpage>603</lpage><pub-id pub-id-type="doi">10.1007/BF02089243</pub-id></citation></ref>
<ref id="b34-sensors-10-08198"><label>34.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Baatz</surname><given-names>M</given-names></name><name><surname>Schape</surname><given-names>A</given-names></name></person-group><article-title>Multiresolution Segmentation: An Optimization Approach for High Quality Multi-Scale Image Segmentation</article-title><source>J. Photogram. Remote Sensing</source><year>2000</year><volume>58</volume><fpage>12</fpage><lpage>23</lpage></citation></ref>
<ref id="b35-sensors-10-08198"><label>35.</label><citation citation-type="web"><source>Definiens Developer 7—Reference Book</source><publisher-name>Definiens AG</publisher-name><publisher-loc>Munich, Germany</publisher-loc><year>2007</year><fpage>197</fpage><comment>Available online: <ext-link xlink:href="http://www.ecognition.cc/download/ReferenceBook" ext-link-type="uri">http://www.ecognition.cc/download/ReferenceBook</ext-link></comment></citation></ref>
<ref id="b36-sensors-10-08198"><label>36.</label><citation citation-type="book"><person-group person-group-type="author"><name><surname>Jensen</surname><given-names>JR</given-names></name></person-group><source>Introductory Digital Image Processing</source><publisher-name>Prentice Hall PTR</publisher-name><publisher-loc>Upper Saddle River, NJ, USA</publisher-loc><year>2004</year></citation></ref>
<ref id="b37-sensors-10-08198"><label>37.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Fischler</surname><given-names>MA</given-names></name><name><surname>Bolles</surname><given-names>RC</given-names></name></person-group><article-title>Random Sample Consensus: A Paradigm for Model Fitting with Applications to Image Analysis and Automated Cartography</article-title><source>Commun. ACM</source><year>1981</year><volume>24</volume><fpage>381</fpage><lpage>395</lpage><pub-id pub-id-type="doi">10.1145/358669.358692</pub-id></citation></ref>
<ref id="b38-sensors-10-08198"><label>38.</label><citation citation-type="book"><person-group person-group-type="author"><name><surname>Hartley</surname><given-names>R</given-names></name><name><surname>Zisserman</surname><given-names>A</given-names></name></person-group><source>Multiple View Geometry in Computer Vision</source><edition>2nd ed</edition><publisher-name>Cambridge University Press</publisher-name><publisher-loc>Cambridge, UK</publisher-loc><year>2003</year><fpage>655</fpage></citation></ref>
<ref id="b39-sensors-10-08198"><label>39.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Khoshelham</surname><given-names>K</given-names></name><name><surname>Gorte</surname><given-names>BG</given-names></name></person-group><article-title>Registering Point Clouds of Polyhedral Buildings to 2D Maps</article-title><conf-name>Proceedings of the 3rd ISPRS International Workshop 3D-ARCH 2009: “3D Virtual Reconstruction and Visualization of Complex Architectures”</conf-name><conf-loc>Trento, Italy</conf-loc><conf-date>25–28 February 2009</conf-date></citation></ref>
<ref id="b40-sensors-10-08198"><label>40.</label><citation citation-type="other"><person-group person-group-type="author"><name><surname>Vosselman</surname><given-names>G</given-names></name></person-group><article-title>On the Estimation of Planimetric Offsets in Laser Altimetry Data</article-title><source>Proceedings of ISPRS Symposium, “Photogrammetric Computer Vision”</source><publisher-loc>Graz, Austria</publisher-loc><day>9–13</day><month>September</month><year>2002</year><fpage>375</fpage><lpage>380</lpage></citation></ref></ref-list>
<sec sec-type="display-objects">
<title>Figures and Table</title>
<fig id="f1-sensors-10-08198" position="float">
<label>Figure 1.</label>
<caption>
<p>The AHN project. <bold>(a)</bold> the height model acquired during the first phase of the AHN project; <bold>(b)</bold> the acquisition plan of AHN-2.</p></caption>
<graphic xlink:href="sensors-10-08198f1.gif"/></fig>
<fig id="f2-sensors-10-08198" position="float">
<label>Figure 2.</label>
<caption>
<p>Overlapping strips. The overlap area between the blue strip and the red strip is represented as the yellow hatched area.</p></caption>
<graphic xlink:href="sensors-10-08198f2.gif"/></fig>
<fig id="f3-sensors-10-08198" position="float">
<label>Figure 3.</label>
<caption>
<p>Robust plane fitting to points on a roof segment. Points marked in red are inliers identified by RANSAC.</p></caption>
<graphic xlink:href="sensors-10-08198f3.gif"/></fig>
<fig id="f4-sensors-10-08198" position="float">
<label>Figure 4.</label>
<caption>
<p>AHN-2 laser altimetry dataset of Zeeland consisting of 15 strips.</p></caption>
<graphic xlink:href="sensors-10-08198f4.gif"/></fig>
<fig id="f5-sensors-10-08198" position="float">
<label>Figure 5.</label>
<caption>
<p>Performance of the segmentation method with different scale parameters.</p></caption>
<graphic xlink:href="sensors-10-08198f5.gif"/></fig>
<fig id="f6-sensors-10-08198" position="float">
<label>Figure 6.</label>
<caption>
<p>Roof segments created by using different scale parameters in the segmentation procedure.</p></caption>
<graphic xlink:href="sensors-10-08198f6.gif"/></fig>
<fig id="f7-sensors-10-08198" position="float">
<label>Figure 7.</label>
<caption>
<p>Mean of point-to-plane distances before and after the strip adjustment.</p></caption>
<graphic xlink:href="sensors-10-08198f7.gif"/></fig>
<fig id="f8-sensors-10-08198" position="float">
<label>Figure 8.</label>
<caption>
<p>Standard deviation of point-to-plane distances before and after the strip adjustment.</p></caption>
<graphic xlink:href="sensors-10-08198f8.gif"/></fig>
<fig id="f9-sensors-10-08198" position="float">
<label>Figure 9.</label>
<caption>
<p>Estimated x-offsets and their associated precision (vertical bars) compared to those estimated from line correspondences.</p></caption>
<graphic xlink:href="sensors-10-08198f9.gif"/></fig>
<fig id="f10-sensors-10-08198" position="float">
<label>Figure 10.</label>
<caption>
<p>Estimated y-offsets and their associated precision (vertical bars) compared to those estimated from line correspondences.</p></caption>
<graphic xlink:href="sensors-10-08198f10.gif"/></fig>
<fig id="f11-sensors-10-08198" position="float">
<label>Figure 11.</label>
<caption>
<p>Vertical offsets and their associated precision (vertical bars) estimated from point-to-plane distances.</p></caption>
<graphic xlink:href="sensors-10-08198f11.gif"/></fig>
<table-wrap id="t1-sensors-10-08198" position="float">
<label>Table 1.</label>
<caption>
<p>Specifications of the 13 strip overlaps.</p></caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="center" valign="middle" rowspan="3"><bold>Overlap ID</bold></th>
<th colspan="2" align="center" valign="middle"><bold>Strip</bold></th>
<th colspan="2" align="center" valign="middle"><bold>Number of points in the strip overlap</bold></th>
<th align="center" valign="middle" rowspan="3"><bold>Overlap Width (m)</bold></th></tr>
<tr>
<th align="center" valign="middle" colspan="4">
<hr/></th></tr>
<tr>
<th align="center" valign="middle"><bold>1st</bold></th>
<th align="center" valign="middle"><bold>2nd</bold></th>
<th align="center" valign="middle"><bold>1st</bold></th>
<th align="center" valign="middle"><bold>2nd</bold></th></tr></thead>
<tbody>
<tr>
<td align="center" valign="middle">o1</td>
<td align="center" valign="middle">s3</td>
<td align="center" valign="middle">s4</td>
<td align="center" valign="middle">21,731,922</td>
<td align="center" valign="middle">27,885,585</td>
<td align="center" valign="middle">200</td></tr>
<tr>
<td align="center" valign="middle">o2</td>
<td align="center" valign="middle">s4</td>
<td align="center" valign="middle">s5</td>
<td align="center" valign="middle">23,114,236</td>
<td align="center" valign="middle">28,984,667</td>
<td align="center" valign="middle">175</td></tr>
<tr>
<td align="center" valign="middle">o3</td>
<td align="center" valign="middle">s5</td>
<td align="center" valign="middle">s6</td>
<td align="center" valign="middle">28,984,667</td>
<td align="center" valign="middle">51,271,482</td>
<td align="center" valign="middle">240</td></tr>
<tr>
<td align="center" valign="middle">o4</td>
<td align="center" valign="middle">s7</td>
<td align="center" valign="middle">s8</td>
<td align="center" valign="middle">24,693,624</td>
<td align="center" valign="middle">24,953,061</td>
<td align="center" valign="middle">175</td></tr>
<tr>
<td align="center" valign="middle">o5</td>
<td align="center" valign="middle">s9</td>
<td align="center" valign="middle">s8</td>
<td align="center" valign="middle">24,534,357</td>
<td align="center" valign="middle">22,834,121</td>
<td align="center" valign="middle">175</td></tr>
<tr>
<td align="center" valign="middle">o6</td>
<td align="center" valign="middle">s9</td>
<td align="center" valign="middle">s10</td>
<td align="center" valign="middle">35,156,934</td>
<td align="center" valign="middle">22,427,804</td>
<td align="center" valign="middle">240</td></tr>
<tr>
<td align="center" valign="middle">o7</td>
<td align="center" valign="middle">s10</td>
<td align="center" valign="middle">s11</td>
<td align="center" valign="middle">10,303,345</td>
<td align="center" valign="middle">7,590,510</td>
<td align="center" valign="middle">200</td></tr>
<tr>
<td align="center" valign="middle">o8</td>
<td align="center" valign="middle">s12</td>
<td align="center" valign="middle">s13</td>
<td align="center" valign="middle">24,771,459</td>
<td align="center" valign="middle">19,671,036</td>
<td align="center" valign="middle">240</td></tr>
<tr>
<td align="center" valign="middle">o9</td>
<td align="center" valign="middle">s14</td>
<td align="center" valign="middle">s13</td>
<td align="center" valign="middle">3,267,309</td>
<td align="center" valign="middle">4,177,717</td>
<td align="center" valign="middle">525</td></tr>
<tr>
<td align="center" valign="middle">o10</td>
<td align="center" valign="middle">s15</td>
<td align="center" valign="middle">s13</td>
<td align="center" valign="middle">22,910,115</td>
<td align="center" valign="middle">14,855,334</td>
<td align="center" valign="middle">240</td></tr>
<tr>
<td align="center" valign="middle">o11</td>
<td align="center" valign="middle">s2</td>
<td align="center" valign="middle">s1</td>
<td align="center" valign="middle">4,618,326</td>
<td align="center" valign="middle">5,251,392</td>
<td align="center" valign="middle">485</td></tr>
<tr>
<td align="center" valign="middle">o12</td>
<td align="center" valign="middle">s2</td>
<td align="center" valign="middle">s3</td>
<td align="center" valign="middle">4,618,326</td>
<td align="center" valign="middle">6,164,108</td>
<td align="center" valign="middle">485</td></tr>
<tr>
<td align="center" valign="middle">o13</td>
<td align="center" valign="middle">s1</td>
<td align="center" valign="middle">s3</td>
<td align="center" valign="middle">65,247,718</td>
<td align="center" valign="middle">77,060,363</td>
<td align="center" valign="middle">320</td></tr></tbody></table></table-wrap></sec></back></article>
