2016 FEMA Lidar: Michigan - Part 1
OCM Partners
Data Set
(DS)
| ID: 67239
| Published / External
Created: 2022-05-13
|
Last Modified: 2023-03-15
Project (PRJ) | ID: 49401
ID: 67239
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2016 FEMA Lidar: Michigan - Part 1 |
---|---|
Short Name | mi2016_part1_m9500_metadata |
* Status | Completed |
Creation Date | 2016 |
Revision Date | |
• Publication Date | 2016 |
* » Abstract |
This metadata supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services. The State of Michigan (DTMB) contracted with Sanborn to provide LiDAR mapping services for 10 counties in the State of Michigan. These counties include Clare, Lake, Mecosta, Missaukee, Montcalm, Muskegon, Newaygo, Osceola, Roscommon, and Wexford. Utilizing multi-return systems, Light Detection and Ranging (LiDAR) data in the form of 3-dimensional positions of a dense set of mass points was collected for the 10 counties in April and May of 2016. LAS data products are suitable for 1 foot contour generation. USGS LiDAR Base Specification 1.2, QL2. 19.6 cm NVA. Clare County: data covers approximately 575 square miles Lake County: data covers approximately 573 square miles Mecosta County: data covers approximately 571 square miles Missaukee County: data covers approximately 574 square miles Montcalm County: data covers approximately 721 square miles Muskegon County: This county is available from a different data set, see the links in the URL section of this metadata record for the metadata and custom download. Newaygo County: data covers approximately 826 square miles Osceola County: data covers approximately 573 square miles Roscommon County: data covers approximately 580 square miles Wexford County: data covers approximately 575 square miles |
* Purpose |
The purpose of this data set is the acquisition and production of high resolution elevation data for the State of Michigan. This LiDAR operation was designed to create high resolution data sets that will establish an authoritative source for elevation information for the State of Michigan to create detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments, and hydrologic modeling. |
Notes | |
Other Citation Details | |
• Supplemental Information |
Project Projection, Datums and Units. Projection - State Plane Michigan Central and South. Horizontal datum - North American Datum of 1983 (NAD83 (2011)). Vertical datum - North American Vertical Datum of 1988 (NAVD88) using the latest geoid (Geoid12a) for converting ellipsoidal heights to orthometric heights. Units - intl feet The following are the USGS lidar fields in JSON: {
"ldrinfo" : {
"ldrspec" : "USGS Base Specification 1.2, QL2 meeting 19.6cm NVA", "ldrsens" : "Leica ALS70", "ldrmaxnr" : "4", "ldrnps" : "0.65", "ldrdens" : "1.67", "ldradens" : "2.2", "ldranps" : "0.71", "ldrfltht" : "2250", "ldrfltsp" : "135", "ldrscana" : "20", "ldrscanr" : "64", "ldrpulsr" : "167", "ldrpulsd" : "10", "ldrpulsw" : "3", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.3", "ldrswatw" : "1222", "ldrswato" : "30", "ldrcrs" : "NAD_1983_2011_State_Plane_Michigan_Central_2112_Ft_Intl" and "NAD_1983_2011_State_Plane_Michigan_South_2113_Ft_Intl", "ldrgeoid" : "NGS Geoid12a" }, "ldraccur" : {
"ldrchacc" : "0.196", "rawnva" : "0.137", "rawnvan" : "183", "clsnva" : "0.156", "clsnvan" : "183", "clsvva" : "0.169", "clsvvan" : "211" }, "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" : "10", "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" } }} |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION |
ISO 19115 Topic Category | elevation |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA |
Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > MICHIGAN |
Global Change Master Directory (GCMD) Location Keywords | VERTICAL LOCATION > LAND SURFACE |
None | Clare County |
None | Lake County |
None | Mecosta County |
None | Missaukee County |
None | Montcalm County |
None | Newaygo County |
None | Osceola County |
None | Roscommon County |
None | Wexford County |
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Instrument Keywords | LIDAR > Light Detection and Ranging |
Platform Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Platform Keywords | Airplane > Airplane |
Physical Location
• » Organization | Office for Coastal Management |
---|---|
• » City | Charleston |
• » State/Province | SC |
• Country | |
• » Location Description |
Data Set Information
* Data Set Scope Code | Data Set |
---|---|
• Data Set Type | Elevation |
• Maintenance Frequency | Unknown |
Maintenance Note | |
» Data Presentation Form | Model (digital) |
• Entity Attribute Overview | |
Entity Attribute Detail Citation |
USGS Base Specification 1.2, QL2 meeting 19.6 cm NVA |
Entity Attribute Detail URL | |
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. |
Data Set Credit | State of Michigan (SOM) |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2022 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2022 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2020 |
Date Effective To | |
Organization | U.S. Geological Survey |
Address |
12201 Sunrise Valley Drive Reston, VA 20191 USA |
Email Address | |
Phone | |
Fax | |
Mobile | |
URL | https://usgs.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2022 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Point of Contact |
---|---|
* » Date Effective From | 2022 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference | Ground Condition |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -86.053291 |
---|---|
* » E° Bound | -84.357281 |
* » N° Bound | 44.519836 |
* » S° Bound | 43.111103 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2016-04-30 |
End | 2016-05-02 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Dates of collection form Missaukee county. |
Extent Group 1 / Time Frame 2
* » Time Frame Type | Range |
---|---|
* » Start | 2016-05-02 |
End | 2016-05-03 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Dates of collection for Roscommon county. |
Extent Group 1 / Time Frame 3
* » Time Frame Type | Range |
---|---|
* » Start | 2016-04-15 |
End | 2016-04-23 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Dates of collection for Mecosta county. |
Extent Group 1 / Time Frame 4
* » Time Frame Type | Range |
---|---|
* » Start | 2016-04-16 |
End | 2016-04-17 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Dates of collection for Clare county. |
Extent Group 1 / Time Frame 5
* » Time Frame Type | Range |
---|---|
* » Start | 2016-04-23 |
End | 2016-05-02 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Dates of collection for Lake and Osceola counties. |
Extent Group 1 / Time Frame 6
* » Time Frame Type | Range |
---|---|
* » Start | 2016-04-29 |
End | 2016-05-02 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Dates of collection for Wexford county. |
Extent Group 1 / Time Frame 7
* » Time Frame Type | Range |
---|---|
* » Start | 2016-04-15 |
End | 2016-05-03 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Dates of collection for Montcalm county. |
Extent Group 1 / Time Frame 8
* » Time Frame Type | Range |
---|---|
* » Start | 2016-04-15 |
End | 2016-04-16 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Dates of collection for Newaygo county. |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | |
Horizontal Distance Units | |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
Spatial Representation
Grid Representation Used? | No |
---|---|
Vector Representation Used? | Yes |
Text / Table Representation Used? | No |
TIN Representation Used? | No |
Stereo Model Representation Used? | No |
Video Representation Used? | No |
Grid Representation
Dimension Count | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | |||||||||||||
Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | |
Curve Object Count | |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
Reference Systems
Reference System
EPSG Code | EPSG:3857 | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Reference System
EPSG Code | EPSG:5703 | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Reference System
EPSG Code | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
* » Security Class | Unclassified |
---|---|
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» Data Access Procedure |
Data is available online for bulk and custom downloads. |
• » Data Access Constraints |
None |
• Data 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. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | 2022-05-13 |
---|---|
End Date | Present |
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9500/details/9500 |
Distributor | NOAA Office for Coastal Management (NOAA/OCM) (2022 - Present) |
File Name | Customized Download |
Description |
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. Change to an orthometric vertical datum is one of the many options. |
File Date/Time | |
File Type | Zip |
File Size | |
Application Version | |
Compression | Zip |
Review Status |
Start Date | 2022-05-13 |
---|---|
End Date | Present |
» Download URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/ |
Distributor | U.S. Geological Survey (2020 - Present) |
File Name | Bulk Download |
Description |
Bulk download of data files in LAZ format, MI State Plane South and Central, NAD83 (2011), international feet coordinates and a vertical datum of NAVD88 (GEOID12A), units in international feet. This url links to the USGS copy of the files, from which the Entwine Point Tile files originated. These have not been reviewed by OCM and the link is provided here for convenience. |
File Date/Time | |
File Type | LAZ |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
URLs
URL | https://coast.noaa.gov/dataviewer/ |
---|---|
Name | NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) |
URL Type | Online Resource |
File Resource Format | HTML |
Description |
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. |
URL | https://www.fisheries.noaa.gov/inport/item/56271 |
---|---|
Name | Muskegon County Metadata |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to the Muskegon County metadata. |
URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8731/details/8731 |
---|---|
Name | Custom Download of Muskegon County Points |
URL Type | Online Resource |
File Resource Format | Zip |
Description |
Link to custom download the Muskegon County lidar points that are part of this larger data set. |
URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_16Co_Clare_2015_LAS_2018/ept.json |
---|---|
Name | Entwine Point Tiles (EPT) for Clare County |
URL Type | Online Resource |
File Resource Format | json |
Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_16Co_Mecosta_2015_LAS_2018/ept.json |
---|---|
Name | Entwine Point Tiles (EPT) for Mecosta County |
URL Type | Online Resource |
File Resource Format | json |
Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_16Co_Newaygo_2015_LAS_2018/ept.json |
---|---|
Name | Entwine Point Tiles (EPT) for Newaygo County |
URL Type | Online Resource |
File Resource Format | json |
Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_16Co_Osceola_2015_LAS_2018/ept.json |
---|---|
Name | Entwine Point Tiles (EPT) for Osceola County |
URL Type | Online Resource |
File Resource Format | json |
Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_16Co_Roscommon_2015_LAS_2018/ept.json |
---|---|
Name | Entwine Point Tiles (EPT) for Roscommon County |
URL Type | Online Resource |
File Resource Format | json |
Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_Lake_2016_LAS_2017/ept.json |
---|---|
Name | Entwine Point Tiles (EPT) for Lake County |
URL Type | Online Resource |
File Resource Format | json |
Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_Missaukee_2016_LAS_2017/ept.json |
---|---|
Name | Entwine Point Tiles (EPT) for Missaukee County |
URL Type | Online Resource |
File Resource Format | json |
Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_Montcalm_2015_LAS_2018/ept.json |
---|---|
Name | Entwine Point Tiles (EPT) for Montcalm County |
URL Type | Online Resource |
File Resource Format | json |
Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_Wexford_2016_LAS_2017/ept.json |
---|---|
Name | Entwine Point Tiles (EPT) for Wexford County |
URL Type | Online Resource |
File Resource Format | json |
Description |
Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud. |
URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/MI_16CountiesFEMA2015_C16/ |
---|---|
Name | USGS Additional Info |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to the additional information available for this data set from the USGS. This information includes reports, tile index shapefiles, and hydro breaklines. |
URL | https://usgs.entwine.io/data/view.html?r=[%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_16Co_Clare_2015_LAS_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_16Co_Mecosta_2015_LAS_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_16Co_Newaygo_2015_LAS_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_16Co_Osceola_2015_LAS_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_16Co_Roscommon_2015_LAS_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_Lake_2016_LAS_2017/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_Missaukee_2016_LAS_2017/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_Montcalm_2015_LAS_2018/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_MI_Wexford_2016_LAS_2017/ept.json%22] |
---|---|
Name | Potree 3D View |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
Microsoft Windows 7; ESRI ArcCatalog 9.3.1.1850 |
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Horizontal positional accuracy for the 10 counties 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. For the 10 counties, 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 the 10 counties. 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 183 independent survey check points located in flat terrain types within the 10 counties. The survey checkpoints were distributed throughout the block area. The 183 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 NVA was tested using 183 independent survey check points located in bare earth terrain types within the 10 counties. The 183 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.070m, or 0.137m @ 95th Confidence Interval 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 211 independent survey check points located in various vegetation terrain types within the 10 counties. The 211 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.078m, or 0.169m @ 95th Percentile defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
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 Fundamental Vertical Accuracy, Supplemental Vertical Accuracy, and Consolidated 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. Control was collected in 10 adjoining counties in Michigan. These counties include: Clare, Lake, Mecosta, Missaukee, Montcalm, Muskegon, Newaygo, Osceola, Roscommon, and Wexford. Accuracy is reported for all 10 counties combined. |
» Quality Control Procedures Employed |
Data Management
» Have Resources for Management of these Data Been Identified? | Yes |
---|---|
» Approximate Percentage of Budget for these Data Devoted to Data Management | Unknown |
» Do these Data Comply with the Data Access Directive? | Yes |
» Is Access to the Data Limited Based on an Approved Waiver? | |
» If Distributor (Data Hosting Service) is Needed, Please Indicate | |
» Approximate Delay Between Data Collection and Dissemination | |
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed | |
» Actual or Planned Long-Term Data Archive Location | NCEI-CO |
» Approximate Delay Between Data Collection and Archiving | |
» How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive? |
Data is backed up to tape and to cloud storage. |
Lineage
» Lineage Statement |
The 2016 FEMA Michigan Part 1 lidar was ingested into the Data Access Viewer for custom product generation by leveraging USGS hosted Entwine Point Tiles. |
---|
Sources
Citation Title | Entwine Point Tiles on AWS |
---|---|
Contact Role Type | Publisher |
Contact Type | Organization |
Contact Name | USGS |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | https://usgs.entwine.io/ |
Citation URL Name | USGS Entwine Point Cloud |
Citation URL Description | |
Source Contribution |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Process Steps
Process Step Number | 1 |
---|---|
» Description |
At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets. |
Process Date/Time | 2016-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
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. |
Process Date/Time | 2016-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
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. |
Process Date/Time | 2016-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
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. |
Process Date/Time | 2016-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 5 |
---|---|
» Description |
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. |
Process Date/Time | 2016-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 6 |
---|---|
» Description |
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. |
Process Date/Time | 2016-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 7 |
---|---|
» Description |
Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were re-projected horizontally to WGS84 Web Mercator (EPSG 3857). Vertically, the data were converted to meters and no changes were made to the vertical datum (NAVD88 GEOID12A; EPSG 5703). |
Process Date/Time | |
Process Contact | U.S. Geological Survey |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 8 |
---|---|
» Description |
References to the entwine point tiles and data reports were ingested into the Digital Coast Data Access Viewer. No changes to the data were made at this point. The Data Access Viewer will access the point cloud as it resides on AWS under the usgs-lidar-public container. |
Process Date/Time | 2022-05-12 00:00:00 |
Process Contact | Office for Coastal Management (OCM) |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Data Set (DS) | Cross Reference |
2016 FEMA Michigan Lidar: Part 1 (Muskegon County) |
Catalog Details
Catalog Item ID | 67239 |
---|---|
Metadata Record Created By | Rebecca Mataosky |
Metadata Record Created | 2022-05-13 12:35+0000 |
Metadata Record Last Modified By | Rebecca Mataosky |
» Metadata Record Last Modified | 2023-03-15 20:24+0000 |
Metadata Record Published | 2022-05-13 |
Owner Org | OCMP |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2022-05-13 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2023-05-13 |
Tags |
---|