<?xml version="1.0" encoding="UTF-8"?><metadata>
<Esri>
<CreaDate>20240327</CreaDate>
<CreaTime>17264000</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISProfile>NAP</ArcGISProfile>
<DataProperties>
<itemProps>
<imsContentType Sync="TRUE" export="False">002</imsContentType>
<itemName Sync="FALSE">ShoreStudyAreas</itemName>
<nativeExtBox>
<westBL Sync="TRUE">-10406158.049900</westBL>
<eastBL Sync="TRUE">-7788578.125100</eastBL>
<southBL Sync="TRUE">3115380.908100</southBL>
<northBL Sync="TRUE">5316259.640300</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<relatedItems>
<item>
<itemName Sync="FALSE">ShoreStudyHasLinks</itemName>
<itemType Sync="TRUE">Relationship</itemType>
</item>
<item>
<itemName Sync="FALSE">ShoreStudyHaveLinkDocs</itemName>
<itemType Sync="TRUE">Relationship</itemType>
</item>
</relatedItems>
</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>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<ModDate>20251014</ModDate>
<ModTime>17533100</ModTime>
<SyncDate>20241028</SyncDate>
<SyncTime>19541000</SyncTime>
<SyncOnce>FALSE</SyncOnce>
</Esri>
<dataIdInfo>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The Shore Study Areas layer contains polygons delineating locations along the U.S. coastline that have experienced increased erosion and, as a result, prompted environmental studies to determine (1) the extent of erosion, (2) baseline documentation of shore sediment character, and (3) if the site could benefit from shoreline stabilization and beach nourishment in order to reduce coastal storm flooding and erosion, and provide economic, cultural, recreational, and environmental habitat benefits. If a shoreline area is designated as being in need of restoration and renourishment, and a composite match is made between the shore sand and sand in the Federal Outer Continental Shelf (OCS), then entities may enter into a Negotiated Non-Competitive Lease or Memoranda of Agreement with the Bureau of Ocean Energy Management (BOEM), in order to dredge sand, gravel, or shell resources from the OCS. Section 8 (k) of the OCS Lands Act (OCSLA) as amended by Public Law 103-426 (enacted in 1994) gives BOEM the authority to negotiate an agreement for the use of OCS sand, gravel, and shell resources for use in: (1) a project for shore protection, beach restoration, or coastal restoration undertaken by a Federal, State, or local government agency; or (2) for use in a construction project funded in whole or in part by or authorized by the Federal government. This dataset is a collection of previous and current shore study areas. Attribution consists of Study ID, year of study, and summarized sediment descriptions. The polygon extents are not guaranteed to be exact and may contain estimate boundaries delineated based on visual interpretation of drawings and descriptions found in study documents. The dataset will be updated on a regular basis to reflect new and previous study areas.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idCitation>
<resTitle Sync="FALSE">ShoreStudyAreas</resTitle>
<date>
<pubDate>2024-10-01T00:00:00</pubDate>
</date>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
<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>
</idCitation>
<dataExt>
<geoEle>
<GeoBndBox>
<westBL>-97.753529</westBL>
<eastBL>-66.82347</eastBL>
<northBL>45.332495</northBL>
<southBL>23.803551</southBL>
</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>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<westBL Sync="TRUE">-93.480108</westBL>
<eastBL Sync="TRUE">-69.965988</eastBL>
<northBL Sync="TRUE">43.028164</northBL>
<southBL Sync="TRUE">26.935222</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<idPoC>
<rpPosName>Oceanographer</rpPosName>
<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>
<cntPhone>
<voiceNum>703-787-1747</voiceNum>
</cntPhone>
<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>
<cntInstr>http://www.boem.gov/Marine-Minerals-Program</cntInstr>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
<displayName>U.S. Department of Interior, Bureau of Ocean Energy Management, Marine Minerals Program</displayName>
</idPoC>
<searchKeys>
<keyword>Beach</keyword>
<keyword>GULF OF MEXICO</keyword>
<keyword>Environment</keyword>
<keyword>Sand</keyword>
<keyword>Mineral Resources</keyword>
<keyword>Geophysical Survey</keyword>
<keyword>Non-Energy</keyword>
<keyword>Dredging</keyword>
<keyword>Geological</keyword>
<keyword>Survey</keyword>
<keyword>Beach Nourishment</keyword>
<keyword>Study</keyword>
<keyword>ATLANTIC OCEAN</keyword>
<keyword>Sand Resources</keyword>
<keyword>Biological Research</keyword>
<keyword>OCS</keyword>
<keyword>Outer Continental Shelf</keyword>
<keyword>Habitat Assessment</keyword>
<keyword>Mining and Mineral Extraction</keyword>
<keyword>Shoreline</keyword>
<keyword>Benthic</keyword>
<keyword>Offshore</keyword>
<keyword>GLOBAL OCEAN</keyword>
<keyword>Physical Oceanography</keyword>
<keyword>NORTH ATLANTIC OCEAN</keyword>
<keyword>SEA FLOOR</keyword>
<keyword>US</keyword>
<keyword>Chemical Research</keyword>
<keyword>Restoration</keyword>
<keyword>Physical Research</keyword>
<keyword>Sediment Characteristics</keyword>
<keyword>Erosion</keyword>
</searchKeys>
<idPurp>The Shore Study Areas layer contains polygons delineating locations along the U.S. coastline that have experienced increased erosion and, as a result, prompted environmental studies to determine (1) the extent of erosion, (2) baseline documentation of shore sediment character, and (3) if the site could benefit from shoreline stabilization and beach nourishment in order to reduce coastal storm flooding and erosion, and provide economic, cultural, recreational, and environmental habitat benefits. If a shoreline area is designated as being in need of restoration and renourishment, and a composite match is made between the shore sand and sand in the Federal Outer Continental Shelf (OCS), then entities may enter into a Negotiated Non-Competitive Lease or Memoranda of Agreement with the Bureau of Ocean Energy Management (BOEM), in order to dredge sand, gravel, or shell resources from the OCS. Section 8 (k) of the OCS Lands Act (OCSLA) as amended by Public Law 103-426 (enacted in 1994) gives BOEM the authority to negotiate an agreement for the use of OCS sand, gravel, and shell resources for use in: (1) a project for shore protection, beach restoration, or coastal restoration undertaken by a Federal, State, or local government agency; or (2) for use in a construction project funded in whole or in part by or authorized by the Federal government. This dataset is a collection of previous and current shore study areas. Attribution consists of Study ID, year of study, and summarized sediment descriptions. The polygon extents are not guaranteed to be exact and may contain estimate boundaries delineated based on visual interpretation of drawings and descriptions found in study documents. The dataset will be updated on a regular basis to reflect new and previous study areas.</idPurp>
<resConst>
<LegConsts>
<othConsts>This data is in the public domain and has no access restrictions.</othConsts>
</LegConsts>
</resConst>
<resConst>
<SecConsts>
<class>
<ClasscationCd value="001"/>
</class>
<classSys>FIPS 199 Security Classification</classSys>
<handDesc>There are no restrictions; the data is releasable to the public.</handDesc>
</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>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<envirDesc Sync="FALSE">Esri ArcPro</envirDesc>
<idStatus>
<ProgCd value="007"/>
</idStatus>
<suppInfo>The most current version of this dataset can be downloaded via the Marine Minerals Information System (MMIS) viewer at https://mmis.boem.gov.</suppInfo>
<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>
<tpCat>
<TopicCatCd value="008"/>
</tpCat>
<tpCat>
<TopicCatCd value="014"/>
</tpCat>
</dataIdInfo>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<mdFileID>6B23C31C-FCA6-49BD-B737-BF21BED4CF8B</mdFileID>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdDateSt Sync="FALSE">20241001</mdDateSt>
<mdContact>
<rpPosName>Oceanographer</rpPosName>
<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>
<cntPhone>
<voiceNum>703-787-1747</voiceNum>
</cntPhone>
<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>
<cntInstr>http://www.boem.gov/Marine-Minerals-Program</cntInstr>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<dataLineage>
<dataSource>
<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>2002-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 were 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 spatial extents of each study area along the U.S. shoreline were either retrieved directly from BOEM in the form of ESRI's ArcGIS shapefiles or the polygons were manually heads-up digitized in ArcMap by referencing written descriptions and figures from the report. A beach study area layer was made for each study and loaded into a project-specific geodatabase in its native projection. Next, a master layer was created in the MMIS geodatabase data model to house all beach study area polygons in a single feature class (reprojected into the NAD83 geodetic reference system). Attributes added to the feature class include the year the report was published and summary values for grain size, Munsell color, and percent sand. This data is summarized for the entire study, regardless of how many sub-locations a study might have, UNLESS the study reported the values specifically for each sub-area. Next, the disparate beach study area feature classes and their attribute data were loaded into the MMIS Beach Study Areas feature class. For increased accessibility, each study area polygon was linked to the corresponding PDF report document(s). For specific process information regarding acquisition, please reference the individual report documents.</stepDesc>
<stepDateTm>2024-10-01T00:00:00</stepDateTm>
</prcStep>
</dataLineage>
<report 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 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 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">
<measName>Absolute external positional accuracy: closeness of reported coordinate values to values accepted as or being true</measName>
<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">
<measName>Absolute external positional accuracy: closeness of reported coordinate values to values accepted as or being true</measName>
<evalMethDesc>Absolute external positional accuracy: closeness of reported coordinate values to values accepted as or being true</evalMethDesc>
<evalMethType>
<EvalMethTypeCd value="003"/>
</evalMethType>
</report>
</dqInfo>
<distInfo>
<distTranOps>
<onLineSrc>
<linkage>https://geoseas.geoplatform.gov/hosting/rest/services/MMP</linkage>
</onLineSrc>
</distTranOps>
<distFormat>
<formatVer>ArcGIS 10.8.1</formatVer>
<formatName Sync="TRUE">Enterprise Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<refSysInfo>
<RefSystem dimension="horizontal">
<refSysID>
<identCode Sync="TRUE" code="3857"/>
<idCodeSpace>EPSG</idCodeSpace>
<idVersion>6.18.3(9.3.1.2)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="012"/>
</maintFreq>
<dateNext>2026-01-01T00:00:00</dateNext>
</mdMaint>
<eainfo>
<detailed Name="ShoreStudyAreas">
<enttyp>
<enttypl Sync="FALSE">ShoreStudyAreas</enttypl>
<enttypd>Extent on the shore of a BOEM funded study, environmental assessment, or other similar report</enttypd>
<enttypds>BOEM</enttypds>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">174</enttypc>
</enttyp>
<attr>
<attrlabl>SHAPE.STArea()</attrlabl>
<attrdef>Area of feature in internal units squared</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Area of feature in internal units squared</udom>
</attrdomv>
<attalias Sync="TRUE">SHAPE.STArea()</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">ShoreStudyArea</attrlabl>
<attalias Sync="TRUE">Shore Study Area</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Shore Study Area</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Shore Study Area</udom>
</attrdomv>
</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>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>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>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 Sync="TRUE">Shore_GlobalLinkID</attrlabl>
<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>
<attrdef>Global Link ID</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Unique ID</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Year</attrlabl>
<attrdef>Year of sample collection</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Year of sample collection</udom>
</attrdomv>
<attalias Sync="TRUE">Year</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</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>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>Shore Study Areas polygons delineate locations where environmental studies have taken place along the U.S. coastline to determine (1) the extent of shoreline erosion, (2) baseline documentation of shore sediment character, and (3) if the site could benefit from shoreline stabilization and beach nourishment in order to reduce coastal storm flooding and erosion, and provide recreational and environmental habitat benefits. Data and conclusions from such studies are heavily relied upon by the Marine Minerals Program within the Bureau of Ocean Energy Management (BOEM) when making decisions for how to best manage non-energy mineral resources (primarily sand and gravel) on the Outer Continental Shelf (OCS). Strong decision making by BOEM ensures that the removal and re-deposition of any mineral resource 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. Shore study area polygons were either provided along with the report in spatial format, such as an ArcGIS shapefile, or were manually digitized by referencing written descriptions and figures from the report.</eaover>
<eadetcit>BOEM</eadetcit>
</overview>
</eainfo>
<spatRepInfo>
<VectSpatRep>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
<geometObjs Name="ShoreStudyAreas">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">174</geoObjCnt>
</geometObjs>
</VectSpatRep>
</spatRepInfo>
<contInfo>
<FetCatDesc>
<compCode>True</compCode>
<catLang>
<languageCode value="eng"/>
<countryCode value="US"/>
<CharSetCd value="004"/>
</catLang>
<catCitation>
<resTitle>Feature Catalogue for MMIS.SDE.ShoreStudyAreas</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>
<incWithDS>True</incWithDS>
</FetCatDesc>
</contInfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="ShoreStudyAreas">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">174</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
</metadata>
