2001 NCFMP Lidar: Phase 1A (Neuse, Pasquotank, Tar-Pamlico, White Oak River Basins)
OCM Partners
Data Set
(DS)
| ID: 49830
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 49830
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2001 NCFMP Lidar: Phase 1A (Neuse, Pasquotank, Tar-Pamlico, White Oak River Basins) |
---|---|
Short Name | nc2001_phase1a_m1397_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2012-12 |
* » Abstract |
This airborne LiDAR terrain mapping data was acquired January through March 2001. The data were collected for the floodplain mapping program for the state of North Carolina. The data were collected for the state in three phases: 1, 2, and 3. This metadata record describes that data that were in phase 1 of collection and fall within the Neuse, Pasquotank, Tar-Pamlico, and White Oak River Basins in central and eastern North Carolina. This area consists of 33 counties which are listed below in the Place Keywords field. The data were received by the NOAA Office for Coastal Management from the U.S. Geological Survey (USGS) Center for Lidar Coordination and Knowledge (CLICK). For data storage and Digital Coast provisioning purposes, the OCM converted the data to geographic coordinates and ellipsoid (Geoid99) elevations. The data are unclassified. Original contact information: Contact Org: NC Floodplain Mapping Program Phone: 919-715-0408 Email: hmorgan@ncem.org |
* Purpose |
These data were collected and derived by the North Carolina Floodplain Mapping Program (www.ncfloodmaps.com) as part of its effort to modernize FEMA Flood Insurance Rate Maps (FIRM) statewide. Although created for specific use in the engineering aspects of floodplain delineation, the data were also developed to address the elevation data requirements of the broader geospatial data user community. The North Carolina Floodplain Mapping Program was established in response to the extensive damage caused by Hurricane Floyd in 1999. |
Notes |
10474 |
Other Citation Details | |
• Supplemental Information |
A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1397/supplemental/nc2001_ncfmp_phase1b_m1397.kmz The Lidar Accuracy Assessment Reports for these data are available by county and may be viewed at: http://portal.ncdenr.org |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
Keywords | Contour |
Keywords | Elevation |
Keywords | ESRI |
Keywords | Flood |
Keywords | Floodplain |
Keywords | Full return |
Keywords | Hydraulic Modeling |
Keywords | LIDAR |
Keywords | Raw |
Keywords | Shapefile |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Geographic Names Information System | Beaufort County |
Geographic Names Information System | Camden County |
Geographic Names Information System | Carteret County |
Geographic Names Information System | Chowan County |
Geographic Names Information System | Coastal |
Geographic Names Information System | Craven County |
Geographic Names Information System | Currituck County |
Geographic Names Information System | Dare County |
Geographic Names Information System | Durham County |
Geographic Names Information System | Edgecombe County |
Geographic Names Information System | Franklin County |
Geographic Names Information System | Gates County |
Geographic Names Information System | Granville County |
Geographic Names Information System | Greene County |
Geographic Names Information System | Halifax County |
Geographic Names Information System | Hyde County |
Geographic Names Information System | Johnston County |
Geographic Names Information System | Jones County |
Geographic Names Information System | Lenoir County |
Geographic Names Information System | Martin County |
Geographic Names Information System | Nash County |
Geographic Names Information System | NC |
Geographic Names Information System | Neuse River Basin |
Geographic Names Information System | North Carolina |
Geographic Names Information System | Onslow County |
Geographic Names Information System | Orange County |
Geographic Names Information System | Pamlico County |
Geographic Names Information System | Pasquotank County |
Geographic Names Information System | Pasquotank River Basin |
Geographic Names Information System | Perquimans County |
Geographic Names Information System | Person County |
Geographic Names Information System | Pitt County |
Geographic Names Information System | Tar-Pamlico River Basin |
Geographic Names Information System | Tyrrell County |
Geographic Names Information System | Vance County |
Geographic Names Information System | Wake County |
Geographic Names Information System | Warren County |
Geographic Names Information System | Washington County |
Geographic Names Information System | Wayne County |
Geographic Names Information System | White Oak River Basin |
Geographic Names Information System | Wilson 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 | Unknown |
Maintenance Note | |
» Data Presentation Form | |
• Entity Attribute Overview |
Files in LAZ format (classified as 1, unclassified) |
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 NC Floodplain Mapping Program, EarthData International, the NOAA Office for Coastal Management, or its partners. |
Data Set Credit | Acknowledgement of the North Carolina Floodplain Mapping Program is appreciated when using the data set. This data set was developed for the North Carolina Floodplain Mapping Program by EarthData International of North Carolina. Parts of the raw data acquisition were subcontracted to Horizons Inc. and 3001 Inc. |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2012-12 |
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 | 2012-12 |
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 | 2012-12 |
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 | 2012-12 |
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 | -79.241832 |
---|---|
* » E° Bound | -75.451653 |
* » N° Bound | 36.563854 |
* » S° Bound | 34.464308 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2001-01-03 |
End | 2001-03-23 |
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 |
None |
Security Handling Description |
N/A |
• 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=1397 ; |
• » Data Access Constraints |
None |
• Data Use Constraints |
Users should be aware that temporal changes may have occurred since this data set was collected and that 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 | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=1397 |
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/1397/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/1397/supplemental/nc2001_ncfmp_phase1b_m1397.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage for the Neuse, Pasquotank, Tar-Pamlico, and White Oak River Basins in Phase 1 of the North Carolina statewide lidar collection. |
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-10-25 |
---|---|
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 |
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722 |
---|
Data Quality
Representativeness | |
---|---|
Accuracy |
LIDAR full returns were compared with NCGS QA/QC checkpoints using only single and final returns per pulse. A vertical bias was acquired after airport calibration based on this comparison. For the NC Floodplain Mapping Program, the vertical accuracy for coastal counties is less than or equal to 20 cm RMSE. For mainland counties, the vertical accuracy of the elevation data is less than or equal to 25 cm RMSE. More information about the Quality Control reports and a summary of the quality control checks for each county can be found at http://portal.ncdenr.org/web/lr/geodetic/floodplaininfo. | Quantitative Value: 20 | Quantitative Test Explanation: Less than or equal to 20 cm RMSE of bare earth LIDAR points compared with independent checkpoints. |
Analytical Accuracy | |
Horizontal Positional Accuracy |
LIDAR full return mass points were compared with surveyed elevations provided by independent contractors to the NCGS. More information about the Quality Control reports is available at http://portal.ncdenr.org/web/lr/geodetic/floodplaininfo. Numerous internal quality assurance/quality control steps taken to ensure the quality of the LIDAR terrain data to meet the bare earth requirements and RMSE accuracy standards in the NC Floodplain Mapping Program. Step 1. Preprocessing Step 2. Post-Automated Editing QC (Data Evaluation) Step 3. QC Check of Tiles Step 4. Manual Editing (Hillshade Checks / Peer Review) Step 5. QC and Tile Edge Matching Step 6. Final EarthData QC Step 7. Comparisons of Independent Field Survey Data with LIDAR Data ; Quantitative Value: 2 meters, Test that produced the value: RMSE (m) of bare earth LIDAR points compared with independent checkpoints. |
Vertical Positional Accuracy |
LIDAR full return mass points were compared with surveyed elevations provided by independent contractors to the NCGS. A vertical bias was acquired after airport calibration based on this comparison. For the NC Floodplain Mapping Program, the vertical accuracy for coastal counties is less than or equal to 20 cm RMSE. For mainland counties, the vertical accuracy of the elevation data is less than or equal to 25 cm RMSE. The RMSE value for each county is available in the Lidar Accuracy Assessment Report. These reports are available by county and may be viewed at: http://portal.ncdenr.org/web/lr/geodetic/floodplaininfo Numerous internal quality assurance/quality control steps were taken to ensure the quality of the LIDAR terrain data to meet the bare earth requirements and RMSE accuracy standards in the NC Floodplain Mapping Program. Step 1. Preprocessing Step 2. Post-Automated Editing QC (Data Evaluation) Step 3. QC Check of Tiles Step 4. Manual Editing (Hillshade Checks / Peer Review) Step 5. QC and Tile Edge Matching Step 6. Final EarthData QC Step 7. Comparisons of Independent Field Survey Data with LIDAR Data ; Quantitative Value: 0.20 meters, Test that produced the value: RMSE (m) of bare earth LIDAR points compared with independent checkpoints. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
The full return mass points contain voids where insufficient energy was reflected from the surface to generate a valid return from the terrain. Voids in the full return mass points tend to occur in water bodies. Wet sand and certain types of vegetation can also cause voids or anomalous elevations. |
Conceptual Consistency |
Data was vertically adjusted based on RMSE and mean difference from control report. |
» 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 |
All data collection flights were initialized and finalized during periods of GPS Position Dilution of Precision greater than 4. GPS data quality was evaluated post-flight to ensure sufficient quality for LIDAR data requirements and integration. GPS base maximum allowable distance between stations was established such that no more than a 50 mile radius occurred between occupations. Swath width of terrain covered in a single flightline for inland areas at an altitude of 12,000 feet AMT was approximately 3,411 meters, coastal areas at an altitude of 8,000 feet AMT was approximately 2,274 meters. Field of View for the Leica GeoSystems Aeroscan system used was 50 degrees project wide, or 25 degrees from nadir with a maximum of 5 returns collected for each pulse. Ground distance between flightlines for inland areas at 12,000 feet AMT was approximately 2,388 meters, for coastal areas at 8,000 feet AMT was approximately 1,592 meters. Nominal post spacing for finalized Bare Earth product was 3 meters. An average of 10-20 rapid static GPS survey collected ground control points were established per base airport project wide to detect and correct horizontal and vertical bias. Typically, 3 or more flightlines of LIDAR returns were collected for each airport lift, one of which being bi-directional for use in optimizing instrument boresight angles to account for aircraft pitch, yaw and roll. All post process collection quality assurance is achieved aided by airport cross and bi-directional flightlines, entire lift cross flightlines, and the use of surveyed ground control points. |
Process Date/Time | 2001-02-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
Checking for coverage and anomalies, Airport calibration, Production flightline calibration, and Removal of blunders |
Process Date/Time | 2001-02-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
Tiling Automated filtering for point classification, Manual editing to classify points, Quality control, Removal of all points not classified as bare earth |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
The methods used to develop these data for the North Carolina Floodplain Mapping Program are documented in LIDAR Bare Earth Mass Points and Breaklines Technical Document, available online at www.ncfloodmaps.com. |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 5 |
---|---|
» Description |
The lidar point data were received by the NOAA Office for Coastal Management from the USGS Center for Lidar Coordination and Knowledge (CLICK) in las format. The files contained lidar elevation and intensity measurements. The data were unclassified, in State Plane coordinates, and were vertically referenced to NAVD88. 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 orthometric (NAVD88) heights to ellipsoidal heights using Geoid99. 3. The data were sorted by time and laszipped. |
Process Date/Time | 2012-12-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 | 49830 |
---|---|
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 |
---|