<?xml version="1.0" encoding="UTF-8"?><metadata>
<dataIdInfo>
<idPurp>The U.S. inland navigation system consists of of rivers maintained by the Corps of Engineers in 22 states, and includes 276 lock chambers with a total lift of 6,100 feet. The highly adaptable and effective system of barge navigation moves over 625 million tons of commodities annually, which includes coal, petroleum products, various other raw materials, food and farm products, chemicals, and manufactured goods. The shallow draft waterways have many unique characteristics and difficulties over coastal harbor and ocean navigation; river levels can change by over 30 feet in a seasonal cycle, the navigation channel can shift significantly within the river banks, and shifting yet ever present river currents pose constant challenges in these confined waterways. Electronic chart systems can offer significant benefits to vessels including accurate and real-time display of vessel position relative to waterway features, voyage planning and monitoring, training tools for new personnel and integrated display of river charts, radar, and Automatic Identification Systems.
Following recommendations by the National Transportation Safety Board, the National Academy of Science and the American Waterways Operators, Congress directed the Corps of Engineers to develop and publish electronic charts for the inland waterways. Development of Inland Electronic Navigational Charts (IENCs) to cover the Mississippi River and tributaries thus began in 2001 with pilot projects on the Atchafalaya River in Louisiana and Lower Mississippi River near Vicksburg, Mississippi. These projects, which involved a combination of in-house and contract activities, were the first efforts to collect and convert inland waterway data, commonly used for river and channel maintenance, into the international S-57 hydrographic data exchange. This highly structured data format is commonly used for electronic chart applications and will be used for Corps IENCs
An S-57 database is extracted into an Esri File Geodatabase for publication. This is that geodatabase and it contains 99 feature classes that make up the IENC data.</idPurp>
<idCitation>
<date>
<pubDate>2026-04-01T00:00:00</pubDate>
</date>
<citRespParty>
<rpOrgName>Army Geospatial Center</rpOrgName>
<rpPosName>IENC POC</rpPosName>
<rpCntInfo>
<cntAddress>
<eMailAdd>IENC_POC@usace.army.mil</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</citRespParty>
<resTitle>OVERHEAD_CABLE_LINE</resTitle>
</idCitation>
<resConst>
<Consts>
<useLimit>Users should be aware that the IENCs reflect best available information at the time the data was collected. These data products are subject to change.</useLimit>
</Consts>
</resConst>
<tpCat>
<TopicCatCd value="Transportation Water"/>
</tpCat>
<themeKeys>
<keyword>USACE</keyword>
<keyword>USCG</keyword>
<keyword>IENC</keyword>
<keyword>HIFLD</keyword>
<keyword>Inland Electronic Navigation Charts</keyword>
</themeKeys>
<placeKeys>
<keyword>Continental United States</keyword>
</placeKeys>
<suppInfo>This geodatabase feature class is created as part of the publication of the IENC data. It is authoritative from the United States Army Corps of Engineers Inland Electronic Navigation Charts (USACE IENC) as of the date of publication. This data may be updated twice a month. A master feature service containing 92 of the 99 layers as feature services that can be exported and queried can be referenced in the Distribution information section.
Note that seven of the services have modified symbology due to feature limitations. They are: DAM_LINE, FERRY, LEVEE_LINE, Overhead_Pipeline, RAILROAD, ROAD_LINE, SUBMARINE_PIPELINE. The six layers that were removed were: Building_Point, Buoy_Special_Purpose, Daymark, Depth_Area, Shoreline_Construction_Area, Shoreline_Construction_Line.
Other download options are included in Distribution information. In addition to these options, KML, RSS, and GeoPDF data downloads can be found at: https://ienccloud.us/#DataDownload
This page also contains up-to-date alternative geo-enabled formats found in other distribution options as well as an interactive browser map viewer and a viewer that visualizes individual chart coverage.
Spelling, capitalization, abbreviation definitions, and formatting in dataset attribution comply with the Encoding Guide of Inland ENC (&lt;http://ienccloud.us/ienc/products/files/documents/IENC%20Encoding%20Guide%20-%20Edition%202.3.6.pdf&gt;). For example:
1) The mandatory source indicator is encoded under the following format (per page 13 of the encoding guide):
2 character country code, 2 character authority code, 5 character source code, identifier (no restriction on number of characters), e.g., (US,U3,SURVY,2001_Hydro_Survey). 2) Blank values indicate data that was not provided or otherwise not available; Denotes missing data that was not present in the source data. However, the missing data may be present in other sources not yet discovered and used in the creation and/or maintenance of this dataset. These records may be populated with valid information in future update cycles. Null values are not the same as blank values and may indicate values that were not translated from the original source charts.
3) Abbreviations and capitalization may reference a temporary status or a standard United States Coast Guard (USCG) Navigation Center entity (&lt;https://www.navcen.uscg.gov/&gt;; a recent light list containing abbreviations can be found at &lt;https://www.navcen.uscg.gov/pdf/lightLists/LightList_V5_2020.pdf&gt;). Additional common abbreviations are included in specific feature class field and supplemental information metadata. These occur in fields such as but not limited to Object_Name and Information in feature classes including but not limited to BUOY_SPECIAL_PURPOSE, CAUTION_AREA, CAUTION_AREA_POINT, DAYMARK, Lateral_Beacon, FLOODWALL, ISOLATED_DANGER_BUOY_POINT, LAND_REGION_POINT, LIGHTS, MOORING_FACILITY_POINT, Notice_Mark, PILE_POINT, PYLONS_AREA, SEA_AREA_POINT, SHORELINE_CONSTRUCTION_AREA, SHORELINE_CONSTRUCTION_LINE, SUBMARINE_PIPELINE_POINT, Lateral_Buoy, and RAILROAD.
4) In cases where units are not indicated in an entry that are encapsulated in parentheses, the units are assumed to be a mile marker referencing statute miles. These occur in fields such as but not limited to Object_Name and Information in feature classes in feature classes including but not limited to Bridge_Area, BUOY_SPECIAL_PURPOSE, CAUTION_AREA, CAUTION_AREA_POINT, CONVEYOR_AREA, FERRY, HARBOR_FACILITY_POINT, ISOLATED_DANGER_BUOY_POINT, LAND_REGION_POINT, Lateral_Beacon, LIGHTS, Lock_Basin, MOORING_FACILITY_AREA, MOORING_FACILITY_POINT, PILE_POINT, SEA_AREA_POINT, SHORELINE_CONSTRUCTION_AREA, SHORELINE_CONSTRUCTION_LINE, Traffic_Signal_Station, Warning_Signal_Station, Waterway_Gauge_Point, DAYMARK, Lateral_Buoy, and OBSTRUCTION_POINT.
To query specific enumerations and definitions not included in this metadata, access an up to date, interactive IENC Feature Catalog at: http://ienccloud.us/ienc/web/s-57/index24.html.</suppInfo>
<idCredit>USACE IENC</idCredit>
<idAbs>An overhead cable is an assembly of wires or fibres, or a wire rope or chain, which is supported b y structures such as poles or pylons and passing over or nearby navigable waters. (Hydrogra phic Service, Royal Australian Navy).</idAbs>
<dataExt>
<exDesc>The USACE IENCs coverage area consists of 7,260 miles across 21 rivers primarily located in the Central United States. IENCs apply to inland waterways that are maintained for navigation by USACE for shallow-draft vessels (e.g., maintained at a depth of 9-14 feet, dependent upon the waterway project authorization). Generally, IENCs are produced for those commercially navigable waterways which the National Oceanic and Atmospheric Administration (NOAA) does not produce Electronic Navigational Charts (ENCs). However, Special Purpose IENCs may be produced in agreement with NOAA. </exDesc>
</dataExt>
</dataIdInfo>
<mdConst>
<Consts>
<useLimit>Users should be aware that the IENCs reflect best available information at the time the data was collected. These data products are subject to change.</useLimit>
</Consts>
</mdConst>
<mdConst>
<LegConsts>
<useLimit>None (Public Domain Information) </useLimit>
</LegConsts>
</mdConst>
<mdConst>
<SecConsts>
<useLimit>None (Public Domain Information) </useLimit>
<classSys>USCAPCO</classSys>
<class>
<ClasscationCd value="001"/>
</class>
</SecConsts>
</mdConst>
<mdMaint>
<maintFreq>
<MaintFreqCd value="005"/>
</maintFreq>
</mdMaint>
<idinfo>
<natvform>Map Service, KML, WMS, WFS, RSS, GeoPDF, Overlays</natvform>
</idinfo>
<distInfo>
<distributor>
<distorTran>
<onLineSrc>
<linkage>https://ienccloud.us/arcgis/rest/services</linkage>
<orName>IENC Map Services</orName>
<orDesc>Hosts Map Services, WFS, and WMS services by Chart and Feature Class for quick attribute review in web maps and ArcMap.</orDesc>
</onLineSrc>
</distorTran>
<distorCont>
<rpOrgName>Army Geospatial Center</rpOrgName>
<rpPosName>IENC POC</rpPosName>
<rpCntInfo>
<cntAddress addressType="">
<eMailAdd>IENC_POC@usace.army.mil</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</distorCont>
</distributor>
<distributor>
<distorTran>
<onLineSrc>
<linkage>https://services3.arcgis.com/JR1tf2VoTNNjWen5/arcgis/rest/services/USACE_IENC_HIFLD_Layers/FeatureServer</linkage>
<orName>IENC Hosted Feature Services</orName>
<orDesc>Hosts a subset of the dataset (see supplemental information on which feature classes have limitations) as Feature Services by Feature Class for ArcMap detailed attribute access and dynamic exporting for offline use.</orDesc>
</onLineSrc>
<unitsODist>KB</unitsODist>
<transSize>339.19</transSize>
</distorTran>
<distorCont>
<rpOrgName>Army Geospatial Center</rpOrgName>
<rpPosName>IENC POC</rpPosName>
<rpCntInfo>
<cntAddress addressType="">
<eMailAdd>IENC_POC@usace.army.mil</eMailAdd>
</cntAddress>
</rpCntInfo>
</distorCont>
</distributor>
<distributor>
<distorTran>
<onLineSrc>
<linkage>https://hifld-geoplatform.opendata.arcgis.com/</linkage>
<orName>HIFLD Open</orName>
<orDesc>The HIFLD Open homepage distributes this data from the map services and allows downloads and web service access in a variety of formats with additional descriptive information.</orDesc>
</onLineSrc>
<unitsODist>KB</unitsODist>
<transSize>339.19</transSize>
</distorTran>
<distorCont>
<rpOrgName>Army Geospatial Center</rpOrgName>
<rpPosName>IENC POC</rpPosName>
<rpCntInfo>
<cntAddress addressType="">
<eMailAdd>IENC_POC@usace.army.mil</eMailAdd>
</cntAddress>
</rpCntInfo>
</distorCont>
</distributor>
<distributor>
<distorTran>
<onLineSrc>
<linkage>http://ienccloud.us/ienc/products/files/u37/ienc_master_dataset_gdb/USACE_IENC_Master_Service_gdb.zip</linkage>
<orName>Master Geodatabase</orName>
<orDesc>The IENC Master Geodatabase downloads all 400,000+ features in all charts and datasets to a single geodatabase for offline use of the entire dataset suite.</orDesc>
</onLineSrc>
<unitsODist>MB</unitsODist>
<transSize>131</transSize>
</distorTran>
<distorCont>
<rpOrgName>Army Geospatial Center</rpOrgName>
<rpPosName>IENC POC</rpPosName>
<rpCntInfo>
<cntAddress addressType="">
<eMailAdd>IENC_POC@usace.army.mil</eMailAdd>
</cntAddress>
</rpCntInfo>
</distorCont>
</distributor>
<distFormat>
<formatName>File Geodatabase Feature Class</formatName>
<formatVer>ArcGIS ArcGISPro 3.3 Build 52636</formatVer>
</distFormat>
</distInfo>
<dqInfo>
<report dimension="" type="">
<measDesc>Users should be aware that the IENCs reflect best available information at the time the data was collected. These data products are subject to change.</measDesc>
<measName>Temporal Validity</measName>
</report>
</dqInfo>
<eainfo>
<detailed>
<attr>
<attrlabl>OBJECTID</attrlabl>
</attr>
<attr>
<attrlabl>SHAPE</attrlabl>
</attr>
<attr>
<attrlabl>Vertical_Clearance</attrlabl>
<attrdef Sync="TRUE">The vertical clearance measured from the plane towards the object overhead.</attrdef>
<attrdefs Sync="TRUE">Inland Electronic Navigational Charts (IENC)</attrdefs>
<attrdomv>
<udom>Numeric in feet. In the case of cables carrying high voltages an additional clearance of from 2 to 5 metres may be needed to avoid an electrical discharge. When known, the authorized safe clearance (known in the UK as the Safe Overhead Clearance) which is the physical clearance minus a safety margin shall be stated (IHO Chart Specifications, M-4). See also 'vertical clearance safe'. The unit of measure is defined in the HUNI subfield of the DSPM record or in the HUNITS attribute of the M_UNIT meta object class, e.g., metre (m). The resolution is 0.1 m or 0.1 ft.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Vertical_Datum</attrlabl>
<attrdef Sync="TRUE">Vertical Datum</attrdef>
<attrdefs Sync="TRUE">Inland Electronic Navigational Charts (IENC)</attrdefs>
<attrdomv>
<edom>
<edomv>Mean lower low water</edomv>
<edomvd>(MLLW) - the average height of the lower low waters at a place over a 19-year period. (IHO Dictionary, S-32, 5th Edition, 3145).</edomvd>
<edomvds>Inland Electronic Navigational Charts (IENC)</edomvds>
</edom>
<edom>
<edomv>Local low water reference level</edomv>
<edomvd>Low water reference level of the local area.</edomvd>
<edomvds>Inland Electronic Navigational Charts (IENC)</edomvds>
</edom>
<edom>
<edomv>Local high water reference level</edomv>
<edomvd>High water reference level of the local area.</edomvd>
<edomvds>Inland Electronic Navigational Charts (IENC)</edomvds>
</edom>
<edom>
<edomv>Local mean water reference level</edomv>
<edomvd>Mean water reference level of the local area.</edomvd>
<edomvds>Inland Electronic Navigational Charts (IENC)</edomvds>
</edom>
<edom>
<edomv>Ohio River Datum</edomv>
<edomvd>Ohio River Datum.</edomvd>
<edomvds>Inland Electronic Navigational Charts (IENC)</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>Waterway_Distance</attrlabl>
<attrdef Sync="TRUE">The distance measured from an origin of a river or canal</attrdef>
<attrdefs Sync="TRUE">Inland Electronic Navigational Charts (IENC)</attrdefs>
<attrdomv>
<udom>Waterway distance (PLACEHOLDER): units, inquire with DP</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Horizontal_Units</attrlabl>
<attrdef Sync="TRUE">Units used to measure horizontal clearance</attrdef>
<attrdefs Sync="TRUE">Homeland Infrastructure Foundation Level Data (HIFLD) Support Team (HST)</attrdefs>
<attrdomv>
<edom>
<edomv>Feet</edomv>
<edomvd>Units are in feet.</edomvd>
<edomvds>Homeland Infrastructure Foundation Level Data (HIFLD) Support Team (HST)</edomvds>
</edom>
<edom>
<edomv>Metres</edomv>
<edomvd>Units are in meters</edomvd>
<edomvds>Homeland Infrastructure Foundation Level Data (HIFLD) Support Team (HST)</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>Object_Name</attrlabl>
<attrdef Sync="TRUE">The individual name of an object.</attrdef>
<attrdefs Sync="TRUE">Inland Electronic Navigational Charts (IENC)</attrdefs>
<attrdomv>
<udom>Object name.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Condition</attrlabl>
<attrdef Sync="TRUE">Condition of structure.</attrdef>
<attrdefs Sync="TRUE">Homeland Infrastructure Foundation Level Data (HIFLD) Support Team (HST)</attrdefs>
<attrdomv>
<edom>
<edomv>Under construction.</edomv>
<edomvd>A structure that is in the process of being built.</edomvd>
<edomvds>Homeland Infrastructure Foundation Level Data (HIFLD) Support Team (HST)</edomvds>
</edom>
<edom>
<edomv>Ruined</edomv>
<edomvd>A structure in a decayed or deteriorated condition resulting from neglect or disuse, or a damaged structure in need of repair.(IHO Dictionary, S-32, 5th Edition, 4456)</edomvd>
<edomvds>Homeland Infrastructure Foundation Level Data (HIFLD) Support Team (HST)</edomvds>
</edom>
<edom>
<edomv>Under reclamation</edomv>
<edomvd>An area of the sea that is being reclaimed as land, usually by the dumping of earth and other material.</edomvd>
<edomvds>Homeland Infrastructure Foundation Level Data (HIFLD) Support Team (HST)</edomvds>
</edom>
<edom>
<edomv>Wingless</edomv>
<edomvd>A windmill or windmotor from which the turbine blades are missing.</edomvd>
<edomvds>Homeland Infrastructure Foundation Level Data (HIFLD) Support Team (HST)</edomvds>
</edom>
<edom>
<edomv>Planned construction</edomv>
<edomvd>An area where a future construction is planned</edomvd>
<edomvds>Homeland Infrastructure Foundation Level Data (HIFLD) Support Team (HST)</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>Information</attrlabl>
<attrdef Sync="TRUE">Textual information about the object.</attrdef>
<attrdefs Sync="TRUE">Inland Electronic Navigational Charts (IENC)</attrdefs>
<attrdomv>
<udom>The textual information could be, for example, a list, a table or a text. This attribute should be used, for example, to hold the information that is shown on paper charts by cautionary and explanatory notes. No formatting of text is possible within INFORM. If formatted text is required, then the attribute TXTDSC must be used.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Scale_Minimum</attrlabl>
<attrdef Sync="TRUE">The minimum scale at which the object may be used e.g. for ECDIS presentation.</attrdef>
<attrdefs Sync="TRUE">Inland Electronic Navigational Charts (IENC)</attrdefs>
<attrdomv>
<udom>Scale minimum; the modulus of the scale is indicated, that is 1:1 250 000 is encoded as 1250000.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Source_Date</attrlabl>
<attrdef Sync="TRUE">The production date of the source of the data (e.g. the date of measurement). The source date should be coded for those objects in an IENC, which are changing regularly, for example depth information. </attrdef>
<attrdefs Sync="TRUE">Inland Electronic Navigational Charts (IENC)</attrdefs>
<attrdomv>
<codesetd>
<codesetn>Numeric calendar date. The format is yearmonthday (YYYYMMDD). For example, SORDAT coding for a feature with of source date of September 30, 2004 is 20040930.</codesetn>
<codesets>Inland Electronic Navigation Charts (IENC) 2</codesets>
</codesetd>
</attrdomv>
</attr>
<attr>
<attrlabl>Source_Indication</attrlabl>
<attrdef Sync="TRUE">The source indicator is a mandatory attribute and must be coded for all objects in the IENC. All objects in the Encoding Guide state that SORIND is Conditional (C); the condition that must be met is that it is a US produced chart.</attrdef>
<attrdefs Sync="TRUE">Inland Electronic Navigational Charts (IENC)</attrdefs>
<attrdomv>
<udom>Per page 13 of the encoding guide (see supplemental information for link):
Each entry contains 2 character country code, 2 character authority code, 5 character source code, identifier (no restriction on number of characters). For example, features reference an authority such as the USCG Mississippi River System Light List, Volume 5: (US,U3,MS_LL,2004_Edition_No.808).</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Source_Dataset</attrlabl>
<attrdef Sync="TRUE">Dataset or chart from which feature is derived.</attrdef>
<attrdefs Sync="TRUE">Homeland Infrastructure Foundation Level Data (HIFLD) Support Team (HST)</attrdefs>
<attrdomv>
<udom>8 character encoded reference name for original chart indicating country, subdivision, state, and state subdivision.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Feature_ID</attrlabl>
<attrdef Sync="TRUE">Feature Object Identifier field (FOID)</attrdef>
<attrdefs Sync="TRUE">Inland Electronic Navigational Charts (IENC)</attrdefs>
<attrdomv>
<udom>Numeric Feature S-57 ID</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>SHAPE_Length</attrlabl>
</attr>
</detailed>
</eainfo>
<Binary>
<Thumbnail>
<Data EsriPropertyType="PictureX"/>
</Thumbnail>
</Binary>
<Esri>
<CreaDate>20260402</CreaDate>
<CreaTime>00280700</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>TRUE</SyncOnce>
<DataProperties>
<itemProps/>
</DataProperties>
</Esri>
</metadata>
