Deeds and Easements

Jennifer Recco, GIS Coordinator July 15, 2011 Deeds and Easements vector digital data See Cross Reference and Source Information for additional citation details. deeds_and_easements This dataset contains deeds, easements, release of easements, covenants, vacations and vacations with easements made with the city and are in city possession. Private transactions are not part of this dataset. The purpose of this dataset is to give the viewer the means to locate a feature, determine its type, and by using the link found in each feature's attribution review that feature's documentation. It may help the viewer to open Pierce County's RTSQ feature class to understand the nomenclature of the doument naming system. 'Deeds and Easements' are kept in AutoCAD format by Development Engineering staff. The AutoCAD drawing is the basis for this dataset and it contains more types of features than found within this dataset. Features in the AutoCAD drawing that are not included or part of this dataset are: Temporary Construction Easements, LID's, Concomitant Agreements, Preannexation Zoning Agreements, Development Agreements, Mitigation Agreements, Ordinances (dependant on nature of ordinance), Covenants to join LID's, Use of ROW Easements, Leases, Possession and Use Agreements, Sewer Connection Agreements, and Utility Extension Agreements. en July 15, 2011 February 2011 Complete Annually -122.330180 -122.211028 47.222259 47.146833 1185670.902919 1214703.423500 666606.522619 693471.906100 NA Deed Easement Vacation Covenant Release of Easement Vacation with Easement City of Puyallup Puyallup Disclaimer to and Warranty by Users of City of Puyallup GIS Data 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 'AS IS' AND 'WITH ALL FAULTS'. 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. 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. 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. 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. 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). 'Commercial Purposes' means contacting or in some way personally affecting the individuals identified on the list with the purpose of facilitating one's commercial activities. 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. 7. Project Data Requestors are encouraged to supply their project data back to the City of Puyallup for use by the City of Puyallup. All users must read the metadata before using the data. Jennifer Recco City of Puyallup GIS Coordinator mailing and physical address

1100 39th Ave SE, Bldg C

Puyallup WA 98374 253-841-5571 253-841-5589 jennifer@ci.puyallup.wa.us 8AM - 5PM Jennifer Recco, GIS Coordinator - GIS conversion, feature research, document reconciliation and dataset creation. Ben Peterson, Development Engineering volunteer. His project was updating the city's deeds and easement documentation and 'Go To Guy' for the research of features/documents not found or inconsistencies noted in, between, or otherwise part of the source data. Linda Lian, Development Technician, custodian of the AutoCAD drawing Unclassified This data is available to anyone who requests it through the city's Public Record Request process. ESRI ArcCatalog 9.3.1.3000 Linda Lian, Development Technician, Development Services Department February 2011 Deeds and Easements.dwg Ben Peterson, Development Engineering Volunteer Ongoing Deeds and Easements Ben Peterson was contracted to map on ATR maps the location of all deeds, easements, vacations, etc so that the inventory was up to date and showed accurate locations of features based upon their legal descriptions. His maps were used extensively during the quality control processes. Shapefile Attribution for features were individually verified by checking each feature's documentation (PDF land use files orginally catelogued in the City Clerk's office) during the reconcilation process. Any descrepancies found were researched and resolved. Linda Lian, Development Technician, Development Engineering February 2011 Deeds and Easements.dwg The source file used to update this dataset is an AutoCAD drawing. Linda Lian in Development Engineering maintains the AutoCAD drawing this dataset is derived from. Any questions pertaining to the AutoCAD drawing should be directed to her. She can be reached at 253-841-5577. Ben Peterson, Development Engineering Volunteer ATR maps and an AutoCAD drawing file Ben Peterson, ATR maps and documents Linda Lian, AutoCAD drawing file and document PDF's The source file used to update this dataset was the 2009 Deeds and Easements shapefile. A copy of the 2010 Deeds and Easements AutoCAD drawing was saved as a .dxf and imported into GIS. It was then used as a reference to identify new features. When features were found that should be added they were selected from the AutoCAD drawing and saved to a temporary folder for later merging. At the end of each day's work all new features were merged to the master file. The new master file was renamed in sequential order of days worked. In several instances features crossed quarter section lines. It is common practice within the City Clerk's office to duplicate and renumber a feature's document to each quarter section it was in. In the AutoCAD drawing the feature is not duplicated to accomodate this but rather relabeled within the neighboring quarter section to match the renumbered document. During the creation of this dataset features were not duplicated so that a duplicate document with a different number would have a feature to connect to. Instead which ever quarter section the majority of the feature resided in dictated the feature number and document number. This was done to reduce the amount of redundant duplication of documents. Copies were made of PDF maps and documents maintained by Development Engineering. Each document was manually renamed to match the numbers given each document when it was filed in the City Clerk's office. In turn each feature was renamed to match its corresponding document. This was done by combining two fields in the attribution. The PDF maps were used along with the older version of Deeds and Easement shapefile to find and identify new features found in the AutoCAD drawing. Three separate quality control checks were performed to assure the number of documents matched the number of documents referenced by features. During the quality control processes mislabeled features, mislabeled documents, duplicate features, and other anomalies were found. Corrections were made after each error found was researched using Ben Peterson's ATR maps as a reference. Eight geographic areas needed further research and reconciliation which was performed by Ben. The dataset was later corrected to reflect Ben's findings. All reconciliations are noted within a Work Notes Excel file maintained by the GIS Coordinator. The last steps performed after quality control was assigning Unique ID's to each feature and adding the document path field to the attribution. Unique ID's were assigned using a VB script adding '1' to the feature's FID number. The Document field is for county use when mapping the path of each document to its feature. Ninety-five notes were made concerning decisions made on the handling of features and documents. Twenty-three notes were made concerning decisions made that applied to the dataset as a whole. All of these notes are in an Excel spreadsheet called Work Notes kept by the GIS Coordinator to document work completed. The spreadsheet is available for viewing upon request. Symbology is based upon symbology used in the AutoCAD maps to avoid user confusion. March 1 -June 30, 2011 Jennifer Recco City of Puyallup GIS Coordinator mailing and physical address Puyallup WA 253-841-5571 253-841-5589 jennifer@ci.puyallup.wa.us 8AM - 5PM Metadata imported. withheld 12184700 Metadata imported. withheld 14162900 Metadata imported. withheld 20110412 15584000 Metadata imported. withheld 20110629 11152800 Assessor Treasurer (ATR) Maps Ben Peterson, Development Engineering Volunteer June 2011 Ben Peterson, Development Engineering Volunteer updated on ATR maps all of the features found within this dataset. His maps were referenced repeatedly during the process of creating this dataset and during the quality control process. Unknown Dataset copied. withheld 20110719 08444300 Dataset copied. withheld 20110719 16390900 This dataset is consistent with records kept on all features within this dataset. This data is complete as of February 2011. Any changes or updates will occur in early 2012. Positional accuracey is based upon legal descriptions, the source AutoCAD file, and Pierce County's Boundary shapefile. Vector Simple FALSE 0 TRUE FALSE coordinate pair 0.000000 0.000000 survey feet D_North_American_1983_HARN Geodetic Reference System 80 6378137.000000 298.257222 GCS_North_American_1983_HARN NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet 0.000000 Explicit elevation coordinate included with horizontal coordinates deeds_and_easements A shapefile containing deeds, easements, vacations, vacations with easements, covenants, and release of easements made with the city and are in city possession. Private transactions are not part of the this dataset. City of Puyallup Information Technology Feature Class 0 OBJECTID OBJECTID OID 4 0 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. Shape Feature geometry. ESRI Coordinates defining the features. Shape Geometry 0 0 0 TYPE What the feature is PDF Documentation Easement These are: drainage, water, utility, sewer, slope and site easements given to the city. Development Engineering Deeds Where land has been gifted to or purchased by the city. Development Engineering Covenants A contract between property owners and the city Development Engineering Vacation with Easements This is a street right-of-way with an easement Development Engineering Vacations Refers to right-of-way only Development Engineering Release of Easement Release of an existing easement Development Engineering Access Agreement Engineering An agreement made with the property owner whereby the City has unfetered access to said property for the sole purpose of maintaining City utilities. TYPE String 25 0 0 DOCUMENT DOCUMENT String 25 An 11 numbered PDF document file that is the legal document related to the feature. A hard copy of the document can be found in the City Clerk's Office. City of Puyallup Clerk's Office Example: 04202104_123.pdf The first 6 numbers are the Range, Township, and Section where the feature is located. The 7th number is a place holder per the Clerk's Office. The 8th number is the Quarter Section where the feature is located. For example: #1 is the NE quarter section, #2 is the NW quarter section, #3 is the SW quarter section and #4 is the SE quarter section. After the underline there are 3 additional numbers. They are sequential in order beginning with 001 of addition to the list of features added within a quarter section. City of Puyallup Clerk's Office 0 0 DOC_LABEL DOC_LABEL String 10 0 0 The last 4 numbers of the feature's Document number. This field is used for labeling purposes. Development Engineering 1_123 A sequential numbering system beginning with 001 used when feature is added to a quarter section. #1 is the NE quarter section where as #2 is the NW quarter section, #3 is the SW quarter section, and #4 is the SE quarter section. The last 3 numbers are the order of addition to the quarter sections' number of features. Pierce County, Development Engineering 2_xxx Features with their last 3 number places that are X's are known features waiting for a corrected number and document. Pierce County, Information Technology DOC_PATH DOC_PATH String 150 Path to the linked document Pierce County GIS 0 0 $MH/Puyallup Path on server where the linked document is stored. PC-GIS Shape_Length Shape_Length Double 8 0 0 Length of feature in internal units. Esri Positive real numbers that are automatically generated. Shape_Area Shape_Area Double 8 0 0 Area of feature in internal units squared. Esri Positive real numbers that are automatically generated. This dataset contains deeds, easements, release of easements, covenants, vacations and vacations with easements made with the city and are in city possession. Private transactions are not part of this dataset. Jennifer Recco City of Puyallup GIS Coordinator mailing and physical address

1100 39th Ave SE, Bldg C

Puyallup WA 98374 253-841-5571 253-841-5589 jennifer@ci.puyallup.wa.us 8AM - 5PM Downloadable Data 0.495 0.495 There is a cost for the CD. Please contact the distributor for details. Public Records Request form and GIS Digital Data Disclaimer must be completed and returned to the GIS Coordinator prior to the data being released. Once done, the data can be emailed, transferred to an FTP site or burned to a CD for purchase. Pierce County GIS may process a request for City of Puyallup data if it is part of a larger data set request made of Pierce County by outside sources. If this were to happen, authorization for release of City data would be granted after the requestor completed and returned a City of Puyallup Public Records Request form and GIS Digital Data Disclaimer to the GIS Coordinator who will then authorize the release of city data. Within two weeks from the date of the Public Record Request. See digital release process July 15, 2011 20110722 City of Puyallup Jennifer Recco GIS Coordinator mailing and physical address

1100 39th Ave SE

Bldg C

Puyallup WA 98444 253-841-5571 253-841-5589 jennifer@ci.puyallup.wa.us 8AM - 5PM FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time Please read Disclaimer to and Warranty by Users of City of Puyallup GIS Data concerning use of City of Puyallup data. All users must read the metadata. en 20110629 20200727 12393400 FALSE 20200325 19150200 20210701 9452900 deeds_and_easements 002 1183616.317451 1215201.455396 666162.173042 693471.906153 1 0.513 Projected GCS_North_American_1983_HARN Linear Unit: Foot_US (0.304801) NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet <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'><WKT>PROJCS["NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602_Feet",GEOGCS["GCS_North_American_1983_HARN",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",1640416.666666667],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-120.5],PARAMETER["Standard_Parallel_1",45.83333333333334],PARAMETER["Standard_Parallel_2",47.33333333333334],PARAMETER["Latitude_Of_Origin",45.33333333333334],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2927]]</WKT><XOrigin>-117498300</XOrigin><YOrigin>-98850300</YOrigin><XYScale>3048.0060960121918</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.0032808333333333331</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>2927</WKID><LatestWKID>2927</LatestWKID></ProjectedCoordinateSystem> FGDC CSDGM Metadata 1.0 FGDC 50000 5000 Jennifer Recco City of Puyallup GIS Coordinator 253-841-5571 333 South Meridian, 4th Floor Puyallup WA 98371 jennifer@ci.puyallup.wa.us US 8AM - 5PM There is a cost for the CD/DVD. Please contact the distributor for details. (USD) Public Records Request form and GIS Digital Data Disclaimer must be completed and returned to the distributor prior to the data being released if requested on media. Once both forms are received the data can be burned to a CD/DVD and mailed or readied for pick-up at the 2nd floor front counter of City Hall. Published City data is available on the City's website: http://www.cityofpuyallup.org/business/gis-data/ Please read the Disclaimer to and Warrant by Users of the data and the data's metadata prior to downloading the data. There is no cost to download the data. Within two weeks from the date of the Public Record Request if requested on media. 2016-02-03T00:00:00 2009-12-30T00:00:00 File Geodatabase Feature Class 0.513 Deeds and Easements - Puyallup Jennifer Recco jennifer@ci.puyallup.wa.us 333 South Meridian, 4th Floor Puyallup WA 98371 US 253-841-5571 Ret. GIS Coordinator See Cross Reference and Source Information for additional citation details. 2011-01-03T00:00:00 2020-03-15T00:00:00 2020-03-15T00:00:00 Deeds and Easements William Keller City of Puyallup GIS Coordinator 333 S Meridian Puyallup WA 98371 wkeller@puyallupwa.gov 253-841-5571 <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This feature class contains deeds, easements, release of easements, covenants, vacations and vacations with easements made with the city and are in city possession. Private transactions are not part of this dataset. A single Access Agreement was added in September 2017 at the request of a City engineer. A second access agreement 'type' of feature was added in September 2019.</SPAN></P><P><SPAN>William Keller, GIS Coordinator - GIS conversion, feature research, document reconciliation and dataset creation. Ben Peterson, Development Engineering volunteer updated the city's deeds and easement documentation and 'Go To Guy' for the research of features/documents not found or inconsistencies noted in, between, or otherwise part of the source data until his retirement early in 2017. Linda Lian, Development Technician, provided the original AutoCAD .dwg and subsequent updates until September 2017. The City Clerk's Office has provided documentation necessary for all updates beginning October 2017 to the present. </SPAN></P></DIV></DIV></DIV> The purpose of this feature class is to give the viewer the means to locate a feature, determine its type, and by using the link found in each feature's attribution review that feature's documentation. It may help the viewer to open Pierce County's RTSQ feature class to understand the nomenclature of the document naming system. William Keller, GIS Coordinator. Ben Peterson, Development Engineering volunteer. Linda Lian, Development Technician. The City Clerk's Office. 2020-01-02T00:00:00 Next update date is an approximation only. William Keller City of Puyallup GIS Coordinator 333 S Meridian Puyallup WA 98371 wkeller@puyallupwa.gov 253-841-5571 William Keller City of Puyallup Puyallup NA Vacation Release of Easement Covenant Deed Easement Vacation with Easement Vacation City of Puyallup Release of Easement Covenant Deed Puyallup Easement Vacation with Easement Utility Easement Critical Area (types of) Easements Access Agreements Disclaimer to and Warranty by Users of City of Puyallup GIS Data 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 'AS IS' AND 'WITH ALL FAULTS'. 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. 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. 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. 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. 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). 'Commercial Purposes' means contacting or in some way personally affecting the individuals identified on the list with the purpose of facilitating one's commercial activities. 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. 7. Project Data Requestors are encouraged to supply their project data back to the City of Puyallup for use by the City of Puyallup. All users must read the metadata before using the data. <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN STYLE="font-size:12pt">All users must read the metadata before using the data.</SPAN></P></DIV></DIV></DIV> This data is available to anyone who requests it through the city's Public Record Request process. Unclassified <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>All users must read the metadata before using the data.</SPAN></P></DIV></DIV></DIV> Deeds and Easements.dwg Deeds and Easements 2015-01-28T00:00:00 2015-01-28T00:00:00 February 2011 2015-01-28T00:00:00 'Deeds and Easements' were kept in AutoCAD by Development Engineering staff through 2016. Beginning in 2017 a new process was established with the City Clerk's office whereby copies of documents were sent to the data custodian who used diagrams included in recorded documents, legal descriptions within recroded documents, or files delivered by the firm handling the action to hand digitize the feature. Construction Notes: Temporary construction easements are not consistently shown. They are not captured as part of this database due to their temporary nature. LID's are not included in database. Concomitant Agreements are not included in database. They have their own geodatabase. When possible multiple features (that do not touch) related to a single document are dissolved into one multi-part feature to create one feature for one document. Where seen and possible if a feature appears to follow parcel boundaries and does not due to parcel shifting - feature was shifted. Not a priority to accomplish but is done where noticed and if time allows PAUE's are not included in the database. Pre-annexation zoning agreement features are not included in dataset. Hatch patterns found in original AutoCAD source are not identifiable therefore are not part of the database. Mitigation agreements are not included in database. Where it was found that one feature had 2 separate types documents pointing to it, the feature was copied so one feature to one document. Features without documents have no shpnam2 - it is an empty field. Ordinances when found are not part of this database (sometimes when they are the only documentation for a feature it is). Covenants to join LID were not originally part of this database but have been added over time. Only features within city possession are in this database. When it is found in the original folders that pdf's had an a or b extension to them, they were researched and renamed a and b accordingly. For example see pg 12 notes above; the PDF doc has an a and b extension Use of ROW easements are not part of this database. 4/3/14 some have been added Leases are not part of this database. Possession and Use agreements are not part of this database. Sewer Connection agreements are not part of this database. Utility extension agreements are not part of this database. This warrants investigation as they may have been added over time. Utility Easements are slowly being added as they are identified. License agreements are not part of this database. Beginning in 2015 Permeable Pavement Maintenance Covenants are included in this database. Critical Area buffers aka geological hazard areas generally are not part of this database (might be if tied to something else like an easement/deed). 04203604_007 is an example of this. The document exists but the feature never did. In Jan 2016 a decision was made to permanently exclude this type of land use restriction. An Access Agreement single feature over two parcels was added during the 2017 Update. This is a utility access agreement between the City of Puyallup and Washington State Fair. Version 6.2 (Build 9200) ; Esri ArcGIS 10.6.1.9273 1 -122.338446 -122.208988 47.222288 47.145484 William Keller City of Puyallup GIS Coordinator 333 S Meridian Puyallup WA 98371 WKeller@PuyallupWA.gov 253-841-5571 William Keller William Keller William Keller Metadata is reviewed and updated at the same time that the data is updated. 2020-11-02T00:00:00 William Keller City of Puyallup GIS Coordinator 333 S Meridian Puyallup WA 98371 wkeller@puyallupwa.gov 253-841-5571 William Keller William Keller Please read Disclaimer to and Warranty by Users of City of Puyallup GIS Data concerning use of City of Puyallup data. <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>All users must read the metadata.</SPAN></P></DIV></DIV></DIV> This dataset is consistent with records kept on all features within this dataset. NA This data is complete up to the Publication Date. NA Attribution for features were individually verified by checking each feature's documentation (PDF land use files orginally catelogued in the City Clerk's office) during the reconcilation process. Any descrepancies found were researched and resolved. NA Positional accuracey is based upon legal descriptions, the source AutoCAD file, and Pierce County's Boundary shapefile. NA Assessor Treasurer (ATR) Maps Ben Peterson, Development Engineering Volunteer Ben Peterson, Development Engineering Volunteer updated on ATR maps all of the features found within this dataset. His maps were referenced repeatedly during the process of creating this dataset and during the quality control process. Beginning late September 2017 a process was established with the City of Puyallup's Clerks Office whereby documents are catalogued for their Land Use files and any document with features relavant to this geodatabase are directed to the City's GIS Coordinator for inclusion into this database. Ben Peterson, ATR maps and documents until his retirement early 2017. Linda Lian, AutoCAD drawing file and document PDF's until September 2017. Beginning late September 2017 a process was established with the City of Puyallup's Clerks Office whereby documents are catalogued for Land Use files and any document with features relavant to this geodatabase are directed to the GIS Coordinator for inclusion into this database. Ben Peterson, ATR maps and documents until his retirement early 2017. Linda Lian, AutoCAD drawing file and document PDF's until September 2017. The source file used to update this dataset was the 2009 Deeds and Easements shapefile. A copy of the 2010 Deeds and Easements AutoCAD drawing was saved as a .dxf and imported into GIS. It was then used as a reference to identify new features. When features were found that should be added they were selected from the AutoCAD drawing and saved to a temporary folder for later merging. At the end of each day's work all new features were merged to the master file. The new master file was renamed in sequential order of days worked. In several instances features crossed quarter section lines. It is common practice within the City Clerk's office to duplicate and renumber a feature's document to each quarter section it was in. In the AutoCAD drawing the feature is not duplicated to accomodate this but rather relabeled within the neighboring quarter section to match the renumbered document. During the creation of this dataset features were not duplicated so that a duplicate document with a different number would have a feature to connect to. Instead which ever quarter section the majority of the feature resided in dictated the feature number and document number. This was done to reduce the amount of redundant duplication of documents. Copies were made of PDF maps and documents maintained by Development Engineering. Each document was manually renamed to match the numbers given each document when it was filed in the City Clerk's office. In turn each feature was renamed to match its corresponding document. This was done by combining two fields in the attribution. The PDF maps were used along with the older version of Deeds and Easement shapefile to find and identify new features found in the AutoCAD drawing. Three separate quality control checks were performed to assure the number of documents matched the number of documents referenced by features. During the quality control processes mislabeled features, mislabeled documents, duplicate features, and other anomalies were found. Corrections were made after each error found was researched using Ben Peterson's ATR maps as a reference. Eight geographic areas needed further research and reconciliation which was performed by Ben. The dataset was later corrected to reflect Ben's findings. All reconciliations are noted within a Work Notes Excel file maintained by the GIS Coordinator. The last steps performed after quality control was assigning Unique ID's to each feature and adding the document path field to the attribution. Unique ID's were assigned using a VB script adding '1' to the feature's FID number. The Document field is for county use when mapping the path of each document to its feature. Ninety-five notes were made concerning decisions made on the handling of features and documents. Twenty-three notes were made concerning decisions made that applied to the dataset as a whole. All of these notes are in an Excel spreadsheet called Work Notes kept by the GIS Coordinator to document work completed. The spreadsheet is available for viewing upon request. Symbology is based upon symbology used in the AutoCAD maps to avoid user confusion. This same process of finding new features using a current .dxf of the master .dwg and existing shapefile, matching them with their documents, and reconcilation of anomalies will not occur after September 2017. After September 2017 all documentation will come from the City of Puyallup's Clerks Office. Maps will either be georeferenced or drawings will be obtained from the engineering firms who drew them for the recorded document. PDF copies of the documents will be mined from the network drived used by the Clerk's Office as a PDF document repository. Jennifer Recco City of Puyallup GIS Coordinator 253-841-5571 Puyallup WA jennifer@ci.puyallup.wa.us 333 South Meridian, 4th Floor 98371 US 8AM - 5PM 2019-06-06T00:00:00 Beginning in September 2017 all features will be drawin in GIS using supporting documentation from recorded documents and/or files obtained from engineering firms and digitized. All documentation for this process will have been recorded at the Pierce County Auditor's Office and originals kept in the City Clerk's Office. dataset EPSG 8.9.3(9.0.0) 0 20210701 William Keller City of Puyallup GIS Coordinator 333 S Meridian Puyallup WA 98371 WKeller@PuyallupWA.gov 253-841-5571 William Keller