<?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>40485</catalog-item-id>
      <title>North Slope, Alaska: SOCECON (Socioeconomic Resource Points and Lines)</title>
      <short-name>N_Slope_socecon</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>46680</parent-catalog-item-id>
      <parent-title>North Slope, 2005</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <publication-date>2005-06</publication-date>
      <abstract>This data set contains data for airports (including airfields, landing strips, helipads, etc., whether they are manned or unmanned), roads, pipelines, and the US/Canadian border for the North Slope of Alaska.  Vector points and lines in this data set represent human-use site locations.  Location-specific type and source information is stored in relational data tables (described below) designed to be used in conjunction with this spatial data layer.This data set comprises a portion of the Environmental Sensitivity Index (ESI) data for North Slope, Alaska.  ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil.  The ESI data include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources. See also the MGT (Management Area Polygons) data layer, part of the larger North Slope, Alaska ESI database, for additional human-use information.</abstract>
      <purpose>The ESI data were collected, mapped, and digitized to provide 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.</purpose>
      <notes>2048</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, Hazardous Materials Response Division, Seattle, Washington and Anchorage, Alaska; NOAA Fisheries, Alaska Region; Oil Spill Recovery Institute, Cordova, Alaska; Alaska CHADUX Corporation, Anchorage, Alaska; Alaska Clean Seas, Deadhorse, Alaska; and Minerals Management Service, Anchorage, Alaska.</other-citation-details>
      <supplemental-information>Resource Description - ESI Atlas for North Slope, Alaska</supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>environment</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>oceans</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <thesaurus>NOS Topic Category</thesaurus>
         <keyword>Environmental Monitoring</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>Human Use Resource</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>Sensitivity maps</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Socioeconomic Resource</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Wildlife</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Spatial</keyword-type>
         <keyword>North Slope, Alaska</keyword>
      </keyword>
   </keywords>
   <physical-location>
      <organization>Office of Response and Restoration</organization>
      <city>Silver Spring</city>
      <state-province>MD</state-province>
   </physical-location>
   <data-set-information>
      <data-set-scope-code>Data Set</data-set-scope-code>
      <maintenance-frequency>None Planned</maintenance-frequency>
      <data-presentation-form>vector digital data</data-presentation-form>
      <entity-attribute-overview>In addition to the geographic data layers, two relational attribute or data tables, SOC_DAT, and SOURCES, are used to store the complex socioeconomic data in the ESI data structure.  The geographic data layer containing socioeconomic data resource information (in this case, SOCECON) is linked to the Socioeconomic Resources table (SOC_DAT) using the unique ID and the lookup table SOC_LUT, or it can be linked directly using HUNUM. HUNUM is a unique reference number concatenated with the atlas number (for North Slope, the number is 75).  ID is a unique combination of the atlas number (75), an element specific number (SOCECON = 10), and a unique record number.  SOC_DAT and the other relational data tables are described below in detail.  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>Unknown</entity-attribute-detail-citation>
      <distribution-liability>Although these data have been processed 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, Office of Response and Restoration, Hazardous Materials Response Division, Seattle, Washington and Anchorage, Alaska; NOAA Fisheries, Alaska Region; Oil Spill Recovery Institute, Cordova, Alaska; Alaska CHADUX Corporation, Anchorage, Alaska; Alaska Clean Seas, Deadhorse, Alaska; and Minerals Management Service, Anchorage, Alaska.</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="5">
      <entity>
         <item-identification>
            <catalog-item-id>44086</catalog-item-id>
            <title>SOCECON.AAT</title>
            <short-name>SOCECON.AAT</short-name>
            <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
            <status>Completed</status>
            <abstract>The SOCECON.AAT table contains attribute information for the vector lines representing roads, pipelines, and the U.S./Canadian border. Note that all attribute information is stored in a series of relational files, 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: Research Planning, Inc.</abstract>
            <notes>Converted from FGDC using 'fgdc_to_inport_xml_entity.pl' script.</notes>
         </item-identification>
         <data-attributes partial-listing="No" total-count="1">
            <data-attribute cc-id="552138">
               <seq-order>1</seq-order>
               <name>TYPE</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <required>No</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: Research Planning, Inc.</description>
               <allowed-values>AB: Area Boundary | PL: Pipeline | R: Road, Transportation, or Bridge |</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
      <entity>
         <item-identification>
            <catalog-item-id>44087</catalog-item-id>
            <title>SOCECON.PAT</title>
            <short-name>SOCECON.PAT</short-name>
            <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
            <status>Completed</status>
            <abstract>The SOCECON.PAT table contains attribute information for the vector points representing airport locations.  Note that all attribute information is stored in a series of relational files, 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: Research Planning, Inc.</abstract>
            <notes>Converted from FGDC using 'fgdc_to_inport_xml_entity.pl' script.</notes>
         </item-identification>
         <data-attributes partial-listing="No" total-count="3">
            <data-attribute cc-id="552139">
               <seq-order>1</seq-order>
               <name>TYPE</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <required>No</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: Research Planning, Inc.</description>
               <allowed-values>A: Airport |</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552140">
               <seq-order>2</seq-order>
               <name>ID</name>
               <data-storage-type>NUMBER</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>An identifier that links vector objects in the human-use data layers to records in the SOC_LUT data table.  ID is a concatenation of atlas number (75), element number (10), and record number. | Description Source: NOAA</description>
               <allowed-values>751000001 - 751000007</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552141">
               <seq-order>3</seq-order>
               <name>HUNUM</name>
               <data-storage-type>NUMBER</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>An identifier that links directly to the SOC_DAT table. | Description Source: NOAA</description>
               <allowed-values>75000001 - 75000001</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
      <entity>
         <item-identification>
            <catalog-item-id>44088</catalog-item-id>
            <title>SOC_LUT</title>
            <short-name>SOC_LUT</short-name>
            <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
            <status>Completed</status>
            <abstract>The data table SOC_LUT is a lookup table that contains items necessary for linking vector objects in the human-use data layers with the SOC_DAT 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: Research Planning, Inc.</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="552142">
               <seq-order>1</seq-order>
               <name>HUNUM</name>
               <data-storage-type>NUMBER</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>An identifier that links records in the SOC_LUT data table to records in the SOC_DAT data table.  HUNUM values of 0 are holes in polygons and do not contain information. | Description Source: NOAA</description>
               <allowed-values>75000001 - 75000010</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552143">
               <seq-order>2</seq-order>
               <name>ID</name>
               <data-storage-type>NUMBER</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>An identifier that links vector objects in the human-use data layers to records in the SOC_LUT data table.  ID is a concatenation of atlas number (75), element number (SOCECON=10; MGT=11), and record number.  ID values of 9999 are holes in polygons and do not contain information. | Description Source: NOAA</description>
               <allowed-values>751000001 - 751000010</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
      <entity>
         <item-identification>
            <catalog-item-id>44089</catalog-item-id>
            <title>SOC_DAT</title>
            <short-name>SOC_DAT</short-name>
            <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: Research Planning, Inc.</abstract>
            <notes>Converted from FGDC using 'fgdc_to_inport_xml_entity.pl' script.</notes>
         </item-identification>
         <data-attributes partial-listing="No" total-count="7">
            <data-attribute cc-id="552144">
               <seq-order>1</seq-order>
               <name>HUNUM</name>
               <data-storage-type>NUMBER</data-storage-type>
               <required>No</required>
               <primary-key>No</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>75000001 - 75000010</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552145">
               <seq-order>2</seq-order>
               <name>TYPE</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Identifies the feature type | Description Source: Research Planning, Inc.</description>
               <allowed-values>AIRPORT: Airport | CRITICAL HABITAT: Designated Critical Habitat | MANAGEMENT AREA: Management Area | NATIONAL PARK: National Park | WILDLIFE REFUGE: Wildlife Refuge |</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552146">
               <seq-order>3</seq-order>
               <name>NAME</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>The feature name. | Description Source: Research Planning, Inc.</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552147">
               <seq-order>4</seq-order>
               <name>CONTACT</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Contact person or entity. | Description Source: Research Planning, Inc.</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552148">
               <seq-order>5</seq-order>
               <name>PHONE</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Contact telephone number. | Description Source: Research Planning, Inc.</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552149">
               <seq-order>6</seq-order>
               <name>G_SOURCE</name>
               <data-storage-type>NUMBER</data-storage-type>
               <required>No</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: Research Planning, Inc.</description>
               <allowed-values>1 - N</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552150">
               <seq-order>7</seq-order>
               <name>A_SOURCE</name>
               <data-storage-type>NUMBER</data-storage-type>
               <required>No</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: Research Planning, Inc.</description>
               <allowed-values>1 - N</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
      <entity>
         <item-identification>
            <catalog-item-id>44090</catalog-item-id>
            <title>SOURCES</title>
            <short-name>SOURCES</short-name>
            <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: Research Planning, Inc.</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="552151">
               <seq-order>1</seq-order>
               <name>SOURCE_ID</name>
               <data-storage-type>NUMBER</data-storage-type>
               <required>No</required>
               <primary-key>No</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, and to G_SOURCE and S_SOURCE in the BIORES table. | Description Source: Research Planning, Inc.</description>
               <allowed-values>1 - N</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552152">
               <seq-order>2</seq-order>
               <name>ORIGINATOR</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Author or developer of source material or data set. | Description Source: Research Planning, Inc.</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552153">
               <seq-order>3</seq-order>
               <name>DATE_PUB</name>
               <data-storage-type>VARCHAR</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: Research Planning, Inc.</description>
               <allowed-values>YYYYMM: YYYY for year and optionally MM for month |</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552154">
               <seq-order>4</seq-order>
               <name>TITLE</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Title of source material or data. | Description Source: Research Planning, Inc.</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552155">
               <seq-order>5</seq-order>
               <name>DATA_FORMAT</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>The format of the source material. | Description Source: Research Planning, Inc.</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552156">
               <seq-order>6</seq-order>
               <name>PUBLICATION</name>
               <data-storage-type>Unknown</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Additional citation information. | Description Source: Research Planning, Inc.</description>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552157">
               <seq-order>7</seq-order>
               <name>SCALE</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <required>No</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>Scale denominator of the source. | Description Source: Research Planning, Inc.</description>
               <allowed-values>integer: Any integer |</allowed-values>
            </data-attribute>
            <data-attribute cc-id="552158">
               <seq-order>8</seq-order>
               <name>TIME_PERIOD</name>
               <data-storage-type>VARCHAR</data-storage-type>
               <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: Research Planning, Inc.</description>
               <allowed-values>YYYY: Year | VARIES: Date information varies |</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
   </entity-attribute-information>
   <support-roles>
      <support-role cc-id="512612" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2005-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="512614" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2005-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="512615" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2005-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="512613" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2005-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>The SOCECON data were compiled during 2003-2004.  The currentness dates for the data range from 1995 to 2003 and are documented in the Lineage section.</currentness-reference>
      <extent cc-id="512616">
         <geographic-areas>
            <geographic-area cc-id="512618">
               <west-bound>-168</west-bound>
               <east-bound>-140.8</east-bound>
               <north-bound>72</north-bound>
               <south-bound>68</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="512617">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>1995</start-date-time>
               <end-date-time>2003</end-date-time>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <vector>Yes</vector>
         </representations-used>
         <vector-representations>
            <vector-representation cc-id="588949">
               <curve-object>
                  <present>Yes</present>
                  <count>5169</count>
               </curve-object>
               <point-object>
                  <present>Yes</present>
                  <count>7</count>
               </point-object>
               <surface-object>
                  <present>Yes</present>
                  <count>1378</count>
               </surface-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>Contact NOAA for distribution options (see Distributor).  ESI data are processed into multiple formats to make them useful to a wider community of GIS/mapping users.  Distribution formats include ARC export, MOSS and Shape files, and MARPLOT map folders.  An ArcView ESI project and ESI_Viewer product are also included on the distribution CDs for ease of use of the ESI data.  The database files are distributed both in the NOAA standard relational database format (see NOAA Technical Memorandum NOS ORCA 115) and in a simplified desktop flat file format.  This metadata document includes information on both of these database formats.;</data-access-procedure>
      <data-access-constraints>None</data-access-constraints>
      <data-use-constraints>DO NOT USE MAPS FOR NAVIGATIONAL PURPOSES.Besides the above warning, there are no use constraints on these data.  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.  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="1383321">
         <download-url>https://response.restoration.noaa.gov/oil-and-chemical-spills/oil-spills/download-esi-maps-and-gis-data</download-url>
         <distributor cc-id="512614">
            <from-date>2005-06</from-date>
            <contact-type>Position</contact-type>
            <contact-name>ESI Program Manager</contact-name>
         </distributor>
         <file-name>NorthSlope_2005_GDB.zip</file-name>
         <distribution-format>ESRI File Geodatabase</distribution-format>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="512610">
         <url>https://response.restoration.noaa.gov/esi</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="512632">
         <activity-date-time>2005-06</activity-date-time>
         <description>Date that the source FGDC record was last modified.</description>
      </activity-log>
      <activity-log cc-id="512631">
         <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="588655">
         <activity-date-time>2017-09-13</activity-date-time>
         <description>Partial upload of Spatial Info section only.</description>
      </activity-log>
      <activity-log cc-id="588948">
         <activity-date-time>2017-09-13</activity-date-time>
         <description>Partial upload of Spatial Info section only.</description>
      </activity-log>
      <activity-log cc-id="604529">
         <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="719307">
         <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 packages used to develop the atlas are Environmental Systems Research Institute's ARC/INFO(r) (version 8.3) and SQL SERVER(r) (version 7.0).  The hardware configuration is PC's with Windows Operating System (NT4.0/2000).The Spatial_Data_Organization Information section refers only to the source files in the ARC export format.  The following files are included in the data set: bioindex.e00, birds.e00, esi.e00, facility.e00, fish.e00, fishl.e00, habitats.e00, hydro.e00, index.e00, m_mammal.e00, mgt.e00, nests.e00, socecon.e00, t_mammal.e00.   Associated relational and desktop data tables provided in Arc export and text format are bio_lut, biofile, biores, breed, breed_dt, seasonal, soc_dat, soc_lut, sources, species, and status.</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, hardcopy 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, hardcopy, or digital sources.  Most of the spatial components of the human-use data layers are developed from pre-existing digital or hardcopy sources and reflect the positional accuracy of these original data.  Some of the spatial components of the human-use data layers are compiled on hardcopy base maps with a scale of 1:250,000.  See the Lineage and Process_Description sections for more information on the original data source 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 digital data on socioeconomic resources.  These data do not necessarily represent all human-use sites in North Slope, Alaska. See also the MGT (Management Area Polygons) data layer, part of the larger North Slope, Alaska ESI database, for additional human-use information.</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 (such as dangles, unnecessary node, etc.), and SQL SERVER(r) to ARC/INFO(r) consistencies.  A final review is made by the GIS manager, where the data are written to CD-ROM and the metadata are written.After the data are delivered to NOAA, they are again subjected to a number of quality and consistency checks.  In the process of checking for topological and database consistencies, new ID's and RARNUM's or HUNUM's are also generated.  The new ID's are a combination of atlas number, element number, and record number. In addition, the value used to represent the element is modified to reflect the type of feature being mapped. In the case of an element that is normally represented by a point or polygon, a value of 20 is added to the standard element value for mapping of linear features.  In the case where an element usually mapped as a polygon is represented by a point, a value of 30 is added to the regular element value. The RARNUM's are also modified to include the atlas number, so multiple atlases can be combined and RARNUM's remain unique. RARNUM's are redefined on an element basis, so "resource at risk" groupings will contain only a single element. HUNUM's are also modified to include the atlas number.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-sources>
         <lineage-source cc-id="604530">
            <citation-title>NORTH SLOPE ALASKA OIL FIELD INFRASTRUCTURE</citation-title>
            <contact-name>BPXA</contact-name>
            <publish-date>2003-01-01</publish-date>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2003</extent-start-date-time>
            <scale-denominator>63360</scale-denominator>
            <source-contribution>SOCECON INFORMATION | Source Geospatial Form: DIGITAL VECTOR DATA | Type of Source Media: online</source-contribution>
         </lineage-source>
         <lineage-source cc-id="604531">
            <citation-title>TOPOGRAPHIC QUADRANGLES</citation-title>
            <contact-name>U.S. GEOLOGICAL SURVEY (USGS)</contact-name>
            <scale-denominator>63360</scale-denominator>
            <source-contribution>SOCECON INFORMATION | Source Geospatial Form: HARDCOPY MAP | Type of Source Media: paper</source-contribution>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="604532">
            <sequence-number>1</sequence-number>
            <description>Two main sources of data were used to depict human-use resources for this data layer: (1) 2003 BP Exploration (Alaska) Inc. (BPXA) digital vector data of oil field infrastructure (pipelines and roads), and (2) USGS Topographic quadrangles for airports and landing strips.The above digital and/or hardcopy sources were compiled by the project biologist to create the SOCECON data layer. Depending on the type of source data, three general approaches are used for compiling a human-use data layer: (1) information gathered during initial interviews and from hardcopy sources are compiled onto U.S. Geological Survey 1:250,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 compiled ESI, biology, and human-use data are plotted onto hardcopy draft maps.  Following the delivery of draft maps to the participating resource experts, a second set of interviews are conducted to review the maps.  If necessary, edits to the SOCECON data layer are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.</description>
            <process-date-time>2005-01-01T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <child-items>
      <child-item>
         <catalog-item-id>44086</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>SOCECON.AAT</title>
      </child-item>
      <child-item>
         <catalog-item-id>44087</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>SOCECON.PAT</title>
      </child-item>
      <child-item>
         <catalog-item-id>44089</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>SOC_DAT</title>
      </child-item>
      <child-item>
         <catalog-item-id>44088</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>SOC_LUT</title>
      </child-item>
      <child-item>
         <catalog-item-id>44090</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>SOURCES</title>
      </child-item>
   </child-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:40485</guid>
      <metadata-record-created-by pers-id="18149">Tyler Christensen</metadata-record-created-by>
      <metadata-record-created>2017-04-05T14:52:02</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:03</metadata-record-last-modified>
      <record-published>2018-02-08</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>2018-02-08</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2019-02-08</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
