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: Northeast (Topo)

spatialRepresentationInfo
referenceSystemInfo
referenceSystemInfo
identificationInfo
distributionInfo
dataQualityInfo
metadataMaintenance

 (MI_Metadata)
    fileIdentifier:  gov.noaa.csc.maps:2010_USACE_NE_m1174
    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: Northeast (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 in LAS 1.2 format classified as ground (2) and unclassified (1) in accordance with the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards. Rejected or invalid data is classified as noise (7). These data were collected by a HawkEye II (HEII) lidar sensor. The HEII integrates topographic and bathymetric lidar sensors, and a digital camera on a single remote sensing platform for use in coastal mapping and charting activities. Data coverage generally extends along the MA coastline, from the waterline onshore 500 meters. Native lidar data is not generally in a format accessible to most Geographical Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data into 3D 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 acquired to the NAD83 ellipsoid. The National Geodetic Survey's (NGS) GEOID09 model was used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). The 3D position data are sub-divided into a series of files each covering approximately 5 kilometers of shoreline.
        purpose:  These data were collected as a part of the NCMP to depict the elevations above the water in the coastal zone of Rhode Island, Massachusetts, New Hampshire, and Maine.
        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/ma/2010_USACE_JALBTCX_Northeast_Lidar.kmz
            fileDescription:  This kmz file shows the extent of coverage for the 2010 USACE Northeast 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:  Rhode Island
            keyword:  Massachusetts
            keyword:  New Hampshire
            keyword:  Maine
            type:  (MD_KeywordTypeCode) place
            thesaurusName:  (CI_Citation)
                title:  None
                date:
        descriptiveKeywords:  (MD_Keywords)
            keyword:  2010
            keyword:  May
            keyword:  July
            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:  -71.966003
                eastBoundLongitude:  -69.672420
                southBoundLatitude:  41.288632
                northBoundLatitude:  43.818460
            temporalElement:  (EX_TemporalExtent)
                extent:
                  TimePeriod:
                    beginPosition:  2010-05-24
                    endPosition:  2010-07-10
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 inertially aided KGPS methods. The horizontal accuracy of the data is better than 0.50m RMSE.
            result:
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Horizontal Positional Accuracy
            measureDescription:  Accuracy based on 1.96 X RMSE.
            result:  (DQ_QuantitativeResult)
                valueUnit:
                  BaseUnit:
                    identifier:  meters
                    unitsSystem:
                value:
                  Record:  0.98
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy Report
            evaluationMethodDescription:  The data positions were obtained using post processed inertially aided KGPS methods. Tested 0.172m fundamental vertical accuracy at 95 percent confidence level in open terrain using RMSEz x 1.9600. Tested 0.270m suplemental vertical accuracy at 95th percentile in short grass. Tested 0.553m suplemental vertical accuracy at 95th percentile in tall grass. Tested 0.640m suplemental vertical accuracy at 95th percentile in brush/canopy.
            result:
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy
            measureDescription:  Tested fundamental vertical accuracy at 95 percent confidence level in open terrain.
            result:  (DQ_QuantitativeResult)
                valueUnit:
                  BaseUnit:
                    identifier:  meters
                    unitsSystem:
                value:
                  Record:  0.172
        report:  (DQ_CompletenessCommission)
            evaluationMethodDescription:  None provided
            result:
        report:  (DQ_ConceptualConsistency)
            measureDescription:  The data provided in this file were tested against ground truth data. Tested 0.172m fundamental vertical accuracy at 95 percent confidence level in open terrain using RMSEz x 1.9600.
            result:
        lineage:  (LI_Lineage)
            processStep:  (LE_ProcessStep)
                description:  These data were collected using a HEII system. The system collects topographic lidar data at 64kHz, bathymetric lidar data at 4kHz and RGB imagery at 1Hz. Aircraft position, velocity and acceleration information are collected using an Applanix POS A/V 410. All raw data are processed using AHAB's Coastal Survey Studio (CSS) 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. Fledermaus and GreenC Solutions software is used to inspect and QA/QC data, and anomalous data are flagged as invalid. Data are exported to LAS format using GreenC Solutions and imported to Terrascan for classification. A customized classification macro is used to distinguish ground points (2) and unclassified points (1). The classification results are reviewed 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. Classified data are exported from Terrascan and Blue Marble Desktop converts all classified LAS data from UTM to NAD83 geographic coordinates and NAVD88 heights using the Geoid 09 model.
                dateTime:
                  DateTime:  2010-11-30T00:00:00
                processor:  (CI_ResponsibleParty)
                    organisationName:  Geomatics Data Solutions
                    positionName:  Data Manager
                    contactInfo:  (CI_Contact)
                        phone:  (CI_Telephone)
                            voice:  760-536-6852
                        address:  (CI_Address)
                            deliveryPoint:  4128 Ingalls St.
                            city:  San Diego
                            administrativeArea:  CA
                            postalCode:  92103
                            country:  USA
                            electronicMailAddress:  Info@GEomaticsDS.com
                        hoursOfService:  8am - 5pm M-F
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  The NOAA Coastal Services Center (CSC) received data in LAS v1.2 format. The files contained LiDAR elevation measurements. The data were received in geographic coordinates (NAD83) and vertically referenced to NAVD88 using the Geoid09 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 09. 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:13:18.236-07:00