2013 Lidar DEM: St. Johns County, FL
OCM Partners
Data Set
(DS)
| ID: 55964
| Published / External
Created: 2019-03-26
|
Last Modified: 2024-01-10
Project (PRJ) | ID: 49404
ID: 55964
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2013 Lidar DEM: St. Johns County, FL |
---|---|
Short Name | fl2013_st_johns_dem_m8701_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2014-11-19 |
* » Abstract |
St. Johns County, Florida (County) has developed a comprehensive countywide base mapping and GIS enhancements to support master drainage planning, transportation planning, and preliminary engineering and wetland preservation studies. As part of this effort, Woolpert was contracted by Jones, Edmunds & Associates (JEA) to develop the new imagery and new DTM. The project consists of new 6-inch 4-Band Orthoimagery, new 1-meter max LiDAR, new 1-foot contours, updating of topographic/planimetric features. This data set is one component of a digital terrain model (DTM) for St. Johns County. The dataset is comprised of mass points, 2-D and 3-D breakline features, 1-foot and 2-foot contours, ground control, vertical test points, and a footprint of the data set, in the ESRI ArcGIS File Geodatabase format. In accordance with the counties specifications, the following breakline features are contained within the database: closed water bodies (lakes, reservoirs, etc) as 3-D polygons; linear hydrographic features (streams, shorelines, canals, swales, embankments, etc) as 3-D breaklines; coastal shorelines as 3-D linear features; edge of pavement road features as 3-D breaklines; soft features (ridges, valleys, etc.) as 3-D breaklines; island features as 3-D polygons; concretedam, culvert, footprint, lowconfidence, lowconfidenceanno, overpass, pipe, roadcenterlineoverbridge and swamppoint as 2-D features. Contours were generated from LiDAR ground class and breaklines and meet National Map Accuracy Standards. The LiDAR masspoints are delivered in the LAS file format based on the Florida statewide 5,000' by 5,000' grid. The GEOID model used to reduce satellite derived elevations to orthometric height is GEOID12A. Breakline features were captured to develop a hydrologically correct DTM. The coastalshoreline has a constant value of -0.6’ that was statistically derived from the LiDAR point cloud collected within the 2-hour window of MLL tide. 2008 Hydrographic and soft features were used to supplement the 2013 breaklines in Low Confidence areas. The NOAA Office for Coastal Management (OCM) received the 5ft DEM data from St. Johns County GIS in March 2018 and processed the data to be available for download from the Data Access Viewer (DAV) and via https. In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from, are also available. These data are available for custom download at the link provided in the URL section of this metadata record. Planimetric and breakline data are also available. These data are available for download at the link provided in the URL section of this metadata record. Please note that these products have not been reviewed by the NOAA Office for Coastal Management (OCM) and any conclusions drawn from the analysis of this information are not the responsibility of NOAA or OCM. |
* Purpose |
The DTM was created to support the development and maintenance of the St. Johns County Countywide Digital Contour Mapping Project. The project includes 6-inch color and IR countywide imagery. Breaklines improve the digital elevation model in areas where the point density is insufficient. |
Notes | |
Other Citation Details | |
• Supplemental Information |
Project Title: ST. JOHNS COUNTY, FL Vendor Name: Woolpert, Inc. |
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 > COASTAL PROCESSES > COASTAL ELEVATION |
ISO 19115 Topic Category | elevation |
None | beach |
None | DEM |
None | erosion |
Temporal Keywords
Thesaurus | Keyword |
---|---|
None | 2013 |
None | January |
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Location Keywords | CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > FLORIDA |
Global Change Master Directory (GCMD) Location Keywords | VERTICAL LOCATION > LAND SURFACE |
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 |
Global Change Master Directory (GCMD) Platform Keywords | DEM > Digital Elevation Model |
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 |
The St. Johns County GIS Division provides this data "as is" and makes no warranties, expressed or implied, concerning the accuracy, completeness, reliability, or suitability of this data for any particular use or purpose. St. Johns County assumes no liability whatsoever associated with the use or misuse of such data. Any conclusions drawn from the analysis of this information are not the responsibility of St. Johns County, NOAA, the Office for Coastal Management or its partners. |
Data Set Credit | St. Johns County GIS Division |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2019 |
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 | 2019 |
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 | 2019 |
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 | 2019 |
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 | -81.700529 |
---|---|
* » E° Bound | -81.192498 |
* » N° Bound | 30.261275 |
* » S° Bound | 29.613391 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Discrete |
---|---|
* » Start | 2013-01-11 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 2
* » Time Frame Type | Discrete |
---|---|
* » Start | 2013-01-12 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 3
* » Time Frame Type | Discrete |
---|---|
* » Start | 2013-01-14 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 4
* » Time Frame Type | Discrete |
---|---|
* » Start | 2013-01-17 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 5
* » Time Frame Type | Discrete |
---|---|
* » Start | 2013-01-20 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 6
* » Time Frame Type | Discrete |
---|---|
* » Start | 2013-01-22 |
End | |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Extent Group 1 / Time Frame 7
* » Time Frame Type | Discrete |
---|---|
* » Start | 2013-01-25 |
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? | |
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 |
Data is available online for bulk and 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 | 2018 |
---|---|
End Date | Present |
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8701 |
Distributor | |
File Name | Customized Download |
Description |
Create custom data files by choosing data area, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | Zip |
Review Status |
Start Date | 2018 |
---|---|
End Date | Present |
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/FL_St_Johns_DEM_2013_8701/index.html |
Distributor | |
File Name | Bulk Download |
Description |
Bulk 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/ |
---|---|
Name | NOAA's Office for Coastal Management (OCM) website |
URL Type | Online Resource |
File Resource Format | HTML |
Description |
Information on the NOAA Office for Coastal Management (OCM) |
URL | https://coast.noaa.gov/dataviewer/ |
---|---|
Name | NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) |
URL Type | Online Resource |
File Resource Format | HTML |
Description |
The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid12b/8698/supplemental/fl2013_st_johns_m8698.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/geoid12b/8698/supplemental/MTS_Report_St_Johns_County_Contour_2013.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/geoid12b/8698/breaklines/ |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Link to the breaklines, planimetric data, and contours. |
URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8698 |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Link to custom download the lidar point data from which these raster Digital Elevation Model (DEM) data were created. |
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 |
Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1 |
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy |
Compiled to meet 1.2 feet (0.37 m) horizontal accuracy at 95% confidence level as defined by the FGDC Geospatial Positional Accuracy Standards, Part 3: NSSDA. LiDAR system calibration is available in the MTS Report of Specific Purpose Survey. |
Vertical Positional Accuracy |
Vertical accuracy of the bare earth lidar is +/- 0.23-foot (7 cm) RMSE for unobscured ground points. The accuracy assessment was performed using a standard method to compute the root mean square error (RMSE) based on a TIN comparison of ground control points and filtered LiDAR data points. Filtered LiDAR data has had vegetation and cultural features removed and by analysis represents bare earth elevations. RMSE was used to compute the vertical accuracy based on methods described by the National Standard for Spatial Data Accuracy (NSSDA). The accuracy assessment was performed using a standard method to compute the root mean square error (RMSE) based on a comparison of ground control points and filtered LiDAR data points. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
This LiDAR data represents the complete set of data for St. Johns County. |
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 |
Airborne terrestrial LiDAR was collected for St. Johns County, FL. The LiDAR system acquisition parameters were developed based on a maximum average ground sample distance of 3.23 feet. A Leica ALS70 LiDAR sensor was used for acquisition. Acquisition specifications for the sensor were as follows: Field of View (full angle) - 40 degrees, Nominal flight altitude (AGL) - 6500 feet, Airspeed - 172 mph (150 knots), Laser pulse rate - 270,000 Hz, Nominal swath width (on ground) - 4732 feet, Maximum cross track point spacing - 2.98 feet, Maximum along track point spacing - 3.01 feet, Average point spacing - 3.28 feet, Flight line spacing - 3314 feet, Side overlap - 29.3 percent. Prior to the LiDAR acquisition, the system underwent a system calibration to verify the operational accuracy and misalignment angles. LiDAR data acquisition only occurred when the sky was sufficiently clear of clouds, smoke, and atmospheric haze. The LiDAR data was processed immediately following the acquisition to verify the coverage had no voids. The GPS and IMU data was post processed using differential and kalman filter algorithms to derive a smoothed best estimate of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the project. The ground control system to support the LiDAR survey consisted of 24 control points surveyed specifically for this project. The LiDAR data was post processed and verified to be consistent with the project requirements in terms of post spacing and absence of artifacts. The point cloud underwent classification to determine bare-earth points (class 2), low vegetation points (class 3), medium vegetation points (class 4), high vegetation points (class 5), building points (class 6) noise points (class 7), water returns (class 9), breakline proximity points (class 10), bridge points (class 13, canopy/covered walkway points (class 14) and unclassified data (class 1). |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
Once the initial lidar point cloud was derived, Woolpert performed QC to look for any systematic error within the lidar flights using proprietary software. Any systematic error was identified and removed, the individual lidar flights were clipped to remove overlap between the adjacent flights lines and to provide a homogeneous coverage over the project extents. Using the homogeneous coverage, above ground features were classified and removed using proprietary software to produce the bare-earth coverage. |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
Hard and soft breakline features were compiled as 2D and 3D features in the softcopy environment using DATEM’s Summit Evolution Capture software on an Intel® Core™ i7 – 3770 CPU @ 3.40GHz photogrammetric workstation. DATEM, Inc. of Anchorage, Alaska distributes the Summit software. The DTM was delivered as lidar mass points in LAS version 1.2 and the breaklines were delivered in an ArcGIS File Geodatabase. |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) received 1 ESRI grid file from the St. Johns County, Florida GIS Department. The data were in Florida State Plane East NAD83 (HARN) coordinates (US survey feet) and NAVD88 (Geoid12A) elevations in US survey feet. This information, however, was not present in the file georeferencing information. The bare earth raster file was at a 5 ft grid spacing. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Used gdal_translate to add the projection and vertical georeferencing (EPSG codes 2881 and 6360) information to the files. 2. Used gdal_translate to convert the file from ESRI grid format to geotiff format. 3. Copied the files to https |
Process Date/Time | 2019-03-26 00:00:00 |
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 | 55964 |
---|---|
Metadata Record Created By | Rebecca Mataosky |
Metadata Record Created | 2019-03-26 15:49+0000 |
Metadata Record Last Modified By | Kirk Waters |
» Metadata Record Last Modified | 2024-01-10 19:05+0000 |
Metadata Record Published | 2024-01-10 |
Owner Org | OCMP |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2022-03-16 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2023-03-16 |
Tags |
---|