<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "https://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1-mathml3.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" article-type="research-article" dtd-version="1.2" xml:lang="en">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">3069</journal-id>
<journal-title-group>
<journal-title>Traffic Safety Research</journal-title>
</journal-title-group>
<issn pub-type="epub">n/a</issn>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">143435</article-id>
<article-id pub-id-type="doi">10.55329/piou4930</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Research article</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Extracting roadway vertical alignment from USGS LiDAR point cloud data using an Artificial Neural Network based method</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author" corresp="yes">
<contrib-id contrib-id-type="orcid" authenticated="false">https://orcid.org/0009-0000-4638-3930</contrib-id>
<name>
<surname>Jami</surname>
<given-names>Mojibulrahman</given-names>
</name>
<xref ref-type="corresp" rid="author-note-1"/>
<xref ref-type="aff" rid="author-aff-1"><sup>1</sup></xref>
</contrib>
<contrib contrib-type="author">
<contrib-id contrib-id-type="orcid" authenticated="false">https://orcid.org/0000-0001-6941-228X</contrib-id>
<name>
<surname>Bartin</surname>
<given-names>Bekir</given-names>
</name>
<xref ref-type="aff" rid="author-aff-1"><sup>1</sup></xref>
</contrib>
<contrib contrib-type="author">
<contrib-id contrib-id-type="orcid" authenticated="false">https://orcid.org/0000-0001-7909-6532</contrib-id>
<name>
<surname>Ozbay</surname>
<given-names>Kaan</given-names>
</name>
<xref ref-type="aff" rid="author-aff-2"><sup>2</sup></xref>
</contrib>
</contrib-group>
<aff id="author-aff-1">
<label>1</label>
<institution-wrap>
<institution content-type="edu">Özyeğin University, Türkiye</institution>
</institution-wrap>
</aff>
<aff id="author-aff-2">
<label>2</label>
<institution-wrap>
<institution content-type="edu">New York University, the United States of America</institution>
</institution-wrap>
</aff>
<author-notes>
<corresp id="author-note-1">Corresponding author: <email>mojibulrahman.jami@ozu.edu.tr</email></corresp>
</author-notes>
<pub-date publication-format="electronic" date-type="pub" iso-8601-date="03-04-2026">
<day>03</day>
<month>04</month>
<year>2026</year>
</pub-date>
<volume>10</volume>
<fpage>e000134</fpage>
<lpage>e000134</lpage>
<history>
<date date-type="received" iso-8601-date="20-10-2025">
<day>20</day>
<month>10</month>
<year>2025</year>
</date>
<date date-type="accepted" iso-8601-date="22-03-2026">
<day>22</day>
<month>03</month>
<year>2026</year>
</date>
</history>
<permissions>
<license license-type="open-access">
<ali:license_ref xmlns:ali="http://www.niso.org/schemas/ali/1.0/">
http://creativecommons.org/licenses/by/4.0
</ali:license_ref>
<license-p>
This is an open access article distributed under the terms of the <ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/4.0">Creative Commons Attribution License (4.0)</ext-link>, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.
</license-p>
</license>
</permissions>
<abstract>
<p>Vertical grades and vertical curvature significantly influence traffic safety. However, obtaining accurate and large-scale data on roadway vertical alignment remains a major challenge. This paper presents a cost-effective and efficient method for estimating roadway vertical alignment using publicly available aerial LiDAR data provided by the United States Geological Survey. An Artificial Neural Network (ANN) model was proposed to predict whether a LiDAR point belongs to a vertical curve or a tangent segment. Due to the limited availability of actual roadway vertical alignment data and the substantial data requirements of machine learning models, a synthetic training dataset was generated by systematically varying road grades and segment lengths to represent realistic combinations of tangents, crest and sag curves. This approach ensured that the model was exposed to a wide range of geometric configurations and allowed it to learn generalized relationships between vertical alignment features and their corresponding geometric parameters. The model was then independently evaluated by comparing the vertical alignment estimated from the extracted aerial LiDAR data for two-lane two-way rural roadways, Route 152 in New Jersey and Route 299 in California, with their corresponding actual vertical alignment data.  In addition, a case study was conducted on another rural two-lane highway in which the model was used to compute safe speeds for each roadway segment. The resulting speeds were then compared with the posted speed limits along the corridor. The satisfactory estimation results of this study indicate that the proposed approach can be used for conducting large-scale analyses to estimate vertical alignment using publicly available LiDAR data.</p>
</abstract>
<kwd-group>
<kwd>Artificial Neural Networks</kwd>
<kwd>Highway Safety Manual</kwd>
<kwd>LiDAR data</kwd>
<kwd>machine learning</kwd>
<kwd>road safety</kwd>
<kwd>roadway vertical alignment</kwd>
<kwd>Northern America</kwd>
</kwd-group>
<funding-group>
<funding-statement>The study is supported by the NJDOT (FHWA-NJ-2017-007) and partially by Ozyegin University and partially by C2SMARTER, a Tier 1 UTC at New York University funded by the USDOT.</funding-statement>
</funding-group>
</article-meta>
</front>
<body>
<sec sec-type="level-A" id="introduction">
  <title>1. Introduction </title>
  <p>Roadway vertical alignment consists of grades connected by parabolic curves. Road elevation data are crucial in traffic safety analysis, roadway geometric design, fuel consumption estimation, and highway capacity analysis. Prior studies indicated that crash rates are notably higher on steep grade sections compared to level sections (<xref ref-type="bibr" rid="Glennon1987">Glennon, 1987</xref>; <xref ref-type="bibr" rid="Yu2014">Yu &amp; Abdel-Aty, 2014</xref>). <xref ref-type="bibr" rid="Hamdar2016">Hamdar et al. (2016)</xref> highlighted that driver behaviour is highly influenced by the challenges posed due to the changes in roadway geometric alignment. For instance, abrupt grade changes at crest curves can significantly restrict a driver's line of sight, adversely impacting available stopping sight distance and overall roadway safety. Vertical grades and curvature directly influence sight distance, operating speed, driver workload, and vehicle dynamics, making them central to both geometric design and crash prediction. The American Association of State Highway and Transportation Officials (AASHTO) and the Federal Highway Administration (FHWA) emphasize the role of grades and crest–sag curvature in determining safe stopping distances, speed consistency, and sight limitations on vertical curves (<xref ref-type="bibr" rid="Donnell2018">Donnell et al., 2018</xref>). Several empirical studies further support this, showing that combinations of horizontal–vertical curvature and steep grades significantly elevate crash risk and reduce speed harmony, particularly on rural two-lane highways (<xref ref-type="bibr" rid="Elvik2023">Elvik &amp; Haugvik, 2023</xref>;<xref ref-type="bibr" rid="Ryan2022">Ryan et al., 2022</xref>; <xref ref-type="bibr" rid="Bauer2013">Bauer &amp; Harwood, 2013</xref>; <xref ref-type="bibr" rid="Papadimitriou2019">Papadimitriou et al., 2019</xref>; <xref ref-type="bibr" rid="Kar2024">Kar et al., 2024</xref>).</p>
  <p>Road elevation profiles allow engineers to accurately identify steep grades that pose operational risks, particularly for heavy vehicles, assisting in targeted design interventions like crawler lanes or escape ramps. Moreover, accurate knowledge of road profiles supports safety analysis by helping identify segments with restricted visibility and elevated crash risk, enabling proactive measures such as advisory signage, speed limit adjustments, or geometric redesign. Beyond safety, vertical alignment also governs aspects such as drainage design, fuel consumption, ride comfort, and infrastructure maintenance, while precise elevation modelling facilitates 3D roadway coordination and driver visibility studies (<xref ref-type="bibr" rid="FHWA2019">FHWA, 2019</xref>).</p>
  <p>Moreover, recent flood events in the US underscore the value of roadway elevation profiles in identifying flood-prone segments. Heavy rains in San Antonio and the Tri-State region in the US flooded roadways in 2025, causing fatalities and roadway closures (<xref ref-type="bibr" rid="WTOP2025">WTOP News, 2025</xref>; <xref ref-type="bibr" rid="MySanAntonio2025">MySanAntonio, 2025</xref>; <xref ref-type="bibr" rid="NPR2025">National Public Radio, 2025</xref>). Accurate vertical alignment extraction, including identification of depressed grades and shallow slopes, can reveal areas prone to ponding or runoff overflow. Integrating these profiles into drainage planning helps agencies implement effective mitigation, such as regrading, culverts, or raised embankments, to improve flood resilience.</p>
  <p>Despite its importance, vertical alignment data remain difficult and expensive to obtain at scale. Historically, such information has resided within engineering plans and profile sheets, many of which predate digital storage and are available only in scanned or paper formats. Modern survey techniques such as Global Positioning System (GPS), Global Navigation Satellite System (GNSS), and mobile light detection and ranging (LiDAR) can yield highly precise 3-D elevation data, yet they require specialized survey vehicles, extensive field operations, and substantial financial resources, limiting their use to select corridors (<xref ref-type="bibr" rid="Gargoum2019">Gargoum &amp; El Basyouny, 2019</xref>). Moreover, unlike horizontal alignment, which is traceable through open geospatial databases or aerial imagery, vertical profiles cannot be easily inferred without access to elevation data, making large-scale network coverage a major challenge. This challenge is even more pronounced for older routes, where profile information may be either unavailable or outdated. As a result, estimating the parameters of roadway vertical alignment becomes essential.</p>
  <p>Advances in remote sensing and open-access LiDAR now offer a practical solution. The U.S. Geological Survey’s 3D Elevation Program (3DEP) provides nationwide LiDAR coverage with point clouds and digital elevation models available through The National Map, enabling researchers to derive elevation and slope information for most US roads at minimal cost (<xref ref-type="bibr" rid="USGS2025">USGS, 2025</xref>). Previous research demonstrates the potential of LiDAR for automated roadway geometry extraction and safety analysis (<xref ref-type="bibr" rid="Yang2024">Yang &amp; Das, 2024</xref>; <xref ref-type="bibr" rid="Gargoum2019">Gargoum &amp; El Basyouny, 2019</xref>; <xref ref-type="bibr" rid="Wang2025">Wang et al., 2025</xref>). Yet processing large datasets, filtering roadway points, and classifying tangent versus curved segments still require robust analytical approaches.</p>
  <p>Various datasets, such as the National Elevation Dataset from the US Geological Survey (USGS NED) (<xref ref-type="bibr" rid="Gesch2014">Gesch et al., 2014</xref>), Global Digital Elevation Model (GDEM) (<xref ref-type="bibr" rid="Tachikawa2011">Tachikawa et al., 2011</xref>), and LiDAR (<xref ref-type="bibr" rid="Reutebuch2005">Reutebuch et al., 2005</xref>) elevation datasets are readily available. The 3DEP from the USGS, which employs LiDAR point cloud data, has gathered extensive three-dimensional data across the US. This dataset contains over 12 trillion LiDAR point cloud records, encompassing data from more than 1,254 projects across the country (<xref ref-type="bibr" rid="USGS2025">USGS, 2025</xref>).</p>
  <p>Various techniques are available for collecting road elevation data, such as GPS, Enhanced GNSS, Inertial Navigation Systems (INS) coupled with GNSS, LiDAR (<xref ref-type="bibr" rid="Baass2005">Baass &amp; Vouland, 2005</xref>; <xref ref-type="bibr" rid="Easa2010">Easa &amp; Wang, 2010</xref>;<xref ref-type="bibr" rid="DiMascio2012">Di Mascio et al., 2012</xref>; <xref ref-type="bibr" rid="Higuera2017">Higuera de Frutos &amp; Castro, 2017</xref>; <xref ref-type="bibr" rid="Gargoum2018">Gargoum et al., 2018</xref>; <xref ref-type="bibr" rid="Liu2018">Liu et al., 2018</xref>; <xref ref-type="bibr" rid="Zhou2021">Zhou et al., 2021</xref>; <xref ref-type="bibr" rid="Shams2023">Shams et al., 2023</xref>; <xref ref-type="bibr" rid="Holgado-Barco2014">Holgado-Barco et al., 2014</xref>;<xref ref-type="bibr" rid="Yang2024">Yang &amp; Das, 2024</xref>), as discussed next in the literature review section. However, these methods may not be feasible due to the cost and effort required for their implementation, especially on a larger scale.</p>
  <p>Therefore, there is a need for estimating road elevation data indirectly from available sources, as done for road horizontal alignment (<xref ref-type="bibr" rid="Anil2010">Anil &amp; Natarajan, 2010</xref>; <xref ref-type="bibr" rid="Easa2007">Easa et al., 2007</xref>;<xref ref-type="bibr" rid="Imran2006">Imran et al., 2006</xref>; <xref ref-type="bibr" rid="Yun2005">Yun &amp; Sung, 2005</xref>; <xref ref-type="bibr" rid="Xu2016">Xu &amp; Wei, 2016</xref>; <xref ref-type="bibr" rid="Bartin2019">Bartin et al., 2019</xref>; <xref ref-type="bibr" rid="Bartin2022">Bartin et al., 2022</xref>; <xref ref-type="bibr" rid="Bartin2021">Bartin et al., 2021</xref>; <xref ref-type="bibr" rid="Bartin2023">Bartin et al., 2023</xref>; <xref ref-type="bibr" rid="Findley2012">Findley et al., 2012</xref>; <xref ref-type="bibr" rid="Luo2018">Luo et al., 2018</xref>). However, this topic has not been as extensively explored in the literature. Although various elevation data sources are available, there is a notable absence of methods for extracting roadway vertical alignment using these resources. The ones that use LiDAR data do not rely on replicable methods. In practice, many LiDAR-based studies rely on mobile mapping systems that are not freely available and are often limited to project-specific deployments. The need for advanced survey vehicles raises costs and lengthens data-collection and post-processing, which constrains scalability.</p>
  <p>To that end, the objective of this paper is to develop an Artificial Neural Network (ANN) based approach that can accurately, quickly, and affordably extract roadway vertical alignment information and determine its geometric properties using publicly available LiDAR data in the USGS repository (<xref ref-type="bibr" rid="USGS2025">USGS, 2025</xref>). However, because the ANN model requires large datasets of known vertical alignment data for training, and such data are not readily available at a large scale, the model was trained and tested using synthetically generated road vertical data. Once trained, the model was able to classify LiDAR points on a roadway as either part of a grade or a vertical curve, considering the surrounding LiDAR points. The developed ANN model was independently evaluated using the actual vertical data of Route 152, a state highway in NJ, and Route 299, a state highway in CA. Also, a case study was conducted on Route 83, a rural two-lane highway in NJ, where the model was applied to regenerate the speed profile.</p>
</sec>
<sec sec-type="level-A" id="literature-review">
  <title>2. Literature Review </title>
  <p>Extracting roadway alignment has been the focus of numerous studies over the years, yet horizontal alignment has been the primary focus alignment (<xref ref-type="bibr" rid="Anil2010">Anil &amp; Natarajan, 2010</xref>; <xref ref-type="bibr" rid="Easa2007">Easa et al., 2007</xref>;<xref ref-type="bibr" rid="Imran2006">Imran et al., 2006</xref>; <xref ref-type="bibr" rid="Yun2005">Yun &amp; Sung, 2005</xref>; <xref ref-type="bibr" rid="Xu2016">Xu &amp; Wei, 2016</xref>; <xref ref-type="bibr" rid="Bartin2019">Bartin et al., 2019</xref>; <xref ref-type="bibr" rid="Bartin2022">Bartin et al., 2022</xref>; <xref ref-type="bibr" rid="Bartin2021">Bartin et al., 2021</xref>; <xref ref-type="bibr" rid="Bartin2023">Bartin et al., 2023</xref>; <xref ref-type="bibr" rid="Findley2012">Findley et al., 2012</xref>; <xref ref-type="bibr" rid="Luo2018">Luo et al., 2018</xref>) Various data sources were utilized for extracting roadway horizontal alignment, ranging from satellite images (<xref ref-type="bibr" rid="Anil2010">Anil &amp; Natarajan, 2010</xref>; <xref ref-type="bibr" rid="Easa2007">Easa et al., 2007</xref>), GPS data (<xref ref-type="bibr" rid="Imran2006">Imran et al., 2006</xref>; <xref ref-type="bibr" rid="Yun2005">Yun &amp; Sung, 2005</xref>), Geographic Information System (GIS) maps (<xref ref-type="bibr" rid="Xu2016">Xu &amp; Wei, 2016</xref>); (<xref ref-type="bibr" rid="Bartin2019">Bartin et al., 2019</xref>; <xref ref-type="bibr" rid="Bartin2022">Bartin et al., 2022</xref>; <xref ref-type="bibr" rid="Bartin2021">Bartin et al., 2021</xref>; <xref ref-type="bibr" rid="Bartin2023">Bartin et al., 2023</xref>), and mobile LiDAR mapping (<xref ref-type="bibr" rid="Findley2012">Findley et al., 2012</xref>; <xref ref-type="bibr" rid="Luo2018">Luo et al., 2018</xref>).</p>
  <p>A limited number of studies focused on developing comprehensive and automated methods for extracting roadway vertical alignment. For example, <xref ref-type="bibr" rid="Baass2005">Baass &amp; Vouland, (2005)</xref> conducted a study on reconstructing vertical alignment using GPS data sources. They applied the rate of slope change between points to distinguish parabolic curves from the tangents of the vertical alignment. Initially, they used least squares approximation to fit tangents, followed by an iterative process to determine the vertical curves using least square approximations. The process required an initial value for the length of the vertical curve, which was obtained from the previously calculated tangent sections' initial and final grades. They validated the method by comparing it with exact design data and real GPS profile data from Quebec highways. To assess accuracy, they calculated the vertical distance from GPS source points and compared it to the result obtained from calculated alignments. The estimated average error was 15 cm, with a maximum error of 1.5 meters. While they applied some form of filtering to the GNSS data to address irregularities, specific details were not provided. It was acknowledged that factoring in device error would be necessary to measure the absolute error of the procedure.</p>
  <p><xref ref-type="bibr" rid="Easa2010">Easa &amp; Wang (2010)</xref> introduced an optimization model aimed at determining the parameters of continuous vertical alignments using GPS data. This model included multiple parabolic vertical curves and aimed to ideally fit the highway profile data through the application of the least squares method. The optimization process operated in two stages: single-curve optimization and multiple-curve optimization. Single-curve optimization employed estimated tangent parameters, derived from the controlling points defined by the operator, to approximate the length of each vertical curve. Conversely, multiple-curve optimization was applied to deduce the globally optimal parameters for both tangents and vertical curves. The model was evaluated using actual data from a 1,700-meter segment of a highway's vertical alignment. To validate the model's accuracy, the study compared the original altitude values with estimated altitudes. The average error observed was 3.8 centimeters.</p>
  <p><xref ref-type="bibr" rid="DiMascio2012">Di Mascio et al. (2012)</xref> utilized a GNSS receiver mounted on a vehicle. They employed the least-squares optimization principle to identify vertical curves and lines that represent the section of the road considered with the respective mobile base. The vertical curves were examined as circular components. As a final step, they fine-tuned the results of their method using the vertical curvature profile. <xref ref-type="bibr" rid="Higuera2017">Higuera de Frutos &amp; Castro (2017)</xref> developed an algorithm to reconstruct the vertical alignment of a road from the longitudinal slopes along its centerline using data from clinometers and GNSS receivers. The algorithm meticulously identified border points on the road's grade profile classified each sample point as a grade point, vertical curve point, or border point, and grouped similar points into segments. The analytical expressions for these segments were then calculated and integrated to formulate the road's vertical alignment. The efficacy of this method was validated through its application on five rural highways in Spain and the results demonstrated the algorithm's precision in recreating vertical alignments, with the results being more accurate in flat terrains compared to mountainous sections.</p>
  <p>Recent advancements in LiDAR technology have found applications in the transportation sector, with numerous studies using LiDAR data to extract road surface characteristics, estimate roadway alignments, and analyse road cross slopes. A brief overview of LiDAR technology is provided first, followed by a review of these studies.</p>
  <p>LiDAR operates by emitting laser pulses. As the laser pulses interact with and are reflected off objects on the Earth's surface, the LiDAR system captures the reflected signals, or returns. These returns are then utilized to generate a dense set of data points known as a “point cloud”, which represents the three-dimensional structure of the survey area. When a single laser pulse intersects various surfaces, it generates multiple reflections captured by the LiDAR sensor. These reflections are categorized as first returns, which represent the highest points, such as tree canopies or building tops, and subsequent returns, which represent lower surfaces, such as the ground beneath vegetation cover. This multi-return capability enables a detailed understanding of various landscape features.</p>
  <p>LiDAR data can be collected via mobile and airborne systems. Mobile LiDAR Systems (MLS), usually mounted on moving vehicles, are exceptional in capturing high-resolution data at street level. They are used for road and bridge inspections, utility mapping, urban planning, and asset management, with the granularity of data being so refined in some cases as to detect asphalt cracks. Typically, the accuracy of Mobile LiDAR systems ranges between 0.05 to 0.10 meters, contingent on system configurations and environmental conditions. They can collect dense cloud data points and provide a detailed representation of the survey area.</p>
  <p>Airborne LiDAR Systems (ALS), installed on an aircraft or a drone, cover vast areas effectively and generate digital terrain models (DTM), topographic mapping, construction of digital 3D city models, natural hazard assessment, and more. The accuracy of ALS data collected by aircraft can reach up to 10 centimeters, depending on the system and the conditions under which data are collected. On the other hand, LiDAR data collected by drones typically offer improved point density and precision due to their lower altitude operation. However, the point density of ALS may be lower compared to MLS due to the greater distance from the ground. Nonetheless, this density and accuracy are sufficient to discern road profile trajectories and estimate road grades.</p>
  <p><xref ref-type="bibr" rid="Gargoum2018">Gargoum et al. (2018)</xref> proposed a method to extract the vertical profile of highways from LiDAR data. This method involved three main stages: centerline generation, road surface creation and overlaying of the centerline, and profile generation using AutoCAD Civil 3D. The centerline was generated by defining points parallel to the road's centerline, overlaying it onto a created surface from the point cloud data, and then generating the highway profile along this centerline. This method was tested on three different highway segments in Alberta, Canada, and the extracted profiles were compared with profiles generated using GPS data and manual surveys. The results demonstrated remarkable precision, with grade differences between LiDAR and manual profiles as low as 0.025% to 0.15%, and a relative elevation error of only 4%. Furthermore, when compared to GPS data, the LiDAR profiles exhibited minimal grade differences, averaging 0.023% and 0.061% on different road segments.</p>
  <p><xref ref-type="bibr" rid="Liu2018">Liu et al. (2018)</xref> proposed a method that utilized the Digital Elevation Model (DEM), a nationwide open data source from the USGS and applied cubic smoothing splines to minimize the impact of noisy data and improve grade estimation accuracy. The selection of a key parameter (λ) in the spline method was discussed to balance smoothing noisy elevation data while retaining vertical fluctuations along the road. To validate the results, actual road grade data consisting of five highway segments and two local road segments, with a total length of 23.24 km in Atlanta, were used. The results demonstrated an average estimation error of 0.5 to 0.58 percent for local roads and 0.21 to 0.23 percent for highways.</p>
  <p><xref ref-type="bibr" rid="Zhou2021">Zhou et al. (2021)</xref> developed a method to extract highway alignments and construct 3D models using ALS data. This involved recognizing highway pavement points, extracting pavement boundaries and lane markings, and then reconstructing highway 3D models by minimizing an energy function. The method was tested on two ALS datasets from Sichuan, China. The extracted alignments achieved correctness rates of 90.67% and 99.25% and completeness rates of 87.60% and 99.55% within 10 cm and 15 cm errors, respectively. The root mean square error (RMSE) of the generated 3D models was 2.4 cm on pavement areas and 5.8 cm on hills and slopes.</p>
  <p>LiDAR technology has also proven to be an invaluable tool for obtaining detailed insights into road aspects such as roadway cross slope extraction. <xref ref-type="bibr" rid="Shams2023">Shams et al. (2023)</xref> conducted a study evaluating the effectiveness of airborne and mobile terrestrial LiDAR scanning systems in measuring pavement cross slopes. They employed end-to-end extraction and interval point extraction methods along cross-sections. The study, implemented on a 3.4-mile corridor along I-85 Business Loop in South Carolina, demonstrated LiDAR's accuracy in collecting pavement cross slopes, highlighting its suitability for large-scale applications and road surface drainage issues. <xref ref-type="bibr" rid="Holgado-Barco2014">Holgado-Barco et al. (2014)</xref> focused on automatically extracting geometric parameters from mobile LiDAR system datasets, with an emphasis on vertical road profiles and cross-sections. Using data from the Spanish highway A-52, the study employed segmentation and principal component analysis-based methods for processing. This approach led to a comprehensive characterization of road slopes and superelevations, showcasing LiDAR's effectiveness in road safety assessment and construction verification.</p>
  <p><xref ref-type="bibr" rid="Yang2024">Yang and Das (2024)</xref> developed an open-source program to extract horizontal and vertical alignment information for roadways, leveraging public data and open APIs. For vertical curves, the program analyses the vertical grade profile, identifying parabolic curves and tangents by fitting piecewise linear regression models. They extracted elevation data from the USGS 3DEP, which provides high-resolution 3D elevation data across the U.S. The elevation data from 3DEP were derived from LiDAR point cloud data available at different resolutions: 30m, 10m, and 1m. The segmentation and detection of vertical curves are optimized by addressing erratic elevation data points.</p>
  <p>In summary, previous studies in the extraction of road elevation data primarily focused on using GPS and GNSS data from vehicles equipped with advanced technologies. There are a few studies that used LiDAR data; however, the underlying datasets were often project-specific mobile or airborne LiDAR acquisitions, while relatively fewer studies leveraged publicly available, large-coverage datasets such as USGS 3DEP. In addition, the necessity of these specially equipped surveying vehicles for data collection limits their methods’ applicability to a wider scale of roadways due to significant costs and extended data collection periods.</p>
  <p>Recognizing these constraints, this study proposes an innovative approach utilizing open-access aerial LiDAR point cloud data, offering a cost-effective and efficient solution for extracting precise roadway elevation data. The ALS data stand out as an extremely valuable resource for road grade estimation due to their easy accessibility, free availability, and nationwide coverage across the US. Despite these advantages, few studies have comprehensively addressed the detailed method of generating high-resolution road grade information from LiDAR data. This study attempts to fill this gap in the literature.</p>
</sec>
<sec sec-type="level-A" id="methodology">
  <title>3. Methodology </title>
  <p>The methodology used in this study is outlined in <xref ref-type="fig" rid="fig1">Figure 1</xref> and extends a previously developed ANN-based method for extracting roadway horizontal alignment data, as described in <xref ref-type="bibr" rid="Bartin2021">Bartin et al. (2021)</xref> and (<xref ref-type="bibr" rid="Bartin2023">Bartin et al., 2023</xref>). In that work, an ANN model was developed to identify horizontal tangent and curved segments using publicly available roadway GIS data. In the current study, the same ANN approach was applied to LiDAR data, which contain a significantly larger number of data points and are inherently much noisier.</p>
  <p>To estimate the vertical alignment of a given roadway, the first step was to identify the relevant LiDAR point cloud data. The LiDAR point cloud datasets used in this study were obtained from USGS (<xref ref-type="bibr" rid="USGS2025">USGS, 2025</xref>), which provides extensive coverage across the US. Each LiDAR point cloud consists of latitude, longitude, and elevation information. According to the USGS, the vertical accuracy of LiDAR data is approximately 10 centimeters (~4 inches) which is suitable for extracting roadway vertical alignment.</p>
  <fig id="fig1">
<object-id pub-id-type="publisher-id"></object-id>
<label>Figure 1</label>
<caption>
<title>Workflow of the developed processing</title>
</caption>
<graphic xlink:href="e000134-Figure1.png" />
</fig>
  <p>In the next step, the LiDAR data specific to the selected roadway were extracted. The following subsection presents the details of the two selected roadways for this study.</p>
  <sec sec-type="level-B" id="study-roadway">
    <title>3.1 Study roadway</title>
  <p>The proposed method was evaluated using the actual vertical alignment data of Route 152, a state highway in Atlantic County, NJ, and Route 299 in Lassen County, CA. The portion of Route 299 starts at (-120.98672, 41.16925) and ends at (-120.96932, 41.17645), and is 1.03 miles in length as depicted in <xref ref-type="fig" rid="fig2">Figure 2</xref>a. The portion of Route 152 included for the analysis starts at (-74.58808, 39.31803) and ends at (-74.53119, 39.31595), and is 3.18 miles, as shown in <xref ref-type="fig" rid="fig2">Figure 2</xref>b. The vertical alignment consists of 8 curved and 9 tangent segments for Route 299, and 18 curved and 18 tangent segments for Route 152. The selection of these specific portions was due to the availability of the vertical alignment data provided by the New Jersey Department of Transportation (NJDOT) and California Department of Transportation (Caltrans). <xref ref-type="fig" rid="fig2">Figure 2</xref>c demonstrates the USGS LiDAR data in the vicinity of the initial segment of Route 152. The elevation can be recognized based on the color scheme, reflecting elevation changes between the road surface and its surroundings.</p>  
    <fig id="fig2">
<object-id pub-id-type="publisher-id"></object-id>
<label>Figure 2</label>
<caption>
<title>(a) Satellite image of the Route 299. (b) Satellite image of Route 152 (c) Example of Route 152 USGS LIDAR data</title>
</caption>
<graphic xlink:href="e000134-Figure2.png" />
</fig>
  </sec>
  <sec sec-type="level-B" id="data-extraction">
    <title>3.2 Data extraction </title>
    <p>This section describes the process of extracting elevation values from LiDAR point cloud data obtained from the USGS data repository. The procedure, illustrated in <xref ref-type="fig" rid="fig3">Figure 3</xref>, was conducted using QGIS software. The aerial LiDAR point cloud data were obtained from the USGS as separate files in LAZ format, which is a compressed version of the standard LiDAR point cloud file format. Each LAZ file corresponds to a grid tile of approximately 0.95 by 0.95 miles. The file size was approximately 60 MB for Route 152 and 40 MB for Route 299. The total file size of the files covering Route 152 was approximately 420 Mb, while the corresponding files for Route 299 totaled about 160 Mb. These files contained point cloud data for the entire geographic area encompassed by the tiles.</p>
    <p>The procedure used the GIS roadway centerline shapefile of Route 152, publicly available on the NJDOT (<xref ref-type="bibr" rid="NJDOT2025">NJDOT, 2025</xref>) website, and the corresponding roadway centerline shapefile for Route 299, publicly available through Caltrans (<xref ref-type="bibr" rid="Caltrans2026">Caltrans, 2026</xref>), to extract point cloud data exclusively associated with the two study roadways. A buffer width ∆w = 1 meter around the road centerline was used for this purpose. As depicted in <xref ref-type="fig" rid="fig3">Figure 3</xref>, the LiDAR points closest to the roadway centerline were then extracted from the buffered point cloud data using QGIS. This process then selected sample points at fixed intervals, ∆f, along the roadway centerline. The choice of ∆f significantly influences the accuracy and efficiency of the elevation extraction process. If ∆f is too long, it may fail to capture essential details of the road elevation profile. Conversely, smaller intervals could lead to increased computational effort. Based on a series of sensitivity analyses, as explained in Section 3.5, it was determined that a 5-meter sampling interval was found to provide an effective balance between accurately representing the vertical alignment and managing the computational effort. A similar sampling strategy was also used by <xref ref-type="bibr" rid="Liu2018">Liu et al. (2018)</xref>, who selected a 10-meter sampling interval after conducting sensitivity analyses for elevation extraction along roadway centerlines. They noted that excessively short sampling intervals may cause consecutive points to fall within the same DEM grid cell, producing duplicate elevation values, increasing noise in the elevation profile, and adding unnecessary computational effort.</p>
    <fig id="fig3">
<object-id pub-id-type="publisher-id"></object-id>
<label>Figure 3</label>
<caption>
<title>LiDAR data extraction process</title>
</caption>
<graphic xlink:href="e000134-Figure3.png" />
</fig>
  </sec>
  <sec sec-type="level-B" id="overview-of-the-ann-model">
    <title>3.3 Overview of the ANN model </title>
    <p>The general overview of the ANN model is presented in <xref ref-type="fig" rid="fig4">Figure 4</xref>. The input vector for the ANN model included the elevation (<italic>z<sub>i</sub></italic>) of the target point <italic>i</italic>, as well as those of its neighbouring vertices. Considering only the elevation of a single LiDAR point, without accounting for its surroundings, is insufficient to accurately determine whether the point belongs to a vertical curve (labelled as 1) or a roadway grade (labelled as 0). Therefore, to improve prediction accuracy, the input vector also incorporated elevation information from the surrounding vertices within a predetermined buffer distance (&#x394;<italic>b</italic>), as shown in <xref ref-type="fig" rid="fig4">Figure 4</xref>.</p>
    <fig id="fig4">
<object-id pub-id-type="publisher-id"></object-id>
<label>Figure 4</label>
<caption>
<title>Details of the input vector to the ANN model</title>
</caption>
<graphic xlink:href="e000134-Figure4.png" />
</fig>
    <p>The limitation of the proposed approach was the need for a substantial amount of real-world alignment data to ensure the ANN model's effectiveness in segmenting different types of roadway alignments. However, as mentioned earlier, obtaining actual road alignment data is challenging. To overcome this limitation, this study utilized synthetically generated random vertical road alignments containing curved and tangent segments. As presented in the next subsection, the synthetic dataset was generated by varying road grades, curve lengths, and curvature transitions to represent realistic combinations of tangents, crest and sag curves. This ensured that the model was trained with diverse geometric conditions and could develop generalized relationships between vertical alignment features and their geometric attributes.</p>
    <p>The accurately labelled points of the synthetically generated roads were used to train the ANN model. The following subsection presents the generation of synthetic vertical alignment data.</p>
  </sec>
  <sec sec-type="level-B" id="generating-synthetic-data">
    <title>3.4 Generating synthetic data </title>
    <p>The process of generating a synthetic vertical alignment dataset was conducted by a computer code developed in the C programming language. The process can be described briefly as follows. Each generated road started from the origin (0, 0). Each roadway was assumed to contain a specific number of distinct segment types. The type of the first segment, i.e. curve or tangent, was determined randomly. The initial and final grades were randomly assigned between zero and a maximum allowable vertical grade of ±9 percent. The lengths of the initial and final tangent segments were randomly assigned between 150 and 750 feet. Similarly, the curve lengths were randomly assigned between 150 feet and 400 feet. Elevations at any given point along these segments could then be calculated using the fundamental vertical alignment equations (<xref ref-type="bibr" rid="Mannering2020">Mannering &amp; Washburn, 2020</xref>). An input vector for each point was then generated, as shown in <xref ref-type="fig" rid="fig4">Figure 4</xref>, containing the elevation of (<italic>z<sub>i</sub></italic>) of the target point <italic>i</italic> and its neighbouring points within a given buffer distance (&#x394;<italic>b</italic>), labelled with the segment type i.e. curved (1) or tangent (0). These vectors were then rescaled by standardization to reduce the size of the search space. Using this process, a total of 40,000 roads were generated, and 20 percent of these points were randomly selected to ensure stochasticity in using the training data for the ANN model.</p>
  </sec>
  <sec sec-type="level-B" id="sensitivity-analysis-for-ann-model">
    <title>3.5 Sensitivity Analysis for ANN Model </title>
    <p>The training of the ANN model was performed using the synthetically generated vertical alignment dataset described above. The overall dataset included approximately 1,800,000 data points. 80 percent of this dataset was used for training and 20 percent for tuning the model hyperparameters and testing the model.</p>
    <p>A series of sensitivity analyses was conducted to evaluate different combinations of ANN model architectures, sampling interval values (&#x394;<italic>f</italic>), and the distance range used to determine which neighbouring vertices were included in the input vector (&#x394;<italic>b</italic>). The models were developed using the Keras library within the TensorFlow package in Python. Rectified Linear Unit (ReLU) was used as the activation function, except at the output node where a sigmoid activation function was used. Each model was trained for 50 epochs. Accuracy results of the full sensitivity analysis are summarized in <xref ref-type="fig" rid="fig5">Figure 5</xref>.</p>
    <fig id="fig5">
<object-id pub-id-type="publisher-id"></object-id>
<label>Figure 5</label>
<caption>
<title>Sensitivity analysis</title>
</caption>
<graphic xlink:href="e000134-Figure5.png" />
</fig>
    <p>As shown in <xref ref-type="fig" rid="fig5">Figure 5</xref>, multiple two hidden-layer ANN structures were tested across combinations of &#x394;<italic>f</italic> = 1, 5, and 10 m and &#x394;<italic>b</italic> = 50, 100, 150, 200, and 250 m. Across all tested scenarios, the highest validation accuracy was achieved at &#x394;<italic>f</italic> = 1 m, reaching 97.18% at &#x394;<italic>b</italic> = 150 m, while &#x394;<italic>f</italic> = 5 m yielded a validation accuracy of 96.34% at &#x394;<italic>b</italic> = 150 m. Thus, the improvement from &#x394;<italic>f</italic> = 1 m relative to Δf = 5 m was approximately 0.84 percentage points at best. In contrast, reducing the sampling interval from &#x394;<italic>f</italic> = 5 m to &#x394;<italic>f</italic> = 1 m increased the number of sampled points and their neighbouring vertices by approximately five times. As a result, the overall data handling and training burden scaled roughly with the product of these effects (approximately 25 times). Given the already large training scale used in this study, the marginal accuracy gain associated with &#x394;<italic>f</italic> = 1 m did not justify the substantially higher computational cost and reduced scalability. Conversely, &#x394;<italic>f</italic> = 10 m reduced computational requirements but decreased validation accuracy and increased the risk of under- sampling short vertical transitions. Based on the sensitivity analysis results and the scalability objective of this study, &#x394;<italic>f</italic> = 5 m and &#x394;<italic>b</italic> = 150 m (approximately 500 feet) were selected as a practical and effective compromise.</p>
    <p>Following the tests with various ANN architectures (<xref ref-type="fig" rid="fig5">Figure 5</xref>), the final model was selected as an <italic>n</italic>-128-64-1 structure, consisting of two hidden layers, and an output layer of one node, where n denotes the size of the input vector. In our analysis, presented in the next section, <italic>n</italic> = 61 for &#x394;<italic>f</italic> = 5 m and &#x394;<italic>b</italic> = 150 m.</p>
  </sec>
</sec>
<sec sec-type="level-A" id="analysis-results">
  <title>4. Analysis results </title>
  <p>The selected ANN model was evaluated independently by using the aerial LiDAR data extracted along Route 152 and Route 299 centerlines. The following subsections present the results for the two study roadways separately.</p>
  <sec sec-type="level-B" id="analysis-of-route-152">
    <title>4.1 Analysis of Route 152 </title>
    <p>The results showed that the ANN model correctly predicted 87.5 percent of the LiDAR points’ labels for Route 152. Further investigation revealed that 82.1 percent of the incorrectly predicted labels were on tangent segments, and the remaining were on curved segments. Also, 88.0 percent of the incorrectly labelled LiDAR points were located in the transition regions between curved and tangent segments. However, the remaining 12 percent corresponded to a total of 14 points, belonging to two clusters, one with six and the other with eight contiguous points. These two clusters were predicted as curved segments. <xref ref-type="fig" rid="fig6">Figure 6</xref> demonstrates these two cases.</p>
    <p>In the left plot, all points belonged to a tangent segment based on the actual vertical alignment data, and the red color indicates the points misidentified as belonging to a curved segment (segment number 14 of the estimated data in <xref ref-type="table" rid="tab1">Table 1</xref>).</p>
    <fig id="fig6">
<object-id pub-id-type="publisher-id"></object-id>
<label>Figure 6</label>
<caption>
<title>Tangent segments misidentified as curved segments</title>
<p>Note: Blue and orange points indicate points of tangent segment and curved segments, and the red color indicates misidentified tangent points as curved.</p>
</caption>
<graphic xlink:href="e000134-Figure6.png" />
</fig>
    <p>In the right plot, blue and orange points belonged to a tangent and a curved segment, respectively, according to the actual data. However, as seen in the actual data, this 200-feet long curve (segment number 28 of actual data in <xref ref-type="table" rid="tab1">Table 1</xref>) has an initial grade of -0.49 and a final grade of -0.40, which made it indiscernible. The model misidentified a part of the tangent segment after this curve as a separate curved segment. Although a part of this misidentified segment overlaps with the curve before, the remaining portion extends into the following tangent segment. Regardless, it was assumed that the proposed method could not properly detect segment number 28.</p>
    <p>Using the predicted labels of LiDAR points, the estimated vertical alignment was generated manually. For example, if the predicted labels indicated a tangent segment, a simple linear regression was conducted using these points, and the grade of a tangent segment was estimated accordingly. It should be noted that although this approach was feasible for a single roadway, an automated process would be more effective if multiple roadways were to be analyzed.</p>
    <p>Notably, a key advantage of this approach is its reliance solely on the labelled LiDAR data points, making it easily replicable for other roadway datasets through the application of fundamental vertical alignment equations.</p>
    <p>Details of the estimated vertical alignment are presented in <xref ref-type="table" rid="tab1">Table 1</xref>. The total actual tangent and curved lengths were 11,457.5 feet and 5,365 feet, respectively, while the estimated total tangent and curved lengths were 10,477 feet and 6,345.5 feet, respectively. Overall, the proposed method detected all segments except one curve (segment number 28 of actual data in <xref ref-type="table" rid="tab1">Table 1</xref>), and one tangent segment was misidentified as a curved segment (segment number 14 of the estimated data in <xref ref-type="table" rid="tab1">Table 1</xref>).</p>
<table-wrap id="tab1">
<object-id pub-id-type="publisher-id"></object-id>
<label>Table 1</label>
<caption>
<title>Estimated Vertical Alignment of Route 152</title>
</caption>
<table>
<thead>
          <tr>
            <th style="background-color:rgb(204,204,204)" align="left" colspan="5">Actual</th>
            <th style="background-color:rgb(204,204,204)" align="center" colspan="5">Estimated</th>
          </tr>
          <tr>
            <th style="background-color:rgb(204,204,204)" align="left">No</th>
            <th style="background-color:rgb(204,204,204)" align="center">Start</th>
            <th style="background-color:rgb(204,204,204)" align="center">End</th>
            <th style="background-color:rgb(204,204,204)" align="center">Type‡</th>
            <th style="background-color:rgb(204,204,204)" align="center">Grade (%)</th>
            <th style="background-color:rgb(204,204,204)" align="center">No</th>
            <th style="background-color:rgb(204,204,204)" align="center">Start</th>
            <th style="background-color:rgb(204,204,204)" align="center">End</th>
            <th style="background-color:rgb(204,204,204)" align="center">Type</th>
            <th style="background-color:rgb(204,204,204)" align="center">Grade (%)</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">1</td>
            <td align="center">10+00</td>
            <td align="center">12+40</td>
            <td align="center">T</td>
            <td align="right">-0.420</td>
            <td align="right">1</td>
            <td align="center">10+00</td>
            <td align="center">12+35</td>
            <td align="center">T</td>
            <td align="right">-0.39</td>
          </tr>
          <tr>
            <td align="left">2</td>
            <td align="center">12+40</td>
            <td align="center">14+40</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">2</td>
            <td align="center">12+35</td>
            <td align="center">14+67</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">3</td>
            <td align="center">14+40</td>
            <td align="center">18+50</td>
            <td align="center">T</td>
            <td align="right">1.020</td>
            <td align="right">3</td>
            <td align="center">14+67</td>
            <td align="center">18+45</td>
            <td align="center">T</td>
            <td align="right">1.07</td>
          </tr>
          <tr>
            <td align="left">4</td>
            <td align="center">18+50</td>
            <td align="center">21+00</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">4</td>
            <td align="center">18+45</td>
            <td align="center">20+40</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">5</td>
            <td align="center">21+00</td>
            <td align="center">25+50</td>
            <td align="center">T</td>
            <td align="right">-0.530</td>
            <td align="right">5</td>
            <td align="center">20+40</td>
            <td align="center">24+76</td>
            <td align="center">T</td>
            <td align="right">-0.59</td>
          </tr>
          <tr>
            <td align="left">6</td>
            <td align="center">25+50</td>
            <td align="center">27+50</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">6</td>
            <td align="center">24+76</td>
            <td align="center">28+45</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">7</td>
            <td align="center">27+50</td>
            <td align="center">33+50</td>
            <td align="center">T</td>
            <td align="right">0.530</td>
            <td align="right">7</td>
            <td align="center">28+45</td>
            <td align="center">32+55</td>
            <td align="center">T</td>
            <td align="right">0.51</td>
          </tr>
          <tr>
            <td align="left">8</td>
            <td align="center">33+50</td>
            <td align="center">35+50</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">8</td>
            <td align="center">32+55</td>
            <td align="center">35+67</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">9</td>
            <td align="center">35+50</td>
            <td align="center">42+00</td>
            <td align="center">T</td>
            <td align="right">-0.500</td>
            <td align="right">9</td>
            <td align="center">35+67</td>
            <td align="center">41+40</td>
            <td align="center">T</td>
            <td align="right">-0.51</td>
          </tr>
          <tr>
            <td align="left">10</td>
            <td align="center">42+00</td>
            <td align="center">44+00</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">10</td>
            <td align="center">41+40</td>
            <td align="center">43+70</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">11</td>
            <td align="center">44+00</td>
            <td align="center">49+00</td>
            <td align="center">T</td>
            <td align="right">0.500</td>
            <td align="right">11</td>
            <td align="center">43+70</td>
            <td align="center">48+45</td>
            <td align="center">T</td>
            <td align="right">0.42</td>
          </tr>
          <tr>
            <td align="left">12</td>
            <td align="center">49+00</td>
            <td align="center">51+00</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">12</td>
            <td align="center">48+45</td>
            <td align="center">50+60</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">&#x00A0;</td>
            <td align="center">&#x00A0;</td>
            <td align="center">&#x00A0;</td>
            <td align="center">&#x00A0;</td>
            <td align="center">&#x00A0;</td>
            <td align="right">13</td>
            <td align="center">50+60</td>
            <td align="center">52+90</td>
            <td align="center">T</td>
            <td align="right">-0.29</td>
          </tr>
          <tr>
            <td align="left">&#x00A0;</td>
            <td align="center">&#x00A0;</td>
            <td align="center">&#x00A0;</td>
            <td align="center">&#x00A0;</td>
            <td align="center">&#x00A0;</td>
            <td align="right">14†</td>
            <td align="center">52+90</td>
            <td align="center">53+90</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">13</td>
            <td align="center">51+00</td>
            <td align="center">56+00</td>
            <td align="center">T</td>
            <td align="right">-0.500</td>
            <td align="right">15</td>
            <td align="center">53+90</td>
            <td align="center">55+35</td>
            <td align="center">T</td>
            <td align="right">-0.76</td>
          </tr>
          <tr>
            <td align="left">14</td>
            <td align="center">56+00</td>
            <td align="center">58+00</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">16</td>
            <td align="center">55+35</td>
            <td align="center">58+48</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">15</td>
            <td align="center">58+00</td>
            <td align="center">65+00</td>
            <td align="center">T</td>
            <td align="right">0.500</td>
            <td align="right">17</td>
            <td align="center">58+48</td>
            <td align="center">64+87</td>
            <td align="center">T</td>
            <td align="right">0.43</td>
          </tr>
          <tr>
            <td align="left">16</td>
            <td align="center">65+00</td>
            <td align="center">67+00</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">18</td>
            <td align="center">64+87</td>
            <td align="center">66+85</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">17</td>
            <td align="center">67+00</td>
            <td align="center">74+50</td>
            <td align="center">T</td>
            <td align="right">-0.500</td>
            <td align="right">19</td>
            <td align="center">66+85</td>
            <td align="center">74+87</td>
            <td align="center">T</td>
            <td align="right">-0.47</td>
          </tr>
          <tr>
            <td align="left">18</td>
            <td align="center">74+50</td>
            <td align="center">80+50</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">20</td>
            <td align="center">74+87</td>
            <td align="center">80+14</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">19</td>
            <td align="center">80+50</td>
            <td align="center">89+00</td>
            <td align="center">T</td>
            <td align="right">4.000</td>
            <td align="right">21</td>
            <td align="center">80+14</td>
            <td align="center">88+84</td>
            <td align="center">T</td>
            <td align="right">4.01</td>
          </tr>
          <tr>
            <td align="left">20</td>
            <td align="center">89+00</td>
            <td align="center">102+00</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">22</td>
            <td align="center">88+84</td>
            <td align="center">101+95</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">21</td>
            <td align="center">102+00</td>
            <td align="center">110+00</td>
            <td align="center">T</td>
            <td align="right">-4.000</td>
            <td align="right">23</td>
            <td align="center">101+95</td>
            <td align="center">110+30</td>
            <td align="center">T</td>
            <td align="right">-4.01</td>
          </tr>
          <tr>
            <td align="left">22</td>
            <td align="center">110+00</td>
            <td align="center">114+00</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">24</td>
            <td align="center">110+30</td>
            <td align="center">113+87</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">23</td>
            <td align="center">114+00</td>
            <td align="center">120+00</td>
            <td align="center">T</td>
            <td align="right">-0.500</td>
            <td align="right">25</td>
            <td align="center">113+87</td>
            <td align="center">119+00</td>
            <td align="center">T</td>
            <td align="right">-0.52</td>
          </tr>
          <tr>
            <td align="left">24</td>
            <td align="center">120+00</td>
            <td align="center">122+00</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">26</td>
            <td align="center">119+00</td>
            <td align="center">122+28</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">25</td>
            <td align="center">122+00</td>
            <td align="center">136+50</td>
            <td align="center">T</td>
            <td align="right">0.400</td>
            <td align="right">27</td>
            <td align="center">122+28</td>
            <td align="center">135+35</td>
            <td align="center">T</td>
            <td align="right">0.39</td>
          </tr>
          <tr>
            <td align="left">26</td>
            <td align="center">136+50</td>
            <td align="center">138+50</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">28</td>
            <td align="center">135+35</td>
            <td align="center">139+65</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">27</td>
            <td align="center">138+50</td>
            <td align="center">141+00</td>
            <td align="center">T</td>
            <td align="right">-0.490</td>
            <td align="right">29</td>
            <td align="center">139+65</td>
            <td align="center">142+14</td>
            <td align="center">T</td>
            <td align="right">-0.53</td>
          </tr>
          <tr>
            <td align="left">28*</td>
            <td align="center">141+00</td>
            <td align="center">143+00</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">30</td>
            <td align="center">142+14</td>
            <td align="center">144+10</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">29</td>
            <td align="center">143+00</td>
            <td align="center">148+00</td>
            <td align="center">T</td>
            <td align="right">-0.400</td>
            <td align="right">31</td>
            <td align="center">144+10</td>
            <td align="center">147+20</td>
            <td align="center">T</td>
            <td align="right">-0.40</td>
          </tr>
          <tr>
            <td align="left">30</td>
            <td align="center">148+00</td>
            <td align="center">150+00</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">32</td>
            <td align="center">147+20</td>
            <td align="center">150+50</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">31</td>
            <td align="center">150+00</td>
            <td align="center">156+00</td>
            <td align="center">T</td>
            <td align="right">0.420</td>
            <td align="right">33</td>
            <td align="center">150+50</td>
            <td align="center">155+40</td>
            <td align="center">T</td>
            <td align="right">0.47</td>
          </tr>
          <tr>
            <td align="left">32</td>
            <td align="center">156+00</td>
            <td align="center">158+00</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">34</td>
            <td align="center">155+40</td>
            <td align="center">158+70</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">33</td>
            <td align="center">158+00</td>
            <td align="center">169+00</td>
            <td align="center">T</td>
            <td align="right">-0.400</td>
            <td align="right">35</td>
            <td align="center">158+70</td>
            <td align="center">169+05</td>
            <td align="center">T</td>
            <td align="right">-0.40</td>
          </tr>
          <tr>
            <td align="left">34</td>
            <td align="center">169+00</td>
            <td align="center">171+00</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">36</td>
            <td align="center">169+05</td>
            <td align="center">171+00</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">35</td>
            <td align="center">171+00</td>
            <td align="center">176+07.5</td>
            <td align="center">T</td>
            <td align="right">0.394</td>
            <td align="right">37</td>
            <td align="center">170+00</td>
            <td align="center">176+25</td>
            <td align="center">T</td>
            <td align="right">0.40</td>
          </tr>
          <tr>
            <td align="left">36</td>
            <td align="center">176+07.5</td>
            <td align="center">178+22.5</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">38</td>
            <td align="center">176+25</td>
            <td align="center">178+22.5</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
        </tbody>
      </table>
      <table-wrap-foot>
    <p>‡T: tangent, C: curved,*Curved segment not detected, †Tangent identified as curved segment</p>
      </table-wrap-foot>
    </table-wrap>
    <p>However, being able to detect the type of segment should not be used as a decisive evaluation metric as these measures only the existence of, not how much, the overlap between the estimated and actual segments (<xref ref-type="bibr" rid="Bartin2021">Bartin et al., 2021</xref>; <xref ref-type="bibr" rid="Bartin2023">Bartin et al., 2023</xref>). Instead, one should measure the ratio of overlap between the estimated curved segments’ lengths and those of the actual ones. Doing so revealed that the overlap ratio of the estimated curve lengths with the actual ones was 92.5 percent, and the same ratio for tangent segments was 87.9 percent. Furthermore, the total undetected lengths of curved and tangent segments were 402.5 feet and 1,383 feet respectively. These corresponded to on average 22.4 feet and 76.8 feet error per curved and tangent segment, respectively. These statistics indicated that the proposed method overpredicted the number of curved points. This can be attributed to the inherent noise in the LiDAR data, as evidenced in <xref ref-type="fig" rid="fig6">Figure 6</xref>.</p>
    <fig id="fig7">
<object-id pub-id-type="publisher-id"></object-id>
<label>Figure 7</label>
<caption>
<title>Actual versus Estimated Vertical Alignment of Route 152</title>
</caption>
<graphic xlink:href="e000134-Figure7.png" />
</fig>
    <p><xref ref-type="fig" rid="fig7">Figure 7</xref> shows the visual comparison of the actual roadway alignment of Route 152 compared to the one estimated by the proposed method. It is worth noting that the start elevation of the LiDAR data was fixed to the actual starting elevation of Route 152 for comparison purposes, since LiDAR only shows the relative elevation and not the actual one.</p>
    <p>As shown in <xref ref-type="fig" rid="fig7">Figure 7</xref>, the estimated vertical alignment demonstrates an overall acceptable fit with the actual profile; however, an overestimation of the curve length for segment 6 in <xref ref-type="table" rid="tab1">Table 1</xref> by 169 feet caused the subsequent portion of the estimated alignment to deviate from the actual alignment. Despite this localized accumulation effect, the estimated grades remained accurate, with a mean absolute error of 0.042 percent relative to the actual values, ranging from zero to 0.26 percent.</p>
  </sec>
  <sec sec-type="level-B" id="analysis-of-route-299">
    <title>4.2 Analysis of Route 299</title>
    <p>For Route 299, the ANN model correctly predicted 85.93 percent of the LiDAR points’ labels. Among the incorrectly predicted labels, 19.15 percent corresponded to LiDAR points located on tangent segments, while the remainder were on curved segments. Notably, nearly all of the mislabeled LiDAR points occurred within the transition regions between tangent and curved segments. Details of the estimated vertical alignment are presented in <xref ref-type="table" rid="tab2">Table 2</xref>, and the model detected all tangent and curved segments along Route 299; however, slight offsets in the predicted transition points between tangents and curves led to overestimation or underestimation of the lengths of the adjacent tangent and curve segments. The total actual tangent and curved lengths were 2,141 feet and 3,301 feet, respectively, while the estimated total tangent and curved lengths were 2,522 feet and 2,920 feet, respectively. The overlap between the actual and estimated segment types along the roadway was 87.2 percent. The overlap ratio of the estimated curve lengths with the actual ones was 83.7 percent, and the corresponding ratio for tangent segments was 92.7 percent. Furthermore, the total undetected lengths of curved and tangent segments were 538 feet and 157 feet, respectively, which corresponded to an average error of 67.3 feet per curved segment and 17.4 feet per tangent segment. Overall, these findings suggest that the proposed method tended to underestimate the extent of curved segments, which may be attributed to the relatively small grade differences across several vertical curves in Route 299, causing portions of curves to be misidentified as tangent, particularly near transition regions.</p>
<table-wrap id="tab2">
<object-id pub-id-type="publisher-id"></object-id>
<label>Table 2</label>
<caption>
<title>Estimated Vertical Alignment of Route 299</title>
</caption>
<table>
<thead>
          <tr>
            <th style="background-color:rgb(204,204,204)" align="left" colspan="5">Actual</th>
            <th style="background-color:rgb(204,204,204)" align="center" colspan="5">Estimated</th>
          </tr>
          <tr>
            <th style="background-color:rgb(204,204,204)" align="left">No</th>
            <th style="background-color:rgb(204,204,204)" align="center">Start</th>
            <th style="background-color:rgb(204,204,204)" align="center">End</th>
            <th style="background-color:rgb(204,204,204)" align="center">Type‡</th>
            <th style="background-color:rgb(204,204,204)" align="center">Grade (%)</th>
            <th style="background-color:rgb(204,204,204)" align="center">No</th>
            <th style="background-color:rgb(204,204,204)" align="center">Start</th>
            <th style="background-color:rgb(204,204,204)" align="center">End</th>
            <th style="background-color:rgb(204,204,204)" align="center">Type</th>
            <th style="background-color:rgb(204,204,204)" align="center">Grade (%)</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">1</td>
            <td align="center">1237+58</td>
            <td align="center">1239+83</td>
            <td align="center">T</td>
            <td align="right">0.71</td>
            <td align="right">1</td>
            <td align="center">1237+58</td>
            <td align="center">1240+52</td>
            <td align="center">T</td>
            <td align="right">0.77</td>
          </tr>
          <tr>
            <td align="left">2</td>
            <td align="center">1239+83</td>
            <td align="center">1244+33</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">2</td>
            <td align="center">1240+52</td>
            <td align="center">1244+14</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">3</td>
            <td align="center">1244+33</td>
            <td align="center">1247+15</td>
            <td align="center">T</td>
            <td align="right">-0.48</td>
            <td align="right">3</td>
            <td align="center">1244+14</td>
            <td align="center">1247+58</td>
            <td align="center">T</td>
            <td align="right">-0.64</td>
          </tr>
          <tr>
            <td align="left">4</td>
            <td align="center">1247+15</td>
            <td align="center">1250+55</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">4</td>
            <td align="center">1247+58</td>
            <td align="center">1250+86</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">5</td>
            <td align="center">1250+55</td>
            <td align="center">1252+33</td>
            <td align="center">T</td>
            <td align="right">-2.12</td>
            <td align="right">5</td>
            <td align="center">1250+86</td>
            <td align="center">1252+83</td>
            <td align="center">T</td>
            <td align="right">-2.32</td>
          </tr>
          <tr>
            <td align="left">6</td>
            <td align="center">1252+33</td>
            <td align="center">1255+54</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">6</td>
            <td align="center">1252+83</td>
            <td align="center">1255+62</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">7</td>
            <td align="center">1255+54</td>
            <td align="center">1257+81</td>
            <td align="center">T</td>
            <td align="right">-0.13</td>
            <td align="right">7</td>
            <td align="center">1255+62</td>
            <td align="center">1258+24</td>
            <td align="center">T</td>
            <td align="right">-0.075</td>
          </tr>
          <tr>
            <td align="left">8</td>
            <td align="center">1257+81</td>
            <td align="center">1259+81</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">8</td>
            <td align="center">1258+24</td>
            <td align="center">1259+88</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">9</td>
            <td align="center">1259+81</td>
            <td align="center">1260+82</td>
            <td align="center">T</td>
            <td align="right">-3.48</td>
            <td align="right">9</td>
            <td align="center">1259+88</td>
            <td align="center">1261+03</td>
            <td align="center">T</td>
            <td align="right">-3.81</td>
          </tr>
          <tr>
            <td align="left">10</td>
            <td align="center">1260+82</td>
            <td align="center">1263+52</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">10</td>
            <td align="center">1261+03</td>
            <td align="center">1264+15</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">11</td>
            <td align="center">1263+52</td>
            <td align="center">1264+40</td>
            <td align="center">T</td>
            <td align="right">0.28</td>
            <td align="right">11</td>
            <td align="center">1264+15</td>
            <td align="center">1265+30</td>
            <td align="center">T</td>
            <td align="right">0.22</td>
          </tr>
          <tr>
            <td align="left">12</td>
            <td align="center">1264+40</td>
            <td align="center">1272+10</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">12</td>
            <td align="center">1265+30</td>
            <td align="center">1271+37</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">13</td>
            <td align="center">1272+10</td>
            <td align="center">1276+25</td>
            <td align="center">T</td>
            <td align="right">-0.20</td>
            <td align="right">13</td>
            <td align="center">1271+37</td>
            <td align="center">1276+78</td>
            <td align="center">T</td>
            <td align="right">-0.16</td>
          </tr>
          <tr>
            <td align="left">14</td>
            <td align="center">1276+25</td>
            <td align="center">1279+25</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">14</td>
            <td align="center">1276+78</td>
            <td align="center">1279+73</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">15</td>
            <td align="center">1279+25</td>
            <td align="center">1281+39</td>
            <td align="center">T</td>
            <td align="right">4.24</td>
            <td align="right">15</td>
            <td align="center">1279+73</td>
            <td align="center">1281+87</td>
            <td align="center">T</td>
            <td align="right">4.43</td>
          </tr>
          <tr>
            <td align="left">16</td>
            <td align="center">1281+39</td>
            <td align="center">1287+89</td>
            <td align="center">C</td>
            <td align="right">-</td>
            <td align="right">16</td>
            <td align="center">1281+87</td>
            <td align="center">1287+60</td>
            <td align="center">C</td>
            <td align="right">-</td>
          </tr>
          <tr>
            <td align="left">17</td>
            <td align="center">1287+89</td>
            <td align="center">1292+00</td>
            <td align="center">T</td>
            <td align="right">-1.42</td>
            <td align="right">17</td>
            <td align="center">1287+60</td>
            <td align="center">1292+00</td>
            <td align="center">T</td>
            <td align="right">-1.21</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
    <p>As shown in <xref ref-type="fig" rid="fig8">Figure 8</xref>, the estimated alignment follows the actual profile with an overall acceptable fit; however, the overestimation of the tangent grades between segments 6 and 10 caused a noticeable deviation from the actual alignment. In addition, another deviation occurred after segment 12, where the estimated curve length was shorter than the actual by 163 feet. This shortening causes the subsequent portion of the estimated profile to progressively drift relative to the actual alignment. Despite these localized discrepancies, grade estimation performance remained strong, with the absolute error between actual and estimated grades varying between 0.04 to 0.33 percent across the evaluated segments with a mean absolute error of 0.15 percent.</p>
    <fig id="fig8">
<object-id pub-id-type="publisher-id"></object-id>
<label>Figure 8</label>
<caption>
<title>Actual versus Estimated Vertical Alignment of Route 299</title>
</caption>
<graphic xlink:href="e000134-Figure8.png" />
</fig>
  </sec>
  <sec sec-type="level-B" id="summary-of-analysis-results">
    <title>4.3 Summary of Analysis Results</title>
    <p><xref ref-type="fig" rid="fig9">Figure 9</xref> summarizes the key performance metrics for the two evaluated roadways. The ANN achieved labelling accuracy of 87.5 percent for Route 152 and 85.93 percent for Route 299. Route 152 showed higher overlap for curves than for tangents, with overlap ratios of 92.5 percent and 87.9 percent, respectively; in contrast, Route 299 showed higher overlap for tangents than for curves, with overlap ratios of 92.7 percent for tangents and 83.7 percent for curves. This pattern is consistent with the average missed lengths. Route 152 had a larger average missed tangent length, 76.8 ft, but a smaller missed curve length, 22.4 ft, while Route 299 showed the opposite behavior, with 67.3 ft missed per curve segment and 17.4 ft per tangent segment.</p>
    <fig id="fig9">
<object-id pub-id-type="publisher-id"></object-id>
<label>Figure 9</label>
<caption>
<title>Summary of performance metrics for Route 152 and Route 299</title>
</caption>
<graphic xlink:href="e000134-Figure9.png" />
</fig>
  </sec>
  <sec sec-type="level-B" id="comparative-studies">
    <title>4.4 Comparative Studies</title>
    <p>The proposed ANN-based vertical alignment estimation method was compared with the DEM-based grade estimation method introduced by <xref ref-type="bibr" rid="Liu2018">Liu et al. (2018)</xref>. They proposed a method to obtain roadway grade from the DEM, using elevation extraction along road centerlines, cleaning and infilling erroneous elevation artifacts, applying cubic smoothing splines to reduce noise, and calculating grade as the derivative of the resulting elevation profile. <xref ref-type="bibr" rid="Liu2018">Liu et al. (2018)</xref>’s approach generates a continuous grade profile and does not directly provide tangent/vertical-curve labelling or vertical-curve geometric parameters. The study used mean absolute error (MAE) as the performance metric when evaluating the accuracy of the grades on tangent segments.</p>
    <p>Accordingly, the comparison in this study focused on the accuracy of tangent grade estimation on the two independent roadways, namely Route 152 and Route 299. The results are summarized in <xref ref-type="table" rid="tab3">Table 3</xref>. For Route 152, the proposed method achieved an MAE of 0.042 percent, compared with 0.057 percent obtained using the DEM-spline method. For Route 299, the proposed method achieved an MAE of 0.145 percent, compared with 0.188 percent for the DEM-spline method. In addition to improved grade estimation accuracy, the proposed method also provides pointwise tangent and vertical curve labels that support vertical alignment segmentation and curve identification, enabling the extraction of segment-level vertical alignment characteristics reported in <xref ref-type="table" rid="tab1">Table 1</xref> and <xref ref-type="table" rid="tab2">Table 2</xref>.</p>
<table-wrap id="tab3">
<object-id pub-id-type="publisher-id"></object-id>
<label>Table 3</label>
<caption>
<title>Alignments estimation results comparison of the introduced methods</title>
</caption>
<table>
<thead>
          <tr>
            <th style="background-color:rgb(204,204,204)" align="left">Roadway</th>
            <th style="background-color:rgb(204,204,204)" align="center">Proposed Method MAE (%)</th>
            <th style="background-color:rgb(204,204,204)" align="center"><xref ref-type="bibr" rid="Liu2018">Liu et al. (2018)</xref> Method MAE (%)</th>
            <th style="background-color:rgb(204,204,204)" align="center">Proposed Method Max error (%)</th>
            <th style="background-color:rgb(204,204,204)" align="center"><xref ref-type="bibr" rid="Liu2018">Liu et al. (2018)</xref> Method Max error (%)</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="left">Route 152</td>
            <td align="right">0.042</td>
            <td align="right">0.057</td>
            <td align="right">0.26</td>
            <td align="right">0.25</td>
          </tr>
          <tr>
            <td align="left">Route 299</td>
            <td align="right">0.145</td>
            <td align="right">0.188</td>
            <td align="right">0.33</td>
            <td align="right">0.64</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
  </sec>
  <sec sec-type="level-B" id="case-study">
    <title>4.5 Case study </title>
    <p>To demonstrate the practical application of LiDAR derived vertical alignment data, case studies were conducted on two rural two-lane roadways: Route 299, presented in the previous section, and Route 83 in Cape May County, NJ, which was examined as an independent case study. The primary objective was to use the extracted vertical alignment data to conduct a speed safety assessment along the roadway and identify locations where speed reductions may be warranted due to limited sight distance or sharp curvature. Because posted speed limits are often established at the time of roadway construction and may not be periodically reassessed, the proposed approach can also be used to reevaluate the appropriateness of speed limits for individual roadway segments based on current geometric conditions estimated using LiDAR data.</p>
    <p>To determine the advisory speed governed by roadway geometry, we first divide the alignment into discrete segments based on changes in vertical grade (tangents vs. vertical curves) and horizontal curvature (tangents vs. horizontal curves).</p>
    <p>For each vertical-curve segment <italic>i</italic> of length <italic>L<sub>i</sub></italic> and average absolute grade <italic>G<sub>i</sub></italic>, we compute the maximum safe stopping speed <italic>V<sub>v,i</sub></italic> by equating the stopping-sight distance to the curve length under a conservative braking deceleration <italic>d</italic>, following standard highway design procedures (<xref ref-type="bibr" rid="AASHTO2011">AASHTO, 2011</xref>):</p>
<p><mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" display="block" id="eq1">
<mml:mtable displaystyle="true">
<mml:mlabeledtr>
<mml:mtd>
<mml:mtext>(1)</mml:mtext>
</mml:mtd>
<mml:mtd>
<mml:mrow><mml:msub><mml:mi>V</mml:mi><mml:mrow><mml:mi>v</mml:mi><mml:mi>,</mml:mi><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:msqrt><mml:mrow><mml:mn>2</mml:mn><mml:mi>g</mml:mi><mml:msub><mml:mi>L</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow></mml:msqrt><mml:mtext>(</mml:mtext><mml:mi>d</mml:mi><mml:mo>+</mml:mo><mml:msub><mml:mi>G</mml:mi><mml:mi>i</mml:mi></mml:msub><mml:mtext>)</mml:mtext><mml:mtext>,</mml:mtext><mml:mspace width="1em"/><mml:mi>d</mml:mi><mml:mo>=</mml:mo><mml:mn>0.347</mml:mn><mml:mi>g</mml:mi></mml:mrow>
</mml:mtd>
</mml:mlabeledtr>
</mml:mtable>
</mml:math></p>
    <p>This formula captures the combined effect of gravity and grade on required stopping distance along the curve. For horizontal curves of radius <italic>R<sub>i</sub></italic>​, we apply the standard rural-road speed formula with superelevation <italic>e</italic> = 0.06 and side-friction <italic>f</italic> = 0.15 (<xref ref-type="bibr" rid="AASHTO2011">AASHTO, 2011</xref>).</p>
<p><mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" display="block" id="eq2">
<mml:mtable displaystyle="true">
<mml:mlabeledtr>
<mml:mtd>
<mml:mtext>(2)</mml:mtext>
</mml:mtd>
<mml:mtd>
<mml:mrow><mml:msub><mml:mi>V</mml:mi><mml:mrow><mml:mi>h</mml:mi><mml:mi>,</mml:mi><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:msqrt><mml:mrow><mml:mn>127</mml:mn><mml:msub><mml:mi>R</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow></mml:msqrt><mml:mtext>(</mml:mtext><mml:mi>e</mml:mi><mml:mo>+</mml:mo><mml:mi>f</mml:mi><mml:mtext>)</mml:mtext></mml:mrow>
</mml:mtd>
</mml:mlabeledtr>
</mml:mtable>
</mml:math></p>
    <p>Each roadway segment was analyzed independently, and the minimum of the vertical and horizontal speeds, subject to the statutory speed limit, was assigned as the regenerated speed.</p>
    <p>Route 299 was evaluated using both the actual vertical alignment and the ANN-estimated vertical alignment. The portion of Route 299 analyzed in this study is located on a straight section where there are no horizontal curves; therefore, the regenerated speed profile was governed by the vertical alignment only (Equation 1). The posted speed limit along the selected portion of Route 299 is 55 mph. <xref ref-type="fig" rid="fig10">Figure 10</xref>a illustrates the regenerated speed profile computed along Route 299 using the actual and estimated vertical alignment data. The dashed black line indicates the speed limit (55 mph), while the stepwise regenerated speed profiles show the segment-based speeds computed from the vertical alignment. Shaded regions correspond to actual vertical curve regions. As seen in <xref ref-type="fig" rid="fig10">Figure 10</xref>a, most segments remain at the posted speed limit, indicating that the vertical geometry along this portion of the corridor generally does not impose substantial stopping-sight constraints. However, a localized reduction occurs at a short vertical-curve segment (Segment 8), which controls the minimum regenerated speed in the corridor. Using the actual vertical alignment, this segment yielded a regenerated speed of approximately 46.7 mph, while the estimated vertical alignment yielded a lower regenerated speed of approximately 42.4 mph. This difference is attributable to the estimated vertical alignment representing the controlling curve as slightly more restrictive, which reduces the stopping-based speed computed from Equation 1. Overall, the results for Route 299 indicate that the proposed method can correctly identify the roadway location that governs the minimum safe speed while also providing a conservative estimate of that speed when the roadway alignment is derived from estimated data.</p>
    <fig id="fig10">
<object-id pub-id-type="publisher-id"></object-id>
<label>Figure 10</label>
<caption>
<title>(a) Speed assessment along Route 299 (b) Speed assessment along Route 83</title>
</caption>
<graphic xlink:href="e000134-Figure10.png" />
</fig>
    <p>Route 83 is a 3.79-mile-long rural highway. Its horizontal alignment data were extracted from as-built plan files provided by the NJDOT, and documented in detail by <xref ref-type="bibr" rid="Bartin2022">Bartin et al. (2022)</xref>, which consists of 22 segments: 11 horizontal curves and 11 tangents. Curve segments account for approximately 5,298 ft (~1.00 mi), averaging about 482 ft each, with radii ranging from 385 ft to 6,910 ft, with an average of 2,881 ft. However, the vertical alignment of Route 83 was not available in the as-built plan files. Thus, following the same analysis steps presented in Section 3, its vertical alignment was estimated using the corresponding USGS LiDAR data. The estimated vertical alignment for Route 83 consisted of 42 vertical segments, of which 21 were vertical curves. Together these curves totaled about 1.31 miles, with an average length of nearly 328 ft per curve. Tangent sections exhibited modest slopes, averaging just over 1.07 %, while the vertical-curve segments had an average rate of grade change of approximately 1.06 %.</p>
    <p><xref ref-type="fig" rid="fig10">Figure 10</xref>b illustrates the speed profile regenerated along Route 83. The regenerated speed limits were mostly constrained by the vertical alignment rather than the horizontal, primarily because the horizontal curves along Route 83 do not impose significant speed limitations. In contrast, the estimated vertical curves were relatively short and steep, which restricted stopping sight distance and necessitated speed reductions. Therefore, <xref ref-type="fig" rid="fig10">Figure 10</xref>b highlights only the vertical curve regions where speed reductions occurred due to vertical alignment constraints. The dashed black line shows the speed limit (50 mph), while the blue line represents the regenerated speed limits computed for each vertical curve segment. As seen, several segments along the roadway required speed reductions, especially where steep or abrupt crest vertical curves were present. These segments represented critical points where limited sight distance could compromise safety, and therefore might benefit from countermeasures such as advisory signage or speed control strategies.</p>
    <p>It should be noted that the higher speeds shown in certain segments in <xref ref-type="fig" rid="fig10">Figure 10</xref> were based on geometric analysis only, using vertical and horizontal alignment characteristics. In practice, additional factors such as intersections, pavement condition, lane width, roadside environment, and driver behaviour may also influence operating speeds and posted limits. Despite these limitations, this case study demonstrates how publicly available USGS LiDAR and ANN based vertical alignment estimates can support network-level safety assessments by identifying segments where geometric conditions impose speed constraints. The same methodology can be applied across other roadways using the widely available USGS LiDAR data and the proposed framework.</p>
  </sec>
</sec>
<sec sec-type="level-A" id="conclusions">
  <title>5. Conclusions </title>
  <p>Roadway vertical alignment data play a crucial role in a wide range of highway engineering and safety applications. Vertical grades and curvature shape sight distance, operating speeds, driver workload, and vehicle dynamics, and thus underpin both geometric design decisions and crash modelling. Guidance from AASHTO and FHWA highlights the decisive role of grade and crest–sag curvature in determining stopping sight distance, maintaining speed consistency, and managing visibility limitations on vertical curves (<xref ref-type="bibr" rid="Donnell2018">Donnell et al., 2018</xref>). Empirical evidence further shows that steep grades, combined with horizontal and vertical curvature, increase crash risk and disrupt speed uniformity, especially on rural two-lane roads (<xref ref-type="bibr" rid="Elvik2023">Elvik &amp; Haugvik, 2023</xref>; <xref ref-type="bibr" rid="Ryan2022">Ryan et al., 2022</xref>; <xref ref-type="bibr" rid="Bauer2013">Bauer &amp; Harwood, 2013</xref>; <xref ref-type="bibr" rid="Papadimitriou2019">Papadimitriou et al., 2019</xref>; <xref ref-type="bibr" rid="Kar2024">Kar et al., 2024</xref>). Beyond safety, vertical alignment influences drainage design, fuel consumption, ride comfort, and maintenance strategies, and supports three-dimensional roadway coordination and visibility assessments (<xref ref-type="bibr" rid="FHWA2019">FHWA, 2019</xref>).</p>
  <p>Despite its importance, obtaining vertical alignment data at scale remains difficult and expensive. Legacy plans and profile sheets are often non-digital, and precision surveys using GPS, GNSS, or mobile LiDAR require specialized equipment and substantial resources, limiting corridor coverage (<xref ref-type="bibr" rid="Gargoum2019">Gargoum &amp; El Basyouny, 2019</xref>). While horizontal alignment can be traced using open geospatial layers or imagery, vertical profiles cannot be inferred without elevation data, which complicates coverage across large networks.</p>
  <p>Recent advances in remote sensing help mitigate these barriers. The USGS 3DEP program provides nationwide point clouds and DEMs via The National Map, enabling low-cost derivation of elevations and slopes for most U.S. roads (<xref ref-type="bibr" rid="USGS2025">USGS, 2025</xref>). Prior work demonstrates the promise of LiDAR for automated geometry extraction and safety assessment (<xref ref-type="bibr" rid="Yang2024">Yang &amp; Das, 2024</xref>; <xref ref-type="bibr" rid="Gargoum2019">Gargoum &amp; El Basyouny, 2019</xref>; <xref ref-type="bibr" rid="Wang2025">Wang et al., 2025</xref>), but network-scale processing, roadway point isolation, and reliable classification of tangents and vertical curves still require robust, scalable analytics.</p>
  <p>In this context, this study introduced an innovative approach to estimating vertical alignment data of roadways, which combines LiDAR data with an ANN model, addressing a critical gap by providing an efficient, scalable, and reproducible way to estimate roadway vertical alignment characteristics. Extraction of vertical alignment is known to be time-consuming and expensive, thus necessitating an efficient and rapid method due to its vital role in various traffic safety-related analyses.</p>
  <p>Prior research on the acquisition of road elevation data has predominantly centered on the utilization of GPS and GNSS data from vehicles equipped with sophisticated technologies. Nevertheless, the requirement of such specialized surveying vehicles for data gathering has constrained the method's relevance to a broader array of road networks, owing to substantial costs and prolonged data collection periods. The proposed approach capitalizes on the aerial LiDAR data on the USGS website (<xref ref-type="bibr" rid="USGS2025">USGS, 2025</xref>), which covers the majority of roads in the US.</p>
  <p>An ANN-based approach was used to detect and identify distinct segment types along a road’s vertical alignment. First, LiDAR data were processed and the points corresponding to the study road were extracted using QGIS. Although applied to one roadway, a similar process can be repeated for multiple roads efficiently in a short period of time. Each LiDAR point's classification, indicating whether it corresponded to a vertical tangent or curved segment, was predicted through the proposed ANN model. These predicted classifications were then utilized to estimate the number and characteristics (tangent or curved) of the road segments.</p>
  <p>To train the ANN model, synthetically generated vertical road alignment data were employed. The results of the segmentation process were used to determine essential geometric parameters such as segment length and grades. The key advantage of the presented approach is that it relies only on the labelled LiDAR data points, which makes it easily replicable for other roadway datasets.</p>
  <p>The test dataset employed in this study comprised the vertical alignment data of Route 152 in NJ and Route 299 in CA, both two-way two-lane rural roadways. The results of the analyses demonstrated a strong agreement with the actual alignment (See <xref ref-type="fig" rid="fig7">Figure 7</xref> and <xref ref-type="fig" rid="fig8">Figure 8</xref>). As shown in the summary of evaluation results presented in <xref ref-type="fig" rid="fig9">Figure 9</xref>, for Route 152, an overlap of 92.5 percent with the curved segments’ lengths and 87.9 percent with the tangent segments’ lengths was achieved, indicating a high level of concurrence between the estimated and actual segments. For Route 299, the overlap of the estimated alignment with the actual one was 83.7 percent for curved segments and 92.7 percent for tangent segments. Regarding the evaluation metrics, the average undetected segment lengths were determined to be 22.4 feet and 76.8 feet for curved and tangent segments, respectively for Route 152, while the corresponding values were 67.3 feet and 17.4 feet for curved and tangent segments, respectively, for Route 299.</p>
  <p>Furthermore, the mean absolute error between the estimated and actual grades was found to be 0.042 percent, with variations ranging from 0 percent to 0.26 percent, for Route 152. For Route 299 the mean absolute error was 0.15 percent, with variations ranging from 0.04 percent to 0.33 percent, thus indicating a generally accurate estimation of grades in the analysis.</p>
  <p>As mentioned earlier, roadway vertical alignment datasets are essential in various safety analyses. To demonstrate this, a case study was conducted for Route 83 in NJ and Route 299 in CA, where the extracted vertical alignment data were used to regenerate speed profiles and to identify segments requiring speed reductions. The satisfactory estimation results of this study indicate that the proposed approach can be employed for conducting large-scale analyses to estimate vertical alignment data.</p>
  <p>Future work will involve comparing aerial and drone-based LiDAR to evaluate differences in resolution, accuracy, and cost for various roadway types. A comparison between DEM and raw point cloud data can also help determine which source better captures subtle vertical transitions. Additionally, developing an automated framework to estimate vertical alignment across multiple roadways would enable efficient, large-scale analysis and support broader safety assessments.</p>
 </sec> 
<sec sec-type="level-A" id="ack">
<title>Acknowledgements</title>
<p>The contents of this paper only reflect the views of the authors, who are responsible for the facts and do not represent any official views of any sponsoring organizations or agencies.</p>
 </sec> 
<sec sec-type="level-A" id="coi">
<title>Competing interests</title>
<p>The authors report no competing interests.</p>
 </sec> 
<sec sec-type="level-A" id="contrib">
<title>CRediT contribution</title>
<p><bold>Mojibulrahman Jami:</bold> Conceptualization, Data curation, Formal analysis, Investigation, Methodology, Writing—original draft, Writing—review &amp; editing. <bold>Bekir Bartin:</bold> Conceptualization, Data curation, Formal analysis, Investigation, Methodology, Writing—original draft, Writing—review &amp; editing. <bold>Kaan Ozbay:</bold> Conceptualization, Formal analysis, Investigation, Methodology, Writing—original draft, Writing—review &amp; editing.</p>
 </sec> 
<sec sec-type="level-A">
<title>Ethics</title>
<p>This study did not involve human participants, or identifiable personal data and relied solely on publicly available geospatial datasets (e.g., USGS 3DEP LiDAR).</p>
 </sec> 
<sec sec-type="level-A" id="fund">
<title>Funding</title>
<p>The study is supported by the NJDOT (FHWA-NJ-2017-007) and partially by Ozyegin University and partially by C2SMARTER, a Tier 1 UTC at New York University funded by the USDOT.</p>
 </sec> 
<sec sec-type="level-A">
<title>Generative AI use in writing</title>
<p>During the preparation of this work, the authors used ChatGPT (OpenAI) in order to improve the clarity, grammar, and wording of specific sections of the manuscript. The output was reviewed and revised by the authors, who take full responsibility for the content of the publication.</p>
 </sec> 
<sec sec-type="level-A">
<title>Editorial information</title>
<p>Handling editor: <bold>Lai Zheng</bold>, Harbin Institute of Technology, China.</p>
<p>Reviewers: <bold>Peijie Wu</bold>, Chongqing Jiaotong University, China; <bold>Feng Jiang</bold>, Harbin Institute of Technology, China.</p>
<p>Submitted: 20 October 2025; Accepted: 22 March 2026; Published: 3 April 2026.</p>
</sec>
</body>
<back>
<ref-list>
<ref id="AASHTO2011">
  <element-citation publication-type="book">
    <collab>AASHTO</collab>
    <source>A Policy on Geometric Design of Highways and Streets, 6th edition</source>
    <publisher-loc>Washington, D.C.</publisher-loc>
    <year>2011</year>
  </element-citation>
</ref>
<ref id="Anil2010">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Anil</surname><given-names>P. N.</given-names></name>
      <name><surname>Natarajan</surname><given-names>S.</given-names></name>
    </person-group>
    <article-title>Automatic Road Extraction from High Resolution Imagery Based On Statistical Region Merging and Skeletoniz</article-title>
    <source>International Journal of Engineering Science and Technology</source>
    <year>2010</year>
    <volume>2</volume>
    <issue>3</issue>
  </element-citation>
</ref>
<ref id="Baass2005">
  <element-citation publication-type="book">
    <person-group person-group-type="author">
      <name><surname>Baass</surname><given-names>K.</given-names></name>
      <name><surname>Vouland</surname><given-names>J.</given-names></name>
    </person-group>
    <source>DÉTERMINATION DE L’ALIGNEMENT ROUTIER À PARTIR DE TRACES GPS</source>
    <year>2005</year>
  </element-citation>
</ref>
<ref id="Bartin2022">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Bartin</surname><given-names>B.</given-names></name>
      <name><surname>Demiroluk</surname><given-names>S.</given-names></name>
      <name><surname>Ozbay</surname><given-names>K.</given-names></name>
      <name><surname>Jami</surname><given-names>M.</given-names></name>
    </person-group>
    <article-title>Automatic Identification of Roadway Horizontal Alignment Information Using Geographic Information System Data: CurvS Tool</article-title>
    <source>Transportation Research Record</source>
    <year>2022</year>
    <volume>2676</volume>
    <issue>1</issue>
    <fpage>532</fpage>
    <lpage>543</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1177/03611981211036364</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1177/03611981211036364">https://doi.org/10.1177/03611981211036364</ext-link>
  </element-citation>
</ref>
<ref id="Bartin2021">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Bartin</surname><given-names>B.</given-names></name>
      <name><surname>Jami</surname><given-names>M.</given-names></name>
      <name><surname>Ozbay</surname><given-names>K.</given-names></name>
    </person-group>
    <article-title>Estimating Roadway Horizontal Alignment using Artificial Neural Network</article-title>
    <source>IEEE Conference on Intelligent Transportation Systems, Proceedings, ITSC</source>
    <year>2021</year>
    <volume>2021-September</volume>
    <fpage>2245</fpage>
    <lpage>2250</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1109/ITSC48978.2021.9565062</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1109/ITSC48978.2021.9565062">https://doi.org/10.1109/ITSC48978.2021.9565062</ext-link>
  </element-citation>
</ref>
<ref id="Bartin2023">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Bartin</surname><given-names>B.</given-names></name>
      <name><surname>Jami</surname><given-names>M.</given-names></name>
      <name><surname>Ozbay</surname><given-names>K.</given-names></name>
    </person-group>
    <article-title>Estimating Roadway Horizontal Alignment from Geographic Information Systems Data: An Artificial Neural Network–Based Approach</article-title>
    <source>Journal of Surveying Engineering</source>
    <year>2023</year>
    <volume>149</volume>
    <issue>4</issue>
    <object-id pub-id-type="doi">https://doi.org/10.1061/jsued2.sueng-1439</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1061/jsued2.sueng-1439">https://doi.org/10.1061/jsued2.sueng-1439</ext-link>
  </element-citation>
</ref>
<ref id="Bartin2019">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Bartin</surname><given-names>B.</given-names></name>
      <name><surname>Ozbay</surname><given-names>K.</given-names></name>
      <name><surname>Xu</surname><given-names>C.</given-names></name>
    </person-group>
    <article-title>Extracting Horizontal Curvature Data from GIS Maps: Clustering Method</article-title>
    <source>Transportation Research Record</source>
    <year>2019</year>
    <volume>2673</volume>
    <issue>11</issue>
    <fpage>264</fpage>
    <lpage>275</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1177/0361198119850789</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1177/0361198119850789">https://doi.org/10.1177/0361198119850789</ext-link>
  </element-citation>
</ref>
<ref id="Bauer2013">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Bauer</surname><given-names>K. M.</given-names></name>
      <name><surname>Harwood</surname><given-names>D. W.</given-names></name>
    </person-group>
    <article-title>Safety effects of horizontal curve and grade combinations on rural two-lane highways</article-title>
    <source>Transportation Research Record</source>
    <year>2013</year>
    <volume>2398</volume>
    <issue>1</issue>
    <fpage>37</fpage>
    <lpage>49</lpage>
  </element-citation>
</ref>
<ref id="Caltrans2026">
  <element-citation publication-type="book">
    <collab>Caltrans</collab>
    <source>California Department of Transportation Website</source>
    <year>2026</year>
    <date-in-citation content-type="access-date">March 8, 2026</date-in-citation>
    <ext-link ext-link-type="uri" xlink:href="https://lab.data.ca.gov/dataset/california-all-public-roads-network">https://lab.data.ca.gov/dataset/california-all-public-roads-network</ext-link>
  </element-citation>
</ref>
<ref id="DiMascio2012">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Di Mascio</surname><given-names>P.</given-names></name>
      <name><surname>Di Vito</surname><given-names>M.</given-names></name>
      <name><surname>Loprencipe</surname><given-names>G.</given-names></name>
      <name><surname>Ragnoli</surname><given-names>A.</given-names></name>
    </person-group>
    <article-title>Procedure to Determine the Geometry of Road Alignment Using GPS Data</article-title>
    <source>Procedia - Social and Behavioral Sciences</source>
    <year>2012</year>
    <volume>53</volume>
    <fpage>1202</fpage>
    <lpage>1215</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1016/j.sbspro.2012.09.969</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/j.sbspro.2012.09.969">https://doi.org/10.1016/j.sbspro.2012.09.969</ext-link>
  </element-citation>
</ref>
<ref id="Donnell2018">
  <element-citation publication-type="book">
    <person-group person-group-type="author">
      <name><surname>Donnell</surname><given-names>E. T.</given-names></name>
      <name><surname>Kersavage</surname><given-names>K.</given-names></name>
      <name><surname>Tierney</surname><given-names>L. F.</given-names></name>
    </person-group>
    <source>Self-Enforcing Roadways: A Guidance Report</source>
    <publisher-name>Federal Highway Administration</publisher-name>
    <publisher-loc>United States</publisher-loc>
    <year>2018</year>
  </element-citation>
</ref>
<ref id="Easa2007">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Easa</surname><given-names>S. M.</given-names></name>
      <name><surname>Dong</surname><given-names>H.</given-names></name>
      <name><surname>Li</surname><given-names>J.</given-names></name>
    </person-group>
    <article-title>Use of Satellite Imagery for Establishing Road Horizontal Alignments</article-title>
    <source>Journal of Surveying Engineering</source>
    <year>2007</year>
    <volume>133</volume>
    <issue>1</issue>
    <fpage>29</fpage>
    <lpage>35</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1061/(ASCE)0733-9453(2007)133:1(29)</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1061/(ASCE)0733-9453(2007)133:1(29)">https://doi.org/10.1061/(ASCE)0733-9453(2007)133:1(29)</ext-link>
  </element-citation>
</ref>
<ref id="Easa2010">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Easa</surname><given-names>S. M.</given-names></name>
      <name><surname>Wang</surname><given-names>F.</given-names></name>
    </person-group>
    <article-title>Estimating continuous highway vertical alignment using the least-squares method</article-title>
    <source>Canadian Journal of Civil Engineering</source>
    <year>2010</year>
    <volume>37</volume>
    <issue>10</issue>
    <fpage>1362</fpage>
    <lpage>1370</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1139/L10-088</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1139/L10-088">https://doi.org/10.1139/L10-088</ext-link>
  </element-citation>
</ref>
<ref id="Elvik2023">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Elvik</surname><given-names>R.</given-names></name>
      <name><surname>Haugvik</surname><given-names>E. S.</given-names></name>
    </person-group>
    <article-title>Safety of horizontal curves on rural two-lane roads in Norway</article-title>
    <source>Traffic Safety Research</source>
    <year>2023</year>
    <volume>4</volume>
    <object-id pub-id-type="doi">https://doi.org/10.55329/hkbk3638</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.55329/hkbk3638">https://doi.org/10.55329/hkbk3638</ext-link>
  </element-citation>
</ref>
<ref id="FHWA2019">
  <element-citation publication-type="book">
    <collab>FHWA</collab>
    <source>Horizontal Curve Safety</source>
    <year>2019</year>
    <ext-link ext-link-type="uri" xlink:href="https://Safety.Fhwa.Dot.Gov/Roadway_dept/Countermeasures/Horicurves/">https://Safety.Fhwa.Dot.Gov/Roadway_dept/Countermeasures/Horicurves/</ext-link>
    <date-in-citation content-type="access-date">July 7, 2022</date-in-citation>
  </element-citation>
</ref>
<ref id="Findley2012">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Findley</surname><given-names>D. J.</given-names></name>
      <name><surname>Hummer</surname><given-names>J. E.</given-names></name>
      <name><surname>Rasdorf</surname><given-names>W.</given-names></name>
      <name><surname>Laton</surname><given-names>B. T.</given-names></name>
    </person-group>
    <article-title>Collecting Horizontal Curve Data: Mobile Asset Vehicles and Other Techniques</article-title>
    <source>Journal of Infrastructure Systems</source>
    <year>2012</year>
    <volume>19</volume>
    <issue>1</issue>
    <fpage>74</fpage>
    <lpage>84</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1061/(ASCE)IS.1943-555X.0000107</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1061/(ASCE)IS.1943-555X.0000107">https://doi.org/10.1061/(ASCE)IS.1943-555X.0000107</ext-link>
  </element-citation>
</ref>
<ref id="Gargoum2019">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Gargoum</surname><given-names>S. A.</given-names></name>
      <name><surname>El Basyouny</surname><given-names>K.</given-names></name>
    </person-group>
    <article-title>A literature synthesis of LiDAR applications in transportation: Feature extraction and geometric assessments of highways</article-title>
    <source>GIScience &amp; Remote Sensing</source>
    <year>2019</year>
    <volume>56</volume>
    <issue>6</issue>
    <fpage>864</fpage>
    <lpage>893</lpage>
  </element-citation>
</ref>
<ref id="Gargoum2018">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Gargoum</surname><given-names>S. A.</given-names></name>
      <name><surname>El-Basyouny</surname><given-names>K.</given-names></name>
      <name><surname>Shalkamy</surname><given-names>A.</given-names></name>
      <name><surname>Gouda</surname><given-names>M.</given-names></name>
    </person-group>
    <article-title>Feasibility of extracting highway vertical profiles from LiDAR data</article-title>
    <source>Canadian Journal of Civil Engineering</source>
    <year>2018</year>
    <volume>45</volume>
    <issue>5</issue>
    <fpage>418</fpage>
    <lpage>421</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1139/cjce-2017-0620</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1139/cjce-2017-0620">https://doi.org/10.1139/cjce-2017-0620</ext-link>
  </element-citation>
</ref>
<ref id="Gesch2014">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Gesch</surname><given-names>D. B.</given-names></name>
      <name><surname>Oimoen</surname><given-names>M. J.</given-names></name>
      <name><surname>Evans</surname><given-names>G. A.</given-names></name>
    </person-group>
    <source>Accuracy assessment of the U.S. Geological Survey National Elevation Dataset, and comparison with other large-area elevation datasets: SRTM and ASTER (Open-File Report)</source>
    <year>2014</year>
    <object-id pub-id-type="doi">https://doi.org/10.3133/ofr20141008</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3133/ofr20141008">https://doi.org/10.3133/ofr20141008</ext-link>
  </element-citation>
</ref>
<ref id="Glennon1987">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Glennon</surname><given-names>J. C.</given-names></name>
    </person-group>
    <source>Effect of Alignment on Highway Safety. State of the Art Report</source>
    <year>1987</year>
    <ext-link ext-link-type="uri" xlink:href="https://api.semanticscholar.org/CorpusID:106474855">https://api.semanticscholar.org/CorpusID:106474855</ext-link>
  </element-citation>
</ref>
<ref id="Hamdar2016">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Hamdar</surname><given-names>S. H.</given-names></name>
      <name><surname>Qin</surname><given-names>L.</given-names></name>
      <name><surname>Talebpour</surname><given-names>A.</given-names></name>
    </person-group>
    <article-title>Weather and road geometry impact on longitudinal driving behavior: Exploratory analysis using an empirically supported acceleration modeling framework</article-title>
    <source>Transportation Research Part C: Emerging Technologies</source>
    <year>2016</year>
    <volume>67</volume>
    <fpage>193</fpage>
    <lpage>213</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1016/J.TRC.2016.01.017</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/J.TRC.2016.01.017">https://doi.org/10.1016/J.TRC.2016.01.017</ext-link>
  </element-citation>
</ref>
<ref id="Higuera2017">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Higuera de Frutos</surname><given-names>S.</given-names></name>
      <name><surname>Castro</surname><given-names>M.</given-names></name>
    </person-group>
    <article-title>A Method to Identify and Classify the Vertical Alignment of Existing Roads</article-title>
    <source>Computer-Aided Civil and Infrastructure Engineering</source>
    <year>2017</year>
    <volume>32</volume>
    <issue>11</issue>
    <fpage>952</fpage>
    <lpage>963</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1111/mice.12302</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1111/mice.12302">https://doi.org/10.1111/mice.12302</ext-link>
  </element-citation>
</ref>
<ref id="Holgado-Barco2014">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Holgado-Barco</surname><given-names>A.</given-names></name>
      <name><surname>Gonzalez-Aguilera</surname><given-names>D.</given-names></name>
      <name><surname>Arias-Sanchez</surname><given-names>P.</given-names></name>
      <name><surname>Martinez-Sanchez</surname><given-names>J.</given-names></name>
    </person-group>
    <article-title>An automated approach to vertical road characterisation using mobile LiDAR systems: Longitudinal profiles and cross-sections</article-title>
    <source>ISPRS Journal of Photogrammetry and Remote Sensing</source>
    <year>2014</year>
    <volume>96</volume>
    <fpage>28</fpage>
    <lpage>37</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1016/J.ISPRSJPRS.2014.06.017</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/J.ISPRSJPRS.2014.06.017">https://doi.org/10.1016/J.ISPRSJPRS.2014.06.017</ext-link>
  </element-citation>
</ref>
<ref id="Imran2006">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Imran</surname><given-names>M.</given-names></name>
      <name><surname>Hassan</surname><given-names>Y.</given-names></name>
      <name><surname>Patterson</surname><given-names>D.</given-names></name>
    </person-group>
    <article-title>GPS-GIS-based procedure for tracking vehicle path on horizontal alignments</article-title>
    <source>Computer-Aided Civil and Infrastructure Engineering</source>
    <year>2006</year>
    <volume>21</volume>
    <issue>5</issue>
    <object-id pub-id-type="doi">https://doi.org/10.1111/j.1467-8667.2006.00444.x</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1111/j.1467-8667.2006.00444.x">https://doi.org/10.1111/j.1467-8667.2006.00444.x</ext-link>
  </element-citation>
</ref>
<ref id="Kar2024">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Kar</surname><given-names>P.</given-names></name>
      <name><surname>Venthuruthiyil</surname><given-names>S. P.</given-names></name>
      <name><surname>Chunchu</surname><given-names>M.</given-names></name>
    </person-group>
    <article-title>Crash risk estimation of Heavy Commercial vehicles on horizontal curves in mountainous terrain using proactive safety method</article-title>
    <source>Accident Analysis &amp; Prevention</source>
    <year>2024</year>
    <volume>199</volume>
    <fpage>107521</fpage>
  </element-citation>
</ref>
<ref id="Liu2018">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Liu</surname><given-names>H.</given-names></name>
      <name><surname>Li</surname><given-names>H.</given-names></name>
      <name><surname>Rodgers</surname><given-names>M. O.</given-names></name>
      <name><surname>Guensler</surname><given-names>R.</given-names></name>
    </person-group>
    <article-title>Development of road grade data using the United States geological survey digital elevation model</article-title>
    <source>Transportation Research Part C: Emerging Technologies</source>
    <year>2018</year>
    <volume>92</volume>
    <fpage>243</fpage>
    <lpage>257</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1016/J.TRC.2018.05.004</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/J.TRC.2018.05.004">https://doi.org/10.1016/J.TRC.2018.05.004</ext-link>
  </element-citation>
</ref>
<ref id="Luo2018">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Luo</surname><given-names>W.</given-names></name>
      <name><surname>Li</surname><given-names>L.</given-names></name>
      <name><surname>Wang</surname><given-names>K. C. P.</given-names></name>
    </person-group>
    <article-title>Automatic Horizontal Curve Identification and Measurement Using Mobile Mapping System</article-title>
    <source>Journal of Surveying Engineering</source>
    <year>2018</year>
    <volume>144</volume>
    <issue>4</issue>
    <object-id pub-id-type="doi">https://doi.org/10.1061/(ASCE)SU.1943-5428.0000257</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1061/(ASCE)SU.1943-5428.0000257">https://doi.org/10.1061/(ASCE)SU.1943-5428.0000257</ext-link>
  </element-citation>
</ref>
<ref id="Mannering2020">
  <element-citation publication-type="book">
    <person-group person-group-type="author">
      <name><surname>Mannering</surname><given-names>F. L.</given-names></name>
      <name><surname>Washburn</surname><given-names>S. S.</given-names></name>
    </person-group>
    <source>Principles of highway engineering and traffic analysis</source>
    <publisher-name>John Wiley &amp; Sons</publisher-name>
    <year>2020</year>
  </element-citation>
</ref>
<ref id="MySanAntonio2025">
  <element-citation publication-type="misc">
    <collab>MySanAntonio</collab>
    <source>Devastating timeline of deadly floods in San Antonio</source>
    <year>2025</year>
    <ext-link ext-link-type="uri" xlink:href="https://www.mysanantonio.com/news/local/article/san-antonio-flooding-20381901.php">https://www.mysanantonio.com/news/local/article/san-antonio-flooding-20381901.php</ext-link>
  </element-citation>
</ref>
<ref id="NPR2025">
  <element-citation publication-type="misc">
    <collab>National Public Radio</collab>
    <source>Heavy rains and flash flooding sweep across Northeast : NPR</source>
    <year>2025</year>
    <ext-link ext-link-type="uri" xlink:href="https://www.npr.org/2025/07/15/nx-s1-5468220/northeast-rains-flooding-new-york-pennsylvania-new-jersey">https://www.npr.org/2025/07/15/nx-s1-5468220/northeast-rains-flooding-new-york-pennsylvania-new-jersey</ext-link>
  </element-citation>
</ref>
<ref id="NJDOT2025">
  <element-citation publication-type="misc">
    <collab>NJDOT</collab>
    <source>New Jersey Department of Transportation Website</source>
    <year>2025</year>
    <date-in-citation content-type="access-date">December 14, 2024</date-in-citation>
    <ext-link ext-link-type="uri" xlink:href="https://www.state.nj.us/transportation/refdata/gis/data.shtm">https://www.state.nj.us/transportation/refdata/gis/data.shtm</ext-link>
  </element-citation>
</ref>
<ref id="Papadimitriou2019">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Papadimitriou</surname><given-names>E.</given-names></name>
      <name><surname>Filtness</surname><given-names>A.</given-names></name>
      <name><surname>Theofilatos</surname><given-names>A.</given-names></name>
      <name><surname>Ziakopoulos</surname><given-names>A.</given-names></name>
      <name><surname>Quigley</surname><given-names>C.</given-names></name>
      <name><surname>Yannis</surname><given-names>G.</given-names></name>
    </person-group>
    <article-title>Review and ranking of crash risk factors related to the road infrastructure</article-title>
    <source>Accident Analysis &amp; Prevention</source>
    <year>2019</year>
    <volume>125</volume>
    <fpage>85</fpage>
    <lpage>97</lpage>
  </element-citation>
</ref>
<ref id="Reutebuch2005">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Reutebuch</surname><given-names>S. E.</given-names></name>
      <name><surname>Andersen</surname><given-names>H. E.</given-names></name>
      <name><surname>McGaughey</surname><given-names>R. J.</given-names></name>
    </person-group>
    <article-title>Light detection and ranging (LIDAR): An emerging tool for multiple resource inventory</article-title>
    <source>Journal of Forestry</source>
    <year>2005</year>
    <volume>103</volume>
    <issue>6</issue>
    <fpage>286</fpage>
    <lpage>292</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1093/jof/103.6.286</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1093/jof/103.6.286">https://doi.org/10.1093/jof/103.6.286</ext-link>
  </element-citation>
</ref>
<ref id="Ryan2022">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Ryan</surname><given-names>A.</given-names></name>
      <name><surname>Hennessy</surname><given-names>E.</given-names></name>
      <name><surname>Ai</surname><given-names>C.</given-names></name>
      <name><surname>Kwon</surname><given-names>W.</given-names></name>
      <name><surname>Fitzpatrick</surname><given-names>C.</given-names></name>
      <name><surname>Knodler</surname><given-names>M. A.</given-names></name>
    </person-group>
    <article-title>Driver performance at horizontal curves: bridging critical research gaps to increase safety</article-title>
    <source>Traffic Safety Research</source>
    <year>2022</year>
    <volume>3</volume>
    <issue>Special issue</issue>
    <object-id pub-id-type="doi">https://doi.org/10.55329/lmji8901</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.55329/lmji8901">https://doi.org/10.55329/lmji8901</ext-link>
  </element-citation>
</ref>
<ref id="Shams2023">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Shams</surname><given-names>A.</given-names></name>
      <name><surname>Sarasua</surname><given-names>W. A.</given-names></name>
      <name><surname>Russell</surname><given-names>B. T.</given-names></name>
      <name><surname>Davis</surname><given-names>W. J.</given-names></name>
      <name><surname>Post</surname><given-names>C.</given-names></name>
      <name><surname>Rastiveis</surname><given-names>H.</given-names></name>
      <name><surname>Famili</surname><given-names>A.</given-names></name>
      <name><surname>Cassule</surname><given-names>L.</given-names></name>
    </person-group>
    <article-title>Extracting Highway Cross Slopes From Airborne and Mobile LiDAR Point Clouds</article-title>
    <source>Transportation Research Record</source>
    <year>2023</year>
    <volume>2677</volume>
    <issue>2</issue>
    <fpage>372</fpage>
    <lpage>384</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1177/03611981221106482</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1177/03611981221106482">https://doi.org/10.1177/03611981221106482</ext-link>
  </element-citation>
</ref>
<ref id="Tachikawa2011">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Tachikawa</surname><given-names>T.</given-names></name>
      <name><surname>Hato</surname><given-names>M.</given-names></name>
      <name><surname>Kaku</surname><given-names>M.</given-names></name>
      <name><surname>Iwasaki</surname><given-names>A.</given-names></name>
    </person-group>
    <article-title>Characteristics of ASTER GDEM version 2</article-title>
    <source>2011 IEEE International Geoscience and Remote Sensing Symposium</source>
    <year>2011</year>
    <fpage>3657</fpage>
    <lpage>3660</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1109/IGARSS.2011.6050017</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1109/IGARSS.2011.6050017">https://doi.org/10.1109/IGARSS.2011.6050017</ext-link>
  </element-citation>
</ref>
<ref id="USGS2025">
  <element-citation publication-type="misc">
    <collab>USGS</collab>
    <source>11. U.S. Geographical Survey (USGS)</source>
    <year>2025</year>
    <ext-link ext-link-type="uri" xlink:href="http://Nationalmap.Gov/Elevation.Html">http://Nationalmap.Gov/Elevation.Html</ext-link>
  </element-citation>
</ref>
<ref id="Wang2025">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Wang</surname><given-names>Y.</given-names></name>
      <name><surname>Liu</surname><given-names>Y.</given-names></name>
      <name><surname>Pauwels</surname><given-names>P.</given-names></name>
      <name><surname>Li</surname><given-names>Z.</given-names></name>
      <name><surname>Yu</surname><given-names>B.</given-names></name>
    </person-group>
    <article-title>Automated extraction of geometric information from LiDAR point clouds on curved ramps</article-title>
    <source>Automation in Construction</source>
    <year>2025</year>
    <volume>177</volume>
    <fpage>106358</fpage>
  </element-citation>
</ref>
<ref id="WTOP2025">
  <element-citation publication-type="misc">
    <collab>WTOP News</collab>
    <source>New data map shows higher flood risks for roads and transit networks - WTOP News</source>
    <year>2025</year>
    <ext-link ext-link-type="uri" xlink:href="https://wtop.com/weather-news/2025/07/a-new-map-from-cog-shows-the-flood-risks-for-roads-and-transit-networks/">https://wtop.com/weather-news/2025/07/a-new-map-from-cog-shows-the-flood-risks-for-roads-and-transit-networks/</ext-link>
  </element-citation>
</ref>
<ref id="Xu2016">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Xu</surname><given-names>H.</given-names></name>
      <name><surname>Wei</surname><given-names>D.</given-names></name>
    </person-group>
    <article-title>Improved identification and calculation of horizontal curves with geographic information system road layers</article-title>
    <source>Transportation Research Record</source>
    <year>2016</year>
    <volume>2595</volume>
    <fpage>50</fpage>
    <lpage>58</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.3141/2595-06</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3141/2595-06">https://doi.org/10.3141/2595-06</ext-link>
  </element-citation>
</ref>
<ref id="Yang2024">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Yang</surname><given-names>X.</given-names></name>
      <name><surname>Das</surname><given-names>J.</given-names></name>
    </person-group>
    <article-title>Efficient Extraction of Horizontal and Vertical Alignment Information for Roadways Using Public Data and Open Application Programming Interfaces</article-title>
    <source>Transportation Research Record</source>
    <year>2024</year>
    <object-id pub-id-type="doi">https://doi.org/10.1177/03611981241254117</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1177/03611981241254117">https://doi.org/10.1177/03611981241254117</ext-link>
  </element-citation>
</ref>
<ref id="Yu2014">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Yu</surname><given-names>R.</given-names></name>
      <name><surname>Abdel-Aty</surname><given-names>M.</given-names></name>
    </person-group>
    <article-title>Analyzing crash injury severity for a mountainous freeway incorporating real-time traffic and weather data</article-title>
    <source>Safety Science</source>
    <year>2014</year>
    <volume>63</volume>
    <fpage>50</fpage>
    <lpage>56</lpage>
    <object-id pub-id-type="doi">https://doi.org/10.1016/J.SSCI.2013.10.012</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/J.SSCI.2013.10.012">https://doi.org/10.1016/J.SSCI.2013.10.012</ext-link>
  </element-citation>
</ref>
<ref id="Yun2005">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Yun</surname><given-names>D.</given-names></name>
      <name><surname>Sung</surname><given-names>J.</given-names></name>
    </person-group>
    <article-title>Development of highway horizontal alignment analysis algorithm applicable to the road safety survey and analysis vehicle, RoSSAV</article-title>
    <source>Proceedings of the Eastern Asia Society for Transportation Studies, Vol 5</source>
    <year>2005</year>
    <volume>5</volume>
  </element-citation>
</ref>
<ref id="Zhou2021">
  <element-citation publication-type="journal">
    <person-group person-group-type="author">
      <name><surname>Zhou</surname><given-names>Y.</given-names></name>
      <name><surname>Huang</surname><given-names>R.</given-names></name>
      <name><surname>Jiang</surname><given-names>T.</given-names></name>
      <name><surname>Dong</surname><given-names>Z.</given-names></name>
      <name><surname>Yang</surname><given-names>B.</given-names></name>
    </person-group>
    <article-title>Highway alignments extraction and 3D modeling from airborne laser scanning point clouds</article-title>
    <source>International Journal of Applied Earth Observation and Geoinformation</source>
    <year>2021</year>
    <volume>102</volume>
    <fpage>102429</fpage>
    <object-id pub-id-type="doi">https://doi.org/10.1016/J.JAG.2021.102429</object-id>
    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/J.JAG.2021.102429">https://doi.org/10.1016/J.JAG.2021.102429</ext-link>
  </element-citation>
</ref>
</ref-list>
</back>
</article>