Text View of ISO 19115/19115-2 Metadata with Links to Guidance on NOAA EDM WikiAlternate Views: Get Data, FAQ, ISO Rubric, DOI Rubric, CSW, HTML, Components, XML

2010 US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) Lidar: Delaware (Topo)

spatialRepresentationInfo
referenceSystemInfo
referenceSystemInfo
identificationInfo
distributionInfo
dataQualityInfo
metadataMaintenance

 (MI_Metadata)
    fileIdentifier:  gov.noaa.csc.maps:2010_USACE_DE_m1125
    language:  eng; USA
    characterSet:  (MD_CharacterSetCode) utf8
    hierarchyLevel:  (MD_ScopeCode) dataset
    contact:  Mike Sutherland(author) (CI_ResponsibleParty)
        organisationName:
        role:  (CI_RoleCode) author
    dateStamp:  2013-01-22
    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:  2010 US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) Lidar: Delaware (Topo)
            date:  (CI_Date)
                date:
                dateType:  (CI_DateTypeCode) publication
            citedResponsibleParty:  NOAA CSC (originator)
            citedResponsibleParty:  JALBTCX (originator)
            citedResponsibleParty:  NOAA CSC (publisher) (CI_ResponsibleParty)
                organisationName:
                role:  (CI_RoleCode) publisher
            presentationForm:  (CI_PresentationFormCode) imageDigital
        abstract:  These files contain topographic lidar data classified as ground (2) and unclassified (1) in accordance with the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards. These data were collected by the Compact Hydrographic Airborne Rapid Total Survey (CHARTS) system along the coast of Delaware. CHARTS integrates topographic and bathymetric lidar sensors, a digital camera and a hyperspectral imager on a single remote sensing platform for use in coastal mapping and charting activities. Data coverage generally extends along the coastline from the waterline inland 500 meters (topography) and offshore 1,000 meters or to laser extinction (bathymetry). Native lidar data is not generally in a format accessible to most Geographic Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data into 3-dimensional positions that can be imported into GIS software for visualization and further analysis. Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to the North American Datum of 1983 (NAD83). Vertical positions are referenced to the NAD83 ellipsoid and provided in meters. The National Geodetic Survey's (NGS) GEOID03 model is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). The 3-D position data are sub-divided into a series of LAS files, each covering approximately 5 kilometers of shoreline. The file index is provided by the shape file, "de_boxes.shp", and the numbers used to identify files are in the "Box" field of the shape file. The LAS file naming convention is based on the year, project, area name, "Box," and the product type. An example file name is "2010_NCMP_DE_01_GeoClassified.las", where 2010 is the year of data collection, NCMP is the project under which data were collected, DE is the area of data collection, 01 is the "Box" number and "GeoClassified" is the product type. The format of the file is LAS version 1.1.
        purpose:  These data were collected as a part of the NCMP to depict the elevations above the water in the Delaware coastal zone.
        credit:  Acknowledgement of US Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX) would be appreciated in products derived from these data.
        status:  (MD_ProgressCode) completed
        pointOfContact:  JALBTCX (pointOfContact) (CI_ResponsibleParty)
            organisationName:
            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/de/2010_USACE_JALBTCX_Delaware_Lidar.kmz
            fileDescription:  This kmz file shows the extent of coverage for the 2010 USACE Delaware lidar data set.
            fileType:  kmz
        descriptiveKeywords:  (MD_Keywords)
            keyword:  Bathymetry/Topography
            keyword:  U.S. Army Corps of Engineers, Mobile District
            keyword:  JALBTCX
            keyword:  NCMP
            keyword:  USACE
            keyword:  JALBTCX
            keyword:  CHARTS
            keyword:  SHOALS
            keyword:  LAS
            keyword:  Lidar
            keyword:  Coastal Elevation
            keyword:  Terrain Elevation
            keyword:  Topobathy
            type:  (MD_KeywordTypeCode) theme
            thesaurusName:  (CI_Citation)
                title:  None
                date:
        descriptiveKeywords:  (MD_Keywords)
            keyword:  US
            keyword:  Delaware
            keyword:  Sussex County
            type:  (MD_KeywordTypeCode) place
            thesaurusName:  (CI_Citation)
                title:  None
                date:
        descriptiveKeywords:  (MD_Keywords)
            keyword:  2010
            keyword:  September
            type:  (MD_KeywordTypeCode) temporal
            thesaurusName:  (CI_Citation)
                title:  None
                date:
        resourceConstraints:  Lidar Use Limitation
        resourceConstraints:  NOAA Legal Statement
        spatialRepresentationType:  (MD_SpatialRepresentationTypeCode) vector
        language:  eng; USA
        topicCategory:  (MD_TopicCategoryCode) elevation
        extent:  (EX_Extent)
            geographicElement:  (EX_GeographicBoundingBox)
                westBoundLongitude:  -75.179399
                eastBoundLongitude:  -75.048537
                southBoundLatitude:  38.450746
                northBoundLatitude:  38.832787
            temporalElement:  (EX_TemporalExtent)
                extent:
                  TimePeriod:
                    beginPosition:  2010-09-11
                    endPosition:  2010-09-25
return to top
    distributionInfo:  (MD_Distribution)
        distributionFormat:  (MD_Format)
            name:  LAZ
            version:
        distributor:  (MD_Distributor)
            distributorContact:  NOAA CSC(distributor) (CI_ResponsibleParty)
                organisationName:
                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:  Mike Sutherland
            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 data positions were obtained using post processed KGPS methods. The horizontal accuracy of the data is better than plus or minus 0.75 m.
            result:
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Horizontal Positional Accuracy
            measureDescription:  1 Sigma
            result:  (DQ_QuantitativeResult)
                valueUnit:
                  BaseUnit:
                    identifier:  meters
                    unitsSystem:
                value:
                  Record:  0.75
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy Report
            evaluationMethodDescription:  The data positions were obtained using post processed KGPS methods. The vertical accuracy of the data is better than plus or minus 0.20 m.
            result:
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy
            measureDescription:  1 Sigma
            result:  (DQ_QuantitativeResult)
                valueUnit:
                  BaseUnit:
                    identifier:  meters
                    unitsSystem:
                value:
                  Record:  0.20
        report:  (DQ_CompletenessCommission)
            evaluationMethodDescription:  None provided
            result:
        report:  (DQ_ConceptualConsistency)
            measureDescription:  The data provided in this file were tested against ground truth data. At these locations the lidar data matched within 0.20 meters and different flight line data agreed within 0.20 meters.
            result:
        lineage:  (LI_Lineage)
            processStep:  (LE_ProcessStep)
                description:  These data were collected using the CHARTS system. It is owned by the Naval Oceanographic Office and operated through contract. The system collects topographic lidar data at 9 kHz, bathymetric lidar data at 1 kHz and RGB imagery at 1Hz. A CASI-1500 hyperspectral line scanner is integrated with the system as well. Aircraft position, velocity and acceleration information are collected through a combination of Novatel and POS A/V 410 equipment. All raw data streams are transferred to the office for downloading and processing in SHOALS GCS software. Aircraft position data are processed using POSPac software and the results are combined with the lidar data to produce 3-D positions for each lidar shot. Upon inspection and QA/QC in the software packages Fledermaus and PFM_ABE, anomalous data are flagged as invalid. PFM_ABE's chartsLAS module then converts all valid data from ellipsoid to orthometric heights based on the NGS' GEOID03 model and exports topographic data as a series of LAS files with a single file per flightline per 5km box.
                dateTime:
                  DateTime:  2010-01-01T00:00:00
                processor:  JALBTCX (processor) (CI_ResponsibleParty)
                    organisationName:
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  The flightline LAS files are imported into the TerraScan V11 module within MicroStation V8.0. The resulting LAS files are thinned to eliminate duplicate points. A customized classification macro is used to distinguish ground points (2) and unclassified points (1). The classification results are QC'd and any misclassified points are manually edited. In areas of dense vegetation the bare ground points might be incorrectly classified due to the inability of the laser to penetrate the canopy and reach the bare ground. In these areas, JALBTCX defaults to the algorithm's "ground" surface instead of manually reclassifying those points. The points are exported to an ASCII file containing the following fields: longitude, latitude, elevation (orthometric), intensity, classification, mirror angle, time (GPS time), number of echos, and echo number. The ASCII file is converted to LAS with the txt2las code from LAStools (<http://www.cs.unc.edu/~isenburg/lastools/>).
                dateTime:
                  DateTime:  2010-01-01T00:00:00
                processor:  JALBTCX (processor) (CI_ResponsibleParty)
                    organisationName:
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  The NOAA Coastal Services Center (CSC) received data in LAS v1.1 format. The files contained LiDAR elevation and intensity measurements. The data were received in geographic coordinates (NAD83) and vertically referenced to NAVD88 using the Geoid03 model. The vertical units of data were meters. The data were classified according to ASPRS LAS classification scheme (1 = unclassified, 2 = ground). CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. The LAS files were converted from orthometric heights to ellipsoidal heights (GRS80) using Geoid 03. 2. The LAS data were sorted by latitude and the headers were updated. 3. The data were converted to LAZ format.
                dateTime:
                  DateTime:  2012-02-01T00:00:00
                processor:  NOAA CSC (processor) (CI_ResponsibleParty)
                    organisationName:
                    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-01-22T00:00:00
                processor:  Mike Sutherland (processor) (CI_ResponsibleParty)
                    organisationName:
                    role:  (CI_RoleCode) processor
return to top
    metadataMaintenance:  (MD_MaintenanceInformation)
        maintenanceAndUpdateFrequency:  (MD_MaintenanceFrequencyCode) annually
        dateOfNextUpdate:  2014-01-22
        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-01-22T13:08:04.096-07:00