<?xml version="1.0" encoding="ascii"?>
<metadata xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.ngdc.noaa.gov/metadata/published/xsd/ngdcSchema/schema.xsd">
    <idinfo>
        <datsetid> gov.noaa.csc.maps:2008_SC_Orangeburg_m514 </datsetid>
        <citation>
            <citeinfo>
                <origin> Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Coastal Services Center (CSC) </origin>
                <origin>South Carolina Department of Natural Resources (SCDNR)</origin>
                <pubdate>2009</pubdate>
                <title>2008 South Carolina Department of Natural Resources (SCDNR) South Carolina Lidar - Orangeburg County</title>
                <pubinfo>
                    <pubplace>Charleston, SC</pubplace>
                    <publish>NOAA's Ocean Service, Coastal Services Center (CSC)</publish>
                </pubinfo>
                <onlink>http://www.csc.noaa.gov/lidar</onlink>
                <onlink>http://www.csc.noaa.gov</onlink>
            </citeinfo>
        </citation>
        <descript>
            <abstract> The project area is composed of 16 counties in the State of South Carolina - Cherokee, Union, Laurens, Greenwood, Newberry, Chester, Fairfield, Lancaster, Chesterfield, Marlboro, Darlington, Dillon, Marion, Williamsburg, Clarendon, and Orangeburg. This metadata file is for the lidar county deliverables for Orangeburg County, SC. The project area consists of approximately 10,194 square miles including a buffer of 50 feet along the edges of the project area and an additional
                buffer in some areas. The project design of the lidar data acquisition was developed to support a nominal post spacing of 1.4 meters. The Fugro EarthData, Inc. acquisition team of Fugro Horizons, Inc. and North West Group acquired 721 flight lines in 44 lifts from January 15, 2008 through February 10, 2008. The data was divided into 5000' by 5000' foot cells that serve as the tiling scheme. Lidar data collection was performed with a Cessna 310 aircraft, utilizing a Leica ALS50-II
                MPiA sensor, collecting multiple return x, y, and z data as well as intensity data. Lidar data was processed to achieve a bare ground surface (Classes 2 and 8). Lidar data is remotely sensed high-resolution elevation data collected by an airborne collection platform. Using a combination of laser range finding, GPS positioning and inertial measurement technologies, lidar instruments are able to make highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made
                structures, and vegetation. </abstract>
            <purpose> The purpose of this project is to collect and deliver topographic elevation point data derived from multiple return light detection and ranging (lidar) measurements for a 16-county area in South Carolina. The elevation data will be used as base data for South Carolina's flood plain mapping program (as part of FEMA's Map Modernization Program) and for additional geospatial map products in the future. </purpose>
            <supplinf> The LiDAR Quality Assurance (QA) Report Orangeburg County, South Carolina may be viewed at: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/sc/orangeburg/LiDAR_QAQC_Report_Orangeburg.pdf </supplinf>
        </descript>
        <timeperd>
            <timeinfo>
                <rngdates>
                    <begdate>20080115</begdate>
                    <enddate>20080210</enddate>
                </rngdates>
            </timeinfo>
            <current>Ground Condition</current>
        </timeperd>
        <status>
            <progress>Complete</progress>
            <update>Unknown</update>
        </status>
        <spdom>
            <bounding>
                <westbc>-81.372904</westbc>
                <eastbc>-80.213204</eastbc>
                <northbc>33.707350</northbc>
                <southbc>33.176350</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>Bare Earth</themekey>
                <themekey>Terrain</themekey>
                <themekey>Model</themekey>
                <themekey>Elevation</themekey>
                <themekey>Surface</themekey>
                <themekey>Intensity</themekey>
            </theme>
            <place>
                <placekt>None</placekt>
                <placekey>US</placekey>
                <placekey>South Carolina</placekey>
                <placekey>Orangeburg County</placekey>
            </place>
        </keywords>
        <accconst>None</accconst>
        <useconst>None</useconst>
    </idinfo>
    <dataqual>
        <attracc>
            <attraccr> The following methods are used to assure lidar accuracy: 1. Use of IMU and ground control network utilizing GPS techniques 2. Use of airborne GPS in conjunction with the acquisition of lidar 3. Measurement of quality control ground survey points within the finished product. The boresight of the lidar was processed against the ground control for Orangeburg County which consisted of 29 lidar ground survey points and 1 airborne GPS (ABGPS) base station at the operation
                airport. The horizontal datum for the control was the North American Datum of 1983, 2007 adjustment (NAD83/2007). The vertical datum was the North American Vertical Datum of 1988 (NAVD88). The Geoid 2003 model was used to transform the ellipsoidal heights to GPS derived orthometric heights. ABGPS data was collected during the acquisition mission for each flight line. During the data acquisition the Positional Dilution of Precision (PDOP) for the ABGPS was monitored. The control
                points were measured by technicians using Terrascan and Fugro EarthData proprietary software and applied to the boresight solution for the project lines. </attraccr>
        </attracc>
        <logic> Compliance with the accuracy standard was ensured by the collection of GPS ground control during the acquisition of aerial lidar and the establishment of a GPS base station operation airport. The following checks were performed. 1. The ground control and airborne GPS data stream were validated through a fully analytical boresight adjustment. 2. The Lidar elevation data were checked against the project control. 3. Lidar elevation data was validated through an inspection of edge
            matching and visual inspection for quality (artifact removal). </logic>
        <complete> The bare earth surface will contain voids where insufficient energy was reflected from the surface to generate a valid return from the terrain. Voids in the bare earth surface tend to occur in heavily vegetated areas, water bodies, and beneath buildings, motor vehicles, bridges etc. Fresh or wet asphalt, wet sand and certain types of vegetation can also cause voids or anomalous elevations. </complete>
        <posacc>
            <horizpa>
                <horizpar> The minimum expected horizontal accuracy was tested during the boresight process to meet or exceed the National Standard for Spatial Data Accuracy (NSSDA). Horizontal accuracy is 1 meter RMSE or better. </horizpar>
            </horizpa>
            <vertacc>
                <vertaccr> 94 high accuracy checkpoints were surveyed following FEMA Guidelines and Specifications for Flood Hazard Mapping Partners Appendix A: Guidance for Aerial mapping and Surveying which is based on the NSSDA. Compared with the 0.363m specification for vertical accuracy at the 95% confidence level, equivalent to 2-foot contours, the dataset passes by all methods of accuracy assessment (tested by Dewberry): Tested 0.189 meter Fundamental Vertical Accuracy at 95 percent
                    confidence level in open terrain using RMSEz x 1.9600 (FEMA/NSSDA and NDEP/ASPRS methodologies); Tested 0.145 meter Consolidated Vertical Accuracy at 95th percentile in all land cover categories combined (NDEP/ASPRS methodology); Tested 0.134 meter Supplemental Vertical Accuracy at 95th percentile in Vegetated terrain (NDEP/ASPRS methodology); Tested 0.110 meter Supplemental Vertical Accuracy at 95th percentile in Urban terrain (NDEP/ASPRS methodology). </vertaccr>
            </vertacc>
        </posacc>
        <lineage>
            <srcinfo>
                <srccite>
                    <citeinfo>
                        <origin>Fugro EarthData, Inc.</origin>
                        <pubdate>20080215</pubdate>
                        <title>Aerial Acquisition of Lidar Data for 16 counties in the State of South Carolina</title>
                    </citeinfo>
                </srccite>
                <typesrc>external hard drive</typesrc>
                <srctime>
                    <timeinfo>
                        <rngdates>
                            <begdate>20080115</begdate>
                            <enddate>20080210</enddate>
                        </rngdates>
                    </timeinfo>
                    <srccurr>Ground Condition</srccurr>
                </srctime>
                <srccitea>Aerial Lidar Acquisition</srccitea>
                <srccontr> The Fugro EarthData, Inc. acquisition team of Fugro Horizons, Inc. and North West Group collected ALS50-II derived lidar over 16 counties in the State of South Carolina with a 1.4m, nominal post spacing using a Cessna 310 aircraft. The collection for the entire project area was accomplished from January 15, 2008 through February 10, 2008 (Flight dates were January 15, 16, 18, 20, 21, 25, 27, 28, 29, 30, 31 and February 2, 3, 4, 7, 8, 10). The collection was performed
                    using a Leica ALS50-II MPiA lidar system, serial numbers ALS039 and ALS064, including an inertial measuring unit (IMU) and a dual frequency GPS receiver. This project required 44 lifts of flight lines to be collected. The lines were flown at an average of 6,000 feet above mean terrain using a maximum pulse rate frequency of 112,000 pulses per second. The planned maximum baseline length was 50 miles. </srccontr>
            </srcinfo>
            <srcinfo>
                <srccite>
                    <citeinfo>
                        <origin>ESP Associates, P.A. (ESP)</origin>
                        <pubdate>20080131</pubdate>
                        <pubtime>Unknown</pubtime>
                        <title>South Carolina Lidar, Quality Control Surveys, 16 Counties</title>
                    </citeinfo>
                </srccite>
                <typesrc>electronic mail system</typesrc>
                <srctime>
                    <timeinfo>
                        <mdattim>
                            <sngdate>
                                <caldate>20080121</caldate>
                            </sngdate>
                            <sngdate>
                                <caldate>20080122</caldate>
                            </sngdate>
                        </mdattim>
                    </timeinfo>
                    <srccurr>Ground Condition</srccurr>
                </srctime>
                <srccitea>Ground Control</srccitea>
                <srccontr> ESP under contract to Fugro EarthData, Inc. successfully established ground control for Orangeburg County, SC. A total of 29 ground control points in Orangeburg County, SC were acquired. GPS was used to establish the control network. The horizontal datum was the North American Datum of 1983, 2007 adjustment (NAD83/2007). The vertical datum was the North American Vertical Datum of 1988 (NAVD88). </srccontr>
            </srcinfo>
            <srcinfo>
                <srccite>
                    <citeinfo>
                        <origin>South Carolina Department of Natural Resources</origin>
                        <pubdate>Unknown</pubdate>
                        <pubtime>Unknown</pubtime>
                        <title>Orangeburg County, SC - Digital Orthophotography</title>
                    </citeinfo>
                </srccite>
                <typesrc>external hard drive</typesrc>
                <srctime>
                    <timeinfo>
                        <sngdate>
                            <caldate>20060530</caldate>
                        </sngdate>
                    </timeinfo>
                    <srccurr>Publication Date</srccurr>
                </srctime>
                <srccitea>Orangeburg County Orthos</srccitea>
                <srccontr> The State of South Carolina, Department of Natural Resources provided digital orthophotography covering the project area in support of this project. </srccontr>
            </srcinfo>
            <procstep>
                <procdesc> 1. Lidar, GPS, and IMU data was processed together using lidar processing software. 2. The lidar data set for each flight line was checked for project area coverage and lidar post spacing was checked to ensure it meets project specifications. 3. The lidar collected at the calibration area and project area were used to correct the rotational, atmospheric, and vertical elevation differences that are inherent to lidar data. 4. Intensity rasters were generated to verify
                    that intensity was recorded for each lidar point. 5. Lidar data was transformed to the specified project coordinate system. 6. By utilizing the ground survey data collected at the calibration site and project area, the lidar data was vertically biased to the ground. 7. Comparisons between the biased lidar data and ground survey data within the project area were evaluated and a final RMSE value was generated to ensure the data meets project specifications. 8. Lidar data in
                    overlap areas of project flight lines were trimmed and data from all swaths were merged into a single data set. 9. The data set was trimmed to the digital project boundary including an additional buffer zone of 50 feet (buffer zone assures adequate contour generation from the DEM). 10.The resulting data set is referred to as the raw lidar data. </procdesc>
                <srcused>lidar</srcused>
                <procdate>20080708</procdate>
                <srcprod>raw lidar</srcprod>
                <proccont>
                    <cntinfo>
                        <cntperp>
                            <cntper>Becky Jordan</cntper>
                            <cntorg>Fugro EarthData, Inc.</cntorg>
                        </cntperp>
                        <cntpos>Project Manager</cntpos>
                        <cntaddr>
                            <addrtype>mailing and physical</addrtype>
                            <address>7320 Executive Way</address>
                            <city>Frederick</city>
                            <state>MD</state>
                            <postal>21704</postal>
                        </cntaddr>
                        <cntvoice>301-948-8550</cntvoice>
                        <cntfax>301-963-2064</cntfax>
                        <cntemail>bjordan@earthdata.com</cntemail>
                        <hours>Monday through Friday, 8:30am to 5:00pm</hours>
                    </cntinfo>
                </proccont>
            </procstep>
            <procstep>
                <procdesc> 1. The raw lidar data was processed through a minimum block mean algorithm, and points were classified as either bare earth or non-bare earth. 2. User developed "macros" that factor mean terrain angle and height from the ground were used to determine bare earth point classification. 3. The next phase of the surfacing process was a 2D edit procedure that ensures the accuracy of the automated feature classification. 4. Editors used a combination of imagery, intensity of
                    the lidar reflection, profiles, and tin-editing software to assess points. 5. The lidar data was filtered, as necessary, using a quadric error metric to remove redundant points. This method leaves points where there is a change in the slope of surfaces (road ditches) and eliminates points from evenly sloped terrain (flat field) where the points do not affect the surface. 6. The algorithms for filtering data were utilized within Fugro EarthData's proprietary software and
                    commercial software written by TerraSolid. 7. The flight line overlap points were merged back into filtered data set for delivery product. 8. The point cloud data were delivered tiled in LAS 1.1 format; class 12 - flight line overlap points, class 9 - points in water, class 8 - model-key points, class 2 - ground points, and class 1 - all other. </procdesc>
                <srcused>raw lidar</srcused>
                <procdate>20081110</procdate>
                <srcprod>classified lidar</srcprod>
                <proccont>
                    <cntinfo>
                        <cntperp>
                            <cntper>Becky Jordan</cntper>
                            <cntorg>Fugro EarthData, Inc.</cntorg>
                        </cntperp>
                        <cntpos>Project Manager</cntpos>
                        <cntaddr>
                            <addrtype>mailing and physical</addrtype>
                            <address>7320 Executive Way</address>
                            <city>Frederick</city>
                            <state>MD</state>
                            <postal>21704</postal>
                        </cntaddr>
                        <cntvoice>301-948-8550</cntvoice>
                        <cntfax>301-963-2064</cntfax>
                        <cntemail>bjordan@earthdata.com</cntemail>
                        <hours>Monday through Friday, 8:30am to 5:00pm</hours>
                    </cntinfo>
                </proccont>
            </procstep>
            <procstep>
                <procdesc> Lidar intensity images were generated in TerraSolid software. The images are then brought up in Photoshop to see if a curve is needed to modify the radiometrics and to ensure they match from group to group. Along with looking for missing coverage and clipping to the boundary, the following steps are run in Photoshop: 1. Flip 0 values to 1 2. Change 3-band images to 1 band 3. Restore GeoTIFF headers. The intensity images were delivered in GeoTIFF format. </procdesc>
                <srcused>classified lidar</srcused>
                <procdate>20081114</procdate>
                <srcprod>intensity image</srcprod>
                <proccont>
                    <cntinfo>
                        <cntperp>
                            <cntper>Becky Jordan</cntper>
                            <cntorg>Fugro EarthData, Inc.</cntorg>
                        </cntperp>
                        <cntpos>Project Manager</cntpos>
                        <cntaddr>
                            <addrtype>mailing and physical</addrtype>
                            <address>7320 Executive Way</address>
                            <city>Frederick</city>
                            <state>MD</state>
                            <postal>21704</postal>
                        </cntaddr>
                        <cntvoice>301-948-8550</cntvoice>
                        <cntfax>301-963-2064</cntfax>
                        <cntemail>bjordan@earthdata.com</cntemail>
                        <hours>Monday through Friday, 8:30am to 5:00pm</hours>
                    </cntinfo>
                </proccont>
            </procstep>
            <procstep>
                <procdesc> Tiled lidar LAS datasets are imported into a single multipoint geodatabase featureclass. Only Ground and Model-Keypoint are imported. An ArcGIS geodatabase terrain feature class is created using the terrain creation dialogue provided through ArcCatalog. The multipoint featureclass is imported as mass point features in the terrain. An overall tile boundary for the county is input as a soft clip feature for the terrain. The terrain pyramid level resolutions and scales
                    are automatically calculated based on the point coverage for the county. </procdesc>
                <srcused>classified lidar</srcused>
                <procdate>20081115</procdate>
                <srcprod>ESRI terrain dataset</srcprod>
                <proccont>
                    <cntinfo>
                        <cntperp>
                            <cntper>Becky Jordan</cntper>
                            <cntorg>Fugro EarthData, Inc.</cntorg>
                        </cntperp>
                        <cntpos>Project Manager</cntpos>
                        <cntaddr>
                            <addrtype>mailing and physical</addrtype>
                            <address>7320 Executive Way</address>
                            <city>Frederick</city>
                            <state>MD</state>
                            <postal>21704</postal>
                        </cntaddr>
                        <cntvoice>301-948-8550</cntvoice>
                        <cntfax>301-963-2064</cntfax>
                        <cntemail>bjordan@earthdata.com</cntemail>
                        <hours>Monday through Friday, 8:30am to 5:00pm</hours>
                    </cntinfo>
                </proccont>
            </procstep>
            <procstep>
                <procdesc> The NOAA Coastal Services Center (CSC) received files in LAS format. The files contained LiDAR intensity and elevation measurements. CSC performed the following processing on the data to make it available within Digital Coast: 1. The data were converted from State Plane, SPCS Zone 3900 coordinates to geographic coordinates. 2. The data were converted from NAVD88 heights to ellipsoid heights using Geoid03. 3. The LAS header fields were sorted by latitude and updated. </procdesc>
                <procdate>200909</procdate>
                <proccont>
                    <cntinfo>
                        <cntorgp>
                            <cntorg> Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Coastal Services Center (CSC) </cntorg>
                        </cntorgp>
                        <cntpos>CEM Project Scientist</cntpos>
                        <cntaddr>
                            <addrtype>mailing and physical</addrtype>
                            <address>2234 South Hobson Ave.</address>
                            <city>Charleston</city>
                            <state>SC</state>
                            <postal>29405</postal>
                            <country>US</country>
                        </cntaddr>
                        <cntvoice>843-740-1200</cntvoice>
                        <cntemail>tcm@csc.noaa.gov</cntemail>
                    </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> 20110907 </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.000000001</latres>
                <longres>0.000000001</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> The information contained in the LAS point cloud data set are the following attributes; X, Y, Z to two significant digits; Intensity as integer; Class as integer; Return number; Number of returns; Scan direction; scan angle rank; GPS time. </eaover>
            <eadetcit> Lidar point cloud data tiled in LAS 1.1 format; ASPRS classification scheme, class 12 - flight line overlap points, class 9 - points in water, class 8 - model-key points, class 2 - ground points, and class 1 - all other. </eadetcit>
        </overview>
    </eainfo>
    <distinfo>
        <distrib>
            <cntinfo>
                <cntorgp>
                    <cntorg> Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Coastal Services Center (CSC) </cntorg>
                    <cntper>CEM Project Scientist</cntper>
                </cntorgp>
                <cntaddr>
                    <addrtype>mailing and physical</addrtype>
                    <address>2234 South Hobson Ave.</address>
                    <city>Charleston</city>
                    <state>South Carolina</state>
                    <postal>29405</postal>
                    <country>USA</country>
                </cntaddr>
                <cntvoice>843.740.1200</cntvoice>
                <cntemail>tcm@csc.noaa.gov</cntemail>
                <hours>9:00am - 5:00pm</hours>
            </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/lidar</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>20111119</metd>
        <metrd>20111119</metrd>
        <metfrd>20121119</metfrd>
        <metc>
            <cntinfo>
                <cntorgp>
                    <cntorg> Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Coastal Services Center (CSC) </cntorg>
                    <cntper>CEM Project Scientist</cntper>
                </cntorgp>
                <cntaddr>
                    <addrtype>mailing and physical</addrtype>
                    <address>2234 South Hobson Ave.</address>
                    <city>Charleston</city>
                    <state>South Carolina</state>
                    <postal>29405</postal>
                    <country>USA</country>
                </cntaddr>
                <cntvoice>843.740.1200</cntvoice>
                <cntemail>tcm@csc.noaa.gov</cntemail>
                <hours>9:00am - 5:00pm</hours>
            </cntinfo>
        </metc>
        <metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
        <metstdv>FGDC-STD-001-1998</metstdv>
    </metainfo>
</metadata>
