<?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>55092</catalog-item-id>
      <title>Georgia 2015 ESI POLITICAL-JURISDICTIONAL Polygons, Points</title>
      <short-name>Georgia 2015 ESI POLITICAL-JURISDICTIONAL Polygons, Points</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>53953</parent-catalog-item-id>
      <parent-title>Georgia, 2015</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <publication-date>2015-06</publication-date>
      <abstract>This data set contains vector polygons depicting U.S. Army Corps of Engineers (USACE) jurisdictional boundaries, U.S. Coast Guard (USCG) districts and divisions, county boundaries, U.S. Environmental Protection Agency (USEPA) jurisdictional regions, and Federal Emergency Management Agency (FEMA) jurisdictional regions; and vector points depicting locations of Coast Guard facilities, in Georgia.

As a whole, the ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil, and include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources. The entirety of the ESI Human-Use data layers consists of: PARKS-MANAGED AREAS Polygons, Points; NAVIGATION-MARINE Polygons, Points, Lines; POLITICAL-JURISDICTIONAL Polygons, Points; RESOURCE MANAGEMENT Polygons, Points; SOCECON Polygons, Points, Lines; and NATURAL HAZARD Polygons.</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>1779</notes>
      <other-citation-details>Prepared by Research Planning, Inc., Columbia, South Carolina for the National Oceanic and Atmospheric Administration (NOAA), National Ocean Service, Office of Response and Restoration, Emergency Response Division, Seattle, Washington.</other-citation-details>
   </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="1ae304de-252c-45da-8dd8-df99a281e4f4">EARTH SCIENCE &gt; HUMAN DIMENSIONS &gt; BOUNDARIES &gt; ADMINISTRATIVE DIVISIONS</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="82c3689a-6bbf-496f-b118-b6ab46a9d2c7">EARTH SCIENCE &gt; HUMAN DIMENSIONS &gt; ENVIRONMENTAL IMPACTS &gt; OIL SPILLS</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>environment</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>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="a4202721-0cba-4fa1-853f-890f146b04f9">OCEAN &gt; ATLANTIC OCEAN &gt; NORTH ATLANTIC OCEAN</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Coastal Zone Management</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Coastal resources</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>ESI</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Environmental Monitoring</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Human use resources</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Management Areas</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Oil spill planning</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Political/Jurisdicitional</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Sensitivity maps</keyword>
      </keyword>
   </keywords>
   <physical-location>
      <organization>Office of Response and Restoration</organization>
      <city>Seattle</city>
      <state-province>WA</state-province>
      <country>USA</country>
   </physical-location>
   <data-set-information>
      <data-set-scope-code>Data Set</data-set-scope-code>
      <data-set-type>GIS Files</data-set-type>
      <maintenance-frequency>As Needed</maintenance-frequency>
      <maintenance-note>Data content is considered static once published. However, if issues with the Geodatabase linkages or table contents are identified, the Geodatabase and/or the associated Map Document may be updated. Assure most current data is being used by downloading from https://response.restoration.noaa.gov/esi_download and/or comparing modification dates provided at this site.</maintenance-note>
      <data-presentation-form>Map (digital)</data-presentation-form>
      <entity-attribute-overview>In addition to the geographic data layers, two associated data tables, SOC_DAT and SOURCES, are used to store the complex socioeconomic data in the ESI data structure. The geographic data layer(s) containing socioeconomic data resource information (in this case, POLITICAL_POLYS, and POLITICAL_POINTS) is linked to the Socioeconomic Resources table (SOC_DAT) using HUNUM. HUNUM is a unique reference number concatenated with the atlas number (for Georgia, the number is 236). SOC_DAT and the associated data tables are described in detail in this document. See the Browse_Graphic section for a link to the entity-relationship diagram, which describes the way these tables relate to the geographic data layers and other attribute tables in the ESI data structure.</entity-attribute-overview>
      <entity-attribute-detail-citation>NOAA ESI Guidelines</entity-attribute-detail-citation>
      <entity-attribute-detail-url>https://response.restoration.noaa.gov/esi_guidelines</entity-attribute-detail-url>
      <distribution-liability>Although these data have been processed and used successfully on a computer system at the National Oceanic and Atmospheric Administration, no warranty, expressed or implied, is made by NOAA regarding the utility of the data on any other system, nor shall the act of distribution constitute any such warranty. NOAA warrants the delivery of this product in computer-readable format, and will offer a replacement copy of the product when the product is determined unreadable by computer input peripherals, or when the physical medium is delivered in damaged condition.</distribution-liability>
      <data-set-credit>This project was supported by the National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Office of Response and Restoration (OR&amp;R), Emergency Response Division (ERD), Seattle, Washington.</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="4">
      <entity>
         <item-identification>
            <catalog-item-id>55096</catalog-item-id>
            <title>SOURCES</title>
            <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
            <status>Completed</status>
            <abstract>The data table SOURCES contains the primary sources used to create the ESI data set.  See the Browse_Graphic section for a link to the entity-relationship diagram, which describes the way this table relates to other attribute tables in the ESI data structure. | Description Source: NOAA ESI Guidelines</abstract>
         </item-identification>
         <data-attributes partial-listing="No" total-count="11">
            <data-attribute cc-id="805376">
               <seq-order>1</seq-order>
               <name>SOURCE_ID</name>
               <data-storage-type>NUMBER</data-storage-type>
               <max-length>8</max-length>
               <min-length>8</min-length>
               <required>Yes</required>
               <primary-key>Yes</primary-key>
               <status>Active</status>
               <description>Source identifier that links records in the SOURCES data table to the items G_SOURCE and A_SOURCE in the SOC_DAT table; G_SOURCE and S_SOURCE in the BIORES table; and SOURCE_ID and ESI_Source in the ESI and HYDRO data layers. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>23600001-23600509</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805371">
               <seq-order>2</seq-order>
               <name>ORIGINATOR</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>255</max-length>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Author or developer of source material or data set. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805369">
               <seq-order>3</seq-order>
               <name>DATE_PUB</name>
               <data-storage-type>NUMBER</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Date of source material, publication, or date of personal communication with expert source.  | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>YYYY, or YYYYMM, or YYYYMMDD, where Y=year, M=month, D=day</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805378">
               <seq-order>4</seq-order>
               <name>TITLE</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>255</max-length>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Title of source material or data. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805368">
               <seq-order>5</seq-order>
               <name>DATA_FORMAT</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>80</max-length>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>The format of the source material. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805374">
               <seq-order>6</seq-order>
               <name>PUB_PLACE</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>255</max-length>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Publication place. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805373">
               <seq-order>7</seq-order>
               <name>PUBLISHER</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>255</max-length>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Publisher. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805372">
               <seq-order>8</seq-order>
               <name>PUBLICATION</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>255</max-length>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Additional citation information. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805370">
               <seq-order>9</seq-order>
               <name>ONLINE_LINK</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>255</max-length>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>URL to the data if internet-available or to the website of the data provider | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>URL. Must be copied as is from the address bar &amp; must be fully qualified (begin with http://) &amp; contain no “&lt;” or “&gt;” characters

</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805375">
               <seq-order>10</seq-order>
               <name>SCALE</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>20</max-length>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Description of the source scale. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>Values may be numeric, such as 1:24000, or text, such as UNKNOWN (non-digital data only), or VARIES</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805377">
               <seq-order>11</seq-order>
               <name>TIME_PERIOD</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>34</max-length>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Date(s) of data collection that the source material is based upon. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>Date fields must be YYYY, or YYYYMM, or YYYYMMDD.  If date is not known or if the day is not of consequence, then it should be YYYYMM.  The same is true if month is not known or is not of consequence, you would use YYYY. The beginning and ending date range is separated by a dash (-)</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
      <entity>
         <item-identification>
            <catalog-item-id>55097</catalog-item-id>
            <title>POLITICAL_POLY</title>
            <short-name>POLITICAL_POLY</short-name>
            <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
            <status>Completed</status>
            <abstract>The POLITICAL-JURISDICTIONAL POLYS table contains the primary key - HUNUM - for the U.S. Army Corps of Engineers (USACE) jurisdictional boundaries, U.S. Coast Guard (USCG) districts and divisions, county boundaries, U.S. Environmental Protection Agency (USEPA) jurisdictional regions, and Federal Emergency Management Agency (FEMA) jurisdictional regions in Georgia. 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. | Description Source: NOAA ESI Guidelines</abstract>
            <notes>Converted from FGDC using 'fgdc_to_inport_xml_entity.pl' script.</notes>
         </item-identification>
         <data-attributes partial-listing="No" total-count="2">
            <data-attribute cc-id="805381">
               <seq-order>1</seq-order>
               <name>TYPE</name>
               <data-storage-type>VARCHAR</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. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>ACE: Army Corps of Engineers | CG: Coast Guard Station, District, or Sector | CO: County Border | EPA: EPA Regions | FEMA: FEMA Region</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805379">
               <seq-order>2</seq-order>
               <name>HUNUM</name>
               <data-storage-type>NUMBER</data-storage-type>
               <max-length>8</max-length>
               <min-length>8</min-length>
               <required>Yes</required>
               <primary-key>Yes</primary-key>
               <status>Active</status>
               <description>An 8-digit identifier that links the managed area polygons to their related attributes in the SOC_DAT table. | Description Source: NOAA</description>
               <allowed-values>23600001-23600739</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
      <entity>
         <item-identification>
            <catalog-item-id>55098</catalog-item-id>
            <title>POLITICAL_POINT</title>
            <short-name>POLITICAL_POINT</short-name>
            <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
            <status>Completed</status>
            <abstract>The POLITICAL-JURISDICTIONAL POINT table contains the primary key - HUNUM - for U.S. Coast Guard stations in Georgia. 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. | Description Source: NOAA ESI Guidelines</abstract>
            <notes>Converted from FGDC using 'fgdc_to_inport_xml_entity.pl' script.</notes>
         </item-identification>
         <data-attributes partial-listing="No" total-count="2">
            <data-attribute cc-id="805383">
               <seq-order>1</seq-order>
               <name>TYPE</name>
               <data-storage-type>VARCHAR</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. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>CG: Coast Guard Station, District, or Sector</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805382">
               <seq-order>2</seq-order>
               <name>HUNUM</name>
               <data-storage-type>NUMBER</data-storage-type>
               <max-length>8</max-length>
               <min-length>8</min-length>
               <required>Yes</required>
               <primary-key>Yes</primary-key>
               <status>Active</status>
               <description>An 8-digit identifier that links the managed area polygons to their related attributes in the SOC_DAT table. | Description Source: NOAA</description>
               <allowed-values>23600001-23600739</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
      <entity>
         <item-identification>
            <catalog-item-id>55099</catalog-item-id>
            <title>SOC_DAT</title>
            <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
            <status>Completed</status>
            <abstract>The data table SOC_DAT contains both human-use attribute data and items necessary for linking the human-use spatial data layers to the SOURCES data table. See the Browse_Graphic section for a link to the entity-relationship diagram, which describes the way this table relates to other attribute tables in the ESI data structure. | Description Source: NOAA ESI Guidelines</abstract>
         </item-identification>
         <data-attributes partial-listing="No" total-count="9">
            <data-attribute cc-id="805388">
               <seq-order>1</seq-order>
               <name>HUNUM</name>
               <data-storage-type>NUMBER</data-storage-type>
               <max-length>8</max-length>
               <min-length>8</min-length>
               <required>Yes</required>
               <primary-key>Yes</primary-key>
               <status>Active</status>
               <description>An identifier that links records in the SOC_DAT data table to records in the SOC_LUT data table. | Description Source: NOAA</description>
               <allowed-values>23600001-23600739</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805386">
               <seq-order>2</seq-order>
               <name>ELEMENT</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>10</max-length>
               <required>Yes</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Category of the human-use features. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>POLITICAL: Political/Jurisdictional management | MANAGED: Parks/Managed areas | RESOURCE: Resource management | NAT_HAZARD: Natural hazard | NAV_MARINE: Navigation/Marine - recreational/Maritime | SOCECON: Other socioeconomic features </allowed-values>
            </data-attribute>
            <data-attribute cc-id="805392">
               <seq-order>3</seq-order>
               <name>TYPE</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>35</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. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>	ABANDONED VESSEL: Abandoned Vessel | ACCESS: Access | AIRPORT: Airport | ANCHORAGE: Anchorage | ARMY CORPS OF ENGINEERS: Army Corps of Engineers | ARTIFICIAL REEF: Artificial Reef | BEACH: Beach | BOAT RAMP: Boat Ramp | COAST GUARD: Coast Guard Station, District, or Sector | COMMERCIAL FISHING: Commercial Fishing | COUNTY: County Border | CRITICAL HABITAT: Critical Habitat | EPA FACILITY: EPA Facility | EPA REGION: EPA Regions | FEMA REGION: FEMA Region | FISHERY AREA: Fishery Area | HELIPORT: Heliport | HISTORICAL SITE: Historical Site or Area | MANAGEMENT AREA: Management Area | MARINA: Marina | MARINE SANCTUARY: Marine Sanctuary | MILITARY: Military | NATIONAL ESTUARINE RESEARCH RESERVE: National Estuarine Research Reserve | NATIONAL GUARD: National Guard | NATIONAL PARK: National Park | NATURE CONSERVANCY: Nature Conservancy | PARK: Regional or State Park | PORT: Port | RAIL ROUTE: Rail Route | RECREATIONAL FISHING: Recreational Fishing | RENEWABLE ENERGY: Renewable Energy | REPEATED MEASUREMENT SITE: Repeated Measurement Site/Area | RIVER MILE: River Mile | SHIPPING LANE: Shipping Lane | WASH OVER: Wash Over | WASTE DISPOSAL: Waste Disposal | WATER INTAKE: Water Intake | WILDLIFE REFUGE: Wildlife Refuge</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805390">
               <seq-order>4</seq-order>
               <name>NAME</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>50</max-length>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>The feature name. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805385">
               <seq-order>5</seq-order>
               <name>CONTACT</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>80</max-length>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Contact person or entity. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805391">
               <seq-order>6</seq-order>
               <name>PHONE</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>12</max-length>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Contact telephone number. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>###-###-####</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805389">
               <seq-order>7</seq-order>
               <name>LINK</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <max-length>255</max-length>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Link to the resource web-page. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>URL. Must be copied as is from the address bar &amp; must be fully qualified (begin with http://) &amp; contain no “&lt;” or “&gt;” characters
</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805387">
               <seq-order>8</seq-order>
               <name>G_SOURCE</name>
               <data-storage-type>NUMBER</data-storage-type>
               <max-length>8</max-length>
               <min-length>8</min-length>
               <required>Yes</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Geographic source identifier that links records in the SOC_DAT data table to records in the SOURCES data table. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>23600001-23600509</allowed-values>
            </data-attribute>
            <data-attribute cc-id="805384">
               <seq-order>9</seq-order>
               <name>A_SOURCE</name>
               <data-storage-type>NUMBER</data-storage-type>
               <max-length>8</max-length>
               <min-length>8</min-length>
               <required>Yes</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Attribute source identifier that links records in the SOC_DAT data table to records in the SOURCES data table. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>23600001-23600509</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
   </entity-attribute-information>
   <support-roles>
      <support-role cc-id="805193" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2015-06</from-date>
         <contact-type>Position</contact-type>
         <contact-name>ESI Program Manager</contact-name>
         <contact-email>orr.esi@noaa.gov</contact-email>
         <contact-address>7600 Sand Point Way NE</contact-address>
         <contact-address-city>Seattle</contact-address-city>
         <contact-address-state>WA</contact-address-state>
         <contact-address-zip>98115</contact-address-zip>
      </support-role>
      <support-role cc-id="805195" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2015-06</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>Office of Response and Restoration</contact-name>
         <contact-noaa-acronym>ORR</contact-noaa-acronym>
         <contact-ror>https://ror.org/03g5tqa50</contact-ror>
         <contact-address>1305 East-West Highway</contact-address>
         <contact-address-city>Silver Spring</contact-address-city>
         <contact-address-state>MD</contact-address-state>
         <contact-address-zip>20910</contact-address-zip>
         <contact-url>https://response.restoration.noaa.gov/</contact-url>
         <contact-url-name>ORR Home Page </contact-url-name>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="805196" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2015-06</from-date>
         <contact-type>Position</contact-type>
         <contact-name>ESI Program Manager</contact-name>
         <contact-email>orr.esi@noaa.gov</contact-email>
         <contact-address>7600 Sand Point Way NE</contact-address>
         <contact-address-city>Seattle</contact-address-city>
         <contact-address-state>WA</contact-address-state>
         <contact-address-zip>98115</contact-address-zip>
      </support-role>
      <support-role cc-id="805194" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2015-06</from-date>
         <contact-type>Position</contact-type>
         <contact-name>ESI Program Manager</contact-name>
         <contact-email>orr.esi@noaa.gov</contact-email>
         <contact-address>7600 Sand Point Way NE</contact-address>
         <contact-address-city>Seattle</contact-address-city>
         <contact-address-state>WA</contact-address-state>
         <contact-address-zip>98115</contact-address-zip>
      </support-role>
   </support-roles>
   <extents>
      <currentness-reference>Publication Date</currentness-reference>
      <extent cc-id="805245">
         <geographic-areas>
            <geographic-area cc-id="805246">
               <west-bound>-81.8341</west-bound>
               <east-bound>-80.62</east-bound>
               <north-bound>32.3516</north-bound>
               <south-bound>30.66</south-bound>
               <description>This reflects the extent of all land and water features included in the overall Georgia ESI study region. The bounding box for this particular feature class may vary depending on occurrences identified and mapped.</description>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="805247">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2014</start-date-time>
               <end-date-time>2015</end-date-time>
               <description>Time Frame Range starts with ESI Project Start Year, and ends with ESI Atlas Publication Year.</description>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <vector>Yes</vector>
            <text-table>Yes</text-table>
         </representations-used>
         <vector-representations>
            <vector-representation cc-id="805206">
               <topology-level>Geometry Only</topology-level>
               <complex-object>
                  <present>Yes</present>
                  <count>14</count>
               </complex-object>
               <point-object>
                  <present>Yes</present>
                  <count>5</count>
               </point-object>
            </vector-representation>
         </vector-representations>
      </spatial-representation>
   </spatial-information>
   <access-information>
      <data-license-type>Standard</data-license-type>
      <data-license>CC0-1.0</data-license>
      <data-license-url>https://creativecommons.org/publicdomain/zero/1.0/</data-license-url>
      <data-license-statement>These data were produced by NOAA and are not subject to copyright protection in the United States. NOAA waives any potential copyright and related rights in these data worldwide through the Creative Commons Zero 1.0 Universal Public Domain Dedication (CC0-1.0).</data-license-statement>
      <security-class>Unclassified</security-class>
      <data-access-procedure>Data can be accessed by downloading the zipped ArcGIS geodatabase from the Download URL (see Distribution Information). Questions can be directed to the ESI Program Manager (Point Of Contact).</data-access-procedure>
      <data-access-constraints>None</data-access-constraints>
      <data-use-constraints>DO NOT USE MAPS FOR NAVIGATIONAL PURPOSES. Management boundaries are not to be considered legal boundaries. Edges may have been altered for cartographic processes. Note that the ESI database should not be used to the exclusion of other pertinent data or information held by state or federal agencies or other organizations. Likewise, information contained in the database cannot be used in place of consultations with environmental, natural resource, and cultural resource agencies, or in place of field surveys. Recognize that the information contained in the ESI database represents known concentration areas or occurrences of natural, cultural, and human-use resources, but does not necessarily represent the full distribution or range of each species or resource. This is particularly important to recognize when considering potential impacts to protected resources, such as endangered species, wetlands, etc. Besides the above warnings, there are no use constraints on these data. Acknowledgment of the originators, publishers, contributors, and sources listed would be appreciated in products derived from these data.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="805250">
         <download-url>https://response.restoration.noaa.gov/esi_download</download-url>
         <distributor cc-id="805195">
            <from-date>2015-06</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>Office of Response and Restoration</contact-name>
            <contact-ror>https://ror.org/03g5tqa50</contact-ror>
         </distributor>
         <file-name>Georgia_2015_ESI_GDB.zip</file-name>
         <description>This feature class is part of the downloadable Esri Arc Geodatabase.</description>
         <file-date-time>2016-09-12T00:00:00</file-date-time>
         <!--Note: file-type is deprecated-->
         <file-type>Arc Geodatabase</file-type>
         <distribution-format>ESRI File Geodatabase</distribution-format>
         <file-size>129 MB</file-size>
         <compression>Zip</compression>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="805249">
         <url>https://response.restoration.noaa.gov/sites/default/files/ESI-Browse-Graphic.pdf</url>
         <name>ESI Browse Graphic</name>
         <url-type>Browse Graphic</url-type>
         <file-resource-format>PDF</file-resource-format>
         <description>ESI Browse Graphic depicts the relationships between the spatial data layers and the attribute data tables for all potential ESI data layers and tables.</description>
      </url>
      <url cc-id="805197">
         <url>https://response.restoration.noaa.gov/esi</url>
         <name>ESI Overview</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>hml</file-resource-format>
         <description>Overview of ESI data content and uses.</description>
      </url>
      <url cc-id="805248">
         <url>https://response.restoration.noaa.gov/esi_guidelines</url>
         <name>ESI Guidelines</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>PDF</file-resource-format>
         <description>Guidelines for developing ESI data content and overview of ESI data structure. Useful for data collectors and users requiring more in depth information on the ESI process.</description>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="805199">
         <activity-date-time>2015-06</activity-date-time>
         <description>Date that the source FGDC record was last modified.</description>
      </activity-log>
      <activity-log cc-id="805198">
         <activity-date-time>2017-04-05</activity-date-time>
         <description>Converted from 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="805200">
         <activity-date-time>2017-09-13</activity-date-time>
         <description>Partial upload of Spatial Info section only.</description>
      </activity-log>
      <activity-log cc-id="805201">
         <activity-date-time>2017-11-01</activity-date-time>
         <description>Replaced entire Lineage section to populate new Source Contribution field.</description>
      </activity-log>
      <activity-log cc-id="805202">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
   </activity-logs>
   <technical-environment>
      <description>The software package used to develop the atlas is Environmental Systems Research Institute's ArcGIS for Desktop 10.2(R). The hardware configuration is PCs with Windows Operating System 7.</description>
   </technical-environment>
   <data-quality>
      <accuracy>	
A multi-stage error checking process is used to verify both attribute accuracy and logical consistency throughout data production. The process includes a standardized data entry methodology, data review by in-house and external resource experts, a final Quality Assurance/Quality Control (QA/QC) process, and multiple automated logical consistency checks. Quantitative data (such as densities, counts, abundances, or concentrations) provided by resource experts for inclusion in the data set may vary widely in attribute accuracy, depending upon the methodology used to collect and compile such data. For a more detailed evaluation of source data attribute accuracy, contact the sources listed in the Lineage section.</accuracy>
      <horizontal-positional-accuracy>Spatial components for the human-use data layers can come from expert interviews and digital sources. Most of the spatial components of the human-use data layers are developed from pre-existing digital sources and reflect the positional accuracy of these original data. Some of the spatial components of the human-use data layers are compiled on digital base maps with a scale of 1:24,000 or larger. See the Lineage and Process_Description sections for more information on the original source data and how these data were integrated or manipulated to create the final data set.</horizontal-positional-accuracy>
      <completeness-report>These data represent a synthesis of expert knowledge and available hardcopy reports and digital data for human-use or management features. It contains vector polygons depicting U.S. Army Corps of Engineers (USACE) jurisdictional boundaries, U.S. Coast Guard (USCG) districts and divisions, county boundaries, U.S. Environmental Protection Agency (USEPA) jurisdictional regions, and Federal Emergency Management Agency (FEMA) jurisdictional regions; and vector points depicting locations of Coast Guard facilities, in Georgia

The entirety of the ESI Human-Use data layers consists of: PARKS-MANAGED AREAS Polygons, Points; NAVIGATION-MARINE Polygons, Points, Lines; POLITICAL-JURISDICTIONAL Polygons, Points; RESOURCE MANAGEMENT Polygons, Points; SOCECON Polygons, Points, Lines; and NATURAL HAZARD Polygons.</completeness-report>
      <conceptual-consistency>A multi-stage error checking process, described in the above Attribute Accuracy Report, is used to verify both attribute accuracy and logical consistency throughout data production. This process includes multiple automated logical consistency checks that test the files for missing or duplicate data, rules for proper coding, GIS topological consistencies, and SQL SERVER(R) to ArcGIS(R) consistencies. A final review is made by the GIS manager, before the final Geodatabase and metadata are created. After the data are delivered to NOAA, they are again subjected to several consistency checks, and processed into the final delivery format.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-sources>
         <lineage-source cc-id="805811">
            <citation-title>2013 GEORGIA DEPARTMENT OF DEFENSE ANNUAL REPORT</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>GEORGIA NATIONAL GUARD</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <publish-date>2014-01-01</publish-date>
            <extent-type>Range</extent-type>
            <extent-start-date-time>2013</extent-start-date-time>
            <extent-end-date-time>2014</extent-end-date-time>
            <citation-url>http://issuu.com/georgiaguard/docs/2013annualreport/6</citation-url>
            <source-contribution>SOCECONPT INFORMATION | Source Geospatial Form: map | Type of Source Media: online</source-contribution>
         </lineage-source>
         <lineage-source cc-id="805223">
            <citation-title>COUNTY BOUNDARIES</citation-title>
            <contact-name>UNITED STATES CENSUS BUREAU</contact-name>
            <publish-date>2014-01-01</publish-date>
            <extent-type>Range</extent-type>
            <extent-start-date-time>2013</extent-start-date-time>
            <extent-end-date-time>2014</extent-end-date-time>
            <citation-url>ftp://ftp2.census.gov/geo/tiger/TIGER2014/COUNTY/</citation-url>
            <source-contribution>MGT INFORMATION | Source Geospatial Form: vector digital data | Type of Source Media: online</source-contribution>
         </lineage-source>
         <lineage-source cc-id="805226">
            <citation-title>EPA REGION BOUNDARIES, US, 2011, USEPA, SEGS</citation-title>
            <contact-name>UNITED STATES ENVIRONMENTAL PROTECTION AGENCY (USEPA)</contact-name>
            <publish-date>2013-01-01</publish-date>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2011</extent-start-date-time>
            <source-contribution>MGT INFORMATION | Source Geospatial Form: vector digital data | Type of Source Media: online</source-contribution>
         </lineage-source>
         <lineage-source cc-id="805209">
            <citation-title>FEDERAL EMERGENCY MANAGEMENT AGENCY (FEMA) REGIONS</citation-title>
            <contact-name>FEDERAL EMERGENCY MANAGEMENT AGENCY (FEMA)</contact-name>
            <publish-date>2008-01-01</publish-date>
            <extent-type>Range</extent-type>
            <extent-start-date-time>2008</extent-start-date-time>
            <extent-end-date-time>2010</extent-end-date-time>
            <citation-url>http://gis.fema.gov/DataFeeds.html</citation-url>
            <source-contribution>MGT INFORMATION | Source Geospatial Form: vector digital data | Type of Source Media: online</source-contribution>
         </lineage-source>
         <lineage-source cc-id="805220">
            <citation-title>UNITED STATES ARMY CORPS OF ENGINEERS DISTRICTS</citation-title>
            <contact-name>UNITED STATES ARMY CORPS OF ENGINEERS (USACE)</contact-name>
            <publish-date>2010-01-01</publish-date>
            <extent-type>Range</extent-type>
            <extent-start-date-time>2010</extent-start-date-time>
            <extent-end-date-time>2011</extent-end-date-time>
            <citation-url>https://www.sciencebase.gov/catalog/item/4f4e4779e4b07f02db47f17f</citation-url>
            <source-contribution>MGT INFORMATION | Source Geospatial Form: vector digital data | Type of Source Media: online</source-contribution>
         </lineage-source>
         <lineage-source cc-id="805221">
            <citation-title>UNITED STATES ARMY CORPS OF ENGINEERS DIVISION</citation-title>
            <contact-name>UNITED STATES ARMY CORPS OF ENGINEERS (USACE)</contact-name>
            <publish-date>2011-01-01</publish-date>
            <extent-type>Range</extent-type>
            <extent-start-date-time>2010</extent-start-date-time>
            <extent-end-date-time>2011</extent-end-date-time>
            <citation-url>https://www.sciencebase.gov/catalog/item/4f4e4779e4b07f02db47f46b</citation-url>
            <source-contribution>MGT INFORMATION | Source Geospatial Form: vector digital data | Type of Source Media: online</source-contribution>
         </lineage-source>
         <lineage-source cc-id="805224">
            <citation-title>UNITED STATES COAST GUARD DISTRICT BOUNDARIES</citation-title>
            <contact-name>UNITED STATES COAST GUARD (USCG)</contact-name>
            <publish-date>2010-01-01</publish-date>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2010</extent-start-date-time>
            <citation-url>https://www.sciencebase.gov/catalog/item/4f4e477ae4b07f02db47f5ba</citation-url>
            <source-contribution>MGT INFORMATION | Source Geospatial Form: vector digital data | Type of Source Media: online</source-contribution>
         </lineage-source>
         <lineage-source cc-id="805225">
            <citation-title>UNITED STATES COAST GUARD SECTOR BOUNDARIES</citation-title>
            <contact-name>UNITED STATES COAST GUARD (USCG)</contact-name>
            <publish-date>2010-01-01</publish-date>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2010</extent-start-date-time>
            <citation-url>https://www.sciencebase.gov/catalog/item/get/4f4e49b0e4b07f02db5c915e</citation-url>
            <source-contribution>MGT INFORMATION | Source Geospatial Form: vector digital data | Type of Source Media: online</source-contribution>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="805230">
            <sequence-number>1</sequence-number>
            <description>This description covers the mapping of all Socioeconomic features mapped as polygons: The mapping extent was dependent upon information availability and location of mapped coastal habitats and shorelines. Sources of data used to depict human-use resources in this data layer include digital datasets provided by the U.S. Army Corps of Engineers (USACE), U.S. Coast Guard (USCG), U.S. Fish and Wildlife Service (USFWS), NOAA, National Park Service (NPS), U.S. Census Bureau (USCB), Federal Emergency Management Agency (FEMA), U.S. Environmental Protection Agency (USEPA), The Nature Conservancy (TNC), National Estuarine Research Reserve System (NERR), Bureau of Ocean Energy Management (BOEM), and Georgia's Department of Natural Resources (GADNR) Coastal Resources Division. Critical Habitat - designated critical habitat was mapped for the piping plover, North Atlantic right whale, and loggerhead sea turtle with data downloaded from USFWS. Commercial fishing - Commercial fishing areas show where shad fishing is approved according to GADNR Coastal Resources Division. Fishery Area - Fishery areas provided by GADNR Coastal Resources Division represent recreational and commercial oyster harvest areas. Management Areas - management areas provided by GADNR Coastal Resources Division represent easements, wildlife management areas, and natural areas. Marine Sanctuary - The Gray's Reef National Marine Sanctuary (GRNMS) boundary was provided by NOAA\x92s National Marine Sanctuaries Program. National Estuarine Research Reserve (NERR) - Boundary data was provided by the Sapelo Island NERR System. National Park - Boundaries for the Cumberland Island National Seashore, Fort Frederica National Monument, and Fort Pulaski National Monument were used from the National Park boundaries dataset downloaded from http://Data.gov. Nature Conservancy - Boundaries of The Nature Conservancy (TNC) properties and easements were provided by TNC. Wildlife Refuges - USFWS National Wildlife Refuge (NWR) data were downloaded from the USFWS National Cadastral Data. Anchorage areas - anchorage areas provided by Marine Cadastre. All polygons were edited to reflect the updated ESI shoreline.</description>
            <process-date-time>2015-06-01T00:00:00</process-date-time>
            <process-contact>
               <contact-type>Position</contact-type>
               <contact-name>ESI Program Manager</contact-name>
               <contact-email>orr.esi@noaa.gov</contact-email>
               <contact-address>7600 Sand Point Way NE</contact-address>
               <contact-address-city>Seattle</contact-address-city>
               <contact-address-state>WA</contact-address-state>
               <contact-address-zip>98115</contact-address-zip>
            </process-contact>
         </lineage-process-step>
         <lineage-process-step cc-id="805808">
            <sequence-number>2</sequence-number>
            <description>This description covers all socioeconomic features mapped as lines: The mapping extent was dependent upon information availability and location of mapped coastal habitats and shorelines. The main sources of data used to depict human-use resources for this data layer were digital data sets. Rail Route data were acquired from U.S. Department of Transportations's (USDOT) National Transportation Atlas Database. Shipping Lanes in US Waters data were provided by NOAA\x92s Coastal and Marine Spatial Planning office.</description>
            <process-date-time>2015-06-01T00:00:00</process-date-time>
            <process-contact>
               <contact-type>Position</contact-type>
               <contact-name>ESI Program Manager</contact-name>
               <contact-email>orr.esi@noaa.gov</contact-email>
               <contact-address>7600 Sand Point Way NE</contact-address>
               <contact-address-city>Seattle</contact-address-city>
               <contact-address-state>WA</contact-address-state>
               <contact-address-zip>98115</contact-address-zip>
            </process-contact>
         </lineage-process-step>
         <lineage-process-step cc-id="805809">
            <sequence-number>3</sequence-number>
            <description>The following description relates to all socioeconomic data represented as points: The mapping extent was dependent upon information availability and location of mapped coastal habitats and shorelines. The main sources of data used to depict human-use resources for this data layer were digital data sets provided by the following agencies: U.S. Army Corps of Engineers (USACE), U.S. Coast Guard (USCG), U.S. Department of Transportation (USDOT), NOAA, Governors' South Atlantic Alliance (GSAA) coast and ocean portal, and Research Planning, Inc. Airports, heliports, ports, and marina data were acquired from USDOT's National Transportation Atlas Database. Known access and beach locations were compiled from NOAA's Office of Response and Restoration. Georgia Department of Natural Resources (GADNR) - Coastal Resources Division provided artificial reefs, marinas, recreational fishing, and repeated measurement sites. Governors' South Atlantic Alliance (GSAA) coast and ocean portal provided boat ramp data. USCG station and facility locations were derived from the USCG Units dataset hosted by http://sciencebase.gov. U.S. Environmental Protection Agency (USEPA) Facility (EPAF) locations represent facilities that maintain a risk management plan describing its hazards and prevention activities as required by the EPA Risk Management Plan Rule (RMP), facilities that manufacture, process, or use certain chemicals in amounts above established levels regulated by the EPA Toxic Release Inventory System (TRIS) program, facilities with permits from the National Pollutant Discharge Elimination System (NPDES), and facilities that the EPA has identified and monitors for storing certain quantities of oil (OIL). The data were provided by the USEPA to NOAA's Emergency Response Division. Historic sites were depicted from sites in the NPS National Register of Historic Places. Abandoned vessel data comes from NOAA's Office of Coast Survey Automated Wrecks and Obstructions Information System (AWOIS). Repeated measurement site (RMS) locations for marine observation sites and tide gauges were obtained through NOAA's National Data Buoy Center (NDBC), and the Center for Operational Oceanographic Products and Services (CO-OPS). Mussel Watch program RMS locations were obtained from the NOAA Chemical Impacts Team. Washover locations are represented by points that were generated by Research Planning, Inc. at a scale of 1:8,000. (A washover, or washover fan, is a relatively flat surface on the top of a barrier spit complex that slopes gently landward. It is usually created when water forced landward by breaking waves flows across the top of the barrier spit during high spring tides or storms. This process creates a flattened-off surface along which sand is transported across the top of the spit into the standing water (lagoon) or marsh landward of the spit. The resulting deposit usually has a fan-like shape.) Waste Disposal Sites were generated from Ocean Disposal Site areas to point features. Army National Guard and Air National Guard base locations were digitized as points from addresses matching and verified with Google Earth imagery by Research Planning, Inc.</description>
            <process-date-time>2015-06-01T00:00:00</process-date-time>
            <process-contact>
               <contact-type>Position</contact-type>
               <contact-name>ESI Program Manager</contact-name>
               <contact-email>orr.esi@noaa.gov</contact-email>
               <contact-address>7600 Sand Point Way NE</contact-address>
               <contact-address-city>Seattle</contact-address-city>
               <contact-address-state>WA</contact-address-state>
               <contact-address-zip>98115</contact-address-zip>
            </process-contact>
         </lineage-process-step>
         <lineage-process-step cc-id="805810">
            <sequence-number>4</sequence-number>
            <description>The above digital and/or hardcopy sources were compiled by the project biologist to create the ESI Human Use data layers. Depending on the type of source data, three general approaches are used for compiling the data layer: 1) information gathered during initial interviews and from hardcopy sources are compiled onto U.S. Geological Survey 1:24,000 topographic quadrangles and digitized; 2) hardcopy maps are digitized at their source scale; 3) digital data layers are evaluated and used "as is" or integrated with the hardcopy data sources. See the Lineage section for additional information on the type of source data for this data layer. The ESI, biology, and human-use data are compiled into the standard ESI digital data format. A second set of interviews with participating resource experts are conducted to review the compiled data. If necessary, edits to the data layers are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.</description>
            <process-date-time>2015-06-01T00:00:00</process-date-time>
            <process-contact>
               <contact-type>Position</contact-type>
               <contact-name>ESI Program Manager</contact-name>
               <contact-email>orr.esi@noaa.gov</contact-email>
               <contact-address>7600 Sand Point Way NE</contact-address>
               <contact-address-city>Seattle</contact-address-city>
               <contact-address-state>WA</contact-address-state>
               <contact-address-zip>98115</contact-address-zip>
            </process-contact>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <child-items>
      <child-item>
         <catalog-item-id>55098</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>POLITICAL_POINT</title>
      </child-item>
      <child-item>
         <catalog-item-id>55097</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>POLITICAL_POLY</title>
      </child-item>
      <child-item>
         <catalog-item-id>55099</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>SOC_DAT</title>
      </child-item>
      <child-item>
         <catalog-item-id>55096</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>SOURCES</title>
      </child-item>
   </child-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:55092</guid>
      <metadata-record-created-by pers-id="20377">Jill Petersen</metadata-record-created-by>
      <metadata-record-created>2018-12-04T16:17:00</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2026-07-09T18:26:04</metadata-record-last-modified>
      <record-published>2019-02-25</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>
      <limited-metadata-available>No</limited-metadata-available>
      <is-do-not-publish>No</is-do-not-publish>
      <metadata-last-review-date>2019-02-25</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2020-02-25</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
