2012 USGS Lidar: Elwha River (WA)
OCM Partners
Data Set
(DS)
| ID: 50170
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 50170
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2012 USGS Lidar: Elwha River (WA) |
---|---|
Short Name | wa2012_usgs_elwha_river_m4955_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2015-09-16 |
* » Abstract |
TASK NAME: Elwha River, WA LiDAR LiDAR Data Acquisition and Processing Production Task USGS Contract No. G10PC00057 Task Order No. G11PD01088 Woolpert Order No. 71910 CONTRACTOR: Woolpert, Inc. LiDAR data is a remotely sensed high resolution elevation data collected by an airborne platform. The LiDAR sensor uses a combination of laser range finding, GPS positioning, and inertial measurement technologies. The LiDAR systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The task required the LiDAR data to be collected at a nominal pulse spacing (NPS) of 1.0 meter. The final products include first, last, and at least one intermediate return LAS, full classified LAS and one (1) meter pixel raster DEMs of the bare-earth surface in ERDAS IMG Format.The task order consisted of approximately thirty-five (35) square mile area along the Elwha River in Washington. This data will be used to assist the Department of Interior with the Elwha River Restoration Project following the removal of the Elwha Dam. The LiDAR data was acquired on October 10, 15, 16, and 17, 2012. |
* Purpose |
This task order consisted of LiDAR data acquisition and processing for the USGS. The task required the LiDAR data to be collected at a nominal pulse spacing (NPS) of 1.0 meter. The LiDAR data was collected to meet a vertical accuracy requirement of 18.2cm (0.6 ft) at the 95% confidence level. The LiDAR data was provided in 1,000 meters x 1,000 meters tiles in the UTM projection. The LiDAR tile file name was derived from the southwest corner of each tile. The tiles were named based on the US National Grid. The LAS tiles were only renamed to add the acquisition date to the beginning of the file and alter the end of the filename to a sequential naming convention. |
Notes |
10814 |
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/4955/supplemental/wa2012_usgs_elwha_river_m4955.kmz A final lidar report can be found here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4955/supplemental/wa2012_usgs_elwha_river_m4955_lidarreport.pdf An accuracy assessment for the project may be viewed here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4955/supplemental/wa2012_usgs_elwha_river_m4955_surveyreport.pdf |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
None | Elwha River Restoration Project |
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 format (ASPRS Classes 1,2,7,9,10,11) |
Entity Attribute Detail Citation |
none |
Entity Attribute Detail URL | |
Distribution Liability |
Any conclusions drawn from the analysis of this information are not the responsibility of Woolpert, USGS, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2015-09-16 |
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 | 2015-09-16 |
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 | 2015-09-16 |
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 | 2015-09-16 |
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 | -123.645513 |
---|---|
* » E° Bound | -123.398714 |
* » N° Bound | 48.1528493 |
* » S° Bound | 47.9318666 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2012-10-10 |
End | 2012-10-17 |
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=4955; |
• » 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=4955 |
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/4955/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 |
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 | 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 | |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Horizontal accuracy is listed as +/- 3.8-foot at the 95% confidence level in delivered (original) metadata though is reported in the lidar report that horizontal accuracy has a relative error estimation of between 1 cm and 2 cm.; Quantitative Value: 0.02 meters, Test that produced the value: See project report, link available in the supplemental information above. |
Vertical Positional Accuracy |
LAS data covering the Elwha River, Washington Lidar Task Order was compared to survey control points to determine the FVA of the LAS Swath and of the Bare-Earth DEM. In addition, this LAS data was compared to supplemental points from categories: Bare Earth Open Terrain, Tall Weeds/Crops, and Forested and Fully Grown. LAS Swath Fundamental Vertical Accuracy (FVA) Tested 0.152m (15.2cm) fundamental vertical accuracy at a 95 percent confidence level, derived according to NSSDA, in open terrain using 0.078m (7.8cm) (RMSE(z) x 1.96000 tested against the TIN. Bare-Earth DEM Fundamental Vertical Accuracy (FVA) Tested 0.162m (16.2cm) fundamental vertical accuracy at a 95 percent confidence level, derived according to NSSDA, in open terrain using 0.083m (8.3cm) (RMSE(z) x 1.96000 tested against the DEM.; Quantitative Value: 0.152 meters, Test that produced the value: LAS Swath Fundamental Vertical Accuracy (FVA) Tested 0.152 meters fundamental vertical accuracy at a 95 percent confidence level, derived according to NSSDA, in open terrain using RMSE(z) x 1.96000. This data set was tested against the TIN using independent check points.; Quantitative Value: 0.162 meters, Test that produced the value: Bare-Earth DEM Fundamental Vertical Accuracy (FVA) tested 0.162 meters fundamental vertical accuracy at a 95 percent confidence level, derived according to NSSDA, in open terrain using RMSE(z) x 1.96000. This data set was tested against the DEM using independent check points.; Quantitative Value: 0.143 meters, Test that produced the value: Bare Earth/Open Terrain Land Cover Classification Supplemental Vertical Accuracy (SVA) tested 0.143 meters supplemental vertical accuracy at the 95th percentile in Bare Earth/Open Terrain. Tested against the DEM. Errors larger than 95th percentile include: Point 106, Easting 455555.814, Northing 5322326.745, Z-Error 0.144 Point 116, Easting 459096.817, Northing 5331529.004, Z-Error 0.148; Quantitative Value: 0.291 meters, Test that produced the value: The Tall Weeds/Crops Land Cover Classification Supplemental Vertical Accuracy (SVA) tested 0.291 meters supplemental vertical accuracy at the 95th percentile in Tall Weeds/Crops. Tested against the DEM. Tall Weeds/Crops errors larger than 95th percentile include: Point 169, Easting 458866.554, Northing 5333118.706, Z-Error 0.293; Quantitative Value: 0.236 meters, Test that produced the value: The Forested and Fully Grown Land Cover Classification Supplemental Vertical Accuracy (SVA) tested 0.236 meters supplemental vertical accuracy at the 95th percentile in Forested and Fully Grown. Tested against the DEM. Forested and Fully Grown errors larger than 95th percentile include: Point 233, Easting 459936.682, Northing 5328485.045, Z-Error 0.239; Quantitative Value: 0.258 meters, Test that produced the value: The Consolidated Vertical Accuracy (CVA) tested 0.258 meters consolidated vertical accuracy at the 95th percentile level, derived according to ASPRS Guidelines for Vertical Accuracy Reporting for LiDAR Data. This data set was tested against the DEM using independent check points. Based on the 95th percentile error in all land cover categories combined. Combined Land Cover Errors larger than 95 percent include: Point 158, Easting 455941.88, Northing 5320597.031, Z-Error 0.263 Point 167, Easting 458742.638, Northing 5332568.325, Z-Error 0.266 Point 168, Easting 458751.388, Northing 5332562.195, Z-Error 0.291 Point 169, Easting 458866.554, Northing 5333118.706, Z-Error 0.293 Point 170, Easting 459282.631, Northing 5327659.036, Z-Error 0.340 |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
The LiDAR data is visually inspected for completeness to ensure that are no gaps between flight lines. |
Conceptual Consistency |
All formatted data are validated using commercial GIS software to ensure proper formatting and loading prior to delivery. |
» 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 |
Using Leica a ALS60 a (LiDAR) system, high density data, at a nominal pulse spacing (NPS) of 1.0 meter, were collected for the Elwha River Restoration Project area of interest (approximately 35 square miles). The LiDAR data was acquired at a height of 900 meters AGL. Multiple returns were recorded for each laser pulse along with an intensity value for each return. A total of four missions were flown during a period of Ocotber 10 , 2012 through Ocotber 17 , 2012. A single airborne global positioning system (GPS) base station was used in support of the LiDAR data acquisition. The ground control and land cover category QA/QC points were surveyed through static and RTK methods. The geoid used to reduce satellite derived elevations to orthometric heights was Geoid09. Data for the task order is referenced to the UTM Zone 10N, North American Datum of 1983 (NAD83), and NAVD88, in Meters. Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a smoothed best estimate of trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. The coverage was classified to extract a bare earth digital elevation model (DEM) and separate returns. In addition to the LAS deliverables, one layer of coverage was delivered in the IMG Format: bare-earth. |
Process Date/Time | 2012-10-17 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
The ALS60 calibration and system performance is verified on a periodic basis using a calibration range. Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position of of ground surveyed data, such as building edges, between opposing flight lines. The scanner scale factor and vertical accuracy is calculated through comparison of LiDAR data against control points. Field calibration is performed on all flight lines to refine the IMU misalignment angles. IMU misalignment angles are calculated from the relative displacement of features within the overlap region of adjacent (and opposing) flight lines. The raw LiDAR data is reduced using the refined misalignment angles. |
Process Date/Time | 2012-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
Once the data acquisition and GPS processing phases are complete, the LiDAR data was processed immediately to verify the coverage had no voids. The GPS and IMU data was post processed using differential and Kalman filter algorithms to derive a best estimate of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the project. |
Process Date/Time | 2012-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
The individual flight lines were inspected to ensure the systematic and residual errors have been identified and removed. Then, the flight lines were compared to adjacent flight lines for any mismatches to obtain a homogenous coverage throughout the project area. The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" LiDAR returns. This process determined bare-earth points (Class 2), Noise (Class 7), Water (Class 9) Ignored ground (Class 10), and default data (Class 1). The bare-earth (Class 2 - Ground) LiDAR points underwent a manual QA/QC step to verify that artifacts have been removed from the bare-earth surface. The surveyed ground control and land category QA/QC points are used to perform the accuracy checks and statistical analysis of the LiDAR dataset. |
Process Date/Time | 2013-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 classified LAZ format from USGS' ftp site. The data were received in UTM Zone 10N NAD83 coordinates (meters) and vertically referenced to NAVD88 meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. LAS files were compressed to LAZ format with LASTools. 2. LAS files were removed of any duplicated points and extraneous points were reclassified to noise. 3. The LAS files were transformed to geographic (decimal degrees) NAD83(2011) coordinates and ellipsoidal coordinates (meters) with respect to Geoid03. |
Process Date/Time | 2015-08-14 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 | 50170 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-15 15:24+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 |
---|