Text View of ISO 19115/19115-2 Metadata with Links to Guidance on NOAA EDM WikiView Metadata As: Get Data, FAQ, HTML, 19139 XML

Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components
spatialRepresentationInfo
referenceSystemInfo
referenceSystemInfo
identificationInfo
contentInfo
distributionInfo
dataQualityInfo
metadataMaintenance

2012 USACE Post-Hurricane Sandy Topographic LiDAR: Coastal Connecticut
 (MI_Metadata)
    fileIdentifier:  gov.noaa.csc.maps:2012_USACE_PostSandy_Connecticut_m1434
    language:  eng; USA
    characterSet:  (MD_CharacterSetCode) utf8
    hierarchyLevel:  (MD_ScopeCode) dataset
    contact:  (CI_ResponsibleParty)
        individualName:  Mike Sutherland
        organisationName:  DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce
        contactInfo:  (CI_Contact)
            phone:  (CI_Telephone)
                voice:  303-497-6120
                facsimile:  303-497-6513
            address:  (CI_Address)
                deliveryPoint:  NOAA/NESDIS/NGDC E/GC1 325 Broadway
                city:  Boulder
                administrativeArea:  CO
                postalCode:  80305-3328
                country:  USA
                electronicMailAddress:  mike.sutherland@noaa.gov
            hoursOfService:  7:30am-5:00pm Mountain
        role:  (CI_RoleCode) author
    dateStamp:  2013-02-20
    metadataStandardName:  ISO 19115-2 Geographic Information - Metadata - Part 2: Extensions for Imagery and Gridded Data
    metadataStandardVersion:  ISO 19115-2:2009(E)
return to top
    spatialRepresentationInfo:  (MD_VectorSpatialRepresentation)
        geometricObjects:  (MD_GeometricObjects)
            geometricObjectType:  (MD_GeometricObjectTypeCode) point
return to top
    referenceSystemInfo:  (MD_ReferenceSystem)
        referenceSystemIdentifier:  (RS_Identifier)
            authority:  (CI_Citation)
                title:  North American Datum 1983
                alternateTitle:  NAD83
                date:  (CI_Date)
                    date:  2007-01-19
                    dateType:  (CI_DateTypeCode) revision
                citedResponsibleParty:  (CI_ResponsibleParty)
                    organisationName:
                    contactInfo:  (CI_Contact)
                        onlineResource:  (CI_OnlineResource)
                            linkage: http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269
                            name:  NAD83
                            description:  Link to Geographic Markup Language (GML) description of reference system.
                            function:  (CI_OnLineFunctionCode) information
                    role:  (CI_RoleCode) resourceProvider
                citedResponsibleParty:  (CI_ResponsibleParty)
                    organisationName:  European Petroleum Survey Group
                    contactInfo:  (CI_Contact)
                        onlineResource:  (CI_OnlineResource)
                            linkage: http://www.epsg-registry.org/
                            name:  European Petroleum Survey Group Geodetic Parameter Registry
                            description:  Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations.
                            function:  (CI_OnLineFunctionCode) search
                    role:  (CI_RoleCode) publisher
            code:  urn:ogc:def:crs:EPSG::4269
return to top
    referenceSystemInfo:  (MD_ReferenceSystem)
        referenceSystemIdentifier:  (RS_Identifier)
            code:  Ellipsoid in Meters
            codeSpace:  Local Vertical Reference
return to top
    identificationInfo:  (MD_DataIdentification)
        citation:  (CI_Citation)
            title:  2012 USACE Post-Hurricane Sandy Topographic LiDAR: Coastal Connecticut
            date:  (CI_Date)
                date:  2013-01-01
                dateType:  (CI_DateTypeCode) publication
            citedResponsibleParty:  (CI_ResponsibleParty)
                organisationName:  DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
                contactInfo:  (CI_Contact)
                    phone:  (CI_Telephone)
                        voice:  843-740-1200
                    address:  (CI_Address)
                        deliveryPoint:  2234 South Hobson Ave.
                        city:  Charleston
                        administrativeArea:  SC
                        postalCode:  29405-2413
                        electronicMailAddress:  coastal.info@noaa.gov
                    onlineResource:  (CI_OnlineResource)
                        linkage: http://coast.noaa.gov
                role:  (CI_RoleCode) originator
            citedResponsibleParty:  (CI_ResponsibleParty)
                organisationName:  US Army Corps of Engineers (USACE) St. Louis District
                role:  (CI_RoleCode) originator
            citedResponsibleParty:  (CI_ResponsibleParty)
                organisationName:  DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
                contactInfo:  (CI_Contact)
                    phone:  (CI_Telephone)
                        voice:  843-740-1200
                    address:  (CI_Address)
                        deliveryPoint:  2234 South Hobson Ave.
                        city:  Charleston
                        administrativeArea:  SC
                        postalCode:  29405-2413
                        electronicMailAddress:  coastal.info@noaa.gov
                    onlineResource:  (CI_OnlineResource)
                        linkage: http://coast.noaa.gov
                role:  (CI_RoleCode) publisher
            presentationForm:  (CI_PresentationFormCode) imageDigital
        abstract:  These topographic elevation data have been acquired and developed by the U.S. Corps of Engineers St. Louis District for a 116 sq. mile project area encompassing the entire coastal region of the State of Connecticut. Using an ALS-60 MPiA sensor mounted on a Cessna 310 twin engine aircraft, Fugro EarthData, Inc. collected LiDAR point measurements over the project area with a 1.0 meter, nominal post spacing. The collection for the was accomplished between November 14, 2012 and November 16, 2012; 46 flight lines were acquired in 4 lifts. The lines were flown at an average of 1825 meters feet above mean terrain using a pulse rate of 123,700 pulses per second. Multiple returns of x,y,z and intensity were acquired. The processed LiDAR classified according to LAS version 1.2 format standard: 1 unclassified, 2 ground, 7 low points, 8 model keypoints, 9 water, and 10 ignored points.
        purpose:  To acquire, process and store multiple-return LiDAR calibrated and classified point cloud data using compliant LAS 1.2 format with the following collection conditions: Atmospheric: cloud and fog free between aircraft and ground; Ground Vegetation: leaf off preferred; Flight Height: as required to acquire point data sufficient to meet requirements. Additionally the LiDAR data must collected at or below MLW tidal elevation 0 whenever possible.
        credit:  USACE, St. Louis District
        status:  (MD_ProgressCode) completed
        pointOfContact:  (CI_ResponsibleParty)
            organisationName:  US Army Corps of Engineers St. Louis District
            contactInfo:  (CI_Contact)
                phone:  (CI_Telephone)
                    voice:  314-331-8389
                address:  (CI_Address)
                    deliveryPoint:  1222 Spruce Street
                    city:  St. Louis
                    administrativeArea:  Missouri
                    postalCode:  63103
                    country:  USA
                    electronicMailAddress:  ted.e.stanton@usace.army.mil
                hoursOfService:  9:00am - 5:00pm
            role:  (CI_RoleCode) pointOfContact
        resourceMaintenance:  (MD_MaintenanceInformation)
            maintenanceAndUpdateFrequency:  (MD_MaintenanceFrequencyCode) asNeeded
        graphicOverview:  (MD_BrowseGraphic)
            fileName:  ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/ny/usace/2012_USACE_PostSandy_Connecticut_footprint.KMZ
            fileDescription:  This kmz file shows the extent of coverage for the 2012 USACE Post-Hurricane Sandy Coastal Connecticut lidar data set.
            fileType:  kmz
        descriptiveKeywords:  (MD_Keywords)
            keyword:  Bathymetry/Topography
            keyword:  LiDAR
            keyword:  LAS
            keyword:  Elevation
            type:  (MD_KeywordTypeCode) theme
            thesaurusName:  (CI_Citation)
                title:  Keywords
                date:
        descriptiveKeywords:  (MD_Keywords)
            keyword:  US
            keyword:  Connecticut
            keyword:  Coast
            type:  (MD_KeywordTypeCode) place
            thesaurusName:  (CI_Citation)
                title:  None
                date:
        resourceConstraints:  (MD_Constraints)
            useLimitation:  These data depict the elevations at the time of the survey and are only accurate for that time. 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. Any conclusions drawn from analysis of this information are not the responsibility of NOAA or any of its partners. These data are NOT to be used for navigational purposes.
        resourceConstraints:  (MD_LegalConstraints)
            useLimitation:  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.
        spatialRepresentationType:  (MD_SpatialRepresentationTypeCode) vector
        language:  eng; USA
        topicCategory:  (MD_TopicCategoryCode) elevation
        extent:  (EX_Extent)
            geographicElement:  (EX_GeographicBoundingBox)
                westBoundLongitude:  -73.661202
                eastBoundLongitude:  -71.847828
                southBoundLatitude:  40.951486
                northBoundLatitude:  41.396254
            temporalElement:  (EX_TemporalExtent)
                extent:
                  TimePeriod:
                    beginPosition:  2012-11-14
                    endPosition:  2012-11-16
return to top
    contentInfo:  (MD_ImageDescription)
        attributeDescription:
        contentType:
        cloudCoverPercentage:
          Real:  0
return to top
    distributionInfo:  (MD_Distribution)
        distributionFormat:  (MD_Format)
            name:  LAZ
            version:
        distributor:  (MD_Distributor)
            distributorContact:  (CI_ResponsibleParty)
                organisationName:  DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
                contactInfo:  (CI_Contact)
                    phone:  (CI_Telephone)
                        voice:  843-740-1200
                    address:  (CI_Address)
                        deliveryPoint:  2234 South Hobson Ave.
                        city:  Charleston
                        administrativeArea:  SC
                        postalCode:  29405-2413
                        electronicMailAddress:  coastal.info@noaa.gov
                    onlineResource:  (CI_OnlineResource)
                        linkage: http://coast.noaa.gov
                role:  (CI_RoleCode) distributor
            distributionOrderProcess:  (MD_StandardOrderProcess)
                orderingInstructions:  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.
        distributor:  (MD_Distributor)
            distributorContact:  (CI_ResponsibleParty)
                individualName:  Mike Sutherland
                organisationName:  DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce
                contactInfo:  (CI_Contact)
                    phone:  (CI_Telephone)
                        voice:  303-497-6120
                        facsimile:  303-497-6513
                    address:  (CI_Address)
                        deliveryPoint:  NOAA/NESDIS/NGDC E/GC1 325 Broadway
                        city:  Boulder
                        administrativeArea:  CO
                        postalCode:  80305-3328
                        country:  USA
                        electronicMailAddress:  mike.sutherland@noaa.gov
                    hoursOfService:  7:30am-5:00pm Mountain
                role:  (CI_RoleCode) distributor
            distributionOrderProcess:  (MD_StandardOrderProcess)
                orderingInstructions:  The National Geophysical Data Center serves as the archive for this LIDAR dataset. NGDC should only be contacted for the data if it cannot be obtained from NOAA Coastal Services Center.
return to top
    dataQualityInfo:  (DQ_DataQuality)
        scope:  (DQ_Scope)
            level:  (MD_ScopeCode) dataset
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Horizontal Positional Accuracy Report
            evaluationMethodDescription:  The minimum expected horizontal accuracy was tested to meet or exceed the National Mapping Accuracy Standard (NMAS 1=100).
            result:
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy Report
            evaluationMethodDescription:  Accuracyz = RMSEz X 1.9600 at the 95% confidence level. However the RMSE is only valid when the errors follow a normal distribution which may not always be the case with LiDAR data particularly in vegetated land cover categories. Therefore the data will also be tested using the ASPRS/NDEP method which acknowledges that vegetated land cover may not follow a normal error distribution. The ASPRS/NDEP methods mandate the use of Fundamental Vertical Accuracy (FVA) in open terrain and provides for the optional use of Supplemental Vertical Accuracy (SVA) in other individual land cover categories and Consolidated Vertical Accuracy (CVA) in all land cover categories combined. FVA is calculated at the 95th percent confidence level as a function of RMSEz. SVA and CVA are calculated at the 95th percentile, where 95% of elevations errors have elevation errors equal to or less that the 95th percentile.
            result:
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy
            measureDescription:  RMSE in meters
            result:  (DQ_QuantitativeResult)
                valueUnit:
                  BaseUnit:
                    identifier:  meters
                    unitsSystem:
                value:
                  Record:  0.0013
        report:  (DQ_CompletenessCommission)
            evaluationMethodDescription:  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 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.
            result:
        report:  (DQ_ConceptualConsistency)
            measureDescription:  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).
            result:
        lineage:  (LI_Lineage)
            processStep:  (LE_ProcessStep)
                description:  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.
                dateTime:
                  DateTime:  2012-11-18T00:00:00
                processor:  (CI_ResponsibleParty)
                    individualName:  Rich McClellan
                    organisationName:  Fugro EarthData, Inc.
                    positionName:  Project Manager
                    contactInfo:  (CI_Contact)
                        phone:  (CI_Telephone)
                            voice:  301.948.8550
                            facsimile:  301.963.2064
                        address:  (CI_Address)
                            deliveryPoint:  7320 Executive Way
                            city:  Frederick
                            administrativeArea:  MD
                            postalCode:  21704
                            country:  USA
                            electronicMailAddress:  rmcclellan@fugro.com
                        hoursOfService:  Mon-Fri 8:30am to 5:00pm
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  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
                dateTime:
                  DateTime:  2012-11-19T00:00:00
                processor:  (CI_ResponsibleParty)
                    individualName:  Rich McClellan
                    organisationName:  Fugro EarthData, Inc.
                    positionName:  Project Manager
                    contactInfo:  (CI_Contact)
                        phone:  (CI_Telephone)
                            voice:  301.948.8550
                            facsimile:  301.963.2064
                        address:  (CI_Address)
                            deliveryPoint:  7320 Executive Way
                            city:  Frederick
                            administrativeArea:  MD
                            postalCode:  21704
                            country:  USA
                            electronicMailAddress:  rmcclellan@fugro.com
                        hoursOfService:  Mon-Fri 8:30am to 5:00pm
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  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) The time stamps for all points 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. 7) The classified point cloud data were packaged into geographic Coordinates, NAD83(NA2011) in meters and the vertical datum is the North American Vertical Datum of 1988 (NAVD88) in meters using GEIOD09 for delivery. The data was also cut to the approved tile layout and clipped to the approved project boundary. The technician checked the output LAS files for coverage and format; d) the technician then QCd the dataset for quality assurance and enhanced the Bare Earth classification in the project area for consistent data quality; ie) these final LiDAR tiles were then used in the hydro flattening process. 8) classified LiDAR point cloud data are delivered in LAS 1.2 format: 1 unclassified, 2 ground, 7 low points, 8 model keypoints, 9 water, and 10 ignored points.
                dateTime:
                  DateTime:  2012-11-27T00:00:00
                processor:  (CI_ResponsibleParty)
                    individualName:  Rich McClellan
                    organisationName:  Fugro EarthData, Inc.
                    positionName:  Project Manager
                    contactInfo:  (CI_Contact)
                        phone:  (CI_Telephone)
                            voice:  301.948.8550
                            facsimile:  301.963.2064
                        address:  (CI_Address)
                            deliveryPoint:  7320 Executive Way
                            city:  Frederick
                            administrativeArea:  MD
                            postalCode:  21704
                            country:  USA
                            electronicMailAddress:  rmcclellan@fugro.com
                        hoursOfService:  Mon-Fri 8:30am to 5:00pm
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  The NOAA Coastal Services Center (CSC) received topographic files in LAS format. The files contained lidar elevation and intensity measurements. The data were received in Geographic (NAD83) coordinates and were vertically referenced to NAVD88 using the Geoid12a model. The vertical units of the data were meters. CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid12a. 2. The data were converted to LAZ format.
                dateTime:
                  DateTime:  2013-01-01T00:00:00
                processor:  (CI_ResponsibleParty)
                    organisationName:  DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
                    contactInfo:  (CI_Contact)
                        phone:  (CI_Telephone)
                            voice:  843-740-1200
                        address:  (CI_Address)
                            deliveryPoint:  2234 South Hobson Ave.
                            city:  Charleston
                            administrativeArea:  SC
                            postalCode:  29405-2413
                            electronicMailAddress:  coastal.info@noaa.gov
                        onlineResource:  (CI_OnlineResource)
                            linkage: http://coast.noaa.gov
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  The NOAA National Geophysical Data Center (NGDC) received lidar data files via ftp transfer from the NOAA Coastal Services Center. The data are currently being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/. The data can be used to re-populate the system. The data are archived in LAS or LAZ format. The LAS format is an industry standard for LiDAR data developed by the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless compressed version of LAS developed by Martin Isenburg (http://www.laszip.org/). The data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data are referenced vertically to the ellipsoid (either GRS80 or ITRF94), allowing for the ability to apply the most up to date geoid model when transforming to orthometric heights.
                dateTime:
                  DateTime:  2013-02-20T00:00:00
                processor:  (CI_ResponsibleParty)
                    individualName:  Mike Sutherland
                    organisationName:  DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce
                    contactInfo:  (CI_Contact)
                        phone:  (CI_Telephone)
                            voice:  303-497-6120
                            facsimile:  303-497-6513
                        address:  (CI_Address)
                            deliveryPoint:  NOAA/NESDIS/NGDC E/GC1 325 Broadway
                            city:  Boulder
                            administrativeArea:  CO
                            postalCode:  80305-3328
                            country:  USA
                            electronicMailAddress:  mike.sutherland@noaa.gov
                        hoursOfService:  7:30am-5:00pm Mountain
                    role:  (CI_RoleCode) processor
return to top
    metadataMaintenance:  (MD_MaintenanceInformation)
        maintenanceAndUpdateFrequency:  (MD_MaintenanceFrequencyCode) annually
        dateOfNextUpdate:  2014-02-20
        maintenanceNote:  This metadata was automatically generated from the FGDC Content Standards for Digital Geospatial Metadata standard (version FGDC-STD-001-1998) using the 2013-01-04 version of the FGDC RSE to ISO 19115-2 for LiDAR transform.
        maintenanceNote:  Translated from FGDC 2013-02-20T11:26:29.999-07:00