| 2008 USGS New Jersey Lidar: Somerset County | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49857 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:38 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(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 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: 2008 USGS New Jersey Lidar: Somerset County alternateTitle: nj2008_somerset_m545_metadata date: (CI_Date) date: 2008-05-01 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49857 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49857 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) abstract: These data support the general geospatial needs of the USGS and other federal agencies. LiDAR data is remotely sensed high-resolution elevation data collected by an airborne collection platform. By positioning laser range finding with the use of 1 second GPS with 200hz inertial measurement unit corrections, Airborne 1's LiDAR instruments are able to make highly detailed geospatial elevation products of the ground, man-made structures and vegetation. The LiDAR flightlines for this project were planned for a 50% acquisition overlap. The nominal resolution of this project without overlap is 1.203m, with a 0.90m resolution with the 50% overlap, assuming a normal distribution. Two returns were recorded for each pulse in addition to an intensity value. GPS Week Time, Intensity, Flightline and number attributes were recorded for each LiDAR point. Positional values were recorded to the centimeter level, while GPS is recorded to a 10th of a millisecond. Scan angle was recorded to the nearest angle, Intensity is recorded as a 12 Bit dynamic range value and echo is recorded as a numeric value from 0 to 256. The data was originally provided as random points, in LAS v1.1 format, classified according to the following codes: Class 1 Non-ground/Extracted Features Last Pulse Class 2 Bare Earth Ground Features Last Pulse Class 3 Extracted Features First Pulse Class 4 Bare Earth Ground Features First Pulse It should be noted that Class 3 and 4 are not ASPRS classes but since this data is a two pulse system, this is the most efficient format to separate the pulses and classification process. The data was reclassified into 2 distinct classifications: Class 1 Non-ground/Extracted Features First and Last Pulse Class 2 Bare Earth Ground Features First and Last Pulse This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: This data was collected to support geospatial analysis of Somerset County, New Jersey. credit: Acknowledgment of the U.S. Geological Survey would be appreciated for products derived from these data. 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: (MD_MaintenanceFrequencyCode) notPlanned 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]: 2008 USGS New Jersey Lidar: Somerset County [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49857. 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 that 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: 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: 49857 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49857.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: -74.798045 eastBoundLongitude: -74.499545 southBoundLatitude: 40.373106 northBoundLatitude: 40.758506 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2008-02-01 supplementalInformation: a) Nominal Pulse density = The nominal resolution of this project without overlap is 1.203m. b) Calibration procedures = - General Overview: The Airborne LiDAR survey was conducted using one OPTECH 2050 systems flying at a nominal height of 1370 meters AGL a total angular coverage of 40 degrees. Flight line spacing nominally 639 meters providing overlap of 50% on adjacent flight lines. Lines were flown in N/S directions to best optimize flying time considering the layout for the project. Distances from base station to aircraft (differential baselines) were kept to a maximum of 30 km while the mean is 6.8 km. The aircraft was a Cessna Caravan, registration N682AC, was used for the survey. This aircraft has a flight range of approximately 13.5 hours and was flown at an average altitude 1370 meters above ground level (AGL). The aircraft was staged from the Morristown and Princeton Airports and ferried daily to the project site for flight operations. Aircraft Speed = 110 Knots Number of Scanners = 1 Swath Width = 1278.01 m Nominal Distance Between Flight Lines = 639m Data Acquisition Height = 1370 meters AGL Pulse Repetition Rate = 50 Kilohertz Number of Returns Per Pulse = 2 Scanner Field of View = 40 degrees Frequency of Scan = 28 Hertz Beam Divergence = Narrow - GPS Receivers: A combination of Leica 500 Series and Applanix POSAv-410 dual frequency GPS receivers were used to support the airborne operations of this survey and to establish the GPS control network. - Number of Flights and Flight Lines: A total of 3 missions were flown for this project with flight time ranging approximately 3.5 hours under good meteorological and GPS conditions. 51 flight lines were flown over the project site to provide complete coverage. - Reference Coordinate System Used: Existing NGS (National Geodetic Survey) monuments were observed as control base stations in a GPS control network - PIDs AG9916 and KV1189. AG9916 and KV1189 were occupied as primary control for the project flight missions and kinematic ground surveys. The published horizontal datum of the NGS stations is NAD83 and the vertical datum NAVD88. The following are the final coordinates of the newly established control points used in this project: Station_PID: AG9916 West_Longitude: -074 26 46.04499 North_Latitude: 40 33 26.21313 Ellips_Elev: -7.771m Station_PID: KV1189 West_Longitude: -074 43 48.85846 North_Latitude: 40 36 22.24551 Ellips_Elev: -7.771m - Geoid Model Used: The Geoid03 geoid model, published by the NGS, was used to transform all ellipsoidal heights to orthometric. The Lidar QA/QC Quantitative and Qualitative Assessment Report for this data set may be viewed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/545/supplemental/lidarqaqcreport_somerset_final.pdf A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/545/supplemental/2008_USGS_NJ_Lidar_Somerset_County.kmz return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: LiDAR point data in LAS 1.1 ASPRS classification scheme Class 1 Non-ground/Extracted Features Last Pulse; Class 2 Bare Earth Ground Features Last Pulse; Class 3 All Shots First Pulse; Class 7 Noise. date: (unavailable) return to top distributionInfo: (MD_Distribution) distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) distributor transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=545 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/545/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Simple download of data files. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_QuantitativeAttributeAccuracy) nameOfMeasure: Accuracy evaluationMethodDescription: According to Airborne 1 standards; the following aspects of the LiDAR data was verified during the course of the project processing: -Data accuracy and errors -Anomaly checks through full-feature hillshades and 3-D modeling -Post automated classification Bare-earth verification -Final quality control of deliverable products ensuring integrity, graphical quality result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Compiled to meet 0.5m horizontal accuracy at the 95 percent confidence level result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Independent accuracy testing was performed by Dewberry using high accuracy quality control checkpoints distributed around Somerset County on near level open bare terrain and near level vegetated terrain. Dewberry uses testing procedures consistent with those specified in the National Standard for Spatial Data Accuracy (NSSDA). The Bare Earth RMSEz is 0.06m compared to the specified 0.15m for accuracy. This number represents the combined vertical accuracy of 40 individual open terrain (RMSEz = 0.058m) and urban (RMSEz = 0.063m) checkpoints. The RMSEz for Vegetation is 0.10m compared to the specified 0.27m for accuracy. This represents the combined vertical accuracy of 20 individual vegetated (plant heights between 1 and 5 ft; RMSEz = 0.119m) and forested (plant heights greater than 5 ft; RMSEz = 0.083m) checkpoints. ; Quantitative Value: 0.114 meters, Test that produced the value: National Standard for Spatial Data Accuracy. Using NSSDA standards, this LiDAR dataset was tested 0.114m fundamental vertical accuracy at 95% confidence level, compared to 0.363m for 2ft equivalent contour. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: According to Airborne 1 standards, data completeness and integrity was verified. Conformance to Airborne 1 standards are met for all delivered products. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: All LAS formatted LiDAR data are validated to ensure that data on delivery media is in correct physical format and is readable and correctly georeferenced and projected. Note that LiDAR intensity is not calibrated or normalized. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: > Airborne GPS Kinematic Airborne GPS kinematic data was post processed at Airborne 1 facilities using POS-GNSS kinematic On-The-Fly (OTF) software. Flights were flown with a minimum of 6 satellites in view (13o above the horizon) and with a PDOP of better than 3.5. Distances from base station to aircraft (differential baselines) were kept to a maximum of 31 km while the mean is 16 km, to ensure a strong OTF (On-The-Fly) solution. For all flights, the GPS data can be classified as excellent, with GPS residuals of 5cm average but no larger than 10 cm being recorded. >Generation and Calibration of laser points (raw data) The initial step of calibration is to verify availability and status of all needed GPS and Laser data against field notes and compile any data if not complete. Subsequently the mission points are output using Optech's REALM, initially with default values from Optech or the last mission calibrated for system. The initial point generation for each mission calibration is verified within Microstation/Terrascan for calibration errors. If a calibration error greater than specification is observed within the mission, the roll pitch and scanner scale corrections that need to be applied are calculated. The missions with the new calibration values are regenerated and validated internally once again to ensure quality. All missions are validated against the adjoining missions for relative vertical biases and collected GPS kinematic ground truthing points for absolute vertical accuracy purposes. On a project level, a coverage check is carried out to ensure no slivers are present. >Data Classification and Editing The data was processed using the software TerraScan, and following the methodology described herein. The initial step is the setup of the TerraScan project, which is done by importing client provided tile boundary index (converted to the native UTM zone for processing)encompassing the entire project areas. The 3D laser point clouds, in binary format, were imported into the TerraScan project and divided in 409 Tiles as specified by 133 Urban Area Ortho tiles in LAS 1.0 format. Once tiled, the laser points were classified using a proprietary routine in TerraScan. This routine removes any obvious outliers from the dataset following which the ground layer is extracted from the point cloud. The ground extraction process encompassed in this routine takes place by building an iterative surface model. This surface model is generated using three main parameters: building size, iteration angle and iteration distance. The initial model is based on low points being selected by a "roaming window" with the assumption is that these are the ground points. The size of this roaming window is determined by the building size parameter. The low points are triangulated and the remaining points are evaluated and subsequently added to the model if they meet the iteration angle and distance constraints. This process is repeated until no additional points are added within an iteration. A second critical parameter is the maximum terrain angle constraint, which determines the maximum terrain angle allowed within the classification model. The data is then manually quality controlled with the use of hillshading, cross-sections and profiles. Any points found to be of class vegetation, building or error during the quality control process, are removed from the ground model and placed on the appropriate layer. An integrity check is also performed simultaneously to verify that ground features such as rock cuts, elevated roads and crests are present. Once data has been cleaned and complete, it is then by a supervisor via manual inspection and through the use of a hillshade mosaic of the entire project area. dateTime: DateTime: 2008-02-01T00:00:00 processStep: (LI_ProcessStep) description: >Deliverable Product Generation -Deliverable Tiling Scheme All files were converted to LAS 1.1, in the specified projection and units and were delivered in the client provided tiling scheme with a total of 409 tiles. -LAS 1.1 Files LiDAR point data in LAS 1.1, classified according to the following classification scheme: Class 1 Non-ground/Extracted Features Last Pulse Class 2 Bare Earth Ground Features Last Pulse Class 3 Extracted Features First Pulse Class 4 Bare Earth Ground Features First Pulse The data contains the following fields of information (Precision reported in brackets): Class (Integer), GPS WeekTime (0.0001 seconds), Easting (0.01 meter), Northing (0.01 meter), Elevation (0.01 meter), Echo Number (Integer 1 to 2), Echo (Integer 1 to 2), Intensity (12 Bit Dynamic), Flightline, Scan Angle (Integer Degree) All points outside project area were assigned to Class 1 - Non-Ground. -GPS Trajectory Files GPS Trajectory Files were provided in digital copy -ABGPS/IMU Positions ABGPS/IMU combined files containing time,x,y,z,kappa,phi,omega were provided in ASCII format. All positions were provided in NAD83 UTM18, NAVD88(Geoid03), GPS seconds (reported to a 10th of a millisecond), meters (reported to a centimeter) for the XYZ and degrees for the kappa,phi,omega (reported to 6 decimals of a degree). dateTime: DateTime: 2008-02-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received the files in las format. The files contained Lidar elevation and intensity measurements. The data were in projected in UTM coordinates, Zone 18 (NAD83), and referenced to the orthometric datum of NAVD88 utilizing Geoid 03. OCM performed the following processing to the data to make it available within the Digital Coast: 1. The data were converted from UTM Zone 18 (NAD83) coordinates to geographic coordinates (NAD83). 2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid 03. 3. The LAS data were reclassifed from 4 to 2 classes: - Class 1, Non-ground/Extracted Features Last Pulse; Extracted Features First Pulse - Class 2, Bare Earth Ground Features Last Pulse; Bare Earth Ground Features First Pulse 4. The LAS data were sorted by latitude and the headers were updated. dateTime: DateTime: 2010-08-27T00:00:00 processStep: (LI_ProcessStep) description: The vertical values in this data set have been converted to reference North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters, using the GEOID18 grids provided by the National Geodetic Survey. Any datum and projection transformations were then done with the Office for Coastal Management 'datum_shift' program. Compression to an LAZ file was done with the LAStools 'laszip' program and can be unzipped with the same free program (laszip.org) Processing notes: dateTime: DateTime: 2023-08-01T06:05:01 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |