gov.noaa.nmfs.inport:49646 eng UTF8 dataset 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) NAD83(2011) 2008-11-12 publication European Petroleum Survey Group https://apps.epsg.org/api/v1/CoordRefSystem/6318/export/?format=gml urn:ogc:def:crs:EPSG:6318 6.18.3 North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters https://apps.epsg.org/api/v1/VerticalCoordRefSystem/5703/?api_key=gml North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters Link to Geographic Markup Language (GML) description of reference system. information resourceProvider European Petroleum Survey Group https://www.epsg.org/ European Petroleum Survey Group Geodetic Parameter Registry Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. search publisher vertical OGP 2006-11-28 false urn:ogc:def:cs:EPSG::6499 Vertical CS. Axis: height (H). Orientation: up. UoM: meter. Used in vertical coordinate reference systems. urn:ogc:def:axis:EPSG::114 H up urn:ogc:def:crs:EPSG::5703 2011 USGS Lidar: Orange County (CA) ca2011_usgs_orange_m4793_metadata 2015-01-16 publication NOAA/NMFS/EDM 49646 https://www.fisheries.noaa.gov/inport/item/49646 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/dataviewer WWW:LINK-1.0-http--link Citation URL Online Resource download https://coast.noaa.gov WWW:LINK-1.0-http--link Citation URL Online Resource download LiDAR (Light Detection and Ranging) discrete-return point cloud data are available in the American Society for Photogrammetry and Remote Sensing (ASPRS) LAS format. The LAS format is a standardized binary format for storing 3-dimensional point cloud data and point attributes along with header information and variable length records specific to the data. Millions of data points are stored as a 3-dimensional data cloud as a series of x (longitude), y (latitude) and z (elevation) points. A few older projects in this collection are in ASCII format. Acquired LiDAR data over an Area of Interest (AOI) entire of Orange County California. The acquisition plan entailed a nominal point spacing of 1.76 points per meter square and a side lap of 40% between flight lines. The AOI covers 696 square miles. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. High-resolution digital elevation maps generated by airborne and stationary LiDAR have led to significant advances in geomorphology, the branch of geoscience concerned with the origin and evolution of Earth's surface topography. LiDAR provides unique characteristics relative to other remotely sensed data sources by providing three-dimensional feature information that cannot be derived from traditional imaging sensors. 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 asNeeded https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4793/supplemental/ca2011_usgs_orange_m4793.kmz This graphic shows the lidar coverage for the 2011 lidar project covering Orange County, CA. kmz 3-dimensional Light Detection and Ranging point cloud radar theme Lidar - partner (no harvest) project InPort otherRestrictions Cite As: OCM Partners, [Date of Access]: 2011 USGS Lidar: Orange County (CA) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49646. 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. These data depict the heights at the time of the survey and are only accurate for that time. otherRestrictions Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of Merrick & Co, USGS, NOAA, the Office for Coastal Management or its partners. unclassified NOAA Data Management Plan (DMP) NOAA/NMFS/EDM 49646 https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49646.pdf WWW:LINK-1.0-http--link NOAA Data Management Plan (DMP) NOAA Data Management Plan for this record on InPort. information crossReference vector eng; US elevation -118.122754 -117.509822 33.428832 33.955557 | Currentness: Ground Condition 2011-12-17 2012-02-09 A report for this project is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4793/supplemental/ca2011_usgs_orange_m4793_surveyreport.pdf A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4793/supplemental/ca2011_usgs_orange_m4793.kmz 3D Breaklines are available for this dataset however NOAA has not evaluated these and therefore are only available by request. false eng false none 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=4793 WWW:LINK-1.0-http--link Customized Download Create custom data files by choosing data area, product type, map projection, file format, datum, etc. download https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4793/index.html WWW:LINK-1.0-http--link Bulk Download Simple download of data files. download dataset Accuracy See survey report Horizontal Positional Accuracy The ortho imagery horizontal positional accuracy and the assurance of that accuracy depend, in part, on the accuracy of the data inputs to the rectification process. These inputs consist of the digital terrain model (DTM), fully digital analytic aerotriangulation (FDAAT) control and methods, the photo source camera calibration, scanner calibration, and aerial photographs. The orthoimagery output from these inputs meet National Map Accuracy Standards (NMAS). Aerial cameras have current certification from the USGS, National Mapping Division, Optical Science Laboratory. Test calibration scans are performed on all source photography scanners.; Quantitative Value: 1.0 meters, Test that produced the value: Not Tested, see report for clarification. Vertical Positional Accuracy Required to meet 0.125 m RMSE(z); Quantitative Value: 0.10 meters, Test that produced the value: Tested RMSE(z) in meters for checkpoints. FVA Computed to 0.19 m. and a CVA of 0.17 m. Completeness Report The dataset was reviewed to ensure complete coverage of the project area. Conceptual Consistency Completed lidar data acquisition and data calibration for the project area. LiDAR mass points were produced to LAS 1.2 specifications, including the following LAS classification codes: The data was processed using GeoCue and TerraScan software. The initial step is the setup of the GeoCue project, which is done by importing a project defined tile boundary index encompassing the entire project area. The acquired 3D laser point clouds, in LAS binary format, were imported into the GeoCue project and tiled according to the project tile grid. Once tiled, the laser points were classified using a proprietary routine in TerraScan. This routine classifies any obvious outliers in the dataset to class 7 and points with scan angles exceeding +/- 20 degrees to class 11. After points that could negatively affect the ground are removed from class 1, the ground layer is extracted from this remaining point cloud. The ground extraction process encompassed in this routine takes place by building an iterative surface model. This surface model is generated using three main parameters: building size, iteration angle and iteration distance. The initial model is based on low points being selected by a "roaming window" with the assumption that these are the ground points. The size of this roaming window is determined by the building size parameter. The low points are triangulated and the remaining points are evaluated and subsequently added to the model if they meet the iteration angle and distance constraints. This process is repeated until no additional points are added within iterations. A second critical parameter is the maximum terrain angle constraint, which determines the maximum terrain angle allowed within the classification model. The following fields within the LAS files are populated to the following precision: GPS Time (0.000001 second precision), Easting (0.003 meter precision), Northing (0.003 meter precision), Elevation (0.003 meter precision), Intensity (integer value - 12 bit dynamic range), Number of Returns (integer - range of 1-4), Return number (integer range of 1-4), Scan Direction Flag (integer - range 0-1), Classification (integer), Scan Angle Rank (integer), Edge of flight line (integer, range 0-1), User bit field (integer - flight line information encoded). The LAS file also contains a Variable length record in the file header that defines the projection, datums, and units. 2010-01-01T00:00:00 Once the initial ground routine has been performed on the data, Dewberry creates Delta Z (DZ) orthos to check the relative accuracy of the LiDAR data. These orthos compare the elevations of LiDAR points from overlapping flight lines on a 1 meter pixel cell size basis. If the elevations of points within each pixel are within 10 cm of each other, the pixel is colored green. If the elevations of points within each pixel are between 10 cm and 20 cm of each other, the pixel is colored yellow, and if the elevations of points within each pixel are greater than 20 cm in difference, the pixel is colored red. Pixels that do not contain points from overlapping flight lines are colored according to their intensity values. DZ orthos can be created using the full point cloud or ground only points and are used to review and verify the calibration of the data is acceptable. Some areas are expected to show sections or portions of red, including terrain variations, slope changes, and vegetated areas or buildings if the full point cloud is used. However, large or continuous sections of yellow or red pixels can indicate the data was not calibrated correctly or that there were issues during acquisition that could affect the usability of the data. The DZ orthos for Orange County California showed that the data was calibrated correctly with no issues that would affect its usability. The figure below shows an example of the DZ orthos. Dewberry utilized a variety of software suites for data processing. The LAS dataset was received and imported into GeoCue task management software for processing in Terrascan. Each tile was imported into Terrascan and a surface model was created to examine the ground classification. Dewberry analysts visually reviewed the ground surface model and corrected errors in the ground classification such as vegetation, buildings, and bridges that were present following the initial processing conducted by Dewberry. Dewberry analysts employ 3D visualization techniques to view the point cloud at multiple angles and in profile to ensure that non-ground points are removed from the ground classification. After the ground classification corrections were completed, the dataset was processed through a water classification routine that utilizes breaklines compiled by dewberry to automatically classify hydro features. The water classification routine selects ground points within the breakline polygons and automatically classifies them as class 9, water. The final classification routine applied to the dataset selects ground points within a specified distance of the water breaklines and classifies them as class 10, ignored ground due to breakline proximity. 2010-01-01T00:00:00 The NOAA Office for Coastal Management (OCM) received the files in laz format from USGS via an FTP online repository. The files contained lidar elevation and intensity measurements. The data were in UTM Zone 11 (meters) and NAVD88 (orthometric) heights in meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from UTM coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights in meters to GRS80 (ellipsoid) heights in feet using Geoid 09. 3. Class 11 points were reclassified to class 15 in accordance to the OCM classification scheme. 2015-01-10T00:00:00 The vertical values in this data set have been converted to reference North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters, using the GEOID18 grids provided by the National Geodetic Survey. Any datum and projection transformations were then done with the Office for Coastal Management 'datum_shift' program. Compression to an LAZ file was done with the LAStools 'laszip' program and can be unzipped with the same free program (https://rapidlasso.de/laszip/) Processing notes: 2025-07-01T11:19:05 NOAA Office for Coastal Management coastal.info@noaa.gov processor