2014 USACE NCMP Topobathy Lidar: California
OCM Partners
Data Set
(DS)
| ID: 49651
| Published / External
Created: 2017-11-15
|
Last Modified: 2023-05-30
Project (PRJ) | ID: 49401
ID: 49651
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2014 USACE NCMP Topobathy Lidar: California |
---|---|
Short Name | ca2014_usace_ncmp_ca_m4912_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2016-12-15 |
* » Abstract |
These files were collected by Fugro and contain topographic data collected with a RIEGL VQ-480 airborne lidar system over the California coastline. Data coverage generally extends along the shoreline from the waterline to 500 meters onshore. The VQ-480 sensor configuration produced a pulse repetition rate of 200 kHz at near-infrared laser wavelength. VQ-480 data was collected concurrently with SHOALS-1000 bathymetric lidar sensor; the line scheme flown was planned for the narrower scan swath of the SHOALS sensor (230 m) therefore VQ-480 data presents overlap that exceeded over 200% (460 m) of area coverage and point density requirements. Quality assessments allowed to keep best quality flight line data and discard redundant or flight lines of lesser quality. Native lidar data are not generally in a format accessible to most Geographical Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data into 3-dimensional positions that can be exported to standard formats and imported into GIS software for visualization and further analysis. Each flight line lidar data containing the XYZ points were exported to ASPRS LAS format. The data file naming convention is based on a standardized structure. LAS format is version 1.2. The files also contain airborne bathymetric lidar data collected with the SHOALS-1000T sensor over the California coast. Data coverage generally extends along the coastline from the waterline to 1,000 meters offshore or to laser depth extinction. The SHOALS system has a laser pulse repetition rate of 2.5 kHz at 532 nm (green wavelength). SHOALS lidar data are contained in two basic file types: HOF and INH. HOF files (Hydrographic Output File) contains the XYZ and supporting information for all shots within a flight line; the INH files (Hydrographic Input File) contains information describing the flight line and the digitized laser shot data (waveforms). These data formats, proprietary of Optech, Inc. (Canada), are commonly used in software packages that include SHOALS-GCS and CZMIL-HydroFusion. The Las files were then classified with class 1 being unclassified, 2 being ground and 29 valid bathymetric data in Terrascan. The 3-D position data are used to generate a series of LAS file products, with each covering approximately 5 kilometers of shoreline. In addition to the lidar point data, topobathy bare earth Digital Elevation Models (DEMs), created from the lidar point data are also available. These products 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. These data are available for download here: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=5189 DEMs that were created from all classes of points (1, 2, 29) at a 1 meter grid size are available by request via email at: coastal.info@noaa.gov. Original contact information: Contact Org: JALBTCX Title: Data Production Manager Phone: 228-252-1131 Email: JALBTCX@usace.army.mil |
* Purpose |
These data were collected as a part of the NCMP to depict the elevations above and below water in the California coastal zone. Data gaps that resulted from terrain, airspace restrictions (around LAX) and temporal changes in the beach profile. |
Notes |
10295 |
Other Citation Details | |
• Supplemental Information | |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > HUMAN DIMENSIONS > ENVIRONMENTAL GOVERNANCE/MANAGEMENT > LAND MANAGEMENT > LAND USE CLASSES |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > GEOMORPHIC LANDFORMS/PROCESSES > COASTAL LANDFORMS |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > GEOMORPHIC LANDFORMS/PROCESSES > COASTAL PROCESSES |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > BATHYMETRY |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > SEAFLOOR TOPOGRAPHY |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION |
ISO 19115 Topic Category | elevation |
ISO 19115 Topic Category | imageryBaseMapsEarthCover |
ISO 19115 Topic Category | oceans |
GCMD Data Center Keywords v7 | DOD/USARMY/USACE/SAM/MOBILE/OPJ/JALBTCX > Department of Defense |
GCMD Data Center Keywords v7 | Spatial Data Branch |
GCMD Data Center Keywords v7 | United States Army |
None | Bathymetry |
None | Bathymetry/Topography |
None | Classified LAS |
None | IWG-OCM |
None | Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) |
None | Mobile District |
None | National Coastal Mapping Program (NCMP) |
None | Topography |
None | U.S. Army Corps of Engineers (USACE) |
Temporal Keywords
Thesaurus | Keyword |
---|---|
None | 2014 |
None | October |
None | September |
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords | VERTICAL LOCATION > LAND SURFACE |
Global Change Master Directory (GCMD) Location Keywords | VERTICAL LOCATION > SEA FLOOR |
Geographic Names Information System | California |
Geographic Names Information System | United States |
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Instrument Keywords | LIDAR > Light Detection and Ranging |
Platform Keywords
Thesaurus | Keyword |
---|---|
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 | |
• Maintenance Frequency | As Needed |
Maintenance Note | |
» Data Presentation Form | |
• Entity Attribute Overview | |
Entity Attribute Detail Citation | |
Entity Attribute Detail URL | |
Distribution Liability |
These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures. Any conclusions drawn from the analysis of this information are not the responsibility of JALBTCX, the Office for Coastal Management or its partners. |
Data Set Credit | Acknowledgement of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any publications or derived products. |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2016-12-15 |
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 | 2016-12-15 |
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 | Metadata Contact |
---|---|
* » Date Effective From | 2016-12-15 |
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 | 2016-12-15 |
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 | -122.529587 |
---|---|
* » E° Bound | -117.087133 |
* » N° Bound | 37.827131 |
* » S° Bound | 32.533892 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2014-09-08 |
End | 2014-10-05 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
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? | |
---|---|
Vector Representation Used? | Yes |
Text / Table Representation Used? | |
TIN Representation Used? | |
Stereo Model Representation Used? | |
Video Representation Used? |
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 | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» Data Access Procedure |
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4912; |
• » Data Access Constraints |
None. These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures. |
• Data Use Constraints |
These data depict the heights at the time of the survey and are only accurate for that time. Acknowledgement of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any publications or derived products. The data herein, including but not limited to geographic data, tabular data, analytical data, electronic data structures or files, are provided "as is" without warranty of any kind, either expressed or implied, or statutory, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the data is assumed by the user. No guarantee of accuracy is granted, nor is any responsibility for reliance thereon assumed. In no event shall the U.S. Army Corps of Engineers, Mobile District Office, Spatial Data Branch be liable for direct, indirect, incidental, consequential or special damages of any kind, including, but not limited to, loss of anticipated profits or benefits arising out of use of or reliance on the data. The Spatial Data Branch does not accept liability for any damages or misrepresentation caused by inaccuracies in the data or as a result of changes to the data caused by system transfers or other transformations or conversions, nor is there responsibility assumed to maintain the data in any manner or form. 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 | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4912 |
Distributor | |
File Name | Customized Download |
Description |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/htdata/lidar1_z/geoid12b/data/4912 |
Distributor | |
File Name | Bulk Download |
Description |
Simple download of data files. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
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 |
Archive Information
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
URLs
URL | https://coast.noaa.gov/dataviewer |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://coast.noaa.gov |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://coast.noaa.gov/htdata/lidar1_z/geoid12b/data/4912/supplemental/ca2014_usace_ncmp_ca_m4912.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar footprint for the 2014 USACE NCMP topobathy lidar project along the coast of California. |
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 | 2016-11-17 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Date that the source FGDC record was last modified. |
Activity Time | 2017-11-14 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details. |
Activity Time | 2018-02-08 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload of Positional Accuracy fields only. |
Activity Time | 2018-03-13 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload to move data access links to Distribution Info. |
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 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.1.0.3035 |
---|
Data Quality
Representativeness | |
---|---|
Accuracy |
These data are not attributed. | Quantitative Value: None | Quantitative Test Explanation: These data are not attributed. |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Compiled to meet 1 m horizontal RMSE at 95% confidence level. |
Vertical Positional Accuracy |
The Topographic data point positions were obtained using post processed KGPS methods. The vertical accuracy of the data is better than +/- 0.095 m. The Bathymetric data point positions were obtained using post processed KGPS methods. The vertical accuracy of the data is better than +/- 0.185 m |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
This data set covers the spatial extent of topographic and bathymetric lidar data obtained during this survey. |
Conceptual Consistency |
During inspection and QC of the lidar point cloud, flightline to flightline elevation differences met the RIEGL VQ-480 AND SHOALS-1000T sensor specifications. |
» Quality Control Procedures Employed |
Data Management
» Have Resources for Management of these Data Been Identified? | |
---|---|
» Approximate Percentage of Budget for these Data Devoted to Data Management | |
» Do these Data Comply with the Data Access Directive? | |
» 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 | |
» If World Data Center or Other, Specify | |
» If To Be Determined, Unable to Archive, or No Archiving Intended, Explain |
|
» 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? |
|
Lineage
» Lineage Statement |
---|
Sources
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 |
The topographic lidar data were collected using the RIEGL VQ-480 lidar system, operated by Fugro Pelagos through contract. The system collects topographic lidar data at maximum pulse rate of 200 kHz in a near-infrared wavelength producing point cloud density between 2.5-2.8 pts/sq m. Aircraft position, velocity and acceleration information are collected a Applanix POS AV 510 sensor. All logged raw data were transferred to the office and processed in RIEGL RiPROCESS software v1.6.1. Aircraft position data are processed using Applanix POSPac MMS v6.2.2 software and the results combined with the lidar data to produce 3-D positions for each lidar shot. 3D point clouds are inspected in RiProcess software and scan adjustments performed after careful scrutiny. The 200% redundant coverage achieved with the VQ-480 flight plan helped in the data validation efforts by removing scan lines that presented excessive mismatch and misalignments. Upon processing and export to LAS format, QA/QC is performed with QPS Fledermaus v7.3.3 software. These bathymetric lidar data were collected using the SHOALS-1000T bathymetric lidar system. It is owned by Fugro Pelagos Inc. and operated through contract. The system collects bathymetric lidar data at 2.5 kHz and RGB imagery at 1 Hz, producing point clouds with an approximate spot spacing of 4.0-5.0 m x 2.5 m. Aircraft position, velocity and acceleration information are collected through a POS AV 510 sensor. All logged raw data streams are transferred to the office for downloading and processing in SHOALS GCS v 6.32 software. Aircraft position data are processed using Applanix POSPac MMS v 6.2.2 software and the results combined with the sensor data to produce 3-D positions for each lidar shot on the NAD83(2011) reference datum. Upon inspection and QA/QC in the software package Fledermaus v7.3.3, anomalous data are flagged as invalid; a percentage of data are also re-processed after further refinement of parameters to account for system-related biases. The data files also contain topographic coverage of adjacent terrain (land elevations). Upon inspection at JALBTCX, utilizing the QA/QC software packages Fledermaus and PFM_ABE, any additional anomalous data are flagged as invalid. PFM_ABE software then exports all bathymetric lidar data as a series of unclassified LAS files. |
Process Date/Time | 2014-09-08 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
LAS files are imported into GeoCue V2014.1.21.4, which is a geospatial workflow production and management software tool employed by JALBTCX to perform and monitor production of data products. Upon import into GeoCue, a customized classification macro, built upon the TerraScan V13 module within Microstation V8i, classifies valid topobathy data as ground points (2) and unclassified points (1), and valid bathymetric points (29). Upon completion the macro, the classification results undergo quality control and any misclassified points are manually edited. In areas of dense vegetation the bare earth ground points might be incorrectly classified due to the inability of the laser to penetrate the canopy and reach the bare ground. In these areas, JALBTCX defaults to the algorithm's "ground" surface instead of manually reclassifying those points. They are partitioned into a series of 5km or quarter quad delivery boxes, one Classified LAS file per box. The format of the file is LAS version 1.2. Data are classified as 1 (valid non-ground topographic data), 2 (valid ground topographic data), and 29 (valid bathymetric data). |
Process Date/Time | 2016-02-02 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) received 117 files in las format from JALBTCX. The files contained lidar intensity and elevation measurements along the coast of California. The data were in geographic coordinates and ellipsoid elevations in meters. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Data filenames were standardized to OCM file naming convention (retaining USACE names). 2. The LAStools software scripts lasinfo and lasvalidate, were run on the las files to check for errors. 3. Internal OCM scripts were run on the las files to check for elevation outliers, to assign the geokeys, to sort the data by gps time and zip the data to database and to http. |
Process Date/Time | 2016-11-15 00:00:00 |
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 |
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 |
---|---|---|
Catalog Details
Catalog Item ID | 49651 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-15 15:21+0000 |
Metadata Record Last Modified By | SysAdmin InPortAdmin |
» Metadata Record Last Modified | 2023-05-30 18:10+0000 |
Metadata Record Published | 2018-03-13 |
Owner Org | OCMP |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2018-03-13 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2019-03-13 |
Tags |
---|