<?xml version="1.0" encoding="UTF-8" standalone="no"?><metadata xml:lang="en">
    <Esri>
        <CreaDate>20200727</CreaDate>
        <CreaTime>12260800</CreaTime>
        <ArcGISFormat>1.0</ArcGISFormat>
        <ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
        <SyncOnce>FALSE</SyncOnce>
        <DataProperties>
            <itemProps>
                <itemName Sync="TRUE">ordinances</itemName>
                <nativeExtBox>
                    <westBL Sync="TRUE">1182589.560600</westBL>
                    <eastBL Sync="TRUE">1208986.891100</eastBL>
                    <southBL Sync="TRUE">666114.554400</southBL>
                    <northBL Sync="TRUE">693434.781200</northBL>
                    <exTypeCode Sync="TRUE">1</exTypeCode>
                </nativeExtBox>
                <imsContentType export="False"/>
            </itemProps>
            <coordRef>
                <type Sync="TRUE">Projected</type>
                <geogcsn Sync="TRUE">GCS_North_American_1983_HARN</geogcsn>
                <csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
                <projcsn Sync="TRUE">NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet</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.6'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983_HARN&amp;quot;,DATUM[&amp;quot;D_North_American_1983_HARN&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Lambert_Conformal_Conic&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,1640416.666666667],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-120.5],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,45.83333333333334],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,47.33333333333334],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,45.33333333333334],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,2927]]&lt;/WKT&gt;&lt;XOrigin&gt;-117498300&lt;/XOrigin&gt;&lt;YOrigin&gt;-98850300&lt;/YOrigin&gt;&lt;XYScale&gt;10000&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;0.00020000000000000001&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;2927&lt;/WKID&gt;&lt;LatestWKID&gt;2927&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
            </coordRef>
        </DataProperties>
        <SyncDate>20200128</SyncDate>
        <SyncTime>15165700</SyncTime>
        <ModDate>20210701</ModDate>
        <ModTime>10075200</ModTime>
        <ArcGISProfile>FGDC</ArcGISProfile>
        <scaleRange>
            <minScale>150000000</minScale>
            <maxScale>5000</maxScale>
        </scaleRange>
    </Esri>
    <mdLang>
        <languageCode value="eng"/>
        <countryCode Sync="TRUE" value="USA"/>
    </mdLang>
    <mdChar>
        <CharSetCd value="004"/>
    </mdChar>
    <mdHrLv>
        <ScopeCd value="005"/>
    </mdHrLv>
    <mdDateSt Sync="TRUE">20210701</mdDateSt>
    <mdStanName>ArcGIS Metadata</mdStanName>
    <mdStanVer>1.0</mdStanVer>
    <distInfo>
        <distributor>
            <distorOrdPrc>
                <resFees units="">Charges based on time to complete the request.</resFees>
                <ordInstr>If you have questions or need supplemental information, please call the Assessor-Treasurer Operations Team at 253-798-3134. Website to order Pierce County Open GeoSpatial Data Portal &lt;http://gisdata.piercecowa.opendata.arcgis.com/&gt; Requests that need individual names will need to contact the Assesor Treasures Office for this data. Requester will need to return a notarized document that pertains to Requester's Warranty Against Commercial Use of Lists: RCW 42.17.260(9) prohibits the release of lists of individuals requested for commercial purposes, and the requester expressly represents that no such use of any such list will be made by requester or its employees, agents, transferee(s) or vendee(s). "Commercial purposes" means to facilitate any profit expecting activity. This information is available on a cd, contact the Assessor-Treasurer Operations Team at 253-798-3134.</ordInstr>
            </distorOrdPrc>
            <distorTran>
                <onLineSrc>
                    <orDesc>.</orDesc>
                    <linkage>http://gisdata.piercecowa.opendata.arcgis.com/</linkage>
                </onLineSrc>
            </distorTran>
        </distributor>
        <distFormat>
            <formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
        </distFormat>
    </distInfo>
    <dataIdInfo>
        <idCitation>
            <resTitle>Tax Parcels</resTitle>
            <citRespParty>
                <rpOrgName>Pierce County Assessor-Treasurer's Office</rpOrgName>
                <role>
                    <RoleCd value="006"/>
                </role>
            </citRespParty>
            <presForm>
                <PresFormCd value="005"/>
            </presForm>
            <presForm>
                <fgdcGeoform>vector digital data</fgdcGeoform>
            </presForm>
            <otherCitDet>The Assessor-Treasurer's Office edits their maintenance "Parcel" geodatabase daily. The "Parcel" database is also known as the "ATR Parcel Geodatabase" and includes 26 data sets (feature classes) other than the tax parcel data. The maintenance database is published daily in the evening. The currency (most recent edit date) of this data can be determined by looking at the "EditDate" field and sorting to find the most recent date.</otherCitDet>
        </idCitation>
        <idAbs>Ordinances from August 1995 to present enacting changes to Zoning and Future Land Use (Comprehensive Plan) designations are included within this feature class. The City's comprehensive plan was adopted in 1994 and is the reason why only ordinances from 1995 to the present are documented within this feature class.</idAbs>
        <idPurp>This feature class is to be used by anyone for research and tracking of ordinances changing Zoning and Future Land Use (Comprehensive Plan) designations.</idPurp>
        <idCredit>Jennifer Recco - GIS Coordinator (ret)
Darrell Wilson, 2017-2018 GIS Intern</idCredit>
        <idStatus>
            <ProgCd value="007"/>
        </idStatus>
        <resMaint>
            <maintFreq>
                <MaintFreqCd value="002"/>
            </maintFreq>
            <maintCont>
                <rpOrgName>Pierce County Assessor-Treasurer's Office</rpOrgName>
                <role>
                    <RoleCd value="006"/>
                </role>
                <displayName>Pierce County Assessor-Treasurer's Office</displayName>
            </maintCont>
        </resMaint>
        <placeKeys>
            <keyword>Washington</keyword>
            <keyword>Pierce County</keyword>
        </placeKeys>
        <themeKeys>
            <keyword>taxes</keyword>
            <keyword>legal</keyword>
            <keyword>ownership</keyword>
            <keyword>property</keyword>
            <keyword>parcel</keyword>
            <keyword>condominiums</keyword>
        </themeKeys>
        <searchKeys>
            <keyword>City</keyword>
            <keyword>Ord</keyword>
            <keyword>Ordinance</keyword>
            <keyword>Planning</keyword>
            <keyword>Puyallup</keyword>
        </searchKeys>
        <resConst>
            <LegConsts>
                <useLimit>All users of this data should read through the metadata. Read Disclaimer to and Warranty by Users of Pierce County GIS Data for more information. &lt;http://yakima.co.pierce.wa.us/GeoDataExpress/disclaimer.cfm&gt;</useLimit>
                <othConsts>All users of this data should read through the metadata. Read Disclaimer to and Warranty by Users of Pierce County GIS Data for more information. &lt;http://yakima.co.pierce.wa.us/GeoDataExpress/disclaimer.cfm&gt;</othConsts>
            </LegConsts>
        </resConst>
        <resConst>
            <SecConsts>
                <class>
                    <ClasscationCd value="001"/>
                </class>
                <classSys>None</classSys>
                <handDesc>None</handDesc>
            </SecConsts>
        </resConst>
        <resConst>
            <Consts>
                <useLimit>&lt;p&gt;Disclaimer to and Warranty by Users of City of Puyallup GIS Data &lt;/p&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt; 1. Limitations The City of Puyallup makes no warranty, expressed or implied, concerning the data's content, accuracy, currency or completeness, or concerning the results to be obtained from queries or use of the data. ALL DATA IS EXPRESSLY PROVIDED &amp;quot;AS IS&amp;quot; AND &amp;quot;WITH ALL FAULTS&amp;quot;. The City of Puyallup makes no warranty of fitness for a particular purpose, and no representation as to the quality of any data. Users of data are responsible for ensuring the accuracy, currency and other qualities of all products (including maps, reports, displays and analysis) produced from or in connection with the City of Puyallup's GIS data. No employee or agent of the City of Puyallup is authorized to waive or modify this paragraph. If a user informs others that a product is based on the City of Puyallup's data, the City of Puyallup specifically requests and directs that the user also disclose the limitations contained in this paragraph and in paragraph 4. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt; 2. Data Interpretation City of Puyallup data is developed and maintained solely for the City of Puyallup business functions, and use or interpretation of data by the Requestor or others is solely their responsibility. The City of Puyallup's Community Development Center will provide data interpretation services. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt; 3. Spatial Accuracy Map data can be plotted or represented at various scales other than the original source of the data. The Requestor is responsible for adhering to industry standard mapping practices which specify that data utilized in a map or analysis, separately or in combination with other data, will be produced at the largest scale common to all data sets. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt; 4. No City of Puyallup Liability City of Puyallup shall not be liable to the Requestor (or transferees or venders or Requestor) for damages of any kind, including lost profits, lost savings or any other incidental of consequential damages relating to the providing of the data or the use of it. The Requestor shall have no remedy by law or equity against the City of Puyallup in the case the data provided is inaccurate, incomplete or otherwise defective in any way. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt; 5. Requester's Warranty Against Commercial Use of Lists RCW 42.17.260 (9) prohibits the release of lists of individuals requested for commercial purposes, and Requestor expressly represents that no such use of any such list will be made by Requestor or its transferee)s) or vender (s). &amp;quot;Commercial Purposes&amp;quot; means contacting or in some way personally affecting the individuals identified on the list with the purpose of facilitating one's commercial activities. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt; 6. Secondary Data Dissemination Requestors may not secondarily disseminate (give City of Puyallup data to other entities) without prior written permission from the City of Puyallup. &lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt; 7. Project Data Requestors are encouraged to supply their project data back to the City of Puyallup for use by the City of Puyallup.&lt;/div&gt;</useLimit>
            </Consts>
        </resConst>
        <aggrInfo>
            <aggrDSName>
                <resTitle>Assessor-Treasurer Parcel Project</resTitle>
                <citRespParty>
                    <rpOrgName>Pierce County Assessor-Treasurer</rpOrgName>
                    <role>
                        <RoleCd value="006"/>
                    </role>
                </citRespParty>
                <otherCitDet>At the end of November 2010 the Assessor-Treasurer's office made significant changes to the way the parcel data was maintained. The old coverage library system was replaced by a parcel geodatabase. The parcel geodatabae allowed data to be collected and maintained more efficiently. The parcel data schema was changed at this time. The related coverage libraray based themes were: Centerlines and Right-of-ways, Easements, Harbors, Hydrography Land Base Land History Lines, PLSS RTSQ, RTSQQ, RTS, Range Township, Survey Monument Lines and Tax Parcels.</otherCitDet>
            </aggrDSName>
            <assocType>
                <AscTypeCd value="001"/>
            </assocType>
        </aggrInfo>
        <aggrInfo>
            <aggrDSName>
                <resTitle>Tax Assessment paper maps</resTitle>
                <citRespParty>
                    <rpOrgName>Pierce County Assessor-Treasurer</rpOrgName>
                    <role>
                        <RoleCd value="006"/>
                    </role>
                </citRespParty>
                <citRespParty>
                    <rpOrgName>Pierce County</rpOrgName>
                    <rpCntInfo>
                        <cntAddress>
                            <delPoint>Tacoma, WA</delPoint>
                        </cntAddress>
                    </rpCntInfo>
                    <role>
                        <RoleCd value="010"/>
                    </role>
                </citRespParty>
                <presForm>
                    <fgdcGeoform>Maps</fgdcGeoform>
                </presForm>
                <otherCitDet>The paper maps were converted to digital format during the "Parcel Conversion" project in the mid 1990's. After the project was complete only the digital map data was updated.</otherCitDet>
            </aggrDSName>
            <assocType>
                <AscTypeCd value="001"/>
            </assocType>
        </aggrInfo>
        <aggrInfo>
            <aggrDSName>
                <resTitle>Assessor-Treasurer's Parcel Geodatabase</resTitle>
                <citRespParty>
                    <rpOrgName>Pierce County Assessor-Treasurer</rpOrgName>
                    <role>
                        <RoleCd value="006"/>
                    </role>
                </citRespParty>
                <otherCitDet>The Assessor-Treasurer's Office is editing their maintenance "Parcel" database daily as needed. The maintenance database is published (uploaded) daily in the evening. The currency or most recent edit date to the data can be determined by looking at the "EditDate" field and sorting to find the most recent date.</otherCitDet>
            </aggrDSName>
            <assocType>
                <AscTypeCd value="001"/>
            </assocType>
        </aggrInfo>
        <aggrInfo>
            <aggrDSName>
                <resTitle>Orthophotography</resTitle>
                <citRespParty>
                    <rpOrgName>Triathlon Mapping (formerly NEIS Mapping)</rpOrgName>
                    <role>
                        <RoleCd value="006"/>
                    </role>
                </citRespParty>
                <otherCitDet>Specific orthophotos are: "County - 1998/99 - Ortho" "County - 2001 - Ortho" "County - 2002 - Ortho"</otherCitDet>
            </aggrDSName>
            <assocType>
                <AscTypeCd value="001"/>
            </assocType>
        </aggrInfo>
        <spatRpType>
            <SpatRepTypCd value="001"/>
        </spatRpType>
        <dataLang>
            <languageCode value="eng"/>
            <countryCode Sync="TRUE" value="USA"/>
        </dataLang>
        <envirDesc>ESRI ArcGIS 10.0.5.4400</envirDesc>
        <dataExt>
            <geoEle>
                <GeoBndBox>
                    <westBL>-122.847869</westBL>
                    <eastBL>-121.44062</eastBL>
                    <southBL>46.724181</southBL>
                    <northBL>47.422256</northBL>
                </GeoBndBox>
            </geoEle>
        </dataExt>
        <suppInfo>The parcel geodatabase has been designed to provide a self-describing context for each feature as much as possible.   However the data has been built for 3d which introduces some complexity.  To simplify the data set use the following query to capture a single record/feature for each unique parcel number including condos.  (TaxParcelType = 'Base Parcel' OR TaxParcelType = 'Tax Purpose Only' OR Land_Acres&gt;0)  This query will capture the records that have the fields populated.  Use this query prior to joining accessory Assessor's tables.  

If you have any questions that are not answered in this metadata contact the contact person found in this metadata. Procedures_Used Reviews_Applied Each tile in the parcel library went through an extensive three-step QC process: 1) Initial QC, which compares the scrubbed paper maps to the digital product to check for completeness and accuracy (spatial and data content) 2) Parcel verification. Parcel legal discriptions were read to verify the parcel number and descriptions were correct per database entries in the X system. 3) Map maintenance. Map maintenance is an onging update process for ATR Parcel Geodatabase. Related_Spatial_and_Tabular_Data_Sets See "Other_Citation_Details" under Assessor-Treasurer Parcel Project. Other_References_Cited Pierce County, Washington, ARC/INFO Data Base Design, Final Production Data Base Design / prepared by ASI: revised February 10, 1995. Note: The accuracy goal for the Data Shift Project is +/- 10 foot difference between datasets. There may be areas where the shift was not able to achieve this goal. Mobile Homes are a separate theme that also contain a Tax Parcel Number and must be taken into account to get an accurate sum of all tax parcels within Pierce County. Sometime in the Fall the values in the fields Land Value and Improvement Value (which are currently for 2015) will be changed to reflect the accessed values for taxes payable in 2016. These 2015 values are available from the Assessor-Treasurer's Office beginning in June, but are not complete for all parcels in the County. The 2015 values are updated in the shapefile sometime in the Fall when all the values have been assessed for taxes payable in 2016.</suppInfo>
        <dataChar>
            <CharSetCd value="004"/>
        </dataChar>
        <dataExt>
            <geoEle>
                <GeoBndBox esriExtentType="search">
                    <exTypeCode Sync="TRUE">1</exTypeCode>
                    <westBL Sync="TRUE">-122.342573</westBL>
                    <eastBL Sync="TRUE">-122.233953</eastBL>
                    <northBL Sync="TRUE">47.221814</northBL>
                    <southBL Sync="TRUE">47.145288</southBL>
                </GeoBndBox>
            </geoEle>
        </dataExt>
        <idPoC>
            <rpIndName>William Keller</rpIndName>
            <rpOrgName>City of Puyallup</rpOrgName>
            <rpPosName>GIS Coordinator</rpPosName>
            <role>
                <RoleCd value="007"/>
            </role>
            <rpCntInfo>
                <cntAddress addressType="both">
                    <delPoint>333 S Meridian</delPoint>
                    <city>Puyallup</city>
                    <adminArea>WA</adminArea>
                    <postCode>98371</postCode>
                    <eMailAdd>wkeller@puyallupwa.gov</eMailAdd>
                    <country>US</country>
                </cntAddress>
                <cntPhone>
                    <voiceNum tddtty="">253-841-5571</voiceNum>
                </cntPhone>
            </rpCntInfo>
        </idPoC>
    </dataIdInfo>
    <dqInfo>
        <dqScope>
            <scpLvl>
                <ScopeCd value="005"/>
            </scpLvl>
        </dqScope>
        <report type="DQTopConsis">
            <evalMethDesc>Polygon and chain-node topology present.</evalMethDesc>
        </report>
        <report type="DQConcConsis">
            <measDesc>Polygon and chain-node topology present.</measDesc>
        </report>
        <report type="DQCompOm">
            <measDesc>All tiles passed the final QC stage. This data is complete for all of Pierce County, except for Fort Lewis, McChord AFB, Mount Rainier NP, and some other federal areas in east Pierce County.</measDesc>
        </report>
        <report type="DQQuanAttAcc">
            <measDesc>The parcel site address data has known quality issues and the County currently uses the street/address centerline data for geocoding. GIS is working with ATR and PALS to get the parcel site address data cleaned up. There are about 10-15% addresses that are incorrect. County departments, as well as the public, use parcel site addresses for business applications and need to understand the quality and accuracy issues of the data.,The parcel site address data has known quality issues and the County currently uses the street/address centerline data for geocoding. GIS is working with ATR and PALS to get the parcel site address data cleaned up. There are about 10-15% addresses that are incorrect.</measDesc>
        </report>
        <report dimension="horizontal" type="DQAbsExtPosAcc">
            <measDesc>This is a tax parcel based theme and is registered to orthophotography. In 2003 the land layer and tax parcels were shifted to align with visual features from the most current orthophotos in the area, all coincident themes were adjusted accordingly. When the tax parcel dataset is used in GIS, the crisp lines can give a false impression of the accuracy level. It is up to the users of GIS to know about data accuracy and take care not to create misleading products. Just because a dataset can be displayed at a scale of 1"=50' does not mean its accuracy is equivalent to that scale.</measDesc>
            <evalMethDesc>In urban areas that used 1:600 scale (.5 foot pixel size) orthophotography, the error is approximately +/- 2.5 feet.</evalMethDesc>
            <measResult>
                <QuanResult>
                    <quanVal>+/-2.5</quanVal>
                </QuanResult>
            </measResult>
        </report>
        <report dimension="vertical" type="DQAbsExtPosAcc">
            <measDesc>Not applicable</measDesc>
        </report>
        <dataLineage>
            <prcStep>
                <stepDesc>On 11/30/2010 the data was no longer maintained in the coverage library format. The data was put into a geodatabase and the database schema changed to take advantage of new features available in ArcGIS 9.3.1. The actual conversion took over a year to complete. The new data is called the ATR Parcel Geodatabase and maintenance start on it as of 12/1/2010.</stepDesc>
                <stepProc>
                    <rpIndName>Tony De Paul</rpIndName>
                    <rpOrgName>Assessor-Treasurer's Office</rpOrgName>
                    <rpPosName>Geographic Information Systems Specialist</rpPosName>
                    <rpCntInfo>
                        <cntPhone>
                            <voiceNum>Geographic Information Systems Specialist</voiceNum>
                            <faxNum>253-798-7108</faxNum>
                        </cntPhone>
                    </rpCntInfo>
                    <role>
                        <RoleCd value="009"/>
                    </role>
                </stepProc>
            </prcStep>
            <prcStep>
                <stepDesc>The parcel dataset is constantly maintained and improved as new plats are entered. ATR staff must reconcile the way new segregations and new parcels are fit into the existing parcels. Sometimes this involves research to correct years-old drawings or source errors. This means that parcel lines can and will change. Therefore, over time, parcel-aligned datasets that have been shifted will need to be adjusted to register the parcel changes.</stepDesc>
                <stepProc>
                    <rpIndName>Tony De Paul</rpIndName>
                    <rpOrgName>Pierce County Assessor-Treasurer (ATR)</rpOrgName>
                    <rpPosName>Geographic Information Systems Specialist</rpPosName>
                    <rpCntInfo>
                        <cntPhone>
                            <voiceNum>(253) 798-7108</voiceNum>
                        </cntPhone>
                    </rpCntInfo>
                    <role>
                        <RoleCd value="009"/>
                    </role>
                </stepProc>
            </prcStep>
            <prcStep>
                <stepDesc>Arc/Info coverages were created by prepping and scrubbing Assessor-Treasurer paper tax assessment maps, which were digitized by a conversion vendor. Each tile then went through an in-house three-step QC process, and is constantly updated by map maintenance.</stepDesc>
                <stepProc>
                    <rpIndName>Tony DePaul</rpIndName>
                    <rpOrgName>Pierce County Assessor-Treasurer's Office</rpOrgName>
                    <rpPosName>Geographic Information Systems Specialist</rpPosName>
                    <rpCntInfo>
                        <cntPhone>
                            <voiceNum>253-798-7108</voiceNum>
                        </cntPhone>
                        <cntAddress addressType="both">
                            <delPoint>2401 S 35th, Suite 142</delPoint>
                            <city>Tacoma</city>
                            <adminArea>WA</adminArea>
                            <postCode>98409</postCode>
                            <country>US</country>
                            <eMailAdd>tdepaul@co.pierce.wa.us</eMailAdd>
                        </cntAddress>
                    </rpCntInfo>
                    <role>
                        <RoleCd value="009"/>
                    </role>
                </stepProc>
            </prcStep>
            <prcStep>
                <stepDesc>In 2001, GIS started an in-house software prototype with the adjustment routines needed to align the parcels to the orthophotos. The results were successful in using one-sixteenth quarter section control and a heads-up display to verify the shift results before acceptance. This software uses a "least-squares" adjustment to move line-work propotionally. Nine control locations are used as adjustment points for each quarter section. The software saves the adjustment information for each parcel, and this information can be used to apply data shift to other datasets. Additionally, right-of-way dimensions are preserved. In many cases, the results of the shifting process exceeded the target accuracy goal of +/- 10 foot difference between parcel lines and orthophoto features. In the parts of the county where the parcel quarter sections did not align they will be redrawn by ATR staff during parcel maintenance.</stepDesc>
                <stepProc>
                    <rpIndName>Steve Savage</rpIndName>
                    <rpOrgName>Pierce County GIS</rpOrgName>
                    <rpPosName>Information Technologist</rpPosName>
                    <rpCntInfo>
                        <cntPhone>
                            <voiceNum>(253) 798-6064</voiceNum>
                        </cntPhone>
                    </rpCntInfo>
                    <role>
                        <RoleCd value="009"/>
                    </role>
                </stepProc>
            </prcStep>
            <prcStep>
                <stepDesc>An AML was run that assembled the shifted Land Base tiles to create a comprehensive dataset of Assessor Treasures data of Pierce County. Specific datasets were then extracted from the Land Base dataset by dissolving attributes. The Land Base is a conglomerate of many themes see "Other_Citation_Details". The AML then used Assessor Treasures tables and joined the data to its respected spatial dataset. No other survey information was extracted. For more survey data please see the PLSS-Pierce County data theme.</stepDesc>
                <stepProc>
                    <rpIndName>De Paul, Tony</rpIndName>
                    <rpOrgName>Pierce County Assessor-Treasurer (ATR)</rpOrgName>
                    <rpPosName>Geographic Information Systems Specialist</rpPosName>
                    <rpCntInfo>
                        <cntPhone>
                            <voiceNum>(253) 798-7108</voiceNum>
                        </cntPhone>
                    </rpCntInfo>
                    <role>
                        <RoleCd value="009"/>
                    </role>
                </stepProc>
            </prcStep>
            <dataSource>
                <srcDesc>Tax Parcels was dissolved from the Polygon Land Base. The parcel table was then joined to the respected spatial dataset. Note: The Land Base (polygon) is used as the source of many themes that are created by dissolving specific attributes, and joining to related tables to the spatial data. An AML is used to accomplish this.</srcDesc>
                <srcScale>
                    <rfDenom>0</rfDenom>
                </srcScale>
            </dataSource>
        </dataLineage>
    </dqInfo>
    <spatRepInfo>
        <VectSpatRep>
            <geometObjs Name="ordinances">
                <geoObjTyp>
                    <GeoObjTypCd Sync="TRUE" value="002"/>
                </geoObjTyp>
                <geoObjCnt Sync="TRUE">648</geoObjCnt>
            </geometObjs>
            <topLvl>
                <TopoLevCd Sync="TRUE" value="001"/>
            </topLvl>
        </VectSpatRep>
    </spatRepInfo>
    <eainfo>
        <detailed Name="ordinances">
            <enttyp>
                <enttypl>TaxParcel</enttypl>
                <enttypt Sync="TRUE">Feature Class</enttypt>
                <enttypc Sync="TRUE">648</enttypc>
            </enttyp>
            <attr>
                <attrlabl>OBJECTID</attrlabl>
                <attrdef>Sequential unique number that are automatically generated by the ESRI software.  The numbers associated with the features change when the data is updated, so this field should not be used as a join field.</attrdef>
                <attrdefs>ESRI</attrdefs>
                <attrdomv>
                    <udom>Sequential unique whole numbers that are automatically generated.</udom>
                </attrdomv>
                <attalias Sync="TRUE">OBJECTID</attalias>
                <attrtype Sync="TRUE">OID</attrtype>
                <attwidth Sync="TRUE">4</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>Coordinates defining the features.</udom>
                </attrdomv>
                <attalias Sync="TRUE">Shape</attalias>
                <attrtype Sync="TRUE">Geometry</attrtype>
                <attwidth Sync="TRUE">0</attwidth>
                <atprecis Sync="TRUE">0</atprecis>
                <attscale Sync="TRUE">0</attscale>
            </attr>
            <attr>
                <attrlabl Sync="TRUE">YEAR</attrlabl>
                <attalias Sync="TRUE">YEAR</attalias>
                <attrtype Sync="TRUE">Integer</attrtype>
                <attwidth Sync="TRUE">4</attwidth>
                <atprecis Sync="TRUE">0</atprecis>
                <attscale Sync="TRUE">0</attscale>
            </attr>
            <attr>
                <attrlabl Sync="TRUE">ORDINANCE_NUMBER</attrlabl>
                <attalias Sync="TRUE">ORDINANCE_NUMBER</attalias>
                <attrtype Sync="TRUE">String</attrtype>
                <attwidth Sync="TRUE">16</attwidth>
                <atprecis Sync="TRUE">0</atprecis>
                <attscale Sync="TRUE">0</attscale>
            </attr>
            <attr>
                <attrlabl Sync="TRUE">EFFECTIVE_DATE</attrlabl>
                <attalias Sync="TRUE">EFFECTIVE_DATE</attalias>
                <attrtype Sync="TRUE">String</attrtype>
                <attwidth Sync="TRUE">16</attwidth>
                <atprecis Sync="TRUE">0</atprecis>
                <attscale Sync="TRUE">0</attscale>
            </attr>
            <attr>
                <attrlabl Sync="TRUE">ACTION</attrlabl>
                <attalias Sync="TRUE">ACTION</attalias>
                <attrtype Sync="TRUE">String</attrtype>
                <attwidth Sync="TRUE">30</attwidth>
                <atprecis Sync="TRUE">0</atprecis>
                <attscale Sync="TRUE">0</attscale>
            </attr>
            <attr>
                <attrlabl Sync="TRUE">FROM_ZONING</attrlabl>
                <attalias Sync="TRUE">FROM_ZONING</attalias>
                <attrtype Sync="TRUE">String</attrtype>
                <attwidth Sync="TRUE">10</attwidth>
                <atprecis Sync="TRUE">0</atprecis>
                <attscale Sync="TRUE">0</attscale>
            </attr>
            <attr>
                <attrlabl Sync="TRUE">TO_ZONING</attrlabl>
                <attalias Sync="TRUE">TO_ZONING</attalias>
                <attrtype Sync="TRUE">String</attrtype>
                <attwidth Sync="TRUE">10</attwidth>
                <atprecis Sync="TRUE">0</atprecis>
                <attscale Sync="TRUE">0</attscale>
            </attr>
            <attr>
                <attrlabl Sync="TRUE">FROM_FUTURE_LANDUSE</attrlabl>
                <attalias Sync="TRUE">FROM_FUTURE_LANDUSE</attalias>
                <attrtype Sync="TRUE">String</attrtype>
                <attwidth Sync="TRUE">10</attwidth>
                <atprecis Sync="TRUE">0</atprecis>
                <attscale Sync="TRUE">0</attscale>
            </attr>
            <attr>
                <attrlabl Sync="TRUE">TO_FUTURE_LANDUSE</attrlabl>
                <attalias Sync="TRUE">TO_FUTURE_LANDUSE</attalias>
                <attrtype Sync="TRUE">String</attrtype>
                <attwidth Sync="TRUE">10</attwidth>
                <atprecis Sync="TRUE">0</atprecis>
                <attscale Sync="TRUE">0</attscale>
            </attr>
            <attr>
                <attrlabl Sync="TRUE">NOTES</attrlabl>
                <attalias Sync="TRUE">NOTES</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_Length</attrlabl>
                <attalias Sync="TRUE">Shape_Length</attalias>
                <attrtype Sync="TRUE">Double</attrtype>
                <attwidth Sync="TRUE">8</attwidth>
                <atprecis Sync="TRUE">0</atprecis>
                <attscale Sync="TRUE">0</attscale>
                <attrdef Sync="TRUE">Length of feature in internal units.</attrdef>
                <attrdefs Sync="TRUE">Esri</attrdefs>
                <attrdomv>
                    <udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
                </attrdomv>
            </attr>
            <attr>
                <attrlabl Sync="TRUE">Shape_Area</attrlabl>
                <attalias Sync="TRUE">Shape_Area</attalias>
                <attrtype Sync="TRUE">Double</attrtype>
                <attwidth Sync="TRUE">8</attwidth>
                <atprecis Sync="TRUE">0</atprecis>
                <attscale Sync="TRUE">0</attscale>
                <attrdef Sync="TRUE">Area of feature in internal units squared.</attrdef>
                <attrdefs Sync="TRUE">Esri</attrdefs>
                <attrdomv>
                    <udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
                </attrdomv>
            </attr>
        </detailed>
        <overview>
            <eaover>There are different attributes for the CountyView tax parcels data than in the LAND coverage that this data originated from. Parcel numbers, area codes, excempt codes, senior citizen exempt codes, land acres, timberland value, land value, improvement value, tax payer name, street address, city/state, zip code, use code, business name, and plat name and number are all included here. There are many caveats for their use, however. Please read relevant descriptions under each attribute field description:</eaover>
            <eadetcit>The LAND_VALUE and IMPR_VAL Dates changes in the fall to the next year.
Update the year in the Attribute Definition to the next year every fall.</eadetcit>
        </overview>
    </eainfo>
    <mdHrLvName Sync="TRUE">dataset</mdHrLvName>
    <refSysInfo>
        <RefSystem>
            <refSysID>
                <identCode Sync="TRUE" code="2927"/>
                <idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
                <idVersion Sync="TRUE">8.9.3(9.0.0)</idVersion>
            </refSysID>
        </RefSystem>
    </refSysInfo>
    <spdoinfo>
        <ptvctinf>
            <esriterm Name="ordinances">
                <efeatyp Sync="TRUE">Simple</efeatyp>
                <efeageom Sync="TRUE" code="4"/>
                <esritopo Sync="TRUE">FALSE</esritopo>
                <efeacnt Sync="TRUE">648</efeacnt>
                <spindex Sync="TRUE">TRUE</spindex>
                <linrefer Sync="TRUE">FALSE</linrefer>
            </esriterm>
        </ptvctinf>
    </spdoinfo>
    <mdContact>
        <rpIndName>Tony De Paul</rpIndName>
        <rpOrgName>Pierce County Assessor-Treasurer's Office</rpOrgName>
        <rpPosName>Geographic Information Systems Specialist</rpPosName>
        <rpCntInfo>
            <cntPhone>
                <voiceNum tddtty="">253-798-7108</voiceNum>
            </cntPhone>
            <cntAddress addressType="both">
                <delPoint>2401 S 35th, Suite 142</delPoint>
                <city>Tacoma</city>
                <adminArea>WA</adminArea>
                <postCode>98409</postCode>
                <country>US</country>
                <eMailAdd>tdepaul@co.pierce.wa.us</eMailAdd>
            </cntAddress>
        </rpCntInfo>
        <role>
            <RoleCd value="006"/>
        </role>
        <displayName>Tony De Paul</displayName>
    </mdContact>
    <mdMaint>
        <maintFreq>
            <MaintFreqCd value="009"/>
        </maintFreq>
        <maintCont>
            <rpOrgName>Pierce County Assessor-Treasurer's Office</rpOrgName>
            <role>
                <RoleCd value="006"/>
            </role>
            <displayName>Pierce County Assessor-Treasurer's Office</displayName>
        </maintCont>
    </mdMaint>
    <mdContact>
        <rpIndName>William Keller</rpIndName>
        <rpOrgName>City of Puyallup</rpOrgName>
        <rpPosName>GIS Coordinator</rpPosName>
        <role>
            <RoleCd value="007"/>
        </role>
        <rpCntInfo>
            <cntAddress addressType="both">
                <delPoint>333 S Meridian</delPoint>
                <city>Puyallup</city>
                <adminArea>WA</adminArea>
                <postCode>98371</postCode>
                <eMailAdd>wkeller@puyallupwa.gov</eMailAdd>
                <country>US</country>
            </cntAddress>
            <cntPhone>
                <voiceNum tddtty="">253-841-5571</voiceNum>
            </cntPhone>
        </rpCntInfo>
        <displayName>William Keller</displayName>
    </mdContact>
    <Binary>
        <Thumbnail>
            <Data EsriPropertyType="PictureX">/9j/4AAQSkZJRgABAQEAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a
HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCACFAMgDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD3+iii
gAooooAKKKKACiiigAoqOfPknBIPHIqqbuaPrF5igdVOGz9On61Lmk7MC9RUMVzDMQEf5sZ2ng/l
U1UAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAJkj3FLnNReegJBzxQsq
O4UA5Peo5le1wFn/ANSfwqnUGrambVobaKJ5pZnA+QA7B/ePI44+tNjvUYDcpXjk9QKxrJ3uCa2H
xXEL3vlC7jDFSpjBG7P1rSiEiQjzWDOMkkDFcpFq/hS8v0uV1a0+0xOQyGUKSRxyDW1PqyTxL/Z0
sc7FwrFMMFB9cGt4LlSTJ5t7lq21K2uY0dZApb+FjgjnFW6466t3t/DdxYzKplfc5bPccrj8a5TT
vFWq6WFAnM0f9yU7h/jW0afMvdZjKvyWUkeuUVxNp8RLeQhbmykQnAyjBh+uK7VTuUEdxmplFx3N
YVIz+Fi0UUVJYUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAZ4dZbiaOP5mjbDj0zzUV1NJaxe
YnDZwMiszxIbjT72HULZyu4bHx0JHIzTrfxdBLsjuLZgWbDEEEAetR7BX5kZOqk3F6G8sEc0ERlR
WYYbp0NVvsKXLTRXNpGISfkIPP19jWgMYGOlVbv7O80EclyYpQ25FV8FvbHcVdi2cF4x0OLRkgvL
aJbnzphEY57RJiMjglsBsZ7kmsyOTWNIha607S7CaNmwbiyjyhHodpz+depNcxvFLlGGwE/vEIH6
15fo/jLxFZ2cYn0SxtbV5OBHH5Q68/LnrWkVdWsZVLLW9jUfX9T1jRheWtpLayQgNJ5igpIvIJXP
BHHQ81S0jULV4bi91Kzt2FvtKFEClmPQYHHan/8ACW63rGvvollY262/lE7zGTlim4DrgAnimaj4
dv44Y4IYwLbeXZmYKEJwMNk9qFGMfdelzKfM/fjqQ6jq+kavKsk1lNayjjfEQ2fqOK7zTfFOl6gy
QQyv5mMbSh/n0rzbVo9G8KLE2szS3EsoLJDAMA49WNc/c+IPEPiC3e10awkhtof9aLGMknPTcw57
VXLGStDYUJTi7y6n0DFPFPu8qRH2na205wfSpK828B+DrzQLK9vtVu1RLmKORDHIwaIjJO7Ix3Hr
0rW0rx7b3WpixnjIVmCRzjox6cjtn+tQ4PW2p0+0StzaXOzoooqDQKKKKACiiigAooooAKKKKACi
iigAooooAy/EKK+hXRIBKoWXI6EV5tC8kqnlQ3rivTdcIGiXhIyPKP8AKuG0HT/7RvQiERlAJCGH
BGa1h8LOSum5pI6rw3e/K+myuzTwIsgJBwUYcc/UEfhWlc6fHcXsF2xbfBnaB3rM1sppt3Z3iRhR
uCSMvB2+lMvfHnhrTsfa9S8nPTdDJz/47UWb1RunH4X0NO/L3Ghzt5W2QxFgjNjBxxk15OttrLWp
N8FhhE+5SpV1I9Mj8a7yX4k+EEjVpNYUJIMqTBJyP++arQ2th4r09n0HVEOnK/K+S3+sA55bB6EV
cLx3RlWjzr3dWZ+gLdHUbYW8CKRGW+2SR5TrjZkdTya7d7O2vApvrWCZ4jkM6Bgp9RnpUenaXbwa
dbxG3MZjw2xn3EN9auwyxStKI3VijbWAOcHHQ1lJtyNacOWNmcP4s0vVXjtZ7CxtNRQs6sk9sr+U
DyGAYE8Ywcda0vBekNouiy3V/DBbXU7GScRxiNVUE447cV1QAUAAAAdhXzx8SNa1XS/iHqsdpf3E
MLiPMSyHYcxqDlelaU1zLlQp2h7x6B408SC90+OHT5CbR5GV3H8ZXBx9Oa82l1CaOZkSylcKeGU9
f0rq/D72viWzW2/s2+slCq4lcjZIxwCV4qnq2kTaVeSwnMkSHiULgGt6cor3OpxVVJvnZ6D8Pdem
1bSmtrneZ7YLy3XaegPuMV2NcP8ADi8t5NPntEgCzw4aSbaAXDEkDPU4ruK56itJnbRd4JsKKKKg
1CiiigAooooAKKKKACiiigAooooAZNDHPE0UqhkYYIPcVXttNs7OUyW8CxuRtJHpVuuY8TeFrvXN
SsL201Q2T2gYcR7i2ce49Ka7XJl3tcm8SXdjNpcsQuIXnRhhAw3A554rxXVPAOsatrX2iyj823uZ
wnyhj5WepbjAHU13d5GYryaNnaRlcgu3Vvc1seGNc0+0vBpc85S6uTmJT908fz61tFuC0OS/PU1O
S1z4PfaLELot7umtvlMc0hYNwCcf3Tn8OldR8MtD1Lw14cuLPVIPs8puWZcsGBXAGeCa6y0t4tHt
53muBseQuWbgDPapd9rqUamOQSxg9UbjNZznJxsdEYJO/Uybq91KeWa0ghcckeYjAHHqM1meH/Du
oeHZ7zbqE89tOQ6xzHLK+TuOe+ePyrorTTLi31GS4e88yJgQsflgEfj3qprHiAabdi3Nt5nyhs7s
f0rNxla0Q0XvSLAe6PVyPqaoL4N0a9v7zUr+1ju7q7AV2lAYIAABtHY8detWNJ1qLVrloRamLau7
O/P9K20QIuBUxjOMtS04yV0cfp3hRtAkmdr5rqN2AiDqQyAds5wfyFYGrazpsOpzRz39ukinlWkA
Ir0W9BaIq2CeoNfOHiHRLjxB8U7nTLYkPNMoLAZ2DAycZGcVpSfPUdzGrBJJI9Y8Ia/odvf3atql
ijzBdn71QXOTn69a9CBDAEHIPQ14g/wWvNEjbUo9fjka2HmBPspG7Hb79e02UbRWMEbNuZY1Bb14
q6lt0y6SlFcrJ6KKKzNQooooAKKKKACiiigAooooAKKKKAK9+StjMVJBCHBBxXJ/brr/AJ+Jf++j
XWX/APx4T/7hrjFIDAkZFBjV3HGyklJkNuzlud23Oar/AGSBLpJzbxieI/K5Qbl+h7V0rXkcFmsi
KCMD5A3SsKR/MlZ8Y3HOKzhOT3IlFR2LkDyakTaXMjvEw5GfTmtrTLSKxXyYdwQknk55rL0q0kWT
z3BUY4BHWl8R+I7TwxpMuoXJVio/dxbsGRvQVEpSc0omsEkuZm7eXEVrbvLNOkSAY3McDPauJ+HJ
bxB4ckutXJubpLmSLfJ1Cg8CsbSfiPa+Nr9NGm0ZoVf95vNxuwV5HG0eldlotnaaDZNaWEPlRM5c
qGJ5P1rW7ppqS1HeMn5GjY2kNnqMkUNkyLtz5+eDk9K0LllSBmZ9gGPmP1rOvNX+w2Qm8szNuwVB
wRV+2lF1axSvHt3qG2HnFUndXBWXuoIpYbtSyHcAcEkEVUi8P6TDqZ1GOwgW8P8Ay2CDd6da0gAO
lFG2xXqUtYAOj3YJxmJh+lWov9Sn+6KglaC732odWdSrMoPTnP8ASrVMAooopDCiiigAooooAKKK
KACiiigAooooAbIiyRsjDKsMGqMunWkMTOlr5jKMhR1NaFFFhNXKNtawTQLJJZLEzdUYDIqC7tXS
dTbwDZjnCitWipcUwscN4tvrhdBv7bS5mbVgqhIImzICTngDnOAT+BrxS+8O+M9SnM17pmq3Eh/i
kjdsfTNfTktnbzTxzvEpmjJKPjkcY/kaY5nSzkl8kNMoYrErfex0GfenGcqWkFciVNS3Z88eFNC8
SaDrEeptoGoOkYKlREQ2DxkA169Hq1rbxf6dcLbSbRIUnOxlU9yD06H8q6qJmeJGdNjkAlc5wfSu
b8QeChr1zc3H2zyTPbCDGzOMFuevvUKr7aVpKwnScFeOpWh8TaDcSrFDrFjJIxwqrOpJPsM10k+0
C0me1llkDBQUz8vufauXj8JeENDtbaB7GK5uoQOQMs7epq/eX2sXQ2Q2s0EXQBUOfzrVQSegnKy1
Ny91e0sM+ZLufHEa8msh7/U9QuIlFtLFauwztU8j60ad4ciubNZbszxzEnK5x39xXSQxLBCkSklU
UKM09ENKUt9EQWunW1k7vBHtZwAxyTmrVFFSaJW2CiiigYUUUUAFFFFABRRRQAUUUUAFFFFABRRR
QAUUUUAFFFFACbR6VC1qrzmVnk+7t2biF/Kp6KSSWwFEaRYBt32dM5zmr1FFMSSWwUUUUDCiiigA
ooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACi
iigAooooA//Z</Data>
        </Thumbnail>
    </Binary>
</metadata>