Data Management Plan (Deprecated)

LiDAR data for Kewaunee, WI was collected by Pictometry International Corp (Pictometry) in 5 missions from March 26 – April 20, 2012. The data was collected at a nominal post spacing of 0.97 meters (3.18 feet) over an area covering approximately 380 square miles. Lidar Data Products for the Kewaunee, WI collection area include a 10ft Digital Elevation Model (DEM), and tiled 2ft Contours.

This metadata record was created by NOAA Office for Coastal Management (OCM) from information taken from the project report.

The NOAA Office for Coastal Management (OCM) downloaded the las files, breaklines, and report from the WisconsinView site:

ftp://ftp.ssec.wisc.edu/pub/wisconsinview/lidar/Kewaunee/Kewaunee_2012_County_Delivery/ and processed the data to the Data Access Viewer (DAV) and to https. While processing the las files, it was noted that there are ground classified points in water bodies, including Lake Michigan.

The hydro breaklines are available for download at the link provided in the URL section of this metadata record. Please note that the breaklines have not been reviewed by the NOAA Office for Coastal Management (OCM) and any conclusions drawn from the analysis of this information are not the responsibility of NOAA or OCM.

Process Steps:

• LiDAR data for Kewaunee, WI was collected by Pictometry International Corp (Pictometry) in 5 missions from March 26 – April 20, 2012. The data was collected at a nominal post spacing of 0.97 meters (3.18 feet) over an area covering approximately 380 square miles. Pictometry processed the raw point cloud data to ensure proper alignment of the data between flight lines. The data was then classified for “Ground” by using a series of automated filters in Terra Solid software to remove above ground vegetation and buildings. Points in water and on bridges were manually removed from the Ground class. The data was then tiled and saved in the industry standard LAS 1.2 format. The data was delivered to Groundpoint in classified LAS format in the summer of 2012.
• 2012-09-20 00:00:00 - Terrain, DEM, and 2ft Contours:For the Bare Earth Data, the Lidar Point Data was converted to a Multipoint feature class, with a filter for Ground (class 2). A Collection Area Boundary breakline was created from the classified lidar points. Breakines for water bodies and wide rivers were created from the lidar data. The multipoint feature classes and the breaklines feature classes were used to create a Ground terrain for the collection area. The terrain was converted to a DEM with 10ft cell resolution. The DEM was used to create the 2ft tiled contours. The contours were edited in the following manner: Lines shorter than 60ft (1.5 raster cells) were deleted, the lines were smoothed using a PAEK algorithm. Attributes were added for 10ft, 20ft, and 50ft Index contours. A Lidar Tile Index Feature Class was created for the original lidar files and a Contour Tiles Index feature class was created for the contour tiles. A hillshade was also created for the DEM using default ESRI illumination parameters.
• 2020-02-13 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded 381 las files from ftp://ftp.ssec.wisc.edu/pub/wisconsinview/lidar/Kewaunee/Kewaunee_2012_County_Delivery/ The 381 files contained elevation and intensity measurements for Kewaunee County, WI. The data were in WI State Plane Central NAD83, US feet, coordinates and NAVD88 (Geoid09) elevations in feet. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Noise. The NOAA Office for Coastal Management processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7. While processing the las files, it was noted that there are ground classified points in water bodies, including Lake Michigan. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes 1. LAStools script laszip was run to convert the las files to laz format. 2. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 3. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid09 model, to convert from WI State Plane Central NAD83, US feet, coordinates to geographic coordinates, to convert vertical units from feet to meters, to assign the geokeys, to sort the data by gps time and zip the data to database and to http.

Data is available online for bulk and custom downloads.

Data is backed up to tape and to cloud storage.