Chapter 9 - Remote Sensing - Revision history

Milanowskia1: /* 9.1 Static Laser Scanning Standards */

2023-05-30T16:42:34Z

9.1 Static Laser Scanning Standards

Show changes

Milanowskia1: /* 9.2 Mobile Terrestrial Laser Scanning Standards */

2022-09-07T14:53:09Z

9.2 Mobile Terrestrial Laser Scanning Standards

Milanowskia1: /* 9.1.3 Scanning Control and QA/QC */

2022-09-07T14:47:20Z

9.1.3 Scanning Control and QA/QC

Milanowskia1: /* 9.1 Static Laser Scanning Standards */

2022-09-07T14:43:39Z

9.1 Static Laser Scanning Standards

Lacrossd1: /* 9.1.3 Scanning Control and QA/QC */

2017-06-16T12:16:41Z

9.1.3 Scanning Control and QA/QC

Lacrossd1: /* 9.2.2 MTL Control and Geo-Referencing */

2017-03-08T18:33:02Z

9.2.2 MTL Control and Geo-Referencing

Lacrossd1: /* 9.1.2 Scanning Data Requirements */

2017-03-08T16:30:51Z

9.1.2 Scanning Data Requirements

Lacrossd1: /* 9.1.1 Scanning Project Folder Requirement Information */

2017-03-08T16:25:49Z

9.1.1 Scanning Project Folder Requirement Information

Lacrossd1: /* 9.1.3 Scanning Control and QA/QC */

2017-03-08T16:07:35Z

9.1.3 Scanning Control and QA/QC

Lacrossd1: /* 9.1.3 Scanning Control and QA/QC */

2017-03-08T16:04:59Z

9.1.3 Scanning Control and QA/QC

@@ Line 72: / Line 72: @@
 ==[[#9.2 Mobile Terrestrial Laser Scanning Standards|9.2 Mobile Terrestrial Laser Scanning Standards]]==
-The intent of this document is to provide guidelines and standards related to the use of Mobile Terrestrial LiDAR (MTL) on design engineering projects for the Michigan Department of Transportation. These standards and guidelines are also intended to provide the methodology and procedures that will help ensure products produced with MTL will meet MDOTâ€™s needs for design engineering for transportation corridors.
+The intent of this document is to provide guidelines and standards related to the use of Mobile Terrestrial LiDAR (MTL) on design engineering projects for the Michigan Department of Transportation. These standards and guidelines are also intended to provide the methodology and procedures that will help ensure products produced with MTL will meet MDOT's needs for design engineering for transportation corridors.
@@ Line 137: / Line 137: @@
 *Any use of MTL technologies must conform to and utilize the information in this document and the following documents in the preparation of MDOT projects and deliverables:
 **Current MDOT Standards of Practice for Design Surveys
-**[http://onlinepubs.trb.org/onlinepubs/nchrp/nchrp_rpt_748.pdf nchrp_rpt_748.pdf] â€œGuidelines for the Use of Mobile LIDAR in Transportation Applicationsâ€, April 2013
+**[http://onlinepubs.trb.org/onlinepubs/nchrp/nchrp_rpt_748.pdf nchrp_rpt_748.pdf] "Guidelines for the Use of Mobile LIDAR in Transportation Applications", April 2013
 **Caltrans Survey Manual Chapter 15 Terrestrial Laser Scanning Specifications
@@ Line 152: / Line 152: @@
 *Upon completion of the raw LiDAR processing and registration and prior to mapping extraction, copies of the following must be provided to Lansing Design Surveys and the Survey Project Manager for review:
 **Project report describing in detail how the mobile mapping project was done, number and general location of passes to acquire data, equipment used, datum surveyed on, and results of the processing.
-**The trajectory plan and a ground control target layout plan (including the locations of any CORS GPS Stations and/or any local GPS base stations) use to complete the LiDAR data acquisition. Provide a copy of manufacturerâ€™s trajectory plot, a set of TopoDOT TopoMission project files and set of .kml/.kmz files.
+**The trajectory plan and a ground control target layout plan (including the locations of any CORS GPS Stations and/or any local GPS base stations) use to complete the LiDAR data acquisition. Provide a copy of manufacturer's trajectory plot, a set of TopoDOT TopoMission project files and set of .kml/.kmz files.
 **Reports and printouts from the processing software showing the results of the registration process.
-**Target to cloud registration â€“ Statistics and comparison of the point cloud to the targets
+**Target to cloud registration - Statistics and comparison of the point cloud to the targets
-**Cloud to cloud registration â€“ Statistics and comparison of adjoining overlapping point clouds.
+**Cloud to cloud registration - Statistics and comparison of adjoining overlapping point clouds.
 **Separation of forward and reverse solution (difference between forward and reverse post-process roll, pitch, yaw and XYZ positions solution).
 **Areas of the project that the data collected exceeded the maximum elapsed time or distance traveled of uncorrected IMU drift due to GNSS signal loss or obstruction.
@@ Line 190: / Line 190: @@
 *Point cloud files must be provided on electronic media of an appropriate size to contain all project information.  Two (2) copies must be provided to MDOT Lansing Survey Support Unit. A third (3rd) copy must be provided for use by the MDOT Region Surveyor.
-*LiDAR and Mobile Mapping information should be prepared and placed in a separate sub-folder named â€œLiDAR/Mobile Mappingâ€ under the Project Mapping Folder and must contain all information and LiDAR/Mobile Mapping deliverables relative to the project.
+*LiDAR and Mobile Mapping information should be prepared and placed in a separate sub-folder named "LiDAR/Mobile Mapping" under the Project Mapping Folder and must contain all information and LiDAR/Mobile Mapping deliverables relative to the project.
-*When other methods of survey and mapping are also employed for the project, the data must be combined and merged with the mobile mapping data and the merged information provided in the appropriate electronic files per the projectâ€™s scope and requested deliverables.
+*When other methods of survey and mapping are also employed for the project, the data must be combined and merged with the mobile mapping data and the merged information provided in the appropriate electronic files per the project's scope and requested deliverables.
@@ Line 201: / Line 201: @@
 **[http://www.dot.ca.gov/hq/row/landsurveys/SurveysManual/Manual_TOC.html CALTRANS Surveys Manual 2011]
 **The Florida DOT document entitled [http://www.dot.state.fl.us/surveyingandmapping/Manuals/20120823_TML_Guidelines.pdf Terrestrial Mobile LiDAR Surveying & Mapping Guidelines, August 23, 2012]
-**Advanced Highway Maintenance and Construction Technology Research Center report entitled [http://ahmct.ucdavis.edu/pdf/UCD-ARR-10-11-30-01.pdf â€œUsing Mobile Laser Scanning to Produce Digital Terrain Models of Pavement Surfacesâ€] prepared by the University of California at Davis Department of Mechanical and Aerospace Engineering for the California DOT, November 30, 2010.
+**Advanced Highway Maintenance and Construction Technology Research Center report entitled [http://ahmct.ucdavis.edu/pdf/UCD-ARR-10-11-30-01.pdf "Using Mobile Laser Scanning to Produce Digital Terrain Models of Pavement Surfaces"] prepared by the University of California at Davis Department of Mechanical and Aerospace Engineering for the California DOT, November 30, 2010.
 {{top}}

@@ Line 59: / Line 59: @@
 **18" long #4 rebar rod with a plastic cap (Preferred & Minimum two per scan)
 **Magnetic Survey Nails (Use in limited access areas) and indented under mag nail to make sure the head of the nail sits flush with the surrounding Asphalt surface.
-***Minimum length in Asphalt is 1Â½â€
+***Minimum length in Asphalt is 1½"
-***Minimum length in Concrete is Â¾â€
+***Minimum length in Concrete is ¾"
 *Uses of Intermediate Control in scans on road types:
 **FREEWAY will require a minimum of 1 (one) Intermediate Control point to be used in every 3rd (Third) scan along the corridor. Exceptions can be made for area with steep inclines to max of 4 (four) scans with MDOT Survey Consultant Project Manager or MDOT Region Surveyor approval.

@@ Line 2: / Line 2: @@
 ==[[#9.1 Static Laser Scanning Standards|9.1 Static Laser Scanning Standards]]==
-*The following guidelines should be followed in order to obtain satisfactory results for MDOT standards.  It is the Surveyorâ€™s / Consultantâ€™s responsibility to discuss targeting, merging, registration, geo-referencing, QA/QC checks, and import into PowerGEOPAK of the scans with the MDOT Survey Consultant Project Manager for the project or the MDOT Region Surveyor before work begins.
+*The following guidelines should be followed in order to obtain satisfactory results for MDOT standards.  It is the Surveyors/Consultants responsibility to discuss targeting, merging, registration, geo-referencing, QA/QC checks, and import into PowerGEOPAK of the scans with the MDOT Survey Consultant Project Manager for the project or the MDOT Region Surveyor before work begins.
 *Scan data must be exported into a format to be used to prepare the DTM surface and Planimetric Data. Point Cloud data and 3D models will be considered as supplements to, and NOT replacements for the required MDOT PowerGEOPAK deliverables.
-*All surveys for control and geo-referencing to support and establish STLS surveys by and for MDOT must meet accuracy standards and follow approved methods as described in [[Chapter_4_-_Survey_-_Types#4.1_Control_Survey|Chapter 4 - Survey Types.]]  Following these standards helps ensure the product deliverables meet MDOT requirements.  It is not MDOTâ€™s intention to limit a companyâ€™s internal practices or the innovation of a company. Input from scanning consultants may be considered for a project, at MDOTâ€™s discretion, to deviate from these guidelines. If appropriate, and at MDOTâ€™s discretion, changes and new methods tested on projects with a good result may be placed in the next update of the standards. All deviations from these standards are required to be explained in the scanning report at the time of submission of the scan data for review.
+*All surveys for control and geo-referencing to support and establish STLS surveys by and for MDOT must meet accuracy standards and follow approved methods as described in [[Chapter_4_-_Survey_-_Types#4.1_Control_Survey|Chapter 4 - Survey Types.]]  Following these standards helps ensure the product deliverables meet MDOT requirements.  It is not MDOT's intention to limit a company's internal practices or the innovation of a company. Input from scanning consultants may be considered for a project, at MDOT's discretion, to deviate from these guidelines. If appropriate, and at MDOT's discretion, changes and new methods tested on projects with a good result may be placed in the next update of the standards. All deviations from these standards are required to be explained in the scanning report at the time of submission of the scan data for review.
 {{top}}
 ===[[#9.1.1 Scanning Project Folder Requirement Information|9.1.1 Scanning Project Folder Requirement Information]]===
 *When scanning is used for data collection, all scanning data must have a separate folder and not a section in the main job portfolio.  See [[Chapter_10_-_Deliverables#10.1.4_Static_Terrestrial_Laser_Scanning_Folder_Structure|Chapter 10 - Deliverables]] for an example of the folder structure
-*A scanning report will be placed in the Scan folder with any notes, or deviations from the standards. The surveyorâ€™s report in the job portfolio must still state that scanning was used, but does not need to be elaborate. A Scanning Report must include at minimum:
+*A scanning report will be placed in the Scan folder with any notes, or deviations from the standards. The surveyor's report in the job portfolio must still state that scanning was used, but does not need to be elaborate. A Scanning Report must include at minimum:
 **The equipment Model, Type, Serial Number, Software, and Version.
 **A discussion about data tolerance issues and errors in creation of DTM, from the registration of the scans and geo-referencing from measured QA/QC checks.
 **Any information pertaining to scanning that will eliminate possible questions.
 *Provide a hand sketched or CAD generated network diagram showing the location and label of each control target, Scanner setup, and related metadata (target heights, target type, etc.).
-*A Scanning Control Point list will be created for Control points used for the scanning project not considered or included in Primary/Intermediate Control list. This file must be an ASCII (P, N, E, and Elev) and associated residuals (Î”N, Î”E, Î”Elev) for each control point must be provided.
+*A Scanning Control Point list will be created for Control points used for the scanning project not considered or included in Primary/Intermediate Control list. This file must be an ASCII (P, N, E, and Elev) and associated residuals ('N, 'E, 'Elev) for each control point must be provided.
 *A copy of the registration residuals between control points of adjacent scan setups must be included in the report.
 *Comparison Spreadsheet showing resulting data coordinates from the scan, check observation coordinates and the coordinate differences. The high and low tolerances must be shown.
@@ Line 35: / Line 35: @@
 *At each scan location and for each scan, hang or place next to each target, a white board with annotation providing the MDOT Job Number, Pt. Name of the target, Date, Scan Name or Number, HI of the target, and any other pertinent information about the point.  This data must be present when the scan and the scanner pictures are collected to assist in processing the project.
 *Environmental conditions (rain) and material being scanned affects the scan quality. Wet pavement conditions and low reflective materials (new bituminous) must be avoided, or will require the maximum distances measured from the scanner to be shortened to meet the minimum density requirement.
-*Any proprietary â€œHomemadeâ€ targets will be required to have a sample to be submitted for acceptance for use. It will also have full documentation (size, shape, materials list, etc...) and have full photographs showing construction and use in field.
+*Any proprietary "Homemade" targets will be required to have a sample to be submitted for acceptance for use. It will also have full documentation (size, shape, materials list, etc...) and have full photographs showing construction and use in field.
-*Any targets approved as â€œProprietaryâ€ must be left on site until approved for removal by the MDOT Survey Consultant Project Manager or the MDOT Region Surveyor.
+*Any targets approved as "Proprietary" must be left on site until approved for removal by the MDOT Survey Consultant Project Manager or the MDOT Region Surveyor.
 **All areas scanned must have an associated high quality digital photograph overlaid on the scans. Note: digital photographs need to be taken in some instances multiple times to eliminate excess obstructions of the area. (i.e. traffic and vehicles).
 *It is recommended that fixed height tripods with standard targets be used for scanning.
@@ Line 56: / Line 56: @@
 **Additional Tie points for registration are always recommended.
 *Control points used for scan targets must be monumented in the field with:
-**Using Main Project Intermediate Control (#5x 36â€ rebar)
+**Using Main Project Intermediate Control (#5x36" rebar)
-**18â€ long #4 rebar rod with a plastic cap (Preferred & Minimum two per scan)
+**18" long #4 rebar rod with a plastic cap (Preferred & Minimum two per scan)
 **Magnetic Survey Nails (Use in limited access areas) and indented under mag nail to make sure the head of the nail sits flush with the surrounding Asphalt surface.
 ***Minimum length in Asphalt is 1Â½â€
@@ Line 66: / Line 66: @@
 **URBAN ARTERIAL AND SINGLE BRIDGE AREAS will require a minimum of 1 (one) Intermediate Control point to be used in every scan. No exceptions can be made for areas with steep inclines
 *At minimum of four hard surface check observations need to exist per scan with overlap. Check shots via total station must be provided to verify the point cloud. The observations do not need to be on a given line, and can reside on a PAVED shoulder or any hard surface that exist in the DTM.
-*The check observations need to reside in a separate segments labeled in the description as â€œScanning QA/QC.â€
+*The check observations need to reside in a separate segments labeled in the description as "Scanning QA/QC."
-*All check points are to be coded as â€œCHKâ€ and be verified they are not part of the DTM surface. Validation elevations should be within 0.05 feet of the calculated DTM.
+*All check points are to be coded as "CHK" and be verified they are not part of the DTM surface. Validation elevations should be within 0.05 feet of the calculated DTM.
 {{top}}

@@ Line 41: / Line 41: @@
 ===[[#9.1.3 Scanning Control and QA/QC|9.1.3 Scanning Control and QA/QC]]===
-*All control points must established via acceptable methods described in [[Chapter_4_-_Survey_-_Types#4.1_Control_Survey|Chapter 4]] of the Survey Standards of Practice.
+*All control points must be established via acceptable methods described in [[Chapter_4_-_Survey_-_Types#4.1_Control_Survey|Chapter 4]] of the Survey Standards of Practice.
 *Elevations to control points must be leveled to NAVD 88.
 *Scan control must be numbered differently than Primary and Secondary control to show geo-referencing points in QA/QC.

@@ Line 136: / Line 136: @@
 '''Specific Application of MTL on MDOT Projects'''
 *Any use of MTL technologies must conform to and utilize the information in this document and the following documents in the preparation of MDOT projects and deliverables:
-**2014 MDOT Standards of Practice for Design Surveys
+**Current MDOT Standards of Practice for Design Surveys
 **[http://onlinepubs.trb.org/onlinepubs/nchrp/nchrp_rpt_748.pdf nchrp_rpt_748.pdf] â€œGuidelines for the Use of Mobile LIDAR in Transportation Applicationsâ€, April 2013
 **Caltrans Survey Manual Chapter 15 Terrestrial Laser Scanning Specifications

@@ Line 30: / Line 30: @@
 ===[[#9.1.2 Scanning Data Requirements|9.1.2 Scanning Data Requirements]]===
 *Individual points should have a final scan density spacing not exceed 0.1 ft. on structures and not exceed 0.3 ft. on road surfaces.
-*The Geo-referenced point cloud proprietary database must be provided as part of the deliverables and in addition, an electronic ASCII comma delimited file X, Y, Z format, and intensity. If Geo-referenced database has the ability to view independent original data, separate copies of scans may be omitted.
+*The Geo-referenced point cloud proprietary database must be provided as part of the deliverables in a las/laz file format or in a POD file format. If Geo-referenced database has the ability to view independent original data, separate copies of scans may be omitted.
 *The scanner must not exceed a maximum of 500 feet between setup positions (Scanner dependent and provided Item 2.a is met.)
 *Scan setups must overlap by a minimum of 20%.

@@ Line 23: / Line 23: @@
 *Documentation of any changes from standards approved by the MDOT Survey Consultant Project Manager or the MDOT Region Surveyor.
 *A copy of each original scan must be provided on CDs, DVDs or USB high-speed peripheral devices. Each item will be labeled with the Job Number and scan data label.
-*Copies of the database in native format as well as an XYZ format (ASCII text file) must be provided.
+*Copies of the database in a las/laz file format or a POD file format must be provided.
 {{top}}
 {{top}}
 ===[[#9.1.2 Scanning Data Requirements|9.1.2 Scanning Data Requirements]]===
 *Individual points should have a final scan density spacing not exceed 0.1 ft. on structures and not exceed 0.3 ft. on road surfaces.