<?xml version="1.0" encoding="UTF-8"?><metadata>
<Esri>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">IsopachArc</itemName>
<nativeExtBox>
<westBL Sync="TRUE">-10818935.156900</westBL>
<eastBL Sync="TRUE">-7993287.215000</eastBL>
<southBL Sync="TRUE">3035736.911400</southBL>
<northBL Sync="TRUE">5022109.344900</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<relatedItems>
<item>
<itemName Sync="FALSE">IsoArcHasLinks</itemName>
<itemType Sync="TRUE">Relationship</itemType>
</item>
<item>
<itemName Sync="FALSE">IsoArcHaveLinkDocs</itemName>
<itemType Sync="TRUE">Relationship</itemType>
</item>
</relatedItems>
<imsContentType Sync="TRUE" export="False">002</imsContentType>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_WGS_1984</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Meter (1.000000)</csUnits>
<peXml Sync="TRUE">&lt;ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.2.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;WGS_1984_Web_Mercator_Auxiliary_Sphere&amp;quot;,GEOGCS[&amp;quot;GCS_WGS_1984&amp;quot;,DATUM[&amp;quot;D_WGS_1984&amp;quot;,SPHEROID[&amp;quot;WGS_1984&amp;quot;,6378137.0,298.257223563]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Mercator_Auxiliary_Sphere&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,0.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,0.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,0.0],PARAMETER[&amp;quot;Auxiliary_Sphere_Type&amp;quot;,0.0],UNIT[&amp;quot;Meter&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,3857]]&lt;/WKT&gt;&lt;XOrigin&gt;-20037700&lt;/XOrigin&gt;&lt;YOrigin&gt;-30241100&lt;/YOrigin&gt;&lt;XYScale&gt;10000&lt;/XYScale&gt;&lt;ZOrigin&gt;0&lt;/ZOrigin&gt;&lt;ZScale&gt;1&lt;/ZScale&gt;&lt;MOrigin&gt;0&lt;/MOrigin&gt;&lt;MScale&gt;1&lt;/MScale&gt;&lt;XYTolerance&gt;0.001&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;102100&lt;/WKID&gt;&lt;LatestWKID&gt;3857&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
<projcsn Sync="TRUE">WGS_1984_Web_Mercator_Auxiliary_Sphere</projcsn>
</coordRef>
</DataProperties>
<SyncDate>20241028</SyncDate>
<SyncTime>19451800</SyncTime>
<ModDate>20250115</ModDate>
<ModTime>15040800</ModTime>
<ArcGISFormat>1.0</ArcGISFormat>
<CreaDate>20240327</CreaDate>
<CreaTime>17252900</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<ArcGISProfile>NAP</ArcGISProfile>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
</Esri>
<mdFileID>9C3576B8-843D-4572-80C6-330C05F3FEFD</mdFileID>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<mdContact>
<rpPosName>Oceanographer</rpPosName>
<rpOrgName>U.S. Department of Interior, Bureau of Ocean Energy Management, Marine Minerals Program</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>703-787-1747</voiceNum>
</cntPhone>
<cntAddress>
<eMailAdd>marineminerals@boem.gov</eMailAdd>
<delPoint>45600 Woodland Road, VAM-LD</delPoint>
<city>Sterling</city>
<adminArea>VA</adminArea>
<postCode>20166</postCode>
<country>US</country>
</cntAddress>
<cntHours>Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)</cntHours>
<cntInstr>http://www.boem.gov/Marine-Minerals-Program</cntInstr>
<cntOnlineRes>
<linkage>http://www.boem.gov/Marine-Minerals-Program</linkage>
<protocol>HyperText Protocol</protocol>
<appProfile>web browser</appProfile>
<orName>BOEM MMIS website</orName>
<orFunct>
<OnFunctCd value="001"/>
</orFunct>
</cntOnlineRes>
<cntHours>Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt Sync="FALSE">20241001</mdDateSt>
<distInfo>
<distFormat>
<formatVer>ArcGIS 10.8.1</formatVer>
<formatName Sync="TRUE">Enterprise Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<date>
<pubDate>2024-10-01T00:00:00</pubDate>
</date>
<citRespParty>
<rpOrgName>U.S. Department of Interior, Bureau of Ocean Energy Management, Marine Minerals Program</rpOrgName>
<rpCntInfo>
<cntAddress>
<eMailAdd>marineminerals@boem.gov</eMailAdd>
<delPoint>45600 Woodland Road, VAM-LD</delPoint>
<city>Sterling</city>
<adminArea>VA</adminArea>
<postCode>20166</postCode>
<country>US</country>
</cntAddress>
<cntOnlineRes>
<linkage>http://www.boem.gov/Marine-Minerals-Program</linkage>
<protocol>HyperText Protocol</protocol>
<appProfile>web browser</appProfile>
<orName>BOEM MMIS website</orName>
<orFunct>
<OnFunctCd value="001"/>
</orFunct>
</cntOnlineRes>
<cntHours>Monday through Friday 8:00 AM to 5:00 PM (Eastern Time)</cntHours>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>U.S. Department of Interior, Bureau of Ocean Energy Management, Marine Minerals Program</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
<resTitle Sync="FALSE">IsopachArc</resTitle>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The Isopach Arc layer contains contour lines, or isopachs, that represent positions of equal formation thickness of a sand body, or other geologic unit, with the thickness being measured vertically with respect to the seafloor. The investigations from which these geospatial data were derived were fully or partially funded by the Bureau of Ocean Energy Management (BOEM) or partner agencies. Attribution consists of location, feature ID and description, study date, contour value (thickness), and study ID. The associated study report(s) are linked via the related Link Documents table within the Marine Minerals Information System (MMIS) geodatabase. This dataset will be updated as new and existing data are received and incorporated in to the Marine Minerals Information System (MMIS) geodatabase.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>Mapping the thickness and lateral extent of discrete bodies of sediment with similar characteristics provides crucial information for a number of coastal and marine spatial planning applications that help identify critical habitat areas for benthic organisms (e.g. clams, corals, demersal fish), select appropriate offshore construction sites, and plan sand/gravel mining operations. The Bureau of Ocean Energy Management (BOEM) can use this information when managing Outer Continental Shelf (OCS) non-energy mineral resources in order to ensure that the removal and relocation of sand is conducted in a safe and environmentally sound manner, and that any potentially adverse impacts on the marine, coastal, or human environments are avoided or minimized.</idPurp>
<idStatus>
<ProgCd value="007"/>
</idStatus>
<resMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
</resMaint>
<placeKeys>
<thesaName>
<resTitle>NASA/GCMD Location Keywords</resTitle>
<date>
<pubDate>2021-01-26T00:00:00</pubDate>
</date>
</thesaName>
<keyword>GULF OF MEXICO</keyword>
<keyword>ATLANTIC OCEAN</keyword>
<keyword>GLOBAL OCEAN</keyword>
<keyword>NORTH ATLANTIC OCEAN</keyword>
<keyword>SEA FLOOR</keyword>
<keyword>Outer Continental Shelf</keyword>
</placeKeys>
<placeKeys>
<thesaName>
<resTitle>U.S. Department of Commerce, 1995, Countries, dependencies, areas of special sovereignty, and their principal administrative divisions, Federal Information Processing Standard (FIPS) 10-4): Washington, D.C., National Institute of Standards and Technology.</resTitle>
<date>
<pubDate>1995-01-01T00:00:00</pubDate>
</date>
</thesaName>
<keyword>US</keyword>
</placeKeys>
<themeKeys>
<thesaName>
<resTitle>SeaDataNet Common Vocabularies</resTitle>
<date>
<pubDate>2019-03-01T00:00:00</pubDate>
</date>
</thesaName>
<keyword>Marine Geology</keyword>
</themeKeys>
<resConst>
<LegConsts>
<othConsts>This data is in the public domain and has no access restrictions.</othConsts>
</LegConsts>
</resConst>
<resConst>
<SecConsts>
<classSys>FIPS 199 Security Classification</classSys>
<handDesc>There are no restrictions; the data is releasable to the public.</handDesc>
<class>
<ClasscationCd value="001"/>
</class>
</SecConsts>
</resConst>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The Bureau of Ocean Energy Management (BOEM) provides the data for use "as is". BOEM provides this information with the understanding that it is not guaranteed to be accurate, correct or complete and conclusions drawn from such information are the responsibility of the user. While every effort has been made to ensure the accuracy, correctness and timeliness of materials presented within the limits of the current state of the art, BOEM assumes no responsibility for errors or omissions, nor as a result of the failure of the data to function on a particular system. BOEM makes no warranty, expressed or implied, nor does the fact of distribution constitute such a warranty. Users are cautioned to consider carefully the provisional nature of these data and information before using them for decisions that concern personal or public safety or the conduct of business that involves substantial monetary or operational consequences. Conclusions drawn from or actions undertaken on the basis of, such data and information are the sole responsibility of the user. The maps shown here are for illustration and planning purposes only and are not suitable for site-specific decision making. The data are not suitable for navigational purposes. Information found here should not be used for making financial or any other commitments. This data was developed by the U.S. Government; no other proprietary rights may be attached to them nor may they be sold to the U.S. Government as part of any procurement of products or services. Public domain data from the U.S. Government are freely redistributable with proper metadata and source attribution. Please recognize the Bureau of Ocean Energy Management (BOEM) as the source of this information.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<dataExt>
<geoEle>
<GeoBndBox>
<westBL>-91.167552</westBL>
<eastBL>-73.854848</eastBL>
<southBL>26.968058</southBL>
<northBL>40.324469</northBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2021-07-23T00:00:00</tmBegin>
<tmEnd>2024-10-01T00:00:00</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<suppInfo>None</suppInfo>
<envirDesc Sync="FALSE">Esri ArcPro</envirDesc>
<searchKeys>
<keyword>US</keyword>
<keyword>Outer Continental Shelf</keyword>
<keyword>ATLANTIC OCEAN</keyword>
<keyword>GULF OF MEXICO</keyword>
<keyword>SEA FLOOR</keyword>
<keyword>GLOBAL OCEAN</keyword>
<keyword>NORTH ATLANTIC OCEAN</keyword>
<keyword>isopach</keyword>
<keyword>seismic</keyword>
<keyword>geophysics</keyword>
<keyword>geologic</keyword>
<keyword>stratigraphy</keyword>
<keyword>sand</keyword>
<keyword>Offshore</keyword>
<keyword>Sand Thickness</keyword>
<keyword>Seismic Reflection</keyword>
<keyword>Ocean</keyword>
<keyword>Sand</keyword>
<keyword>Survey</keyword>
<keyword>Subsurface</keyword>
</searchKeys>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-97.188148</westBL>
<eastBL Sync="TRUE">-71.804921</eastBL>
<northBL Sync="TRUE">41.066188</northBL>
<southBL Sync="TRUE">26.295587</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<tpCat>
<TopicCatCd value="008"/>
</tpCat>
<tpCat>
<TopicCatCd value="014"/>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="012"/>
</maintFreq>
<dateNext>2026-01-01T00:00:00</dateNext>
</mdMaint>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report dimension="" type="DQConcConsis">
<measDesc>The MMIS data model utilizes a hierarchical structure where an ESRI enterprise geodatabase represents the top tier, and feature datasets and raster catalogs are the secondary tiers which contain groupings of similar data layers. These individual data layers were identified by MMP as important, and they make up the bottom tier. Most individual vector layers and tables are collections of data from multiple sources and across multiple dates. Extensive research went into the construction of (1) the hierarchical groupings of data (primarily by subject matter and file format) and (2) technical aspects of the data model. Data within the geodatabase was consolidated to reduce redundancy, resulting in several stand-alone tables. Relationship classes utilizing global IDs were built between vector layers and stand-alone tables in order to link disparate data. The entire MMIS data model was originally constructed using ESRI ArcGIS Diagrammer, a tool that creates and edits a geodatabase schema. The resulting geodatabase structure, data, and relationship classes were reviewed thoroughly by multiple individuals using ESRI Geodatabase Diagrammer Add-In, ESRI ArcGIS, and Microsoft Visio. ESRI Geodatabase Diagrammer Add-In creates a detailed break-down of the geodatabase and a Visio data model poster.</measDesc>
<measName>Conceptual consistency: adherence to rules of the conceptual schema</measName>
<evalMethDesc>The MMIS data model utilizes a hierarchical structure where an ESRI enterprise geodatabase represents the top tier, and feature datasets and raster catalogs are the secondary tiers which contain groupings of similar data layers. These individual data layers were identified by MMP as important, and they make up the bottom tier. Most individual vector layers and tables are collections of data from multiple sources and across multiple dates. Extensive research went into the construction of (1) the hierarchical groupings of data (primarily by subject matter and file format) and (2) technical aspects of the data model. Data within the geodatabase was consolidated to reduce redundancy, resulting in several stand-alone tables. Relationship classes utilizing global IDs were built between vector layers and stand-alone tables in order to link disparate data. The entire MMIS data model was originally constructed using ESRI ArcGIS Diagrammer, a tool that creates and edits a geodatabase schema. The resulting geodatabase structure, data, and relationship classes were reviewed thoroughly by multiple individuals using ESRI Geodatabase Diagrammer Add-In, ESRI ArcGIS, and Microsoft Visio. ESRI Geodatabase Diagrammer Add-In creates a detailed break-down of the geodatabase and a Visio data model poster.</evalMethDesc>
<evalMethType>
<EvalMethTypeCd value="003"/>
</evalMethType>
</report>
<report dimension="" type="DQCompOm">
<measDesc>The spatial data and attribute tables loaded into the MMIS data model are believed to be complete, in regards to maintaining each data layer/table after retrieving it from its source. Please refer to the scientific reports, as well as BOEM MMP Leases, negotiated agreements, Memoranda of Agreements, and project completion reports, for discussions of the results on the corresponding source data. Most individual vector layers and tables in the MMIS data model are collections of data from multiple sources and across multiple dates. Most likely, these MMIS layers/tables will continue to have more data loaded in the future, therefore expanding upon the list of sources and dates. Additionally, the Pacific Outer Continental Shelf (OCS) and Alaska OCS regions may eventually be added to the data model, aside from the Atlantic and Gulf of Mexico OCS regions.</measDesc>
<measName>Completeness omission: data absent from the dataset, as described by the scope</measName>
<evalMethDesc>The spatial data and attribute tables loaded into the MMIS data model are believed to be complete, in regards to maintaining each data layer/table after retrieving it from its source. Please refer to the scientific reports, as well as BOEM MMP Leases, negotiated agreements, Memoranda of Agreements, and project completion reports, for discussions of the results on the corresponding source data. Most individual vector layers and tables in the MMIS data model are collections of data from multiple sources and across multiple dates. Most likely, these MMIS layers/tables will continue to have more data loaded in the future, therefore expanding upon the list of sources and dates. Additionally, the Pacific Outer Continental Shelf (OCS) and Alaska OCS regions may eventually be added to the data model, aside from the Atlantic and Gulf of Mexico OCS regions.</evalMethDesc>
<evalMethType>
<EvalMethTypeCd value="003"/>
</evalMethType>
</report>
<report dimension="" type="DQQuanAttAcc">
<measDesc>Please refer to the scientific reports, as well as Bureau of Ocean Energy Management (BOEM) Marine Minerals Program (MMP) Leases, negotiated agreements, cooperative agreements, Memoranda of Agreements, and project completion reports, for accuracy statements on the corresponding source data. These documents are referenced in the attribute tables, where appropriate. In regards to attribute assignment in the Marine Minerals Information Systems (MMIS) data model, every effort was made to load source data into MMIS without error or modification. Some attributes contain domain restrictions in an effort to standardize the field entries and to decrease potential inconsistent entries (e.g., spelling, grammar, typographical errors, and subject matter) in the attribute.</measDesc>
<measName>Quantitative attribute accuracy: accuracy of quantitative attributes</measName>
<evalMethDesc>Please refer to the scientific reports, as well as Bureau of Ocean Energy Management (BOEM) Marine Minerals Program (MMP) Leases, negotiated agreements, cooperative agreements, Memoranda of Agreements, and project completion reports, for accuracy statements on the corresponding source data. These documents are referenced in the attribute tables, where appropriate. In regards to attribute assignment in the Marine Minerals Information Systems (MMIS) data model, every effort was made to load source data into MMIS without error or modification. Some attributes contain domain restrictions in an effort to standardize the field entries and to decrease potential inconsistent entries (e.g., spelling, grammar, typographical errors, and subject matter) in the attribute.</evalMethDesc>
<evalMethType>
<EvalMethTypeCd value="003"/>
</evalMethType>
</report>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>unknown</measDesc>
<measName>Absolute external positional accuracy: closeness of reported coordinate values to values accepted as or being true</measName>
<measDesc>Absolute external positional accuracy: closeness of reported coordinate values to values accepted as or being true</measDesc>
<evalMethDesc>Absolute external positional accuracy: closeness of reported coordinate values to values accepted as or being true</evalMethDesc>
<evalMethType>
<EvalMethTypeCd value="003"/>
</evalMethType>
</report>
<report dimension="vertical" type="DQAbsExtPosAcc">
<measDesc>unknown</measDesc>
<measName>Absolute external positional accuracy: closeness of reported coordinate values to values accepted as or being true</measName>
<measDesc>Absolute external positional accuracy: closeness of reported coordinate values to values accepted as or being true</measDesc>
<evalMethDesc>Absolute external positional accuracy: closeness of reported coordinate values to values accepted as or being true</evalMethDesc>
<evalMethType>
<EvalMethTypeCd value="003"/>
</evalMethType>
</report>
<dataLineage>
<dataSource type="">
<srcDesc>Lineage varies by data source. Some data was contributed, some was mapped/reformatted from scientific and technical reports for MMIS.</srcDesc>
<srcCitatn>
<resTitle>BOEM Archives</resTitle>
<resAltTitle>BOEM Archives</resAltTitle>
<date>
<pubDate>2024-10-01T00:00:00</pubDate>
</date>
<citRespParty>
<rpOrgName>U.S. Department of Interior, Bureau of Ocean Energy Management, Marine Minerals Program</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Multiple investigators and projects</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="002"/>
</presForm>
<presForm>
<fgdcGeoform>document</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2000-01-01T00:00:00</tmBegin>
<tmEnd>2024-10-01T00:00:00</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<prcStep>
<stepDesc>The spatial and tabular data presented in this dataset was identified by the Bureau of Ocean Energy Management (BOEM) Marine Minerals Program (MMP) for the MMIS project as being critical for MMP's decision making and management responsibilities of federal Outer Continental Shelf (OCS) mineral exploration and federal non-energy sand/gravel lease activities. The data was retrieved directly from BOEM, or another government entity, in the form of one or more ArcGIS shapefiles, raster (grid) layers, Microsoft Excel spreadsheets, XYZ files, field logs, project reports, PDF tables, and maps. This data was linked to source documents including environmental study reports and data deliverables associated with Negotiated Non-Competitive Leases or Memorandum of Agreements between BOEM and partnering agencies or contractors. First, the source data was reformatted, if needed, into an ESRI ArcGIS compatible format and then loaded into a project-specific geodatabase in its native projection. Second, the data was reprojected into the NAD83 geodetic reference system and then loaded into corresponding layers and tables in the MMIS enterprise geodatabase. Relationship classes were made between disparate layers and tables to join related data. Lastly, for use in the web application, a duplicate "publishable" MMIS enterprise geodatabase was created in a Web Mercator (Auxiliary Sphere) projection. For specific process information regarding acquisition, please reference the individual study reports.</stepDesc>
<stepDateTm>2024-10-01T00:00:00</stepDateTm>
</prcStep>
</dataLineage>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="IsopachArc">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">7609</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<refSysInfo>
<RefSystem dimension="horizontal">
<refSysID>
<identCode Sync="TRUE" code="3857"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.18.3(9.3.1.2)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<contInfo>
<FetCatDesc>
<compCode>True</compCode>
<catLang>
<languageCode value="eng"/>
<countryCode value="US"/>
<CharSetCd value="004"/>
</catLang>
<incWithDS>True</incWithDS>
<catCitation>
<resTitle>Feature Catalogue for MMIS.SDE.IsopachArc</resTitle>
<date>
<pubDate>2024-10-01T00:00:00</pubDate>
</date>
<citRespParty>
<rpOrgName>U.S. Department of Interior, Bureau of Ocean Energy Management, Marine Minerals Program</rpOrgName>
<role>
<RoleCd value="002"/>
</role>
<rpCntInfo>
<cntOnlineRes>
<linkage>https://mmis.boem.gov</linkage>
<protocol>HyperText Protocol</protocol>
<appProfile>web browser</appProfile>
<orName>Content Information for the Resource</orName>
<orDesc>Link to access information about the data content.</orDesc>
</cntOnlineRes>
</rpCntInfo>
</citRespParty>
</catCitation>
</FetCatDesc>
</contInfo>
<eainfo>
<detailed Name="IsopachArc">
<enttyp>
<enttypl Sync="FALSE">IsopachArc</enttypl>
<enttypd>Contour representation of sediment thickness</enttypd>
<enttypds>BOEM</enttypds>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">7609</enttypc>
</enttyp>
<attr>
<attrlabl>RuleID</attrlabl>
<attrdef>Assigns Cartographic Representation</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Assigns Cartographic Representation</udom>
</attrdomv>
<attalias Sync="TRUE">RuleID</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Override_2</attrlabl>
<attrdef>Overrides Cartographic Representation</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Overrides Cartographic Representation</udom>
</attrdomv>
<attalias Sync="TRUE">Override_2</attalias>
<attrtype Sync="TRUE">Blob</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Location</attrlabl>
<attrdef>Feature ID</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Feature ID</udom>
</attrdomv>
<attalias Sync="TRUE">Feature ID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>State</attrlabl>
<attrdef>Location relative to closest state; state funded for OCS study, two letter postal code</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Location relative to closest state; state funded for OCS study, two letter postal code</udom>
</attrdomv>
<attalias Sync="TRUE">State</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>SHAPE.STLength()</attrlabl>
<attrdef>Length of feature in internal units</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Length of feature in internal units</udom>
</attrdomv>
<attalias Sync="TRUE">SHAPE.STLength()</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>OBJECTID</attrlabl>
<attrdef>Internal feature number</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Internal feature number</udom>
</attrdomv>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>IsoArc_GlobalLinkID</attrlabl>
<attrdef>Unique identifier that links the feature to the study report</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Unique identifier that links the feature to the study report</udom>
</attrdomv>
<attalias Sync="TRUE">Global Link ID</attalias>
<attrtype Sync="TRUE">GUID</attrtype>
<attwidth Sync="TRUE">38</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Override_1</attrlabl>
<attrdef>Overrides Cartographic Representation</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Overrides Cartographic Representation</udom>
</attrdomv>
<attalias Sync="TRUE">Override_1</attalias>
<attrtype Sync="TRUE">Blob</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Thickness_m</attrlabl>
<attrdef>Sand thickness in meters</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Sand thickness in meters</udom>
</attrdomv>
<attalias Sync="TRUE">Thickness (Meters)</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl>Thickness_ft</attrlabl>
<attrdef>Sand thickness in feet</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Sand thickness in feet</udom>
</attrdomv>
<attalias Sync="TRUE">Thickness (Feet)</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl>Override</attrlabl>
<attrdef>Overrides Cartographic Representation</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Overrides Cartographic Representation</udom>
</attrdomv>
<attalias Sync="TRUE">Override</attalias>
<attrtype Sync="TRUE">Blob</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>SHAPE</attrlabl>
<attrdef>Feature geometry</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Feature geometry</udom>
</attrdomv>
<attalias Sync="TRUE">SHAPE</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>RuleID_2</attrlabl>
<attrdef>Assigns Cartographic Representation</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<edom>
<edomv>11</edomv>
<edomvd>60 - 70</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>10</edomv>
<edomvd>50 - 60</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>2</edomv>
<edomvd>2.0 - 4.0</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>3</edomv>
<edomvd>4.0 - 8.0</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>1</edomv>
<edomvd>0 - 2.0</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>8</edomv>
<edomvd>30 - 40</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>-1</edomv>
<edomvd>Free Representation</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>6</edomv>
<edomvd>16 - 20</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>12</edomv>
<edomvd>70 - 80</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>5</edomv>
<edomvd>12 - 16</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>7</edomv>
<edomvd>20 - 30</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>9</edomv>
<edomvd>40 - 50</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>4</edomv>
<edomvd>8.0 - 12</edomvd>
<edomvds>BOEM</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">RuleID_2</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>StudyID</attrlabl>
<attrdef>Study ID of the study in which the feature was identified. Study ID following the convention noted in the Data Management Plan</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Study ID of the study in which the feature was identified. Study ID following the convention noted in the Data Management Plan</udom>
</attrdomv>
<attalias Sync="TRUE">Study ID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Description</attrlabl>
<attrdef>Description</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Description</udom>
</attrdomv>
<attalias Sync="TRUE">Description</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">1000</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Date</attrlabl>
<attrdef>Study Date</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Study Date</udom>
</attrdomv>
<attalias Sync="TRUE">Study Date</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>RuleID_1</attrlabl>
<attrdef>Assigns Cartographic Representation</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Assigns Cartographic Representation</udom>
</attrdomv>
<attalias Sync="TRUE">RuleID_1</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>created_user</attrlabl>
<attalias>created_user</attalias>
<attrdef>Stores the name of the user who creates features or records</attrdef>
<attrdefs>Esri</attrdefs>
<attrtype>Text</attrtype>
<attwidth>255</attwidth>
<attrdomv>
<udom>Read-only. Stores the name of the user who creates features or records.</udom>
</attrdomv>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>created_date</attrlabl>
<attalias>created_date</attalias>
<attrdef>Stores the date and time a feature or record was created</attrdef>
<attrdefs>Esri</attrdefs>
<attrtype>Date</attrtype>
<attwidth>8</attwidth>
<attrdomv>
<udom>Read-only. Stores the date and time a feature or record was created.</udom>
</attrdomv>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>last_edited_user</attrlabl>
<attalias>last_edited_user</attalias>
<attrdef>Stores the name of the user who last edited a feature or record</attrdef>
<attrdefs>Esri</attrdefs>
<attrtype>Text</attrtype>
<attwidth>255</attwidth>
<attrdomv>
<udom>Read-only. Stores the name of the user who last edited a feature or record.</udom>
</attrdomv>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>last_edited_date</attrlabl>
<attalias>last_edited_date</attalias>
<attrdef>Stores the date a feature or record was last edited</attrdef>
<attrdefs>Esri</attrdefs>
<attrtype>Date</attrtype>
<attwidth>8</attwidth>
<attrdomv>
<udom>Read-only. Stores the date a feature or record was last edited.</udom>
</attrdomv>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
<overview>
<eaover>Isopach maps are used to identify variations and trends in the thickness and lateral extent of discrete bodies of sediment. The Bureau of Ocean Energy Management (BOEM) relies heavily on isopach maps in order to identify sand resource areas in the Federal Outer Continental Shelf (OCS) and to estimate the volume and extent of sand reservoirs. Having centralized access to these layers facilitates decision making and administrative planning within BOEM and the U.S. Army Corps of Engineers (USACE).</eaover>
<eadetcit>BOEM</eadetcit>
</overview>
</eainfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="IsopachArc">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="3"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">7609</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
</metadata>
