2011 Federal Emergency Management Agency (FEMA) Topographic LiDAR: Quinnipiac River Watershed, Connecticut
OCM Partners
Data Set
(DS)
| ID: 49656
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49656
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2011 Federal Emergency Management Agency (FEMA) Topographic LiDAR: Quinnipiac River Watershed, Connecticut |
---|---|
Short Name | ct2011_fema_quinnipiacriver_m1472_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2013-04 |
* » Abstract |
The Quinnipiac AOI consists of one 443 square mile area. Ground Control is collected throughout the AOI for use in the processing of LiDAR data to ensure data accurately represents the ground surface. QA/QC checkpoints, (FVA and CVA - see Ground Control process step for further information) also collected throughout the AOI, are used for independent quality checks of the processed LiDAR data. LiDAR acquisition products include Pre- and Post- flight reports which contain information on the flightlines, equipment parameters, and other pertinant acquisition details. The LiDAR product is considered to be point cloud data and consists of 1500mx1500m tiles of LAS points which are partially classified such that the bare earth points can be calibrated to the ground surface and tested via the independent QC to ensure the ground surface is accurately represented. The average point spacing of the data set is 0.5m. |
* Purpose |
To provide precise elevation data to aid in flood hazard mapping and flood risk evalutation projects. |
Notes |
10300 |
Other Citation Details | |
• Supplemental Information |
A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1472/supplemental/ct2011_fema_quinnipiacriver_footprint.KMZ |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
None | Land Surface |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Platform Keywords
Thesaurus | Keyword |
---|---|
Physical Location
• » Organization | Office for Coastal Management |
---|---|
• » City | Charleston |
• » State/Province | SC |
• Country | |
• » Location Description |
Data Set Information
* Data Set Scope Code | Data Set |
---|---|
• Data Set Type | |
• Maintenance Frequency | As Needed |
Maintenance Note | |
» Data Presentation Form | las |
• Entity Attribute Overview |
LiDAR points in LAS 1.2 format |
Entity Attribute Detail Citation |
Appendix M of FEMA Guidelines and Specifications for FEMA Flood Hazard Mapping Partners contains a detailed description of the data themes and references to other relevant information. |
Entity Attribute Detail URL | |
Distribution Liability |
Any conclusions drawn from the analysis of this information are not the responsibility of Photo Science Inc, CompassData Inc, Greenhorne & O'Mara Inc, STARR, FEMA, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit | Ground control and quality control checkpoints were collected by CompassData, Inc. LiDAR was acquired and processed by Photo Science, Inc. Quality Control testing was performed by CompassData, Inc. Quality Assurance testing was conducted by Greenhorne & O'Mara, Inc. All firms were under contract to STARR, A Joint Venture which held the FEMA contract and task order for this work. |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2013-04 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2013-04 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2013-04 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Point of Contact |
---|---|
* » Date Effective From | 2013-04 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference | Ground Condition |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -73.1058 |
---|---|
* » E° Bound | -72.374263 |
* » N° Bound | 41.710591 |
* » S° Bound | 41.202098 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Discrete |
---|---|
* » Start | 2011-08-23 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | |
Horizontal Distance Units | |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
Spatial Representation
Grid Representation Used? | |
---|---|
Vector Representation Used? | Yes |
Text / Table Representation Used? | |
TIN Representation Used? | |
Stereo Model Representation Used? | |
Video Representation Used? |
Grid Representation
Dimension Count | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | |||||||||||||
Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | |
Curve Object Count | |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
Reference Systems
Reference System
EPSG Code | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» Data Access Procedure |
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=1472 ; |
• » Data Access Constraints |
None |
• Data 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. These data depict the heights at the time of the survey and are only accurate for that time. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=1472 |
Distributor | |
File Name | Customized Download |
Description |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1472/index.html |
Distributor | |
File Name | Bulk Download |
Description |
Simple download of data files. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Archive Information
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
URLs
URL | https://coast.noaa.gov/dataviewer |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://coast.noaa.gov |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | 2017-03-20 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Date that the source FGDC record was last modified. |
Activity Time | 2017-11-14 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details. |
Activity Time | 2018-02-08 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload of Positional Accuracy fields only. |
Activity Time | 2018-03-13 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload to move data access links to Distribution Info. |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
|
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy | |
Vertical Positional Accuracy |
Deliverables were tested by for both vertical and horizontal accuracy. The vertical unit of the data file is in meters with 2-decimal point precision.; Quantitative Value: 0.114 meters, Test that produced the value: RMSEz calculated in open terrain. Reported in meters. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
Survey data have been checked for completeness, points have been collected in correct vegetation units, and distributed throughout the AOI. The terrain data have been checked for completeness against AOI polygons. No gaps as defined by FEMA Procedural Memo No. 61 are known to exist within the dataset. |
Conceptual Consistency |
Survey data have been confirmed to be in proper units, coordinate systems and format. The terrain data have been confirmed as complete LAS format data files. Header files are in proper LAS format with content as specified by FEMA Procedural Memo No. 61. |
» Quality Control Procedures Employed |
Data Management
» Have Resources for Management of these Data Been Identified? | |
---|---|
» Approximate Percentage of Budget for these Data Devoted to Data Management | |
» Do these Data Comply with the Data Access Directive? | |
» Is Access to the Data Limited Based on an Approved Waiver? | |
» If Distributor (Data Hosting Service) is Needed, Please Indicate | |
» Approximate Delay Between Data Collection and Dissemination | |
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed |
|
» Actual or Planned Long-Term Data Archive Location | |
» If World Data Center or Other, Specify | |
» If To Be Determined, Unable to Archive, or No Archiving Intended, Explain |
|
» Approximate Delay Between Data Collection and Archiving | |
» How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive? |
|
Lineage
» Lineage Statement |
---|
Sources
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Process Steps
Process Step Number | 1 |
---|---|
» Description |
GPS based surveys were utilized to support both processing and testing of LiDAR data within FEMA designated Areas of Interest (AOIs). Geographically distinct ground points were surveyed using GPS technology throughout the AOIs to provide support for three distinct tasks. Task 1 was to provide Vertical Ground Control to support the aerial acquisition and subsequent bare earth model processing. To accomplish this, survey-grade Trimble R-8 GPS receivers were used to collect a series of control points located on open areas, free of excessive or significant slope, and at least 5 meters away from any significant terrain break. Most if not all control points were collected at street/road intersections on bare level pavement. Task 2 was to collect Fundamental Vertical Accuracy (FVA) checkpoints to evaluate the initial quality of the collected point cloud and to ensure that the collected data was satisfactory for further processing to meet FEMA specifications. The FVA points were collected in identical fashion to the Vertical Ground Control Points, but segregated from the point pool to ensure independent quality testing without prior knowledge of FVA locations by the aerial vendor. Task 3 was to collect Consolidated Vertical Accuracy CVA) checkpoints to allow vertical testing of the bare-earth processed LiDAR data in different classes of land cover, including: Open (pavement, open dirt, short grass), High Grass and Crops, Brush and Low Trees, Forest, Urban. CVA points were collected in similar fashion as Control and FVA points with emphasis on establishing point locations within the predominant land cover classes within each AOI or Functional AOI Group. In order to successfully collect the Forest land cover class, it was necessary to establish a Backsight and Initial Point with the R8 receiver, and then employ a Nikon Total Station to observe a retroreflective prism stationed under tree canopy. This was necessary due to the reduced GPS performance and degradation of signal under tree canopy. |
Process Date/Time | 2011-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
The R-8 receivers were equipped with cellular modems to receive real-time correction signals from the Keystone Precision Virtual Reference Station (VRS) network encompassing the Region 1 AOIs. Use of the VRS network allowed rapid collection times (~3 minutes/point) at 2.54 cm (1 inch) initial accuracy. All points collected were below the 8cm specification for testing 24cm, Highest category LiDAR data. To ensure valid in-field collections, an NGS monument with suitable vertical reporting was measured using the same equipment and procedures used for Control, FVA and CVA points on a daily basis. The measurement was compared to the NGS published values to ensure that the GPS collection schema was producing valid data and as a physical proof point of quality of collection. Those monument measurements are summarized in the Accuracy report included in the data delivered to FEMA. In order to meet FEMA budgetary requirements, AOIs were consolidated into Functional Groups: if AOIs were contiguous, they were treated as one large AOI to allow collection of 20 FVA points and 15 additional CVA points across the group of AOIs. 20 FVA points are necessary to allow testing to CE95 - 1 point out of 20 may fail vertical testing and still allow the entire dataset to meet 95% accuracy requirements. In similar fashion, 20 CVA points are necessary to test to CE95 as discussed above. 15 CVA points were collected per AOI or per Functional Group with the intention at the outset that 5 of the collected FVAs would perform double - duty as Open-class CVA points, to total 20 CVAs per AOI or Functional Group. The Functional Groups are as follows: Narragansett/Charles/Blackstone(northeast), Nashua, Blackstone(north and west), Quinnipiac, Quincy/Suffolk (while included as part of the FEMA Charles AOI, was physically separated from the Charles AOI polygon and treated as an independent functional area). The following software packages and utilities were used to control the GPS receiver in the field during data collection, and then ingest and export the collected GPS data for all points: Trimble Survey Controller, Trimble Pathfinder Office. The following software utilities were used to translate the collected Latitude/Longitude Decimal Degree HAE GPS data for all points into Latitude/Longitude Degrees/Minutes/Seconds for checking the collected monument data against the published NGS Datasheet Lat/Long DMS values and into UTM NAD83 Northings/Eastings: U.S. Army Corps of Engineers CorpsCon, National Geodetic Survey Geoid09NAVD88. MSL values were determined using the most recent NGS-approved geoid model to generate geoid separation values for each Lat/Long coordinate pair. In this fashion, Orthometric heights were determined for each Control, FVA and CVA point by subtracting the generated Geoid Separation value from the Ellipsoidal Height (HAE) for publication and use as MSL NAVD88 (09). |
Process Date/Time | 2011-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
Using a Leica ALS60 LiDAR system, 101 flight lines of highest density (Nominal Pulse Spacing of 1.0m) were collected over the Quinnipiac area which encompasses 443 square miles. A total of 10 missions were flown on Dec 11, 2010, Dec 16, 2010, Dec 17, 2010, Dec 18, 2010, March 29, 2011, March 30, 2011, May 6, 2011, May 8, 2011, May 10, 2011, and May 27, 2011. One airborne global positioning system (GPS) base station was used to support the LiDAR data acquisition: MMK-A. Additional information can be found in the Post-Flight Aerial Acquisition Report. |
Process Date/Time | 2011-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
Leica proprietary software was used in the post-processing of the airborne GPS and inertial data that is critical to the positioning and orientation of the sensor during all flights. Pairing the aircraft's raw trajectory data with the stationary GPS base station data, this software yields Leica's IPAS TC ("Inertial Positioning & Attitude Sensor - Tightly Coupled") smoothed best estimate of trajectory (an "SBET", in Leica's .sol file format) that is necessary for Leica's ALSPP post processing software to develop the resulting geo-referenced point cloud from the LiDAR missions. The point cloud is the mathematical three dimensional composite of all returns from all laser pulses as determined from the aerial mission. At this point this data is ready for analysis, classification, and filtering to generate a bare earth surface model in which the above-ground features are removed from the data set. The point cloud was created using Leica's Post Processor software. GeoCue was used in the creation of some of the files needed in downstream processing, as well as in the tiling of the dataset into more manageable file sizes. The TerraScan and TerraModeler software packages are then used for the automated data classification, manual cleanup, and bare earth generation from this data. Project specific macros were used to classify the ground and to remove the side overlap between parallel flight lines. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. QT Modeler was used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. In-house software was then used to perform final statistical analysis of the classes in the LAS files. |
Process Date/Time | 2011-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 5 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) received the topographic files in LAZ V1.2 format (a compressed LAS format). The files contained lidar elevation measurements. The data were received in NAD83 UTM Zone 18N coordinates and were vertically referenced to NAVD88 using the Geoid09 model. The vertical units of the data were meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The topographic las files were converted from a Projected Coordinate System (UTM 18N) to a Geographic Coordinate system (GCS). 2. The topographic las files' horizontal units were converted from meters to decimal degrees. 3. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid09. |
Process Date/Time | 2013-03-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 49656 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-15 15:21+0000 |
Metadata Record Last Modified By | SysAdmin InPortAdmin |
» Metadata Record Last Modified | 2022-08-09 17:11+0000 |
Metadata Record Published | 2022-03-16 |
Owner Org | OCMP |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2022-03-16 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2023-03-16 |
Tags |
---|