<?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>49764</catalog-item-id>
      <title>2012 USACE HSDRRS Lidar: New Orleans</title>
      <short-name>la2012_usace_new_orleans_m6350_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>49401</parent-catalog-item-id>
      <parent-title>Lidar - partner (no harvest)</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <publication-date>2017-08-12</publication-date>
      <abstract>Acquisition of Light Detection and Ranging (LiDAR) elevation data was for the Hurricane and Storm Damage Risk Reduction System (HSDRRS). In February 2012,
USACE, Contracting Division contracted with The Atlantic Group to provide acquisition of Light Detection and Ranging (LiDAR) elevation data in the Hurricane and Storm Damage Risk Reduction System, St. Charles, Jefferson, Orleans, St. Bernard and Plaquemines Parishes, LA. This data will be used to support interior drainage modeling. LiDAR data should be collected to fully capture the total interior of the HSDRRS, including floodwalls, structures, and levees, and 200 feet outside of the HSDRRS to water's edge as appropriate. The project shall include capture of LiDAR data and the creation of digital elevation models derived from the LiDAR. The project area is approximately 418.4 sq. miles, including a 200' buffer. The purpose of the survey is to obtain measurements of the bare ground surface, as well as top surface feature elevation data for providing geometry input to USACE hydrodynamic and other numerical models as well as for performing economic related assessments. 

Upon receipt of data, the NOAA Office for Coastal Management (OCM) noted that many areas have lidar points over water that are classified as ground. This was mainly seen in lidar points over Lake Pontchartrain. In these areas, those points were reclassified from ground (2) to unclassified (1). In other areas, however, the user should be aware that points over water may be classified as ground.

In addition to the lidar point data, bare earth Digital Elevation Models (DEMs), at a 2 ft grid spacing, created from the lidar point data are also available. These data are available for download here: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=6352 
Breaklines created from the lidar are also available for download in shp format at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/6350/breaklines 
The DEM and breakline 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, OCM or its partners.
Original contact information: 
   Contact Name: Patrick Robinson
   Contact Org: Atlantic Group
   Title: LiDARManager
   Phone: 256-971-9991
   Email: probinson@theatlgrp.com</abstract>
      <purpose>The purpose of the survey is to obtain measurements of the bare ground surface, as well as top surface feature elevation data for providing geometry input to USACE hydrodynamic and other numerical models as well as for performing economic related assessments.</purpose>
      <notes>10408</notes>
      <supplemental-information>The lidar report may be accessed here:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/6350/supplemental/la2012_usace_new_orleans_m6350_lidar_report.pdf
The survey report may be accessed here:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/6350/supplemental/la2012_usace_new_orleans_m6350_survey_report.pdf</supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>ArcMap</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Corps of Engineers</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>ESRI</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>HSDRRS</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Hurricane</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>New Orleans District</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Risk Reduction System</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>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility of the Atlantic Group, USACE, NOAA, the NOAA Office for Coastal Management (OCM) or its partners.</distribution-liability>
      <data-set-credit>Paul Weyant, Patrick Robinson, Josh Hester</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="1">
      <entity>
         <item-identification>
            <catalog-item-id>50225</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>GPS, IMU, and laser pulse range data | Description Source: ASPRS LiDAR Data Exchange Format Standard version 1.2</abstract>
            <notes>Converted from FGDC using 'fgdc_to_inport_xml_entity.pl' script.</notes>
         </item-identification>
         <data-attributes partial-listing="No" total-count="8">
            <data-attribute cc-id="694087">
               <seq-order>1</seq-order>
               <name>X_Coord</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Easting Coordinate | Description Source: ASPRS LiDAR Data Exchange Format</description>
               <allowed-values>Coordinates defining the features.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="694088">
               <seq-order>2</seq-order>
               <name>Y_coord</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>North Coordinate | Description Source: ASPRS LiDAR Data Exchange Format</description>
               <allowed-values>Coordinates defining the features.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="694089">
               <seq-order>3</seq-order>
               <name>Z_coord</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Elevation above Sea-Level | Description Source: ASPRS LiDAR Data Exchange Format</description>
               <allowed-values>Coordinates defining the features.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="694090">
               <seq-order>4</seq-order>
               <name>Intensity</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Strength of return value within a given range (0-255) | Description Source: ASPRS LiDAR Data Exchange Format</description>
               <allowed-values>Intensity value</allowed-values>
            </data-attribute>
            <data-attribute cc-id="694091">
               <seq-order>5</seq-order>
               <name>Return</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>The number of returns for a given pulse | Description Source: ASPRS LiDAR Data Exchange Format</description>
               <allowed-values>Number of returns</allowed-values>
            </data-attribute>
            <data-attribute cc-id="694092">
               <seq-order>6</seq-order>
               <name>Scan Direction Flag</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Direction the scanner mirror was traveling at the time of the output pulse | Description Source: ASPRS LiDAR Data Exchange Format</description>
               <allowed-values>Scan direction</allowed-values>
            </data-attribute>
            <data-attribute cc-id="694093">
               <seq-order>7</seq-order>
               <name>Edge of Flightline</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>It is the last point on a given scan line before it changes direction | Description Source: ASPRS LiDAR Data Exchange Format</description>
               <allowed-values>Edge of flightline</allowed-values>
            </data-attribute>
            <data-attribute cc-id="694094">
               <seq-order>8</seq-order>
               <name>Classification</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Assigned Point Classification | Description Source: ASPRS LiDAR Data Exchange Format</description>
               <allowed-values>Point classification</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
   </entity-attribute-information>
   <support-roles>
      <support-role cc-id="676107" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2017-08-12</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="676109" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2017-08-12</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="676110" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2017-08-12</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="676108" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2017-08-12</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="1140079">
         <geographic-areas>
            <geographic-area cc-id="1140081">
               <west-bound>-90.609656</west-bound>
               <east-bound>-89.609035</east-bound>
               <north-bound>30.169328</north-bound>
               <south-bound>29.632568</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1140080">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2012-03-04</start-date-time>
               <end-date-time>2012-03-25</end-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>
      <security-classification-system>N/A</security-classification-system>
      <security-handling-description>Nothing Specified</security-handling-description>
      <data-access-procedure>This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=6350;</data-access-procedure>
      <data-access-constraints>None</data-access-constraints>
      <data-use-constraints>None. However, users should be aware that temporal changes may have occurred since this dataset was collected and that some parts of these data may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of its limitations. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="741208">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=6350</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="741209">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/6350/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="741214">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/6350/supplemental/la2012_usace_new_orleans_m6350.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 footprint for the 2012 USACE HSDRRS New Orleans project area.</description>
      </url>
      <url cc-id="741213">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="741212">
         <url>https://coast.noaa.gov/dataregistry</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="741211">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="676133">
         <activity-date-time>2017-08-18</activity-date-time>
         <description>Date that the source FGDC record was last modified.</description>
      </activity-log>
      <activity-log cc-id="676132">
         <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="718330">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="741210">
         <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>
   <technical-environment>
      <description>ArcMAP V.10.1 ; LP360 V.2011.1.54.1 ; Microstation V8 ; ALTMnav ; Dashmap ;</description>
   </technical-environment>
   <data-quality>
      <accuracy>A minimum of 20 test points where selected for each land cover class (except HSDRRS Class 7) identified per 100 Sq miles. Therefore, 120 test points were selected for the six land cover classes specified above per 100 Sq miles, plus 20 test points each for any additional land cover classes added. Additionally, test points were geographically distributed throughout the project area. Test points were carefully selected in areas of the highest PDOP to evaluate DEM accuracy under trees and in vegetation representative of the study area. A minimum of 50 test points was collected along the HSDRRS levees to enable an accuracy assessment for the HSDRRS. These levee test points where spaced at least 0.25 miles apart, but they do not need to cover the entire HSDRRS levee system.</accuracy>
      <horizontal-positional-accuracy>The data must meet the NSSDA RMSEr of 2.2 ft (0.67 m) and the NSSDA Accuracyr of 95% confidence level is 3.80 ft (1.16 m). Horizontal point accuracy is a function of angular origination of the pulse; IMU orientation; the scanner encoder and ranging function and will vary depending on the proposed point density selected for the collection. Statistically, the error is roughly 1/3 of the illuminated foot print on the ground and is a function of the beam divergences.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>Based on the vertical accuracy testing conducted by The Atlantic Group, LLC using NSSDA methodology, the dataset tested 12.2 cm for vertical accuracy at 95% confidence level in open terrain. LiDAR vertical data accuracy determination shall employ the National Standard for Spatial Data Accuracy (NSSDA).  Contracted to meet 18cm (RMSE) or better.</vertical-positional-accuracy>
      <completeness-report>All data is complete to standards as specified.LIDAR raster data is visually inspected for completeness to ensure that any gaps between flight lines of required collection area. LIDAR is self-illuminating and has minimal cloud penetration capability. Water vapor in steam plumes or particulates in smoke may cause reflection of LIDAR signals and loss of elevation information beneath these plumes. Glass structures and roofs may appear transparent to the LIDAR signal and therefore may not register on the reflective surface.</completeness-report>
      <conceptual-consistency>QC/QA process shall include reviews of flight alignments and
completeness of supporting data. The USACE New Orleans district or its designee may perform
additional QC/QA testing. The root mean square error (RMSE) is used to estimate both
horizontal and vertical accuracy. RMSE is the square root of the average of the set of squared
differences between dataset coordinate values and coordinate values from an independent source.
Bare-earth processed data for this acquisition block comply with the following accuracy requirements for Artifact/Feature removal:  artifacts - 90%; outliers - 95%; vegetation - 95%; buildings - 98%.  All LAS formatted LIDAR data are validated using commercial GIS software to ensure proper formatting and loading before delivery. This validation procedure ensures that data on delivery media is in correct physical format and is readable.
of higher accuracy for identical points. If those differences are normally distributed and average
zero, 95 percent of any sufficiently large sample should be less than 1.96 times the RMSE.
Therefore 9-centimeter RMSE can be referred to as "18-centimeter accuracy at the 95-percent
confidence level." Following that convention, the vertical accuracy of any DEM is defined as
1.96 times the RMSE of linearly interpolated elevations in the DEM, as compared with known
elevations from high-accuracy test points. DEMs should have a maximum RMSE as specified to
meet its required vertical accuracy. The contractor must field verify the vertical accuracy of this
DEM to ensure that the RMSE requirement is satisfied for all land cover classes that
predominate within the floodplain being studied.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-sources>
         <lineage-source cc-id="1140074">
            <citation-title>LiDAR Acquisition for the Hurricane and Storm Damage Risk Reduction System</citation-title>
            <extent-type>Range</extent-type>
            <extent-start-date-time>2012-03-04</extent-start-date-time>
            <extent-end-date-time>2012-03-25</extent-end-date-time>
            <source-contribution>Lidar | Source Geospatial Form: remote-sensing image | Type of Source Media: digital tape media</source-contribution>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1140075">
            <sequence-number>1</sequence-number>
            <description>The ABGPS, IMU, and raw Optech LiDAR data are integrated into the Optech post processor software. The resultant file is in a LAS binary file format. The LAS file version 1.2 format can be easily transferred from one file format to another.  It is a binary file format that maintains information specific to the LiDAR data (return#, intensity value, xyz, etc.). The resultant points are produced in the geodetic coordinates referenced to the NAD83 horizontal datum and NAVD88 2004.65 vertical datum.</description>
            <process-date-time>2012-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1140076">
            <sequence-number>2</sequence-number>
            <description>The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters is applied as appropriate for the production of bare earth digital terrain models (dtms).  Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. The LiDAR mass points were delivered in American Society for Photogrammetry and Remote Sensing LAS 1.2 format.  The header file for each dataset is complete as define by the LAS 1.2 specification.  The data was classified as follows: Class 1 = Unclassified.  This class includes all non-ground classified points. Class 2 = Ground.  Class 7 = Low Points.  Class 9 = water.   Class 12 = Overlap.</description>
            <process-date-time>2012-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1140077">
            <sequence-number>3</sequence-number>
            <description>Conversion from Geodetic coordinates NAD83 into Louisiana state plane zone 1702 using NAD83 and conversion from ellipsoid heights (meters) into orthometric heights using NAVD88 (US Survey Foot).  Files are orthogonally tiled based to a  1500m x 1500m extent, and labeled with a "Tile_ID" attribute.</description>
            <process-date-time>2012-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1140078">
            <sequence-number>4</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received 525 files in las 1.2 format. LAS files from the 2004.65 folder were processed. The files contained lidar intensity and elevation measurements for the USACE HSDRRS project area. The data were in LA State Plane, Zone 1702 (NAD83 2007) coordinates and in NAVD88 elevations in feet. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 
1. The data were converted from las to laz format.
2. Spaces in the filenames were converted to underscores.
3. The LAStools software scripts lasinfo and lasvalidate were run on the las files to check for errors.
4. The data were converted from GPS seconds of the week to adjusted GPS time.
5. In 46 files, reclassified points that were over Lake Pontchartrain from ground (2) to unclassified (1).
6. Reclassified outlier elevation points (greater than 2000 ft and less than -100 ft) to noise (7).
7. Internal OCM scripts were run to convert the files from LA State Plane Zone 1702 coordinates to geographic coordinates and to convert from NAVD88 elevations in feet to ellipsoid elevations in meters using Geoid09. 
8. Internal OCM scripts were run on the las files to assign the geokeys, to sort the data by gps time and zip the data to database and to http.</description>
            <process-date-time>2017-08-15T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <child-items>
      <child-item>
         <catalog-item-id>50225</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>LAS</title>
      </child-item>
   </child-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:49764</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:22:09</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:36</metadata-record-last-modified>
      <record-published>2022-03-16</record-published>
      <owner-organization>OCM Partners</owner-organization>
      <owner-organization-acronym>OCMP</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>
