| March 2006 Lidar Point Data of Southern California Coastline: Long Beach to US/Mexican Border | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:50010 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset contact: (CI_ResponsibleParty) organisationName: OCM Partners contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) role: (CI_RoleCode) resourceProvider contact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2022-08-09T17:11:37 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top spatialRepresentationInfo: return to top referenceSystemInfo: return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(HARN) date: (CI_Date) date: 2008-11-12 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/CoordRefSystem/4152/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:4152 version: 6.18.3 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: 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: March 2006 Lidar Point Data of Southern California Coastline: Long Beach to US/Mexican Border alternateTitle: scripps_20060324_m54_metadata date: (CI_Date) date: 2006-07-26 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 50010 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/50010 protocol: WWW:LINK-1.0-http--link name: Full Metadata Record description: View the complete metadata record on InPort for more information about this dataset. function: (CI_OnLineFunctionCode) information role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) otherCitationDetails: quad names (from north to south): Long Beach, Los Alamitos, Long Beach OE S, Seal Beach, Newport Beach, Newport Beach OE S, Laguna Beach, San Juan Capistrano, Dana Point, San Clemente, San Onofre Bluff, Las Pulgas Canyon, Oceanside, San Luis Rey, Encinitas, Del Mar OE W, Del Mar, La Jolla OE W, La Jolla, Point Loma OE W, Point Loma, Imperial Beach OE W, Imperial Beach abstract: This data set contains lidar point data (Geodetic Coordinates) from a strip of Southern California coastline (including water, beach, cliffs, and top of cliffs) from Long Beach to the US/Mexico border. The data set was created by combining data collected using an Optech Inc. Airborne Laser Terrain Mapper (ALTM) 1225 in combination with geodetic quality Global Positioning System (GPS) airborne and ground-based receivers. The Bureau of Economic Geology, the University of Texas at Austin owns and operates an ALTM 1225 system (serial number 99d118). The system was installed in a twin engine Partenavia P-68 (tail number N3832K) owned and operated by Aspen Helicopter, Inc. The lidar data set described by this document was collected on 24 and 25 March 2006; Julian Days 08306 and 08406 (see Lineage, Source_Information, Source_Contribution for pass information). 99d118 instrument settings for these flights were; laser pulse rate: 25kHz, scanner rate: 26Hz, scan angle: +/- 20deg, beam divergence: narrow, altitude: 300-600m AGL, and ground speed: 95-120kts. Two GPS base stations were operating during each day of the survey, Point Loma and San Onofre on 08306 and Seal Beach and San Onofre on 08406 (see Lineage, Source_Information, and Source Contribution for coordinates). Data represented is all points including terrain, vegetation, and structures. This data also contains returns from the water surface. No processing has been done to remove returns from terrain, vegetation, structures or water surfaces. Original contact information: Contact Name: Julie Thomas/Randy Bucciarelli Contact Org: SCBPS/CDIP, Scripps Institution of Oceanography Title: Project Managers Phone: 858-534-3032 This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The data described in this document will be compared with previous and forthcoming data sets to determine rates of shoreline change along the Southern California coastline. The SCBPS program is designed to improve the understanding of beach sand transport by waves and currents, thus improving local and regional coastal management. credit: SCBPS/CDIP is jointly funded by the US Army Corps of Engineers and the California Department of Boating and Waterways. The initial data are collected by Bureau of Economic Geology, The University of Texas at Austin: R. Gutierrez and T. Hepner. Center for Space Research, The University of Texas at Austin: A. Neuenschwander. Data are further classified and processed by the SCBPS group, located at the Scripps Institution of Oceanography. 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 Aug 01, 2023 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: 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: (missing) maintenanceNote: None planned, as needed descriptiveKeywords: (MD_Keywords) keyword: Latitude keyword: Longitude keyword: beach keyword: intensity keyword: point file keyword: shoreline type: (MD_KeywordTypeCode) theme descriptiveKeywords: (MD_Keywords) keyword: 2006 keyword: March type: (MD_KeywordTypeCode) temporal 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]: March 2006 Lidar Point Data of Southern California Coastline: Long Beach to US/Mexican Border [Data Date Range], https://www.fisheries.noaa.gov/inport/item/50010. 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: This data was collected in partnership with Scripps Institution of Oceanography, The University of California, San Diego. Any conclusions drawn from analysis of this information are not the responsibility of the Bureau of Economic Geology or the University of Texas at Austin, NOAA, the OCM 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: 50010 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/50010.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: -118.203606 eastBoundLongitude: -117.116806 southBoundLatitude: 32.510392 northBoundLatitude: 33.768792 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2006-03-24 endPosition: 2006-03-25 supplementalInformation: The ALTM 1225 (SN#99d118) lidar instrument has the following specifications: operating altitude = 410-2,000 m AGL; maximum laser pulse rate = 25 kHz; laser scan angle = variable from 0 to +/-20deg from nadir; scanning frequency = variable, 28 Hz at the 20deg scan angle; and beam divergence: narrow = 0.2 milliradian (half angle, 1/e). The ALTM 1225 does not digitize and record the waveform of the laser reflection, but records the range and backscatter intensity of the first and last laser reflection using a constant-fraction discriminator and two Timing Interval Meters (TIM). ALTM elevation points are computed using three sets of data: laser ranges and their associated scan angles, platform position and orientation information, and calibration data and mounting parameters (Wehr and Lohr, 1999). Global Positioning System (GPS) receivers in the aircraft and on the ground provide platform positioning. The GPS receivers record pseudo-range and phase information for post-processing. Platform orientation information comes from an Inertial Measurement Unit (IMU) containing three orthogonal accelerometers and gyroscopes. An aided-Inertial Navigation System (INS) solution for the aircraft's attitude is estimated from the IMU output and the GPS information. Wehr, A. and U. Lohr, 1999, Airborne laser scanning - an introduction and overview, ISPRS Journal of Photogrammetry and Remote Sensing, vol. 54, no.2-3, pp.68-82. 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=54 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/54/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Simple download of data files. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: The lidar data is estimated to have a horizontal error of less than or equal to 0.50 m from comparison between kinematic GPS road survey and a 1m resolution grey-scale image generated from the lidar backscatter intensity data. Kinematic GPS data were superimposed on the lidar backscatter image and examined for any mismatch between the horizontal position of the ground GPS and the corresponding features on the lidar image. Horizontal agreement between the ground kinematic GPS and the lidar was within the resolution of the 1m -resolution backscatter image. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The March 2006 lidar data were compared to the 1998 ATM LIDAR data to determine offsets in the vertical position. The ATM survey points are estimated to have a vertical accuracy of +/- 15 cm. The March 2006 lidar data set was sorted to find data points that fell within 0.5 m of an ATM LIDAR survey point along piers in the survey area. The mean elevation difference between the The elevation differences between the March 2006 survey and the ATM survey were used to estimate and remove TIM1 and TIM2 elevation biases from each lidar flight. The standard deviation of these elevation differences provides estimates of the lidar precision. After bias adjustment the mean lidar elevations have a vertical accuracy of 0.10 m. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: Data were edited by an automated method to remove obvious outliers above a threshold of 150m. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Not Applicable result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: GPS and XYZ-Point Data Processing Transfer raw ALTM 1225 flight data (laser ranges with associated scan angle information and IMU data), airborne GPS data collected at 1 Hz using Ashtech receiver, and ground-based GPS data collected at 1 Hz using Ashtech Z-12 receivers to processing computer. Generate decimated lidar point file from above three data sets using Optech's Realm 2.27 software. This is a 9-column ASCII data set with the following format: time tag; first pulse Easting, Northing, HAE; last pulse Easting, Northing, HAE; first pulse intensity; and last pulse intensity. View decimated lidar point file to check data coverage (i.e. sufficient overlap of flight lines and point spacing). Compute base station coordinates using National Geodetic Survey's PAGES-NT software. Compute aircraft trajectories from each base station GPS dataset using National Geodetic Survey's KINPOS software. Solutions for base stations coordinates and aircraft trajectories are in the International Terrestrial Reference Frame of 2000 (ITRF2000). A final aircraft trajectory was computed from a weighted average of the trajectories from the two base stations. Epoch-by-epoch weighting for the individual trajectories was inversely proportional to the baseline length (distance from base station) and solution RMS. Transformed trajectory solution from ITRF2000 to North American Datum of 1983 (NAD83) using the National Geodetic Survey's Horizontal Time Dependent Positioning software (http://www.ngs.noaa.gov/TOOLS/Htdp/Htdp.html). Input NAD83 trajectories and aircraft inertial measurement unit data into Applanix's POSProc version 2.1.4 to compute an optimal 50Hz inertial navigation solution (INS) and smoothed best estimate of trajectory (SBET). Substitute the INS and SBET into Realm 2.27. Generate a set of initial lidar instrument calibration parameters (pitch, roll, scale, and elevation bias) for each lidar flight, then incrementally improve parameters by iteratively comparing a subset of the lidar output to the GPS kinematic ground control. Once the instrument calibration parameters are sufficiently accurate, create the complete lidar point file (9-column ASCII file) for the entire survey area in UTM Zone 11 with elevations being heights above the GRS-80 reference ellipsoid (HAE). The output format from REALM 2.27 was a 9-column ASCII file containing: the second in the GPS week, easting, northing and HAE of the first lidar return, the easting, northing and HAE of the last lidar return, and the laser backscatter intensity of the first and last returns. Using the GEOID99 geoid model, heights above the GRS80 ellipsoid were converted to orthometric heights with respect to the North American Vertical Datum of 1988 (NAVD88). Parse the 9-column lidar point file into 3.75-minute quarter-quadrangle components. Convert UTM Easting and Northing to geodetic latitude and longitude with respect to the GRS80 ellipsoid. The conversion was computed using the TMGEOD and TCONPC fortran subroutines written by T. Vincenty (NGS). Each record contains 9 columns of data: time tag (seconds in the GPS week), first return Latitude,first return Longitude, first return NAVD88, last return Latitude, last return Longitude, last return NAVD88, first return intensity, and last return intensity. In some cases either the first or last return values may be missing (5 columns). Latitude and longitude are in decimal degrees with nine significant digits to retain the 0.01m resolution of the UTM coordinates. West longitude is negative and north latitude is positive. The UTM quarter-quad files were re-organized into latitude delineated files. UTM quarter-quads files that were delineated by the same upper and lower latitude bounds were concatenated. The lat-long files were named by the month-year of the survey (e.g. mar06) and the lower latitude bounding the quarter-quad. Processing occurred 20060324-20060726. dateTime: DateTime: 2006-03-24T00:00:00 processStep: (LI_ProcessStep) description: Created initial metadata dateTime: DateTime: 2003-04-18T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received files in ASCII format. The files contained LiDAR intensity and elevation measurements. OCM performed the following processing on the data to make it available within the LiDAR Data Retrieval Tool (LDART) 1. Data returned to ellipsoid heights from NAVD88, using GEOID99. 2. Data converted to LAS format. 3. The LAS data were sorted by latitude and the headers were updated. dateTime: DateTime: 2007-07-24T00:00:00 source: (LI_Source) description: Source Contribution: air and ground GPS files base station coordinates Easting, Northing, HAE in NAD83, Zone 11 (Latitude, Longitude): Seal Beach (SEAL) = 399190.210, 3733584.054, -27.287 (N 33 44 15.03814, W 118 05 17.77225) San Onofre (SANO) = 447430.058, 3693036.854, -5.193 (N 33 22 31.08745, W 117 33 54.55130) Point Loma (LOMA) = 477399.573, 3614791.280, 90.855 (N 32 40 13.99848, W 117 14 27.74927) | Type of Source Media: digital file sourceCitation: (CI_Citation) title: Air and Ground GPS files from 08306 and 08406 date: (CI_Date) date: 2006-03-25 dateType: (CI_DateTypeCode) publication sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2006-03-24 endPosition: 2006-03-25 source: (LI_Source) description: Source Contribution: raw lidar data from ALTM 1225 (all times UTC) 08306 Pass A (Carlsbad to Mexico) = 18:41-19:14 Pass B (Mexico to Point Loma) = 19:17-19:24 Pass C (Point Loma to Mexico) = 19:29-19:35 Pass D (Point Loma to Dana Point) = 20:06-20:43 Pass E (Dana Point to La Jolla) = 20:49-21:16 Pass F (La Jolla to Dana Point) = 21:39-22:26 Pass G (Dana Point to Carlsbad) = 22:13-22:26 2 Calibration Passes = 21:19-21:25 08406 Pass H (Newport Beach to Long Beach) = 20:44-20:56 Pass I (Long Beach to Dana Point) = 21:00-21:17 Pass J (Dana Point to Long Beach) = 21:31-21:47 Pass K (Long Beach to Dana Point) = 21:51-22:08 Pass L (Dana Point to Newport Beach) = 22:12-22:19 2 Calibration Passes = 22:24-22:30 | Type of Source Media: digital file sourceCitation: (CI_Citation) title: Raw lidar data output from ALTM 1225, SN#99D118 date: (CI_Date) date: 2006-03-25 dateType: (CI_DateTypeCode) publication sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2006-03-24 endPosition: 2006-03-25 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-08-01T06:03:56 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |