2012-2013 Post-Hurricane Sandy EAARL-B Submerged Topography - Barnegat Bay, New Jersey
OCM Partners
Data Set
(DS)
| ID: 49861
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49861
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2012-2013 Post-Hurricane Sandy EAARL-B Submerged Topography - Barnegat Bay, New Jersey |
---|---|
Short Name | nj2012_usgs_barnegatbay_m4730_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2014 |
* » Abstract |
Binary point-cloud data for part of Barnegat Bay, New Jersey, post-Hurricane Sandy (October 2012 hurricane), were produced from remotely sensed, geographically referenced elevation measurements by the U.S. Geological Survey. Elevation measurements were collected over the area using the second-generation Experimental Advanced Airborne Research Lidar, a pulsed laser ranging system mounted onboard an aircraft to measure ground elevation, vegetation canopy, and coastal topography. The system uses high-frequency laser beams directed at the Earth's surface through an opening in the bottom of the aircraft's fuselage. The laser system records the time difference between emission of the laser beam and the reception of the reflected laser signal in the aircraft. The plane travels over the target area at approximately 55 meters per second at an elevation of approximately 300 meters, resulting in a laser swath of approximately 240 meters with an average point spacing of 0.5-1.6 meters. The nominal vertical elevation accuracy expressed as the root mean square error (RMSE) is 25 centimeters. A peak sampling rate of 15-30 kilohertz results in an extremely dense spatial elevation dataset. More than 100 kilometers of coastline can be surveyed easily within a 3- to 4-hour mission. When resultant elevation maps for an area are analyzed, they provide a useful tool to make management decisions regarding land development. |
* Purpose |
The purpose of this project was to produce highly detailed and accurate digital elevation maps for part of Barnegat Bay, New Jersey, post-Hurricane Sandy (October 2012 hurricane), for use as a management tool and to make these data available to natural-resource managers and research scientists. |
Notes |
10505 |
Other Citation Details | |
• Supplemental Information |
Raw lidar data are not in a format that is generally usable by natural-resource managers and research scientists for scientific analysis. Converting dense lidar elevation data into a readily usable format without loss of essential information requires specialized processing. The U.S. Geological Survey's Coastal and Marine Geology Program (CMGP) has developed custom software to convert raw lidar data into a GIS-compatible map product to be provided to GIS specialists, managers, and scientists. The primary tool used in the conversion process is Airborne Lidar Processing System (ALPS), a multitiered processing system developed originally by a USGS-NASA collaborative project. Specialized processing algorithms are used to convert raw waveform lidar data acquired by the EAARL-B to georeferenced spot (x,y,z) returns for "first surface" and "bare earth" topography. The terms first surface and bare earth refer to the digital elevation data of the terrain, but although first-surface data include vegetation, buildings, and other manmade structures, bare-earth data do not. The zero crossing of the second derivative (that is, detection of stationary points) is used to detect the first return, resulting in "first surface" topography, whereas the trailing edge algorithm (that is, the algorithm searches for the location before the last return where direction changes along the trailing edge) is used to detect the range to the last return, or "bare earth" (the first and last returns being the first and last significant measurable part of the return pulse). Statistical filtering, known as the Random Consensus Filter (RCF), is used to remove false bottom returns and other outliers from the EAARL-B topography data. The filter uses a grid of non-overlapping square cells (buffer) of user-defined size overlaid onto the original point cloud. The user also defines the vertical tolerance (vertical width) based on the topographic complexity and point-sampling density of the data. The maximum allowable elevation range within a cell is established by this vertical tolerance. An iterative process searches for the maximum concentration of points within the vertical tolerance and removes those points outside of the tolerance (Nayegandhi and others, 2009). These data are then converted to the North American Datum of 1983 and the North American Vertical Datum of 1988 (using the GEOID12A model). Each file contains data located in a 2-kilometer by 2-kilometer tile, where the upper-left bound can be ascertained quickly through the filename. The first 3 numbers in the filename represent the left-most UTM east bounding coordinate (e###000) in meters, the next 4 numbers represent the top-most UTM north bounding coordinate (n####000) in meters, and the last 2 numbers (##) represent the UTM zone in which the tile is located (for example, post_e123_n4567_18). The development of custom software for creating these data products has been supported by the U.S. Geological Survey CMGP's Lidar for Science and Resource Management project. Processed data products are used by the U.S. Geological Survey CMGP's National Assessments of Coastal Change Hazards project to quantify the vulnerability of shorelines to coastal change hazards such as severe storms, sea-level rise, and shoreline erosion and retreat. |
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 |
ISO 19115 Topic Category | elevation |
General | Airborne Lidar Processing System |
General | ALPS |
General | bathymetry |
General | Cessna 310 |
General | DEM |
General | Digital Elevation Model |
General | EAARL-B |
General | Experimental Advanced Airborne Research Lidar |
General | laser altimetry |
General | lidar |
General | remote sensing |
General | topography |
Global Change Master Science Directory | DOI/USGS/CMG > COASTAL AND MARINE GEOLOGY |
Global Change Master Science Directory | OCEAN > COASTAL PROCESSES > BARRIER ISLANDS |
Global Change Master Science Directory | OCEAN > COASTAL PROCESSES > BEACHES |
Global Change Master Science Directory | OCEAN > COASTAL PROCESSES > SHORELINE DISPLACEMENT |
Global Change Master Science Directory | U.S. GEOLOGICAL SURVEY |
Global Change Master Science Directory | U.S.DEPARTMENT OF INTERIOR |
Temporal Keywords
Thesaurus | Keyword |
---|---|
General | 2012 |
General | 2013 |
General | Post-Hurricane Sandy |
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Geographic Names Information System | Atlantic Ocean |
Geographic Names Information System | Barnegat Bay |
Geographic Names Information System | New Jersey |
Geographic Names Information System | Ocean |
Stratum Keywords
Thesaurus | Keyword |
---|---|
General | Submerged |
Instrument Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Instrument Keywords | LIDAR > Light Detection and Ranging |
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 | Map (digital) |
• Entity Attribute Overview |
Lidar points in LAZ format (Class 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 USGS, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2014 |
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 | 2014 |
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 | 2014 |
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 | 2014 |
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 | -74.4186321 |
---|---|
* » E° Bound | -73.94403664 |
* » N° Bound | 40.10738038 |
* » S° Bound | 39.47675859 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Discrete |
---|---|
* » Start | 2012-11-01 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 2
* » Time Frame Type | Discrete |
---|---|
* » Start | 2012-11-05 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 3
* » Time Frame Type | Discrete |
---|---|
* » Start | 2012-11-16 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 4
* » Time Frame Type | Discrete |
---|---|
* » Start | 2012-11-20 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 5
* » Time Frame Type | Discrete |
---|---|
* » Start | 2012-11-30 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 6
* » Time Frame Type | Discrete |
---|---|
* » Start | 2012-12-05 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 7
* » Time Frame Type | Discrete |
---|---|
* » Start | 2012-12-06 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 8
* » Time Frame Type | Discrete |
---|---|
* » Start | 2012-12-21 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 9
* » Time Frame Type | Discrete |
---|---|
* » Start | 2013-01-10 |
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=4730; |
• » Data Access Constraints |
None |
• Data Use Constraints |
The U.S. Geological Survey requests to be acknowledged as originators of these data in future products or derivative research. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4730 |
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/4730/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 | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4730/supplemental/nj2012_usgs_barnegatbay_m4730.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the coverage of the 2012 USGS Post Sandy Topobathy lidar collection of Barnegat Bay, NJ. |
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 expected accuracy of the measured variables is as follows: attitude within 0.05 degree, 3 centimeters nominal ranging accuracy, and vertical elevation accuracy of 25 centimeters RMSE for the topographic surface. Quality checks are built into the data-processing software. |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Expected horizontal accuracy for the Leica ALS70-cm sensor, as determined from system studies and other methods, is 1/5500th of the flight height, which, in the instance of this particular project was 3,800-feet AGL (1250m), giving a horizontal tolerance of less than 0.691 US survey feet (0.211 m).; Quantitative Value: 100 meters, Test that produced the value: 1.0 m |
Vertical Positional Accuracy |
The nominal vertical elevation accuracy expressed as the root mean square error (RMSE) is 25 centimeters.; Quantitative Value: 0.25 meters, Test that produced the value: 25 cm RMSEz |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
These point-cloud data may appear sparse or nonexistent, which is a result of removal from manual editing or lack of survey coverage. |
Conceptual Consistency |
Each file contains data located in a 2-kilometer by 2-kilometer tile where the upper-left bound can be ascertained quickly through the filename. The first 3 numbers in the filename represent the left-most UTM east bounding coordinate (e###000) in meters, the next 4 numbers represent the top-most UTM north bounding coordinate (n####000) in meters, and the last 2 numbers (##) represent the UTM zone in which the tile is located (for example, post_e123_n4567_18). |
» 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 data were collected using a Cessna 310 aircraft. The EAARL-B laser scanner collects the data using a green-wavelength (532-nanometer) raster scanning laser, while a digital camera acquires a visual record of the flight. The data are stored on hard drives and archived at the U.S. Geological Survey office in St. Petersburg, Florida. The navigational data are processed and then, along with the raw data, are downloaded into ALPS, or the Airborne Lidar Processing System (20130211-20140219). Data are converted from units of time to x,y,z points for elevation and formatted into .las and .xyz files, and the derived surface data are converted into raster data (GeoTIFFs). |
Process Date/Time | 2014-02-19 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
A bias correction of -16 centimeters (value determined from instrument calibrations) was applied to the point-cloud data using ALPS (20140827) to account for a change in configuration parameters. Data are formatted into .las and .xyz files, and the derived surface data are converted into raster data (GeoTIFFs). |
Process Date/Time | 2014-08-27 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
The lidar data were downloaded as LAS files from the USGS Data Series' website for the survey. The data obtained were projected in NAD83 UTM coordinates (Zone 18), and referenced vertically to the North American Vertical Datum of 1988 (NAVD88) using the NGS Geoid12A model. The vertical units of the data were meters. For preparation of the data for Digital Coast provisioning and data storage, the following processing steps were performed: Using NOAA VDatum software the data were 1) reprojected from NAD83 UTM Zone 18 to NAD83 geographic coordinates and 2) the data were transformed from orthometric to ellipsoidal (GRS80) heights using Geoid12A. Bathymetric ("submerged topography") points were reclassfied from 0 to 11 for consistency with NOAA OCM's classification scheme for bathymetric lidar. 3) data were then converted to .laz format using LASzip. |
Process Date/Time | 2014-03-06 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) reviewed the bathymetric lidar files for quality assurance. |
Process Date/Time | 2014-12-19 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 | 49861 |
---|---|
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 |
---|