2006 Fulton County Georgia Lidar
OCM Partners
Data Set
(DS)
| ID: 49724
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49724
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2006 Fulton County Georgia Lidar |
---|---|
Short Name | ga2006_fultoncounty_m2526_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2013-08-12 |
* » Abstract |
The Light Detection and Ranging (LiDAR) LAS dataset is a survey of Fulton County. The Fulton County LiDAR Survey project area consists of approximately 690.5 square miles. The LiDAR point cloud was flown at a density sufficient to support a maximum final post spacing of 5 meters for unobscured areas. 3001 Inc. acquired 75 flightlines between March 3, 2006 and March 6, 2006 and 120 flightlines were reflown between July 29, 2006 and August 4, 2006. The data was divided into 5000' by 5000' foot cells that serve as the tiling scheme. The Fulton County LiDAR Survey was collected under the guidance of a Professional Mapper/Surveyor. Original contact information: Contact Org: Ayres Associates Phone: 608-443-1200 |
* Purpose |
The Fulton County LiDAR Survey data will support the creation of Federal Emergency Management Agency Flood Insurance Rate Maps (FEMA FIRM) and an integrated ground and surface water model. The Fulton County LiDAR Survey was collected under the guidance of a Licensed and Professional Surveyor/Mapper. |
Notes |
10369 |
Other Citation Details | |
• Supplemental Information |
The metadata are not complete if the format is not compatible with ArcGIS 9, if it is not FDGC Compliant, and if copies of the survey report in PDF format are not delivered as an attachment. The information in this report are the result of the LiDAR surveys performed on the dates indicated and the general conditions at the time. A footprint of this data may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2526/supplemental/ga2006_fultoncounty.KMZ A LiDAR Report from the vendor for this data set may be viewed here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2526/supplemental/FultonCountyGA_QAreport.pdf |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
None | TIN |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Fulton County | Carroll County |
Fulton County | City of Atlanta |
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 | None Planned |
Maintenance Note | |
» Data Presentation Form | |
• Entity Attribute Overview | |
Entity Attribute Detail Citation | |
Entity Attribute Detail URL | |
Distribution Liability |
Any conclusions drawn from the analysis of this information are not the responsibility of the Fulton County Public Works Department, Ayres Associates, USGS, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2013-08-12 |
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-08-12 |
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-08-12 |
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-08-12 |
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 | -84.86636 |
---|---|
* » E° Bound | -84.089227 |
* » N° Bound | 34.192198 |
* » S° Bound | 33.489459 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2006-03-03 |
End | 2006-03-06 |
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 The data set is dynamically generated based on user-specified parameters. ; |
• » Data Access Constraints |
None |
• Data Use Constraints |
These unaltered data may not be redistributed without all of the elements of the metadata listed in the Supplemental Information section of this metadata document. Acknowledgement of Ayres Associates would be appreciated in products derived from these data. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2526 |
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/2526/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 | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2526/supplemental/ga2006_fultoncounty.KMZ |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage for the topography of Fulton County LiDAR survey area in Georgia. |
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 | 2016-05-23 |
---|---|
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 |
Stream shore lines and 3-D coordinate line strings were collected as breaklines using LiDAR that was acquired and processed to FEMA specifications. These breaklines were created from on-screen digitizing using a combination of the LiDAR points and the orthophotography. Attributes were verified using routines that verify the vertical and horizontal positions of the breaklines. |
Analytical Accuracy | |
Horizontal Positional Accuracy |
All ground control processing and adjustments are performed using published coordinate horizontal and vertical datums (e.g. NGS CORS). For deliverables, Corpscon for Windows Version 5.11.08 (geoid 99) has been used for horizontal and vertical datum conversion as well as for coordinate system conversion purposes (e.g. UTM to State Plane).; Quantitative Value: 3.3 meters, Test that produced the value: This value is computed by comparing ground control to an intensity based image derived from the classified LiDAR data and represents the RMSE of residuals on controls within the project area. |
Vertical Positional Accuracy |
The accuracy assessment was performed using a standard method to compute the root mean square error (RMSE) based on a comparison of ground control points (GCP) and filtered LiDAR data points. Filtered LiDAR data has had vegetation and cultural features removed and by analysis represents bare earth elevations. Testing was performed prior to gridding of the filtered LiDAR data points and construction of the Intergraph .dtm file format. The RMSE figure was used to compute the vertical National Standard for Spatial Data Accuracy (NSSDA). Ground control was established by 3001, Inc. A spatial proximity analysis was used to select edited LiDAR data points contiguous to the relevant GCPs. A search radius decision rule is applied with consideration of terrain complexity, cumulative error and adequate sample size. Cumulative error results from the errors inherent in the various sources of horizontal measurement. These sources include the airborne GPS, GCPs and the uncertainty of the accuracy of the LiDAR data points. This accuracy is achieved prior to the sub-sampling that occurs through integration with the inertial measurement unit (IMU) positions that are recorded. It is unclear at this time whether the initial accuracy is maintained. The horizontal accuracy of the GCPs is estimated to be in the range of approximately 1 to 1.6 inches. Finally, sample size was considered. The specification for the National Standard for Spatial Data Accuracy is a minimum of 20 points to conduct a statistically significant accuracy evaluation (Minnesota Planning, 1999, Positional Accuracy Handbook, Minnesota Planning Land Management Information Center, St. Paul, Minnesota., p.3). Most statistical texts indicate that a minimum of 30 sample points provide a reasonable Approximation of a normal distribution. The intent of the NSSDA is to reflect the geographic area of interest and the distribution of error in the data set (Federal Geographic Data Committee, 1998, Geospatial National Standard for Spatial Data Accuracy, Federal Geographic Data Committee Secretariat, Reston, Virginia, p.3-4). Additional steps were taken to ensure the vertical accuracy Of the LiDAR data including: Step 1: Precision Bore sighting (Check Edge-matching) Step 2: Compare the LiDAR data to the Field Survey (Field survey is to FEMA specifications and more stringent internal specifications) Step 3: Automated Filtering Step 4: Manual Editing (Quality Control) Step 5: 3-D digitizing and Photogrammetric Compilation of hydrographic breaklines.; Quantitative Value: 0.0579 meters, Test that produced the value: This value is computed by comparing ground control elevation to the classified LiDAR ground surface and represents the RMSE of residuals on controls within the project area. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
The LAS files were flown at a density sufficient to support a maximum final post spacing of 5 meters for unobscured areas. The bare-earth surface will contain voids in areas that were densely vegetated, covered by bridges, buildings, water, fresh asphalt, sand etc. |
Conceptual Consistency |
The LAS files were flown at a density sufficient to support a maximum final post spacing of 5 meters for unobscured areas. 3001 Inc. acquired 75 flightlines between March 3, 2006 and March 6, 2006 and 120 flightlines were reflown between July 29, 2006 and August 4, 2006. The data was divided into 5000' by 5000' foot cells that serve as the tiling scheme. The Fulton County LiDAR Survey was collected under the guidance of a Professional Mapper/Surveyor. |
» 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 | Fulton County LiDAR Survey |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | 2010-01-01 |
Extent Type | Range |
Extent Start Date/Time | 2010-03-29 |
Extent End Date/Time | 2010-04-02 |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
The Fulton County LiDAR Survey was acquired and processed by Ayres Associates and 3001, Inc. | Source Geospatial Form: Remote sensing image | Type of Source Media: digital tape media |
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 |
The ABGPS, IMU, and raw scans are integrated using proprietary software developed by the Leica Geosystems and delivered with the Leica ALS50 System. The resultant file is in a LAS binary file format. The LAS file version 1.0 format can be easily transferred from one file format to another. It is a binary file format that maintains information specific to the LiDAR data (return#, intensity value, xyz, etc.). The resultant points are produced in the State Plane Georgia West (FIPS 1002) coordinate system, with units in feet and referenced to the NAD83 horizontal datum and NAVD88 vertical datum. Fulton County LiDAR Point Cloud data sets LAS 1.0 file format. The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters are applied as appropriate for the production of bare earth digital terrain models (DTMs). Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. Filtered and edited data are subjected to rigorous QA/QC. Very briefly, a series of quantitative and visual procedures are employed to validate the accuracy and consistency of the filtered and edited data. Ground control is established by 3001, Inc. and GPS-derived ground control points (GCPs) points in various areas of dominant and prescribed land cover. These points are coded according to landcover, surface material and ground control suitability. A suitable number of points are selected for calculation of a statistically significant accuracy assessment as per the requirements of the National Standard for Spatial Data Accuracy. A spatial proximity analysis is used to select edited LiDAR data points within a specified distance of the relevant GCPs. A search radius decision rule is applied with consideration of terrain complexity, cumulative error and adequate sample size. Accuracy validation and evaluation is accomplished using proprietary software to apply relevant statistical routines for calculation of Root Mean Square Error (RMSE) and the National Standard for Spatial Data Accuracy (NSSDA) according to Federal Geographic Data Committee (FGDC) specifications. The LiDAR mass points were delivered in American Society for Photogrammetry and Remote Sensing LAS 1.0 format. The header file for each dataset is complete as define by the LAS 1.0 specification. In addition the following fields are included: Flight Date Julian, Year, and Class. The LAS files do not include overlap. The data was classified as follows: Class 1 = Unclassified. This class includes vegetation, buildings, noise etc. Class 1 = Unclassified, Class 2 = Ground. The datasets were delivered in Fulton County's standard 5000' by 5000' tiling scheme. The tiles are contiguous and do not overlap. The tiles are suitable for seamless topographic data mosaics that include no "no data" areas. The names of the tiles are left padded with zeros as required to achieve a five character length and all files utilize the LAS file extension. |
Process Date/Time | 2010-04-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» 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 GA State Plane coordinates and NAVD88 (orthometric) heights in feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from GA State Plane coordinates to geographic coordinates. 2. The data were filtered to remove outliers below 660 and 2050 feet. 3. The data were converted from NAVD88 (orthometric) heights in feet to GRS80 (ellipsoid) heights in meters using Geoid 03. 4. Attempts were made to find the water class (9) though data received had water reclassed to unclassed along with a number of ground points, therefore processing to pull out only water classes were thwarted. 5. The LAS data were sorted by latitude and the headers were updated. |
Process Date/Time | 2012-08-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 | 49724 |
---|---|
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 |
---|