2001 USACE LRE Topobathy Lidar: Lake Ontario (NY)
OCM Partners
Data Set
(DS)
| ID: 49880
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49880
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2001 USACE LRE Topobathy Lidar: Lake Ontario (NY) |
---|---|
Short Name | ny2001_usace_loslrs_ontario_m4700_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2003-04-30 |
* » Abstract |
NOAA Office for Coastal Management received the 2001 Lake Ontario dataset with 2 separate metadata records in 2013 on a hard-drive device from the USGS Center for LiDAR Information Coordination and Knowledge (CLICK); the first record was for the topographic portion of the shoreline from the USACE Detroit Office collected in May of 2001 and a second stating the USACE JALBTCX SHOALS system as having collected the bathymetric points for these same areas in August of 2001. The collection dates and GPS times correspond to each having successfully collected and delivered their respective areas. This record is a combination of the two and will highlight sections from both in order to create a complete and complementary metadata record. The original metadata records will be available by request only. This data set is the raw topographic LIDAR data set. The data set contains selected base categories of geographic features, and characteristics of these features (X,Y,Z), in digital form. The X,Y represent geographic coordinates and the Z represents elevation in meters. The information was collected by EarthData International, LLC for the U.S. Army Corps of Engineers, Detroit District. This collection was done on the behalf of the Lake Ontario St. Lawrence River Study by the International Joint Commission. These data were collected by the SHOALS (Scanning Hydrographic Operational Airborne Lidar Survey) system which consists of an airborne laser transmitter/receiver capable of measuring 400 soundings per second. The system operates from a deHavilland DHC-6 Twin Otter flying at altitudes between 200 and 400 meters with a ground speed of about 100 knots. The SHOALS system also includes a ground-based data processing system for calculating accurate horizontal position and water depth. Lidar is an acronym for LIght Detection And Ranging. The system operates by emitting a pulse of light that travels from an airborne platform to the water surface where a small portion of the laser energy is backscattered to the airborne receiver. The remaining energy at the water's surface propagates through the water column and reflects off the sea bottom and back to the airborne detector. The time difference between the surface return and the bottom return corresponds to water depth. The maximum depth the system is able to sense is related to the complex interaction of radiance of bottom material, incident sun angle and intensity, and the type and quantity of organics or sediments in the water column. As a rule-of-thumb, the SHOALS system should be capable of sensing bottom to depths equal to two or three times the Secchi depth. |
* Purpose |
The purpose for the topographic collection of raw Topographic LIDAR, was to support coastal and water modeling of the Lake Ontario South Shore shoreline. This was conducted as part of a study by the Lake Ontario - St. Lawrence River Study by the International Joint Commission. The purpose of the bathymetric survey was to collect data from the shoreline to approximately -10m depths. The data will be used to build models of the Lake Ontario shoreline. |
Notes |
10524 |
Other Citation Details | |
• Supplemental Information |
A footprint of the entire dataset is available here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4700/supplemental/ny2001_usace_loslrs_ontario_m4700.kmz A footprint of the bathymetric data is available here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4700/supplemental/ny2001_usace_loslrs_ontario_m4700_bathy.kmz A report concerning the control points is available here: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4700/supplemental/ny2001_usace_loslrs_ontario_m4700_surveyreport.pdf |
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 |
---|---|
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 | None Planned |
Maintenance Note | |
» Data Presentation Form | |
• Entity Attribute Overview |
LiDAR points in LAZ format (Classes 1,2,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 LOSLR, GLC, USACE, JALBTCX, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2003-04-30 |
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 | 2003-04-30 |
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 | 2003-04-30 |
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 | 2003-04-30 |
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 | -78.289001 |
---|---|
* » E° Bound | -76.159606 |
* » N° Bound | 43.814086 |
* » S° Bound | 43.227111 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2001-05-09 |
End | 2001-08 |
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
* » 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=4700; |
• » Data Access Constraints |
None |
• Data Use Constraints |
These data depict the heights at the time of the survey and are only accurate for that time. Acknowledgment of the Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) would be appreciated in any publications or derived products. The data herein, including but not limited to geographic data, tabular data, analytical data, electronic data structures or files, are provided "as is" without warranty of any kind, either expressed or implied, or statutory, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the data is assumed by the user. No guarantee of accuracy is granted, nor is any responsibility for reliance thereon assumed. In no event shall the U.S. Army Corps of Engineers, Mobile District Office, Spatial Data Branch be liable for direct, indirect, incidental, consequential or special damages of any kind, including, but not limited to, loss of anticipated profits or benefits arising out of use of or reliance on the data. The Spatial Data Branch does not accept liability for any damages or misrepresentation caused by inaccuracies in the data or as a result of changes to the data caused by system transfers or other transformations or conversions, nor is there responsibility assumed to maintain the data in any manner or form. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4700 |
Distributor | |
File Name | Customized Download |
Description |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. |
File Date/Time | |
File Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4700/index.html |
Distributor | |
File Name | Bulk Download |
Description |
Simple download of data files. |
File Date/Time | |
File Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
URLs
URL | https://coast.noaa.gov/dataviewer |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://coast.noaa.gov |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4700/supplemental/ny2001_usace_loslrs_ontario_m4700.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage for the 2001 lidar project covering Lake Ontario, with bathymetric and topographic lidar in portions of New York. |
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 raw digital elevation model (DEM) was generated for the project area from the raw data. This raw DEM includes elevations for vegetation and buildings. The raw DEM was further processed to an even 4-m interval in both the latitude and longitude direction by "gridding" the data. The raw DEM was derived with an accuracy to support the generation of 0.6-m (2') contours at National Map Accuracy Standards (NMAS). SHOALS has demonstrated capabilities that meet US Army Corps of Engineers Hydrographic Survey accuracy requirements for Class 1 surveys and the International Hydrographic Organization nautical charting standards for Order 1. |
Analytical Accuracy | |
Horizontal Positional Accuracy |
One simultaneous adjustment was performed on the entire data set to ensure that all coordinates and adjustments were unique to one network.; Quantitative Value: 3 meters, Test that produced the value: +/- 3 meters (1 sigma) |
Vertical Positional Accuracy |
GPS and IMU data collection for the first mission began at 19:50 May 09, 2001 GMT and ended at 00:45 on May 10, 2001, GMT. The LIDAR data collection began at 20:45 GMT (334000 week second) and continued until 00:05 GMT (345900 week second). During that time there were no significant cycle slips in the data collected at the Genessee airport nor in the data collected onboard the aircraft. There were 2 data gaps in the data collected by Costage Engineering. However this did not significantly impact the differential solution. The aircraft did not travel more than 50 statute miles from either base station. During the LIDAR data collection the PDOP was less than 2.5 and the DDOP was less than 4. The phase differential solution from the data collected at the Genessee airport is a fixed integer solution. Ionospheric error modeling was selected in the post processing software for this data set. The "forward" and "reverse" solutions were compared to each other and are nearly identical. These 2 trajectory files were averaged together to yield the final solution (solution A). The phase differential solution from the data collected by Costage Engineering, located at the project site, is a "float" solution. This is due to the large distance from the Genessee airport to the project area at the time of GPS initialization. Ionospheric error modeling was selected in the post processing software for this data set. The forward and reverse solutions were compared to each other. The differences in the 2 solutions were well within acceptable tolerances. These two were averaged together to yield a single trajectory file (solution B). To determine the overall quality and accuracy of the GPS data collection and subsequent processing solutions A and B were compared to each other. The differences between these 2 trajectory files were well within acceptable tolerances. The small difference between these 2 solutions indicates that the GPS positioning of the aircraft is valid and exceeds the precision required for this project. The IMU data collection for the entire flight was continuous. The static initialization of the IMU was not less than 10 minutes. This is more than 3 times the minimum amount of time recommended by Applanix Corporation. The post processing of the IMU data indicates that the resulting Smoothed Best Estimate Trajectory (SBET) was free of anomalies and yielded the best position and orientation that the system can provide. Solution A was used with the IMU data for all subsequent LIDAR data processing for Area 1.; Quantitative Value: 0.15 meters, Test that produced the value: +/- 15 cm (1 sigma) |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
The raw LIDAR dataset required a substantial amount of editing since the project area was flown so late in the spring. Much of the vegetation had "leafed-out", so there were a number of areas where it was difficult to distinguish the low-lying vegetation from the surface of the ground. |
Conceptual Consistency |
Point topological relationships are collected or generated to satisfy topological requirements. Some of the requirements include populated X coordinate, Y coordinate, and Z coordinate values all with in NMAS. |
» 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 |
The aircraft was based at Genessee County airport located in Batavia, New York. During the first airborne mission on May 09 Area #1 was completeley collected. For the duration of the data collection there were 2 stationary GPS receivers in constant operation. One receiver was located at the Genessee county airport. The second GPS receiver was operated by Costage Engineering located in Rochester, New York. Both instruments collected GPS phase data at 1 Hz. for the duration of the mission. |
Process Date/Time | 2001-05-09 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
A second flight was executed on May 10, 2001. During this airborne mission Area #2 and Area #3 were completely collected. During the data collection there were 3 stationary GPS receivers in constant operation. One receiver was located at the Oswego County Airport, NY. A second receiver was located at the Williamson-Sodus Airport. The third receiver was located at the Genessee County airport. All 3 instruments collected GPS phase data at 1 Hz. for the duration of the mission. |
Process Date/Time | 2001-05-10 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
LIDAR data was collected at a flying height of 8,000't AMT (above mean terrain), at an average post-spacing of 4 m, at a laser pulse rate of 15 kHz, and with a field-of-view (FOV) of 40 degrees. The average swath width of the LIDAR flight lines was 5800'. Survey data also was collected over the project area to check the vertical accuracy of the LIDAR dataset. |
Process Date/Time | 2001-05-09 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
The SHOALS airborne system acquires a tremendous volume of raw data during a single mission. The lidar data are unique and require a specialized Data Processing System (DPS) for post-processing. The DPS main funcions 1) import airborne data stored on high density data tape; 2) perform quality control checks on initial depths and horizontal positions; 3) provide display and edit capabilities; 4) calculate depth and position (XYZ) values for each sounding; and 5) output final positions and depths for each sounding. |
Process Date/Time | 2001-08-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 5 |
---|---|
» Description |
Original reach-specific topographic LIDAR data were merged, checked for consistency, and packaged/compressed using the gzip compression utility. |
Process Date/Time | 2006-07-07 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 6 |
---|---|
» Description |
Original reach-specific bathymetric LIDAR data were merged, checked for consistency, and packaged/compressed using the gzip compression utility. |
Process Date/Time | 2006-07-10 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 7 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) received ASCII text files without classifications or complete attributes for each point. The data were received in UTM Zone 18 (meters) and referenced vertically to NAVD88 (meters) using the Geoid99 model in meters. Three separate areas arrived in OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. ASCII files were converted from to LAS files with LASTools (txt2las). 2. LAS files were removed of any duplicated points and extraneous points were reclassified to noise. 3. The LAS tiles were then processed to reclassify unclassified topographic points to ground using an existing shoreline footprint from NOAA. 4. The LAS tiles were then processed to reclassify unclassified to bathymetric points for all submerged, open water area points. Processing errors were caused by data uncertainties beyond the reasonable extent of bathymetric depths (for 2001) therefore these points were not reclassified to bathymetric points, class 11. 5. The LAS files were transformed to geographic (decimal degrees), ellipsoidal coordinates (meters) referenced to the Geoid12a model. |
Process Date/Time | 2015-07-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 49880 |
---|---|
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 |
---|