| 2009 NYS DEC Lidar: West of Hudson, NY | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:63037 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation 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: Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2020-10-08T18:22:48 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) topologyLevel: (MD_TopologyLevelCode) geometricObjects: (MD_GeometricObjects) geometricObjectType: (MD_GeometricObjectTypeCode) point geometricObjectCount: 20032884536 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(NSRS2007) 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/4759/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:4759 version: 6.18.3 (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: 2009 NYS DEC Lidar: West of Hudson, NY date: (CI_Date) date: 2009-09-01 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 63037 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: NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) description: The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: Lidar based surface elevation data collection project in WOH (NYSDEP), collected in 2009. Products generated include LiDAR point data in LAS Binary format v1.1. The final LiDAR LAS 1.1 was created in UTM Zone 18 North, referenced to NAD83 and NAVD 88, in meters. The final LiDAR DEM was verified against FEMA checkpoints in order to perform a redundency check against the GPS solutions. These accuracy checks also verified that the data meets the guidelines outlined in FEMA's Guidelines and Specifications for Flood Hazard Mapping Partners and Appendix 4B, Airborne Light Detection and Ranging Systems. The areas of interest were flown at an altitude of 1200 meters (3937 feet) above mean terrain. Airspeed - 120 knots, Laser Pulse Rate - 50,000 Hz, Full Field of View - 60 degrees, Scane Rate - 32 Hz, Swath Width - 1300 meters. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: Support of FEMA's Floodplain Map Modernization Program. Multiple other uses expected. credit: New York State Department of Environmental Preservation, Division of Water, Watershed GIT Support Group The custom download may be cited as National Oceanic and Atmospheric Administration (NOAA) Digital Coast Data Access Viewer. Charleston, SC: NOAA Office for Coastal Management. Accessed Oct 20, 2020 at https://coast.noaa.gov/dataviewer. 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: 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: 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://coast.noaa.gov/htdata/lidar4_z/geoid18/data/9180/supplemental/extent_NYC_west_hudson_m9180.kmz fileDescription: This graphic displays the footprint for this lidar data set. fileType: KML descriptiveKeywords: (MD_Keywords) keyword: EARTH SCIENCE > Land Surface > Topography > Terrain Elevation type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: GCMD Science Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: LiDAR keyword: LiDAR Point Cloud type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: EDI Thesaurus date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Earth Science > Land Surface > Topography > Terrain Elevation keyword: Earth Science > Oceans > Bathymetry/Seafloor Topography > Bathymetry > Coastal Bathymetry keyword: Earth Science > Oceans > Coastal Processes > Coastal Elevation type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Continent > North America > United States Of America keyword: Vertical Location > Land Surface keyword: Vertical Location > Seafloor type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: New York keyword: WOH type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Geographic Names Information System date: (missing) descriptiveKeywords: (MD_Keywords) keyword: U.S. Coastline type: (MD_KeywordTypeCode) place descriptiveKeywords: (MD_Keywords) keyword: Earth Remote Sensing Instruments > Active Remote Sensing > Profilers/Sounders > Lidar/Laser Sounders > LIDAR > Light Detection and Ranging type: (MD_KeywordTypeCode) instrument thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Instrument Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Aircraft > Aircraft type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) 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. | Distribution Liability: New York State Department of Environmental Preservation (NYS DEC) provides these geographic data "as is." NYS DEC makes no guarantee or warranty concerning the accuracy of information contained in the geographic data. NYS DEC further makes no warranty, either expressed or implied, regarding the condition of the product or its fitness for any particular purpose. The burden for determining fitness for use lies entirely with the user. Although these data have been processed successfully on a computer system at NYSDEP, no warranty expressed or implied is made regarding the accuracy or utility of the data on any other system or for general or scientific purposes. This disclaimer applies both to individual use of the data and aggregate use with other data. It is strongly recommended that careful attention be paid to the contents of the metadata file associated with these data. NYS DEC shall not be held liable for improper or incorrect use of the data described and/or contained herein. Any conclusions drawn from the analysis of this information are not the responsibility of 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: 63037 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/63037.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 3; ESRI ArcCatalog 9.2.6.1500 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -75.407586 eastBoundLongitude: -74.038881 southBoundLatitude: 41.768409 northBoundLatitude: 42.4816 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2009-03-31 endPosition: 2009-06-24 supplementalInformation: In the spring of 2009, The Sanborn Map Company, Inc. (Sanborn) acquired 1996.18 square miles of terrestrial LiDAR data in WOH (NYSDEP) 2009. Two Leica Airborne LiDAR sensors was used for the collection. The LiDAR data associated with this metadata file is in LAS binary format, version 1.1 (ASPRS specification, see Cross References). return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: The LAS file is version 1.1 (see ASPRS LAS 1.1 cross reference) and includes the following information at the file level: GUID (project identifier), file creation day and year, Variable Length Records (VLR) which include file projection information. The LAS 1.1 file contains the following information at the point level: Grid coordinate (x,y,z), 8-bit intensity value, return number, scan direction, classification value, Point Source ID (flight-line delineator), GPS Time (GPS seconds of the we date: (unavailable) return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Zip version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: LAZ version: (missing) 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: 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=9180/details/9180 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. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar4_z/geoid18/data/9180 protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum. 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 LiDAR data horizontal accuracy is in compliance with the National Standard for Spatial Data Accuracy (NSSDA) RMSE estimation of elevation data in support of 2ft. contour mapping products as it is referenced in the FEMA guidelines for flood hazard mapping, appendix A (see Cross References). Quantitative value: 1.000 m RMSE, Test that produced the valued: Horizontal error associated with this LiDAR data set is a function of several factors including acquisition practices, height of the sensor above terrain, point spacing, diameter of the pulse footprint, network control station coordinates, kinematic GPS solutions, IMU calibration and post-processing functions. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The LiDAR data vertical accuracy is in compliance with the National Standard for Spatial Data Accuracy (NSSDA) RMSE estimation of elevation data in support of 2ft. contour mapping products as it is referenced in the FEMA guidelines for flood hazard mapping, appendix A (see Cross References). The Sanborn Map Company has performed a data accuracy validation and found this data to be in compliance. Additionaly, The New York State Department of Environmental Preservation performed a ground control analysis of the NY LiDAR data using ground control checkpoints in several land cover classes and found the resultant RMSE in the exposed ground class to be within the contract specifications of 0.185 meters.Quantitative value: 0.185 m RMSE, Test that produced the value: Vertical error associated with this LiDAR data is a function of several factors including acquisition practices, height of the sensor above terrain, point spacing, diameter of the pulse footprint, network control station coordinates, kinematic GPS solutions, IMU calibration and post-processing functions. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: The 2009 NY LiDAR data associated with this metadata file completely covers the project-specified boundary with no data voids caused by acquisition or sensor issues. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: The 2009 NY LiDAR data associated with this metadata file has met all quality checks in terms of relative accuracy, absolute accuracy, coverage. and point and file format. The relative accuracy of the LiDAR data refers to how well the data set matches within itself. That is to say, adjacent LiDAR scans are in alignment with each other with no vertical or horizontal shifts caused by improper calibration and/or georeferencing. The absolute elevation has been validated by both Sanborn and NYS DEC. This was done by comparing the LiDAR ground surface against known ground control points. The data file format and point attribution is in compliance with the LAS version 1.1 specifications (see ASPRS LAS1.1 cross reference). result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Data collection: Using Sanborn's Leica ALTM_SN40 and ALTM_SN49 Light Detection And Ranging (LiDAR) system, 428 flight lines of standard density (1.0 meter ground sample distance) data were collected over areas in WOH (NYSDEP) 2009 (approximately 1996.18 square miles). Two returns were recorded for each laser pulse along with an intensity value for each return. The data acquisition occurred in 45 missions between April 16, 2009 , and June 25, 2009. During the LiDAR campaign, the Sanborn field crew conducted a GPS field survey to establish final coordinates of the ground control stations for final processing of the base-remote GPS solutions. dateTime: DateTime: 2009-01-01T00:00:00 processStep: (LI_ProcessStep) description: Airborne GPS processing: 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 georeferenced point. Airborne GPS is differentially processed using the GrafNAV v7.50 software by Waypoint Consulting of Calgary, Alberta, Canada. dateTime: DateTime: 2009-01-01T00:00:00 processStep: (LI_ProcessStep) description: IMU data processing: 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. IMU data is processed using the POSPac v4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada. dateTime: DateTime: 2009-01-01T00:00:00 processStep: (LI_ProcessStep) description: LiDAR point classification The classification and quality control (QC) of LiDAR data is carried out using TerraScan software v. 8.003 by Terrasolid Limited of Helinski, Finland. The bare earth extraction from the point cloud is the result of a morphological processing routine run in TerraScan. A set of user-defined distances and angles are used by the software to build a ground surface from established 'aerial low seed points'. The reclassifying of the data in areas of overlapping scans is done before the classification of the LAS ground points (DEM). This means the point cloud from which the ground points are extracted is more uniform in terms of point density. The 'cut-overlap' process is performed with the aid of the aircraft trajectory (reduced to the sensor's trajectory) and the scan angle value within the LAS data. For this project, the value used for cutting the overlap was 25 degrees. This means that data from a single scan greater than 12.5 degrees off nadir was classified to class 12 overlap. Using the trajectory and embedded angle information, the software (TerraScan) is able to properly reclassify the overlap points so that the remaining point cloud is edge-matched. That is to say, there are no data voids within the point cloud with class 12 overlap points turned off. dateTime: DateTime: 2009-01-01T00:00:00 processStep: (LI_ProcessStep) description: Output LAS files The tiling and final LAS file creation was performed using LiDAR CuePac v5.0 from GeoCue Corporation of Madison, Alabama, USA. By client specification, the LiDAR point cloud data were cut to square, 750 x 750 meter (~56 Ha, 140 acres) tiles. The naming convention used for the tiles is based on the truncated grid coordinate at the southwest corner point of origin of the tile. dateTime: DateTime: 2009-01-01T00:00:00 processStep: (LI_ProcessStep) description: Summary and algorithms for filtering data: The classification algorithms used on the LiDAR point cloud involved several iterative steps including the removal of low points and other outlyers, the culling of overlap data, and finally the classification of the LiDAR DEM. This process begins with automated routines and ends with a 100% manual edit and QC check of the data. Once the data set classification accuracy was deemed sufficient and no quality issues were found, a final vertical accuracy assessment was performed on the LiDAR DEM. dateTime: DateTime: 2009-01-01T00:00:00 processStep: (LI_ProcessStep) description: Data Validation - The final LiDAR LAS 1.1 was created in UTM Zone 18 North, referenced to NAD83 and NAVD 88, in meters. The final LiDAR DEM was verified against FEMA checkpoints in order to perform a redundency check against the GPS solutions. These accuracy checks also verified that the data meets the guidelines outlined in FEMA's Guidelines and Specifications for Flood Hazard Mapping Partners and Appendix 4B, Airborne Light Detection and Ranging Systems. dateTime: DateTime: 2009-01-01T00:00:00 processStep: (LI_ProcessStep) description: NOAA OCM received the lidar data in 8,909 LAS format binary files. No project report was delivered with the data. The data were in UTM Zone 18N NAD83 meters coordinates and NAVD88 (Geoid03) elevations in meters. 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. It was determined that, in addition to the lidar point classifications specified in the metadata of 1 - Unclassified, 2 - Bare Earth, 7 - Low Points (noise), and 12 - Overlap, classes 3 - Low Vegetaion, 4 - Medium Vegetation, 5 - High Vegetation and 6 - Building were also present. 2. Internal OCM scripts were run on the las files to convert to laz format, to convert from orthometric (NAVD88) elevations to NAD83 (2011) ellipsoid elevations using the Geoid 03 model, to convert from UTM Zone 18 North NAD83 (2007) coordinates in meters to geographic coordinates, to assign the geokeys, to sort the data by gps time and zip the data to database and to http. All point classifications were processed through. dateTime: DateTime: 2020-10-04T00:00:00 processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) description: Source Contribution: The following values are nominal and were taken directly from the LiDAR flight planning software for the Optech system - ALTM-NAV Planner v.2.0.52. Several variables could have affected these figures including wind speed, air turbulence, pilot error and subtle changes in terrain. One issue encountered during the NY LiDAR campaign was a shift in wind direction causing alternating head and tail winds. The pilot did what was possible to keep the ground speed of the aircraft close to 120 knots however could not cancel out this problem entirely. The resulting effect on the point cloud is a change in the point spacing; increasing with the tailwind and decreasing with the headwind. The average point density for the entire NY LiDAR data set should be somewhat consistent regardless of the wind issue. The areas of interest were flown at an altitude of 1200 meters (3937 feet) above mean terrain. Airspeed - 120 knots, Laser Pulse Rate - 50,000 Hz, Full Field of View - 60 degrees, Scane Rate - 32 Hz, Swath Width - 1300 meters. sourceCitation: (CI_Citation) title: LiDAR Acquisition Parameters date: (CI_Date) date: 2009-06-24 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Sanborn role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2009-06-24 source: (LI_Source) description: Source Contribution: Ground Control: X,Y,Z 598538.296 4591353.934 322.866 590384.087 4578455.087 168.941 590540.135 4587940.729 135.632 590630.285 4583427.292 168.539 589826.617 4578257.171 123.774 590422.522 4589177.338 121.721 602810.281 4592789.119 215.014 607108.305 4588314.292 155.988 597850.386 4590811.304 309.875 598763.945 4578194.974 191.793 601367.188 4584840.656 107.463 602773.781 4592801.105 217.981 594284.184 4572059.404 104.295 606338.273 4574885.380 135.672 599577.466 4576356.278 133.079 588936.680 4572298.184 2.389 607308.851 4583738.702 181.576 607066.856 4588325.969 155.748 598515.616 4591382.960 323.784 595300.243 4588736.091 323.564 603240.986 4587215.339 142.469 606402.898 4581152.286 198.288 sourceCitation: (CI_Citation) title: Report of Survey - Ground Control date: (CI_Date) date: 2009-06-09 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Sanborn role: (CI_RoleCode) originator 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: 2020-10-20T05:17:48 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |