<?xml version="1.0" encoding="UTF-8"?><metadata>
<Esri>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">DredgeAreas</itemName>
<nativeExtBox>
<westBL Sync="TRUE">-10413742.739500</westBL>
<eastBL Sync="TRUE">-8242851.506400</eastBL>
<southBL Sync="TRUE">2959561.259300</southBL>
<northBL Sync="TRUE">4820731.571100</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<relatedItems>
<item>
<itemType Sync="TRUE">Relationship</itemType>
</item>
<item>
<itemName Sync="FALSE">DredgeAreasHaveLeaseDocs</itemName>
<itemType Sync="TRUE">Relationship</itemType>
</item>
<item>
<itemName Sync="FALSE">DredgeHasFinalReport</itemName>
<itemType Sync="TRUE">Relationship</itemType>
</item>
<item>
<itemName Sync="FALSE">DredgeHaveExposure</itemName>
<itemType Sync="TRUE">Relationship</itemType>
</item>
<item>
<itemName Sync="FALSE">DredgeHasLeaseDoc</itemName>
<itemType Sync="TRUE">Relationship</itemType>
</item>
<item>
<itemName Sync="FALSE">DredgeHasFinalReport</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>19414800</SyncTime>
<ModDate>20250115</ModDate>
<ModTime>15023000</ModTime>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISProfile>NAP</ArcGISProfile>
<CreaDate>20240327</CreaDate>
<CreaTime>17232800</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
</Esri>
<mdFileID>54B29768-EB93-4D42-BE88-0134D900BE04</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">DredgeAreas</resTitle>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Dredge area polygons represent the approximate lateral extent of where dredging of outer continental shelf (OCS) sediment has occurred within authorized OCS lease areas, which are maintained by the Bureau of Ocean Energy Management (BOEM), part of the U.S. Department of the Interior. The dredged material (e.g. sediment) is typically transported via pipeline and deposited along the shoreline of a pre-determined coastal area needing nourishment. Entities are authorized to dredge sand, gravel, or shell resources from the OCS after entering into a Negotiated Non-Competitive Lease or Memorandum of Agreement with BOEM. 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 part by or authorized by the Federal government. This dataset is a collection of dredge areas under BOEM's purview. Attribution consists of state, OCS lease number, project ID, borrow area ID, construction (dredging) start and end dates, dredged volume, and delineation quality; see attribute definitions for full explanations. This dataset will be updated as new data are received from lessees.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>The dredge areas feature class serves as a geospatial record of where individual dredge events have occurred within OCS borrow areas authorized for use by the Bureau of Ocean Energy Management (BOEM), part of the U.S. Department of the Interior. The footprint of each polygon represents the approximate lateral extent of changes to the seabed (increased depth) that have occurred directly as a result of dredging. Each polygon is delineated based on analysis and interpretation of before- and after-dredge bathymetric data, the computed bathymetric surface difference (e.g., the output surface resulting from subtracting after-dredge bathymetric data from before-data bathymetric data over an equally-sized grid). The analysis of these data enables BOEM to monitor and quantify natural and anthropogenic changes (e.g., dredged volume) to the seabed in OCS borrow areas, which facilitates comprehensive resource management and conservation. Entities are authorized to dredge sand, gravel, or shell resources from the OCS after entering into a Negotiated Non-Competitive Lease or Memorandum of Agreement with BOEM. 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 part by or authorized by the Federal government. This dataset is a collection of dredge areas under BOEM's purview. Attribution consists of state, OCS lease number, project ID, borrow area ID, construction (dredging) start and end dates, approximate dredged volume, and delineation quality; see attribute definitions for full explanations of how individual fields are calculated (if applicable). This dataset will be updated as new data are received from lessees.</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>Library of Congress Subject Headings</resTitle>
<date>
<pubDate>2021-03-01T00:00:00</pubDate>
</date>
</thesaName>
<keyword>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>-93.548236</westBL>
<eastBL>-75.193337</eastBL>
<southBL>25.680481</southBL>
<northBL>37.857258</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>Source (bathymetric) data are available upon request. 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>Maine</keyword>
<keyword>Maryland</keyword>
<keyword>Massachusetts</keyword>
<keyword>Florida</keyword>
<keyword>Rhode Island</keyword>
<keyword>New Jersey</keyword>
<keyword>Georgia</keyword>
<keyword>North Carolina</keyword>
<keyword>Virginia</keyword>
<keyword>Delaware</keyword>
<keyword>South Carolina</keyword>
<keyword>New York</keyword>
<keyword>ATLANTIC OCEAN</keyword>
<keyword>Geology</keyword>
<keyword>Geophysical</keyword>
<keyword>Marine Mineral Resources</keyword>
<keyword>Sediment</keyword>
<keyword>Survey</keyword>
<keyword>Non-Energy</keyword>
<keyword>Sand Resources</keyword>
<keyword>Offshore</keyword>
<keyword>Sand</keyword>
<keyword>Outer Continental Shelf</keyword>
<keyword>Cubic Yards</keyword>
<keyword>Physical Habitats</keyword>
<keyword>OCS</keyword>
<keyword>Mining and Mineral Extraction</keyword>
<keyword>Dredging</keyword>
<keyword>Gravel</keyword>
<keyword>US</keyword>
<keyword>GULF OF MEXICO</keyword>
<keyword>NORTH ATLANTIC OCEAN</keyword>
<keyword>SEA FLOOR</keyword>
<keyword>Oceans</keyword>
<keyword>Lease</keyword>
<keyword>Sand</keyword>
<keyword>Mineral Resources</keyword>
<keyword>Geophysical Survey</keyword>
<keyword>Non-Energy</keyword>
<keyword>Dredging</keyword>
<keyword>Shoal</keyword>
<keyword>Bathymetric Survey</keyword>
<keyword>Beach Nourishment</keyword>
<keyword>Authorized Lease</keyword>
<keyword>Benthic</keyword>
<keyword>Oceanographic Sensors</keyword>
<keyword>Offshore</keyword>
<keyword>Physical Oceanography</keyword>
<keyword>Dredge Volume</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.548243</westBL>
<eastBL Sync="TRUE">-74.046795</eastBL>
<northBL Sync="TRUE">39.688174</northBL>
<southBL Sync="TRUE">25.680486</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<tpCat>
<TopicCatCd value="014"/>
</tpCat>
<tpCat>
<TopicCatCd value="015"/>
</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>Attribute data were collected from lease documents provided by lessees. Source data used to delineate the approximate extent of dredging were also provided by the lessees. These data were utilized by BOEM to produce the dredge areas features.</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. All OCS marine mineral lessees are required to submit pre- and post-dredge bathymetric data, which are then analyzed by BOEM staff to verify the reported material extraction volumes, that dredging solely occurred within the authorized lease area boundaries, and to gain an understanding of seabed dynamics within borrow and the surrounding vicinity. The approximate lateral extent of dredging within each lease area was determined based on analysis and interpretation of before- and after-dredge bathymetric data, the computed bathymetric surface difference between each survey, and or operational dredge plant data.A polygon representing the approximate extent of dredging was manually digitized around the area disturbed (generally where depth has increased) directly as a result of dredge activity. Later, a master layer was created in the MMIS geodatabase data model to house all dredge 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 borrow area ID (e.g. Shoal A), construction (dredging) start and ends dates, calculated and reported dredge volume in cubic yards, and a qualitative description of the accuracy of the delineated dredge area (partially based on the pixel resolution). Attribute data were collected from lease documents, post construction reports, survey reports, and survey data. Next, the disparate dredge area shapefiles and their attribute data were loaded into the MMIS Dredge Areas feature class. For increased accessibility, each dredge 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="DredgeAreas">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">69</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.DredgeAreas</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="DredgeAreas">
<enttyp>
<enttypl Sync="FALSE">DredgeAreas</enttypl>
<enttypd>Enables BOEM to ensure dredge operations are within the lease boundaries. Quality is determined by the resolution of the pre and post survey data from which the polygon is delineated.</enttypd>
<enttypds>BOEM</enttypds>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">69</enttypc>
</enttyp>
<attr>
<attrlabl>BorrowArea</attrlabl>
<attrdef>Borrow Area Identifier Name (e.g. Shoal A)</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Borrow Area Identifier Name (e.g. Shoal A)</udom>
</attrdomv>
<attalias Sync="TRUE">Borrow Area 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>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>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>DredgeVolRep</attrlabl>
<attrdef>Amount of sand dredged in cubic yards as reported in the Project Completion Report</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Amount of sand dredged in cubic yards as reported in the Project Completion Report</udom>
</attrdomv>
<attalias Sync="TRUE">Dredge Volume Reported</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</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</attrlabl>
<attrdef>Assigns Cartographic Representation</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<edom>
<edomv>1</edomv>
<edomvd>Dredge Areas</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>-1</edomv>
<edomvd>Free Representation</edomvd>
<edomvds>BOEM</edomvds>
</edom>
</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>ConstructionStart</attrlabl>
<attrdef>The date construction (dredging) started.</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>The date construction (dredging) started.</udom>
</attrdomv>
<attalias Sync="TRUE">Construction 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>Dredge_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>DredgeVolCalc</attrlabl>
<attrdef>Amount of sand dredged in cubic yards as calculated within the lease area by computing the volume change between pre- and post-dredge survey bathymetric data. This volume is derived from the grid volume report generated as an output when using the calculate volume command in Golden Software's Surfer program. In most cases, the dredge volume calculated field of this feature class is populated with the positive cut volume in the output grid volume report (converted to cubic yards). This value is representative of volume loss in the borrow area due to dredging and is valid under two main assumptions: (1) an otherwise static seabed in the intervening time period and (2) acceptable vertical survey error tolerances (e.g., +/- 0.1 feet minimum vertical survey accuracy over a 1 square mile (640 acres) survey area translates to a minimum uncertainty of at least +/- 103,000 cubic yards). However, there are many factors (e.g., source data quality/vertical uncertainty, time between dredge surveys, timing of surveys relative to dredging, significant natural sediment mobilization, method of calculation, missing information or context, etc.; ) that can result in discrepancies between calculating dredge volume based on positive cut volume using the method described above and the dredge volume reported (or calculated) by the Lessee or their contractors. Thus, if the positive cut volume is a significant deviation from the expected result (based on static seabed assumption and approximate vertical uncertainty across the borrow area) and is deemed an invalid representation of dredge volume, then an alternative method of analysis may be required to calculate a value representative of volume loss directly due to dredging. In these situations, supporting notes and explanation have been added in the Comments attribute field to provide as much context as possible within the allotted character limit. If the dredged volume cannot be determined with reasonable confidence, then no value is reported in the dredge volume calculated field.</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Amount of sand dredged in cubic yards as calculated within the lease area by computing the volume change between pre- and post-dredge survey bathymetric data. This volume is derived from the grid volume report generated as an output when using the calculate volume command in Golden Software's Surfer program. In most cases, the dredge volume calculated field of this feature class is populated with the positive cut volume in the output grid volume report (converted to cubic yards). This value is representative of volume loss in the borrow area due to dredging and is valid under two main assumptions: (1) an otherwise static seabed in the intervening time period and (2) acceptable vertical survey error tolerances (e.g., +/- 0.1 feet minimum vertical survey accuracy over a 1 square mile (640 acres) survey area translates to a minimum uncertainty of at least +/- 103,000 cubic yards). However, there are many factors (e.g., source data quality/vertical uncertainty, time between dredge surveys, timing of surveys relative to dredging, significant natural sediment mobilization, method of calculation, missing information or context, etc.; ) that can result in discrepancies between calculating dredge volume based on positive cut volume using the method described above and the dredge volume reported (or calculated) by the Lessee or their contractors. Thus, if the positive cut volume is a significant deviation from the expected result (based on static seabed assumption and approximate vertical uncertainty across the borrow area) and is deemed an invalid representation of dredge volume, then an alternative method of analysis may be required to calculate a value representative of volume loss directly due to dredging. In these situations, supporting notes and explanation have been added in the Comments attribute field to provide as much context as possible within the allotted character limit. If the dredged volume cannot be determined with reasonable confidence, then no value is reported in the dredge volume calculated field.</udom>
</attrdomv>
<attalias Sync="TRUE">Dredge Volume Calculated</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</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>Dredge_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>Quality</attrlabl>
<attrdef>Qualitative description of the accuracy of the dredge area delineation. This metric largely relies on resolution of survey data used in the delineation, where higher resolution surveys usually result in better delineations.</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<edom>
<edomv>Fair</edomv>
<edomvd>Fair - 10-50ft</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>Poor</edomv>
<edomvd>Poor - &gt; 50ft</edomvd>
<edomvds>BOEM</edomvds>
</edom>
<edom>
<edomv>Good</edomv>
<edomvd>Good - &lt; 10ft</edomvd>
<edomvds>BOEM</edomvds>
</edom>
</attrdomv>
<attalias Sync="TRUE">Delineation Quality</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</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>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>ConstructionComplete</attrlabl>
<attrdef>The date construction (dredging) ended.</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>The date construction (dredging) ended expressed as MM\DD\YYYY</udom>
</attrdomv>
<attalias Sync="TRUE">Construction Complete 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>Comments</attrlabl>
<attrdef>Additional comments or notes containg supporting information</attrdef>
<attrdefs>BOEM</attrdefs>
<attrdomv>
<udom>Additional comments or notes containg supporting information</udom>
</attrdomv>
<attalias Sync="TRUE">Comments</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</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>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 Federal Outer Continental Shelf (OCS) Dredge Area feature class serves as a geospatial record of where individual dredge events have occurred within OCS borrow areas authorized for use by the Bureau of Ocean Energy Management (BOEM), part of the U.S. Department of the Interior. The footprint of each polygon represents the approximate lateral extent of changes to the seabed (increased depth) that have occurred directly as a result of dreding. Each polygon is delineated based on analysis and interpretation of before- and after-dredge bathymetric data and the computed surface difference (e.g., the output surface resulting from subtracting after-dredge bathymetric data from before-data bathymetric data over an equally-sized grid). The analysis of these data enables BOEM to monitor and quantify natural and anthropogenic changes (e.g., dredged volume) to the seabed in OCS borrow areas, which facilitates comprehensive resource management and conservation. Polygon quality is partially dependent on the resolution of the pre- and post- dredge bathymetric survey data.</eaover>
<eadetcit>BOEM</eadetcit>
</overview>
</eainfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="DredgeAreas">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">69</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
</metadata>
