2004 USACE Puerto Rico Lidar | spatialRepresentationInfo|
---|---|
(MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:50051 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: 2022-08-09T17:11:37 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(HARN) 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/4152/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:4152 version: 6.18.3 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: Puerto Rico Vertical Datum of 2002 (PRVD02) (GEOID18) meters alternateTitle: Puerto Rico Vertical Datum of 2002 (PRVD02) (GEOID18) meters citedResponsibleParty: (CI_ResponsibleParty) organisationName: (withheld) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/VerticalCoordRefSystem/6641/?api_key=gml name: Puerto Rico Vertical Datum of 2002 (PRVD02) (GEOID18) meters 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: https://www.epsg.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 VerticalCS: metaDataProperty: CommonMetaData: type: vertical informationSource: OGP revisionDate: 2006-11-28 isDeprecated: false identifier: urn:ogc:def:cs:EPSG::6499 name: Vertical CS. Axis: height (H). Orientation: up. UoM: meter. remarks: Used in vertical coordinate reference systems. axis: CoordinateSystemAxis: descriptionReference: urn:ogc:def:axis-name:EPSG::9904 identifier: urn:ogc:def:axis:EPSG::114 axisAbbrev: H axisDirection: up code: urn:ogc:def:crs:EPSG::6641 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2004 USACE Puerto Rico Lidar alternateTitle: usace2004_puertorico_m560_metadata date: (CI_Date) date: 2007 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 50051 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/50051 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: This record describes Light Detection and Ranging (Lidar) data acquired for the island of Puerto Rico. The data were acquired for USACE, St. Louis District by 3001, Inc., between January 10 and February 8, 2004. The mission was flown at a density sufficient to support a maximum final post spacing of 6 feet for unobscured areas. The Puerto Rico LiDAR Survey was collected under the guidance of a Professional Mapper/Surveyor. Original contact information: Contact Org: 3001, Inc. Title: LiDAR Department Phone: (985) 661- 3001 Email: lidar@3001inc.com This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The Puerto Rico LiDAR dataset will support the creation of Federal Emergency Management Agency (FEMA) Flood Insurance Rate Maps (FIRM) and an integrated ground and surface water model. 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) notPlanned 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: Cite As: OCM Partners, [Date of Access]: 2004 USACE Puerto Rico Lidar [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50051. 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 useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Access Constraints: None | 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. Acknowledgement of USACE, St. Louis District would be appreciated in products derived from these data. | 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: 50051 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50051.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 XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -67.271346 eastBoundLongitude: -65.204146 southBoundLatitude: 17.913132 northBoundLatitude: 18.515932 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2004-01-10 endPosition: 2004-02-08 supplementalInformation: The Puerto Rico data provided by the NOAA Office for Coastal Management via the Digital Coast Data Access Viewer has been reviewed by Center staff as well as other outside parties. The data, as processed and provided by the OCM, have some noted quality issues and some potential accuracy problems. The OCM has not done any further accuracy assessment, but we have received some feedback from other organizations about accuracy and datum issues. Please note that the geoid grids for Puerto Rico, themselves, have a varying level of accuracy. The data is being provided as a 'best available' data set, but should be used with a level of caution. The Lidar QA/QC Quantitative and Qualitative Assessment Report for this data set may be viewed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/560/supplemental/lidarqaqcreport_puertorico_final.pdf A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/560/supplemental/2004_USACE_Puerto_Rico_Lidar.kmz return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: https://www.fisheries.noaa.gov/inport/item/50249 (CI_Citation) title: LAS date: (CI_Date) date: 2022-03-16 dateType: (CI_DateTypeCode) publication 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=560 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/560/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: Vertical Positional Accuracy evaluationMethodDescription: The accuracy assessment was performed using a standard method to compute the root mean square error (RMSE) based on a comparison of ground control points (GCP) and filtered LiDAR data points. Filtered LiDAR data has had vegetation and cultural features removed and by analysis represents bare-earth elevations. Testing was performed prior to gridding of the filtered LiDAR data points and construction of the Intergraph .dtm file format. The RMSE figure was used to compute the vertical National Standard for Spatial Data Accuracy (NSSDA). Ground control was established by 3001, Inc. A spatial proximity analysis was used to select edited LiDAR data points contiguous to the relevant GCPs. A search radius decision rule is applied with consideration of terrain complexity, cumulative error and adequate sample size. Cumulative error results from the errors inherent in the various sources of horizontal measurement. These sources include the airborne GPS, GCPs and the uncertainty of the accuracy of the LiDAR data points. This accuracy is achieved prior to the sub-sampling that occurs through integration with the inertial measurement unit (IMU) positions that are recorded. It is unclear at this time whether the initial accuracy is maintained. The horizontal accuracy of the GCPs is estimated to be in the range of approximately 1 to 1.6 feet. Finally, sample size was considered. The specification for the National Standard for Spatial Data Accuracy is a minimum of 20 points to conduct a statistically significant accuracy evaluation (Minnesota Planning, 1999, Positional Accuracy Handbook, Minnesota Planning Land Management Information Center, St. Paul, Minnesota., p.3). Most statistical texts indicate that a minimum of 30 sample points provide a reasonable Approximation of a normal distribution. The intent of the NSSDA is to reflect the geographic area of interest and the distribution of error in the data set (Federal Geographic Data Committee, 1998, Geospatial National Standard for Spatial Data Accuracy, Federal Geographic Data Committee Secretariat, Reston, Virginia, p.3-4). Additional steps were taken to ensure the vertical accuracy of the LiDAR data including: Step 1: Precision Bore sighting (Check Edge-matching) Step 2: Compare the LiDAR data to the Field Survey (Field survey is to FEMA specifications and more stringent internal specifications) Step 3: Automated Filtering Step 4: Manual Editing (Quality Control) Step 5: 3-D digitizing and Photogrammetric Compilation of hydrographic breaklines. ; Quantitative Value: 11.90 meters, Test that produced the value: Based upon the result of vertical accuracy testing conducted by 3001, Inc., vertical accuracy at the 95% confidence level (Accuracyz) is computed by the formula RMSEz x 1.9600. The overall vertical accuracy of the Puerto Rico Lidar dataset is 11.90 cm, based upon an RMSEz of 6.07 cm. These values were derived from a comparison of Lidar data points that fell within a 1 m horizontal radius of 20 established ground control points. They represent the overall vertical accuracy in all surface types surveyed, which include ashphalt, dirt and mowed grass. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: At the end of each flight, the Lidar data was processed to check for complete coverage and to verify that there were no voids in data coverage. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Unknown result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: The ABGPS, inertial measurement unit (IMU), and raw scans are collected during the LiDAR aerial survey. The ABGPS monitors the xyz position of the sensor and the IMU monitors the orientation. During the aerial survey laser pulses reflected from features on the ground surface are detected by the receiver optics and collected by the data logger. GPS locations are based on data collection receivers on the aircraft and base stations on the ground. The ground base stations are placed no more than 35 km radius from the flight survey area. dateTime: DateTime: 2007-01-01T00:00:00 processStep: (LI_ProcessStep) description: The ABGPS, IMU, and raw scans are integrated using proprietary software developed by the Leica Geosystems and delivered with the Leica ALS50 System. The resultant file is in a LAS binary file format. The LAS file version 1.0 format can easily transferred from one file format to another. It is a binary file format that maintains information specific to the LiDAR data (return#, intensity value, xyz, etc.). The resultant points are produced in the State Plane Puerto Rico FIPS 5200 coordinate system, with units in feet and referenced to the NAD83 horizontal datum and NAVD88 vertical datum. dateTime: DateTime: 2007-01-01T00:00:00 processStep: (LI_ProcessStep) description: The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters is applied as appropriate for the production of bare-earth digital terrain models (DTMs). Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. dateTime: DateTime: 2007-01-01T00:00:00 processStep: (LI_ProcessStep) description: Filtered and edited data are subjected to rigorous QA/QC according to the 3001 Inc. Quality Control Plan and procedures. Very briefly, a series of quantitative and visual procedures are employed to validate the accuracy and consistency of the filtered and edited data. Ground control is established by 3001, Inc. and GPS-derived ground control points (GCPs) points in various areas of dominant and prescribed land cover. These points are coded according to landcover, surface material and ground control suitability. A suitable number of points are selected for calculation of a statistically significant accuracy assessment as per the requirements of the National Standard for Spatial Data Accuracy. A spatial proximity analysis is used to select edited LiDAR data points within a specified distance of the relevant GCPs. A search radius decision rule is applied with consideration of terrain complexity, cumulative error and adequate sample size. Accuracy validation and evaluation is accomplished using proprietary software to apply relevant statistical routines for calculation of Root Mean Square Error (RMSE) and the National Standard for Spatial Data Accuracy (NSSDA) according the Federal Geographic Data Committee (FGDC) specifications. dateTime: DateTime: 2007-01-01T00:00:00 processStep: (LI_ProcessStep) description: The LiDAR mass points were delivered in ASPRS LAS 1.0 format. The header file for each dataset is complete as defined by the LAS 1.0 specification. The LAS files do not include overlap. The delivered tiles are suitable for seamless topographic data mosaics that include no "no data" areas. The names of the tiles are left padded with zeros as required to achieve a five character length and all files utilize the LAS file extension. dateTime: DateTime: 2007-01-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received the files in las format. The files contained Lidar elevation and intensity measurements. The data were in projected in Puerto Rico State Plane Coordinates (FIPS 5200/NAD83), and referenced to the orthometric datum of NAVD88 utilizing Geoid 99. Both planar and vertical units were measured in feet. OCM performed the following processing to the data to make it available within the Digital Coast: 1. The data were converted from State Plane Coordinates (NAD83; ft) to UTM coordinates (Zone 20/NAD83; m). 2. The vertical units of the data were converted from NAVD88 (ft) to NAVD88 (m). 3. The data were re-tiled using MARS software. 4. The data were reclassified such that all classifications were set to Class 0. 5. The data were filtered to Bare Earth (Class 2) and Unclassified (Class 1) using an automated process in LASEdit. 6. The data were converted from UTM coordinates (Zone 20/NAD83) to geographic coordinates (NAD83) and ellipsoidal elevations (GRS80) using Geoid 99. 7. The LAS data were sorted by latitude and the headers were updated. dateTime: DateTime: 2010-12-07T00:00:00 source: (LI_Source) description: Source Contribution: The Puerto Rico LiDAR Survey was acquired for USACE, St. Louis District and processed by 3001, Inc. | Source Geospatial Form: vector digital data | Type of Source Media: online sourceCitation: (CI_Citation) title: Puerto Rico LiDAR Survey date: (CI_Date) date: 2007-01-01 dateType: (CI_DateTypeCode) publication sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2004-01-10 endPosition: 2004-02-08 processStep: (LI_ProcessStep) description: The vertical values in this data set have been converted to reference Puerto Rico Vertical Datum of 2002 (PRVD02) (GEOID18) meters, using the GEOID18 grids provided by the National Geodetic Survey. Any datum and projection transformations were then done with the Office for Coastal Management 'datum_shift' program. Compression to an LAZ file was done with the LAStools 'laszip' program and can be unzipped with the same free program (laszip.org) Processing notes: dateTime: DateTime: 2023-08-01T06:07:55 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor |