2015 FEMA Lidar: Marinette County, WI
OCM Partners
Data Set
(DS)
| ID: 58940
| Published / External
Created: 2020-02-27
|
Last Modified: 2023-12-07
Project (PRJ) | ID: 49401
ID: 58940
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2015 FEMA Lidar: Marinette County, WI |
---|---|
Short Name | FEMA_STARR_MarinetteCo_WI_Lidar |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2015-08-30 |
* » Abstract |
The collection area consists of 1,430 square miles, the entirety of Marinette County in Wisconsin.. Specifications listed below are based on FEMA Procedure Memorandum No. 61 Standards for LiDAR and Other High Quality Digital Topography. This collection specification is the equivalent of a 2 foot contour accuracy, and was collected with a nominal pulse spacing of 1.3 meters. The airborne GPS and IMU data were processed immediately following each mission. In addition, a sample of the LIDAR data was post-processed at the completion of each mission and the data was reviewed to ensure planned data quality and coverage. FEMA STARR Project number 4000000254. FEMA Task Order number is HSFE05-14-J-0037. |
* Purpose |
The STARR - Marinette County project is to provide high accuracy processed LiDAR data in Wisconsin. The project includes re-classification of previously collected LiDAR data to produce LAS files, contours, DTMs, DEMs and Breaklines for a 2 foot contour accuracy. The project consisted of acquisition, post-processing, and classification of LiDAR data. |
Notes | |
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 |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > BATHYMETRY/SEAFLOOR TOPOGRAPHY > BATHYMETRY > COASTAL BATHYMETRY |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION |
ISO 19115 Topic Category | elevation |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA |
Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > WISCONSIN |
Global Change Master Directory (GCMD) Location Keywords | VERTICAL LOCATION > LAND SURFACE |
Global Change Master Directory (GCMD) Location Keywords | VERTICAL LOCATION > SEA FLOOR |
Global Change Master Directory (GCMD) Location Keywords | Continent > North America > United States Of America > U.S. Coastline |
None | Continent > North America > United States Of America > Wisconsin > Marinette County |
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Instrument Keywords | LIDAR > Light Detection and Ranging |
Platform Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Platform Keywords | Airplane > Airplane |
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 | Elevation |
• Maintenance Frequency | Unknown |
Maintenance Note | |
» Data Presentation Form | Model (digital) |
• 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 NOAA, the Office for Coastal Management or its partners |
Data Set Credit | Continental Mapping Consultants |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2020 |
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 | 2020 |
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 | 2020 |
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 | 2020 |
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 | -88.454147 |
---|---|
* » E° Bound | -87.481796 |
* » N° Bound | 45.809515 |
* » S° Bound | 44.950953 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2015-04-15 |
End | 2015-04-24 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Lidar collection dates. |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | 0.5 |
Horizontal Distance Units | Meter |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
Spatial Representation
Grid Representation Used? | No |
---|---|
Vector Representation Used? | Yes |
Text / Table Representation Used? | No |
TIN Representation Used? | No |
Stereo Model Representation Used? | No |
Video Representation Used? | No |
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? | Yes |
Point Object Count | 15022067894 |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
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 |
Data is available online for bulk or custom downloads |
• » 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 | 2020-02-27 |
---|---|
End Date | Present |
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9033 |
Distributor | NOAA Office for Coastal Management (NOAA/OCM) (2020 - Present) |
File Name | Customized Download |
Description |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. |
File Date/Time | |
File Type (Deprecated) | Zip |
Distribution Format | |
File Size | |
Application Version | |
Compression | Zip |
Review Status |
Start Date | 2020-02-27 |
---|---|
End Date | Present |
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9033/index.html |
Distributor | NOAA Office for Coastal Management (NOAA/OCM) (2020 - Present) |
File Name | Bulk Download |
Description |
Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum. |
File Date/Time | |
File Type (Deprecated) | LAZ |
Distribution Format | LAS/LAZ - LASer |
File Size | |
Application Version | |
Compression | Zip |
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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9033/supplemental/extent_2015_marinette_m9033.kmz |
---|---|
Name | Browse graphic |
URL Type | Browse Graphic |
File Resource Format | KML |
Description |
This graphic displays the footprint for this lidar data set. |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9033/supplemental/55075C_Elevation_Data_QA_Report_for_Marinette_County_Wisconsin.pdf |
---|---|
Name | Dataset report |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to data set report. |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9033/supplemental/Control_Final_Report_Marinette_County.pdf |
---|---|
Name | Dataset report |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to data set report. |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9033/breaklines/index.html |
---|---|
Name | Breaklines |
URL Type | Online Resource |
File Resource Format | Zip |
Description |
Link to the breaklines. |
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 | |
---|---|
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 |
Processing Programs and versions- MicroStation (V8i Select Series 3 v8.11.09.4.459), TerraScan (15.002), TerraModeler (15.002), LP360 (2014.1.51.1) |
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy |
The Marinette County Project was acquired in seven (7) separate missions, flown as close together as the weather permitted, to ensure consistent ground conditions across the project area. The 1,430 square miles of data was acquired at 7,800 feet above ground level (AGL) and has a horizontal accuracy of 0.42 meters. Compiled to meet 0.42 meters horizontal accuracy at 95 percent confidence level. Quantitative value: 0.42m, Test that produced the valued: Lidar system specifications are available int he project report. |
Vertical Positional Accuracy |
CVA = 12.6 cm RMSE, tested with 57 independent ground survey points. Relative accuracy also known as "between swath" accuracy was tested through a series of well distributed flight line overlap locations. The relative accuracy for this site is tested at 0.162 survey feet RMSDz. |
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 void areas or missing data. |
Conceptual Consistency |
All formatted data cover the entire area specified for this project and are validated using a combination of commercial lidar processing software, GIS software, and proprietary programs to ensure proper formatting and loading prior to delivery. |
» Quality Control Procedures Employed |
Data Management
» Have Resources for Management of these Data Been Identified? | Yes |
---|---|
» Approximate Percentage of Budget for these Data Devoted to Data Management | Unknown |
» Do these Data Comply with the Data Access Directive? | Yes |
» 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 | NCEI-CO |
» 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? |
Data is backed up to tape and to cloud storage. |
Lineage
» Lineage Statement |
---|
Sources
Citation Title | Lidar |
---|---|
Contact Role Type | Originator |
Contact Type | Organization |
Contact Name | Continental Mapping Associates |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Source Contribution |
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 one Leica ALS70 (lidar) system on board a Cessna 310 aircraft, high density data, at a nominal pulse spacing (NPS) of 1.0 meter, were collected for this task order (approximately 1, square miles). AGL = 7800 feet - Aircraft Speed = 150 Knots, Field of View (Full) = 40 degrees, Pulse Rate = 230 kHz, Scan Rate = 34.4 Hz, with an average side lap of 25%. Multiple returns were recorded for each laser pulse along with an intensity value for each return. Seven (7) missions were flown between April 15, 2015 and April 24, 2015. One (1) Global Navigation Satellite System (GNSS) Base Station was used in support of the lidar data acquisition. Specific information regarding latitude, longitude, and ellipsoid height to the L1 phase center is included in the lidar processing report. The geoid used to reduce satellite derived elevations to orthometric heights was GEOID12A. Data for the task order is referenced to the UTM Zone 16N, North American Datum of 1983 (2011) meters, and NAVD88, in US Survey Feet. 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. The SBET was used to reduce the lidar slant range measurements to a raw reflective surface for each flight line. The ALS70 calibration and system performance is verified on a periodic basis using Woolpert's calibration range. The calibration range consists of a large building and runway. The edges of the building and control points along the runway have been located using conventional survey methods. Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position of the building edges between opposing flight lines. The scanner scale factor and vertical accuracy is calculated through comparison of lidar data against control points along the runway. 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 | 2015-04-15 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» 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 surveyed ground control points provided by Compass Data are used to make vertical adjustments to the data set and to perform the accuracy checks and statistical analysis of the lidar dataset. Supervisory QC monitoring of work ensured consistency of calibration and adjustments in adherence to project requirements across the entire project area. The resulting deliverables for this task order consist of unclassified LAS 1.2 files provided in a tiled format, fgdc metadata, and a post-flight aerial acquisition and calibration report. As part of this report, additional shape files were delivered and include flight line trajectories, planned flight lines, swath index, base station locations, tile index, and buffered AOI. |
Process Date/Time | 2015-04-16 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
Tile Size: 1,500m x 1,500m. The tile file name was derived from the southwest corner of each tile. |
Process Date/Time | 2014-04-30 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
Data was received in meters horizontally and US survey feet vertically. Automated macro to classify ground points, classify overlap, and apply multiplier to vertical values to convert to meters were run. Manual edits were conducted to ensure accurate classification of ground points and breaklines were digitized for any bodies of water and for any significant cliffs that were encountered. A macro was then run to classify water points within bodies of water and hydro polygons were draped and water bodies with flow were hydro-enforced to show downstream flow. Breaklines were collected over the entire project area along streams greater than 100ft in width and water bodies greater than2 acres in area. These breaklines were used to define water points and hydro-flatten the data. 3D Breaklines were collected at breaks in slope to support production of the 2-foot contours. Breaklines were collected in the full collection area (including the buffer area). Final macro was run to convert vertical values back to US Survey Feet and to assign points to delivery classes of: Class 1 – Default Class 2 – Ground Class 7 – Noise ?? Class 9 – Water (Including 1 meter buffer around hydro breaklines) Class 10 – Ignored Ground (including 1 meter buffer around terrain breaklines) Class 156 – Overlap/Withheld** **LP360 was used to apply withheld flag to overlap points that were initially classified to class 12. However, due to data being LAS version 1.2, the overlap flag is not included in the code structure of the files. Therefore, the withheld flag was applied and the points were reclassified to class 28. For an undetermined reason, when the points are subsequently viewed in TerraScan, the class for the withheld points is class 156 instead of class 28. However the withheld flag stayed intact. |
Process Date/Time | 2015-08-24 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 5 |
---|---|
» Description |
OCM retrieved 1,800 las files from WisconsinVIew. Data was received in UTM 16N NAD 83 (2011) meters horizontally and NAVD88 US survey feet vertically. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water, 10 - Ignored Ground, and 28 - Withheld. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 9, 10 and 12 - which were reclassified and still marked as withheld. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. The laszip program was used to convert the files to laz format. 2. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 3. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12A model, to convert from UTM 16N NAD83 (2011) coordinates in meters to geographic coordinates, to convert vertical units from feet to meters, to assign the geokeys, to sort the data by gps time, to change the point classification of 28 to 12, and zip the data to database and to http. |
Process Date/Time | |
Process Contact | Office for Coastal Management (OCM) |
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 | 58940 |
---|---|
Metadata Record Created By | Blake Waring |
Metadata Record Created | 2020-02-27 15:23+0000 |
Metadata Record Last Modified By | Rebecca Mataosky |
» Metadata Record Last Modified | 2023-12-07 21:44+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 |
---|