<?xml version="1.0" encoding="UTF-8"?>
<inport-metadata xmlns:xs="http://www.w3.org/2001/XMLSchema"
                 version="1.11"
                 source="https://www.fisheries.noaa.gov">
   <item-identification>
      <catalog-item-id>48182</catalog-item-id>
      <title>2012 Georgia Department of Natural Resources (DNR) Lidar: Baldwin, Hancock, Morgan, and Putnam Counties</title>
      <short-name>ga2012_gadnr_baldwin_hancock_morgan_putnam_m2619_metadata</short-name>
      <catalog-item-type>Data Set</catalog-item-type>
      <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
      <parent-catalog-item-id>37231</parent-catalog-item-id>
      <parent-title>Lidar</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <publication-date>2014-04</publication-date>
      <abstract>LiDAR data is a remotely sensed high resolution elevation data collected by an airborne platform. The LiDAR sensor uses a combination of laser range finding,
GPS positioning, and inertial measurement technologies. The LiDAR systems collect data point clouds that are used to produce highly detailed Digital
Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The task required the LiDAR data to be collected at a nominal pulse
spacing (NPS) of 1.0 meter. The final products include full classified LAS, hydrologically flattened four (4) foot pixel raster DEM's of the bare earth
surface in IMG Format, and hydrologically flattened breaklines in gdb format. Links to the hydrologically flattened 4 foot pixel raster bare earth DEMs and
the hydrologically flattened breaklines are provided in the Supplemental Information section below.
This metadata record describes the classified LAS files. The classifications of lidar data available from the Digital Coast are:
1  Unclassified
2  Ground
7  Noise
9  Water
10 Ignored Ground
17 Overlap Unclassified
18 Overlap Ground

This lidar data set also includes lidar intensity values. Intensity information is captured from the reflective surface pulse and indicates the relative energy
returned to the sensor, as compared to the energy transmitted. The intensity image is not calibrated or normalized but indicates differences in energy absorption due to the interaction of the surface materials with laser energy, at the wavelength transmitted by the sensor.
This lidar data set covers 1455 sq miles in Baldwin, Hancock, Morgan, and Putnam counties in Georgia. The data were collected Dec 19, 22, 28, 30, 2012 and
January 4, 5, 2013.

The LiDAR data were collected to meet Fundamental Vertical Accuracy (FVA) Root Mean Square Error (RMSE) of 18.0 cm or better at a 95% confidence level,
so that when combined with breaklines, the data adequately supports the generation of two (2) foot FEMA compliant contours. The final LiDAR data were
delivered in 5,000 ft x 5,000 ft tiles using NAD 1983(2011), Georgia State Plane Coordinate System, West Zone, and expressed in US Survey Feet for Morgan
and Putnam Counties. The final LiDAR data was delivered in 5,000 ft x 5,000 ft tiles using NAD 1983(2011), Georgia State Plane Coordinate System, East Zone,
and expressed in US Survey Feet for Baldwin and Hancock Counties. The vertical datum used for this survey is North American Vertical Datum 1988 (NAVD88),
and expressed in US Survey Feet. Upon receipt of the data, the NOAA Office for Coastal Management (OCM) converted the data for Digital Coast storage purposes.
The data were converted to geographic coordinates and ellipsoid heights, expressed in meters.</abstract>
      <purpose>This task order consisted of LiDAR data acquisition and processing for the National Oceanic and Atmospheric Administration's (NOAA) Office for Coastal Management
(OCM) four Counties in Georgia: Baldwin, Hancock, Morgan, and Putnam. The LiDAR data was collected to meet Fundamental Vertical
Accuracy (FVA) Root Mean Square Error (RMSE) of 18.0 cm or better at a 95% confidence level, so that when combined with breaklines, the data adequately
supports the generation of two (2) foot FEMA compliant contours.</purpose>
      <notes>10205</notes>
      <supplemental-information>The final report for this data set may be viewed at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2619/supplemental/ga2012_gadnr_baldwin_hancock_morgan_putnam_m2619_final_report.pdf
A footprint of this data set may be viewed in Google Earth at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2619/supplemental/ga2012_gadnr_baldwin_hancock_morgan_putnam_m2619.kmz
The hydrologically flattened breaklines may be accessed here:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2619/breaklines/
The hydrologically flattened 4 foot pixel raser bare earth DEMs may be accessed here:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2619/dems/</supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="f7d2e34a-c5c2-4c21-9132-2472620dbda1">EARTH SCIENCE &gt; LAND SURFACE &gt; TOPOGRAPHY &gt; TERRAIN ELEVATION &gt; TOPOGRAPHICAL RELIEF MAPS</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="b6b51058-1111-4498-a9ac-e1515270fb27">EARTH SCIENCE &gt; OCEANS &gt; BATHYMETRY/SEAFLOOR TOPOGRAPHY &gt; SEAFLOOR TOPOGRAPHY</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="1fbf5df2-ab7c-43fc-9bb2-8eb3f8891f7b">EARTH SCIENCE &gt; OCEANS &gt; COASTAL PROCESSES &gt; COASTAL ELEVATION</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="a94fb5d3-6a0a-44a1-ac31-5e8978b5f0b1">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA &gt; GEORGIA</keyword>
      </keyword>
   </keywords>
   <physical-location>
      <organization>Office for Coastal Management</organization>
      <city>Charleston</city>
      <state-province>SC</state-province>
   </physical-location>
   <data-set-information>
      <data-set-scope-code>Data Set</data-set-scope-code>
      <maintenance-frequency>As Needed</maintenance-frequency>
      <data-presentation-form>Map (digital)</data-presentation-form>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility Woolpert, Inc, the National Oceanic and Atmospheric Administration (NOAA),
National Ocean Service (NOS), the Office for Coastal Management or its partners.</distribution-liability>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="1">
      <entity>
         <item-identification>
            <catalog-item-id>49298</catalog-item-id>
            <title>las</title>
            <short-name>las</short-name>
            <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
            <status>Completed</status>
            <abstract>las file for Morgan, Putnam, Hancock and Baldwin Counties | Description Source: Woolpert, Inc.</abstract>
            <notes>Converted from FGDC using 'fgdc_to_inport_xml_entity.pl' script.</notes>
         </item-identification>
      </entity>
   </entity-attribute-information>
   <support-roles>
      <support-role cc-id="623879" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2014-04</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="623881" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2014-04</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="623882" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2014-04</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="623880" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2014-04</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
   </support-roles>
   <extents>
      <currentness-reference>Ground Condition</currentness-reference>
      <extent cc-id="1135130">
         <geographic-areas>
            <geographic-area cc-id="1135137">
               <west-bound>-83.704424</west-bound>
               <east-bound>-82.739281</east-bound>
               <north-bound>33.831072</north-bound>
               <south-bound>32.901943</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1135131">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-12-19</start-date-time>
            </time-frame>
            <time-frame cc-id="1135132">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-12-22</start-date-time>
            </time-frame>
            <time-frame cc-id="1135133">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-12-28</start-date-time>
            </time-frame>
            <time-frame cc-id="1135134">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2012-12-30</start-date-time>
            </time-frame>
            <time-frame cc-id="1135135">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2013-01-04</start-date-time>
            </time-frame>
            <time-frame cc-id="1135136">
               <time-frame-type>Discrete</time-frame-type>
               <start-date-time>2013-01-05</start-date-time>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <vector>Yes</vector>
         </representations-used>
      </spatial-representation>
   </spatial-information>
   <access-information>
      <security-class>Unclassified</security-class>
      <data-access-procedure>This data can be obtained on-line at the following URL:
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2619
This data set is dynamically generated based on user-specified parameters.;</data-access-procedure>
      <data-access-constraints>None</data-access-constraints>
      <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.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="743832">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2619</download-url>
         <file-name>Customized Download</file-name>
         <description>Create custom data files by choosing data area, product type, map projection, file format, datum, etc.</description>
      </distribution>
      <distribution cc-id="743833">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2619/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="743837">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2619/supplemental/ga2012_gadnr_baldwin_hancock_morgan_putnam_m2619.kmz</url>
         <name>Browse Graphic</name>
         <url-type>Browse Graphic</url-type>
         <file-resource-format>kmz</file-resource-format>
         <description>This graphic shows the lidar coverage</description>
      </url>
      <url cc-id="743836">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="743835">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="623908">
         <activity-date-time>2016-05-23</activity-date-time>
         <description>Date that the source FGDC record was last modified.</description>
      </activity-log>
      <activity-log cc-id="623907">
         <activity-date-time>2017-11-14</activity-date-time>
         <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.</description>
      </activity-log>
      <activity-log cc-id="717858">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="743834">
         <activity-date-time>2018-03-13</activity-date-time>
         <description>Partial upload to move data access links to Distribution Info.</description>
      </activity-log>
   </activity-logs>
   <data-quality>
      <accuracy>The LiDAR collected for this task order was collected to meet a Fundamental Vertical Accuracy (FVA) of NSSDA RMSEZ = 18cm (NSSDA AccuracyZ 95% = 30cm)
or better; assessment procedures to comply with FEMA, NSSDA, NDEP, and ASPRS guidelines. | Quantitative Value: 18 cm RMSE | Quantitative Test Explanation: Points measured will produce an error less than 18.0 cm RMSE.</accuracy>
      <horizontal-positional-accuracy>Horizontal accuracy is plus or minus 1.2 m (4 feet) at the 95% confidence level using RMSE(r) x 1.7308 when compared to the classified lidar as defined by the FGDC
Geospatial Positional Accuracy Standards, Part 3: NSSDA.; Quantitative Value: 1.2 meters, Test that produced the value: Horizontal accuracy is plus or minus 1.2 m (4 feet) at the 95% confidence level. LiDAR system calibration is
available in the project report. See link to the report in Supplemental Information field.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>The LiDAR data vertical accuracy of the lidar bare earth point is 5.2 cm (0.17 feet) RMSE when compared to ground surveyed QA/QC points. The data
collected under this task Order meets the FEMA, NSSDA, NDEP, and ASPRS guidelines for accuracy standards. These standards specify that vertical
accuracy be reported at the 95 percent confidence level for data tested by an independent source of higher accuracy.
(http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part3/index_html). Twenty-Three (23) survey control points were surveyed
by Woolpert survey crews and used for lidar processing. Twenty-Two (22) control points were surveyed by Woolpert survey crews and used for
the independent survey control point accuracy reporting.
LAS Swath Fundamental Vertical Accuracy (FVA) Tested 10.1 cm (0.333 feet) fundamental vertical accuracy at a 95 percent confidence level, derived according
to NSSDA, in open terrain using (RMSEz) x 1.96000 tested against the TIN using independent check points.; Quantitative Value: 0.052 meters, Test that produced the value: Vertical Accuracy Statistics Morgan, Hancock, Putnam, and Baldwin:
Tested 10.1 cm (0.333 feet) fundamental vertical accuracy at 95 percent confidence level when compared to the classified lidar in open terrain using RMSE(z)
x 1.9600. RMSE in open terrain when compared to ground surveyed QA/QC points is 5.2 cm (0.17 feet)</vertical-positional-accuracy>
      <completeness-report>The LiDAR data is visually inspected for completeness to ensure that are no gaps between flight lines.</completeness-report>
      <conceptual-consistency>All formatted data are validated using commercial GIS software to ensure proper formatting and loading prior to delivery.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-process-steps>
         <lineage-process-step cc-id="1135125">
            <sequence-number>1</sequence-number>
            <description>Using an Optech Gemini LiDAR system, 142 flight lines of high density data, at a nominal pulse spacing (NPS) of 1.0 meter, were collected
over Morgan, Hancock, Putnam, and Baldwin Counties, GA (approximately 1455 square miles). Multiple returns were recorded for each laser pulse
along with an intensity value for each return. A total of thirteen (13) missions were flown on December 19, 22, 28, 30 in 2012 and January 4 and 5
in 2013. The geoid used to reduce satellite derived elevations to orthometric heights was GEOID12A. The horizontal datum used for this survey is NAD 1983
(2011), Georgia State Plane Coordinate System, West Zone, and expressed in US Survey Feet for Morgan and Putnam Counties. The horizontal datum used for
this survey is NAD 1983 (2011), Georgia State Plane Coordinate System, East Zone, and expressed in US Survey Feet for Baldwin and Hancock Counties. The
vertical datum used for this survey is North American Vertical Datum 1988 (NAVD88), and expressed in US Survey Feet. Airborne GPS data was differentially
processed and integrated with the post processed IMU data to derive a smoothed best estimate of trajectory (SBET). The SBET was used to reduce the
LiDAR slant range measurements to a raw reflective surface for each flight line.</description>
            <process-date-time>2012-12-20T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1135126">
            <sequence-number>2</sequence-number>
            <description>The Optech Gemini LiDAR system calibration and performance is verified on a periodic basis using Woolpert's calibration range. The calibration range
consists of a large building and runway. The edges of the building and control points along the runway have been located using conventional survey
methods. Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position of the building edges
between opposing flight lines. The scanner scale factor and vertical accuracy is calculated through comparison of LiDAR data against control points
along the runway. Field calibration is performed on all flight lines to refine the IMU misalignment angles. IMU misalignment angles are calculated
from the relative displacement of features within the overlap region of adjacent (and opposing) flight lines. The raw LiDAR data is reduced using
the refined misalignment angles.</description>
            <process-date-time>2012-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1135127">
            <sequence-number>3</sequence-number>
            <description>Once the data acquisition and GPS processing phases are complete, the LiDAR data was processed immediately to verify the coverage had no voids. The
GPS and IMU data was post processed using differential and Kalman filter algorithms to derive a best estimate of trajectory. The quality of the
solution was verified to be consistent with the accuracy requirements of the task order.</description>
            <process-date-time>2012-12-20T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1135128">
            <sequence-number>4</sequence-number>
            <description>The individual flight lines were inspected to ensure the systematic and residual errors have been identified and removed. Then, the flight lines were
compared to adjacent flight lines for any mismatches to obtain a homogenous coverage throughout the project area. The point cloud underwent a
classification process to determine bare-earth points and non-ground points utilizing first and only as well as last of many LiDAR returns.
This process determined bare-earth points (Class 2), noise (Class 7), water (Class 9) ignored ground (Class 10), unclassified data (Class 1), overlap
default (Class 17), and overlap ground (Class 18). The bare-earth (Class 2 - Ground) LiDAR points underwent a manual QA/QC step to verify that artifacts
have been removed from the bare-earth surface. The surveyed ground control points are used to perform the accuracy checks and statistical analysis of the
LiDAR dataset.</description>
            <process-date-time>2012-12-20T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1135129">
            <sequence-number>5</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received the files in las format. The files contained lidar elevation and intensity measurements.
The data were in Georgia State Plane coordinates, NAVD88 elevations, and US Survey feet vertical units. OCM performed the following processing
for data storage and Digital Coast provisioning purposes:
1. The data were converted from Georgia State Plane (Zones East (FIPs 1011) and West (FIPS 1002)) coordinates to geographic coordinates.
2. The data were converted from NAVD88 heights to ellipsoid elevations using Geoid12A.
3. The data were converted from US Survey Feet vertical units to meters vertical units.
4. The data were filtered for elevation outliers.
5. The data were zipped to laz format.</description>
            <process-date-time>2014-03-15T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <child-items>
      <child-item>
         <catalog-item-id>49298</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>las</title>
      </child-item>
   </child-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:48182</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-14T14:19:54</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2022-08-09T17:11:33</metadata-record-last-modified>
      <record-published>2022-03-16</record-published>
      <owner-organization>Office for Coastal Management</owner-organization>
      <owner-organization-acronym>OCM</owner-organization-acronym>
      <owner-organization-address/>
      <owner-organization-address-city/>
      <owner-organization-address-state/>
      <owner-organization-address-zip/>
      <owner-organization-address-country/>
      <owner-organization-phone/>
      <owner-organization-url/>
      <owner-organization-business-hours/>
      <owner-organization-group-id>1002</owner-organization-group-id>
      <publication-status>Public</publication-status>
      <limited-metadata-available>No</limited-metadata-available>
      <is-do-not-publish>No</is-do-not-publish>
      <metadata-last-review-date>2022-03-16</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2023-03-16</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
