| 2008 City of Baltimore Lidar | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49785 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset contact: (CI_ResponsibleParty) organisationName: OCM Partners contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) role: (CI_RoleCode) resourceProvider contact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2024-02-29T00:00:00 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: return to top referenceSystemInfo: return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(NSRS2007) / UTM zone 18N date: (CI_Date) date: 2008-11-12 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/CoordRefSystem/3725/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:3725 version: 6.18.3 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2008 City of Baltimore Lidar alternateTitle: md2008_baltimorecity_m1199_metadata date: (CI_Date) date: 2012-07 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49785 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49785 protocol: WWW:LINK-1.0-http--link name: Full Metadata Record description: View the complete metadata record on InPort for more information about this dataset. function: (CI_OnLineFunctionCode) information role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) 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. Original contact information: Contact Name: Josh Nimetz Contact Org: KCI/Sanborn Joint Venture Partnership, L.L.C. (hereafter referred to as KCI/Sanborn) Title: LiDAR Production Manager Phone: 719-264-5513 Email: jnimetz@sanborn.com This data set contains point cloud data(' in LAZ (compressed LAS) format', ''). The data may have been reprojected or otherwise modified from the original data in an automated process. Disregard projection information in this abstract and refer to the spatial reference section. 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) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) asNeeded descriptiveKeywords: (MD_Keywords) keyword: Drainage Area type: (MD_KeywordTypeCode) theme descriptiveKeywords: (MD_Keywords) keyword: 2008 keyword: April type: (MD_KeywordTypeCode) temporal descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-03-21 from the NOAA system. Cite As: OCM Partners, [Date of Access]: 2008 City of Baltimore Lidar [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49785. resourceConstraints: (MD_Constraints) useLimitation: NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose. resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-03-21 from the NOAA system. Access Constraints: None resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-03-21 from the NOAA system. Use Constraints: 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. These data depict the heights at the time of the survey and are only accurate for that time. resourceConstraints: (MD_LegalConstraints) useLimitation: (MD_RestrictionCode) otherRestrictions otherConstraints: This data set was compiled dynamically. It will be removed 10 days after 2025-03-21 from the NOAA system. Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of the Office for Coastal Management or its partners. resourceConstraints: (MD_SecurityConstraints) classification: (MD_ClassificationCode) unclassified classificationSystem: (missing) handlingDescription: (missing) aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: NOAA Data Management Plan (DMP) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 49785 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49785.pdf protocol: WWW:LINK-1.0-http--link name: NOAA Data Management Plan (DMP) description: NOAA Data Management Plan for this record on InPort. function: (CI_OnLineFunctionCode) information role: (inapplicable) associationType: (DS_AssociationTypeCode) crossReference spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vector language: eng; US topicCategory: (MD_TopicCategoryCode) elevation environmentDescription: Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 9.3.0.1770 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -76.713701 eastBoundLongitude: -76.526548 southBoundLatitude: 39.195787 northBoundLatitude: 39.372703 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2008-04-15 supplementalInformation: A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1199/supplemental/2008_City_of_Baltimore_Lidar.kmz A detailed description of this dataset can be found in the Final Project Report, found here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1199/supplemental/2008_City_of_Baltimore_Lidar_QA_Report.pdf return to top distributionInfo: (MD_Distribution) distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) distributor transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=1199 protocol: WWW:LINK-1.0-http--link name: Customized Download description: Create custom data files by choosing data area, product type, map projection, file format, datum, etc. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1199/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Simple download of data files. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: The project specifications called for the LiDAR survey to comply with industry standard FEMA guidelines for horizontal accuracy. ; Quantitative Value: 1.0 meters, Test that produced the value: Assumed to meet FEMA specifications for horizontal accuracy. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy 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. ; Quantitative Value: 0.058 meters, Test that produced the value: The LiDAR derived elevations for this project compared against 50 ground control check points showed the RMSE error observed was 0.058 meters. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: None provided result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: 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: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_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 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) 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). OCM 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. dateTime: DateTime: 2012-07-01T00:00:00 processStep: (LI_ProcessStep) description: The dataset has been mosaiced, reprojected, and clipped as needed from the original input files using PDAL and GDAL commands. dateTime: DateTime: 2025-03-21 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |