gov.noaa.nmfs.inport:55534
eng
UTF8
dataset
Elevation
OCM Partners
resourceProvider
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
pointOfContact
2024-02-29T00:00:00
ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data
ISO 19115-2:2009(E)
2
row
1250
2
point
1
Oceana County - Michigan Lidar DEM 2017
2017 Lidar: Oceana, MI 8662
2017
publication
NOAA/NMFS/EDM
55534
https://www.fisheries.noaa.gov/inport/item/55534
WWW:LINK-1.0-http--link
Full Metadata Record
View the complete metadata record on InPort for more information about this dataset.
information
https://coast.noaa.gov/
WWW:LINK-1.0-http--link
NOAA's Office for Coastal Management (OCM) website
Information on the NOAA Office for Coastal Management (OCM)
download
https://coast.noaa.gov/dataviewer/
WWW:LINK-1.0-http--link
NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV)
The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer.
download
mapDigital
This metadata record describes the lidar-based digital elevation model (DEM) for the 2017 Michigan LiDAR project covering approximately 512 square miles, covering Oceana County.
To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments, and hydrologic modeling. LAS data products are suitable for 1 foot contour generation. USGS LiDAR Base Specification 1.2, QL2. 19.6 cm NVA.
State of Michigan (SOM)
completed
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
pointOfContact
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
custodian
unknown
https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/MI_31Co-Oceana_2017_8662/data_extent_oceana_m8662.kmz
This graphic displays the footprint for this lidar data set.
KML
EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION
EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION
theme
Global Change Master Directory (GCMD) Science Keywords
17.0
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA
VERTICAL LOCATION > LAND SURFACE
place
Global Change Master Directory (GCMD) Location Keywords
17.0
LIDAR > Light Detection and Ranging
instrument
Global Change Master Directory (GCMD) Instrument Keywords
17.2
Airplane > Airplane
platform
Global Change Master Directory (GCMD) Platform Keywords
17.2
ALS70
Bare Earth
Intensity return
Overlap points
ground points
mapping
Michigan
Oceana, Mason
United States
theme
MI
DEM
theme
DEMs - partner (no harvest)
project
InPort
otherRestrictions
Cite As: OCM Partners, [Date of Access]: Oceana County - Michigan Lidar DEM 2017 [Data Date Range], https://www.fisheries.noaa.gov/inport/item/55534.
NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose.
otherRestrictions
Access Constraints: None
otherRestrictions
Use Constraints: Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations.
otherRestrictions
Distribution Liability: 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.
Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners
unclassified
2016 - 2017 NRCS 30 County MI Lidar
NOAA/NMFS/EDM
55315
crossReference
NOAA Data Management Plan (DMP)
NOAA/NMFS/EDM
55534
https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/55534.pdf
WWW:LINK-1.0-http--link
NOAA Data Management Plan (DMP)
NOAA Data Management Plan for this record on InPort.
information
crossReference
grid
2
eng; US
elevation
Microsoft Windows 7; ESRI ArcCatalog 9.3.1.1850
-86.539744
-86.035556
43.463623
43.81499
| Currentness: Ground Condition
2017-04-08
2017-04-09
The following are the USGS lidar fields in JSON of the original input files:
{
"ldrinfo" : {
"ldrspec" : "USGS Base Specification 1.2, QL2 meeting 19.6cm NVA",
"ldrsens" : "Leica ALS70",
"ldrmaxnr" : "4",
"ldrnps" : "0.67",
"ldrdens" : "2.2",
"ldranps" : "0.67",
"ldradens" : "2.2",
"ldrfltht" : "2345",
"ldrfltsp" : "130",
"ldrscana" : "38",
"ldrscanr" : "47.3",
"ldrpulsr" : "235",
"ldrpulsd" : "10",
"ldrpulsw" : "0.53",
"ldrwavel" : "1064",
"ldrmpia" : "1",
"ldrbmdiv" : "0.3",
"ldrswatw" : "1615",
"ldrswato" : "30",
"ldrcrs" : "NAD_1983_2011_StatePlane_Michigan_South_FIPS_2113_Ft_Intl",
"ldrgeoid" : "NGS Geoid12B"
},
"ldraccur" : {
"ldrchacc" : "0",
"rawnva" : "0.176",
"rawnvan" : "58",
"clsnva" : "0.178",
"clsnvan" : "58",
"clsvva" : "0.191",
"clsvvan" : "48"
},
"lasinfo" : {
"lasver" : "1.4",
"lasprf" : "6",
"laswheld" : "Withheld points were identified in these files with the withheld flag",
"lasolap" : "Overlap points were identified in these files with the overlap flag",
"lasintr" : "16",
"lasclass" : {
"clascode" : "1",
"clasitem" : "Unclassified"
},
"lasclass" : {
"clascode" : "2",
"clasitem" : "Bare earth"
},
"lasclass" : {
"clascode" : "7",
"clasitem" : "Noise"
},
"lasclass" : {
"clascode" : "9",
"clasitem" : "Water"
},
"lasclass" : {
"clascode" : "10",
"clasitem" : "Ignored Ground (Breakline Proximity)"
},
"lasclass" : {
"clascode" : "17",
"clasitem" : "Bridges"
},
"lasclass" : {
"clascode" : "18",
"clasitem" : "High Noise"
}
}}
false
eng
false
USGS Base Specification 1.2, QL2 meeting 19.6 cm NVA
GeoTIFF
NOAA Office for Coastal Management
(843) 740-1202
2234 South Hobson Ave
Charleston
SC
29405-2413
coastal.info@noaa.gov
https://coast.noaa.gov
WWW:LINK-1.0-http--link
NOAA Office for Coastal Management Website
NOAA Office for Coastal Management Home Page
information
distributor
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8662
WWW:LINK-1.0-http--link
Customized Download
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base.
download
https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/MI_31Co-Oceana_2017_8662/index.html
WWW:LINK-1.0-http--link
Bulk Download
Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document.
download
dataset
Horizontal Positional Accuracy
Horizontal positional accuracy for Oceana 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. Qualitative value: 1.0, Test that produced the valued: For Oceana, 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.
Vertical Positional Accuracy
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 Oceana. 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.
Qualitative value: 0.090m RMSE, or 0.176m NVA @ 95 percent Confidence Level 0.091m RMSE, or 0.178m NVA @ 95 percent Confidence Level 0.089m RMSE, or 0.191m VVA @ 95th Percentile, Test that produced the value: The raw NVA was tested using 58 independent survey check points located in flat terrain types within the Oceana. The survey checkpoints were distributed throughout the block area. The 58 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 DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.088 m. 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. The NVA was tested using 58 independent survey check points located in bare earth terrain types within the Oceana. The 58 independent check points contained all NVA points and 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 DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.091m, or 0.178m @ 95 percent confidence level defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines. The VVA was tested using 48 independent survey check points located in various vegetation terrain types within the Oceana. The 48 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 DEM surface were then compared to the elevation values of the surveyed control. The RMSE was computed to be 0.093m, or 0.196m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.
Completeness Report
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.
Conceptual Consistency
LiDAR data is collected within the project area and processed. After the DEMs were created, the dataset was verified against control. The control points for Oceana were collected as part of a larger control area that includes Mason County
Lidar data were collected via an airborne platform and lidar sensor. They were then processed to a classified point cloud and finally a digital elevation model.
At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets.
2017-01-01T00:00:00
New LiDAR data is captured for the project area using a Leica ALS70 LiDAR instrument an integrated IPAS20 GPS/INS system mounted within a Aero Commander twin engine airplane.
2017-01-01T00:00:00
The airborne GPS data is post-processed in Inertial 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-01T00:00:00
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-01T00:00:00
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-01T00:00:00
The classified lidar data is exported as 2500 X 2500 foot tiles in the LAS format with any or all classes required to produce derivative products.
2017-01-01T00:00:00
Bare-earth points from the classified lidar were interpolated to create a digital elevation model (DEM). The area was tiled with 1250 x 1250 pixel tiles at 2-foot pixel size.
Data were downloaded from the USGS Rocky ftp site in NAD83(2011) Michigan South State Plane (ft) coordinates with vertical feet NAVD88 (Geoid12b). Data were in individual zip files for each DEM tile. The tiles were unzipped to allow ingestion into the Digital Coast Data Access Viewer. The Data Access Viewer may change the georeferencing to meet user requests and those changes should be shown in subsequent process steps.
2018-12-18T00:00:00
Office for Coastal Management
processor
Source Contribution: 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
Sanborn Map Company Inc.
originator
2017
DEM
Sanborn Map Company Inc.
originator
Source Contribution: 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
2010-01-01
publication
Sanborn Map Company Inc.
originator
2017
Source Contribution: 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
Sanborn Map Company Inc.
originator
2017
Source Contribution: 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
Sanborn Map Company Inc.
originator
2017
Source Contribution: 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
Sanborn Map Company Inc.
originator
2017
Source Contribution: 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
State of Michigan
originator
2017