|
|
2008 - 2009 Oregon Department of Geology and Mineral Industries (DOGAMI) South Coast LiDAR ProjectspatialRepresentationInforeferenceSystemInfo referenceSystemInfo identificationInfo distributionInfo dataQualityInfo metadataMaintenance |
| (MI_Metadata) fileIdentifier: gov.noaa.csc.maps:2008_OR_DOGAMI_South_Coast_m519 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-06-05 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: 2008 - 2009 Oregon Department of Geology and Mineral Industries (DOGAMI) South Coast LiDAR Project date: (CI_Date) date: 2009-01-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: Oregon Department of Geology and Mineral Industries (DOGAMI) 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: The Oregon Department of Geology & Mineral Industries (DOGAMI) contracted with Watershed Sciences, Inc. to collect high resolution topographic LiDAR data for multiple areas within the State of Oregon. The areas for LiDAR collection have been designed as part of a collaborative effort of state, federal, and local agencies in order to meet a wide range of project goals. This LiDAR data set was collected between May 3, 2008 and April 25, 2009 and encompasses portions of the following counties in southwest Oregon: Coos, Curry, Lane, and Douglas. This data set consists of bare earth and unclassified points. There are approximately 8 points per square meter over terrestrial surfaces. In some areas of heavy vegetation or forest cover, there may be relatively few ground points in the LiDAR data. Elevation values for open water surfaces are not valid elevation values because few LiDAR points are returned from water surfaces. LiDAR intensity values were also collected. This LiDAR data set was collected on different dates and organized into 14 deliveries. To determine which delivery or deliveries are in your area of interest, view the delivery area coverage graphic at: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/or/2008-2009_south_coast/2008_2009_dogami_oregon_lidar_south_coast.jpg The specific date of collection and total area covered for each delivery are listed below. Delivery 1: Date of Collection: 20080503-20080626 Total Area = 74.68 sq miles Delivery 2: Date of Collection: 20080503-20080626 Total Area = 138.73 sq miles Delivery 3: Date of Collection: 20080503-20080626 Total Area = 112.17 sq miles Delivery 4: Date of Collection: 20080612-20080629 Total Area = 177.55 sq miles Delivery 5: Date of Collection: 20080612-20080629 Total Area = 177.80 sq miles Delivery 6: Date of Collection: 20080615-20080803 Total Area = 437.95 sq miles Delivery 7: Date of Collection: 20080615-20080803 Total Area = 209.81 sq miles Delivery 8a: Date of Collection: 20080615-20080803 Total Area = 146.30 sq miles Delivery 8b: Date of Collection: 20080608-20080928 Total Area = 74.06 sq miles Delivery 9: Date of Collection: 20080608-20080928 Total Area = 217.22 sq miles Delivery 10: Date of Collection: 20080608-20080928 Total Area = 224.82 sq miles Delivery 11: Date of Collection: 20080727-20090425 Total Area = 237.06 sq miles Delivery 12: Date of Collection: 20080727-20090425 Total Area = 216.10 sq miles Delivery 13: Date of Collection: 20080727-20090425 Total Area = 181.17 sq miles purpose: Provide high resolution terrain elevation and land cover elevation data. credit: DOGAMI status: (MD_ProgressCode) completed pointOfContact: (CI_ResponsibleParty) individualName: Ian Madin organisationName: DOGAMI contactInfo: (CI_Contact) phone: (CI_Telephone) voice: 971-673-1542 address: (CI_Address) deliveryPoint: 800 NE Oregon St. #28, Ste. 965 city: Portland administrativeArea: OR postalCode: 97232 country: USA electronicMailAddress: ian.madin@dogami.state.or.us role: (CI_RoleCode) pointOfContact resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) notPlanned descriptiveKeywords: (MD_Keywords) keyword: Bathymetry/Topography keyword: LiDAR keyword: Light Detection and Ranging keyword: DEM keyword: Digital Terrain Model keyword: DOGAMI keyword: Elevation data keyword: Bare earth keyword: High-resolution keyword: Bare ground keyword: DTM type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: None date: descriptiveKeywords: (MD_Keywords) keyword: United States keyword: Oregon keyword: Coos County keyword: Curry County keyword: Douglas County keyword: Lane County keyword: Pacific Northwest 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. aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: Lidar Project Reports date: citedResponsibleParty: (CI_ResponsibleParty) positionName: Citation URL contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/or/2008-2009_south_coast/delivery_1/ name: Lidar Project Reports description: Delivery 1 QA/QC report, as well as Data Collection Report function: (CI_OnLineFunctionCode) information role: associationType: (DS_AssociationTypeCode) crossReference aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: Lidar Project Reports date: citedResponsibleParty: (CI_ResponsibleParty) positionName: Citation URL contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/or/2008-2009_south_coast/delivery_2/ name: Lidar Project Reports description: Delivery 2 QA/QC report, as well as Data Collection Report function: (CI_OnLineFunctionCode) information role: associationType: (DS_AssociationTypeCode) crossReference aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: Lidar Project Reports date: citedResponsibleParty: (CI_ResponsibleParty) positionName: Citation URL contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/or/2008-2009_south_coast/delivery_3/ name: Lidar Project Reports description: Delivery 3 QA/QC report, as well as Data Collection Report function: (CI_OnLineFunctionCode) information role: associationType: (DS_AssociationTypeCode) crossReference aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: Lidar Project Reports date: citedResponsibleParty: (CI_ResponsibleParty) positionName: Citation URL contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/or/2008-2009_south_coast/delivery_4/ name: Lidar Project Reports description: Delivery 4 QA/QC report, as well as Data Collection Report function: (CI_OnLineFunctionCode) information role: associationType: (DS_AssociationTypeCode) crossReference aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: Lidar Project Reports date: citedResponsibleParty: (CI_ResponsibleParty) positionName: Citation URL contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/or/2008-2009_south_coast/delivery_5/ name: Lidar Project Reports description: Delivery 5 QA/QC report, as well as Data Collection Report function: (CI_OnLineFunctionCode) information role: associationType: (DS_AssociationTypeCode) crossReference aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: Lidar Project Reports date: citedResponsibleParty: (CI_ResponsibleParty) positionName: Citation URL contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/or/2008-2009_south_coast/delivery_6_7_8a/ name: Lidar Project Reports description: Delivery 6-8a QA/QC report, as well as Data Collection Report function: (CI_OnLineFunctionCode) information role: associationType: (DS_AssociationTypeCode) crossReference aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: Lidar Project Reports date: citedResponsibleParty: (CI_ResponsibleParty) positionName: Citation URL contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/or/2008-2009_south_coast/delivery_8b_9_10/ name: Lidar Project Reports description: Delivery 8b-10 QA/QC report, as well as Data Collection Report function: (CI_OnLineFunctionCode) information role: associationType: (DS_AssociationTypeCode) crossReference aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: Lidar Project Reports date: citedResponsibleParty: (CI_ResponsibleParty) positionName: Citation URL contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: ftp://ftp.csc.noaa.gov/pub/crs/beachmap/qa_docs/or/2008-2009_south_coast/delivery_11_12_13/ name: Lidar Project Reports description: Delivery 11-13 QA/QC report, as well as Data Collection Report function: (CI_OnLineFunctionCode) information role: associationType: (DS_AssociationTypeCode) crossReference spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vector language: eng; USA topicCategory: (MD_TopicCategoryCode) elevation extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -124.568779 eastBoundLongitude: -123.545579 southBoundLatitude: 41.996103 northBoundLatitude: 44.000003 temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2008-05-03 endPosition: 2009-04-25 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: Horizontal accuracies were not specified in the agreement since true horizontal accuracy is regarded as a product of the LiDAR ground foot print. LiDAR is referenced to co-acquired GPS base station data that has accuracies far greater than the value of the LiDAR foot print. The ground footprint is equal to 1/3333rd of above ground flying height. Survey altitude for this acquisition was targeted at 900 meters yielding a ground foot print of 0.27 meters. This value exceeds the typical accuracy value of ground control used to reference the LiDAR data (<0.01m). Project specifications required the LiDAR foot print to fall within 0.15 and 0.40 meters. For more information about the horizontal accuracy, please refer to the reports for each delivery, listed above in the Supplemental_Information field of this metadata record. result: report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy Report evaluationMethodDescription: Because this data set was collected in 14 different deliveries, each delivery has a different RMSE. The specific RMSE for each delivery is listed below: Delivery 1: RMSE: 0.061 m (0.2 ft) Delivery 2: RMSE: 0.066 m (0.21 ft) Delivery 3: RMSE: 0.054 m (0.178 ft) Delivery 4: RMSE: 0.057 m (0.187 ft) Delivery 5: RMSE: 0.058 m (0.191 ft) Delivery 6: RMSE: 0.057 m (0.186 ft) Delivery 7: RMSE: 0.057 m (0.186 ft) Delivery 8a: RMSE: 0.057 m (0.186 ft) Delivery 8b: RMSE: 0.073 m (0.24 ft) Delivery 9: RMSE: 0.073 m (0.24 ft) Delivery 10: RMSE: 0.073 m (0.24 ft) Delivery 11: RMSE: 0.071 m (0.158 ft) Delivery 12: RMSE: 0.071 m (0.158 ft) Delivery 13: RMSE: 0.071 m (0.158 ft) For more information about the vertical accuracies, please refer to the survey reports for each of these deliveries, listed above in the Supplemental_Information field of this metadata record. result: report: (DQ_CompletenessCommission) evaluationMethodDescription: LiDAR data has been collected and processed for all areas within the project study area. result: report: (DQ_ConceptualConsistency) measureDescription: Upon receipt from vendor (Watershed Sciences), all LiDAR data was independently reviewed by staff from the Oregon Department of Geology and Mineral Industries (DOGAMI) to ensure project specifications were met. All data were inventoried for completeness and data were checked for quality, which included examining LiDAR data for errors associated with internal data consistency, model quality, and accuracy. result: lineage: (LI_Lineage) processStep: (LE_ProcessStep) description: The LiDAR data was collected between May 3, 2008 and April 25, 2009. The survey used a Leica ALS50 Phase II laser system mounted in a Cessna Caravan 208B. The system was set to acquire > or = 105,000 laser pulses per second (i.e. 105 kHz pulse rate) and flown at 900 meters above ground level (AGL), capturing a scan angle of +/- 14 degrees from nadir. These settings were developed to yield points with an average native density of > or = 8 points per square meter over terrestrial surfaces. The native pulse density is the number of pulses emitted by the LiDAR system. Some types of surfaces (i.e. dense vegetation or water) may return fewer pulses than the laser originally emitted. Therefore, the delivered density can be less than the native density and lightly variable according to distributions of terrain, land cover, and water bodies. The completed areas were surveyed with opposing flight line side-lap of > or = 50% (> or = 100% overlap) to reduce laser shadowing and increase surface laser painting. The system allows up to four range measurements per pulse, and all discernible laser returns were processed for the output dataset. During the LiDAR survey of the study area, a static (1 Hz recording frequency) ground survey was conducted over monuments with known coordinates. After the airborne survey, the static GPS data are processed using triangulation with CORS stations checked against the Online Positioning User Service (OPUS) to quantify daily variance. Multiple sessions are processed over the same monument to confirm the antenna height measurements and reported position accuracy. Multiple DGPS units are used for the ground real-time kinematic (RTK) portion of the survey. To collect accurate ground surveyed points, a GPS base unit is set up over monuments to broadcast a kinematic correction to a roving GPS unit. The ground crew uses a roving unit to receive radio-relayed kinematic corrected positions from the base unit. This method is referred to as real-time kinematic (RTK) surveying and allows precise location measurement (sigma < or = 1.5 cm (0.6 in)). dateTime: DateTime: 2009-01-01T00:00:00 processor: (CI_ResponsibleParty) organisationName: Watershed Sciences, Inc. contactInfo: (CI_Contact) phone: (CI_Telephone) voice: 971-223-5152 address: (CI_Address) deliveryPoint: 215 SE 9th Ave., Suite 106 city: Portland administrativeArea: OR postalCode: 97214 electronicMailAddress: watershedsciences.com role: (CI_RoleCode) processor processStep: (LE_ProcessStep) description: 1. Laser point coordinates are computed using the IPAS and ALS Post Processor software suites based on independent data from the LiDAR system (pulse time, scan angle), and aircraft trajectory data (SBET). Laser point returns (first through fourth) are assigned an associated (x, y, z) coordinate along with unique intensity values (0-255). The data are output into large LAS v. 1.1 files; each point maintains the corresponding scan angle, return number (echo), intensity, and x, y, z (easting, northing, and elevation) information. 2. These initial laser point files are too large to process. To facilitate laser point processing, bins (polygons) are created to divide the dataset into manageable sizes (< 500 MB). Flightlines and LiDAR data are then reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. 3. Once the laser point data are imported into bins in TerraScan, a manual calibration is performed to assess the system offsets for pitch, roll, heading, and mirror scale. Using a geometric relationship developed by Watershed Sciences, each of these offsets is resolved and corrected if necessary. 4. The LiDAR points are then filtered for noise, pits, and birds by screening for absolute elevation limits, isolated points, and height above ground. Each bin is then inspected for pits and birds manually; spurious points are removed. For a bin containing approximately 7.5-9.0 million points, an average of 50-100 points are typically found to be artificially low or high. These spurious non-terrestrial laser points must be removed from the dataset. Common sources of non-terrestrial returns are clouds, birds, vapor, and haze. 5. The internal calibration is refined using TerraMatch. Points from overlapping lines are tested for internal consistency and final adjustments are made for system misalignments (i.e., pitch, roll, heading offsets and mirror scale). Automated sensor attitude and scale corrections yield 3-5 cm improvements in the relative accuracy. Once the system misalignments are corrected, vertical GPS drift is then resolved and removed per flight line, yielding a slight improvement (<1 cm) in relative accuracy. At this point in the workflow, data have passed a robust calibration designed to reduce inconsistencies from multiple sources (i.e. sensor attitude offsets, mirror scale, GPS drift) using a procedure that is comprehensive (i.e. uses all of the overlapping survey data). Relative accuracy screening is complete. 6. The TerraScan software suite is designed specifically for classifying near-ground points (Soininen, 2004). The processing sequence begins by "removing" all points that are not "near" the earth based on geometric constraints used to evaluate multi-return points. The resulting bare earth (ground) model is visually inspected and additional ground point modeling is performed in site-specific areas (over a 50-meter radius) to improve ground detail. This is only done in areas with known ground modeling deficiencies, such as: bedrock outcrops, cliffs, deeply incised stream banks, and dense vegetation. In some cases, ground point classification includes known vegetation (i.e., understory, low/dense shrubs, etc.) and these points are manually reclassified as non-grounds. dateTime: DateTime: 2009-01-01T00:00:00 processor: (CI_ResponsibleParty) organisationName: Watershed Sciences, Inc. contactInfo: (CI_Contact) phone: (CI_Telephone) voice: 971-223-5152 address: (CI_Address) deliveryPoint: 215 SE 9th Ave., Suite 106 city: Portland administrativeArea: OR postalCode: 97214 electronicMailAddress: watershedsciences.com role: (CI_RoleCode) processor processStep: (LE_ProcessStep) description: The NOAA Coastal Services Center (CSC) received the files in las format. The files contained LiDAR elevation and intensity measurements. The data were in Oregon Lambert (NAD83), International Feet coordinates and NAVD88 (Geoid 03) vertical datum. CSC performed the following processing to the data to make it available within the Digital Coast: 1. The data were converted from Oregon Lambert (NAD83), International Feet coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid 03. 3. The vertical units of the data were converted from International feet to meters. 4. The data were sorted by latitude and the headers were updated. dateTime: DateTime: 2010-06-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: 2011-10-31T00:00:00 processor: (CI_ResponsibleParty) individualName: Pamela Grothe organisationName: DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce contactInfo: (CI_Contact) contactInstructions: Contact Data Center role: (CI_RoleCode) processor return to top metadataMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) annually dateOfNextUpdate: 2014-06-05 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-06-05T15:38:06.249-06:00 maintenanceNote: Last Metadata Review Date: 2011-11-19 |