Parcel Data Status
Status |
|||
| Statewide Parcel Participator: | yes | ||
| Assessor Office URL: | http://www.co.grays-harbor.wa.us/info/assessor/Index.asp | ||
| Has GIS: | GIS Dept URL: |
http://www.ghc-gis.org/info/GIS/download.html | |
| Has IMS: | IMS URL: |
||
| Requires License: | License File: |
http://www.co.grays-harbor.wa.us/info/pub_svcs/GHCCode/pdf/PublicRecordsRequestForm.pdf | |
| Requires Request: | Request File: |
Public Records Request.pdf | |
| Requires Fee: | Fee: |
||
| Acquire Method: | 2015: Downloaded Parcels (has parcel.shp and Asr-Landuse.dbf) from http://www.ghc-gis.org/info/GIS/download.html. Need ghresmas.txt. 2012: In response to our initial e-mail request, Grays Harbor's GIS Coordinator e-mailed us the link (http://www.co.grays-harbor.wa.us/info/GIS/download.html) to download the data. He informed us that the data sets are current and available to download for updates. We must contact the GIS department to obtain a license agreement to distribute the data. |
||
| Last Updated: | 2019-10-02 10:07:41 | ||
Primary Assessment Contact |
|||
| Name: | Rick Hole | ||
| Position: | Assessor | ||
| Organization: | Grays Harbor County Assessor's Office | ||
| Address: | 100 W Broadway, Suite 21 | ||
| City, St, Zip: | Montesano, WA 98563 | ||
| Phone: | (360) 249-4121x353 | ||
| Fax: | (360) 249-6633 | ||
| Email: | rhole@co.grays-harbor.wa.us | ||
| Contact Last Updated: | 2012-08-09 10:55:30 | ||
Primary GIS Contact |
|||
| Name: | Sue Carlson | ||
| Position: | Administrative Assistant | ||
| Organization: | Grays Harbor County Assessor's Office | ||
| Address: | |||
| City, St, Zip: | , WA | ||
| Phone: | (360) 249-4121 x354 | ||
| Fax: | |||
| Email: | scarlson@co.grays-harbor.wa.us | ||
| Contact Last Updated: | 2009-05-21 11:56:35 | ||
Database Schema
The normalized Statewide Parcel Database consists of multiple related tables, relationship classes and lookup tables. Detailed information about the database schema can be found on the technical documentation page.
QA/QC
QA/QC Process Description
- While processing and normalizing the data for each county to a standardized statewide dataset, five possible procedures could have been applied: Removing Duplicate Parcels, Flattening Stacked Parcels, Creating Multipart Parcels, Removing Duplicate Names, and Removing Duplicate Taxrolls.
- The data for each county was tested to see whether or not these five procedures were applied. For each of these procedures applied in a county, one test parcel to which a process was applied was selected and tested to ensure the procedure was applied correctly.
- A parcel to which none of the procedures was applied was also tested to make sure all of the normalized attributes in the original data were correctly transferred to the final dataset.
- It is therefore possible that up to six data quality tests were performed for each county.
QA/QC Procedure Descriptions
The following five Procedures were performed in this order on the data for each county.- Removing Duplicate Parcels (PARCELS:DUPLICATE): There are two or more polygons representing a single parcel in the original data. They have the same geometry and identical attribute information. These are assumed to be multiple copies of the same parcel, and so duplicates are removed leaving a single polygon, and single set of attribute information in the final database. This flag tells how many duplicates of the parcel were in the original data.
- Flattening Stacked Parcels (PARCELS:FLATTENED): There are two or more polygons representing a parcel in the original data, however, while sharing the same geometry, they have different attributes. These are assumed to be multiple owners for the same parcel. The polygon only needs to be in the final database a single time, but all original attribute information for the different owners needs to be retained. This flag tells how many stacked polygons there were in the original data for each parcel.
- Creating Multipart Parcels (PARCELS:AGGREGATED): There are two or more polygons in the original data with different geometries but, identical attribute information. It is assumed that these parcels are all owned by the same owner. The original polygons are all retained as a single, multipart polygon, but duplicate versions of the attributes are removed. Only a single copy of the attribute information is needed in the final database. This flag tells how many parcels were aggregated into each multipart polygon.
- Removing Duplicate Taxrolls (TAXROLL:FLATTENED): Two or more parcels in a county have identical taxroll attributes. These attributes only need to be in the final database a single time. This flag records how many of the original parcels shared each set of taxroll attributes.
- Removing Duplicate Names (NAMES:FLATTENED): Two or more parcels in a county have the same name attributes in the original data. These attributes only need to be in the final database a single time. This flag records how many of the original parcels shared each set of name attributes.
Parcel Data Documentation (select a normalization date):
2009 Washington State Parcel Database
Data Normalization, Integration and Quality Control Notes
| Integration Date: | 2009-10-09 |
| Integration Notes: | New for 2009: attributes added EXEMPTCODE --> TaxStatus LANDUSE from Asr-Landuse.dbf --> SourceLandUseDescription attributes changed LANDUSE2 --> PropertyType instead of SourceLandUseDescription parcel.shp was run through the ArcGIS Repair Geometry Tool to parcel_repair.shp. 37 parcels were repaired due to self intersections. FME was unable to process this repaired shapefile. Instead, parcel.shp was converted to a coverage using the ArcGIS Feature Class to Coverage tool with an XY tolerance set to 1 foot. The region of the coverage was then copied back to a shapefile using the Feature Class to Feature Class tool. parcel.shp contained 60338 records. The new shapefile, parcel_1ft_tolerance_edit.shp contains 60302. 36 records were removed in the process. These appear to be the parcels with self-intersection problems detected by the Repair Geometry tool. Parcels in the parcel.shp source data that were aggregated into multi-part features in FME (grouped by SourceParcelID), had identical taxroll attributes, even though the individual source parcels were separate. In particular, total acreage appeared to be for the entire aggregated parcel even though the individual parcel acreages were less. Attibutes appear to be for the aggregated parcel even though the parcels are separate in the shapefile. As a results parcels that were aggegated into multi-part parcels have ProcessTaxRollFlattened values greater than 1. |
| QAQC Date: | 2009-11-17 |
| QAQC Notes: | PolyID=414000058815; ProcParcelAggregated=2. There are 2 parcels with the PARCELATT=150705220020 in the original shapefile (parcel_1ft_tolerance_edit.shp). Parcels aggregated correctly. PolyID=414000059064; ProcTaxrollFlattened=2. There are 2 polygons in original shapefile with PARCELATT=201008330010; both polygons have same owner (STATE OF WASHINGTON). Taxroll Flattened correctly. PolyID=414000041095; ProcNameFlattened=4. Original data PARCELATT=170705110030,170705110010, 731500001300, 731500001400; 4 records with same owner name/address. Names flattened correctly. |
Tables
| Name | Notes |
| parcel_1ft_tolerance_edit.shp | same as the original source data, parcel.shp (with 36 records removed) after having been converted to a coverage and back to a shapefile to repair topology. See normalization notes for more details. |
| Asr-Landuse.dbf |
Table Relationships
| Primary Table | Primary Key | Foreign Table | Foreign Key | Cardinality | Notes |
| Asr-Landuse.dbf | LANDUSE | parcel_1ft_tolerance_edit.shp | LANDUSE | 1:1 |
Attribute Normalization
Lookups
| Original Field | Original Value | Normalized Value | Normalized Field |
| LANDUSE | 10 | StateLandUseCode | |
| LANDUSE | 11 | 11 | StateLandUseCode |
| LANDUSE | 12 | 12 | StateLandUseCode |
| LANDUSE | 13 | 13 | StateLandUseCode |
| LANDUSE | 14 | 14 | StateLandUseCode |
| LANDUSE | 15 | 15 | StateLandUseCode |
| LANDUSE | 16 | 16 | StateLandUseCode |
| LANDUSE | 17 | 17 | StateLandUseCode |
| LANDUSE | 18 | 18 | StateLandUseCode |
| LANDUSE | 19 | 19 | StateLandUseCode |
| LANDUSE | 21 | 21 | StateLandUseCode |
| LANDUSE | 22 | 22 | StateLandUseCode |
| LANDUSE | 23 | 23 | StateLandUseCode |
| LANDUSE | 24 | 24 | StateLandUseCode |
| LANDUSE | 25 | 25 | StateLandUseCode |
| LANDUSE | 26 | 26 | StateLandUseCode |
| LANDUSE | 27 | 27 | StateLandUseCode |
| LANDUSE | 28 | 28 | StateLandUseCode |
| LANDUSE | 29 | 29 | StateLandUseCode |
| LANDUSE | 31 | 30 | StateLandUseCode |
| LANDUSE | 32 | 32 | StateLandUseCode |
| LANDUSE | 33 | 33 | StateLandUseCode |
| LANDUSE | 34 | 34 | StateLandUseCode |
| LANDUSE | 35 | 35 | StateLandUseCode |
| LANDUSE | 36 | 39 | StateLandUseCode |
| LANDUSE | 37 | 39 | StateLandUseCode |
| LANDUSE | 38 | 38 | StateLandUseCode |
| LANDUSE | 39 | 39 | StateLandUseCode |
| LANDUSE | 40 | 39 | StateLandUseCode |
| LANDUSE | 41 | 41 | StateLandUseCode |
| LANDUSE | 42 | 42 | StateLandUseCode |
| LANDUSE | 43 | 43 | StateLandUseCode |
| LANDUSE | 44 | 44 | StateLandUseCode |
| LANDUSE | 45 | 45 | StateLandUseCode |
| LANDUSE | 46 | 46 | StateLandUseCode |
| LANDUSE | 47 | 47 | StateLandUseCode |
| LANDUSE | 48 | 48 | StateLandUseCode |
| LANDUSE | 49 | 49 | StateLandUseCode |
| LANDUSE | 50 | 50 | StateLandUseCode |
| LANDUSE | 51 | 51 | StateLandUseCode |
| LANDUSE | 52 | 52 | StateLandUseCode |
| LANDUSE | 53 | 53 | StateLandUseCode |
| LANDUSE | 54 | 54 | StateLandUseCode |
| LANDUSE | 55 | 55 | StateLandUseCode |
| LANDUSE | 56 | 56 | StateLandUseCode |
| LANDUSE | 57 | 57 | StateLandUseCode |
| LANDUSE | 58 | 58 | StateLandUseCode |
| LANDUSE | 59 | 59 | StateLandUseCode |
| LANDUSE | 60 | 11 | StateLandUseCode |
| LANDUSE | 61 | 61 | StateLandUseCode |
| LANDUSE | 62 | 62 | StateLandUseCode |
| LANDUSE | 63 | 63 | StateLandUseCode |
| LANDUSE | 64 | 64 | StateLandUseCode |
| LANDUSE | 65 | 65 | StateLandUseCode |
| LANDUSE | 66 | 66 | StateLandUseCode |
| LANDUSE | 67 | 67 | StateLandUseCode |
| LANDUSE | 68 | 68 | StateLandUseCode |
| LANDUSE | 69 | 69 | StateLandUseCode |
| LANDUSE | 71 | 71 | StateLandUseCode |
| LANDUSE | 72 | 72 | StateLandUseCode |
| LANDUSE | 73 | 73 | StateLandUseCode |
| LANDUSE | 74 | 74 | StateLandUseCode |
| LANDUSE | 75 | 75 | StateLandUseCode |
| LANDUSE | 76 | 76 | StateLandUseCode |
| LANDUSE | 77 | 77 | StateLandUseCode |
| LANDUSE | 78 | 78 | StateLandUseCode |
| LANDUSE | 79 | 79 | StateLandUseCode |
| LANDUSE | 8 | StateLandUseCode | |
| LANDUSE | 81 | 81 | StateLandUseCode |
| LANDUSE | 82 | 82 | StateLandUseCode |
| LANDUSE | 83 | 83 | StateLandUseCode |
| LANDUSE | 84 | 84 | StateLandUseCode |
| LANDUSE | 85 | 85 | StateLandUseCode |
| LANDUSE | 88 | 88 | StateLandUseCode |
| LANDUSE | 89 | 89 | StateLandUseCode |
| LANDUSE | 91 | 91 | StateLandUseCode |
| LANDUSE | 92 | 92 | StateLandUseCode |
| LANDUSE | 93 | 93 | StateLandUseCode |
| LANDUSE | 94 | 94 | StateLandUseCode |
| LANDUSE | 95 | 95 | StateLandUseCode |
| LANDUSE | 96 | 81 | StateLandUseCode |
| LANDUSE | 97 | 81 | StateLandUseCode |
| LANDUSE | 98 | 98 | StateLandUseCode |
| LANDUSE | 99 | StateLandUseCode |
