2009 - 2011 CA Coastal Conservancy Coastal Lidar Project: Hydro-flattened Bare Earth DEM
OCM Partners
Data Set
(DS)
| ID: 49415
| Published / External
Created: 2017-11-15
|
Last Modified: 2024-01-10
Project (PRJ) | ID: 49404
ID: 49415
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2009 - 2011 CA Coastal Conservancy Coastal Lidar Project: Hydro-flattened Bare Earth DEM |
---|---|
Short Name | ca2010_coastal_dem |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2012 |
* » Abstract |
Light Detection and Ranging (LiDAR) data is remotely sensed high-resolution elevation data collected by an airborne collection platform. This LiDAR dataset is a survey of Coastal California. The project area consists of approximately 2616 square miles. The project design of the LiDAR data acquisition was developed to support a nominal post spacing of 1 meter. Fugro EarthData, Inc. acquired 1546 flight lines in 108 lifts between October 2009 and August 2011. LiDAR data collection was performed with two Piper Navajo twin engine aircrafts, utilizing a Leica ALS60 MPiA sensor; collecting multiple return x, y, and z as well as intensity data. The bare-earth lidar data was used to create hydro-flattened DEMs (Digital Elevation Models) available for download from the NOAA OCM Digital Coast. Original contact information: Contact Org: NOAA Office for Coastal Management Phone: 843-740-1202 Email: coastal.info@noaa.gov |
* Purpose |
These digital data are intended to support the local coastal zone managers in their decision-making processes, including applications such as sea level rise. |
Notes |
12078 |
Other Citation Details | |
• Supplemental Information |
The information in this report is the result of LiDAR surveys performed on the date indicated and the general conditions at the time of flight. |
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 |
Keywords | Bare Earth |
Keywords | Bathymetry/Topography |
Keywords | DEM |
Keywords | Elevation |
Keywords | LiDAR |
Keywords | Model |
Keywords | Surface |
Keywords | Terrain |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > CALIFORNIA |
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 | |
• Entity Attribute Overview |
Leica ALS60 MPiA sensor; 1m nominal post spacing |
Entity Attribute Detail Citation |
see process steps within this record |
Entity Attribute Detail URL | |
Distribution Liability |
Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners. |
Data Set Credit | Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Office for Coastal Management (OCM); the California State Coastal Conservancy (SCC) Ocean Protection Council (OPC); Scripps Institution of Oceanography; and the Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX). |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2012 |
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 | 2012 |
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 | 2012 |
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 | 2012 |
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 | Publication Date |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -124.44374 |
---|---|
* » E° Bound | -116.267734 |
* » N° Bound | 42.012737 |
* » S° Bound | 32.521695 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2009-09 |
End | 2011-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? | |
---|---|
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 |
None |
Security Handling Description |
N/A |
• Data Access Policy | |
» Data Access Procedure |
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/ This data set is dynamically generated based on user-specified parameters. ; |
• » 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. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=1131 |
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.us-east-1.amazonaws.com/dem/California_Lidar_DEM_2009_1131/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 | 2016-07-14 |
---|---|
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-02-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 |
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.6.1500 |
---|
Data Quality
Representativeness | |
---|---|
Accuracy |
During LiDAR data collection the airborne GPS receiver was collecting data at 2 Hz frequency and the Dilution of Precision (PDOP) was monitored. One GPS base station was also running at the operation airport and was recording data at 1 Hz. The airborne GPS data was post-processed in DGPS mode together with the base station data to provide high accuracy aircraft positions. The GPS trajectory then was combined with the IMU data using loosely coupled approach to yield high accuracy aircraft positions and attitude angles. Then the LiDAR data was processed using the aircraft trajectory and raw LiDAR data. After boresighting the LiDAR data, the ground control points were measured against the LiDAR data by technicians using TerraScan and proprietary software and the LiDAR data was adjusted vertically to the ground control. Independent ground control check points were used to ensure vertical accuracy of the data. The horizontal datum for the control was the North American Datum of 1983 (NAD83, NSRS2007).The vertical datum was the North American Vertical Datum of 1988 (NAVD88). The vertical datum was realized through the use of the published/calculated ellipsoidal heights of the base station to process the aircraft trajectory and then later applying the GEOID09 model to the processed LiDAR data to obtain orthometric heights. |
Analytical Accuracy | |
Horizontal Positional Accuracy |
The minimum expected horizontal accuracy was tested to meet or exceed the National Standard for Spatial Data Accuracy (NSSDA). Horizontal accuracy is 50 cm RMSE or better. |
Vertical Positional Accuracy |
The minimum expected vertical accuracy was tested to meet or exceed the National Standard for Spatial Data Accuracy (NSSDA). When compared to GPS survey grade points in generally flat, non-vegetated areas, at least 95% of the positions had an error less than or equal to 9.4 cm (equivalent to root mean square error (rmse) of 4.8 cm if errors were normally distributed). |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure |
Cloud Cover: 0 |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
The following methods are used to ensure LiDAR data accuracy: 1) Use of a ground control network utilizing GPS survey techniques; 2) Use of airborne GPS and IMU in conjunction with the acquisition of LiDAR; and 3) Measurement of quality control ground survey points within the finished product. The following software is used for the validation: 1) Terrascan and 2) Fugro EarthData Proprietary Software. |
Conceptual Consistency |
Compliance with the accuracy standard was ensured by the collection of ground control and the establishment of a GPS base station at the operation airport. The following checks were performed: 1) The LiDAR data accuracy was validated by performing a full boresight adjustment and then checking it against the ground control prior to generating a digital terrain model (DTM) or other products. 2) LiDAR elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal). |
» 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 | Aerial Acquisition of Coastal California LiDAR |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | 2011-08-04 |
Extent Type | Range |
Extent Start Date/Time | 2009-10-15 |
Extent End Date/Time | 2011-08-02 |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
Fugro EarthData, Inc. collected ALS60-derived LiDAR over Coastal California with a 1 meter, nominal post spacing using two Piper Navajo twin engine aircrafts. The collection for the entire project area was accomplished between October 2009 and August 2011; 1,546 flight lines were acquired in 108 lifts. The lines were flown at an average of 6,244 feet above mean terrain using a pulse rate of 121,300 pulses per second. The collection was performed using Leica ALS60 MPiA LiDAR systems, serial numbers 113 and 142. | Type of Source Media: External hard drive |
Citation Title | Coastal California LiDAR; Classified LiDAR Point Cloud Data |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | 2011-10-20 |
Extent Type | Discrete |
Extent Start Date/Time | 2011-10-20 |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
Fugro EarthData, Inc. utilized commercial software as well as proprietary software for automatic filtering of LiDAR data to identify and re-classify elevation points falling on vegetation, building, and other above ground structures into separate data layers. The parameters used in the process were customized for each terrain type to obtain optimum results. Once the automated filtering was completed, the files were run through a visual inspection to ensure that the filtering was not too aggressive or not aggressive enough. In cases where the filtering was too aggressive and important terrain features were filtered out, the data was either run through a different filter or was corrected during the manual filtering process. Interactive editing was then completed in 3D visualization software which also provides manual and automatic point classification tools using commercial and proprietary software for the process. Vegetation and artifacts remaining after automatic data post-processing were reclassified manually through interactive editing. The hard edges of ground features that were automatically filtered out during the automatic filtering process were brought back into ground class during manual editing. The technician then reviewed the LiDAR points with color shaded TINs for anomalies in ground class during interactive filtering. Upon the completion of bare earth filtering and peer review process, the classified LiDAR point cloud work tiles went through a water classification routine based on the collected water polygons. Upon the completion of finalization of the classified LiDAR point cloud work tiles, the topographic LiDAR classified point cloud data that was produced under the JALBTCX and NOAA OCM programs was merged. The final classified LiDAR point data were packaged to NAD83 (NSRS2007), UTM zones 10 and 11 north, meters; NAVD88, meters, using GEOID09 and cut to the approved tile layout and project boundary in LAS format. | Type of Source Media: Internal net |
Citation Title | Report of Survey California Coast Ground Control for LiDAR |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | 2010-11-17 |
Extent Type | Range |
Extent Start Date/Time | 2009-09-25 |
Extent End Date/Time | 2010-10-21 |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
TerraSurv under contract to Fugro EarthData, Inc. successfully established ground control for Coastal California LiDAR. A total of 307 ground control points were acquired. GPS was used to establish the control network. The horizontal datum was the North American Datum of 1983 (NAD83, NSRS2007). The vertical datum was the North American Vertical Datum of 1988 (NAVD88). | Type of Source Media: electronic mail system |
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 hydro-enforced bare earth DEM was generated using the bare earth points, as well as the 3D hydro breaklines. The following is a step-by-step breakdown of the process: 1) After the deliverable LAS files were generated for the entire project area and QC'ed, and the 3D breaklines were collected and QC'ed, they were used to produce the hydro-enforced bare earth DEM. The bare earth points that fell within 1*NPS along the hydro breaklines were taken out of from Ground class so that these points were excluded from the DEM generation process. This process was done in batch mode using Fugro EarthData's proprietary software. 2) Inland ponds and lakes, inland streams and rivers, and tidal water bodies were hydro-flattened within the DEM. Hydro-flattening was applied to water impoundments, natural or man-made, larger than ~2 acres in area (inland ponds and lakes larger than 1 acre were collected for the 500 meter corridor); to streams nominally wider than 100' (inland streams and rivers wider than 15 meters were collected for the 500 meter corridor); and to tidal waters bodies, which includes any significant water body that is affected by tidal variations. 3) The hydro-flattened bare earth DEM generated in initial grid format was then clipped to the approved DEM product boundary. 4) After the hydro-flattened bare earth DEM was clipped to the boundary, the technician checked the tiles to ensure that the grid spacing met specifications and checked the surface to ensure proper hydro-flattening. The data was cut to the approved tile layout. The entire data set was checked for complete project coverage and to ensure it was free of anomalies. 5) The hydro-flattened bare earth DEM was then converted to the delivery ESRI Grid format. |
Process Date/Time | 2011-11-15 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source | Coastal California LiDAR; Classified LiDAR Point Cloud Data |
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 | 49415 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-15 15:13+0000 |
Metadata Record Last Modified By | Kirk Waters |
» Metadata Record Last Modified | 2024-01-10 18:52+0000 |
Metadata Record Published | 2024-01-10 |
Owner Org | OCMP |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2018-02-13 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2019-02-13 |
Tags |
---|