<?xml version="1.0" encoding="UTF-8"?><metadata>
<Esri>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">ShorePlacement</itemName>
<nativeExtBox>
<westBL Sync="TRUE">-10407275.803800</westBL>
<eastBL Sync="TRUE">-8250828.387500</eastBL>
<southBL Sync="TRUE">2968557.390200</southBL>
<northBL Sync="TRUE">4827220.169200</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<relatedItems>
<item>
<itemType Sync="TRUE">Relationship</itemType>
</item>
<item>
<itemName Sync="FALSE">ShorePlaceHaveLeaseDocs</itemName>
<itemType Sync="TRUE">Relationship</itemType>
</item>
<item>
<itemName Sync="FALSE">ShoreHasFinalReport</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>19534400</SyncTime>
<ModDate>20251014</ModDate>
<ModTime>17525300</ModTime>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISProfile>NAP</ArcGISProfile>
<CreaDate>20240327</CreaDate>
<CreaTime>17263800</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
</Esri>
<mdFileID>FC74384F-C942-4325-8B05-AEC6F85B202A</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>
<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>
<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">ShorePlacement</resTitle>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The Shore Placement Areas feature class contains polygons representing approximate locations along the U.S. coastline where dredged material from the Outer Continental Shelf (OCS) has been placed as part of a project for shore protection, beach restoration, coastal restoration, or construction project undertaken by a Federal, State, or local government agency. These locations mainly include (but are not limited to) beaches that require shoreline stabilization and beach nourishment in order to reduce future coastal storm flooding and erosion, and to provide cultural, economic, recreational, and environmental habitat benefits. Placement areas for dredged OCS material are specifically defined in every Negotiated Non-Competitive Lease or Memorandum of Agreement with Bureau of Ocean Energy Management (BOEM) which authorizes contracted entities 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. Planned and/or as-built project placement locations are typically provided to the BOEM within or as an attachment (e.g. as-built survey drawing) to the lease agreement and post-construction/project completion reports. The polygon extents are not guaranteed to be exact and may contain estimate boundaries or generalized locations where as-built survey data were not available. Attribution consists of OCS lease number, project ID, Shore ID (placement area location or beach name), placement (construction) start and end dates, placement volume, the number of linear miles of coastline restored, and supplemental comments that provide additional context regarding the placement/construction event. This dataset will receive regular updates as new OCS leases are added or renewed and OCS sediment is allocated to planned placement sites along the U.S. coastline.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>The Shore Placement Areas feature class was created to represent the locations where sand or sediment placement is planned or has occurred as part of a coastal nourishment project and at least in part utilizing BOEM-authorized Outer Continental Shelf (OCS) sand / sediment sources for project construction. Each polygon feature illustrates the approximate lateral extent of placement associated with each project and contains attributes with supplemental information associated with project construction (e.g., BOEM OCS lease number, placement time range, placement volume, location/beach name (shore ID), planned vs actual mileage of placement, comments on ). In certain instances, project construction was completed utilizing sediment from the OCS and from state waters (landward of 3-nautical mile Submerged Lands Act Boundary). Thus, all shore placement polygon features do not represent areas exclusive to the placement of Outer Continental Shelf (OCS) sediment but rather represent an approximation of the entire placement area for the specified time range/construction event. Similarly, some placement features represent projects for which OCS sand was authorized for use but were not constructed prior to the expiration of the BOEM lease agreement. These features have a value of '0' in the 'placement volume' and 'actual miles restored' attribute fields and are also noted in the 'comments' field.</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>
<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>-93.490143</westBL>
<eastBL>-74.118451</eastBL>
<southBL>25.75329</southBL>
<northBL>39.733006</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>The most current version of this dataset can be downloaded via the Marine Minerals Information System (MMIS) viewer at https://mmis.boem.gov.</suppInfo>
<searchKeys>
<keyword>Beach</keyword>
<keyword>GULF OF MEXICO</keyword>
<keyword>Environment</keyword>
<keyword>Sand</keyword>
<keyword>Sediment</keyword>
<keyword>Mineral Resources</keyword>
<keyword>Non-Energy</keyword>
<keyword>Dredging</keyword>
<keyword>Beach Nourishment</keyword>
<keyword>Beach Placement</keyword>
<keyword>Habitat Restoration</keyword>
<keyword>Shoreline</keyword>
<keyword>Construction</keyword>
<keyword>Sediment Placement</keyword>
<keyword>ATLANTIC OCEAN</keyword>
<keyword>Sand Resources</keyword>
<keyword>OCS</keyword>
<keyword>Outer Continental Shelf</keyword>
<keyword>Habitat Assessment</keyword>
<keyword>Mining and Mineral Extraction</keyword>
<keyword>GLOBAL OCEAN</keyword>
<keyword>NORTH ATLANTIC OCEAN</keyword>
<keyword>SEA FLOOR</keyword>
<keyword>US</keyword>
<keyword>Coastline</keyword>
<keyword>Coastal</keyword>
<keyword>Coastal Resilience</keyword>
<keyword>Barrier Island</keyword>
<keyword>Placement Volume</keyword>
<keyword>Dredge Disposal Site</keyword>
<keyword>Post Construction Report</keyword>
<keyword>Non-Energy</keyword>
<keyword>Mineral Resources</keyword>
<keyword>Sand</keyword>
<keyword>Shoreline</keyword>
<keyword>OCS</keyword>
<keyword>Authorized Lease</keyword>
<keyword>Physical Oceanography</keyword>
<keyword>Dredged Material</keyword>
<keyword>Erosion</keyword>
<keyword>Beach Nourishment</keyword>
</searchKeys>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<idPoC>
<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>
<displayName>U.S. Department of Interior, Bureau of Ocean Energy Management, Marine Minerals Program</displayName>
</idPoC>
<envirDesc Sync="FALSE">Esri ArcPro</envirDesc>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-93.490149</westBL>
<eastBL Sync="TRUE">-74.118452</eastBL>
<northBL Sync="TRUE">39.733014</northBL>
<southBL Sync="TRUE">25.753295</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<tpCat>
<TopicCatCd value="014"/>
</tpCat>
<tpCat>
<TopicCatCd value="015"/>
</tpCat>
<tpCat>
<TopicCatCd value="005"/>
</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>
<measResult>
<ConResult>
<conExpl>Pass</conExpl>
<conPass>0</conPass>
</ConResult>
</measResult>
</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>
<measResult>
<ConResult>
<conExpl>Pass</conExpl>
</ConResult>
</measResult>
</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>
<measResult>
<ConResult>
<conExpl>Pass</conExpl>
</ConResult>
</measResult>
</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>
<measResult>
<ConResult>
<conExpl>Pass</conExpl>
</ConResult>
</measResult>
</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>
<measResult>
<ConResult>
<conExpl>Pass</conExpl>
</ConResult>
</measResult>
</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>1995-05-17T00: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 locational descriptions of each beach placement area were retrieved directly from BOEM's Negotiated Non-Competitive Leases or Memorandum of Agreements. For each lease where as-planned or as-built placement shapes were not available, the placement areas were digitized in Esri's ArcMap as a point shapefile and stored in the corresponding lease project folder. Each point represented the approximate central location of the beach placement area. To provide the ability to map the beach areas as polygons, the points were buffered by a standard 100 meters using the Buffer Tool which resulted in a polygon layer. Next, a master layer was created in the MMIS geodatabase data model to house all beach placement area polygons in a single feature class (reprojected into the NAD83 geodetic reference system). A list of attributes was developed including the corresponding lease number, the construction start and ends dates, placement volume in cubic yards, and the total miles of beach restored. Attribute data were collected from lease documents, post-construction reports, survey reports, and survey data. Next, the disparate shore placement area shapefiles and their attribute data were loaded into the MMIS Shore Placement Areas feature class. For increased accessibility, each shore placement area polygon was linked to the corresponding PDF lease document(s). For specific process information regarding acquisition, please reference the individual lease documents.</stepDesc>
<stepDateTm>2024-10-01T00:00:00</stepDateTm>
</prcStep>
</dataLineage>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="ShorePlacement">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">89</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.ShorePlacement</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="ShorePlacement">
<enttyp>
<enttypl Sync="FALSE">ShorePlacement</enttypl>
<enttypd>Fill placement area on the shoreline</enttypd>
<enttypds>BOEM</enttypds>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">89</enttypc>
</enttyp>
<attr>
<attrlabl>Comments</attrlabl>
<attrdef>Additional comments pertaining to the dataset</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Additional comments pertaining to the dataset</udom>
</attrdomv>
<attalias Sync="TRUE">Comments</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">1000</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>PlacementEnd</attrlabl>
<attrdef>The date construction ended</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>The date construction ended</udom>
</attrdomv>
<attalias Sync="TRUE">Placement End 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>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>PlacementStart</attrlabl>
<attrdef>The date construction started</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>The date construction started</udom>
</attrdomv>
<attalias Sync="TRUE">Placement Start 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>ProjectID</attrlabl>
<attrdef>General project name associated with lease; county, locality, or project name followed by fiscal year of original lease execution (e.g. Brevard County 2005)</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>General project name associated with lease; county, locality, or project name followed by fiscal year of original lease execution (e.g. Brevard County 2005)</udom>
</attrdomv>
<attalias Sync="TRUE">Project 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>Shore_GlobalReportID</attrlabl>
<attrdef>Unique identifier that links feature to Post Construction Report</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Unique identifier that links feature to Post Construction Report</udom>
</attrdomv>
<attalias Sync="TRUE">Global Report 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>PlacementVolume</attrlabl>
<attrdef>Volume of sand utilized (in fill template; cubic yards); entered as '0' if no construction took place utilizing OCS sediment within authorized lease term</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Volume of sand utilized (in fill template; cubic yards); entered as '0' if no construction took place utilizing OCS sediment within authorized lease term</udom>
</attrdomv>
<attalias Sync="TRUE">Shore Placement Volume (Cubic Yards)</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl>ShoreID</attrlabl>
<attrdef>ID for Shore Placement Area</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>ID for Shore Placement Area</udom>
</attrdomv>
<attalias Sync="TRUE">Shore ID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">200</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>Shore_GlobalLeaseID</attrlabl>
<attrdef>Unique identifier that links feature to lease documents</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Unique identifier that links feature to lease documents</udom>
</attrdomv>
<attalias Sync="TRUE">Global Lease 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>LeaseNo</attrlabl>
<attrdef>BOEM Lease Agreement Number</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>BOEM Lease Agreement Number</udom>
</attrdomv>
<attalias Sync="TRUE">Lease Number</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">ShoreMilesConstructed</attrlabl>
<attalias Sync="TRUE">Actual Miles Constructed</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
<attrdef>Total miles of shore restored from construction which is reported in the Project Completion Report or based on the measurement of the polygons shapefiles.</attrdef>
<attrdefs>BOEM</attrdefs>
</attr>
<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>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>The Shore Placement Areas feature class contains polygons representing approximate locations along the U.S. coastline where dredged material from the Outer Continental Shelf (OCS) has been placed as part of a project for shore protection, beach restoration, coastal restoration, or construction project undertaken by a Federal, State, or local government agency. These actions are a mitigation exercise that create new beaches, restore eroded coastal areas and habitat, or widen them as part of a coastal defense or restoration scheme to slow down eroding shorelines. Shore placement areas are first identified in Negotiated Non-Competitive Leases and / or Memoranda of Agreement (MOA) between the Department of the Interior (DOI) Bureau of Ocean Energy Management (BOEM) and another Federal agency (such as the U.S. Army Corps of Engineers), State agency, or local government agency. After dredging and placement has occurred, final placements areas are described in post-construction reports that are required by BOEM. Maintaining a spatial record of these placement areas enables BOEM to (1) keep an inventory of locations, (2) maintain records of the amount of dredged material being placed on the shoreline, and (3) monitor for the correct allocation and efficacy of materials. Shore placement polygons are created using location maps and diagrams from final reporting as well as discussions with BOEM Marine Minerals Program (MMP) scientists.</eaover>
<eadetcit>BOEM</eadetcit>
</overview>
</eainfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="ShorePlacement">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">89</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
</metadata>
