20221110
09270200
1.0
FGDC CSDGM Metadata
FALSE
CreateMosaicDataset "Database Connections\DEVGISStaging_gisras1_owner.sde" DEM2017_small "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]];-107138600 -97193800 3048;-100000 10000;-100000 10000;3.28083989501312E-03;0.001;0.001;IsHighPrecision" # # NONE #
AddRastersToMosaicDataset "Database Connections\DEVGISStaging_gisras1_owner.sde\gisras1.OC.DEM2017_small" "Raster Dataset" \\gisfs1p\Orthos\Lidar_2017\DEM\302492.img UPDATE_CELL_SIZES UPDATE_BOUNDARY NO_OVERVIEWS # 0 1500 # # SUBFOLDERS ALLOW_DUPLICATES NO_PYRAMIDS NO_STATISTICS NO_THUMBNAILS # NO_FORCE_SPATIAL_REFERENCE NO_STATISTICS #
ColorBalanceMosaicDataset "Database Connections\DEVGISStaging_gisras1_owner.sde\gisras1.OC.DEM2017_small" DODGING SINGLE_COLOR # # NONE 1 #
CalculateStatistics "Database Connections\DEVGISStaging_gisras1_owner.sde\gisras1.OC.DEM2017_small" 1 1 # OVERWRITE "Feature Set"
file://\\gisfs1p\Orthos\Lidar_2017\DEM2017.gdb
Local Area Network
gisras1.OC.DEM2017
13302500.000000
13472500.000000
340000.000000
510000.000000
1
Projected
GCS_North_American_1983
Linear 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.4'><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>
32
FALSE
None
1
AMD
TRUE
continuous
floating point
4100
15000
1000
20
2048
20
75
0.01
10
600
300
Basic
1
NorthWest,Center,LockRaster,ByAttribute,Nadir,Viewpoint,Seamline,None
None,JPEG,LZ77,LERC
None
None,Basic,Base-Top Height,Top-Top Shadow Height,Base-Top Shadow Height,3D
0
-1
0.8
1
NorthWest,Center,LockRaster,ByAttribute,Nadir,Viewpoint,Seamline,None
None,JPEG,LZ77,LERC
None,Basic,Full
NONE
Name,MinPS,MaxPS,LowPS,HighPS,Tag,GroupName,ProductName,CenterX,CenterY,ZOrder,Shape.STArea(),Shape.STLength()
72900
2
1458
20180523
14393000
20180523
14393000
1200
1200
Shawn Benham
Sanborn Map Co
Project Manager
719.502.1296
1935 Jamboree Dr
Colorado Springs
CO
80920
U.S.A.
sbenham@sanborn.com
8:00 AM - 5:00 PM
ArcGIS Metadata
1.0
Everett Root
State of Michigan
Manager, Geodata Services Section
517-335-7180
111 S. Capitol Ave
10th Floor Romney
Lansing
MI
48933
U.S.A.
roote@michigan.gov
8:00 AM - 5:00 PM
unknown
2017-01-01
State of Michigan
unknown
LAS
1.4
2000
http://www.michigan.gov
unknown
2000
Michigan 2017 LiDAR project
http://www.michigan.gov
EnterpriseDEM2017ImageService
2017-01-01
1.0
State of Michigan
Michigan
State of Michigan (SOM)
raster digital data
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This metadata record describes the hydro-flattened bare earth digital elevation model (DEM) derived from the classified LiDAR data for the 2017 Michigan LiDAR project covering approximately 907 square miles, in which its extents cover Oakland County.</SPAN></P></DIV></DIV></DIV>
This metadata record describes the hydro-flattened bare earth digital elevation model (DEM) derived from the classified LiDAR data for the 2017 Michigan LiDAR project covering approximately 907 square miles, in which its extents cover Oakland County.
Everett Root
State of Michigan
Manager, Geodata Services Section
517-335-7180
10th Floor Romney
111 S. Capitol Ave
Lansing
MI
48933
U.S.A.
roote@michigan.gov
8:00 AM - 5:00 PM
MI
Oakland
United States
Michigan
2017
MI
Water points
Contour
First Return
Intensity return
Overlap points
Ground points
LAS
Digital Elevation Model (DEM)
Digital Terrain Model (DTM)
point cloud
mapping
Bare Earth
ALS70
IMG
Grid
Digital Surface Model (DSM)
Unclassified points
LiDAR
Water points
Contour
First Return
Oakland
United States
Intensity return
Overlap points
Ground points
LAS
Michigan
Digital Elevation Model (DEM)
Digital Terrain Model (DTM)
2017
point cloud
mapping
Bare Earth
ALS70
IMG
Grid
Digital Surface Model (DSM)
Unclassified points
LiDAR
The State of Michigan Geographic Information Systems digital data have been tested and their documentation carefully reviewed. However, the State of Michigan and its representatives make no warranty or representation, either expressed or implied, with respect to the digital data and their documentation, their quality, performance, merchantability, or fitness for a particular purpose. The digital data are distributed on "as is" basis, and the user assumes all risk to their quality, the results obtained from their use, and the performance of the data. In no event will the State of Michigan or its representatives be liable for any direct, indirect, special, incidental or consequential damages resulting from and defect in the State of Michigan or in their documentation. This disclaimer of warranty is exclusive and in lieu of all others, oral or written, express or implied. No agent or employee is authorized to make any modification, extension, or addition to this warranty.
unknown
unknown
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This data is for planning purposes only and should not be used for legal or cadastral purposes. Any conclusions drawn from analysis of this information are not the responsibility of Sanborn Map Company. Users should be aware that temporal changes may have occurred since this dataset was collected and some parts of this dataset may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of its limitations. Contact: State of Michigan</SPAN></P></DIV></DIV></DIV>
ground condition
2017-03-29
2017-05-03
-83.68924
-83.07976
42.425409
42.883532
The raw raster tiles were imported into a mosaic and re-projected into the County's standard projection from the following original project projection: Datums and Units. Projection - State Plane Michigan South. Horizontal datum - North American Datum of 1983 (NAD83 (2011)). Vertical datum - North American Vertical Datum of 1988 (NAVD88) using the latest geoid (Geoid12B) for converting ellipsoidal heights to orthometric heights. Units - intl feet
Version 6.2 (Build 9200) ; Esri ArcGIS 10.4.1.5686
1
-83.703082
-83.063686
42.897504
42.425611
LiDAR data is collected within the project area and processed. After all of the deliverables were created, the dataset was verified against control. The control points were compared to the following counties and reported as one accuracy assessment: Tuscola, Huron, Sanilac, St Clair, Macomb, Oakland, Jackson, Washtenaw, Wayne, Hillsdale, Lenawee, Monroe.
LiDAR data is collected for the project area. Post processing of the simultaneously acquired GPS/INS is performed and applied to the laser returns to output a point cloud in the specified project coordinate system and datums. The point cloud data is then subjected to automated classification routines to assign all points in the point cloud to ground, water, overlap and unclassified point classes. Anomalous laser returns that occur infrequently are removed entirely from the data set. Once clean bare earth points are established, DEMs are created using bare earth points and hydro features. The DEM surface is then compared to the survey checkpoints. These accuracies must pass the Non-Vegetated and Vegetated Vertical Accuracy Specifications.
12 Counties: The LiDAR surface was evaluated using a collection of 185 GPS surveyed checkpoints for the raw NVA report. The surface was compared to this checkpoint class yielding a better result than was required for the project. Raw NVA Control Accuracy Report (feet) --------- Report Disclaimer --------- This report does not guarantee accuracy. The report only reflects one statistical representation of the control points, LIDAR data and surface used. This report does not replace a through quality control process. --------- Report Summary --------- Average dz +0.010 Minimum dz -0.598 Maximum dz +0.615 Average magnitude 0.170 Root mean square 0.217 Std deviation 0.217 ---------------------------------------------------------------------------------------- Attribute accuracy is tested after the LiDAR processing stage. After classification of the LiDAR data, DEMs are created using the bare earth points. The NVA and VVA reports are generated from the comparison of the DEM and the ground control collected within the project area. The DEM surface was evaluated using a collection of 185 GPS surveyed checkpoints for the NVA report. The DEM was compared to this checkpoint class yielding a better result than was required for the project. NVA Control Accuracy Report (feet) --------- Report Disclaimer --------- This report does not guarantee accuracy. The report only reflects one statistical representation of the control points, LIDAR data and surface used. This report does not replace a through quality control process. --------- Report Summary --------- Average dz -0.010 Minimum dz -0.598 Maximum dz +0.615 Average magnitude 0.172 Root mean square 0.216 Std deviation 0.217 ---------------------------------------------------------------------------------------- Attribute accuracy is tested after the LiDAR processing stage. After classification of the LiDAR data, DEMs are created using the bare earth points. The VVA report is generated from the comparison of the DEM and the ground control collected within the project area. The DEM was evaluated using a collection of 132 GPS surveyed checkpoints. The DEM was compared to this checkpoint class yielding a better result than was required for the project. VVA Control Accuracy Report (feet) --------- Report Disclaimer --------- This report does not guarantee accuracy. The report only reflects one statistical representation of the control points, LIDAR data and surface used. This report does not replace a through quality control process. --------- Report Summary --------- Average dz +0.187 Minimum dz -0.576 Maximum dz +1.041 Average magnitude 0.276 Root mean square 0.346 Std deviation 0.292 ----------------------------------------------------------------------------------------
Horizontal positional accuracy for Oakland is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture. The standard system results for horizontal accuracy meet or exceed the project specified 1.0 meter RMSE.
This value is computed by comparing ground control to a DEM derived from the classified LiDAR data and represents the RMSE of residuals on controls within the project area.
1.0
For the DEM data derived from the classified point cloud, the NVA and VVA were computed. The vertical accuracy was tested with independent survey check points located in various terrain types within the 12 county control area. These check points were not used in the calibration or post processing of the lidar point cloud data. The survey check points were distributed throughout the block area. Specifications for this project require that the NVA be 19.6 cm or better @ 95 percent confidence level.
The raw NVA was tested using 185 independent survey check points located in flat terrain types within the 12 county area. The survey checkpoints were distributed throughout the block area. The 185 independent check points were surveyed using static GPS base stations collecting point location for 20 minute intervals. Elevations were measured for the x,y,z location of each check point. Elevations interpolated from the surface were then compared to the elevation values of the surveyed control. The RMSEz was computed to be 0.066m. AccuracyZ has been tested to meet 10 cm Nonvegetated Vertical Accuracy at 95 Percent confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines.
0.066m RMSEz, or 0.13m NVA @ 95 percent Confidence Level
The post processed lidar data has been projected and oriented in the specified coordinate system as an un-classified point cloud.
1200
Post processed lidar
LAS
1.0
Sanborn Map Company Inc.
Point digital data
ground condition
2017-01-01
Targeted ground control is used to create a digital control file and control report as well as QC check of LiDAR accuracy. Predefined points (NGS when available) within the project area are targeted.
Ground control
CONT
2010-01-01
1.0
None
None
Sanborn Map Company Inc.
tabular digital data
Ground condition
2017-01-01
The classified lidar point cloud is used to derive various data products such as, but not limited to, bare earth gridded DEM, triangulated irregular networks (TIN), contours, digital surface models (DSM). The output format is fully compliant LAS v1.4, Point Record Format 6
1200
Classified lidar
LAS
1.0
Sanborn Map Company Inc.
Point digital data
ground condition
2017-01-01
Aerial LiDAR and GPS/IMU data are recorded for the defined project area at an altitude, flight speed, scanner swath width and scanner pulse frequency to achieve the design goals of the project.
LiDAR Data
LIDAR and GPS_RAW
1.0
None
None
Sanborn Map Company Inc.
Remote sensing image
ground condition
2017-01-01
Post processed GPS/INS is applied to the lidar point data to georeference each point in the project coordinate system
1200
Post processed GPS/INS
GPS
1.0
Sanborn Map Company Inc.
Tabular digital data
Ground condition
2017-01-01
The tile definition defines discreet non-overlapping rectangular areas used as cut lines to break up the large classified lidar dataset into smaller, more manageable data tiles. Each tile is 2500ft by 2500ft in dimension.
1200
Tile Definition
TLDEF
1.0
State of Michigan
raster digital data
ground condition
2017-01-01
The post processed GPS/INS solution is applied to the raw lidar data to orient and project the data points into the project area reference system as an unclassified point cloud.
2017-01-01
LIDAR, GPS_SOL
LAS
The bare earth points of the processed lidar data are then output to a DEM tile format. The DEM is compared to the ground control and elevation differences between the surface and surveyed elevation are recorded in tabular form. Vertical accuracy statistics are then developed to produce vertical RMSE and overall accuracy estimates and reports.
2017-01-01
CONT, LIDAR
None
At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets.
2017-01-01
None
CONT
The georeferenced lidar data is then classified and edited in Terrasolid Terrascan software. Data is classified to produce: Class 1: unclassified, Class 2: ground, Class 7: low point, Class 9: water, Class 10: ignored ground, Class 11: withheld.
2017-01-01
CONT, GPS_SOL, LIDAR
LAS
New LiDAR data is captured for the project area using a Leica ALS70 w/MPiA LiDAR instrument an integrated IPAS20 GPS/INS system mounted within a Aero Commander twin engine airplane.
2017-01-01
None
LIDAR, GPS_RAW
The airborne GPS data is post-processed in Intertial Explorer software and LEICA CloudPro software to determine the LiDAR sensor's angle and orientation in the terrain (project) coordinate system and datums during the survey.
2017-01-01
GPS_RAW
GPS_SOL
85000
2.000000
85000
2.000000
2
1
0
13302500.000000 340000.000000
13302500.000000 510000.000000
13472500.000000 510000.000000
13472500.000000 340000.000000
13387500.000000 425000.000000
Band_1
1289.555786
594.921326
32
Bare Earth only
Classes:
2 - Bare-Earth Ground
USGS Base Specification 1.2, QL2 meeting 19.6 cm NVA
EPSG
5.3(9.0.0)
20180523