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
distributionInfo
dataQualityInfo
metadataMaintenance

2005 Baltimore County Maryland Lidar
 (MI_Metadata)
    fileIdentifier:  gov.noaa.csc.maps:2005_baltimore_county_m1382
    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-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:  2005 Baltimore County Maryland Lidar
            date:  (CI_Date)
                date:  2012-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:  Baltimore County, MD GIS Services
                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:  In the spring of 2005, Sanborn as part of the Dewberry team was contracted to execute a LiDAR (Light Detection and Ranging) survey campaign to collect the 3-dimensional positions of a dense set of masspoints for the entire 689 plus square mile project area of Baltimore County, Maryland. These data are suitable for the development of a digital elevation model (DEM) to support orthometric photo rectification and contouring. The lidar first and Last Return value data were obtained from the post processed data and provided in separate files containing all georeferenced First Return and Last Return data in an ASCII comma delimited format to the NOAA Coastal Services Center. For data storage and Digital Coast provisioning purposes, the NOAA Coastal Services Center converted the ascii data to geographic coordinates, ellipsoid heights in meters, and las format and created a bare earth data set using an automated algorithm.
        purpose:  The Baltimore County LiDAR campaign was designed specifically to collect LIDAR derived masspoints at an approximate spacing of 1.5 meters or better within the project area. The data was processed to facilitate the generation of an appropriate DEM for orthorectification and 2' contour mapping. Rigorous quality assurance procedures were followed to ensure that the appropriate data accuracy was achieved.
        status:  (MD_ProgressCode) completed
        pointOfContact:  (CI_ResponsibleParty)
            organisationName:  Baltimore County GIS Services
            contactInfo:  (CI_Contact)
                phone:  (CI_Telephone)
                    voice:  410.887.2553
                address:  (CI_Address)
                    deliveryPoint:  400 Washington Ave
                    city:  Towson
                    administrativeArea:  Maryland
                    postalCode:  21204
                    country:  US
            role:  (CI_RoleCode) pointOfContact
        resourceMaintenance:  (MD_MaintenanceInformation)
            maintenanceAndUpdateFrequency:  (MD_MaintenanceFrequencyCode) notPlanned
        graphicOverview:  (MD_BrowseGraphic)
            fileName:  ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/md/2005_Baltimore_County_Lidar.kmz
            fileDescription:  This kmz file shows the extent of coverage for the 2005 Baltimore County lidar data set.
            fileType:  kmz
        descriptiveKeywords:  (MD_Keywords)
            keyword:  Bathymetry/Topography
            keyword:  Lidar
            keyword:  DEM
            keyword:  Digital Elevation Model
            keyword:  Elevation
            keyword:  Digital Terrain Model
            keyword:  Point cloud data
            type:  (MD_KeywordTypeCode) theme
            thesaurusName:  (CI_Citation)
                title:  None
                date:
        descriptiveKeywords:  (MD_Keywords)
            keyword:  United States
            keyword:  Maryland
            keyword:  Baltimore County
            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:  -76.9156
                eastBoundLongitude:  -76.3155
                southBoundLatitude:  39.1934
                northBoundLatitude:  39.7221
            temporalElement:  (EX_TemporalExtent)
                extent:
                  TimePeriod:
                    beginPosition:  2005-03-18
                    endPosition:  2005-04-15
        supplementalInformation:  The original Lidar Acquisition plan was designed for all East/West flight lines. Due to several Air Traffic Control Restrictions in the southern portion of the County, 54 North/South flight lines were used to acquire the southern portion of the county, minimizing time in restricted airspace. In addition, the Bay Coast line was planned for acquisition within one hour either side of low tide. Due to the same ATC restrictions it was impossible to comply with the low tide requirement for this area.
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:  LIDAR First Return and Last Return data were compared with airport surveyed elevations provided by Kinematic survey. The data and survey were compared and verified per project specifications. The horizontal accuracy of the FR and LR data meets the 15 cm accuracy normally achieved from this flight height and scan resolution for this data set.
            result:
        report:  (DQ_AbsoluteExternalPositionalAccuracy)
            nameOfMeasure:  Vertical Positional Accuracy Report
            evaluationMethodDescription:  The vertical accuracy of the FR and LR data was checked using LIDAR First Return and Last Return data were compared with airport surveyed elevations provided by Kinematic survey. The data and survey were compared and verified per project specifications. The Fundamental Vertical Accuracy (FVA) tested 21.9 cm (0.72 ft) at the 95% confidence level in open terrain, based on RMSE x 1.96. The RMSE for this data set is 11.2 cm. For more information about the vertical accuracy, please refer to The Report of Vertical Accuracy Testing which may be accessed at: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/md/2005_Baltimore_County_Lidar_Vertical_Accuracy_Report.pdf
            result:
        report:  (DQ_CompletenessCommission)
            evaluationMethodDescription:  Sanborn and Dewberry performed various inspections of the BE data to ensure that each file contained points within the project limits. Checks for correct tile naming were performed. The BE data generally may contain some voids where insufficient energy was reflected from the surface to generate a valid return from the terrain. Voids tend to occur in heavily vegetated areas, water bodies, and beneath buildings, motor vehicles, bridges, etc. There were no gaps in the data due to insufficient side overlap or instrument malfunctions.
            result:
        report:  (DQ_ConceptualConsistency)
            measureDescription:  The FR and LR data is is supplied as an ASCII comma delimited file with each point represented with an X, Y and elevation. The data is processed from the last return raw point cloud data. This bare earth (BE) data is consistent with the original data. Data were filtered using automated procedures followed by manual editing to remove points that did not belong to the terrain surface (e.g. water, vegetation, buildings, system (noise)).
            result:
        lineage:  (LI_Lineage)
            processStep:  (LE_ProcessStep)
                description:  Step 1- LIDAR Data Acquisition Sanborn flew the entire project area as a contiguous block of more than 870 square miles using the ALTM 2050 LIDAR sensor equipped with Airborne GPS and IMU positioning and orientation units. A total of 54 north south flight lines and 90 east-west flight lines were required to cover the required entire County project area. Prior to data collection, two AGPS ground stations were established to support the LiDAR campaign. NGS monument BELL (PID AJ7978) was used as the northern base station, while NGS monument MTN-B (PID AI4374) was used as the Martin State Airfield base station. The MTN-B point was used in a previous survey campaign completed by Sanborn in 2001. Since the MTN-B point has only horizontal coordinates published, the vertical coordinates generated by the 2001 adjustment were used. Point MTN-B is First Order horizontal, while BELL is Horizontal Order A and Vertical Order 2. We tied our network and adjusted our mini network vertically to a First Class I and five second Class II. The network accuracy is a function of the fully constrained adjustment and follows very closely the NOAA Technical Memorandum NOS NGS58 " Guidelines for Establishing GPS Derived Ellipsoid Heights (Standards: 2 cm and 5 cm)," November 1997 yielding sound network adjustment. The combination (Horizontal & Vertical) achieved the height adjustment meeting the 5 cm standard. Adjustments constraints for the survey to derive the coordinates The Optech ALTM (Airborne Laser Terrain Mapping) LiDAR system was calibrated regularly by conducting several passes over a flat surface of known elevation at the job location. Calibration flights were performed prior to and following every mission. The calibration parameters were inserted into the post-processing software before final data processing. The observations used to establish the fiducial and survey point networks were made at various times during the LiDAR data collection period. The LiDAR aircraft arrived on site March 18th, 2005 and the LiDAR data collection was accomplished between March 18, 2005 and April 15, 2005. The flight plan for the project includes the following specifications to fully meet the project requirements. Single pass density of approximately 1.0 square meters per sample Average area sampling density - 1.4 square meters per sample Swath width 728 meters Flight altitude 1000 meters Flight line spacing -589 meters with 125 meters overlap The Scan Frequency- 35 Hz *Scan Angle- 20 degrees Aircraft ground speed -- 140 knots System Calibration pre and post mission Two GPS base stations within 30 KM. The acquired LiDAR data was combined by flight line in a merge process that eliminated redundant points. The data was clipped into more manageable 1 KM by 1 KM tiles bounds. Noise, or anomalous returs were filtered from all data during this processing step. The data was quality check using commercial software TerraScan.
                dateTime:
                  DateTime:  2005-01-01T00:00:00
                processor:  (CI_ResponsibleParty)
                    individualName:  Mr. James Young
                    organisationName:  Sanborn Map Company Inc.
                    positionName:  Project Engineer
                    contactInfo:  (CI_Contact)
                        phone:  (CI_Telephone)
                            voice:  719-264-5602
                        address:  (CI_Address)
                            deliveryPoint:  1935 Jamboree Drive #100
                            city:  Colorado Springs
                            administrativeArea:  CO
                            postalCode:  80920
                            country:  US
                    role:  (CI_RoleCode) processor
            processStep:  (LE_ProcessStep)
                description:  Step 2- AGPS Processing and Point Cloud- First and Last Return Data Processing Final post-processing of LiDAR data involves several steps. The airborne GPS data were post-processed using Waypoint's GravNAVTM software (version 6.03). A fixed-bias carrier phase solution was computed in both the forward and reverse chronological directions. All LiDAR acquisition was limited to periods when the PDOP was less than 4.0. The GPS trajectory is combined with the raw IMU data and post-processed using Applanix Inc.'s POSPROC Kalman Filtering software. This results in a two-fold improvement in the attitude accuracies over the real-time INS data. The best estimated trajectory (BET) and refined attitude data are then re-introduced into the Optech REALM software to compute the laser point-positions - the trajectory is combined with the attitude data and laser range measurements to produce the 3-dimensional coordinates of the mass points. The acquired LiDAR data was combined by flight line in a merge process that eliminated redundant points. The data was clipped into more manageable 1 KM by 1 KM tiles bounds. Noise or anomalous returns were filtered from all data during this processing step. The data was quality check using commercial software TerraScan.
                dateTime:
            processStep:  (LE_ProcessStep)
                description:  Step 3-- Elevation and Coordinate Processing All elevation data was processed on a point by point basis for ellipsoid to orthometric height conversion using the National Geodetic Survey (NGS) Geoid Model, GEOID99. Datum and coordinate system conversion from WGS84 to the Maryland State Plane coordinate system was performed using U.S. Army Corps of Engineers CorpsCon software algorithms. The LIDAR first and last return data is filtered to remove the vegetation and above ground manmade features. Computations are produced for both first and last laser return observations. The ground-filtered delivery and corresponding regular grid DEM are produced from the last return data. The first return information provides a useful depiction of the "canopy" within the project area. Laser point filtering was accomplished using TerraScan LiDAR processing and modeling software. The bare earth surface generated by TerraScan is used to produce regular grid DEMs.
                dateTime:
                  DateTime:  2005-01-01T00:00:00
            processStep:  (LE_ProcessStep)
                description:  Step 4 First and Last return data Formatting The Terrascan final processed first and last return data is exported in exported in ASCII comma delimited file format and clipped to the County' standard tile layout. 837 FR files and 837 LR Data tiles were supplied on DVD media. QC is performed
                dateTime:
                  DateTime:  2005-01-01T00:00:00
            processStep:  (LE_ProcessStep)
                description:  The NOAA Coastal Services Center (CSC) received the first and last return files in ascii format. NOAA CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were filtered for elevation outliers 2. The data were converted from orthometric heights to ellipsoid heights using Geoid03 3. The data were converted from Maryland State Plane to geographic coordinates 4. The vertical units of the data were converted from feet to meters 5. A bare earth data set was created using an automated algorithm. 6. The data were converted to LAZ format.
                dateTime:
                  DateTime:  2012-08-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-01-22T00: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-01-22
        maintenanceNote:  This metadata was automatically generated from the FGDC Content Standard 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:16.932-07:00