Wayne and Washtenaw Counties 1.0 PPSM LiDAR
OCM Partners
Data Set
(DS)
| ID: 49798
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49798
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | Wayne and Washtenaw Counties 1.0 PPSM LiDAR |
---|---|
Short Name | mi2009_usgs_wayne_washtenaw_m4809_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2015-02-09 |
* » Abstract |
TASK NAME: Wayne and Washtenaw Counties 1.0 PPSM LiDAR LiDAR Data Acquisition and Processing Production Task USGS CONTRACT: 07CRCN0006 TASK ORDER NUMBER: G09PD00300 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. This data was collected at a resolution of one point per square meter. The final products include reflective surface, first, last, and at least one intermediate return, a bare earth model, and intensity data in separate files. The reflective surface data represents the DEM created by the laser energy reflected from the first surface encountered by the laser pulse. Some energy may continue beyond this initial surface, to be reflected by a subsequent surface as represented by the last return data. Intensity information is captured from the reflective surface pulse and indicates the relative energy returned to the sensor, as compared to the energy transmitted. The intensity image is not calibrated or normalized but indicates differences in energy absorption due to the the interaction of the surface materials with laser energy, at the wavelength transmitted by the sensor. The bare earth model is created by identifying the returns that fall on the ground surface and by interpolating a surface between these points. In this manner, buildings and vegetation are removed from the bare earth model. This data set does not include bridges and overpasses in the bare earth model as the delineation point for these structures is not reliably discernible in the LiDAR data. |
* Purpose |
This task order consisted of LiDAR data acquisition and processing for Wayne and Washtenaw Counties in southeastern Michigan. The task order area of interest encompasses approximately 1324 square miles. The task required the LiDAR data to be collected at a minimum of one (1) point per square meter (1.0 meter GSD). The LiDAR data was collected to meet a vertical accuracy requirement of 18.0 cm (0.59 ft) RMSE, or better, so that when combined with breaklines, the data adequately supports the generation of two (2) foot FEMA compliant contours. The final LiDAR data was delivered as 5,000' x 5,000' tiles, aligned to even 5,000' coordinates. The LAS files are comprised of the full class data. |
Notes |
10442 |
Other Citation Details | |
• Supplemental Information |
Reports for this project are available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4809/supplemental/mi2009_usgs_wayne_washtenaw_m4809_surveyreport.pdf https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4809/supplemental/mi2009_usgs_wayne_m4809_surveyreport.pdf A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4809/supplemental/mi2009_usgs_wayne_washtenaw_m4809.kmz |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
None | Ground |
None | Terrain |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Michigan | Wayne and Washtenaw County |
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 |
LAS 1.2 format (classes 1,2,8,9,12) |
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-02-09 |
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-02-09 |
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-02-09 |
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-02-09 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference | Ground Condition |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -84.158227 |
---|---|
* » E° Bound | -82.859494 |
* » N° Bound | 42.473937 |
* » S° Bound | 42.011439 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Discrete |
---|---|
* » Start | 2009-04-16 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 2
* » Time Frame Type | Discrete |
---|---|
* » Start | 2009-04-17 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 3
* » Time Frame Type | Discrete |
---|---|
* » Start | 2009-04-18 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 4
* » Time Frame Type | Discrete |
---|---|
* » Start | 2009-04-23 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 5
* » Time Frame Type | Discrete |
---|---|
* » Start | 2009-04-24 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 6
* » Time Frame Type | Discrete |
---|---|
* » Start | 2009-05-03 |
End | |
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=4809 The 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. 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=4809 |
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/4809/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 | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4809/supplemental/mi2009_usgs_wayne_washtenaw_m4809.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage for the 2009 USGS lidar collection of Wayne and Washtenaw Counties, Michigan. |
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 |
The LiDAR collected for this task order was collected at a vertical accuracy of 18.0 cm (0.59 ft) Root Mean Squared (RMSE), or better, so that when combined with breaklines, it will adequately support the generation of two (2) foot FEMA compliant contours. | Quantitative Value: 18.0 cm (0.59 ft) RMSE | Quantitative Test Explanation: Points measured will produce an error less than 18.0 cm (0.59 ft) RMSE. |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Horizontal accuracy is +/- 1.158 meters at the 95% confidence level using RMSE(r) x 1.7308 as defined by the FGDC Geospatial Positional Accuracy Standards, Part 3: NSSDA.; Quantitative Value: 0.669 meters, Test that produced the value: 66.9 cm RMSE |
Vertical Positional Accuracy |
The LiDAR data vertical accuracy RMSE is 8.84 cm. The data collected under this Task Order meets the National Standard for Spatial Database Accuracy (NSSDA) accuracy standards. The NSSDA standards specify that vertical accuracy be reported at the 95 percent confidence level for data tested by an independent source of higher accuracy. (http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part3/index_html). The Fundamental Vertical Accuracy (FVA) of the TIN: 36.3 cm (1.19 ft) at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 18.5 cm in the "open terrain" land cover category. This data set tested to 0.56 ft. The Supplemental Vertical Accuracy (SVA) of the TIN: 36.3 cm (1.19 ft) at a 95% confidence level, derived according to American Society for Photogrammetry and Remote Sensing (ASPRS) Guidelines, Vertical Accuracy Reporting for LiDAR Data, i.e., based on the 95th percentile error in each of the individual other land cover categories. This criterion is a target value; larger errors in category could be offset by smaller errors in other categories so long as the overall consolidated vertical accuracy (CVA) is satisfied.This data set tested to 0.56 ft. for all categories. The Consolidated Vertical Accuracy (CVA): 36.3 cm (1.19 ft) at a 95% confidence level, derived according to ASPRS Guidelines, Vertical Accuracy Reporting for LiDAR Data, i.e., based on the 95th percentile error in all land cover categories combined. This data set tested to 0.56 ft. for all categories.; Quantitative Value: 0.0884 meters, Test that produced the value: 8.84 cm RMSEz |
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 a LH Systems ALS50 Light Detection And Ranging (LiDAR) system, 135 flight lines of high density data, one point per square meter, were collected over Wayne and Washtenaw Counties (approximately 1,324 square miles). Multiple returns were recorded for each laser pulse along with an intensity value for each return. A total of six missions were flown over an 18 day period: April 16, 2009 through May 3, 2009. A minimum of two airborne global positioning system (GPS) base stations were used in support of the LiDAR data acquisition. The mean baseline length was 28 miles, with a maximum baseline length of 52 miles. In addition, 31 ground control points were surveyed through static methods. The geoid used to reduce satellite derived elevations to orthometric heights was Geoid03. All data for the task order is referenced to Michigan State Plane South Zone (2113), NAD83/2007, NAVD88, in international feet. 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 last returns. Four layers of coverage were delivered in the ArcINFO ArcGrid binary format: reflective surface, bare-earth, last return and intensity. System Parameters: - Type of Scanner = LH Systems ALS50 - Data Acquisition Height = 7,000-feet AGL - Scanner Field of View = 14 degrees - Scan Frequency = 65.3 Hertz - Pulse Repetition Rate - 114.6 Kilohertz - Aircraft Speed = 120 Knots - Swath Width = 1,719-feet - Number of Returns Per Pulse = Maximum of 4 - Distance Between Flight Lines = 1,289-feet |
Process Date/Time | 2009-08-31 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
The ALS50 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 | 2009-08-31 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 | 2009-08-31 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 homogeneous 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), model keypoints (Class 8), overlap (Class 12) and unclassified 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 points are used to perform the accuracy checks and statistical analysis of the LiDAR dataset. |
Process Date/Time | 2009-08-31 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 5 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) received the files in laz format from USGS via an FTP online repository. The files contained lidar elevation and intensity measurements. The data were in State Plane MI 2113 South, NAVD88 (orthometric) international feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from State Plane coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights in international feet to GRS80 (ellipsoid) heights in meters using Geoid 03. 3. The LAS data were sorted by latitude and the headers were updated. 4. Erroneous elevations were removed. |
Process Date/Time | 2015-01-20 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 | 49798 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-15 15:22+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 |
---|