<?xml version="1.0" encoding="ISO-8859-1"?>
<metadata>
<idinfo>
<datsetid> gov.noaa.csc.maps:2010_California_Coastal_m1124 </datsetid>
<citation>
<citeinfo>
<origin>
Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS),
Coastal Services Center (CSC)
</origin>
<pubdate>201201</pubdate>
<title>2009 - 2011 CA Coastal Conservancy Coastal Lidar Project</title>
<pubinfo>
<pubplace>Charleston, SC</pubplace>
<publish>NOAA's Ocean Service, Coastal Services Center (CSC)</publish>
</pubinfo>
<onlink>http://www.csc.noaa.gov/dataviewer/index.html?action=advsearch&amp;qType=in&amp;qFld=ID&amp;qVal=1124</onlink>
<onlink>http://www.csc.noaa.gov/lidar</onlink>
<onlink>http://www.csc.noaa.gov</onlink>
</citeinfo>
</citation>
<descript>
<abstract>
Light Detection and Ranging (LiDAR) data is remotely sensed high-resolution elevation data collected by an airborne collection platform.
This LiDAR dataset is a survey of Coastal California. The project area consists of approximately 2616 square miles. The project design
of the LiDAR data acquisition was developed to support a nominal post spacing of 1 meter. Fugro EarthData, Inc. acquired 1546 flight
lines in 108 lifts between October 2009 and August 2011. This collection was a joint effort by the NOAA Coastal Services Center (CSC);
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 data collection was performed with two Piper Navajo twin engine aircrafts, utilizing a Leica ALS60 MPiA sensor;
collecting multiple return x, y, and z as well as intensity data. The data were classified as Unclassified (1), Ground (2), Low Point
(Noise) (7), Water (9), Mudflats (10), and 12 (Overlap). Only the Unclassified (1), Ground (2), Water (9), and Overlap (12) points are
available for download from the NOAA CSC Digital Coast.
</abstract>
<purpose>
These digital data are intended to support the local coastal zone managers in their decision-making processes, including applications such
as sea level rise.
</purpose>
</descript>
<timeperd>
<timeinfo>
<rngdates>
<begdate>200909</begdate>
<enddate>201110</enddate>
</rngdates>
</timeinfo>
<current>Publication Date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>As needed</update>
</status>
<spdom>
<bounding>
<westbc>-124.443740</westbc>
<eastbc>-116.267734</eastbc>
<northbc>42.012737</northbc>
<southbc>32.521695</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>ISO 19115 Topic Category</themekt>
<themekey>elevation</themekey>
</theme>
<theme>
<themekt>None</themekt>
<themekey>Bathymetry/Topography</themekey>
<themekey>LiDAR</themekey>
<themekey>Terrain</themekey>
<themekey>Model</themekey>
<themekey>Elevation</themekey>
<themekey>Surface</themekey>
</theme>
<place>
<placekt>None</placekt>
<placekey>United States</placekey>
<placekey>California</placekey>
</place>
</keywords>
<accconst>None</accconst>
<useconst>
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.
</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>NOAA Coastal Services Center</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>2234 South Hobson Ave.</address>
<city>Charleston</city>
<state>SC</state>
<postal>29405-2413</postal>
<country>US</country>
</cntaddr>
<cntvoice>843-740-1200</cntvoice>
<cntemail>csc.info@noaa.gov</cntemail>
<cntinst>For questions please use the form at http://www.csc.noaa.gov/contact/contactForm.htm</cntinst>
</cntinfo>
</ptcontac>
<datacred>
Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Coastal Services
Center (CSC); 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).
</datacred>
<secinfo>
<secsys>None</secsys>
<secclass>Unclassified</secclass>
<sechandl>N/A</sechandl>
</secinfo>
<native>
Microsoft Windows XP Version 5.1 (Build 2600) Service
Pack 2; ESRI ArcCatalog 9.2.6.1500
</native>
</idinfo>
<dataqual>
<attracc>
<attraccr>
During LiDAR data collection the airborne GPS receiver was collecting data at 2 Hz frequency and the Dilution of Precision (PDOP) was
monitored. One GPS base station was also running at the operation airport and was recording data at 1 Hz. The airborne GPS data was
post-processed in DGPS mode together with the base station data to provide high accuracy aircraft positions. The GPS trajectory then was
combined with the IMU data using loosely coupled approach to yield high accuracy aircraft positions and attitude angles. Then the LiDAR
data was processed using the aircraft trajectory and raw LiDAR data. After boresighting the LiDAR data, the ground control points were
measured against the LiDAR data by technicians using TerraScan and proprietary software and the LiDAR data was adjusted vertically to
the ground control. Independent ground control check points were used to ensure vertical accuracy of the data. The horizontal datum
for the control was the North American Datum of 1983 (NAD83, NSRS2007).The vertical datum was the North American Vertical Datum of
1988 (NAVD88). The vertical datum was realized through the use of the published/calculated ellipsoidal heights of the base station to
process the aircraft trajectory and then later applying the GEOID09 model to the processed LiDAR data to obtain orthometric heights.
</attraccr>
</attracc>
<logic>
Compliance with the accuracy standard was ensured by the collection of ground control and the establishment of a GPS base station at the
operation airport. The following checks were performed:
1) The LiDAR data accuracy was validated by performing a full boresight adjustment and then checking it against the ground control prior
to generating a digital terrain model (DTM) or other products.
2) LiDAR elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal).
</logic>
<complete>
The following methods are used to ensure LiDAR data accuracy:
1) Use of a ground control network utilizing GPS survey techniques;
2) Use of airborne GPS and IMU in conjunction with the acquisition of LiDAR; and
3) Measurement of quality control ground survey points within the finished product.
The following software is used for the validation: 1) Terrascan and 2) Fugro EarthData Proprietary Software.
</complete>
<posacc>
<horizpa>
<horizpar>
The minimum expected horizontal accuracy was tested to meet or exceed the National Standard for Spatial Data Accuracy (NSSDA).
Horizontal accuracy is 50 cm RMSE or better.
</horizpar>
</horizpa>
<vertacc>
<vertaccr>
The minimum expected vertical accuracy was tested to meet or exceed the National Standard for Spatial Data Accuracy (NSSDA).
When compared to GPS survey grade points in generally flat, non-vegetated areas, at least  95% of the positions had an error less
than or equal to 18 cm (equivalent to root mean square error (rmse) of 9 cm if errors were normally distributed).
</vertaccr>
</vertacc>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>Fugro EarthData, Inc.</origin>
<pubdate>20110804</pubdate>
<title>Aerial Acquisition of Coastal California LiDAR</title>
</citeinfo>
</srccite>
<typesrc>External hard drive</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>20091015</begdate>
<enddate>20110802</enddate>
</rngdates>
</timeinfo>
<srccurr>Ground Condition</srccurr>
</srctime>
<srccitea>Aerial LiDAR Acquisition</srccitea>
<srccontr>
Fugro EarthData, Inc. collected ALS60-derived LiDAR over Coastal California with a 1 meter, nominal post spacing
using two Piper Navajo twin engine aircrafts. The collection for the entire project area was accomplished between October 2009 and
August 2011; 1,546 flight lines were acquired in 108 lifts. The lines were flown at an average of 6,244 feet above mean terrain using
a pulse rate of 121,300 pulses per second. The collection was performed using Leica ALS60 MPiA LiDAR systems, serial numbers 113 and 142.
</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>TerraSurv</origin>
<pubdate>20101117</pubdate>
<title>Report of Survey California Coast Ground Control for LiDAR</title>
</citeinfo>
</srccite>
<typesrc>electronic mail system</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>20090925</begdate>
<enddate>20101021</enddate>
</rngdates>
</timeinfo>
<srccurr>Ground Condition</srccurr>
</srctime>
<srccitea>Ground Control</srccitea>
<srccontr>
TerraSurv under contract to Fugro EarthData, Inc. successfully established ground control for Coastal California LiDAR. A total of 307
ground control points were acquired. GPS was used to establish the control network. The horizontal datum was the North American Datum
of 1983 (NAD83, NSRS2007). The vertical datum was the North American Vertical Datum of 1988 (NAVD88).
</srccontr>
</srcinfo>
<procstep>
<procdesc>
All acquired LiDAR data went through a preliminary review to assure that complete coverage was obtained and that there were no gaps
between flight lines before the flight crew left the project site. Once back in the office, the data is run through a complete
iteration of processing to ensure that it is complete, uncorrupted, and that the entire project area has been covered without gaps
between flight lines. There are essentially three steps to this processing:
1) GPS/IMU Processing - Airborne GPS and IMU data was immediately processed using the airport GPS base station data, which was available
to the flight crew upon landing the plane. This ensured the integrity of all the mission data. These results were also used to
perform the initial LiDAR system calibration test.
2) Raw LiDAR Data Processing - Technicians processed the raw data to LAS format flight lines with full resolution output before
performing QC. A starting configuration file was used in this process, which contains the latest calibration parameters for the
sensor. The technician also generated flight line trajectories for each of the flight lines during this process.
3) Verification of Coverage and Data Quality - Technicians checked flight line trajectory files to ensure completeness of acquisition
for project flight lines, calibration lines, and cross flight lines. The intensity images were generated for the entire lift at the
required post spacing for the project. The technician visually checked the intensity images against the project boundary to ensure
full coverage. The intensity histogram was analyzed to ensure the quality of the intensity values. The technician also thoroughly
reviewed the data for any gaps in project area. The technician generated a few sample TIN surfaces to ensure no anomalies were
present in the data. Turbulence was inspected for and if it affected the quality of the data, the flight line was rejected and
reflown. The technician also evaluated the achieved post spacing against project specified post spacing.
</procdesc>
<srcused>Raw LiDAR Data</srcused>
<procdate>20110804</procdate>
<srcprod>Verified LiDAR Data</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Fugro EarthData, Inc.</cntorg>
<cntper>Rich McClellan</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>7320 Executive Way</address>
<city>Frederick</city>
<state>MD</state>
<postal>21704</postal>
<country>US</country>
</cntaddr>
<cntvoice>301-948-8550</cntvoice>
<cntfax>301-963-2064</cntfax>
<cntemail>rmcclellan@fugro.com</cntemail>
<hours>Mon-Fri 8:30am to 5:00pm</hours>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>
The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe
the Raw Data Processing and Boresight process:
1) Technician processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source
data for boresight.
2) Technician first used commercial software to calculate initial boresight adjustment angles based on sample areas selected in the
lift- mini project. These areas cover calibration flight lines collected in the lift, cross tie and production flight lines.
These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle
calculation. The technician then analyzed the result and made any necessary additional adjustment until it is acceptable for the
mini project.
3) Once the boresight angle calculation was done for the mini project, the adjusted settings were applied to all of the flight lines
of the lift and checked for consistency. The technician utilized commercial and proprietary software packages to analyze the
matching between flight line overlaps for the entire lift and adjusted as necessary until the results met the project specifications.
4) Once the boresight adjustment was completed for each lift individually, the technician ran a routine to check the vertical
misalignment of all flight lines in the project and also compared data to ground truth. The entire dataset was then adjusted to
ground control points.
5) The technician ran a final vertical accuracy check between the adjusted data and surveyed ground control points after the z
correction. The result was analyzed against the project specified accuracy to make sure it meets the project requirements.
6) The flight lines collected under the following programs:  National Coastal Mapping Program - JALBTCX and Coastal California LiDAR
and Digital Imagery for NOAA CSC in partnership with the SCC were tied together in the boresight process. Control points are shared
in both projects. The overlap between flight lines from both projects was compared for matching.
</procdesc>
<srcused>Verified LiDAR Data</srcused>
<procdate>20110919</procdate>
<srcprod>Boresighted Data</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Fugro EarthData, Inc.</cntorg>
<cntper>Rich McClellan</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>7320 Executive Way</address>
<city>Frederick</city>
<state>MD</state>
<postal>21704</postal>
<country>US</country>
</cntaddr>
<cntvoice>301-948-8550</cntvoice>
<cntfax>301-963-2064</cntfax>
<cntemail>rmcclellan@fugro.com</cntemail>
<hours>Mon-Fri 8:30am to 5:00pm</hours>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>
Once boresighting is complete for the project, the project was set up for classification. The LiDAR data was cut to production tiles.
The flight line overlap points, Noise points and Ground points were classified automatically in this process. Fugro EarthData, Inc.
has developed a unique method for processing LiDAR data to identify and re-classify elevation points falling on vegetation, building,
and other above ground structures into separate data layers. The steps are as follows:
1) Fugro EarthData, Inc. utilized commercial software as well as proprietary software for automatic filtering. The parameters used in
the process were customized for each terrain type to obtain optimum results.
2) The Automated Process typically re-classifies 90-98% of points falling on vegetation depending on terrain type. Once the automated
filtering was completed, the files were run through a visual inspection to ensure that the filtering was not too aggressive or not
aggressive enough. In cases where the filtering was too aggressive and important terrain features were filtered out, the data was
either run through a different filter or was corrected during the manual filtering process.
3) Interactive editing was completed in 3D visualization software which also provides manual and automatic point classification tools.
Fugro EarthData, Inc. used commercial and proprietary software for this process. Vegetation and artifacts remaining after automatic
data post-processing were reclassified manually through interactive editing. The hard edges of ground features that were
automatically filtered out during the automatic filtering process were brought back into ground class during manual editing.
Auto-filtering routines were utilized as much as possible within fenced areas during interactive editing for efficiency. The
technician reviewed the LiDAR points with color shaded TINs for anomalies in ground class during interactive filtering.
4) All LAS tiles went through peer review after the first round of interactive editing was finished. This helps to catch
misclassification that may have been missed by the interactive editing.
5) Upon the completion of peer review and finalization of bare earth filtering, the classified LiDAR point cloud work tiles went
through a water classification routine based on the collected water polygons.
6) Upon the completion of finalization of the classified LiDAR point cloud work tiles, the topographic LiDAR classified point cloud
data that was produced under the JALBTCX and NOAA CSC programs was merged. The following methodology was used:
a) due to the differences in deliverable specifications between the two projects, the technician re-projected the data covered by
JALBTCX to UTM zones 10 and 11 north, NAD83 (NSRS2007), NAVD88, meters. Once complete, the JALBTCX data was reformatted to
LAS 1.2 format in accordance with the NOAA CSC project requirements. The time stamps for all points that are stored in GPS
Weekly Time were converted to Adjusted Standard GPS time using proprietary software developed by Fugro EarthData, Inc. The
data collection date and the current GPS time stamp were used in calculating the Adjusted Standard GPS time. The technician
applied the same time stamp conversion to the flight lines collected and processed for JALBTCX project that were used in
NOAA CSC project;
b) the technician clipped the NOAA CSC dataset to the inland 500 meter boundary line used in the JALBTCX project. There were not
any gaps or overlap between the coverage from these two projects;
c) once the process finished, the reformatted JALBTCX data and final NOAA CSC LiDAR classified point cloud data were packaged into
NAD83 (NSRS2007), UTM zones 10 and 11 north, meters; NAVD88, meters, using GEOID09 together for delivery. The data was also
cut to the approved 1500 meter by 1500 meter tile layout and clipped to the approved project boundary. The technician checked
the output LAS files for coverage and format;
d) the technician then QC'ed the merged dataset for quality assurance and enhanced the Bare Earth classification in the JALBTCX area
for consistent data quality;
e) these final LiDAR tiles were then used in the hydro flattening process. Water classification in some JALBTCX areas was modified
in order to achieve the best hydro flattening result.
7) The classified LiDAR point cloud data were delivered in LAS 1.2 format: 1  unclassified, 2  ground, 7  low points, 9  water,
10  mudflats, and 12  overlap points.
</procdesc>
<srcused>Boresighted Data</srcused>
<procdate>20111020</procdate>
<srcprod>Classified LiDAR Point Cloud Data</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Fugro EarthData, Inc.</cntorg>
<cntper>Rich McClellan</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>7320 Executive Way</address>
<city>Frederick</city>
<state>MD</state>
<postal>21704</postal>
<country>US</country>
</cntaddr>
<cntvoice>301-948-8550</cntvoice>
<cntfax>301-963-2064</cntfax>
<cntemail>rmcclellan@fugro.com</cntemail>
<hours>Mon-Fri 8:30am to 5:00pm</hours>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>
The NOAA Coastal Services Center (CSC) received the files in las format. The files contained lidar elevation and intensity
measurements. The data were in UTM Zones 10 and 11 coordinates and NAVD88 Geoid 09 vertical datum. Only points classified
as Unclassified (1), Ground (2), Water (9), and Overlap (12) were made available for download. CSC 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 to GRS80 (ellipsoid) heights using Geoid 09.
3. The data were filtered to remove outliers.
4. The LAS data were sorted by latitude and the headers were updated.
</procdesc>
<procdate>201201</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>NOAA Coastal Services Center</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>2234 South Hobson Ave.</address>
<city>Charleston</city>
<state>SC</state>
<postal>29405-2413</postal>
<country>US</country>
</cntaddr>
<cntvoice>843-740-1200</cntvoice>
<cntemail>csc.info@noaa.gov</cntemail>
<cntinst>For questions please use the form at http://www.csc.noaa.gov/contact/contactForm.htm</cntinst>
</cntinfo>
</proccont>
</procstep>
<procstep>
    <procdesc> The NOAA National Geophysical Data Center (NGDC) received Lidar data files by ftp. The data received compressed containing LiDAR data from the NOAA Coastal Services Center. The data are currently being served via Digital Coastl at http://www.csc.noaa.gov/digitalcoast/. The data can be used to re-populate the system. The data are provided in LAS format. LAS format is an industry standard for serving LiDAR data. The data are exclusively in geographic coordinates, however, the datums used vary. Most are NAD 83, however some are in ITRF. Vertical systems include both ellipsoid (ITRF and NAD 83) and NAVD 88. For NAVD 88 values, Geiod 03 is primarily used; however, data received in NAVD 88 prior to 2003 was processed using Geoid 99. </procdesc>
    <procdate> 20120213 </procdate>
    <proccont>
        <cntinfo>
            <cntorgp>
                <cntorg> DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce </cntorg>
                <cntper> Pamela Grothe </cntper>
            </cntorgp>
            <cntaddr>
                <addrtype> Mailing and Physical Address </addrtype>
                <address> NOAA/NESDIS/NGDC E/GC1 325 Broadway </address>
                <city> Boulder </city>
                <state> CO </state>
                <postal> 80305-3328 </postal>
                <country> USA </country>
            </cntaddr>
            <cntvoice> (303) 497-6120 </cntvoice>
            <cnttdd> (303) 497-6958 </cnttdd>
            <cntfax> (303) 497-6513 </cntfax>
            <cntemail> pamela.grothe@noaa.gov </cntemail>
            <hours> 7:30-5:00 Mountain </hours>
            <cntinst> Contact Data Center </cntinst>
        </cntinfo>
    </proccont>
</procstep>
</lineage>
<cloud>0</cloud>
</dataqual>
<spdoinfo>
<direct>Point</direct>
<ptvctinf>
<sdtsterm>
<sdtstype>Point</sdtstype>
</sdtsterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<geograph>
<latres>0.0000001</latres>
<longres>0.0000001</longres>
<geogunit>Decimal degrees</geogunit>
</geograph>
<geodetic>
<horizdn>North American Datum of 1983</horizdn>
<ellips>Geodetic Reference System 80</ellips>
<semiaxis>6378137.000000</semiaxis>
<denflat>298.257222</denflat>
</geodetic>
</horizsys>
<vertdef>
<altsys>
<altdatum>Ellipsoid</altdatum>
<altres>0.001</altres>
<altunits>Meters</altunits>
<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
</altsys>
</vertdef>
</spref>
<eainfo>
<overview>
<eaover>Leica ALS60 MPiA sensor; 1 m nominal post spacing</eaover>
<eadetcit>see process steps within this record</eadetcit>
</overview>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>NOAA Coastal Services Center</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>2234 South Hobson Ave.</address>
<city>Charleston</city>
<state>SC</state>
<postal>29405-2413</postal>
<country>US</country>
</cntaddr>
<cntvoice>843-740-1200</cntvoice>
<cntemail>csc.info@noaa.gov</cntemail>
<cntinst>For questions please use the form at http://www.csc.noaa.gov/contact/contactForm.htm</cntinst>
</cntinfo>
</distrib>
<resdesc>Downloadable Data</resdesc>
<distliab>
Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Coastal Services Center
or its partners.
</distliab>
<custom>
This data can be obtained on-line at the following URL:
http://www.csc.noaa.gov/dataviewer/index.html?action=advsearch&amp;qType=in&amp;qFld=ID&amp;qVal=1124
This data set is dynamically generated based on user-specified parameters.
</custom>
</distinfo>
<distinfo>
    <distrib>
        <cntinfo>
            <cntorgp>
                <cntorg> DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce </cntorg>
                <cntper> Pamela Grothe </cntper>
            </cntorgp>
            <cntaddr>
                <addrtype> Mailing and Physical Address </addrtype>
                <address> NOAA/NESDIS/NGDC E/GC1 325 Broadway </address>
                <city> Boulder </city>
                <state> CO </state>
                <postal> 80305-3328 </postal>
                <country> USA </country>
            </cntaddr>
            <cntvoice> (303) 497-6120 </cntvoice>
            <cnttdd> (303) 497-6958 </cnttdd>
            <cntfax> (303) 497-6513 </cntfax>
            <cntemail> pamela.grothe@noaa.gov </cntemail>
            <hours> 7:30-5:00 Mountain </hours>
            <cntinst> Contact Data Center </cntinst>
        </cntinfo>
    </distrib>
    <distliab> Disclaimer While every effort has been made to ensure that these data are accurate and reliable within the limits of the current state of the art, NOAA cannot assume liability for any damages caused by any errors or omissions in the data, nor as a result of the failure of the data to function on a particular system. NOAA makes no warranty, expressed or implied, nor does the fact of distribution constitute such a warranty. </distliab>
    <custom> The National Geophysical Data Center serves as the archive for this LIDAR data. NGDC should only be contacted for this data if it cannot be obtained from NOAA Coastal Services Center. </custom>
</distinfo>
<metainfo>
<metd> 20120213 </metd>
<metrd> 20120213 </metrd>
<metfrd> 20130213 </metfrd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>NOAA Coastal Services Center</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>2234 South Hobson Ave.</address>
<city>Charleston</city>
<state>SC</state>
<postal>29405-2413</postal>
<country>US</country>
</cntaddr>
<cntvoice>843-740-1200</cntvoice>
<cntemail>csc.info@noaa.gov</cntemail>
<cntinst>For questions please use the form at http://www.csc.noaa.gov/contact/contactForm.htm</cntinst>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
</metainfo>
</metadata>
