<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "http://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="methods-article" dtd-version="1.2" xml:lang="en">
    <front>
        <journal-meta>
            <journal-id journal-id-type="pmc">F1000Research</journal-id>
            <journal-title-group>
                <journal-title>F1000Research</journal-title>
            </journal-title-group>
            <issn pub-type="epub">2046-1402</issn>
            <publisher>
                <publisher-name>F1000 Research Limited</publisher-name>
                <publisher-loc>London, UK</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="doi">10.12688/f1000research.151861.1</article-id>
            <article-categories>
                <subj-group subj-group-type="heading">
                    <subject>Method Article</subject>
                </subj-group>
                <subj-group>
                    <subject>Articles</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>Extracting ridge and valley lines in mountainous areas from airborne lidar data by utilizing line feature strength</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 1; peer review: 2 not approved]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>You</surname>
                        <given-names>Rey-Jer</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>Lee</surname>
                        <given-names>Chao-Liang</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <uri content-type="orcid">https://orcid.org/0009-0001-3169-0441</uri>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>Department of Geomatics, National Cheng-Kung University, Tainan, 70101, Taiwan</aff>
                <aff id="a2">
                    <label>2</label>Department of Geomatics, National Cheng-Kung University, Tainan, 70101, Taiwan</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:abecare@gmail.com">abecare@gmail.com</email>
                </corresp>
                <fn fn-type="conflict">
                    <p>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>5</day>
                <month>9</month>
                <year>2024</year>
            </pub-date>
            <pub-date pub-type="collection">
                <year>2024</year>
            </pub-date>
            <volume>13</volume>
            <elocation-id>1011</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>13</day>
                    <month>8</month>
                    <year>2024</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2024 You RJ and Lee CL</copyright-statement>
                <copyright-year>2024</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <self-uri content-type="pdf" xlink:href="https://f1000research.com/articles/13-1011/pdf"/>
            <abstract>
                <sec>
                    <title>Background</title>
                    <p>Digital elevation models (DEMs) are important in many fields, such as geomatics and water conservation in mountainous areas. Geomorphic feature lines are necessary for topography interpolation and computation from DEMs.</p>
                </sec>
                <sec>
                    <title>Methods</title>
                    <p>Instead of a parameter space, we propose a novel automatic extraction of geomorphic feature lines in the feature space from discrete airborne light detection and ranging (LiDAR) data by the tensor voting method (TVM), which was originally developed for image data. A tensor field for discrete airborne LiDAR points was first established, and then, utilizing the TVM, a new geometric feature metric of data, the line feature strength, was captured. A practical line-growing method based on the local maxima line feature strength is proposed in this study.</p>
                </sec>
                <sec>
                    <title>Results</title>
                    <p>Compared with general line growing, which is based on a certain threshold, our line growing method is quite effective, particularly for the extraction of primary and minor ridge and valley lines in mountainous areas.</p>
                </sec>
                <sec>
                    <title>Conclusions</title>
                    <p>The method presented in this paper is fast and automated, and can furnish operators with a wealth of detailed information about minor line features. This enables the extraction of ridge and valley lines that are tailored to specific requirements. Undoubtedly, the method developed here can be generalized to a large amount of LiDAR data.</p>
                </sec>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>LiDAR</kwd>
                <kwd>feature extraction</kwd>
                <kwd>ridge and valley.</kwd>
            </kwd-group>
            <funding-group>
                <award-group id="fund-1" xlink:href="http://dx.doi.org/10.13039/501100020363">
                    <funding-source>Institute for Information Industry, Ministry of Science and Technology, Taiwan</funding-source>
                    <award-id>MOST105-2119-M-006-034</award-id>
                </award-group>
                <funding-statement>This work was funded by Institute for Information Industry, Ministry of Science and Technology, Taiwan- MOST 105-2119-M-006-034 </funding-statement>
                <funding-statement>
                    <italic>The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.</italic>
                </funding-statement>
            </funding-group>
        </article-meta>
    </front>
    <body>
        <sec id="sec5" sec-type="intro">
            <title>Introduction</title>
            <p>Light detection and ranging (LiDAR) technology has gained increasing prominence because of its capacity to rapidly generate voluminous amounts of three-dimensional (3D) point clouds, enabling expedient characterization of Earth&#x2019;s topography.</p>
            <p>LiDAR can quickly provide a large amount of terrain data that is useful for building reconstruction, extraction of road paths, construction of topography, and terrain change monitoring etc.
                <sup>
                    <xref ref-type="bibr" rid="ref1">1</xref>
                </sup>
                <sup>&#x2013;</sup>
                <sup>
                    <xref ref-type="bibr" rid="ref7">7</xref>
                </sup> LiDAR is also employed for environmental protection, soil and water conservation, and the hydrological structure of mountainous areas, which are important issues.
                <sup>
                    <xref ref-type="bibr" rid="ref8">8</xref>
                </sup>
                <sup>&#x2013;</sup>
                <sup>
                    <xref ref-type="bibr" rid="ref10">10</xref>
                </sup> Furthermore, LiDAR is a very useful tool for monitoring forest growth and forest area changes, especially for estimating vegetation height, canopy cover, and tree species in mountainous areas.
                <sup>
                    <xref ref-type="bibr" rid="ref11">11</xref>
                </sup>
                <sup>&#x2013;</sup>
                <sup>
                    <xref ref-type="bibr" rid="ref13">13</xref>
                </sup>
            </p>
            <p>Compared with photogrammetric data, LiDAR data offer a more straightforward approach for understanding changes in 3D topography. However, the irregular distribution of LiDAR point clouds can pose a challenge, particularly when shaping complex terrain within topological data. This paper introduces a method for extracting ridge and valley lines from low-density point clouds in mountainous regions.</p>
            <p>Edge detection is an established technique in computer vision. Various algorithms, such as Sobel, Prewitt, and Laplacian algorithms, have been developed to identify line features.
                <sup>
                    <xref ref-type="bibr" rid="ref14">14</xref>
                </sup> Image data are stored in pixel format, and moving masks can easily navigate this regular grid to extract line features. Conversely, the data storage format for irregularly discrete LiDAR data consists of the point coordinates. If image extraction techniques are employed, the point coordinates must be interpolated into a pixel format, which can influence the accuracy depending on the interpolation method used.</p>
            <p>Scholars have proposed various methods for extracting line features from LiDAR data. Zhao and You
                <sup>
                    <xref ref-type="bibr" rid="ref4">4</xref>
                </sup> focused on extracting road networks. Their approach entails the removal of points associated with buildings and trees by applying the elevation criteria. Subsequently, they employed the intensity data and variance between the tangent vectors to define the line segments. Given that roads possess a certain non-negligible width, a sufficient number of point clouds are usually present on road surfaces to enable line segment extraction. To deal with narrower features, such as power lines, McLaughlin
                <sup>
                    <xref ref-type="bibr" rid="ref15">15</xref>
                </sup> proposed a method that uses covariance to calculate the eigenvalues. These eigenvalues can be employed to categorize the point clouds into three groups: vegetation, surfaces, and power lines. Cable-specific formulas are applied to the point clouds allocated to the power line category to yield complete power-line representations. Guan
                <sup>
                    <xref ref-type="bibr" rid="ref16">16</xref>
                </sup> used ground-based LiDAR scanning to obtain point cloud data of street views and extracted individual power lines using Hough transformation and Euclidean distance clustering.</p>
            <p>Line features that do not correspond to existing lines typically exist at points of change, such as turns and junction areas. Both sharp and gradual turns affect the position of the final extracted line segment. Bailly et al.
                <sup>
                    <xref ref-type="bibr" rid="ref17">17</xref>
                </sup> used wavelet transformation and a flooding algorithm to identify the ditch lines in artificial drainage networks. In their study on mountainous settings, Chang et al.
                <sup>
                    <xref ref-type="bibr" rid="ref18">18</xref>
                </sup> proposed a profile recognition and polygon-breaking algorithm (PPA) that performs target recognition, target connection, segment verification, and line smoothing. In the PPA approach, elevation grids from digital terrain models (DTMs) were used, and moving masks were employed to extend the ridge and valley lines. G&#x00fc;lgen and G&#x00f6;kg&#x00f6;z
                <sup>
                    <xref ref-type="bibr" rid="ref19">19</xref>
                </sup> modified PPA to reduce the computational time required for the DTM generation process. However, PPA is easily influenced by noise, which may lead to redundant lines and non-matched results. A pre-processing procedure is necessary to obtain reliable valley and ridge lines.</p>
            <p>A new type of data, termed feature strength, was introduced to aid feature extraction. Medioni et al.
                <sup>
                    <xref ref-type="bibr" rid="ref20">20</xref>
                </sup> applied the tensor voting method (TVM) to image data to obtain the eigenvalues and eigenvectors. This method enables the classification of image pixels into various features based on their strengths. TVM has also been demonstrated to be applicable to point-cloud data. You and Lin
                <sup>
                    <xref ref-type="bibr" rid="ref1">1</xref>
                </sup> utilized feature strength to extract surfaces and lines from data in urban settings. Furthermore, in the context of urban regions, feature strength data can serve as raw data for calibrating biases between LiDAR strips during the preprocessing stage.
                <sup>
                    <xref ref-type="bibr" rid="ref21">21</xref>
                </sup> In urban environments, where buildings and roofs exhibit regular patterns, point clouds on surfaces are readily distinguishable from others owing to their high surface feature strength. Lines can be identified at the intersections of two adjacent surfaces. However, because of the irregular nature of mountainous regions, this approach may result in more fragmented surfaces, making it challenging to intersect ridge and valley lines. The aim of this study is to analyze and discuss the feature strength of point clouds in mountainous regions, particularly the line feature strength extracted by TVM.</p>
        </sec>
        <sec id="sec6" sec-type="methods">
            <title>Methods</title>
            <sec id="sec7">
                <title>Geometric feature strength</title>
                <p>TVM encompasses three stages: tensor representation, tensor communication, and tensor decomposition/encoding.
                    <sup>
                        <xref ref-type="bibr" rid="ref20">20</xref>
                    </sup>
                    <sup>,</sup>
                    <sup>
                        <xref ref-type="bibr" rid="ref22">22</xref>
                    </sup> First, a tensor field was established by setting up a disk tensor for each LiDAR point, as proposed by You and Lin,
                    <sup>
                        <xref ref-type="bibr" rid="ref1">1</xref>
                    </sup> and the geometric character of each LiDAR point was represented by a second symmetric tensor. Using tensor communication, each point collects the tensors of neighboring LiDAR points to form its final tensor. Consequently, each point has a strong geometric relationship with its neighboring points based on the final tensor, which is helpful for the extraction of ridge and valley lines in mountainous areas. After tensor communication, the final tensor of each point was decomposed into surface features, line features, and noise point features by tensor encoding.
                    <sup>
                        <xref ref-type="bibr" rid="ref20">20</xref>
                    </sup> You and Lin
                    <sup>
                        <xref ref-type="bibr" rid="ref1">1</xref>
                    </sup>
                    <sup>,</sup>
                    <sup>
                        <xref ref-type="bibr" rid="ref2">2</xref>
                    </sup> used a normal vector field to obtain the surface feature strengths using the TVM and applied the region-growing method to extract surface features from LiDAR point clouds for urban regions. For our purpose, the line feature strength (denoted as 
                    <italic toggle="yes">C</italic> here) is more suitable for extracting valley and river lines in mountainous regions than the other types of feature strength. This aspect is elaborated in the subsequent section.</p>
            </sec>
            <sec id="sec8">
                <title>Line feature strength</title>
                <p>
                    <italic toggle="yes">C</italic> data can be obtained using the TVM. This section describes the characteristics of 
                    <italic toggle="yes">C</italic> data. 
                    <xref ref-type="fig" rid="f1">Figure 1</xref> shows the same mountainous region from various perspectives and data modes. In 
                    <xref ref-type="fig" rid="f1">Figure 1(a)</xref>, the ridge and valley regions appear in the 2.5D view, with an elevation range of approximately 1,400 meters. 
                    <xref ref-type="fig" rid="f1">Figure 1(b)</xref> shows the elevation data from a 2D view. 
                    <xref ref-type="fig" rid="f1">Figure 1(c)</xref> presents the 
                    <italic toggle="yes">C </italic>data from a 2D view.</p>
                <fig fig-type="figure" id="f1" orientation="portrait" position="float">
                    <label>Figure 1. </label>
                    <caption>
                        <title>LiDAR data for a river and valley region, displayed in various views and data modes.</title>
                        <p>NOTE: (a) Point clouds illustrated in 2.5D view; (b) Elevation data illustrated in 2D view; (c) 
                            <italic toggle="yes">C </italic>data illustrated in 2D view. Own work.</p>
                    </caption>
                    <graphic id="gr1" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/166549/112563b0-442d-44f2-ba21-368e5ffed671_figure1.gif"/>
                </fig>
                <p>To analyze the characteristics of the 
                    <italic toggle="yes">C</italic> data in relation to variations in elevation, this study established a section line. In 
                    <xref ref-type="fig" rid="f2">Figure 2</xref>, the red line represents the elevation data and the blue line represents 
                    <italic toggle="yes">C</italic> data from the section lines shown in 
                    <xref ref-type="fig" rid="f1">Figure 1(b)</xref> and 
                    <xref ref-type="fig" rid="f1">(c)</xref>. As depicted in 
                    <xref ref-type="fig" rid="f2">Figure 2</xref>, 
                    <italic toggle="yes">C</italic> was higher in regions with large elevation gradients, and its magnitude was influenced by the extent of the elevation gradient. In areas with smaller elevation gradients, 
                    <italic toggle="yes">C</italic> was relatively stable. Hence, establishing a single threshold for identifying all points in the valley versus ridge regions is infeasible. In 
                    <xref ref-type="fig" rid="f2">Figure 2</xref>, points near the ridge and valley regions display local maxima in the 
                    <italic toggle="yes">C</italic> data curves, confirming that 
                    <italic toggle="yes">C</italic> data can effectively assist in the identification of nodes of line features.</p>
                <fig fig-type="figure" id="f2" orientation="portrait" position="float">
                    <label>Figure 2. </label>
                    <caption>
                        <title>Section lines corresponding to C data in 
                            <xref ref-type="fig" rid="f1">Figure 1</xref>.</title>
                        <p>NOTE: Red line, elevation data; blue line, line feature strength data in section line of 
                            <xref ref-type="fig" rid="f1">Figure 1(b)</xref> and 
                            <xref ref-type="fig" rid="f1">(c)</xref>. Own work.</p>
                    </caption>
                    <graphic id="gr2" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/166549/112563b0-442d-44f2-ba21-368e5ffed671_figure2.gif"/>
                </fig>
            </sec>
            <sec id="sec9">
                <title>Tangent vector of point clouds</title>
                <p>The eigenvectors for LiDAR point clouds can be derived using the TVM. Each point cloud possessed three associated eigenvectors, each with a distinct interpretation. For points located on a surface, the first eigenvector is the vector that is normal to the surface. Conversely, for points situated on a line, the third eigenvector is the tangent vector along the direction of the line, as shown by Medioni et al.
                    <sup>
                        <xref ref-type="bibr" rid="ref20">20</xref>
                    </sup> and You and Lin.
                    <sup>
                        <xref ref-type="bibr" rid="ref1">1</xref>
                    </sup>
                    <sup>,</sup>
                    <sup>
                        <xref ref-type="bibr" rid="ref2">2</xref>
                    </sup> Given that this study focuses on the extraction of ridge and valley lines, the tangent vector
                    <italic toggle="yes"> v</italic> for each point is considered. This vector is derived using the TVM and is crucial for eliminating extraneous point clouds.</p>
            </sec>
            <sec id="sec10">
                <title>Line growth</title>
                <p>Drawing inspiration from the region-growing method, this study established line growth criteria by choosing seed points and setting item thresholds. According to the next section, points located on the ridge or valley regions have higher 
                    <italic toggle="yes">C</italic> values than their surrounding points. Hence, points with local maxima 
                    <italic toggle="yes">C</italic> values serve as seeds for initiating line growth. Second, the 
                    <italic toggle="yes">v</italic> vectors of adjacent points located in the same valley or ridge line are similar. These two considerations guide the line-growth process, the specifics of which are explained in the following section.</p>
            </sec>
            <sec id="sec11">
                <title>Choosing seeds with local maxima of line feature strength</title>
                <p>This study establishes that such local maxima are directional in nature to provide a detailed explanation of how they are identified in 3D point cloud data. Vector 
                    <bold>
                        <italic toggle="yes">v</italic>
                    </bold>, derived from the TVM, is a critical factor. Points (
                    <italic toggle="yes">i</italic> = 1, 2, &#x2026;, 
                    <italic toggle="yes">k</italic>) considered centers within a specified search radius are divided into right (
                    <italic toggle="yes">a</italic> = 1, &#x2026;, 
                    <italic toggle="yes">m</italic>) and left (
                    <italic toggle="yes">b</italic> = 1, &#x2026;, 
                    <italic toggle="yes">n</italic>) subsets based on 
                    <bold>
                        <italic toggle="yes">v</italic>
                    </bold>, which serves as a divide. A center point cloud is deemed to be a local maxima in terms of 
                    <italic toggle="yes">C</italic> when the average 
                    <italic toggle="yes">C</italic> values on the two sides are lower than the 
                    <italic toggle="yes">C</italic> value of the center point. This is formalized in the following equations:
                    <disp-formula id="e1">
                        <mml:math display="block">
                            <mml:mtext>If</mml:mtext>
                            <mml:mspace width="0.25em"/>
                            <mml:mrow>
                                <mml:mo stretchy="true">(</mml:mo>
                                <mml:mfrac>
                                    <mml:mrow>
                                        <mml:msubsup>
                                            <mml:mo>&#x2211;</mml:mo>
                                            <mml:mrow>
                                                <mml:mi>a</mml:mi>
                                                <mml:mo>=</mml:mo>
                                                <mml:mn>1</mml:mn>
                                            </mml:mrow>
                                            <mml:mi>m</mml:mi>
                                        </mml:msubsup>
                                        <mml:mrow>
                                            <mml:mo stretchy="true">(</mml:mo>
                                            <mml:msub>
                                                <mml:mi>C</mml:mi>
                                                <mml:mi>a</mml:mi>
                                            </mml:msub>
                                            <mml:mo stretchy="true">)</mml:mo>
                                        </mml:mrow>
                                    </mml:mrow>
                                    <mml:mi mathvariant="normal">m</mml:mi>
                                </mml:mfrac>
                                <mml:mo>&#x2212;</mml:mo>
                                <mml:msub>
                                    <mml:mi>C</mml:mi>
                                    <mml:mi>i</mml:mi>
                                </mml:msub>
                                <mml:mo stretchy="true">)</mml:mo>
                            </mml:mrow>
                            <mml:mo>&lt;</mml:mo>
                            <mml:mn>0</mml:mn>
                            <mml:mspace width="0.25em"/>
                            <mml:mtext>and</mml:mtext>
                            <mml:mspace width="0.25em"/>
                            <mml:mrow>
                                <mml:mo stretchy="true">(</mml:mo>
                                <mml:mfrac>
                                    <mml:mrow>
                                        <mml:msubsup>
                                            <mml:mo>&#x2211;</mml:mo>
                                            <mml:mrow>
                                                <mml:mi>b</mml:mi>
                                                <mml:mo>=</mml:mo>
                                                <mml:mn>1</mml:mn>
                                            </mml:mrow>
                                            <mml:mi>n</mml:mi>
                                        </mml:msubsup>
                                        <mml:mrow>
                                            <mml:mo stretchy="true">(</mml:mo>
                                            <mml:msub>
                                                <mml:mi>C</mml:mi>
                                                <mml:mi>b</mml:mi>
                                            </mml:msub>
                                            <mml:mo stretchy="true">)</mml:mo>
                                        </mml:mrow>
                                    </mml:mrow>
                                    <mml:mi mathvariant="normal">n</mml:mi>
                                </mml:mfrac>
                                <mml:mo>&#x2212;</mml:mo>
                                <mml:msub>
                                    <mml:mi>C</mml:mi>
                                    <mml:mi>i</mml:mi>
                                </mml:msub>
                                <mml:mo stretchy="true">)</mml:mo>
                            </mml:mrow>
                            <mml:mo>&lt;</mml:mo>
                            <mml:mn>0</mml:mn>
                            <mml:mspace width="0.25em"/>
                        </mml:math>
                        <label>(1)</label>
                    </disp-formula>
                </p>
                <p>Subscript 
                    <italic toggle="yes">i</italic> indicates point 
                    <italic toggle="yes">i</italic> located on a line. 
                    <inline-formula>
                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>C</mml:mi>
                                <mml:mi>a</mml:mi>
                            </mml:msub>
                        </mml:math>
                    </inline-formula> represents the 
                    <italic toggle="yes">C</italic> value in point cloud 
                    <italic toggle="yes">a</italic> on the right-hand side of 
                    <italic toggle="yes">v</italic> (
                    <italic toggle="yes">a</italic> = 1, &#x2026;, 
                    <italic toggle="yes">m</italic>). 
                    <inline-formula>
                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>C</mml:mi>
                                <mml:mi>b</mml:mi>
                            </mml:msub>
                        </mml:math>
                    </inline-formula> represents the 
                    <italic toggle="yes">C</italic> value in point cloud 
                    <italic toggle="yes">b</italic> on the left-hand side of 
                    <italic toggle="yes">v</italic> (
                    <italic toggle="yes">b</italic> = 1, &#x2026;, 
                    <italic toggle="yes">n</italic>).</p>
                <p>As depicted in 
                    <xref ref-type="fig" rid="f3">Figure 3</xref>, points within the search radius are divided into right (R1, R2, R3, and R4) and left (L1 and L2) subsets based on 
                    <italic toggle="yes">v</italic> of 
                    <italic toggle="yes">P</italic>1. Point 
                    <italic toggle="yes">P</italic>1 is classified as the local maxima of 
                    <italic toggle="yes">C</italic> when it satisfies 
                    <xref ref-type="disp-formula" rid="e1">Equation (1)</xref>. This criterion was employed to eliminate redundant points in the line growth process. Points satisfying 
                    <xref ref-type="disp-formula" rid="e1">Eq. (1)</xref> serve as candidate seeds for line growth.</p>
                <fig fig-type="figure" id="f3" orientation="portrait" position="float">
                    <label>Figure 3. </label>
                    <caption>
                        <title>Defining a local maxima in 3D space.</title>
                        <p>NOTE: points within the search radius are divided into right (R1, R2, R3, and R4) and left (L1 and L2) subsets based on v of P1. Point P1 is classified as the local maxima of 
                            <italic toggle="yes">C</italic> when it satisfies 
                            <xref ref-type="disp-formula" rid="e1">Equation (1)</xref>. Own work.</p>
                    </caption>
                    <graphic id="gr3" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/166549/112563b0-442d-44f2-ba21-368e5ffed671_figure3.gif"/>
                </fig>
                <p>When employing a large search radius, numerous point clouds not located on the line were included in the calculations. Conversely, when the search radius is small, many point clouds near the line segment are excluded, leading to incomplete line segments, particularly in the case of low-density point clouds. In this study, the radius used to identify point clouds with local maxima was consistent with the radius employed in TVM applications.</p>
            </sec>
            <sec id="sec12">
                <title>Setting an angle threshold between two tangent vectors</title>
                <p>A threshold of 
                    <italic toggle="yes">C</italic> value may be chosen to determine all candidate seeds whose 
                    <italic toggle="yes">C</italic> values are larger than that threshold, as in the conventional growing method. The result would lead to the extraction of the primary ridge and valley lines only, but might filter out other minor lines. Different from the conventional method, candidate seeds are identified by seeking local 
                    <italic toggle="yes">C</italic> maxima for the line-growing in this article. Using this line-growing method, more details of the ridge and valley lines can be obtained. Points with higher 
                    <italic toggle="yes">C</italic> values are more likely to be located on lines and are therefore prioritized for line growth. According to empirical observations, neighboring points on a line should have similar tangent vectors. The threshold angle between the two 
                    <italic toggle="yes">v</italic> vectors can then be defined.</p>
                <p>To meet the criteria of the angle threshold, the five points with the largest 
                    <italic toggle="yes">C</italic> value are regarded as the center of the ball in the TV&#x2019;s searching radius, and the tangent vectors of points that meet the local maxima 
                    <italic toggle="yes">C</italic> value within the range are the calculated angles between the center points. The average angle value of the five groups was used as the basic threshold (&#x03c9;), and three times the average value (3&#x03c9;) was used as the threshold value in this study. An excessively large threshold can introduce inaccuracies by leading to the inclusion of numerous point clouds that are not actually part of the line segment, skewing the final calculations. Conversely, a too-small threshold can lead to the omission of relevant clouds and fragmentation of lines; the procedure cuts off branch lines to multiple single lines.</p>
                <p>To preserve the detailed line features, the proposed approach adopts a moving mask algorithm from computer vision and employs an overlapping mechanism. The size of the moving ball matches that of the search ball used in the TVM, and its moving distance equals the radius of the ball. Points that satisfy both the angle threshold and 
                    <xref ref-type="disp-formula" rid="e1">Equation (1)</xref> are considered, with their 
                    <italic toggle="yes">C</italic> values serving as weights because a higher 
                    <italic toggle="yes">C</italic> value implies a higher likelihood that the point is part of a line. The node of a line and its associated tangent vector were then calculated using the following equations:
                    <disp-formula id="e2">
                        <mml:math display="block">
                            <mml:mrow>
                                <mml:mo stretchy="true">(</mml:mo>
                                <mml:msub>
                                    <mml:mi>V</mml:mi>
                                    <mml:mi>i</mml:mi>
                                </mml:msub>
                                <mml:mo stretchy="true">)</mml:mo>
                            </mml:mrow>
                            <mml:mo>=</mml:mo>
                            <mml:mfrac>
                                <mml:mrow>
                                    <mml:mo>&#x2211;</mml:mo>
                                    <mml:mrow>
                                        <mml:mo stretchy="true">(</mml:mo>
                                        <mml:msub>
                                            <mml:mi>C</mml:mi>
                                            <mml:mi>j</mml:mi>
                                        </mml:msub>
                                        <mml:mo>&#x2219;</mml:mo>
                                        <mml:msub>
                                            <mml:mi>V</mml:mi>
                                            <mml:mi>j</mml:mi>
                                        </mml:msub>
                                        <mml:mo stretchy="true">)</mml:mo>
                                    </mml:mrow>
                                </mml:mrow>
                                <mml:mrow>
                                    <mml:mo>&#x2211;</mml:mo>
                                    <mml:msub>
                                        <mml:mi>C</mml:mi>
                                        <mml:mi>j</mml:mi>
                                    </mml:msub>
                                </mml:mrow>
                            </mml:mfrac>
                            <mml:mspace width="0.25em"/>
                            <mml:mtext>when</mml:mtext>
                            <mml:mspace width="0.25em"/>
                            <mml:mi>i</mml:mi>
                            <mml:mo>=</mml:mo>
                            <mml:mn>1</mml:mn>
                            <mml:mo>&#x2026;</mml:mo>
                            <mml:mo>.</mml:mo>
                            <mml:mi>n</mml:mi>
                            <mml:mo>,</mml:mo>
                            <mml:mi>j</mml:mi>
                            <mml:mo>=</mml:mo>
                            <mml:mn>1</mml:mn>
                            <mml:mo>&#x2026;</mml:mo>
                            <mml:mo>.</mml:mo>
                            <mml:mi>m</mml:mi>
                        </mml:math>
                        <label>(2)</label>
                    </disp-formula>
                    <disp-formula id="e3">
                        <mml:math display="block">
                            <mml:msub>
                                <mml:mrow>
                                    <mml:mo stretchy="true">(</mml:mo>
                                    <mml:mtable>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mi>x</mml:mi>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mi>y</mml:mi>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mi>z</mml:mi>
                                            </mml:mtd>
                                        </mml:mtr>
                                    </mml:mtable>
                                    <mml:mo stretchy="true">)</mml:mo>
                                </mml:mrow>
                                <mml:mi>i</mml:mi>
                            </mml:msub>
                            <mml:mo>=</mml:mo>
                            <mml:mfrac>
                                <mml:mrow>
                                    <mml:mo>&#x2211;</mml:mo>
                                    <mml:mrow>
                                        <mml:mo stretchy="true">(</mml:mo>
                                        <mml:msub>
                                            <mml:mi>C</mml:mi>
                                            <mml:mi>j</mml:mi>
                                        </mml:msub>
                                        <mml:mo>&#x2219;</mml:mo>
                                        <mml:msub>
                                            <mml:mrow>
                                                <mml:mo stretchy="true">(</mml:mo>
                                                <mml:mtable>
                                                    <mml:mtr>
                                                        <mml:mtd>
                                                            <mml:mi>x</mml:mi>
                                                        </mml:mtd>
                                                    </mml:mtr>
                                                    <mml:mtr>
                                                        <mml:mtd>
                                                            <mml:mi>y</mml:mi>
                                                        </mml:mtd>
                                                    </mml:mtr>
                                                    <mml:mtr>
                                                        <mml:mtd>
                                                            <mml:mi>z</mml:mi>
                                                        </mml:mtd>
                                                    </mml:mtr>
                                                </mml:mtable>
                                                <mml:mo stretchy="true">)</mml:mo>
                                            </mml:mrow>
                                            <mml:mi>j</mml:mi>
                                        </mml:msub>
                                        <mml:mo stretchy="true">)</mml:mo>
                                    </mml:mrow>
                                </mml:mrow>
                                <mml:mrow>
                                    <mml:mo>&#x2211;</mml:mo>
                                    <mml:msub>
                                        <mml:mi>C</mml:mi>
                                        <mml:mi>j</mml:mi>
                                    </mml:msub>
                                </mml:mrow>
                            </mml:mfrac>
                            <mml:mspace width="0.25em"/>
                            <mml:mtext>when</mml:mtext>
                            <mml:mspace width="0.25em"/>
                            <mml:mi>i</mml:mi>
                            <mml:mo>=</mml:mo>
                            <mml:mn>1</mml:mn>
                            <mml:mo>&#x2026;</mml:mo>
                            <mml:mo>.</mml:mo>
                            <mml:mi>n</mml:mi>
                            <mml:mo>,</mml:mo>
                            <mml:mi>j</mml:mi>
                            <mml:mo>=</mml:mo>
                            <mml:mn>1</mml:mn>
                            <mml:mo>&#x2026;</mml:mo>
                            <mml:mo>.</mml:mo>
                            <mml:mi>m</mml:mi>
                        </mml:math>
                        <label>(3)</label>
                    </disp-formula>
                </p>
                <p>
                    <italic toggle="yes">i</italic>: node 
                    <italic toggle="yes">i</italic> of a line. 
                    <italic toggle="yes">j</italic>: point 
                    <italic toggle="yes">j</italic> within the search ball.</p>
                <p>
                    <italic toggle="yes">n</italic> the number of nodes in a line. 
                    <italic toggle="yes">m</italic>: number of points within the search ball.</p>
                <p>
                    <inline-formula>
                        <mml:math display="inline">
                            <mml:msubsup>
                                <mml:mrow>
                                    <mml:mo stretchy="true">(</mml:mo>
                                    <mml:mi>x</mml:mi>
                                    <mml:mspace width="0.5em"/>
                                    <mml:mi>y</mml:mi>
                                    <mml:mspace width="0.5em"/>
                                    <mml:mi>z</mml:mi>
                                    <mml:mo stretchy="true">)</mml:mo>
                                </mml:mrow>
                                <mml:mi>i</mml:mi>
                                <mml:mi>T</mml:mi>
                            </mml:msubsup>
                        </mml:math>
                    </inline-formula> and tangent vector
                    <inline-formula>
                        <mml:math display="inline">
                            <mml:mspace width="0.25em"/>
                            <mml:mrow>
                                <mml:mo stretchy="true">(</mml:mo>
                                <mml:msub>
                                    <mml:mi>V</mml:mi>
                                    <mml:mi>i</mml:mi>
                                </mml:msub>
                                <mml:mo stretchy="true">)</mml:mo>
                            </mml:mrow>
                        </mml:math>
                    </inline-formula>. The subsequent node of the line was determined using the following equation:
                    <disp-formula id="e4">
                        <mml:math display="block">
                            <mml:msub>
                                <mml:mrow>
                                    <mml:mo stretchy="true">(</mml:mo>
                                    <mml:mtable>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mi>x</mml:mi>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mi>y</mml:mi>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mi>z</mml:mi>
                                            </mml:mtd>
                                        </mml:mtr>
                                    </mml:mtable>
                                    <mml:mo stretchy="true">)</mml:mo>
                                </mml:mrow>
                                <mml:mrow>
                                    <mml:mi>i</mml:mi>
                                    <mml:mo>+</mml:mo>
                                    <mml:mn>1</mml:mn>
                                </mml:mrow>
                            </mml:msub>
                            <mml:mo>=</mml:mo>
                            <mml:msub>
                                <mml:mrow>
                                    <mml:mo stretchy="true">(</mml:mo>
                                    <mml:mtable>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mi>x</mml:mi>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mi>y</mml:mi>
                                            </mml:mtd>
                                        </mml:mtr>
                                        <mml:mtr>
                                            <mml:mtd>
                                                <mml:mi>z</mml:mi>
                                            </mml:mtd>
                                        </mml:mtr>
                                    </mml:mtable>
                                    <mml:mo stretchy="true">)</mml:mo>
                                </mml:mrow>
                                <mml:mi>i</mml:mi>
                            </mml:msub>
                            <mml:mo>+</mml:mo>
                            <mml:mtext>Radius</mml:mtext>
                            <mml:mo>&#x2219;</mml:mo>
                            <mml:mrow>
                                <mml:mo stretchy="true">(</mml:mo>
                                <mml:mfrac>
                                    <mml:msub>
                                        <mml:mi>V</mml:mi>
                                        <mml:mi>i</mml:mi>
                                    </mml:msub>
                                    <mml:mrow>
                                        <mml:mo>|</mml:mo>
                                        <mml:msub>
                                            <mml:mi>V</mml:mi>
                                            <mml:mi>i</mml:mi>
                                        </mml:msub>
                                        <mml:mo>|</mml:mo>
                                    </mml:mrow>
                                </mml:mfrac>
                                <mml:mo stretchy="true">)</mml:mo>
                            </mml:mrow>
                        </mml:math>
                        <label>(4)</label>
                    </disp-formula>
                </p>
                <p>In line with the techniques used in computer vision for line extraction, overlapping regions were maintained between the moving masks. In this study, approximately half of the search balls were designed to overlap adjacent balls.</p>
                <p>P0 [
                    <xref ref-type="fig" rid="f4">Figure 4(a)</xref>] was selected as the initial seed. Points that satisfy both 
                    <xref ref-type="disp-formula" rid="e1">Equation (1)</xref> and the angle threshold within searching ball O1 are evaluated using 
                    <xref ref-type="disp-formula" rid="e2">Equations (2)</xref> and 
                    <xref ref-type="disp-formula" rid="e3">(3)</xref>, which yield new values for P1 and v1, respectively. Search ball O2 is generated through 
                    <xref ref-type="disp-formula" rid="e4">Equation (4)</xref>, and the procedure is repeated to obtain P2, v2, and so on until no points within the search ball meet the criteria. At this juncture, P1, P2, and P3 become the nodes of the line, as illustrated in 
                    <xref ref-type="fig" rid="f4">Figure 4(b)</xref>, and new seeds are selected for the growth of additional lines until all the points satisfying 
                    <xref ref-type="disp-formula" rid="e1">Equation (1)</xref> are used.</p>
                <fig fig-type="figure" id="f4" orientation="portrait" position="float">
                    <label>Figure 4. </label>
                    <caption>
                        <title>Line-growing procedure.</title>
                        <p>NOTE: (a) Move the searching ball to grow nodes and vectors on the basis of multiple criteria. (b) Connect the nodes to obtain a complete line. Own work.</p>
                    </caption>
                    <graphic id="gr4" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/166549/112563b0-442d-44f2-ba21-368e5ffed671_figure4.gif"/>
                </fig>
            </sec>
            <sec id="sec13">
                <title>Theoretical accuracy and interpolated accuracy</title>
                <p>Node-point coordinates were calculated by weighting them in accordance with their 
                    <italic toggle="yes">C</italic> values. 
                    <xref ref-type="disp-formula" rid="e4">Equation (4)</xref> describes the method used to determine the node coordinates. To ascertain the theoretical accuracy, error propagation calculations were conducted for each point 
                    <italic toggle="yes">i</italic>, as outlined in 
                    <xref ref-type="disp-formula" rid="e5">Equation (5)</xref>. For simplicity, any correlations among 
                    <italic toggle="yes">x</italic>
                    <sub>i</sub>, 
                    <italic toggle="yes">y</italic>
                    <sub>i</sub>, and 
                    <italic toggle="yes">z</italic>
                    <sub>i</sub> were disregarded.
                    <disp-formula id="e5">
                        <mml:math display="block">
                            <mml:msubsup>
                                <mml:mi>&#x03c3;</mml:mi>
                                <mml:mi>x</mml:mi>
                                <mml:mn>2</mml:mn>
                            </mml:msubsup>
                            <mml:mo>=</mml:mo>
                            <mml:mo>&#x2211;</mml:mo>
                            <mml:msup>
                                <mml:mrow>
                                    <mml:mo stretchy="true">(</mml:mo>
                                    <mml:mfrac>
                                        <mml:msub>
                                            <mml:mi>&#x03c3;</mml:mi>
                                            <mml:msub>
                                                <mml:mi>x</mml:mi>
                                                <mml:mi>i</mml:mi>
                                            </mml:msub>
                                        </mml:msub>
                                        <mml:mrow>
                                            <mml:mo stretchy="true">(</mml:mo>
                                            <mml:mo>&#x2211;</mml:mo>
                                            <mml:msub>
                                                <mml:mi>C</mml:mi>
                                                <mml:mi>i</mml:mi>
                                            </mml:msub>
                                            <mml:mo stretchy="true">)</mml:mo>
                                        </mml:mrow>
                                    </mml:mfrac>
                                    <mml:mo stretchy="true">)</mml:mo>
                                </mml:mrow>
                                <mml:mn>2</mml:mn>
                            </mml:msup>
                            <mml:msubsup>
                                <mml:mi>&#x03c3;</mml:mi>
                                <mml:mi>y</mml:mi>
                                <mml:mn>2</mml:mn>
                            </mml:msubsup>
                            <mml:mo>=</mml:mo>
                            <mml:mo>&#x2211;</mml:mo>
                            <mml:msup>
                                <mml:mrow>
                                    <mml:mo stretchy="true">(</mml:mo>
                                    <mml:mfrac>
                                        <mml:msub>
                                            <mml:mi>&#x03c3;</mml:mi>
                                            <mml:msub>
                                                <mml:mi>y</mml:mi>
                                                <mml:mi>i</mml:mi>
                                            </mml:msub>
                                        </mml:msub>
                                        <mml:mrow>
                                            <mml:mo stretchy="true">(</mml:mo>
                                            <mml:mo>&#x2211;</mml:mo>
                                            <mml:msub>
                                                <mml:mi>C</mml:mi>
                                                <mml:mi>i</mml:mi>
                                            </mml:msub>
                                            <mml:mo stretchy="true">)</mml:mo>
                                        </mml:mrow>
                                    </mml:mfrac>
                                    <mml:mo stretchy="true">)</mml:mo>
                                </mml:mrow>
                                <mml:mn>2</mml:mn>
                            </mml:msup>
                            <mml:mspace width="0.25em"/>
                            <mml:msubsup>
                                <mml:mi>&#x03c3;</mml:mi>
                                <mml:mi>z</mml:mi>
                                <mml:mn>2</mml:mn>
                            </mml:msubsup>
                            <mml:mo>=</mml:mo>
                            <mml:mo>&#x2211;</mml:mo>
                            <mml:msup>
                                <mml:mrow>
                                    <mml:mo stretchy="true">(</mml:mo>
                                    <mml:mfrac>
                                        <mml:msub>
                                            <mml:mi>&#x03c3;</mml:mi>
                                            <mml:msub>
                                                <mml:mi>z</mml:mi>
                                                <mml:mi>i</mml:mi>
                                            </mml:msub>
                                        </mml:msub>
                                        <mml:mrow>
                                            <mml:mo stretchy="true">(</mml:mo>
                                            <mml:mo>&#x2211;</mml:mo>
                                            <mml:msub>
                                                <mml:mi>C</mml:mi>
                                                <mml:mi>i</mml:mi>
                                            </mml:msub>
                                            <mml:mo stretchy="true">)</mml:mo>
                                        </mml:mrow>
                                    </mml:mfrac>
                                    <mml:mo stretchy="true">)</mml:mo>
                                </mml:mrow>
                                <mml:mn>2</mml:mn>
                            </mml:msup>
                        </mml:math>
                        <label>(5)</label>
                    </disp-formula>
                </p>
                <p>Another quality indicator of a node point is interpolated accuracy using contour data obtained by Delauney triangulation. The formula is as follows:
                    <disp-formula id="e6">
                        <mml:math display="block">
                            <mml:msubsup>
                                <mml:mi>z</mml:mi>
                                <mml:mtext>contour</mml:mtext>
                                <mml:mi>i</mml:mi>
                            </mml:msubsup>
                            <mml:mo>=</mml:mo>
                            <mml:msqrt>
                                <mml:mfrac>
                                    <mml:mrow>
                                        <mml:mo>&#x2211;</mml:mo>
                                        <mml:mrow>
                                            <mml:mo stretchy="true">(</mml:mo>
                                            <mml:msub>
                                                <mml:mi>d</mml:mi>
                                                <mml:mi>i</mml:mi>
                                            </mml:msub>
                                            <mml:mo>&#x2219;</mml:mo>
                                            <mml:msub>
                                                <mml:mi>d</mml:mi>
                                                <mml:mi>i</mml:mi>
                                            </mml:msub>
                                            <mml:mo stretchy="true">)</mml:mo>
                                        </mml:mrow>
                                    </mml:mrow>
                                    <mml:mi mathvariant="normal">n</mml:mi>
                                </mml:mfrac>
                            </mml:msqrt>
                        </mml:math>
                        <label>(6)</label>
                    </disp-formula>
                </p>
                <p>
                    <italic toggle="yes">i</italic>: node 
                    <italic toggle="yes">i</italic> of a line. 
                    <italic toggle="yes">n</italic> the number of nodes in a line.</p>
                <p>
                    <inline-formula>
                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>d</mml:mi>
                                <mml:mi>i</mml:mi>
                            </mml:msub>
                        </mml:math>
                    </inline-formula>: elevation from point D to plane ABC in 
                    <xref ref-type="fig" rid="f5">Figure 5</xref>.</p>
                <fig fig-type="figure" id="f5" orientation="portrait" position="float">
                    <label>Figure 5. </label>
                    <caption>
                        <title>Elevation d is obtained from point D to surface ABC in delauney triangulation.</title>
                        <p>NOTE: Interpolated accuracy using contour data is obtained by Delauney triangulation. Elevation 
                            <italic toggle="yes">d</italic> is applied in 
                            <xref ref-type="disp-formula" rid="e6">Equation (6)</xref>. Own work.</p>
                    </caption>
                    <graphic id="gr5" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/166549/112563b0-442d-44f2-ba21-368e5ffed671_figure5.gif"/>
                </fig>
                <p>Contour data were used to produce a Delauney triangulation network. The nodes of the line are interpolated to obtain the difference in the elevation data and calculate the interpolated accuracy for each line. Once the theoretical and interpolated accuracies of each node of a line segment have been determined, the error propagation technique can be used to obtain the error band of the segment (
                    <xref ref-type="fig" rid="f6">Figure 6</xref>). Here, 
                    <italic toggle="yes">x</italic> and 
                    <italic toggle="yes">y</italic> are treated as independent uncorrelated random variables, as indicated by the following formula:
                    <disp-formula id="e7">
                        <mml:math display="block">
                            <mml:msubsup>
                                <mml:mi>&#x03c3;</mml:mi>
                                <mml:mrow>
                                    <mml:mi>x</mml:mi>
                                    <mml:mo>&#x2032;</mml:mo>
                                </mml:mrow>
                                <mml:mn>2</mml:mn>
                            </mml:msubsup>
                            <mml:mo>=</mml:mo>
                            <mml:msubsup>
                                <mml:mi>&#x03c3;</mml:mi>
                                <mml:mi>x</mml:mi>
                                <mml:mn>2</mml:mn>
                            </mml:msubsup>
                            <mml:mo>.</mml:mo>
                            <mml:msup>
                                <mml:mo mathvariant="italic">cos</mml:mo>
                                <mml:mn>2</mml:mn>
                            </mml:msup>
                            <mml:mi>&#x03b8;</mml:mi>
                            <mml:mo>+</mml:mo>
                            <mml:msubsup>
                                <mml:mi>&#x03c3;</mml:mi>
                                <mml:mi>y</mml:mi>
                                <mml:mn>2</mml:mn>
                            </mml:msubsup>
                            <mml:mo>.</mml:mo>
                            <mml:msup>
                                <mml:mo mathvariant="italic">sin</mml:mo>
                                <mml:mn>2</mml:mn>
                            </mml:msup>
                            <mml:mi>&#x03b8;</mml:mi>
                            <mml:mspace width="0.25em"/>
                            <mml:mo>&#x00a0;</mml:mo>
                            <mml:mo>&#x00a0;</mml:mo>
                            <mml:mo>&#x00a0;</mml:mo>
                            <mml:mo>&#x00a0;</mml:mo>
                            <mml:mo>&#x00a0;</mml:mo>
                            <mml:mo>&#x00a0;</mml:mo>
                            <mml:mo>&#x00a0;</mml:mo>
                            <mml:msubsup>
                                <mml:mi>&#x03c3;</mml:mi>
                                <mml:mrow>
                                    <mml:mi>y</mml:mi>
                                    <mml:mo>&#x2032;</mml:mo>
                                </mml:mrow>
                                <mml:mn>2</mml:mn>
                            </mml:msubsup>
                            <mml:mo>=</mml:mo>
                            <mml:msubsup>
                                <mml:mi>&#x03c3;</mml:mi>
                                <mml:mi>x</mml:mi>
                                <mml:mn>2</mml:mn>
                            </mml:msubsup>
                            <mml:mo>.</mml:mo>
                            <mml:msup>
                                <mml:mo mathvariant="italic">sin</mml:mo>
                                <mml:mn>2</mml:mn>
                            </mml:msup>
                            <mml:mi>&#x03b8;</mml:mi>
                            <mml:mo>+</mml:mo>
                            <mml:msubsup>
                                <mml:mi>&#x03c3;</mml:mi>
                                <mml:mi>y</mml:mi>
                                <mml:mn>2</mml:mn>
                            </mml:msubsup>
                            <mml:mo>.</mml:mo>
                            <mml:msup>
                                <mml:mo mathvariant="italic">cos</mml:mo>
                                <mml:mn>2</mml:mn>
                            </mml:msup>
                            <mml:mi>&#x03b8;</mml:mi>
                        </mml:math>
                        <label>(7)</label>
                    </disp-formula>
                </p>
                <fig fig-type="figure" id="f6" orientation="portrait" position="float">
                    <label>Figure 6. </label>
                    <caption>
                        <title>Confidence interval between two nodes with known standard deviations.</title>
                        <p>(a) Angle &#x03b8; between two coordinate systems. (b) The confidence interval established between two known nodes on the basis of the selected significance level. From &#x201c;a stochastic process-based model for the positional error of line segments in GIS.&#x201d; by Shi, W., Liu, W., 2000, International Journal of Geographical Information Science, 14(1), 51-66.</p>
                    </caption>
                    <graphic id="gr6" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/166549/112563b0-442d-44f2-ba21-368e5ffed671_figure6.gif"/>
                </fig>
                <p>When (
                    <inline-formula>
                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>A</mml:mi>
                            </mml:msub>
                            <mml:mo>,</mml:mo>
                            <mml:msub>
                                <mml:mi>y</mml:mi>
                                <mml:mi>A</mml:mi>
                            </mml:msub>
                        </mml:math>
                    </inline-formula>) and (
                    <inline-formula>
                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>B</mml:mi>
                            </mml:msub>
                            <mml:mo>,</mml:mo>
                            <mml:msub>
                                <mml:mi>y</mml:mi>
                                <mml:mi>B</mml:mi>
                            </mml:msub>
                        </mml:math>
                    </inline-formula>) follow a normal distribution, the transformed coordinates (
                    <italic toggle="yes">x</italic>,
                    <italic toggle="yes">y</italic>) and (
                    <italic toggle="yes">x</italic>&#x2019;,
                    <italic toggle="yes">y</italic>&#x2019;) also have a normal distribution. Given a significance level of &#x03b1;, the confidence interval for the line on the 
                    <italic toggle="yes">y</italic>&#x2019;-axis can be calculated as (
                    <inline-formula>
                        <mml:math display="inline">
                            <mml:mo>&#x2212;</mml:mo>
                            <mml:msub>
                                <mml:mi>Z</mml:mi>
                                <mml:mfrac bevelled="true">
                                    <mml:mi>&#x03b1;</mml:mi>
                                    <mml:mn>2</mml:mn>
                                </mml:mfrac>
                            </mml:msub>
                            <mml:mo>.</mml:mo>
                            <mml:msub>
                                <mml:mi>&#x03c3;</mml:mi>
                                <mml:mrow>
                                    <mml:mi>y</mml:mi>
                                    <mml:mo>&#x2032;</mml:mo>
                                </mml:mrow>
                            </mml:msub>
                        </mml:math>
                    </inline-formula>&#x2003;
                    <inline-formula>
                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>Z</mml:mi>
                                <mml:mfrac bevelled="true">
                                    <mml:mi>&#x03b1;</mml:mi>
                                    <mml:mn>2</mml:mn>
                                </mml:mfrac>
                            </mml:msub>
                        </mml:math>
                    </inline-formula>. 
                    <inline-formula>
                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>&#x03c3;</mml:mi>
                                <mml:mrow>
                                    <mml:mi>y</mml:mi>
                                    <mml:mo>&#x2032;</mml:mo>
                                </mml:mrow>
                            </mml:msub>
                        </mml:math>
                    </inline-formula>). Plotting and connecting all points within this confidence level yields 
                    <xref ref-type="fig" rid="f6">Figure 6</xref>, which is similar to the GIS result.
                    <sup>
                        <xref ref-type="bibr" rid="ref23">23</xref>
                    </sup>
                </p>
            </sec>
        </sec>
        <sec id="sec14" sec-type="results">
            <title>Results</title>
            <p>The LiDAR data employed in this study were collected in a mountainous region using an Optech Galaxy ALTM&#x2122; 30/70 scanner provided by Chung-Hsing Surveying, Taichung, Taiwan. The flight altitude was set at 4,400 m. Non-terrain LiDAR point clouds were filtered out of the data. The LiDAR system captured data at a density of 0.05 points/m
                <sup>2</sup> and had horizontal and vertical accuracies of approximately 2.2 and 0.35 m, respectively. The authors have provided flow diagram of line growin to benefit readers and peers to replicate our work in 
                <xref ref-type="fig" rid="f10">Figure 10</xref>. The mountainous region investigated in this study is shown in 
                <xref ref-type="fig" rid="f1">Figure 1(a)</xref>. Given the low density of LiDAR data, a search radius of 50 m was selected to capture a sufficient number of point clouds for depicting ridge and valley lines.</p>
            <p>Identifying local maxima in 
                <italic toggle="yes">C</italic> values is critical for designating seed points to initiate the growth of ridge and valley lines. In 
                <xref ref-type="fig" rid="f7">Figure 7</xref>, the point clouds are classified into two types using 
                <xref ref-type="disp-formula" rid="e1">Equation (1)</xref>.</p>
            <fig fig-type="figure" id="f7" orientation="portrait" position="float">
                <label>Figure 7. </label>
                <caption>
                    <title>LiDAR point clouds in the mountainous region.</title>
                    <p>NOTE: Candidate seeds are indicated in orange, and other points are in green. Own work.</p>
                </caption>
                <graphic id="gr7" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/166549/112563b0-442d-44f2-ba21-368e5ffed671_figure7.gif"/>
            </fig>
            <p>Following the initial phase, the line growth was executed using 
                <xref ref-type="disp-formula" rid="e2">Equations (2)</xref>&#x2013;
                <xref ref-type="disp-formula" rid="e4">(4)</xref>. In this step, redundant point clouds were eliminated, and points were connected to form ridges or valley lines. 
                <xref ref-type="fig" rid="f8">Figure 8</xref> illustrates the results with different colors demarcating the various line segments. The search radius was 50 m. The basic threshold (&#x03c9;) is approximately 5&#x00b0;, and three times the average value (3&#x03c9;) is 15&#x00b0;applied as the threshold value in this study. Although some fragmented ridge and valley lines were obtained, the line growth algorithm effectively extracted both prominent and subtle line features, despite the low point cloud density.</p>
            <fig fig-type="figure" id="f8" orientation="portrait" position="float">
                <label>Figure 8. </label>
                <caption>
                    <title>Ridge and valley lines after line growth.</title>
                    <p>NOTE: Each with a unique color. The most crucial lines were successfully extracted. Own work.</p>
                </caption>
                <graphic id="gr8" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/166549/112563b0-442d-44f2-ba21-368e5ffed671_figure8.gif"/>
            </fig>
            <p>Ridges and valley lines were obtained following the line-growing procedure, although these lines consisted of fragmented segments (
                <xref ref-type="fig" rid="f8">Figure 8</xref>). The theoretical accuracies of the ridge and valley lines were calculated and the corresponding data are listed in 
                <xref ref-type="table" rid="T1">Table 1</xref>. The lowest horizontal and vertical theoretical accuracies are approximately 2.5 and 0.40 m. These values closely match the accuracies reported in LiDAR instrument documentation. In some instances, the theoretical accuracy surpassed the reported instrument accuracy. Notably, applying the line-growing method resulted in considerably greater line accuracy, as indicated by a 90% enhancement in both horizontal and vertical measurements (2.508 vs. 0.253 m and 0.398 vs. 0.040 m, respectively; 
                <xref ref-type="table" rid="T1">Table 1</xref>).</p>
            <table-wrap id="T1" orientation="portrait" position="float">
                <label>Table 1. </label>
                <caption>
                    <title>Theoretical accuracies of the results in the vertical and horizontal dimensions.</title>
                </caption>
                <table content-type="article-table" frame="hsides">
                    <thead>
                        <tr>
                            <th align="left" colspan="1" rowspan="1" valign="top">Theory accuracy</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">Horizontal (m)</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">Vertical (m)</th>
                        </tr>
                    </thead>
                    <tbody>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Min</bold>
                            </td>
                            <td align="left" colspan="1" rowspan="1" valign="top">0.253</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">0.04</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Max</bold>
                            </td>
                            <td align="left" colspan="1" rowspan="1" valign="top">2.508</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">0.398</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Avg</bold>
                            </td>
                            <td align="left" colspan="1" rowspan="1" valign="top">1.239</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">0.197</td>
                        </tr>
                    </tbody>
                </table>
                <table-wrap-foot>
                    <p>NOTE: Applying line-growing method resulted in considerably greater line accuracy, as indicated by a 90% enhancement in both horizontal and vertical measurements. (2.508 vs. 0.253 m and 0.398 vs. 0.040 m, respectively). Own work.</p>
                </table-wrap-foot>
            </table-wrap>
            <p>In this region, a contour map was drawn by experienced survey workers using stereo plotters. The interval height of the contour lines was 20 m, and the nodes of the contour lines were applied to produce a Delauney triangulation network. The extracted nodes of the line in 
                <xref ref-type="fig" rid="f8">Figure 8</xref> were interpolated using 
                <xref ref-type="disp-formula" rid="e6">Equation (6)</xref>, and the interpolated accuracy is displayed in 
                <xref ref-type="table" rid="T2">Table 2</xref>. The worst interpolated accuracy (approximately 16.102 m) is still less than the interval height of contour lines (20m), therefore the method is effective in enhancing the accuracy, even at 98% (16.102 vs. 0.205 m).</p>
            <table-wrap id="T2" orientation="portrait" position="float">
                <label>Table 2. </label>
                <caption>
                    <title>Interpolated accuracy in the experimental region.</title>
                </caption>
                <table content-type="article-table" frame="hsides">
                    <thead>
                        <tr>
                            <th align="left" colspan="1" rowspan="1" valign="top">Interpolation accuracy</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">Vertical (m)</th>
                        </tr>
                    </thead>
                    <tbody>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Min</bold>
                            </td>
                            <td align="left" colspan="1" rowspan="1" valign="top">0.205</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Max</bold>
                            </td>
                            <td align="left" colspan="1" rowspan="1" valign="top">16.102</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Avg</bold>
                            </td>
                            <td align="left" colspan="1" rowspan="1" valign="top">3.403</td>
                        </tr>
                    </tbody>
                </table>
                <table-wrap-foot>
                    <p>NOTE: The worst interpolated accuracy (approximately 16.102 m) is still less than the interval height of contour lines (20m), therefore the method is effective in enhancing the accuracy, even at 98% (16.102 vs. 0.205 m). Own work.</p>
                </table-wrap-foot>
            </table-wrap>
            <p>
                <xref ref-type="fig" rid="f9">Figure 9</xref> shows the contour lines together with the results, and indicates the favorable accuracy and reliability of the results. Automated processes can reduce the required time and effort by eliminating redundant tasks.</p>
            <fig fig-type="figure" id="f9" orientation="portrait" position="float">
                <label>Figure 9. </label>
                <caption>
                    <title>Relationship between extracted lines and contour lines.</title>
                    <p>NOTE: Lines extracted through line growth (red) and contour lines (green). Own work.</p>
                </caption>
                <graphic id="gr9" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/166549/112563b0-442d-44f2-ba21-368e5ffed671_figure9.gif"/>
            </fig>
            <fig fig-type="figure" id="f10" orientation="portrait" position="float">
                <label>Figure 10. </label>
                <caption>
                    <title>Flow diagram.</title>
                </caption>
                <graphic id="gr10" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/166549/112563b0-442d-44f2-ba21-368e5ffed671_figure10.gif"/>
            </fig>
        </sec>
        <sec id="sec15" sec-type="discussion">
            <title>Discussion</title>
            <p>This study employed the TVM to obtain the line feature strength 
                <italic toggle="yes">C</italic> and its corresponding eigenvector 
                <bold>
                    <italic toggle="yes">v</italic>
                </bold> of discrete LiDAR point clouds, which are helpful parameters for extracting valley and ridge lines from LiDAR datasets on mountainous terrain. By utilizing the local 
                <italic toggle="yes">C</italic> maxima, redundant data points can be effectively eliminated, and the computational efficiency can be enhanced. Furthermore, the angles between successive 
                <italic toggle="yes">v</italic> vectors serve as crucial metrics for refining the alignment of adjacent points along the lines. 
                <italic toggle="yes">C</italic> and 
                <italic toggle="yes">v</italic> values contribute substantially to the line-growing technique applied to mountainous regions in this study. The concept of a moving mask was adopted to maintain intricate line details. Employing the line-growing technique enables the extraction of primary and minor ridge and valley lines contingent upon specific project requirements. The method can be applied to any terrain to extract line features, which is different from setting thresholds to affect the final results.</p>
            <p>The line-growing technique developed in this study can yield highly accurate line nodes for the extraction of ridge and valley lines in mountainous regions. The proposed approach is effective in capturing both primary and minor ridges but tends to produce lines that are short and fragmented. One avenue for improvement lies in connecting these fragmented ridge or valley lines when they belong to the same topographical features that will be studied in the future. The method presented in this paper is fast and automated and can furnish operators with a wealth of detailed information about minor line features. This enables the extraction of ridge and valley lines that are tailored to specific requirements. Undoubtedly, the method developed here can be generalized to a large amount of LiDAR data.</p>
            <sec id="sec16">
                <title>Ethical approval and consent</title>
                <p>Ethical approval and consent were not required.</p>
            </sec>
        </sec>
    </body>
    <back>
        <sec id="sec19" sec-type="data-availability">
            <title>Data availability</title>
            <sec id="sec20">
                <title>Underlying data</title>
                <p>Zenodo: Extracting Ridge and Valley Lines in Mountainous Areas from Airborne Lidar Data by Utilizing Line Feature Strength, 
                    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5281/zenodo.12771247">https://doi.org/10.5281/zenodo.12771247</ext-link>.
                    <sup>

                        <xref ref-type="bibr" rid="ref24">24</xref>
</sup>
                </p>
                <p>This project contains the following underlying data:
                    <list list-type="bullet">
                        <list-item>
                            <label>&#x2022;</label>
                            <p>Contour.ods</p>
                        </list-item>
                        <list-item>
                            <label>&#x2022;</label>
                            <p>LidarData.ods</p>
                        </list-item>
                    </list>
                </p>
                <p>Data are available under the terms of the 
                    <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/publicdomain/zero/1.0/">Creative Commons Zero &#x201c;No rights reserved&#x201d; data waiver</ext-link> (CC0 1.0 Public domain dedication).</p>
            </sec>
        </sec>
        <ack>
            <title>Acknowledgements</title>
            <p>The authors are grateful to Chung-Hsing Surveying Co., Ltd., Taichung, Taiwan, for providing LiDAR datasets.</p>
        </ack>
        <ref-list>
            <title>References</title>
            <ref id="ref1">
                <label>1</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>You</surname>
                            <given-names>RJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lin</surname>
                            <given-names>BC</given-names>
                        </name>
</person-group>:
                    <article-title>Building feature extraction from airborne Lidar data based on tensor voting algorithm.</article-title>
                    <source>

                        <italic toggle="yes">Photogramm. Eng. Remote. Sens.</italic>
</source>
                    <year>2011</year>;<volume>77</volume>(<issue>12</issue>):<fpage>1221</fpage>&#x2013;<lpage>1231</lpage>.
                    <pub-id pub-id-type="doi">10.14358/PERS.77.12.1221</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref2">
                <label>2</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>You</surname>
                            <given-names>RJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lin</surname>
                            <given-names>BC</given-names>
                        </name>
</person-group>:
                    <article-title>A quality prediction method for building model reconstruction using LiDAR data and topographic map.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Trans. Geosci. Remote Sens.</italic>
</source>
                    <year>2011</year>;<volume>49</volume>(<issue>9</issue>):<fpage>3471</fpage>&#x2013;<lpage>3480</lpage>.
                    <pub-id pub-id-type="doi">10.1109/TGRS.2011.2128326</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref3">
                <label>3</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Dey</surname>
                            <given-names>EK</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Awrangjeb</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tarsha Kurdi</surname>
                            <given-names>F</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Machine learning-based segmentation of aerial LiDAR point cloud data on building roof.</article-title>
                    <source>

                        <italic toggle="yes">Eur. J. Remote Sens.</italic>
</source>
                    <year>2023</year>;<volume>56</volume>(<issue>1</issue>):<fpage>2210745</fpage>.
                    <pub-id pub-id-type="doi">10.1080/22797254.2023.2210745</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref4">
                <label>4</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zhao</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>You</surname>
                            <given-names>S</given-names>
                        </name>
</person-group>:
                    <chapter-title>Road network extraction from airborne LiDAR data using scene context.</chapter-title>
                    <source>

                        <italic toggle="yes">In 2012 IEEE Computer Society Con-ference on Computer Vision and Pattern Recognition Workshops.</italic>
</source>
                    <year>2012</year>; pp.<fpage>9</fpage>&#x2013;<lpage>16</lpage>.
                    <pub-id pub-id-type="doi">10.1109/CVPRW.2012.6238909</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref5">
                <label>5</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Kraus</surname>
                            <given-names>K</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Pfeifer</surname>
                            <given-names>N</given-names>
                        </name>
</person-group>:
                    <article-title>Advanced DTM generation from LIDAR data.</article-title>
                    <source>

                        <italic toggle="yes">International Archives of Photogrammetry Remote Sensing And Spatial Inf. Sci.</italic>
</source>
                    <year>2001</year>;<volume>34</volume>(<issue>3/W4</issue>):<fpage>23</fpage>&#x2013;<lpage>30</lpage>.</mixed-citation>
            </ref>
            <ref id="ref6">
                <label>6</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>&#x0160;troner</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Urban</surname>
                            <given-names>R</given-names>
                        </name>

                        <name name-style="western">
                            <surname>K&#x0159;emen</surname>
                            <given-names>T</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>UAV DTM acquisition in a forested area&#x2013;comparison of low-cost photogrammetry (DJI Zenmuse P1) and LiDAR solutions (DJI Zenmuse L1).</article-title>
                    <source>

                        <italic toggle="yes">Eur. J. Remote Sens.</italic>
</source>
                    <year>2023</year>;<volume>56</volume>(<issue>1</issue>):<fpage>2179942</fpage>.
                    <pub-id pub-id-type="doi">10.1080/22797254.2023.2179942</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref7">
                <label>7</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Okyay</surname>
                            <given-names>U</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Telling</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Glennie</surname>
                            <given-names>CL</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Airborne lidar change detection: An overview of Earth sciences applications.</article-title>
                    <source>

                        <italic toggle="yes">Earth Sci. Rev.</italic>
</source>
                    <year>2019</year>;<volume>198</volume>:<fpage>102929</fpage>.
                    <pub-id pub-id-type="doi">10.1016/j.earscirev.2019.102929</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref8">
                <label>8</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Al-Kakey</surname>
                            <given-names>O</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Othman</surname>
                            <given-names>AA</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Al-Mukhtar</surname>
                            <given-names>M</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Proposing Optimal Locations for Runoff Harvesting and Water Management Structures in the Hami Qeshan Watershed, Iraq.</article-title>
                    <source>

                        <italic toggle="yes">ISPRS Int. J. Geo Inf.</italic>
</source>
                    <year>2023</year>;<volume>12</volume>(<issue>8</issue>):<fpage>312</fpage>.
                    <pub-id pub-id-type="doi">10.3390/ijgi12080312</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref9">
                <label>9</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Vernon</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>St. Peter</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Crandall</surname>
                            <given-names>C</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Spatial Application of Southern US Pine Water Yield for Prioritizing Forest Management Activities.</article-title>
                    <source>

                        <italic toggle="yes">ISPRS Int. J. Geo Inf.</italic>
</source>
                    <year>2023</year>;<volume>12</volume>(<issue>2</issue>):<fpage>34</fpage>.
                    <pub-id pub-id-type="doi">10.3390/ijgi12020034</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref10">
                <label>10</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Soycan</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tunal&#x0131;o&#x011f;lu</surname>
                            <given-names>N</given-names>
                        </name>

                        <name name-style="western">
                            <surname>&#x00d6;calan</surname>
                            <given-names>T</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Three dimensional modeling of a forested area using an airborne light detection and ranging method.</article-title>
                    <source>

                        <italic toggle="yes">Arab. J. Sci. Eng.</italic>
</source>
                    <year>2011</year>;<volume>36</volume>:<fpage>581</fpage>&#x2013;<lpage>595</lpage>.
                    <pub-id pub-id-type="doi">10.1007/s13369-011-0054-8</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref11">
                <label>11</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Streutker</surname>
                            <given-names>DR</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Glenn</surname>
                            <given-names>NF</given-names>
                        </name>
</person-group>:
                    <article-title>LiDAR measurement of sagebrush steppe vegetation heights.</article-title>
                    <source>

                        <italic toggle="yes">Remote Sens. Environ.</italic>
</source>
                    <year>2006</year>;<volume>102</volume>(<issue>1-2</issue>):<fpage>135</fpage>&#x2013;<lpage>145</lpage>.
                    <pub-id pub-id-type="doi">10.1016/j.rse.2006.02.011</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref12">
                <label>12</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Kushwaha</surname>
                            <given-names>SKP</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Singh</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Jain</surname>
                            <given-names>K</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Qualitative Analysis of Tree Canopy Top Points Extraction from Different Terrestrial Laser Scanner Combinations in Forest Plots.</article-title>
                    <source>

                        <italic toggle="yes">ISPRS Int. J. Geo Inf.</italic>
</source>
                    <year>2023</year>;<volume>12</volume>(<issue>6</issue>):<fpage>250</fpage>.
                    <pub-id pub-id-type="doi">10.3390/ijgi12060250</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref13">
                <label>13</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Micha&#x0142;owska</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Rapi&#x0144;ski</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Janicka</surname>
                            <given-names>J</given-names>
                        </name>
</person-group>:
                    <article-title>Tree species classification on images from airborne mobile mapping using ML. NET.</article-title>
                    <source>

                        <italic toggle="yes">Eur. J. Remote Sens.</italic>
</source>
                    <year>2023</year>;<volume>56</volume>(<issue>1</issue>):<fpage>2271651</fpage>.
                    <pub-id pub-id-type="doi">10.1080/22797254.2023.2271651</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref14">
                <label>14</label>
                <mixed-citation publication-type="book">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Gonzales</surname>
                            <given-names>RC</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Paul</surname>
                            <given-names>W</given-names>
                        </name>
</person-group>:
                    <source>

                        <italic toggle="yes">Digital image processing.</italic>
</source>
                    <publisher-name>Addison-Wesley Longman Publishing Co., Inc.</publisher-name>;<year>1987</year>.</mixed-citation>
            </ref>
            <ref id="ref15">
                <label>15</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>McLaughlin</surname>
                            <given-names>RA</given-names>
                        </name>
</person-group>:
                    <article-title>Extracting transmission lines from airborne LIDAR data.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Geosci. Remote Sens. Lett.</italic>
</source>
                    <year>2006</year>;<volume>3</volume>(<issue>2</issue>):<fpage>222</fpage>&#x2013;<lpage>226</lpage>.
                    <pub-id pub-id-type="doi">10.1109/LGRS.2005.863390</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref16">
                <label>16</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Guan</surname>
                            <given-names>H</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Yu</surname>
                            <given-names>Y</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Li</surname>
                            <given-names>J</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Extraction of power-transmission lines from vehicle-borne lidar data.</article-title>
                    <source>

                        <italic toggle="yes">Int. J. Remote Sens.</italic>
</source>
                    <year>2016</year>;<volume>37</volume>(<issue>1</issue>):<fpage>229</fpage>&#x2013;<lpage>247</lpage>.
                    <pub-id pub-id-type="doi">10.1080/01431161.2015.1125549</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref17">
                <label>17</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Bailly</surname>
                            <given-names>JS</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lagacherie</surname>
                            <given-names>P</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Millier</surname>
                            <given-names>C</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Agrarian landscapes linear features detection from LiDAR: application to artificial drainage networks.</article-title>
                    <source>

                        <italic toggle="yes">Int. J. Remote Sens.</italic>
</source>
                    <year>2008</year>;<volume>29</volume>(<issue>12</issue>):<fpage>3489</fpage>&#x2013;<lpage>3508</lpage>.
                    <pub-id pub-id-type="doi">10.1080/01431160701469057</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref18">
                <label>18</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Chang</surname>
                            <given-names>YC</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Song</surname>
                            <given-names>GS</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Hsu</surname>
                            <given-names>SK</given-names>
                        </name>
</person-group>:
                    <article-title>Automatic extraction of ridge and valley axes using the profile recognition and polygon-breaking algorithm.</article-title>
                    <source>

                        <italic toggle="yes">Comput. Geosci.</italic>
</source>
                    <year>2008</year>;<volume>24</volume>(<issue>1</issue>):<fpage>83</fpage>&#x2013;<lpage>93</lpage>.
                    <pub-id pub-id-type="doi">10.1016/S00983004 (97)00078-2</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref19">
                <label>19</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>G&#x00fc;lgen</surname>
                            <given-names>F</given-names>
                        </name>

                        <name name-style="western">
                            <surname>G&#x00f6;kg&#x00f6;z</surname>
                            <given-names>T</given-names>
                        </name>
</person-group>:
                    <article-title>Automatic extraction of terrain skeleton lines from digital elevation models.</article-title>
                    <source>

                        <italic toggle="yes">International Archives of Photogrammetry, Remote Sensing and Spatial Inf. Sci.</italic>
</source>
                    <year>2004</year>;<volume>35</volume>(<issue>B3</issue>).</mixed-citation>
            </ref>
            <ref id="ref20">
                <label>20</label>
                <mixed-citation publication-type="book">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Medioni</surname>
                            <given-names>G</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lee</surname>
                            <given-names>MS</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Tang</surname>
                            <given-names>CK</given-names>
                        </name>
</person-group>:
                    <source>

                        <italic toggle="yes">A Computational framework for segmentation and grouping.</italic>
</source>
                    <publisher-name>Elsevier Science B.V</publisher-name>;<year>2000</year>.</mixed-citation>
            </ref>
            <ref id="ref21">
                <label>21</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>You</surname>
                            <given-names>RJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lee</surname>
                            <given-names>CL</given-names>
                        </name>
</person-group>:
                    <article-title>Accuracy improvement of airborne Lidar strip adjustment by using height data and surface Feature strength information derived from the tensor voting algorithm.</article-title>
                    <source>

                        <italic toggle="yes">ISPRS Int. J. Geo Inf.</italic>
</source>
                    <year>2020</year>;<volume>9</volume>:<fpage>50</fpage>.
                    <pub-id pub-id-type="doi">10.3390/ijgi9010050</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref22">
                <label>22</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Schuster</surname>
                            <given-names>HF</given-names>
                        </name>
</person-group>:
                    <chapter-title>Segmentation of lidar data using the tensor voting framework.</chapter-title>
                    <source>

                        <italic toggle="yes">Proceedings of the XXth ISPRS Congress: Geo-Imagery Bridging Continents, Commission III, 12&#x2013;23 July, Istanbul, Turkey, 12&#x2013;23 July.</italic>
</source>
                    <year>2004</year>; pp.<fpage>1073</fpage>&#x2013;<lpage>1078</lpage>.</mixed-citation>
            </ref>
            <ref id="ref23">
                <label>23</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Shi</surname>
                            <given-names>W</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Liu</surname>
                            <given-names>W</given-names>
                        </name>
</person-group>:
                    <article-title>A stochastic process-based model for the positional error of line segments in GIS.</article-title>
                    <source>

                        <italic toggle="yes">Int. J. Geogr. Inf. Sci.</italic>
</source>
                    <year>2000</year>;<volume>14</volume>(<issue>1</issue>):<fpage>51</fpage>&#x2013;<lpage>66</lpage>.
                    <pub-id pub-id-type="doi">10.1080/136588100240958</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref24">
                <label>24</label>
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>You</surname>
                            <given-names>R</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lee</surname>
                            <given-names>C</given-names>
                        </name>
</person-group>:
                    <data-title>Extracting Ridge and Valley Lines in Mountainous Areas from Airborne Lidar Data by Utilizing Line Feature Strength.</data-title>[Data set].<year>2024</year>.
                    <pub-id pub-id-type="doi">10.5281/zenodo.12207561</pub-id>
                </mixed-citation>
            </ref>
        </ref-list>
    </back>
    <sub-article article-type="reviewer-report" id="report426826">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.166549.r426826</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Olatunji Raufu</surname>
                        <given-names>Ibrahim</given-names>
                    </name>
                    <xref ref-type="aff" rid="r426826a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-3474-8618</uri>
                </contrib>
                <aff id="r426826a1">
                    <label>1</label>Department of Surveying and Geoinformatics,, Lead City University, Ibadan, Oyo, Nigeria</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>11</day>
                <month>11</month>
                <year>2025</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2025 Olatunji Raufu I</copyright-statement>
                <copyright-year>2025</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport426826" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.151861.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>reject</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>
                <bold>Peer Review Report.</bold>
            </p>
            <p>
                <bold> </bold>
            </p>
            <p>
                <bold> Summary of the Article</bold>
            </p>
            <p> The paper introduces a method for extracting ridge and valley lines from airborne LiDAR point clouds by applying the Tensor Voting Method (TVM) to compute a new parameter called line feature strength. The authors propose an automated line-growing approach that uses the local maxima of this feature strength and the similarity of tangent vectors to detect geomorphic line structures. The study applies the method to LiDAR data collected over a mountainous area in Taiwan and claims improved accuracy compared with standard threshold-based approaches.</p>
            <p> The topic is relevant to geomatics, LiDAR analysis, and digital terrain modeling, and the paper demonstrates technical understanding of 3D feature extraction. However, several sections need improvement before the paper can be considered scientifically sound.</p>
            <p> </p>
            <p> 
                <bold>Evaluation and Comments</bold>
            </p>
            <p> 
                <bold>1. Rationale for developing the new method: Partly</bold>
            </p>
            <p> The motivation for the new approach is generally stated, but the research gap is not sufficiently clear. The Introduction mentions previous works but does not critically explain why existing ridge or valley extraction methods like PPA or wavelet-based are inadequate for low-density LiDAR data. The novelty of using &#x201c;line feature strength&#x201d; within TVM should be highlighted as the central innovation.</p>
            <p> 
                <bold>Suggestion:</bold> Expand the final paragraph of the Introduction to clearly state: (a) what limitation the proposed method solves, and (b) how the approach differs from earlier work in terms of efficiency, accuracy, or automation.</p>
            <p> </p>
            <p> 
                <bold>2. Technical soundness of the method: Partly</bold>
            </p>
            <p> The method follows the principles of tensor voting and appears mathematically coherent, but important implementation details are missing. The section on &#x201c;tensor communication&#x201d; should include a more explicit description of how neighboring points are weighted and how the final tensor field is computed. Equations (1)-(7) should have all variables defined directly underneath each equation for clarity.</p>
            <p> The paper would also benefit from better structure within the Methods. Two section titles appear consecutively without transition; a short introductory paragraph should connect them. Figure 10 (the workflow diagram) should be placed early in the Methods to help readers understand the full algorithm.</p>
            <p> 
                <bold>Suggestion:</bold> Add a subsection summarizing parameter settings such as search radius and angle threshold and provide justification or references for their selection. Also, cite relevant sources for eigenvector calculation, the region-growing algorithm, and the local maxima detection approach.</p>
            <p> </p>
            <p> 
                <bold>3. Sufficient details for replication: Partly</bold>
            </p>
            <p> The study outlines the main steps but lacks enough procedural information to allow independent replication. Pre-processing steps for filtering ground points and removing non-terrain returns are only briefly mentioned. The derivation of Figure 2 (the C-elevation relationship) is not clearly described. Please indicate how section lines were extracted from the 3D point cloud.</p>
            <p> 
                <bold>Suggestion:&#x00a0;</bold>Add a short Dataset subsection describing the LiDAR acquisition parameters (sensor type, point density, and area size), specify the software tools or programming environment used for tensor voting and line growth, and include a concise table listing all thresholds and constants used during processing.</p>
            <p> These improvements will make the method reproducible for other researchers.</p>
            <p> </p>
            <p> 
                <bold>4. Availability of underlying data: Yes</bold>
            </p>
            <p> The authors have made the underlying LiDAR and contour datasets publicly available on Zenodo under a CC0 license. This is commendable and ensures transparency and data accessibility.</p>
            <p> </p>
            <p> 
                <bold>5. Conclusions and interpretation of findings: Partly</bold>
            </p>
            <p> The conclusions are consistent with the results but are largely descriptive and lack analytical depth. The reported accuracy improvements for instance, 90% enhancement, are not supported by comparison with a baseline algorithm or by statistical testing. The discussion also acknowledges that the extracted lines are fragmented, but no potential solutions are proposed.</p>
            <p> 
                <bold>Suggestion:&#x00a0;</bold>Include a quantitative comparison with a conventional method such as PPA or a threshold-based approach. Add a dedicated Conclusion section summarizing key achievements, known limitations, and future work.</p>
            <p> </p>
            <p> 
                <bold>Points That Must Be Addressed to Make the Article Scientifically Sound</bold>
            </p>
            <p> 1. Clearly define the research gap and novelty of the proposed method in the Introduction.</p>
            <p> 2. Provide a detailed description of the tensor communication step and define all parameters and variables in the equations.</p>
            <p> 3. Include a flow diagram or organigram early in the Methods to clarify the process sequence.</p>
            <p> 4. Add a Data and Implementation subsection specifying pre-processing steps, parameter values, and software used.</p>
            <p> 5. Give quantitative comparisons or validation against an existing extraction technique.</p>
            <p> 6. Add a Conclusion section with key findings, limitations, and suggestions for future work.</p>
            <p> 7. Improve the English by removing informal terms (e.g., &#x201c;etc.&#x201d;) and ensuring consistent terminology.</p>
            <p> </p>
            <p> 
                <bold>Overall Recommendation: Major Revision</bold>
            </p>
            <p> The paper presents a promising and potentially useful method for geomorphic feature extraction from LiDAR data. However, the methodological explanations and validation need to be expanded and clarified before the work meets indexing standards. The suggested revisions will substantially strengthen the paper&#x2019;s scientific soundness and readability.</p>
            <p>Is the rationale for developing the new method (or application) clearly explained?</p>
            <p>Partly</p>
            <p>Is the description of the method technically sound?</p>
            <p>Partly</p>
            <p>Are the conclusions about the method and its performance adequately supported by the findings presented in the article?</p>
            <p>Partly</p>
            <p>If any results are presented, are all the source data underlying the results available to ensure full reproducibility?</p>
            <p>Yes</p>
            <p>Are sufficient details provided to allow replication of the method development and its use by others?</p>
            <p>Partly</p>
            <p>Reviewer Expertise:</p>
            <p>Geodesy, GNSS Meteorology, GNSS Positioning and Navigation, GIS, Remote Sensing, Photogrammetry</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to state that I do not consider it to be of an acceptable scientific standard, for reasons outlined above.</p>
        </body>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report324632">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.166549.r324632</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Tarsha Kurdi</surname>
                        <given-names>Fayez</given-names>
                    </name>
                    <xref ref-type="aff" rid="r324632a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-4952-4350</uri>
                </contrib>
                <aff id="r324632a1">
                    <label>1</label>University of Southern Queensland, Springfield Campus, Springfield, Australia</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>26</day>
                <month>9</month>
                <year>2024</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2024 Tarsha Kurdi F</copyright-statement>
                <copyright-year>2024</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport324632" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.151861.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>reject</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>
                <bold>Introduction</bold>
            </p>
            <p> large amount of terrain data that: remove &#x201c;terrain&#x201d;</p>
            <p> please don&#x2019;t use &#x201c;etc&#x201d;, please check the text.</p>
            <p> If image extraction techniques are employed, please cite a suitable reference such as: [ ref 1 ]</p>
            <p> Please replace &#x201c;Scholars&#x201d; with &#x201c;authors&#x201d;.</p>
            <p> In urban environments, where buildings and roofs exhibit regular patterns, point clouds</p>
            <p> on surfaces are readily distinguishable from others owing to their high surface feature strength. Lines can be identified at the intersections of two adjacent surfaces. Please cite a suitable reference such as: [ ref 2 ]</p>
            <p> Please highlight the contribution and novelty of this study.</p>
            <p> </p>
            <p> 
                <bold>Methods</bold>
            </p>
            <p> Please don&#x2019;t put two section titles consecutively, you must add a transition paragraph between them, please check the paper.</p>
            <p> </p>
            <p> Please add an organigram that describes the suggested approach.</p>
            <p> </p>
            <p> Geometric feature strength</p>
            <p> </p>
            <p> You don&#x2019;t discuss how you extracted the ground class from the measured point cloud.</p>
            <p> Please detailed &#x201c;tensor communication&#x201d; approach and mention the used equations.</p>
            <p> Please explain how you got Figure 2.</p>
            <p> </p>
            <p> Please cite a reference about the calculation of eigenvectors such as: [ ref 3 ]</p>
            <p> </p>
            <p> Please cite a reference for the region growing algorithm.</p>
            <p> How did you select the threshold values?</p>
            <p> Please cite a reference for the local maxima algorithm.</p>
            <p> Please add a new section to detail all used thresholds.</p>
            <p> Please cite the source of all used equations in the paper, if you develop an equation, please explain how you got it. Please define all parameters used in all used Equations.</p>
            <p> Please define all equation elements under them.</p>
            <p> Please add a datasets section to present the used data.</p>
            <p> Figure 10 should be in the method section.</p>
            <p> Please add a conclusion section and do not forget to present future work.</p>
            <p>Is the rationale for developing the new method (or application) clearly explained?</p>
            <p>Partly</p>
            <p>Is the description of the method technically sound?</p>
            <p>Partly</p>
            <p>Are the conclusions about the method and its performance adequately supported by the findings presented in the article?</p>
            <p>No</p>
            <p>If any results are presented, are all the source data underlying the results available to ensure full reproducibility?</p>
            <p>Yes</p>
            <p>Are sufficient details provided to allow replication of the method development and its use by others?</p>
            <p>Partly</p>
            <p>Reviewer Expertise:</p>
            <p>Extraction and modeling of LiDAR data</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to state that I do not consider it to be of an acceptable scientific standard, for reasons outlined above.</p>
        </body>
        <back>
            <ref-list>
                <title>References</title>
                <ref id="rep-ref-324632-1">
                    <label>1</label>
                    <mixed-citation>
                        <person-group person-group-type="author"/>:
                        <article-title>Joint combination of point cloud and DSM for 3D building reconstruction using airborne laser scanner data</article-title>.
                        <source>
                            <italic>ResearchGate</italic>
                        </source>.<year>2007</year>;
                        <ext-link ext-link-type="uri" xlink:href="https://www.researchgate.net/publication/4254359_Joint_combination_of_point_cloud_and_DSM_for_3D_building_reconstruction_using_airborne_laser_scanner_data">Reference source</ext-link>
                    </mixed-citation>
                </ref>
                <ref id="rep-ref-324632-2">
                    <label>2</label>
                    <mixed-citation publication-type="journal">
                        <person-group person-group-type="author"/>:
                        <article-title>Automatic filtering and 2D modeling of airborne laser scanning building point cloud</article-title>.
                        <source>
                            <italic>Transactions in GIS</italic>
                        </source>.<year>2021</year>;<volume>25</volume>(<issue>1</issue>) :
                        <elocation-id>10.1111/tgis.12685</elocation-id>
                        <fpage>164</fpage>-<lpage>188</lpage>
                        <pub-id pub-id-type="doi">10.1111/tgis.12685</pub-id>
                    </mixed-citation>
                </ref>
                <ref id="rep-ref-324632-3">
                    <label>3</label>
                    <mixed-citation publication-type="journal">
                        <person-group person-group-type="author"/>:
                        <article-title>Effective Selection of Variable Point Neighbourhood for Feature Point Extraction from Aerial Building Point Cloud Data</article-title>.
                        <source>
                            <italic>Remote Sensing</italic>
                        </source>.<year>2021</year>;<volume>13</volume>(<issue>8</issue>) :
                        <elocation-id>10.3390/rs13081520</elocation-id>
                        <pub-id pub-id-type="doi">10.3390/rs13081520</pub-id>
                    </mixed-citation>
                </ref>
            </ref-list>
        </back>
    </sub-article>
</article>
