|
|
2007 USGS Topographic LiDAR: Valdez, AlaskaspatialRepresentationInforeferenceSystemInfo referenceSystemInfo identificationInfo distributionInfo dataQualityInfo metadataMaintenance |
| (MI_Metadata) fileIdentifier: gov.noaa.csc.maps:ak2007_aerometric_valdez_m1466 language: eng; USA characterSet: (MD_CharacterSetCode) utf8 hierarchyLevel: (MD_ScopeCode) dataset contact: (CI_ResponsibleParty) individualName: Mike Sutherland organisationName: DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce contactInfo: (CI_Contact) phone: (CI_Telephone) voice: 303-497-6120 facsimile: 303-497-6513 address: (CI_Address) deliveryPoint: NOAA/NESDIS/NGDC E/GC1 325 Broadway city: Boulder administrativeArea: CO postalCode: 80305-3328 country: USA electronicMailAddress: mike.sutherland@noaa.gov hoursOfService: 7:30am-5:00pm Mountain role: (CI_RoleCode) author dateStamp: 2013-04-25 metadataStandardName: ISO 19115-2 Geographic Information - Metadata - Part 2: Extensions for Imagery and Gridded Data metadataStandardVersion: ISO 19115-2:2009(E) return to top spatialRepresentationInfo: (MD_VectorSpatialRepresentation) geometricObjects: (MD_GeometricObjects) geometricObjectType: (MD_GeometricObjectTypeCode) point return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: North American Datum 1983 alternateTitle: NAD83 date: (CI_Date) date: 2007-01-19 dateType: (CI_DateTypeCode) revision citedResponsibleParty: (CI_ResponsibleParty) organisationName: contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4269 name: NAD83 description: Link to Geographic Markup Language (GML) description of reference system. function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) resourceProvider citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: http://www.epsg-registry.org/ name: European Petroleum Survey Group Geodetic Parameter Registry description: Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. function: (CI_OnLineFunctionCode) search role: (CI_RoleCode) publisher code: urn:ogc:def:crs:EPSG::4269 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) code: Ellipsoid in Meters codeSpace: Local Vertical Reference return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2007 USGS Topographic LiDAR: Valdez, Alaska date: (CI_Date) date: 2013-02-01 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce contactInfo: (CI_Contact) phone: (CI_Telephone) voice: 843-740-1200 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave. city: Charleston administrativeArea: SC postalCode: 29405-2413 electronicMailAddress: csc.info@noaa.gov role: (CI_RoleCode) originator citedResponsibleParty: (CI_ResponsibleParty) organisationName: DOI/USGS > United States Geological Survey, U.S. Department of the Interior role: (CI_RoleCode) originator citedResponsibleParty: (CI_ResponsibleParty) organisationName: DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce contactInfo: (CI_Contact) phone: (CI_Telephone) voice: 843-740-1200 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave. city: Charleston administrativeArea: SC postalCode: 29405-2413 electronicMailAddress: csc.info@noaa.gov role: (CI_RoleCode) publisher presentationForm: (CI_PresentationFormCode) imageDigital abstract: This project was completed by Aerometric, Inc. under USGS Contract No. 07CRCN0002, Task Order No. 070020009. This delivery contains point cloud data in LAS 1.1 format, classified in the following manner. Class 1: Unclassified, Class 2: Ground, Class 7: Low Point (Noise), Class 9: Water, Class 10: High Point (Noise), Class 12: Overlap, and Class 17: Port The following are the collection parameters and equipment used to create these data sets. Aircraft: Cessna 320 (N3443Q) and Piper Navajo (N6GR) Lidar System: Optech ALTM Gemini (03SEN145) Approximate Collection Altitude (Above Mean Terrain): 1800 meters Ground Speed: 145 kts Pulse Rate Frequency: 70 kHz Mirror Scan Frequency: 62.6 Hz Scan Angle (+/-): 5.3 degrees Beam Divergence: Narrow (0.25 mrad) Accuracy statements are based on areas of moderate terrain, with points classified as ground. Diminished accuracies are to be expected in areas of extreme terrain and dense vegetation. The accuracy of each point is expected to meet the vertical accuracy standard. Derived products may be less accurate in areas of extreme terrain and dense vegetation due to a lesser number of points defining the ground in these areas. Classified data sets such as this one may have varying posting due to some pulses not reaching the ground. purpose: The purpose of this data set is to provide processed lidar data over Valdez at a nominal point spacing of 0.3 meter. status: (MD_ProgressCode) completed pointOfContact: (CI_ResponsibleParty) individualName: Jacques Cloutier organisationName: Aero-Metric, Inc. positionName: Senior Geodetic Surveyor contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (907) 272-4495 facsimile: (907) 274-3265 address: (CI_Address) deliveryPoint: 2014 Merrill Field Drive city: Anchorage administrativeArea: Alaska postalCode: 99501-4116 country: USA electronicMailAddress: aerometric@aerometric-ak.com hoursOfService: 8:00 am to 5:00 pm Alaska Standard Time role: (CI_RoleCode) pointOfContact resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) asNeeded graphicOverview: (MD_BrowseGraphic) fileName: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/ak/ak2007_aerometric_valdez_footprint.KMZ fileDescription: This kmz file shows the extent of coverage for the 2007 USGS Valdez, Alaska lidar data set. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: Topography/Bathymetry keyword: Elevation keyword: Topography keyword: Remote Sensing keyword: lidar keyword: Laser keyword: Terrain type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: None date: descriptiveKeywords: (MD_Keywords) keyword: USA keyword: Alaska keyword: Valdez type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: None date: resourceConstraints: (MD_Constraints) useLimitation: These data depict the elevations at the time of the survey and are only accurate for that time. Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. Any conclusions drawn from analysis of this information are not the responsibility of NOAA or any of its partners. These data are NOT to be used for navigational purposes. resourceConstraints: (MD_LegalConstraints) useLimitation: While every effort has been made to ensure that these data are accurate and reliable within the limits of the current state of the art, NOAA cannot assume liability for any damages caused by any errors or omissions in the data, nor as a result of the failure of the data to function on a particular system. NOAA makes no warranty, expressed or implied, nor does the fact of distribution constitute such a warranty. spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vector language: eng; USA topicCategory: (MD_TopicCategoryCode) elevation extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -146.641106 eastBoundLongitude: -145.913257 southBoundLatitude: 61.036345 northBoundLatitude: 61.158460 temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2007-10-16 temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2008-10-20 temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2008-10-25 temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2008-10-31 return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: LAZ version: distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce contactInfo: (CI_Contact) phone: (CI_Telephone) voice: 843-740-1200 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave. city: Charleston administrativeArea: SC postalCode: 29405-2413 electronicMailAddress: csc.info@noaa.gov role: (CI_RoleCode) distributor distributionOrderProcess: (MD_StandardOrderProcess) orderingInstructions: The National Geophysical Data Center serves as the archive for this LIDAR data. NGDC should only be contacted for this data if it cannot be obtained from NOAA Coastal Services Center. distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) individualName: Mike Sutherland organisationName: DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce contactInfo: (CI_Contact) phone: (CI_Telephone) voice: 303-497-6120 facsimile: 303-497-6513 address: (CI_Address) deliveryPoint: NOAA/NESDIS/NGDC E/GC1 325 Broadway city: Boulder administrativeArea: CO postalCode: 80305-3328 country: USA electronicMailAddress: mike.sutherland@noaa.gov hoursOfService: 7:30am-5:00pm Mountain role: (CI_RoleCode) distributor distributionOrderProcess: (MD_StandardOrderProcess) orderingInstructions: The National Geophysical Data Center serves as the archive for this LIDAR dataset. NGDC should only be contacted for the data if it cannot be obtained from NOAA Coastal Services Center. return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy Report evaluationMethodDescription: All these data products were acquired at 1800 meters above mean terrain (AMT) and have a horizontal accuracy of 0.3 meter, with a nominal point spacing of 0.6 meters as per manufacturer's specifications, not field verified. result: report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy measureDescription: Compiled to meet value (meters) result: (DQ_QuantitativeResult) valueUnit: BaseUnit: identifier: meters unitsSystem: value: Record: 0.3 report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy Report evaluationMethodDescription: The final lidar data set was verified using 2554 GPS surveyed ground truth points. These points were collected by Aero-Metric along the roads throughout the developed areas of the project, using Real-Time Kinematic (RTK) GPS techniques. The ground truth points were compared against the lidar using TerraScan, which computes the difference between each ground truth point and the lidar generated surface. These differences are recorded in an output file in ASCII format. This file is imported into Microsoft Excel, where a statistical analysis is performed. The full lidar control check analysis is included in the deliverables for this project, named Valdez_Low_Altitude_QC_Results.pdf. We recommend additional ground truth surveys of the data set to verify the vertical accuracy has not changed due to natural causes, such as techtonic motion or freeze/thaw cycles, and non-natural causes such as road construction. Without ground truth survey checks this data is not recommended for design grade mapping or engineering. result: report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy measureDescription: Consolidated vertical accuracy at the 95th percentile on road surfaces in meters result: (DQ_QuantitativeResult) valueUnit: BaseUnit: identifier: meters unitsSystem: value: Record: 0.092 report: (DQ_CompletenessCommission) evaluationMethodDescription: Complete result: report: (DQ_ConceptualConsistency) measureDescription: Data has been verified using surveyed check points along road surfaces thoughout the project area. result: lineage: (LI_Lineage) processStep: (LE_ProcessStep) description: System Calibration: Aero-Metric collected data over a previously surveyed area in Palmer, Alaska. Data was collected at the same settings as this project, using two intersecting perpendicular lines. Two GPS ground stations were operating on site in order to minimize GPS error. The data was classified in each line separately for ground and other common features between lines, such as building roofs. This data was processed in TerraMatch 8.001 (TerraSolid, Ltd.), to compute corrections for roll, pitch, heading, and mirror scale. These corrections were applied to the initial processing settings (.res file). The data was reprocessed to verify the corrections were applied properly. The corrected data was then compared to ground surveyed measurements in order to check for any consistent vertical bias. The final step in calibration verified there was minimal vertical noise due to changes in intensity. This was done by comparing elevations of points on the airport runway, one point on a runway stripe and another adjacent point on the pavement. dateTime: DateTime: 2008-10-18T00:00:00 processStep: (LE_ProcessStep) description: Create a smoothed-best estimated trajectory (SBET) of the sensor at a rate of 200 Hz, by integrating the airborne GPS and IMU data. The basis of the GPS coordinates were computed using NGS OPUS, and were referenced to NAD83 (CORS96) with GEOID06 derived orthometric heights. The maximum baseline distance for this project was 30 km, the average base line length was 12 km. The mean GPS positional accuracy for this project was +/- 0.08 meters. dateTime: DateTime: 2008-11-02T00:00:00 processStep: (LE_ProcessStep) description: Integrate SBET and raw laser data to produce point cloud data in LAS 1.1 format for each flight line. dateTime: DateTime: 2008-11-02T00:00:00 processStep: (LE_ProcessStep) description: Compute the roll, pitch, heading, and mirror scale correction factors for each flight line, then apply corrections to the corresponding flight line. dateTime: DateTime: 2009-01-15T00:00:00 processStep: (LE_ProcessStep) description: Automated classification of the bare-earth data from the lidar point cloud using a series of algorithms customized for the types of terrain encountered in the project. dateTime: DateTime: 2009-01-16T00:00:00 processStep: (LE_ProcessStep) description: Manual classification of any data which appears to be bare-earth but was not properly classified using the automated methods. dateTime: DateTime: 2009-03-20T00:00:00 processStep: (LE_ProcessStep) description: The shorelines of the lakes and port areas were determined using manual techniques, starting with digitized shorelines from the orthophotography of the project area. The lidar points then underwent an intensive manual edit to determine with greater accuracy the points which represented the water surface. For the final data products the mean elevation of the water on each lake was used to determine its fixed elevation. The port areas fixed elevation was determined using the highest water point in the port data set. This value was found to be 4.72 meters. All points below 4.72 meters in the port area were fixed to this elevation, as per the contract. dateTime: DateTime: 2009-05-25T00:00:00 processStep: (LE_ProcessStep) description: Create point clouds in LAS 1.1 format for all returns. dateTime: DateTime: 2009-05-26T00:00:00 processStep: (LE_ProcessStep) description: Data verified using survey control points, located throughout the area. dateTime: DateTime: 2009-05-27T00:00:00 processStep: (LE_ProcessStep) description: The metadata was updated for Bounding coordinates, Spatial Reference info using FGDC template dateTime: DateTime: 2009-06-18T00:00:00 processStep: (LE_ProcessStep) description: The NOAA Coastal Services Center (CSC) received topographic files in LAS 1.1 format. The files contained lidar elevation and intensity measurements. The data were received in projected coordinates of NAD83 UTM6N, meters and were vertically referenced to NAVD88 orthometric elevations using GEOID06(Alaska). The vertical units of the data were meters. CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. LAS Classifications 11(first return only), 13(first of many returns), 14(second of many returns), 15(third of many returns), 16(last of many returns) were all placed into Class 1 (Unclassified) 2. The topographic las files were converted from Projected Coordinates (NAD83 UTM6N, meters) to Geographic Coordinates (NAD83, decimal degrees). 3. The topographic las files were vertically converted from orthometric elevations (NAVD88) to ellipsoidal elevations (NAD83) using GEOID06. 4. The data were converted to LAZ format. dateTime: DateTime: 2013-02-01T00:00:00 processor: (CI_ResponsibleParty) organisationName: DOC/NOAA/NOS/CSC > Coastal Services Center, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce contactInfo: (CI_Contact) phone: (CI_Telephone) voice: 843-740-1200 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave. city: Charleston administrativeArea: SC postalCode: 29405-2413 electronicMailAddress: csc.info@noaa.gov role: (CI_RoleCode) processor processStep: (LE_ProcessStep) description: The NOAA National Geophysical Data Center (NGDC) received lidar data files via ftp transfer from the NOAA Coastal Services Center. The data are currently being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/. The data can be used to re-populate the system. The data are archived in LAS or LAZ format. The LAS format is an industry standard for LiDAR data developed by the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless compressed version of LAS developed by Martin Isenburg (http://www.laszip.org/). The data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data are referenced vertically to the ellipsoid (either GRS80 or ITRF94), allowing for the ability to apply the most up to date geoid model when transforming to orthometric heights. dateTime: DateTime: 2013-04-25T00:00:00 processor: (CI_ResponsibleParty) individualName: Mike Sutherland organisationName: DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce contactInfo: (CI_Contact) phone: (CI_Telephone) voice: 303-497-6120 facsimile: 303-497-6513 address: (CI_Address) deliveryPoint: NOAA/NESDIS/NGDC E/GC1 325 Broadway city: Boulder administrativeArea: CO postalCode: 80305-3328 country: USA electronicMailAddress: mike.sutherland@noaa.gov hoursOfService: 7:30am-5:00pm Mountain role: (CI_RoleCode) processor return to top metadataMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) annually dateOfNextUpdate: 2014-04-25 maintenanceNote: This metadata was automatically generated from the FGDC Content Standards for Digital Geospatial Metadata standard (version FGDC-STD-001-1998) using the 2013-01-04 version of the FGDC RSE to ISO 19115-2 for LiDAR transform. maintenanceNote: Translated from FGDC 2013-04-25T14:11:16.794-06:00 |