<?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>55607</catalog-item-id>
      <title>NAV_MARINE_LINE</title>
      <short-name>NAV_MARINE_LINE</short-name>
      <catalog-item-type>Entity</catalog-item-type>
      <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
      <parent-catalog-item-id>55600</parent-catalog-item-id>
      <parent-title>South Carolina 2015 ESI NAVIGATION_MARINE Polygons, Points, Lines</parent-title>
      <parent-catalog-item-type>Data Set</parent-catalog-item-type>
      <status>Completed</status>
      <abstract>The NAV_MARINE_LINE table contains the primary key - HUNUM - for the vector lines depicting  locations of shipping lanes  in South Carolina. 

The HUNUM links to all attribute information stored in the SOURCES and SOCECON tables, described below. See the Browse_Graphic section for a link to the entity-relationship diagram, which describes the relationships between attribute tables in the ESI data structure.</abstract>
      <purpose>The ESI data are intended to provide baseline environmental data for oil spill planning and response. The Clean Water Act with amendments by the Oil Pollution Act of 1990 requires response plans for immediate and effective protection of sensitive resources. The ESI data may be appropriate for many other coastal management efforts, though the original intent should be kept in mind.</purpose>
      <notes>Converted from FGDC using 'fgdc_to_inport_xml_entity.pl' script.</notes>
   </item-identification>
   <data-attributes>
      <data-attribute cc-id="824606">
         <seq-order>1</seq-order>
         <name>TYPE</name>
         <data-storage-type>TEXT</data-storage-type>
         <max-length>4</max-length>
         <required>Yes</required>
         <primary-key>No</primary-key>
         <status>Active</status>
         <description>The human-use features depicted on the maps are those that could be impacted by an oil spill or could provide access for response operations. TYPE can be used as a quick identifier for the socioeconomic or human-use point features and is the attribute that is used to symbolize the layer. Greater detail about the object is provided in the SOC_DAT table. | Description Source: NOAA ESI Guidelines</description>
         <allowed-values>SL: shipping lane</allowed-values>
      </data-attribute>
      <data-attribute cc-id="824605">
         <seq-order>2</seq-order>
         <name>HUNUM</name>
         <data-storage-type>NUMBER</data-storage-type>
         <max-length>8</max-length>
         <required>Yes</required>
         <primary-key>Yes</primary-key>
         <status>Active</status>
         <description>An 8-digit identifier that links the SOCECON points to their related attributes in the SOC_DAT table. | Description Source: NOAA ESI Guidelines</description>
         <allowed-values>23400001- 23401943</allowed-values>
      </data-attribute>
   </data-attributes>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:55607</guid>
      <metadata-record-created-by pers-id="20377">Jill Petersen</metadata-record-created-by>
      <metadata-record-created>2019-02-25T12:56:31</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:47</metadata-record-last-modified>
      <record-published>2019-02-26</record-published>
      <owner-organization>Office of Response and Restoration</owner-organization>
      <owner-organization-acronym>ORR</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>
      <is-do-not-publish>No</is-do-not-publish>
      <metadata-last-review-date>2019-02-26</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2020-02-26</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
