2013 NOAA Topographic Lidar: US Virgin Islands Digital Elevation Models (DEMs)
Office for Coastal Management
Data Set
(DS)
| ID: 48382
| Published / External
Created: 2017-11-14
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 47844
ID: 48382
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2013 NOAA Topographic Lidar: US Virgin Islands Digital Elevation Models (DEMs) |
---|---|
Short Name | usvi2013_stc_stj_stt_m3669_dem_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2014-08-29 |
* » Abstract |
The United States Virgin Islands Topographic LiDAR Task Order involved collecting and delivering topographic elevation point data derived from multiple return light detection and ranging (LiDAR) measurements on the islands of St. Thomas, St. John, St. Croix and numerous smaller islands and islets in the United States Virgin Islands. The data collected for the project area will exhibit Hydro Flattened DEMs (1m resolution) for inclusion into the NED. The purpose of the data is for use in coastal management decision making, including applications such as flood plain mapping and water rights management. LiDAR was collected at an average of 0.7 meter point spacing for all acquired project areas. Overall the DEMs were acceptable, but appear oversampled as a result of low ground point density (heavy vegetation), and is not a contractor issue as a 1 m DEM was specified. Incremental improvements to the DEMs were earned through breakline adjustments. Another characteristic of the USVI lidar data that was observed on all islands is the appearance of divots where there is a single tree or a narrow line of trees that lie in areas of open, bare terrain. The cause appeared to be sub-canopy points that were lower than the surrounding land. In most cases these low points were lower than the true ground surface at those locations, but were classified as ground and retained in the point cloud for use in DEM generation. This issue was not addressed during revisions. |
* Purpose |
Raster DEM files are used to show the Digital Elevation Model of the LAS Class 2 points. Breaklines can be incorporated into the DEM to show a more representative surface. |
Notes |
11401 |
Other Citation Details | |
• Supplemental Information | |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > TOPOGRAPHICAL RELIEF MAPS |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION |
ISO 19115 Topic Category | elevation |
None | DEM |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords | OCEAN > ATLANTIC OCEAN > NORTH ATLANTIC OCEAN > CARIBBEAN SEA > VIRGIN ISLANDS |
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 | Unknown |
Maintenance Note | |
» Data Presentation Form | Model |
• Entity Attribute Overview |
ERDAS .IMG files with a 1 meter pixel. No Data values outside of the project area are represented with -3.4028235e+038. |
Entity Attribute Detail Citation |
All deliverables meet specifications in contract. LAS Files meet ASPRS Classification Standards. |
Entity Attribute Detail URL | |
Distribution Liability |
Any conclusions drawn from the analysis of this information are not the responsibility of the PhotoScience, the Office for Coastal Management, or its partners. |
Data Set Credit | Precision Aerial Reconnaissance, LLC. acquired the LiDAR for the entire project area. Photo Science performed all LiDAR post-processing and created all required deliverables for the project. |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2014-08-29 |
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 | 2014-08-29 |
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 | 2014-08-29 |
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 | 2014-08-29 |
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 | -65.093469 |
---|---|
* » E° Bound | -64.561957 |
* » N° Bound | 18.423828 |
* » S° Bound | 17.670388 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2013-11-09 |
End | 2013-12-10 |
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? | Yes |
---|---|
Vector Representation Used? | |
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
* » 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 ; |
• » Data Access Constraints |
None |
• Data Use Constraints |
None. However, users should be aware that temporal changes may have occurred since this data set was collected and that some parts of the data may no longer represent actual surface conditions. Users should not use the data for critical applications without a full awareness of its limitations. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8390 |
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 | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/htdata/raster2/elevation/NOAA_USVI_DEM_2013_8390 |
Distributor | |
File Name | Bulk Download |
Description |
Simple download of data files. |
File Date/Time | |
File 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 |
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 |
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-09-26 |
---|---|
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 |
MicroStation Version 8; TerraScan Version 14; TerraModeler Version 14; GeoCue Version 2013.1.45.1; ESRI ArcGIS 10.1; Global Mapper Version 15.2; ALS Post Processor Version 2.75 Build #25; Windows 7 Operating System |
---|
Data Quality
Representativeness | |
---|---|
Accuracy |
The project area requires LiDAR to be collected on average of 0.7 meter point spacing or better and vertical accuracy of 9.25 centimeters RMSE or better to support 1' contour generation when combined with breaklines. |
Analytical Accuracy | |
Horizontal Positional Accuracy |
There is no assessment of the accuracy of the DEMs. However, the horizontal accuracy of the lidar that was collected and used to help create the DEMs was determined. The LiDAR data was compiled to meet a 1 meter horizontal accuracy. The calibration of the LiDAR sensor itself and the calibration process of the data produced by this sensor ensure that this accuracy is met.; Quantitative Value: 1.0 meters, Test that produced the value: Value stated in meters |
Vertical Positional Accuracy |
There is no assessment of the accuracy of the DEMs. However, the vertical accuracy of the lidar that was collected and used to help create the DEMs was determined. NOAA OCM conducted the vertical accuracy assessment for this data set. Eighty ground control points were collected on all three islands. The following are the number of points collected per island: St. Croix (31), St. John (19), St. Thomas (30). The accuracy specification called for a 9.25 cm Root Mean Square Error (RMSE) for all the islands. St. John and St. Thomas met this specification, however, St. Croix did not. The RMSE values for each island are as follows: St. Croix (14 cm), St. John (7 cm), St. Thomas (8 cm). The all islands RMSE value is 11 cm. The Quality Assurance Review Report may be viewed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12a/3669/supplemental/usvi2013_stc_stj_stt_m3669_qa_report.pdf The Check Point Survey Report may be viewed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12a/3669/supplemental/usvi2013_stc_stj_stt_m3669_chk_pnt_report.pdf ; Quantitative Value: 0.11 meters, Test that produced the value: RMSE in meters of classified LiDAR |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
Datasets contain complete coverage of tiles. |
Conceptual Consistency |
Bare-earth DEMs were tested by Photo Science, Inc. for vertical accuracy. All data are seamless from one tile to the next, no gaps or no data areas. |
» 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 | LiDAR |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | 2014-01-01 |
Extent Type | Range |
Extent Start Date/Time | 2013-11-09 |
Extent End Date/Time | 2013-12-10 |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
LiDAR points were used to produce the deliverables. | Source Geospatial Form: digital data | Type of Source Media: Hard Drive |
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 |
Applanix + POSPac Mobile Mapping Suite software was used for post-processing of airborne GPS and inertial data (IMU), which is critical to the positioning and orientation of the LiDAR sensor during all flights. POSPac combines aircraft raw trajectory data with stationary GPS base station data yielding a "Smoothed Best Estimate Trajectory (SBET) necessary for additional post processing software to develop the resulting geo-referenced point cloud from the LiDAR missions. During the sensor trajectory processing (combining GPS and IMU datasets) certain statistical graphs and tables are generated within the Applanix POSPac processing environment which are commonly used as indicators of processing stability and accuracy. This data for analysis include: Max horizontal / vertical GPS variance, separation plot, altitude plot, PDOP plot, base station baseline length, processing mode, number of satellite vehicles, and mission trajectory. The generated point cloud is the mathematical three dimensional composite of all returns from all laser pulses as determined from the aerial mission. Point clouds were created using the Leica ALS Post Processor software. Laser point data are imported into TerraScan and a manual calibration is performed to assess the system offsets for pitch, roll, heading and scale. 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. GeoCue distributive processing software was used in the creation of some files needed in downstream processing, as well as in the tiling of the dataset into more manageable file sizes. |
Process Date/Time | 2013-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
TerraScan and TerraModeler software packages were used for the automated data classification, manual cleanup, and bare earth generation. Project specific macros were developed to classify the ground and remove side overlap between parallel flight lines. The classes used in the dataset are as follows and have the following descriptions:
Class 1 - Processed, but Unclassified - These points would be the catch all for points that do not fit any of the other deliverable classes. This would cover things like vegetation, buildings, cars, bridges, etc. Class 2 - Bare earth ground - This is the bare earth surface Class 7 - Noise - Low or high points, manually and/or automatically identified above or below the surface that could be noise points in point cloud. Class 9 - Water - Points found inside of inland lake/ponds, rivers or points on the ocean side of any shoreline feature. Class 10 - Ignored Ground - Points found to be close to breakline features. Points are typically moved to this class from Class 2. This class is ignored during the DEM creation. Class 17 - Overlap Default (Unclassified) - Points found in the overlap between flight lines. These points are created through automated processing methods and are not cleaned up during manual classification. Class 18 - Overlap Bare-earth ground - Points found in the overlap between flight lines. These points are created through automated processing, matching the specifications determined during the automated process, that are close to the Class 2 dataset (when analyzed using height from ground analysis) Class 25 - Overlap Water - Points found in the overlap between flight lines that are located inside hydro features. These points are created through automated processing methods and are not cleaned up during manual classification.
All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified to Class 17 (Overlap Default) and Class 18 (Overlap Ground). These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages.
The bare earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare earth surface is finalized; it is then used to generate all hydro-breaklines through heads-up digitization.
Class 2 LIDAR was used to create a bare earth surface model. The surface model and LAS intensity were then used to heads-up digitize 2D breaklines of inland streams and rivers as well as the ocean shoreline. Inland Ponds and Lakes of 2 acres or greater were also collected.
Elevation values were assigned to all Inland Ponds and Lakes using TerraModeler functionality.
Elevation values were assigned to all Inland Streams and Rivers using Photo Science proprietary software.
Elevation values were assigned to all Coastal Shoreline features using TerraModeler functionality. Z values for the shorelines were assigned based on tidal conditions at the time of acquisition.
All ground (ASPRS Class 2) LiDAR data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 1 meter was also used around each hydro flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 10). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed.
LAS data was then run throu |
Process Date/Time | 2014-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
NOAA OCM received the Digital Elevation Models (DEMs) along with the las points and the hydro-flattened breaklines. Overall the DEMs were acceptable, but appear oversampled as a result of low ground point density (heavy vegetation), and is not a contractor issue as a 1 m DEM was specified. Incremental improvements to the DEMs were earned through breakline adjustments. Another characteristic of the USVI lidar data that was observed on all islands is the appearance of divots where there is a single tree or a narrow line of trees that lie in areas of open, bare terrain. The cause appeared to be sub-canopy points that were lower than the surrounding land. In most cases these low points were lower than the true ground surface at those locations, but were classified as ground and retained in the point cloud for use in DEM generation. This issue was not addressed during revisions. For further information, the QA Review Report may be accessed here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12a/3669/supplemental/usvi2013_stc_stj_stt_m3669_qa_report.pdf |
Process Date/Time | 2014-01-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 | 48382 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-14 14:43+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 | OCM |
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 |
---|