<?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>55812</catalog-item-id>
      <title>NY/NJ Metro Area, Hudson River, and South Long Island 2016 ESI NAVIGATION_MARINE Lines, Points</title>
      <short-name>NY/NJ Metro Area, Hudson River, and South Long Island 2016 ESI NAVIGATION_MARINE Lines, 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>50664</parent-catalog-item-id>
      <parent-title>NY_NJ_HudsonRiver_S_LI 2016</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <publication-date>2016</publication-date>
      <abstract>This data set contains vector lines depicting shipping lanes; and vector points  depicting access sites, anchorages, boat ramps, diving sites, ferries, lock and dam sites, marinas, and ports in the New York/New Jersey Metro Area, Hudson River, and South Long Island regions.

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 NY/NJ Metro Area, Hudson River, and South Long Island Human-Use data layers consists of: PARKS-MANAGED AREAS Polygons, Points; NAVIGATION-MARINE 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>Loaded by FGDC Metadata Uploader, batch 10506, 03-06-2018 15:42

The following FGDC sections are not currently supported in InPort, but were preserved and will be included in the FGDC export:
-  Spatial Reference Information (FGDC:spref),
-  Spatial Data Organization Information (FGDC:spdoinfo)</notes>
      <other-citation-details>Prepared by Quantum Spatial Inc., Corvallis, Oregon 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="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 version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="d4313915-2d24-424c-a171-30ee9a6f4bb5">EARTH SCIENCE &gt; HUMAN DIMENSIONS &gt; INFRASTRUCTURE</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="37a6c8e2-f2ac-48a4-a4fa-d80f700f68db">EARTH SCIENCE &gt; HUMAN DIMENSIONS &gt; INFRASTRUCTURE &gt; TRANSPORTATION</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="854d0bb3-dcc3-48eb-a65a-2d26a8b87394">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA &gt; NEW YORK</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>Navigation</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/Jurisdictional</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Sensitivity maps</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Shipping Lanes</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Socioeconomic resources</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Spatial</keyword-type>
         <keyword>Hudson River</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Spatial</keyword-type>
         <keyword>South Long Island</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 containing socioeconomic data resource information (in this case, POLITICAL_JURISDICTIONAL polygons and points) are linked to the Socioeconomic Resources table (SOC_DAT) using HUNUM. HUNUM is a unique reference number concatenated with the atlas number (for NY/NJ Metro Area, Hudson River, and South Long Island, the number is 284). 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 (NOAA), 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.</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>55813</catalog-item-id>
            <title>NAV_MARINE_POINT</title>
            <short-name>NAV_MARINE_POINT</short-name>
            <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
            <status>Completed</status>
            <abstract>The NAV_MARINE_POINT table contains the primary key - HUNUM - for the vector points depicting locations of access sites, anchorages, boat ramps, diving sites, ferries, lock and dam sites, marinas, and portss in the New York/New Jersey Metro Area, Hudson River, and South Long Island regions.

The HUNUM links to all attribute information stored in the SOURCES and SOCECON tables, described below. See the Browse_Graphic section for a link to the entity-relationship diagram, which describes the relationships between attribute tables in the ESI data structure.</abstract>
            <notes>Loaded by FGDC Metadata Uploader, batch 10512, 03-06-2018 16:03</notes>
         </item-identification>
         <entity-information>
            <description>The NAV_MARINE_POINT table contains a type identifier, and links to the associated data tables housing attribute information for the vector points. The following data types were included: access sites, anchorages, boat ramps, diving sites, ferries, lock and dam sites, marinas, and ports.  Note that all attribute information is stored in the associated data 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>
         </entity-information>
         <data-attributes partial-listing="No" total-count="2">
            <data-attribute cc-id="827880">
               <seq-order>1</seq-order>
               <name>TYPE</name>
               <data-storage-type>TEXT</data-storage-type>
               <max-length>4</max-length>
               <required>Yes</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>The human-use features depicted on the maps are those that could be impacted by an oil spill or could provide access for response operations. TYPE can be used as a quick identifier for the socioeconomic or human-use point features and is the attribute that is used to symbolize the layer. Greater detail about the object is provided in the SOC_DAT table. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>A2: access | AN: anchorage | BR: boat ramp | DV: diving | F: ferry | LD: lock and dam | M: marina | PT: port</allowed-values>
            </data-attribute>
            <data-attribute cc-id="827879">
               <seq-order>2</seq-order>
               <name>HUNUM</name>
               <data-storage-type>NUMBER</data-storage-type>
               <max-length>9</max-length>
               <min-length>9</min-length>
               <required>Yes</required>
               <primary-key>Yes</primary-key>
               <status>Active</status>
               <description>A 9-digit identifier that links the SOCECON points to their related attributes in the SOC_DAT table. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>284000002-284005906</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
      <entity>
         <item-identification>
            <catalog-item-id>55814</catalog-item-id>
            <title>NAV_MARINE_LINE</title>
            <short-name>NAV_MARINE_LINE</short-name>
            <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
            <status>Completed</status>
            <abstract>The NAV_MARINE_LINE table contains the primary key - HUNUM - for the vector lines depicting locations of shipping lanes in the New York/New Jersey Metro Area, Hudson River, and South Long Island regions.

The HUNUM links to all attribute information stored in the SOURCES and SOCECON tables, described below. See the Browse_Graphic section for a link to the entity-relationship diagram, which describes the relationships between attribute tables in the ESI data structure.</abstract>
            <notes>Loaded by FGDC Metadata Uploader, batch 10512, 03-06-2018 16:03</notes>
         </item-identification>
         <entity-information>
            <description>The NAV_MARINE_LINE table contains a type identifier, and links to the associated data tables housing attribute information for the vector polygons. The following data types were included: shipping lanes. Note that all attribute information is stored in the associated data 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>
         </entity-information>
         <data-attributes partial-listing="No" total-count="2">
            <data-attribute cc-id="827882">
               <seq-order>1</seq-order>
               <name>TYPE</name>
               <data-storage-type>TEXT</data-storage-type>
               <max-length>4</max-length>
               <required>Yes</required>
               <primary-key>No</primary-key>
               <status>Active</status>
               <description>The human-use features depicted on the maps are those that could be impacted by an oil spill or could provide access for response operations. TYPE can be used as a quick identifier for the socioeconomic or human-use point features and is the attribute that is used to symbolize the layer. Greater detail about the object is provided in the SOC_DAT table. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>SL: shipping lane</allowed-values>
            </data-attribute>
            <data-attribute cc-id="827881">
               <seq-order>2</seq-order>
               <name>HUNUM</name>
               <data-storage-type>NUMBER</data-storage-type>
               <max-length>9</max-length>
               <min-length>9</min-length>
               <required>Yes</required>
               <primary-key>Yes</primary-key>
               <status>Active</status>
               <description>A 9-digit identifier that links the SOCECON points to their related attributes in the SOC_DAT table. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>284000002-284005906</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
      <entity>
         <item-identification>
            <catalog-item-id>55815</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>
            <notes>Converted from FGDC using 'fgdc_to_inport_xml_entity.pl' script.</notes>
         </item-identification>
         <data-attributes partial-listing="No" total-count="9">
            <data-attribute cc-id="827887">
               <seq-order>1</seq-order>
               <name>HUNUM</name>
               <data-storage-type>NUMBER</data-storage-type>
               <max-length>9</max-length>
               <required>Yes</required>
               <primary-key>Yes</primary-key>
               <status>Active</status>
               <description>A 9-digit identifier that links records in the SOC_DAT data table to the feature records in the vector data tables. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>284000002-284005906</allowed-values>
            </data-attribute>
            <data-attribute cc-id="827885">
               <seq-order>2</seq-order>
               <name>ELEMENT</name>
               <data-storage-type>TEXT</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>MANAGED: Managed Areas | NAT_HAZARD: Natural Hazard | NAV_MARINE: Navigational/Marine | POLITICAL: Political/Jurisdictional | RESOURCE: Resource Management | SOCECON: Socioeconomic Resources</allowed-values>
            </data-attribute>
            <data-attribute cc-id="827891">
               <seq-order>3</seq-order>
               <name>TYPE</name>
               <data-storage-type>TEXT</data-storage-type>
               <max-length>25</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, could provide access for response operations, or may themselves pose a risk for an environmentally hazardous release. | 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 | ESSENTIAL HABITAT: Essential Habitat | FEMA REGION: FEMA Region | FISHERY AREA: Fishery Area | HELIPORT: Heliport | HISTORICAL SITE: Historical Site or Area | LOCK AND DAM: Lock and Dam | MANAGEMENT AREA: Management Area | MARINA: Marina | MILITARY: Military | NATIONAL ESTUARINE RESEARCH RESERVE: National Estuarine Research Reserve | NATIONAL FOREST: National Forest | NATIONAL GUARD: National Guard | NATIONAL PARK: National Park | NATURE CONSERVANCY: Nature Conservancy | NOAA FACILITY: NOAA Facility | PARK: Regional or State Park | PORT: Port | RAIL ROUTE: Rail Route | RENEWABLE ENERGY: Renewable Energy | REPEATED MEASUREMENT SITE: Repeated Measurement Site/Area | RIVER MILE: River Mile | SHIPPING LANE: Shipping Lane | STATE WATERS: State Waters | TRIBAL LAND: Tribal Land | WASH OVER: Wash Over | WASTE DISPOSAL: Waste Disposal | WATER INTAKE: Water Intake | WILDLIFE REFUGE: Wildlife Refuge |</allowed-values>
            </data-attribute>
            <data-attribute cc-id="827889">
               <seq-order>4</seq-order>
               <name>NAME</name>
               <data-storage-type>TEXT</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="827884">
               <seq-order>5</seq-order>
               <name>CONTACT</name>
               <data-storage-type>TEXT</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="827890">
               <seq-order>6</seq-order>
               <name>PHONE</name>
               <data-storage-type>TEXT</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>xxx-xxx-xxxx</allowed-values>
            </data-attribute>
            <data-attribute cc-id="827888">
               <seq-order>7</seq-order>
               <name>LINK</name>
               <data-storage-type>TEXT</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="827886">
               <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>28400001-28400450</allowed-values>
            </data-attribute>
            <data-attribute cc-id="827883">
               <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>28400001-28400450</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
      <entity>
         <item-identification>
            <catalog-item-id>55816</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>
            <notes>Converted from FGDC using 'fgdc_to_inport_xml_entity.pl' script.</notes>
         </item-identification>
         <data-attributes partial-listing="No" total-count="11">
            <data-attribute cc-id="827900">
               <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>An 8-digit 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 BIOFILE table; SOURCE_ID and ESI_SOURCE in the ESIP and ESIL data layers, and SOURCE_ID in the HYDROL data layer. | Description Source: NOAA ESI Guidelines</description>
               <allowed-values>28400001-28400450</allowed-values>
            </data-attribute>
            <data-attribute cc-id="827895">
               <seq-order>2</seq-order>
               <name>ORIGINATOR</name>
               <data-storage-type>TEXT</data-storage-type>
               <required>Yes</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>
               <case-restriction>Upper</case-restriction>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="827893">
               <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="827902">
               <seq-order>4</seq-order>
               <name>TITLE</name>
               <data-storage-type>TEXT</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>
               <case-restriction>Upper</case-restriction>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="827892">
               <seq-order>5</seq-order>
               <name>DATA_FORMAT</name>
               <data-storage-type>TEXT</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. Examples include DOCUMENT, EXPERT KNOWLEDGE, VECTOR DIGITAL DATA...</allowed-values>
            </data-attribute>
            <data-attribute cc-id="827898">
               <seq-order>6</seq-order>
               <name>PUB_PLACE</name>
               <data-storage-type>TEXT</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>
               <case-restriction>Upper</case-restriction>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="827897">
               <seq-order>7</seq-order>
               <name>PUBLISHER</name>
               <data-storage-type>TEXT</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="827896">
               <seq-order>8</seq-order>
               <name>PUBLICATION</name>
               <data-storage-type>TEXT</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>
               <case-restriction>Upper</case-restriction>
               <allowed-values>Acceptable values change from atlas to atlas.</allowed-values>
            </data-attribute>
            <data-attribute cc-id="827894">
               <seq-order>9</seq-order>
               <name>ONLINE_LINK</name>
               <data-storage-type>TEXT</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="827899">
               <seq-order>10</seq-order>
               <name>SCALE</name>
               <data-storage-type>TEXT</data-storage-type>
               <max-length>10</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="827901">
               <seq-order>11</seq-order>
               <name>TIME_PERIOD</name>
               <data-storage-type>TEXT</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. The beginning and ending date range is separated by a dash (-)</allowed-values>
            </data-attribute>
         </data-attributes>
      </entity>
   </entity-attribute-information>
   <support-roles>
      <support-role cc-id="827824" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2016</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="827825" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2016</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="827826" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2016</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="827827" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2016</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="827853">
         <geographic-areas>
            <geographic-area cc-id="827855">
               <west-bound>-74.595</west-bound>
               <east-bound>-71.7215</east-bound>
               <north-bound>42.8226</north-bound>
               <south-bound>39.9993</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="827854">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2014</start-date-time>
               <end-date-time>2016</end-date-time>
            </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="827835">
               <topology-level>Geometry Only</topology-level>
               <curve-object>
                  <present>Yes</present>
                  <count>468</count>
               </curve-object>
               <point-object>
                  <present>Yes</present>
                  <count>70</count>
               </point-object>
            </vector-representation>
         </vector-representations>
      </spatial-representation>
      <reference-systems>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Geographic 2D</crs-type>
               <epsg-code>EPSG:4269</epsg-code>
               <epsg-name>NAD83</epsg-name>
               <datum-name>North American Datum 1983</datum-name>
               <ellipsoid>GRS 1980</ellipsoid>
               <semimajor-axis>6378137</semimajor-axis>
               <flattening-ratio>298.257222101</flattening-ratio>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Geodetic Latitude</name>
                     <abbreviation>Lat</abbreviation>
                     <units>degree</units>
                     <orientation>north</orientation>
                  </axis>
                  <axis>
                     <order>1</order>
                     <name>Geodetic Latitude</name>
                     <abbreviation>Lat</abbreviation>
                     <units>degree</units>
                     <orientation>north</orientation>
                  </axis>
                  <axis>
                     <order>2</order>
                     <name>Geodetic Longitude</name>
                     <abbreviation>Lon</abbreviation>
                     <units>degree</units>
                     <orientation>east</orientation>
                  </axis>
                  <axis>
                     <order>2</order>
                     <name>Geodetic Longitude</name>
                     <abbreviation>Lon</abbreviation>
                     <units>degree</units>
                     <orientation>east</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
      </reference-systems>
   </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="827828">
         <download-url>https://response.restoration.noaa.gov/esi_download</download-url>
         <distributor cc-id="827825">
            <from-date>2016</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>NY_NJ_2016_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>64 MB</file-size>
         <compression>Zip</compression>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="827829">
         <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>Depicts the relationships between the spatial data layers and the attribute data tables for the NY/NJ Metro Area, Hudson River, and South Long Island ESI data.</description>
      </url>
      <url cc-id="827830">
         <url>https://response.restoration.noaa.gov/esi</url>
         <name>ESI Overview</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>html</file-resource-format>
         <description>Overview of ESI data content and uses.</description>
      </url>
      <url cc-id="827831">
         <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>
   <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 lines depicting shipping lanes, and vector points depicting  access sites, anchorages, boat ramps, diving sites, ferries, lock and dam sites, marinas, and ports in the New York/New Jersey Metro Area, Hudson River, and South Long Island regions.

For additional human-use information, see other feature class themes within the SOCECON Directory, including PARKS/MANAGED AREAS (POLYGONS), NAVIGATION/MARINE (POINTS and LINES), POLITICAL/JURISDICTIONAL (POLYGONS and POINTS), RESOURCE MANAGEMENT (POLYGONS and POINTS), SOCEON (POLYGONS, LINES and POINTS), and NAT_HAZARD (POLYGONS) data layers 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, 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="827861">
            <citation-title>ACCESSIBLE RECREATION DESTINATIONS</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>NEW YORK STATE DEPARTMENT OF ENVIRONMENTAL CONSERVATION</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2009</extent-start-date-time>
            <citation-url>http://WWW.NYSGIS.STATE.NY.US/GISDATA/INVENTORIES/DETAILS.CFM?DSID=1201</citation-url>
         </lineage-source>
         <lineage-source cc-id="827860">
            <citation-title>DEEPWATER PORTS IN US WATERS AS OF AUGUST 2013</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>DEPARTMENT OF COMMERCE, NATIONAL OCEANIC AND ATMOSPHERIC ADMINISTRATION, NATIONAL OCEAN SERVICE, COASTAL SERVICES CENTER</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2013</extent-start-date-time>
            <scale-denominator>80000</scale-denominator>
            <citation-url>http://MARINECADASTRE.GOV/DATA/</citation-url>
         </lineage-source>
         <lineage-source cc-id="827862">
            <citation-title>DLF.DECLANDS</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>NEW YORK STATE DEPARTMENT OF ENVIRONMENTAL CONSERVATION</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2012</extent-start-date-time>
            <scale-denominator>24000</scale-denominator>
            <citation-url>http://GIS.NY.GOV/GISDATA/INVENTORIES/DETAILS.CFM?DSID=1114</citation-url>
         </lineage-source>
         <lineage-source cc-id="827863">
            <citation-title>FACILITIES</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>NYC DEPARTMENT OF CITY PLANNING </contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>http://WWW.NYC.GOV/HTML/DCP/HTML/BYTES/APPLBYTE.SHTML#TOP1</citation-url>
         </lineage-source>
         <lineage-source cc-id="827864">
            <citation-title>HUDSON RIVER BOAT AND YACHT CLUBS</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>HUDSON RIVER BOAT AND YACHT CLUBS</contact-name>
            <contact-role-type>Originator</contact-role-type>
         </lineage-source>
         <lineage-source cc-id="827865">
            <citation-title>INVENTORY OF DAMS - NEW YORK STATE (NYSDEC)</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>NEW YORK STATE DEPARTMENT OF ENVIRONMENTAL CONSERVATION, DIVISION OF WATER, DAM SAFETY SECTION</contact-name>
            <contact-role-type>Publisher</contact-role-type>
         </lineage-source>
         <lineage-source cc-id="827866">
            <citation-title>KAYAKING LAUNCH SITES</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>NATIONAL PARK SERVICE</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2009</extent-start-date-time>
         </lineage-source>
         <lineage-source cc-id="827867">
            <citation-title>MARINA SITES</citation-title>
            <contact-type>Person</contact-type>
            <contact-name>PETER CUNNINGHAM</contact-name>
            <contact-role-type>Originator</contact-role-type>
         </lineage-source>
         <lineage-source cc-id="827868">
            <citation-title>MID ATLANTIC COASTAL AND OCEAN RECREATION STUDY - UNDERWATER-BASED ACTIVITIES</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>POINT 97, SURFRIDER FOUNDATION, URBAN COAST INSTITUTE AT MONMOUTH UNIVERSITY, AND THE NATURE CONSERVANCY</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>http://PORTAL.MIDATLANTICOCEAN.ORG/DATA-CATALOG/RECREATION/</citation-url>
         </lineage-source>
         <lineage-source cc-id="827869">
            <citation-title>MOHAWK HUDSON COUNCIL OF YACHT CLUBS</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>MOHAWK HUDSON COUNCIL OF YACHT CLUBS</contact-name>
            <contact-role-type>Originator</contact-role-type>
         </lineage-source>
         <lineage-source cc-id="827870">
            <citation-title>NATIONAL WATERWAY NETWORK</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>VANDERBILT ENGINEERING CENTER FOR TRANSPORTATION OPERATIONS AND RESEARCH, VANDERBILT UNIVERSITY</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <extent-type>Range</extent-type>
            <extent-start-date-time>1994</extent-start-date-time>
            <extent-end-date-time>2013</extent-end-date-time>
            <citation-url>http://WWW.NAVIGATIONDATACENTER.US/DATA/DATANWN.HTM</citation-url>
         </lineage-source>
         <lineage-source cc-id="827872">
            <citation-title>NEW YORK STATE BOAT LAUNCHES (NYSDEC) - KML/KMZ FILE FORMAT</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>NEW YORK STATE DEPARTMENT OF ENVIRONMENTAL CONSERVATION</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2009</extent-start-date-time>
            <citation-url>http://GIS.NY.GOV/GISDATA/INVENTORIES/DETAILS.CFM?DSID=1268</citation-url>
         </lineage-source>
         <lineage-source cc-id="827871">
            <citation-title>NEW YORK STATE HISTORIC SITES AND PARK BOUNDARY/ NATIONAL REGISTER SITES</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>NYS OFFICE OF PARKS, RECREATION &amp; HISTORIC PRESERVATION</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>http://GIS.NY.GOV/GISDATA/INVENTORIES/DETAILS.CFM?DSID=430</citation-url>
         </lineage-source>
         <lineage-source cc-id="827873">
            <citation-title>POINTS OF INTEREST - NEW YORK STATE (NYSDEC)</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>NEW YORK STATE DEPARTMENT OF ENVIRONMENTAL CONSERVATION</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2012</extent-start-date-time>
            <citation-url>http://GIS.NY.GOV/GISDATA/INVENTORIES/DETAILS.CFM?DSID=1258</citation-url>
         </lineage-source>
         <lineage-source cc-id="827874">
            <citation-title>PORTS OF THE UNITED STATES</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>NATIONAL ATLAS OF THE UNITED STATES</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2014</extent-start-date-time>
            <scale-denominator>100000</scale-denominator>
            <citation-url>http://WWW.NATIONALATLAS.GOV/ATLASFTP.HTML?OPENCHAPTERS=CHPBOUND%2CCHPGEOL%2CCHPREF%2CCHPPEOPL%2CCHPTRANS#CHPTRANS</citation-url>
         </lineage-source>
         <lineage-source cc-id="827875">
            <citation-title>POTENTIAL ACCESS SITE</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>QUANTUM SPATIAL INC.</contact-name>
            <contact-role-type>Originator</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2015</extent-start-date-time>
         </lineage-source>
         <lineage-source cc-id="827876">
            <citation-title>PROBABLE MARINA LOCATIONS BASED ON GOOGLE EARTH IMAGERY</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>QUANTUM SPATIAL INC.</contact-name>
            <contact-role-type>Originator</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2015</extent-start-date-time>
         </lineage-source>
         <lineage-source cc-id="827877">
            <citation-title>STATERECREATION</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>NYS OFFICE OF CYBER SECURITY</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2004</extent-start-date-time>
            <citation-url>http://GIS.NY.GOV/GISDATA/INVENTORIES/DETAILS.CFM?DSID=931</citation-url>
         </lineage-source>
         <lineage-source cc-id="827878">
            <citation-title>THE STATE OF NEW JERSEY FERRY TERMINAL EMBARKATION POINTS</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>NEW JERSEY DEPARTMENT OF STATE, OFFICE FOR PLANNING ADVOCACY</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <extent-type>Discrete</extent-type>
            <extent-start-date-time>2014</extent-start-date-time>
            <citation-url>http://WWW.STATE.NJ.US/STATE/PLANNING/SPC-RESEARCH-RESOURCES-GIS.HTML</citation-url>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="827849">
            <sequence-number>1</sequence-number>
            <description>Process steps 1 and 2 describe the process used to map all points within the  human use data layers found within the SOCECON feature data set.

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 publicly-available digital data supplemented with expert knowledge. Abandoned vessel data originated from the National Oceanic and Atmospheric Administration (NOAA) Office of Coast Survey Automated Wrecks and Obstructions Information System. Access locations were compiled using New York State Department of Environmental Conservation (NYSDEC) digital data and Quantum Spatial, Inc. (QSI) generated points. Airport locations were acquired from Federal Aviation Administration Aeronautical Information Services. NYSDEC and Rutgers Agricultural Experiment Station provided information on aquaculture sites. Archeological sites were provided by Hudsonia LTD and New Jersey Department of Environmental Protection. NOAA.s Coastal Services Center provided data for artificial reefs. Beach locations were compiled by QSI using aerial imagery and data from United States Geological Survey Geographic Names Information System. Boat ramp locations were mapped using digital data from NYSDEC, New York State Office of Parks, Recreation &amp; Historic Preservation, New York State Office of Cyber Security (NYSOCS), and National Park Service. The NYSOCS also provided state campground data. Coast Guard unit locations were acquired from the U.S. Coast Guard (USCG) Operation Systems Center and U.S. Department of Commerce, Census Bureau, Geographic Products Branch. Diving and surfing sites were acquired from EcoTrust as part of the Mid-Atlantic Coastal and Ocean Recreation Study. The New Jersey Department of State and New York City Department of City Planning provided ferry terminal data. U.S. Environmental Protection Agency (USEPA) Facility locations represent facilities that are required to maintain a risk management plan, because they use/store regulated substances exceeding an EPA-specified threshold quantity. 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. Landfill sites were compiled from Energy Justice and NYSDEC tabular data. Lock and Dam data were acquired from NYSDEC.s Inventory of Dams. Marina data were provided by the Hudson River Boat and Yacht Club Association, the Mohawk Hudson Council of Yacht Clubs, and Peter Cunningham. Additional probable marina locations were mapped by QSI using Google Earth imagery. NYSDEC and United States Energy Information Administration provided locations of major oil facilities.</description>
            <process-date-time>2015-11-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="827850">
            <sequence-number>2</sequence-number>
            <description>Port locations were obtained from NOAAS.s Coastal Services Center, National Atlas, and NYC Department of City Planning. Recreational fishing sites came from NYSDEC. NOAA.s Office for Coastal Management provided data for renewable energy. Repeated measurement site (RMS) locations for marine observation sites and tide gauges were obtained through NOAA's National Data Buoy Center, and the Center for Operational Oceanographic Products and Services. Mussel Watch program RMS locations were obtained from the NOAA Chemical Impacts Team. An oyster restoration site was provided by New York/New Jersey Baykeeper. Streamflow gage locations were obtained from the USGS. NYSDEC Bureau of Water Resources Management provided water intake locations and were supplemented with expert knowledge. Water intakes in New Jersey were mapped as polygons and were not included in this feature class. The above digital and expert knowledge sources were compiled by the project biologist to create the SOCECON point data layers. Depending on the type of source data, two general approaches are used for compiling the data layer: 1) digital data layers are evaluated and used "as is" or integrated with the ESI base map features (ESIP, HYDROP, ESIL) 2) information gathered during initial interviews and from hardcopy sources are compiled and digitized using ESI base map features. 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 SOCECON point 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-11-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="827851">
            <sequence-number>3</sequence-number>
            <description>Process step 3 describes the process used to map all lines within the human use data layers found within the SOCECON feature data set.

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 publicly-available digital data sets. Bridge locations were mapped using the National Atlas of the United States Major Roads and supplemented by Quantum Spatial, Inc. (QSI) using ESRI aerial imagery. Pipeline data were acquired from the United States Energy Information Administration. Rail routes were acquired from the National Atlas. Shipping Lanes were mapped using the National Waterway Network provided by the United States Army Corps of Engineers. The above digital sources were compiled by the project biologist to create the SOCECONL data layer. Depending on the type of source data, two general approaches are used for compiling the data layer: 1) digital data layers are evaluated and used "as is" or integrated with the ESI base map features (ESIP, HYDROP, ESIL) 2) information gathered during initial interviews and from hardcopy sources are compiled and digitized using ESI base map features. 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 SOCECON line data layers are made based on the recommendations of the resource experts, and final hardcopy maps and digital data are created.</description>
            <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>55814</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>NAV_MARINE_LINE</title>
      </child-item>
      <child-item>
         <catalog-item-id>55813</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>NAV_MARINE_POINT</title>
      </child-item>
      <child-item>
         <catalog-item-id>55815</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>SOC_DAT</title>
      </child-item>
      <child-item>
         <catalog-item-id>55816</catalog-item-id>
         <catalog-item-type>Entity</catalog-item-type>
         <title>SOURCES</title>
      </child-item>
   </child-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:55812</guid>
      <metadata-record-created-by pers-id="20377">Jill Petersen</metadata-record-created-by>
      <metadata-record-created>2019-03-08T13:12:54</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-03-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>2019-03-08</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2020-03-08</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
