Woolpert, Inc.20100917UnknownMI_Tri-County_LiDAR_Tiles_HARNvector digital dataU:\PH\70400_TriCounty_MI_LiDAR_2010\Lidar\output\5_Final_Deliverables\Metadata\TriCounty_ArcGrid_DEM.xml
TASK NAME: Michigan Tri-County LiDAR (ARRA Lidar Task Order)
LiDAR Data Acquisition and Processing Production Task
USGS CONTRACT: G10PC00057
TASK ORDER NUMBER: G10PD00844
CONTRACTOR: Woolpert, Inc.
LiDAR data is a remotely sensed high resolution elevation data collected by an airborne platform. The LiDAR sensor uses a combination of laser range finding, GPS positioning, and inertial measurment technologies.The LiDAR systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. This data was collected at a resolution of one and one half point point per square meter. The final products include first, last, and at least one intermediate return LAS, a bare earth model, and intensity data in separate files.
This task order consisted of LiDAR data acquisition and processing for Clinton, Eaton and Ingham Counties in southeastern Michigan. The task order area of interest encompasses approximately 1,810 square miles. The task required the LiDAR data to be collected at a minimum of one and one half (1.5) point per square meter (1.5 meter GSD). The LiDAR data was collected to meet a vertical accuracy requirement of 15.0 cm (0.49 ft) RMSE, or better, so that when combined with breaklines, the data adequately supports the generation of two (2) foot FEMA compliant contours. The final LiDAR data was delivered as 5,000' x 5,000' tiles, aligned to even 5,000' coordinates.
USGS CONTRACT: G10PC00057
TASK ORDER NUMBER: G10PD00844
CONTRACTOR: Woolpert Inc.
The reflective surface data represents the DEM created by the laser energy reflected from the first surface encountered by the laser pulse. Some energy may continue beyond this initial surface, to be reflected by a subsequent surface as represented by the last return data. Intensity information is captured from the reflective surface pulse and indicates the relative energy returned to the sensor, as compared to the energy transmitted. The intensity image is not calibrated or normalized but indicates differences in energy absorption due to the the interaction of the surface materials with laser energy, at the wavelength transmitted by the sensor. The bare earth model is created by identifying the returns that fall on the ground surface and by interpolating a surface between these points. In this manner, buildings and vegetation are removed from the bare earth model. This data set does not include bridges and overpasses in the bare earth model as the delineation point for these structures is not reliably discernable in the LiDAR data.
2010040220100403201004042010040520100410201004122010041320100414REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.ground conditionAs needed-85.109774-84.11700143.13268942.403153NoneLiDARMichiganClinton, Eaton and Ingham CountiesNo restrictions apply to this data.No restrictions apply to this data.USGSNational Geospatial Technical Operations Centermailing and physical address1400 Independence RoadRollaMO65401USA(573) 308-3667(573) 308-36457:30 a.m. to 4:00 p.m. Central TimeClinton, Eaton and Ingham CountiesArc Grid FilesCGMUnclassifiedUnclassifiedUnclassifiedMicrosoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.1.1850USGSUnpublished MaterialMichigan Tri-County LiDAR (ARRA Lidar Task Order)mapThe LiDAR collected for this task order was collected at a vertical accuracy of 15.0 cm (0.49 ft) Root Mean Squared (RMSE), or better, so that when combined with breaklines, it will adequately support the generation of two (2) foot FEMA compliant contours.15.0 cm (0.49 ft) RMSEPoints measured will produce an error less than 15.0 cm (0.49 ft) RMSE.All formatted data are validated using commercial GIS software to ensure proper formatting and loading prior to delivery.The LIDAR data is visually inspected for completeness to ensure that are no gaps between flight lines.Horizontal accuracy is +/- 3.8-foot at the 95% confidence level using RMSE(r) x 1.9600 as defined by the FGDC Geospatial Positional Accuracy Standards, Part 3: NSSDA.3.8LiDAR system calibration is available in the project report.
The LiDAR data vertical accuracy RMSE is 0.28 ft.
The data collected under this Task Order meets the National Standard for Spatial Database Accuracy (NSSDA) accuracy standards. The NSSDA standards specify that vertical accuracy be reported at the 95 percent confidence level for data tested by an independent source of higher accuracy. (http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part3/index_html).
The Fundamental Vertical Accuracy (FVA) of the TIN: 8.65 cm (0.28 ft) at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 18.5 cm in the "open terrain" land cover category. This data set tested to 0.28 ft.
The Consolidated Vertical Accuracy (CVA): 31.5 cm (1.03 ft) at a 95% confidence level, derived according to ASPRS Guidelines, Vertical Accuracy Reporting for LiDAR Data, i.e., based on the 95th percentile error in all land cover categories combined. This data set tested to 0.53 ft. for all categoires.
0.28Tested 0.28 feet vertical accuracy at 95 percent confidence level.USGS20090831UnknownLiDAR Data Collectionmapdisc2010040220100403201004042010040520100410201004122010041320100414ground conditionLiDARThe LiDAR data collected for this task order.Using a LH Systems ALS50 Light Detection And Ranging (LiDAR) system, 68 flight lines of high density data, one and one half point per square meter, were collected over Clinton, Eaton and Ingham Counties (approximately 1,810 square miles). Multiple returns were recorded for each laser pulse along with an intensity value for each return. A total of eight missions were flown over a 12 day period: April 02, 2010 through April 14, 2010. A minimum of two airborne global positioning system (GPS) base stations were used in support of the LiDAR data acquisition. The mean baseline length was 28 miles, with a maximum baseline length of 52 miles. In addition, 31 ground control points were surveyed through static methods. The geoid used to reduce satellite derived elevations to orthometric heights was Geoid03. All data for the task order is referenced to Michigan State Plane South Zone (2113), NAD83/2007, NAVD88, in international feet. Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a smoothed best estimate of trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. The coverage was classified to extract a bare earth digital elevation model (DEM) and separate last returns. Two layers of coverage were delivered in the ArcINFO ArcGrid binary format: bare-earth and intensity. System Parameters: - Type of Scanner = LH Systems ALS50 - Data Acquisition Height = 7,800-feet AGL - Scanner Field of View = 40 degrees - Scan Frequency = 35.3 Hertz - Pulse Repetition Rate - 99.0 Kilohertz - Aircraft Speed = 130 Knots - Swath Width = 5,200-feet - Number of Returns Per Pulse = Maximum of 4 - Distance Between Flight Lines = 4,200-feet201004141200Woolpert, Inc.Photogrammetry and Remote Sensingmailing and physical address4454 Idea Center BlvdDaytonOH45430USA(937) 461.5660(937) 461-07438:00 a.m. to 5:00 p.m. Eastern TimeThe ALS50 calibration and system performance is verified on a periodic basis using Woolpert's calibration range. The calibration range consists of a large building and runway. The edges of the building and control points along the runway have been located using conventional survey methods. Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position of the building edges between opposing flight lines. The scanner scale factor and vertical accuracy is calculated through comparison of LiDAR data against control points along the runway. Field calibration is performed on all flight lines to refine the IMU misalignment angles. IMU misalignment angles are calculated from the relative displacement of features within the overlap region of adjacent (and opposing) flight lines. The raw LiDAR data is reduced using the refined misalignment angles.201009171200Woolpert, Inc.Photogrammetry and Remote Sensingmailing and physical address4454 Idea Center BlvdDaytonOH45430USA(937) 461-5660(937) 461-07438:00 a.m. to 5:00 p.m. Eastern TimeOnce the data acquisition and GPS processing phases are complete, the LiDAR data was processed immediately to verify the coverage had no voids. The GPS and IMU data was post processed using differential and Kalman filter algorithms to derive a best estimate of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the project.201009171200Woolpert, Inc.Photogrammetry and Remote Sensingmailing and physical address4454 Idea Center BlvdDaytonOH45430USA(937) 461-5660(937) 461-07438:00 a.m. to 5:00 p.m. Eastern TimeThe individual flight lines were inspected to ensure the systematic and residual errors have been identified and removed. Then, the flight lines were compared to adjacent flight lines for any mismatches to obtain a homogenous coverage throughout the project area. The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" LiDAR returns. This process determined bare-earth points (Class 2), Noise (Class 7), Water (Class 9) Ignored ground (Class 10) and unclassified data (Class 1). The bare-earth (Class 2 - Ground) LiDAR points underwent a manual QA/QC step to verify that artifacts have been removed from the bare-earth surface. The surveyed ground control points are used to perform the accuracy checks and statistical analysis of the LiDAR dataset.201009171200Woolpert, Inc.Photogrammetry and Remote Sensingmailing and physical address4454 Idea Center BlvdDaytonOH32817USA(937) 461-5660(937) 461-07438:00 a.m. to 5:00 p.m. Eastern TimeMetadata imported.U:\PH\70400_TriCounty_MI_LiDAR_2010\Lidar\output\5_Final_Deliverables\Metadata\TriCounty_TileLayout.shp.xml2010091608565100Dataset copied.U:\PH\70400_TriCounty_MI_LiDAR_2010\Lidar\layout\Shapefile\MI_Tri-County_LiDAR_Tiles_HARN20100916085811000VectorSimpleFALSE0FALSEFALSEcoordinate pair0.0000000.000000international feetD_North_American_1983_HARNGeodetic Reference System 806378137.000000298.257222North American Vertical Datum of 19880.000100metersExplicit elevation coordinate included with horizontal coordinates_001_clipArc Grid Files for the Michigan Tri-County liDAR (ARRA LiDAR Task Order)Woolpert, Inc.Feature Class0FIDFIDOID400Internal feature number.EsriSequential unique whole numbers that are automatically generated.ShapeFeature geometry.ESRICoordinates defining the features.ShapeGeometry000GROUPIDGROUPIDString500Shape_LengShape_LengDouble1900Shape_AreaArea of feature in internal units squared.ESRIPositive real numbers that are automatically generated.Shape_AreaDouble1900USGSNational Geospatial Technical Operations Centermailing and physical address1400 Independence RoadRollaMO65401USA(573) 308-3667(573) 308-36457:30 a.m. to 4:00 p.m. Central TimeDownloadable DataNone.Shape File1.0Feature ClassFeature Classno compression applied1.0CD-ROMDigitalNone.unknown20100916USGSREQUIRED: The person responsible for the metadata information.National Geospatial Technical Operations Centermailing and physical address1400 Independence RoadRollaMO65401USA(573) 308-3667(573) 308-36457:30 a.m. to 4:00 p.m. Central TimeFGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998local timeUnclassifiedUnclassifiedUnclassifiedMicrosoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; ESRI ArcGIS 10.0.3.3600_001_clip12925001.19107813190001.629834595000.629415329999.7821971-85.109774-84.11700143.13268942.4031531ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002file://\\ph40nsx5\v5$\PH\70400_TriCounty_MI_LiDAR_2010\Lidar\output\5_Final_Deliverables\Tile_Layout_Shp\MI_Tri-County_LiDAR_Tiles_HARNLocal Area Network0.279ShapefileFile Geodatabase Feature Class0.000NAD_1983_HARN_StatePlane_Michigan_South_FIPS_2113_Feet_IntlEPSG7.4.1020130328Contours_Index0020.000file://\\LAURA\D$\GIS\Data\Contours_BldgFtPrint_MSU_2013\Contour_Shapefiles\Contours_Index.shpLocal Area NetworkProjectedGCS_North_American_1983Linear Unit: Foot (0.304800)NAD_1983_StatePlane_Michigan_South_FIPS_2113_Feet_Intl<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.1'><WKT>PROJCS["NAD_1983_StatePlane_Michigan_South_FIPS_2113_Feet_Intl",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",13123359.58005249],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-84.36666666666666],PARAMETER["Standard_Parallel_1",42.1],PARAMETER["Standard_Parallel_2",43.66666666666666],PARAMETER["Latitude_Of_Origin",41.5],UNIT["Foot",0.3048],AUTHORITY["EPSG",2253]]</WKT><XOrigin>-107138600</XOrigin><YOrigin>-97193800</YOrigin><XYScale>37448250.484633707</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.0032808398950131233</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>2253</WKID><LatestWKID>2253</LatestWKID></ProjectedCoordinateSystem>CopyFeatures D:\GIS\Data\Contours_BldgFtPrint_MSU_2013\Tri_County.gdb\Contours_Index D:\GIS\Data\Contours_BldgFtPrint_MSU_2013\Contour_Shapefiles\Contours_Index.shp # 0 0 020131106101611002013110610161100