|
|
2008 City of Baltimore LidarspatialRepresentationInforeferenceSystemInfo referenceSystemInfo identificationInfo distributionInfo dataQualityInfo metadataMaintenance |
| (MI_Metadata) fileIdentifier: gov.noaa.csc.maps:2008_CityofBaltimore_m1199 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: 2008 City of Baltimore Lidar date: (CI_Date) date: 2012-07-01 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: DOC/NOAA/NOS/CSC > Coastal Services Center, 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: csc.info@noaa.gov role: (CI_RoleCode) originator citedResponsibleParty: (CI_ResponsibleParty) organisationName: KCI/Sanborn Joint Venture Partnership, L.L.C. (hereafter referred to as KCI/Sanborn) role: (CI_RoleCode) originator citedResponsibleParty: (CI_ResponsibleParty) organisationName: DOC/NOAA/NOS/CSC > Coastal Services Center, 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: csc.info@noaa.gov role: (CI_RoleCode) publisher presentationForm: (CI_PresentationFormCode) imageDigital abstract: In the spring of 2008, the City of Baltimore expressed an interest to upgrade the City GIS Database with mapping quality airborne LiDAR data. The City of Baltimore currently had in place a contract for mapping GIS/services with the KCI/Sanborn Joint Venture Partnership, L.L.C. under Project 1051. The City of Baltimore issued Change Order #1 on on Project 1051 for the LiDAR acquisition and processing. KCI/Sanborn acquired the LiDAR data over the City of Baltimore (approximately 90 square miles) during one long mission on 15 April 2008. A Leica Airborne Airborne Laser Scanner Model ALS 50 was used in a Sanborn Aero Commander 500B (Registration N6172X) to acquire the data. The airborne mission was flown 15 April 2008. The LiDAR system acquired calibration data the same day by conducting flight passes over a known ground surface before and the LiDAR mission. During final data processing, the calibration parameters were used in the final post-processing software. The acquired LiDAR data were processed to obtain the following deliverables: -DEMs of first and last returns and bare earth (all point data) -LAS format data in a tile grid provided by the City/KCI -Gridded DEM in ESRI format (Arc Binary Grid -Arc/INFO Lattice ) produced from Bare Earth Mass Points in 1-meter resolution (Grid size) -Associated FGDC compliant metadata in XML format The project specifications called for the LiDAR survey to comply with industry standard FEMA guidelines for accuracy. The FEMA requirement for this type of mapping calls for vertical errors not to exceed 0.185 meter (0.61 feet) RMSE when compared with ground check points over open flat terrain and 0.370 meter (1.22 feet) for other types of terrain. This accuracy requirement was comfortably met with comparing LiDAR derived elevations against 50 ground control check points provided by KCI Technologies. These control points were photo control points used as part of the photogrammetric mapping project and independent LiDAR checkpoints surveyed by KCI and Mercado after the data was delivered. The RMSE error observed was 0.058 meter (0.189 feet) over all 50 check points. purpose: This LIDAR operation was designed to provide a high density set of masspoints within the defined areas. The data sets are suitable for the development of contours for use in hydraulic/hydrologic model development, and for assessing environmental impacts. Typical uses for the dataset include FEMA Flood Map Modernization, DFIRM map updates, watershed delineation and other hydro studies per FEMA specifications, as well as general use by the City of Baltimore. status: (MD_ProgressCode) completed pointOfContact: (CI_ResponsibleParty) individualName: Josh Nimetz organisationName: KCI/Sanborn Joint Venture Partnership, L.L.C. (hereafter referred to as KCI/Sanborn) positionName: LiDAR Production Manager contactInfo: (CI_Contact) phone: (CI_Telephone) voice: 719-264-5513 facsimile: 719-264-5631 address: (CI_Address) deliveryPoint: 1935 Jamboree Drive Suite 100 city: Colorado Springs administrativeArea: CO postalCode: 80920 country: USA electronicMailAddress: jnimetz@sanborn.com hoursOfService: 8am - 5pm MST M-F 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/md/2008_City_of_Baltimore_Lidar.kmz fileDescription: This kmz file shows the extent of coverage for the 2008 City of Baltimore lidar data set. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: Bathymetry/Topography keyword: DEM keyword: Lidar keyword: Surface Model keyword: Digital Elevation Model keyword: Hydrologic Modeling keyword: LIDAR keyword: LAS keyword: Drainage Area keyword: Coastal Elevation keyword: Terrain Elevation type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: None date: descriptiveKeywords: (MD_Keywords) keyword: US keyword: Maryland keyword: City of Baltimore type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: None date: descriptiveKeywords: (MD_Keywords) keyword: 2008 keyword: April type: (MD_KeywordTypeCode) temporal 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.713701 eastBoundLongitude: -76.526548 southBoundLatitude: 39.195787 northBoundLatitude: 39.372703 temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2008-04-15 return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: LAZ version: distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: DOC/NOAA/NOS/CSC > Coastal Services Center, 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: csc.info@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 project specifications called for the LiDAR survey to comply with industry standard FEMA guidelines for horizontal accuracy. result: report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy measureDescription: Assumed to meet FEMA specifications for horizontal accuracy. result: (DQ_QuantitativeResult) valueUnit: BaseUnit: identifier: meters unitsSystem: value: Record: 1.0 report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy Report evaluationMethodDescription: The FEMA requirements call for vertical errors not to exceed 0.185 meter (0.61 feet) RMSE when compared with ground check points over open flat terrain. result: report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy measureDescription: The LiDAR derived elevations for this project compared against 50 ground control check points showed the RMSE error observed was 0.058 meters. result: (DQ_QuantitativeResult) valueUnit: BaseUnit: identifier: meters unitsSystem: value: Record: 0.058 report: (DQ_CompletenessCommission) evaluationMethodDescription: None provided result: report: (DQ_ConceptualConsistency) measureDescription: All LAS formatted LiDAR data are validated to ensure that data on delivery media is in correct physical format and is readable and correctly georeferenced and projected. Note that LiDAR intensity is not calibrated or normalized. result: lineage: (LI_Lineage) processStep: (LE_ProcessStep) description: Using a Leica Geosystems ALS50 Light Detection And Ranging (LiDAR) system, 29 flight lines of an average density of 1.0 meter ground sample distance, data were collected over areas in Baltimore City, MD (approximately 90 square miles). Multiple returns were recorded for each laser pulse along with an intensity value for each return. The data acquisition occurred in 1 mission on April 15, 2008. During the LIDAR campaign, the Sanborn field crew conducted a GPS field survey to establish final coordinates of the ground base stations for final processing of the base-remote GPS solutions. Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a Smoothed Best Estimate of Trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. The overlap between flight lines was removed to provide a homogeneous coverage, and the coverage was classified to extract a bare earth digital elevation model (DEM). Airborne GPS is differentially processed using the GrafNAV V7.50 software by Waypoint Consulting of Calgary, Alberta, Canada. The PDOP and distance separation is as follows: The classification and quality control (QC) of LiDAR data is carried out using TerraScan software by Terrasolid Limited of Helinski, Finland. IMU data provides information concerning roll, pitch and yaw of collection platform during collection event. IMU information allows the pulse vector to be properly placed in 3D space allowing the distance from the aircraft reference point to be properly positioned on the elevation model surface. The IMU data is processed using the PosPac V4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada. The reflective surface is derived using the ALS Post Processor software by Leica Geosystems GIS & Mapping Division of Atlanta, Georgia. dateTime: DateTime: 2008-04-15T00:00:00 processor: (CI_ResponsibleParty) individualName: Josh Nimetz organisationName: Sanborn Map Company, Inc. positionName: LiDAR Production Manager contactInfo: (CI_Contact) phone: (CI_Telephone) voice: 719-264-5513 facsimile: 719-264-5631 address: (CI_Address) deliveryPoint: 1935 Jamboree Drive Suite 100 city: Colorado Springs administrativeArea: CO postalCode: 80920 country: USA electronicMailAddress: jnimetz@sanborn.com hoursOfService: 8am - 5pm MST M-F 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 state plane coordinates (Maryland; NAD83) and vertically referenced to NAVD88 using the Geoid03 model. The vertical units of data were feet. The data were classified according to ASPRS LAS classification scheme (0 = never classified, 1 = unclassified, 2 = ground 3 = low vegetation, 7 = noise, 12 = overlap). CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from state plane coordinates to geographic coordinates (NAD83). 2. The data were converted from orthometric heights to ellipsoidal heights (GRS80) using Geoid 03. 3. The vertical units of the data were changed from feet to meters. 2. The LAS data were sorted by latitude and the headers were updated. 3. The data were converted to LAZ format. dateTime: DateTime: 2012-07-01T00:00:00 processor: (CI_ResponsibleParty) organisationName: DOC/NOAA/NOS/CSC > Coastal Services Center, 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: csc.info@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 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:01.53-07:00 |