| 2001 USACE LRE Topobathy Lidar: Lake Ontario (NY) | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49880 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: EPSG code 4152 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: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters alternateTitle: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters citedResponsibleParty: (CI_ResponsibleParty) organisationName: (withheld) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/VerticalCoordRefSystem/5703/?api_key=gml name: North American Vertical Datum of 1988 (NAVD88) (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::5703 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2001 USACE LRE Topobathy Lidar: Lake Ontario (NY) alternateTitle: ny2001_usace_loslrs_ontario_m4700_metadata date: (CI_Date) date: 2003-04-30 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49880 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49880 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/dataviewer 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 protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) abstract: NOAA Office for Coastal Management received the 2001 Lake Ontario dataset with 2 separate metadata records in 2013 on a hard-drive device from the USGS Center for LiDAR Information Coordination and Knowledge (CLICK); the first record was for the topographic portion of the shoreline from the USACE Detroit Office collected in May of 2001 and a second stating the USACE JALBTCX SHOALS system as having collected the bathymetric points for these same areas in August of 2001. The collection dates and GPS times correspond to each having successfully collected and delivered their respective areas. This record is a combination of the two and will highlight sections from both in order to create a complete and complementary metadata record. The original metadata records will be available by request only. This data set is the raw topographic LIDAR data set. The data set contains selected base categories of geographic features, and characteristics of these features (X,Y,Z), in digital form. The X,Y represent geographic coordinates and the Z represents elevation in meters. The information was collected by EarthData International, LLC for the U.S. Army Corps of Engineers, Detroit District. This collection was done on the behalf of the Lake Ontario St. Lawrence River Study by the International Joint Commission. These data were collected by the SHOALS (Scanning Hydrographic Operational Airborne Lidar Survey) system which consists of an airborne laser transmitter/receiver capable of measuring 400 soundings per second. The system operates from a deHavilland DHC-6 Twin Otter flying at altitudes between 200 and 400 meters with a ground speed of about 100 knots. The SHOALS system also includes a ground-based data processing system for calculating accurate horizontal position and water depth. Lidar is an acronym for LIght Detection And Ranging. The system operates by emitting a pulse of light that travels from an airborne platform to the water surface where a small portion of the laser energy is backscattered to the airborne receiver. The remaining energy at the water's surface propagates through the water column and reflects off the sea bottom and back to the airborne detector. The time difference between the surface return and the bottom return corresponds to water depth. The maximum depth the system is able to sense is related to the complex interaction of radiance of bottom material, incident sun angle and intensity, and the type and quantity of organics or sediments in the water column. As a rule-of-thumb, the SHOALS system should be capable of sensing bottom to depths equal to two or three times the Secchi depth. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The purpose for the topographic collection of raw Topographic LIDAR, was to support coastal and water modeling of the Lake Ontario South Shore shoreline. This was conducted as part of a study by the Lake Ontario - St. Lawrence River Study by the International Joint Commission. The purpose of the bathymetric survey was to collect data from the shoreline to approximately -10m depths. The data will be used to build models of the Lake Ontario shoreline. 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 graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4700/supplemental/ny2001_usace_loslrs_ontario_m4700.kmz fileDescription: This graphic shows the lidar coverage for the 2001 lidar project covering Lake Ontario, with bathymetric and topographic lidar in portions of New York. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: Ground keyword: Terrain type: (MD_KeywordTypeCode) theme 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]: 2001 USACE LRE Topobathy Lidar: Lake Ontario (NY) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49880. 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: These data depict the heights at the time of the survey and are only accurate for that time. Acknowledgment of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any publications or derived products. The data herein, including but not limited to geographic data, tabular data, analytical data, electronic data structures or files, are provided "as is" without warranty of any kind, either expressed or implied, or statutory, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the data is assumed by the user. No guarantee of accuracy is granted, nor is any responsibility for reliance thereon assumed. In no event shall the U.S. Army Corps of Engineers, Mobile District Office, Spatial Data Branch be liable for direct, indirect, incidental, consequential or special damages of any kind, including, but not limited to, loss of anticipated profits or benefits arising out of use of or reliance on the data. The Spatial Data Branch does not accept liability for any damages or misrepresentation caused by inaccuracies in the data or as a result of changes to the data caused by system transfers or other transformations or conversions, nor is there responsibility assumed to maintain the data in any manner or form. | Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of LOSLR, GLC, USACE, JALBTCX, NOAA, 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: 49880 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49880.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 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -78.289001 eastBoundLongitude: -76.159606 southBoundLatitude: 43.227111 northBoundLatitude: 43.814086 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Publication Date beginPosition: 2001-05-09 endPosition: 2001-08-01 supplementalInformation: A footprint of the entire dataset is available here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4700/supplemental/ny2001_usace_loslrs_ontario_m4700.kmz A footprint of the bathymetric data is available here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4700/supplemental/ny2001_usace_loslrs_ontario_m4700_bathy.kmz A report concerning the control points is available here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4700/supplemental/ny2001_usace_loslrs_ontario_m4700_surveyreport.pdf return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: none date: (unavailable) 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=4700 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/4700/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_QuantitativeAttributeAccuracy) nameOfMeasure: Accuracy evaluationMethodDescription: The raw digital elevation model (DEM) was generated for the project area from the raw data. This raw DEM includes elevations for vegetation and buildings. The raw DEM was further processed to an even 4-m interval in both the latitude and longitude direction by "gridding" the data. The raw DEM was derived with an accuracy to support the generation of 0.6-m (2') contours at National Map Accuracy Standards (NMAS). SHOALS has demonstrated capabilities that meet US Army Corps of Engineers Hydrographic Survey accuracy requirements for Class 1 surveys and the International Hydrographic Organization nautical charting standards for Order 1. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: One simultaneous adjustment was performed on the entire data set to ensure that all coordinates and adjustments were unique to one network.; Quantitative Value: 3 meters, Test that produced the value: +/- 3 meters (1 sigma) result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: GPS and IMU data collection for the first mission began at 19:50 May 09, 2001 GMT and ended at 00:45 on May 10, 2001, GMT. The LIDAR data collection began at 20:45 GMT (334000 week second) and continued until 00:05 GMT (345900 week second). During that time there were no significant cycle slips in the data collected at the Genessee airport nor in the data collected onboard the aircraft. There were 2 data gaps in the data collected by Costage Engineering. However this did not significantly impact the differential solution. The aircraft did not travel more than 50 statute miles from either base station. During the LIDAR data collection the PDOP was less than 2.5 and the DDOP was less than 4. The phase differential solution from the data collected at the Genessee airport is a fixed integer solution. Ionospheric error modeling was selected in the post processing software for this data set. The "forward" and "reverse" solutions were compared to each other and are nearly identical. These 2 trajectory files were averaged together to yield the final solution (solution A). The phase differential solution from the data collected by Costage Engineering, located at the project site, is a "float" solution. This is due to the large distance from the Genessee airport to the project area at the time of GPS initialization. Ionospheric error modeling was selected in the post processing software for this data set. The forward and reverse solutions were compared to each other. The differences in the 2 solutions were well within acceptable tolerances. These two were averaged together to yield a single trajectory file (solution B). To determine the overall quality and accuracy of the GPS data collection and subsequent processing solutions A and B were compared to each other. The differences between these 2 trajectory files were well within acceptable tolerances. The small difference between these 2 solutions indicates that the GPS positioning of the aircraft is valid and exceeds the precision required for this project. The IMU data collection for the entire flight was continuous. The static initialization of the IMU was not less than 10 minutes. This is more than 3 times the minimum amount of time recommended by Applanix Corporation. The post processing of the IMU data indicates that the resulting Smoothed Best Estimate Trajectory (SBET) was free of anomalies and yielded the best position and orientation that the system can provide. Solution A was used with the IMU data for all subsequent LIDAR data processing for Area 1.; Quantitative Value: 0.15 meters, Test that produced the value: +/- 15 cm (1 sigma) result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: The raw LIDAR dataset required a substantial amount of editing since the project area was flown so late in the spring. Much of the vegetation had "leafed-out", so there were a number of areas where it was difficult to distinguish the low-lying vegetation from the surface of the ground. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Point topological relationships are collected or generated to satisfy topological requirements. Some of the requirements include populated X coordinate, Y coordinate, and Z coordinate values all with in NMAS. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: The aircraft was based at Genessee County airport located in Batavia, New York. During the first airborne mission on May 09 Area #1 was completeley collected. For the duration of the data collection there were 2 stationary GPS receivers in constant operation. One receiver was located at the Genessee county airport. The second GPS receiver was operated by Costage Engineering located in Rochester, New York. Both instruments collected GPS phase data at 1 Hz. for the duration of the mission. dateTime: DateTime: 2001-05-09T00:00:00 processStep: (LI_ProcessStep) description: A second flight was executed on May 10, 2001. During this airborne mission Area #2 and Area #3 were completely collected. During the data collection there were 3 stationary GPS receivers in constant operation. One receiver was located at the Oswego County Airport, NY. A second receiver was located at the Williamson-Sodus Airport. The third receiver was located at the Genessee County airport. All 3 instruments collected GPS phase data at 1 Hz. for the duration of the mission. dateTime: DateTime: 2001-05-10T00:00:00 processStep: (LI_ProcessStep) description: LIDAR data was collected at a flying height of 8,000't AMT (above mean terrain), at an average post-spacing of 4 m, at a laser pulse rate of 15 kHz, and with a field-of-view (FOV) of 40 degrees. The average swath width of the LIDAR flight lines was 5800'. Survey data also was collected over the project area to check the vertical accuracy of the LIDAR dataset. dateTime: DateTime: 2001-05-09T00:00:00 processStep: (LI_ProcessStep) description: The SHOALS airborne system acquires a tremendous volume of raw data during a single mission. The lidar data are unique and require a specialized Data Processing System (DPS) for post-processing. The DPS main funcions 1) import airborne data stored on high density data tape; 2) perform quality control checks on initial depths and horizontal positions; 3) provide display and edit capabilities; 4) calculate depth and position (XYZ) values for each sounding; and 5) output final positions and depths for each sounding. dateTime: DateTime: 2001-08-01T00:00:00 processStep: (LI_ProcessStep) description: Original reach-specific topographic LIDAR data were merged, checked for consistency, and packaged/compressed using the gzip compression utility. dateTime: DateTime: 2006-07-07T00:00:00 processStep: (LI_ProcessStep) description: Original reach-specific bathymetric LIDAR data were merged, checked for consistency, and packaged/compressed using the gzip compression utility. dateTime: DateTime: 2006-07-10T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received ASCII text files without classifications or complete attributes for each point. The data were received in UTM Zone 18 (meters) and referenced vertically to NAVD88 (meters) using the Geoid99 model in meters. Three separate areas arrived in OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. ASCII files were converted from to LAS files with LASTools (txt2las). 2. LAS files were removed of any duplicated points and extraneous points were reclassified to noise. 3. The LAS tiles were then processed to reclassify unclassified topographic points to ground using an existing shoreline footprint from NOAA. 4. The LAS tiles were then processed to reclassify unclassified to bathymetric points for all submerged, open water area points. Processing errors were caused by data uncertainties beyond the reasonable extent of bathymetric depths (for 2001) therefore these points were not reclassified to bathymetric points, class 11. 5. The LAS files were transformed to geographic (decimal degrees), ellipsoidal coordinates (meters) referenced to the Geoid12a model. dateTime: DateTime: 2015-07-01T00:00:00 processStep: (LI_ProcessStep) description: The vertical values in this data set have been converted to reference North American Vertical Datum of 1988 (NAVD88) (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-07-01T06:48:57 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |