2009-2011 CA Coastal California TopoBathy Merged Project Digital Elevation Model (DEM)
OCM Partners
Data Set
(DS)
| ID: 49417
| Published / External
Created: 2017-11-15
|
Last Modified: 2024-07-23
Project (PRJ) | ID: 49404
ID: 49417
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2009-2011 CA Coastal California TopoBathy Merged Project Digital Elevation Model (DEM) |
---|---|
Short Name | ca_2011_topobathy_metadata_m2616 |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2014-03 |
* » Abstract |
This project merged recently collected topographic, bathymetric, and acoustic elevation data along the entire California coastline from approximately the 10 meter elevation contour out to California's 3 mile state water's boundary. This metadata record describes the Digital Elevation Model (DEM) created from the lidar and multibeam data. The DEM has a 1m cell size. Topographic LiDAR: The topographic lidar data used in this merged project was the 2009-2011 CA Coastal Conservancy Lidar Project. The data were collected between October 2009 and August 2011. This collection was a joint effort by the NOAA Office for Coastal Management (OCM); the California State Coastal Conservancy (SCC) Ocean Protection Council (OPC); Scripps Institution of Oceanography; and the Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX). The data coverage extends landward 500 m from the shoreline, along the entire California coastline. The LAS classifications are as follows: 1-Unclassified, 2-Ground, 7-Noise, 9-Water, 10- Mudflats, 12-Overlap. The LAS points were manually re-classified from water and unclassified to ground in offshore areas where necessary. Bathymetric LiDAR: The bathymetric lidar data used in this merged project was 2009-2010 U.S. Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Center of Expertise (JALBTCX) lidar, provided by JALBTCX. The data were collected for the California Coastal Mapping Project (CCMP). The original data were in ASCII format and were converted to LAS v1.2. The LAS data were classified as follows: 21-Non-submerged Bathymetry, 22-Bathymetry, 23-Ignored Submerged Bathymetry/Overlap. Multibeam Acoustic Data: The acoustic data data used in this merged project were provided by the California Seafloor Mapping Program (CSMP) Ocean Protection Council and NOAA's National Geophysical Data Center (NGDC). The original data were in ASCII format and were converted to LAS v1.2. NOAA's VDatum software was used to vertically transform soundings from mean lower low water (MLLW) tidal datum to NAVD88 orthometric datum where necessary. The LAS data were classified as follows: 25-Submerged Acoustic, 26-Ignored Submerged Acoustic/Overlap. |
* Purpose |
The primary purpose is to merge recently collected topographic, bathymetric, and acoustic data along the entire California coastline from approximately the 10 meter elevation contour out to California's 3 mile state water's boundary. The result of this merge is a DEM containing the best available topographic LiDAR, bathymetric LiDAR, and multibeam acoustic data from various primary data sources. |
Notes |
12077 |
Other Citation Details | |
• Supplemental Information |
The Dewberry Report for the Coastal California TopoBathy Merge Project may be accessed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12a/2612/supplemental/ca2011_noaa_topobathy_merge_m2612_final_report.pdf A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12a/2612/supplemental/ca2011_noaa_topobathy_merge_m2612.kmz |
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 > TOPOGRAPHICAL RELIEF MAPS |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > BATHYMETRY |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION |
ISO 19115 Topic Category | elevation |
None | Acoustic |
None | Best Fit |
None | DEM |
None | Interpolated Voids |
None | Merge |
None | Multibeam |
None | Smoothed |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > CALIFORNIA |
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
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 |
Any conclusions drawn from the analysis of this information are not the responsibility of the National Oceanic and Atmospheric Administration (NOAA), Dewberry, Fugro Earthdata, or the NOAA Office for Coastal Management or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2014-03 |
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 | 2014-03 |
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 | 2014-03 |
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 | 2014-03 |
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 | calendar date |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -124.535124 |
---|---|
* » E° Bound | -117.047904 |
* » N° Bound | 42.012734 |
* » S° Bound | 32.525255 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2009-01-01 |
End | 2011-01-01 |
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? | Yes |
---|---|
Vector Representation Used? | |
Text / Table Representation Used? | |
TIN Representation Used? | |
Stereo Model Representation Used? | |
Video Representation Used? |
Grid Representation
Dimension Count | 3 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | Area | ||||||||||||
Transformation Parameters Available? | No | ||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
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:3717 | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Reference System
EPSG Code | EPSG:3718 | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Reference System
EPSG Code | EPSG:5703 | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
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=2616 This data set is dynamically generated based on user-specified parameters.; |
• » 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 | 2013-12-01 |
---|---|
End Date | Present |
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2616 |
Distributor | NOAA Office for Coastal Management (NOAA/OCM) (2014-03 - Present) |
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) | GeoTIFF |
Distribution Format | GeoTIFF |
File Size | |
Application Version | |
Compression | Zip |
Review Status |
Start Date | 2013-12-01 |
---|---|
End Date | Present |
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/California_Topobathy_DEM_2011_2616/index.html |
Distributor | NOAA Office for Coastal Management (NOAA/OCM) (2014-03 - Present) |
File Name | Bulk Download |
Description |
Simple download of data files. Data are cloud optimized geotiffs. |
File Date/Time | |
File Type (Deprecated) | IMG |
Distribution Format | GeoTIFF |
File Size | |
Application Version | |
Compression | Uncompressed |
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/dataregistry |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/laz/geoid18/2612/supplemental/ca2013_noaa_topobathy_merge_m2612.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage for the Coastal California TopoBathy Merge Project DEM. |
URL | https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/laz/geoid18/2612/supplemental/ca2013_noaa_topobathy_merge_m2612_final_report.pdf |
---|---|
Name | Processing report |
URL Type | Online Resource |
File Resource Format | |
Description |
Processing report for the merged product. |
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-07-14 |
---|---|
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-02-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 |
|
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Lidar sources used for this DEM merge project were existing. Horizontal accuracy testing was not performed. Industry standard calibration procedures used for topographic LiDAR sensors would yield 1 meter horizontal accuracy at the 95% confidence level. For the bathymetric data, the data positions were obtained using post processed KGPS methods. The horizontal accuracy of the data is better than +/- 1.5m RMSE. As multiple acoustic datasets from multiple sources were used, the horizontal accuracy varies. |
Vertical Positional Accuracy |
The DEMs are derived from the source LiDAR. Vertical accuracy has not been performed on the DEMs or source LiDAR data. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
A visual qualitative assessment was performed to ensure data completeness. |
Conceptual Consistency |
Covers data found in Universal Transverse Mercator (UTM) Zones 10 and 11 in California. |
» 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 |
All data were imported into GeoCue software, converted to LAS v1.2, and transformed, if necessary, to UTM coordinate system, zone 10 North, meters, horizontal datum NAD83 (NSRS2007), vertical datum NAVD88, Geoid 09, meters. Each data type (topographic, bathymetric, and acoustic) were then tiled individually according to project specifications (1500m x 1500m). Data for the NOAA Coastal California Data Merge Project were provided by various sources. Topographic data were provided by NOAA in LAS format, collected for the California Coastal Mapping Project (CCMP). The topographic data were provided with the following classifications: Class 1 = Unclassified (This class includes vegetation, buildings, noise etc.), Class 2 = Ground, Class 7 = Noise, Class 9 = Water, Class 10 = Mudflats, Class 12 = Overlap Bathymetric data were provided by Joint Airborne Bathymetry LiDAR Technical Center of Expertise (JALBTCX) in ASCII format, collected for the National Coastal Mapping Program (NCMP) in 2009. Initial bathymetric data were classified in GeoCue to Class 22 = Submerged bathymetry. Multibeam acoustic data were downloaded from the California Seafloor Mapping Program: Ocean Protection Council (CSMP)(http://seafloor.csumb.edu/SFMLwebDATA.htm), and from NOAA's NGDC (http://maps.ngdc.noaa.gov/viewers/bathymetry/) in ASCII formats, or from USGS open file reports where available. NOAA's VDatum software (version 2.3.5) was used to vertically transform soundings from mean lower low water (MLLW) tidal datum to NAVD88 orthometric datum where necessary. |
Process Date/Time | 2012-12-14 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
Reclassification of Topographic data: Reclassification of offshore islands and pinnacles was a critical component to the success of the final merged product. Tiles within 100m of the coastal shoreline were selected for review and manual classification. Each tile was brought into TerraScan and a temporary surface model was created from the topographic ground points (class 2). Using aerial imagery as a guide, the coastline was examined for any exposed islands that may be incorrectly classified as water in the LAS. Once located, points were reclassified from water (class 9) to ground (class 2) or from unclassified (class 1) to ground. Date for this process step is 20130201-20130412. |
Process Date/Time | 2013-04-12 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
Topographic-Bathymetric Seamline: All breaklines provided by NOAA were merged into a single polygon feature class. This became the foundation of the initial seamline. Areas containing both topographic and bathymetric data along the coastline were reviewed on a tile-by-tile basis using difference rasters. Because the topographic data had better horizontal resolution and vertical accuracy than the bathymetric data, it generally took priority over bathymetric data in overlap areas. However, a smoother transition between the topographic and bathymetric LiDAR datasets may be achieved by modifying the extent of the topographic data in favor of the bathymetric data. In these cases, the breakline was adjusted accordingly. The final polygon feature class was used for reclassification of LAS points in TerraScan. The polygon was converted to a polyline in Arc and clipped to the extent of the coastal shoreline. This final polyline was used as basis for the creation of the DEM smoothing buffers. Date for this process step is 20130222-20130510. |
Process Date/Time | 2013-05-10 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
Acoustic-Acoustic Seamline (Production Block 2b):In surveys with multiple resolutions, the best available resolution data was prioritized and reclassified using TerraScan software. A best fit line was not produced. Between surveys, a best fit line was generated by creating difference rasters and manually digitizing a new boundary. |
Process Date/Time | 2013-02-19 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 5 |
---|---|
» Description |
Acoustic-Acoustic Seamline (Production Blocks 3 and 4):In bathymetric attributed grid (BAG) surveys with multiple resolutions, the best available resolution data was prioritized and reclassified using TerraScan software. A best fit line was not produced. Between unique surveys, a best fit line was generated by creating difference rasters and manually digitizing a new boundary along areas with minimal offset. Date for this process setp 20130501-20130621. |
Process Date/Time | 2013-06-21 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 6 |
---|---|
» Description |
Bathymetric-Acoustic Seamline (Production Block 2b): The bathymetric-acoustic seamline was generated using the same methodology as the acoustic overlap seamline. The final polyline was used as basis for the creation of the DEM smoothing buffers. |
Process Date/Time | 2013-02-27 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 7 |
---|---|
» Description |
Bathymetric-Acoustic Seamline (Production Blocks 3 and 4):The bathymetric-acoustic seamline was generated using the same methodology as the acoustic overlap seamline, using difference rasters and manually digitizing seamlines with minimal offset. The final polyline was used as basis for the creation of the DEM smoothing buffers. The date for this process step is 20130501-20130621. |
Process Date/Time | 2013-06-21 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 8 |
---|---|
» Description |
Reclassification of Bathymetric data: In areas of overlap where topographic data were given priority over bathymetric data, overlapping bathymetric points were moved to class 21(non-submerged bathymetry). This was performed in TerraScan using the final seamline polygon. A minimum of three (3) data points within a 15m eter radius is required for inclusion in the DEM. An extent polygon is needed to accomplish this task. Topographic ground points (class 2) and bathymetric points (class 22) were converted to a masspoint feature class in Arc. The masspoints were used as the input in the Aggregate Points tool in Arc with a set distance of 15m. After the final extent polygons were generated, class 22 bathymetric points not within these polygons were moved to class 23 in TerraScan. Points outside the extent polygon remained in class 21/22. Finally, to remove above-ground artifacts from the bathymetric data, all class 22 points with elevations above +1m were reassigned to class 21 using an automated process in TerraScan. This removed docks, piers, bridges, and other miscellaneous artifacts from the point cloud. Bathymetric data between 0-1m elevation were left in class 22 to avoid classifying out too many data points in the nearshore areas. Bathymetric elevations between 0-1m were evaluated on a tile-by-tile basis and moved to class 21 if necessary. The date for this process step is 20130304-20130517. |
Process Date/Time | 2013-05-17 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 9 |
---|---|
» Description |
Reclassification of Acoustic data (Production Block 2b):Each area of the acoustic data was reclassified from the temporary class codes to the final class 25 (submerged multibeam acoustic) and class 26 (acoustic overlap) designations using the polygons generated from the acoustic-acoustic seamline boundaries. Best resolution data was prioritized in multi-resolution surveys. Best fit seamline was used between surveys. |
Process Date/Time | 2013-03-06 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 10 |
---|---|
» Description |
Reclassification of Acoustic data (Production Blocks 3 and 4):Each area of the acoustic data was reclassified from the temporary class codes to the final class 25 (submerged multibeam acoustic) and class 26 (acoustic overlap) designations. Voids in high resolution acoustic BAG data were filled with available lower resolution BAG data for each acoustic data set. This is an automated process using Fugro proprietary software specially developed for this project. This process results in a merged LAS point cloud for each survey location utilizing the best resolution BAG data. The ignored points were classified as class 26. The same filling process was used in case of NCCMP data for survey locations where data of various acquisition dates were available within a survey. Priority was given to data collected in 2010, following by 2008 and older datasets. Surface subtraction images were generated and utilized to digitize best fit line between overlapping acoustic project data sets. Overlapping acoustic datasets were reclassified and merged based on the best fit line using LAS mosaic software developed by Fugro. The merged point cloud data for each acoustic project was tiled to the project required tiling scheme. The date for this process step is 20130501-20130621. |
Process Date/Time | 2013-06-21 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 11 |
---|---|
» Description |
Reclassification of Bathymetric data (Production Block 2b):In overlapping areas between acoustic and bathymetric datasets, priority was given to the acoustic dataset due to more efficient coverage and higher resolution where available. With exception of two instances where best fit line was used, the bathymetric-acoustic seamline was represented by geographic extent of class 25. The bathymetric data within this extent was reclassified to class 23. |
Process Date/Time | 2013-03-06 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 12 |
---|---|
» Description |
Reclassification of Bathymetric data (Production Blocks 3 and 4):In overlapping areas between acoustic and bathymetric datasets, priority was given to the acoustic dataset due to more efficient coverage and higher resolution where available. With exception of two instances where best fit line was used, the bathymetric-acoustic seamline was represented by geographic extent of class 25. The bathymetric data within this extent was reclassified to class 23. Acoustic point cloud and bathymetric lidar data were merged using TSCAN project. The date for this process step is 20130501-20130621. |
Process Date/Time | 2013-06-21 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 13 |
---|---|
» Description |
Topographic-Bathymetric-Acoustic data merge process: Class 2, topographic ground, class 22, bathymetric ground, and class 25, acoustic ground, LiDAR points were exported from the combined LAS files into an Arc Geodatabase (GDB) in multipoint format. An ESRI Terrain was generated using 0.7 average point spacing. The ESRI Terrain was converted to an ERDAS Imagine raster with a 1 meter cell size using the natural neighbors interpolation method. The resulting raster was smoothed to reduce vertical offsets between the topographic-bathymetric and bathymetric-acoustic datasets. The best fit seamlines were used as the starting point for the smoothing process of the DEM. Using the raster as a visual guide, the seamlines were reviewed manually on a tile by tile basis in Global Mapper. The lines were clipped and removed in areas where vertical offests were not visible in the DEM or where cliffs, berms, voids, or other features would be not be smoothed. This prevents any unnecessary alteration of the original elevation data. A 10m radius buffer polygon was generated in Arc around the remaining portions of the best fit line. In Arc, the polygon buffer was used to extract a raster "strip" that would be used in the smoothing process. After extraction, the cell values in this raster strip were resampled to 3m cell size using mean aggregation. The resulting raster strip was resampled back to a 1m cell size using bilinear interpolation. This process produced a raster strip that would be used to smooth between data sources. The raster, the raster strip, and the seamline polygon buffer were opened in Global Mapper software. To ensure that raster values are not automatically resampled in Global Mapper when performing the final export, the default raster interpolation option was changed to Nearest Neighbor (none) before any further processing was performed. The seamline polygon buffer was selected in Global Mapper and the raster strip was feathered by 8 pixels. This eliminated any hard edges that would normally be produced by merging the two raster datasets. The two rasters were exported as one merged raster from Global Mapper using the following parameters: File Type: ERDAS Imagine (IMG) Cell Size: 1x1 m Data: 32-bit floating elevation Create Compressed File (UNCHECKED) Interpolate Gaps (CHECKED) The DEM was reopened in ESRI ArcGIS software and QCed. Any alignment shifts, projection issues, or other problems were corrected as necessary. This satisfies the Smoothed with Interpolated Voids portion of the project. To produce the Smoothed with Voids DEM, a void mask was first generated from the masspoints using the point aggregate tool in Arc. Aggregation distance was set to 15m. Extents were generated past the project boundary to prevent excessive voids along the edges. The resulting data extent was buffered by 1m. This prevents points on the edge of the extents from being included in the final void mask. The buffered extent was inverted using the symmetrical difference tool in Arc. These areas represent the new initial data voids layer. Multipart features were exploded and area calculations were made on the resulting void polygons. Void polygons smaller than 225 sq meters in area were removed. Remaining void polygons within the topographic area not within breakline boundaries were also removed. Inland breaklines were converted to polygons and added to the void mask as necessary. The void mask was converted to raster format and used to remove voids from the smoothed raster. This satisfies the Smoothed with Voids portion of the project. Each DEM was clipped to the project boundary.The date for this process step is 20130420-20130717. |
Process Date/Time | 2013-01-17 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 14 |
---|---|
» Description |
Each DEM was clipped to individual tiles. Dewberry uses a proprietary tool that clips the area DEMs to each tile located within the final Tile Grid, names the clipped DEM to the Tile Grid Cell name, and verifies that final extents are correct. All individual tiles were loaded into Global Mapper for the last review. During this last review, products are checked to ensure full, complete coverage, no issues along tile boundaries, tiles seamlessly edge-match, and that there are no remaining processing artifacts in the dataset.The date for this process step is 20130422-20130719 |
Process Date/Time | 2013-07-19 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 15 |
---|---|
» Description |
Data were converted from Imagine (*.img) format to cloud optimized geotiff in order to save space and support online access. Vertical georeferencing information was added. |
Process Date/Time | 2024-07-23 00:00:00 |
Process Contact | NOAA Office for Coastal Management (NOAA/OCM) |
Phone (Voice) | (843) 740-1202 |
Email Address | coastal.info@noaa.gov |
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 |
2009-2011 Merged Topobathy DEM (interpolated): Coastal California Same DEM with voids filled by interpolation. |
Catalog Details
Catalog Item ID | 49417 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-15 15:13+0000 |
Metadata Record Last Modified By | Kirk Waters |
» Metadata Record Last Modified | 2024-07-23 11:37+0000 |
Metadata Record Published | 2024-01-10 |
Owner Org | OCMP |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2022-03-16 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2023-03-16 |
Tags |
---|