<?xml version="1.0" encoding="UTF-8"?><metadata>
<idinfo>
<citation>
<citeinfo>
<pubdate>20040101</pubdate>
<pubtime>000000</pubtime>
<title>NewDelTerritory5</title>
<geoform>vector digital data</geoform>
<onlink>http://dataexchange.gis.delaware.gov</onlink>
<origin>U. S. Geological Survey on behalf of the Delaware geological Survey</origin>
<ftname Sync="TRUE">DE_BOUNDARY_STATE_OUTLINE</ftname>
</citeinfo>
</citation>
<descript>
<abstract>This geospatial data file comprises the bounding lines relating to the political boundary delineation for the State of DelawareNew Castle, Kent, and Sussex Counties have come to an agreement on where approximately the county boundaries should fall. The Kent and Sussex County Boundary has momuments which set the boundary line. These momuments have been GPS.</abstract>
<purpose>This dataset was created by merging three different data sets together. Two of the data sets were from the U.S. Geological Survey and the thrid from Kent County, DE.
The representation of the Delaware State boundary line and the coastal shore line were created in support of USGS's The National Map project and the Delaware's Spatial Data Framework/DataMIL project.
The County lines were created by Kent County, DE to show where approximately the Kent Boundary lines up with New Castle and Sussex Counties.</purpose>
<langdata Sync="TRUE">en</langdata>
</descript>
<timeperd>
<timeinfo>
<rngdates>
<begdate>18940101</begdate>
<begtime>000000</begtime>
<enddate>20020101</enddate>
<endtime>000000</endtime>
</rngdates>
</timeinfo>
<current>publication date</current>
</timeperd>
<spdom>
<bounding>
<westbc>-75.789988</westbc>
<eastbc>-75.047775</eastbc>
<northbc>39.839605</northbc>
<southbc>38.450799</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>none</themekt>
<themekey>boundary line</themekey>
<themekey>boundary lines</themekey>
<themekey>state boundary</themekey>
<themekey>boundary</themekey>
<themekey>political</themekey>
<themekey>boundaries</themekey>
<themekey>political line</themekey>
</theme>
<theme>
<themekt>ISO 19115 Topic Categories</themekt>
<themekey>boundaries</themekey>
</theme>
<place>
<placekt>U.S. Department of Commerce/National Institute of Standards and Technology, 1995, Countries, Dependencies, Areas of Special Sovereignty, and Their Principal Administrative Divisions (Federal Information Processing Standard (FIPS) 10-4), Washington, D.C.</placekt>
<placekey>U.S.</placekey>
<placekey>United States</placekey>
</place>
<place>
<placekt>U.S. Department of Commerce/National Institute of Standards and Technology, 1987, Codes for the Identification of the States, the District of Columbia and the Outlying Areas of the United States, and Associated Areas (Federal Information Processing Standard (FIPS) 5-2), Washington, D.C.</placekt>
<placekey>New Jersey</placekey>
<placekey>Pennsylvania</placekey>
<placekey>Delaware</placekey>
<placekey>Maryland</placekey>
</place>
</keywords>
<accconst>use constraints: None. Acknowledgement of the U.S. Geological Survey would be appreciated in products derived from these data.</accconst>
<useconst>None</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>Delaware Geospatial Data Exchange</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>Delaware Geospatial Data Exchange</address>
<city>Dover</city>
<state>DE</state>
<postal>19904</postal>
<country>US</country>
</cntaddr>
<cntvoice>302-739-9611</cntvoice>
<cntemail>DTI_GIS@state.de.us</cntemail>
</cntinfo>
</ptcontac>
<browse>
<browsen>withheld</browsen>
<browsed>thumbnail</browsed>
<browset>png</browset>
</browse>
<browse>
<browsen>withheld</browsen>
<browsed>large_thumbnail</browsed>
<browset>png</browset>
</browse>
<native>ESRI ArcCatalog 9.1.0.722</native>
<status>
<progress>Complete</progress>
<update>None planned</update>
</status>
<natvform Sync="TRUE">File Geodatabase Feature Class</natvform>
</idinfo>
<dataqual>
<posacc>
<horizpa>
<qhorizpa>
<horizpae>No formal horizontal positional accuracy testing has been performed to qualify or validate these data. The horizontal positional accuracy of the source data used to generate this boundary varies greatly. Accordingly, the placement of boundary lines on land are generally more horizontally accurate and reliable than the position of boundary lines as they exists on large water bodies such as the Delaware Bay and the Atlantic Ocean. These boundary lines are positoned so they are coincident with known boundary monuments and boundary points. Boundary monument positions were based upon NGS coordinates as documented in several joint agreements between the States of Delaware, New Jersey, Maryland and Pennsylvania. These monument positions were stated to be within first and second order horizontal network accuracy. Not used were the computed boundary points and boundary reference monument positions from "Exhibit C" of the Joint Agreement between Delaware and New Jersey along the 1934 mean low water line (20010829). Boundary, boundary monument, and boundary reference monument positions were calculated and included in this file along the mean low water line of the Delaware - New Jersey boundary. These values were calculated from descriptions in the 1934/1935 U.S. Supreme Court Decree.</horizpae>
</qhorizpa>
</horizpa>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<pubdate>19350603</pubdate>
<pubtime>000000</pubtime>
<title>U.S. Supreme Court (Decree), State of New Jersey v. State of Delaware, No. 11, 295 U.S. 694 (1934/1935)</title>
</citeinfo>
</srccite>
<typesrc>None</typesrc>
<srccitea>U.S. Supreme Court (Decree), State of New Jersey v. State of Delaware, No. 11, 295 U.S. 694 (1934/1935)</srccitea>
<srccontr>A narrative describing the boundary between Delaware and New Jersey as decided by the U.S. Supreme Court. Boundary point, boundary monument, and boundary reference monument positions were calculated along the mean low water line of the Delaware - New Jersey boundary. These values were calculated from descriptions contained in this document and transformed to the correct datum.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<pubdate>18940101</pubdate>
<pubtime>000000</pubtime>
<title>The Boundary Line Between the States of Pennsylvania and Delaware</title>
</citeinfo>
</srccite>
<typesrc>None</typesrc>
<srccitea>The Boundary Line Between the States of Pennsylvania and Delaware</srccitea>
<srccontr>A descriptive and historical account of the circular portion of the Delaware boundary. An understanding of how the circular portions of the boundary were delineated was necessary for the creation of the computer programs (AMLs) which were used to create the digital representation of the boundary.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<title>Joint Agreements between the States of Delaware, New Jersey, Pennsylvania, and Maryland</title>
</citeinfo>
</srccite>
<typesrc>None</typesrc>
<srccitea>Joint Agreements between the States of Delaware, New Jersey, Pennsylvania, and Maryland</srccitea>
<srccontr>References describing information pertinent to the Delaware boundary. Of critical importance are the NAD83 (1991) point positions for boundary and reference monuments for the Delaware boundary.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<pubdate>19930101</pubdate>
<pubtime>000000</pubtime>
<title>USGS 7.5 minute DLGs</title>
</citeinfo>
</srccite>
<srcscale>24</srcscale>
<typesrc>None</typesrc>
<srccitea>USGS 7.5 minute DLGs</srccitea>
<srccontr>A digital line file containing the placement of the mean low water line boundary between Delaware and New Jersey.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<pubdate>19341101</pubdate>
<pubtime>000000</pubtime>
<title>The Circular Boundary of Delaware</title>
</citeinfo>
</srccite>
<typesrc>None</typesrc>
<srccitea>The Circular Boundary of Delaware</srccitea>
<srccontr>A description and history of the circular portion of the Delaware boundary. An understanding of how the circular portions of the boundary were delineated was necessary for the creation of the computer programs (AMLs) which were used to crete the digital representation of the boundary.</srccontr>
</srcinfo>
<procstep>
<procdesc>Dataset copied.</procdesc>
</procstep>
<procstep>
<procdesc>Dataset copied.</procdesc>
</procstep>
<procstep>
<procdesc>Metadata imported.</procdesc>
</procstep>
<procstep>
<procdesc>Mr. William Schenck of the Delaware Geological Survey graciously provided most of the sources that were used either directly or indirecly to create this version of the lines comprising the Delaware State boundary. A text file containing NAD83 (1991) point positions for boundary and reference monuments was created. This information was extracted from Joint Agreements between the States of Delaware, New Jersey, Pennsylvania, and Maryland. Not used were computed boundary points and boundary reference monument positions from "Exhibit C" of the Joint Agreement between Delaware and New Jersey along the 1934 mean low water line (20010829). Added to this text file were 1) additional calculated positions along the Delaware - New Jersey boundary originating from the 1934/1935 U.S. Supreme Court Decree, and 2) other pertinent miscellaneous point positions used in the computation and delineation of the boundary. The mean low water line portion of the boundary between the States of Delaware and New Jersey was revised by locally registering the composite map from the 1934/1935 U.S. Supreme Court Decree with the USGS boundary DLG data and the 2002 orthoimage. The geometry of this revised boundary was then registered to the calculated positions of appropriate monuments as described in the 1934/1935 U.S. Supreme Court Decree. A series of GIS computer software (ESRI Arc Macro Language) - AML) programs were developed by Mr. George Miller of the USGS that used as input, the positional data from the source information listed above. Output from this program yielded an an ESRI coverage. The ESRI coverage data were then exported to point, line, and polygon shapefiles. The line shapefile was then interactively edited in order to fulfill specific content and attribution requirements.</procdesc>
<procdate>20031201</procdate>
<proctime>000000</proctime>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>U.S. Geological Survey</cntorg>
<cntper>George Miller</cntper>
</cntorgp>
<cntaddr>
<addrtype>unknown</addrtype>
<address>1400 Independence Road</address>
<city>Rolla</city>
<state>Missouri</state>
<postal>65401</postal>
</cntaddr>
<cntvoice>573/308-3519</cntvoice>
</cntinfo>
</proccont>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct>Vector</direct>
<ptvctinf>
<esriterm Name="BOUNDARIES_STATE_COUNTY">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<planar>
<planci>
<plance>coordinate pair</plance>
<coordrep>
<absres>0.00000000222090124069041</absres>
<ordres>0.00000000222090124069041</ordres>
</coordrep>
<plandu Sync="TRUE">meters</plandu>
</planci>
</planar>
<geodetic>
<horizdn>D North American 1983 HARN</horizdn>
<ellips>GRS 1980</ellips>
<semiaxis>6378137.0</semiaxis>
<denflat>298.257222101</denflat>
</geodetic>
<cordsysn>
<geogcsn Sync="TRUE">GCS_North_American_1983_HARN</geogcsn>
<projcsn Sync="TRUE">NAD_1983_HARN_StatePlane_Delaware_FIPS_0700</projcsn>
</cordsysn>
</horizsys>
<vertdef>
<altsys>
<altenc Sync="TRUE">Explicit elevation coordinate included with horizontal coordinates</altenc>
<altres Sync="TRUE">1.000000</altres>
</altsys>
</vertdef>
</spref>
<eainfo>
<detailed Name="BOUNDARIES_STATE_COUNTY">
<enttyp>
<enttypl>STATE_OUTLINE_LAND</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<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>
<attrdef Sync="TRUE">Internal feature number.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Shape</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
<attalias Sync="TRUE">SHAPE</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">FID_DE_BOUNDARY_STATE_OUTLINE</attrlabl>
<attalias Sync="TRUE">FID_DE_BOUNDARY_STATE_OUTLINE</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>TYPE</attrlabl>
<attalias Sync="TRUE">TYPE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">25</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">FID_Kent_County_Bndy</attrlabl>
<attalias Sync="TRUE">FID_KENT_COUNTY_BNDY</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">ID</attrlabl>
<attalias Sync="TRUE">ID</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">NAME</attrlabl>
<attalias Sync="TRUE">NAME</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">SHAPE.AREA</attrlabl>
<attalias Sync="TRUE">SHAPE.AREA</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">SHAPE.LEN</attrlabl>
<attalias Sync="TRUE">SHAPE.LEN</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
</eainfo>
<metainfo>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Delaware Geospatial Data Exchange</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>Delaware Division of Technology and Information</address>
<city>Dover</city>
<state>DE</state>
<postal>19904</postal>
<country>US</country>
</cntaddr>
<cntvoice>302-739-9611</cntvoice>
<cntemail>DTI_GIS@state.de.us</cntemail>
</cntinfo>
</metc>
<metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<mettc>local time</mettc>
<langmeta Sync="TRUE">en</langmeta>
<metd Sync="TRUE">20120509</metd>
</metainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Delaware Geospatial Data Exchange</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>Delaware Geospatial Data Exchange</address>
<city>Dover</city>
<state>DE</state>
<postal>19904</postal>
<country>US</country>
</cntaddr>
<cntvoice>302-739-9611</cntvoice>
<cntemail>DTI_GIS@state.de.us</cntemail>
</cntinfo>
</distrib>
<resdesc Sync="TRUE">Downloadable Data</resdesc>
</distinfo>
<dataIdInfo>
<envirDesc Sync="FALSE">Esri ArcGIS 10.2.2.3552</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="FALSE">BOUNDARIES_STATE_COUNTY</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<idPurp>This dataset was created by merging three different data sets together. Two of the data sets were from the U.S. Geological Survey and the thrid from Kent County, DE.
The representation of the Delaware State boundary line and the coastal shore line were created in support of USGS's The National Map project and the Delaware's Spatial Data Framework/DataMIL project.
The County lines were created by Kent County, DE to show where approximately the Kent Boundary lines up with New Castle and Sussex Counties.</idPurp>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;This geospatial data file comprises the bounding lines relating to the political boundary delineation for the State of Delaware&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;New Castle, Kent, and Sussex Counties have come to an agreement on where approximately the county boundaries should fall. The Kent and Sussex County Boundary has momuments which set the boundary line. These momuments have been GPS.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idCredit>U.S. Geological Survey Kent County Levy Court - Danielle Lamborn GIS Specialist 302-744-2410 or 302-744-2416 danielle.lamborn@co.kent.de.us</idCredit>
<searchKeys>
<keyword>boundary line</keyword>
<keyword>boundary lines</keyword>
<keyword>state boundary</keyword>
<keyword>boundary</keyword>
<keyword>political</keyword>
<keyword>boundaries</keyword>
<keyword>political line</keyword>
<keyword>boundaries</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;None&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<westBL Sync="TRUE">-75.789988</westBL>
<eastBL Sync="TRUE">-74.936685</eastBL>
<northBL Sync="TRUE">39.839605</northBL>
<southBL Sync="TRUE">38.450426</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
</dataIdInfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName>
<mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer>
<mdChar>
<CharSetCd Sync="TRUE" value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<distInfo>
<distributor>
<distorTran>
<onLineSrc>
<orDesc Sync="TRUE">002</orDesc>
<protocol Sync="TRUE">Local Area Network</protocol>
</onLineSrc>
</distorTran>
<distorFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distorFormat>
</distributor>
<distFormat>
<formatName Sync="FALSE">Feature Class</formatName>
</distFormat>
</distInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="3857" value="26957">NAD_1983_HARN_StatePlane_Delaware_FIPS_0700</identCode>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">8.2.6</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="BOUNDARIES_STATE_COUNTY">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<Esri>
<SyncDate>20140917</SyncDate>
<SyncTime>10450600</SyncTime>
<ModDate>20140917</ModDate>
<ModTime>10450600</ModTime>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">BOUNDARIES_STATE_COUNTY</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">168046.065000</westBL>
<eastBL Sync="TRUE">241083.696900</eastBL>
<southBL Sync="TRUE">50102.276700</southBL>
<northBL Sync="TRUE">204220.881600</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_WGS_1984</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Meter (1.000000)</csUnits>
<projcsn Sync="TRUE">WGS_1984_Web_Mercator_Auxiliary_Sphere</projcsn>
<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/10.1'&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>
</coordRef>
</DataProperties>
<ArcGISProfile>ItemDescription</ArcGISProfile>
</Esri>
<mdDateSt Sync="TRUE">20140917</mdDateSt>
</metadata>
