Parcel Data Status
Status |
|||
| Statewide Parcel Participator: | yes | ||
| Assessor Office URL: | http://www.okanogancounty.org/Assessor/index.htm | ||
| Has GIS: | GIS Dept URL: |
http://www.okanogancounty.org/planning/ | |
| Has IMS: | IMS URL: |
||
| Requires License: | License File: |
||
| Requires Request: | Request File: |
||
| Requires Fee: | Fee: |
||
| Acquire Method: | The parcel layer is updated dated every two weeks. You can just download and use the layer. Direct download link here: http://www.okanogancounty.org/planning/zip/parcels.zip |
||
| Last Updated: | 2025-06-24 23:05:24 | ||
Primary Assessment Contact |
|||
| Name: | Larry Gilman | ||
| Position: | Assessor | ||
| Organization: | Okanogan County Assessor's Office | ||
| Address: | P.O. Box 152 | ||
| City, St, Zip: | Okanogan, WA 98840 | ||
| Phone: | 509-422-7190 | ||
| Fax: | |||
| Email: | lgilman@co.okanogan.wa.us | ||
| Contact Last Updated: | 2024-06-11 12:00:10 | ||
Primary GIS Contact |
|||
| Name: | Gene Wyllson | ||
| Position: | GIS Coordinator | ||
| Organization: | Okanogan County Office of Planning & Development | ||
| Address: | 123 Fifth Ave. North #130 | ||
| City, St, Zip: | Okanogan, WA 98840 | ||
| Phone: | (509) 422-7123 | ||
| Fax: | |||
| Email: | ghwyllson@co.okanogan.wa.us | ||
| Contact Last Updated: | 2008-06-26 17:47:02 | ||
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 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 tp 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 (PRCELS: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):
Data Normalization, Integration and Quality Control Notes
| Integration Date: | 2009-09-17 |
| Integration Notes: | New For 2009 DATE_CREAT --> SourceCreationDate E911 --> SiteAddressFull E911_ADD --> SiteAddressNumber E911_ROAD --> SiteAddressStreetFullName LAST_DATE --> SourceRevisionDate PROPERTY_C --> PropertyType BOOK_PG --> SourceDocumentReference Converted to coverage with 1 ft xy tolerance, then back to shapefile so FME could handle the topology. The original shapefile 'landuse 051209.shp' had 56038 records. The edited shapefile 'landuse_051209_1ft_tolerance_edit.shp' has 56020 records, 18 fewer. The DATE_CREAT and LAST_DATE fields in the shapefile have NULL values, which are represented depending on the system as 1899-12-30 or 12:00:00 AM. FME reads these in as 00000000 but then stores them to the SDE database as 1899-12-30 00:00:00.000 which then gets represented in ArcMap/Catalog as 12:00:00 AM. There were 24 records in landuse_051209_1ft_tolerance_edit.shp and the original shapefile with these NULL dates. Field Calculator was used to set these dates to NULL in ArcMap. FME NullAttributeSetter and Tester transformers were then able to pass through these NULL dates. There are 3 parcels with PIN value '3023360094'. The two western-most parcels overlap. When they were aggregated in FME, a multi-part polygon was created that overlaps itself, which is illegal in an SDE database. To solve this problem, the eastern-most (smaller) of the two overlapping parcels had its western edge edited using the Editor toolbar in ArcMap to snap its vertices to the vertices of the larger overlapping parcel. This removed the overlap, and FME was able to process them. |
| QAQC Date: | 2009-11-24 |
| QAQC Notes: | PolyID=424000048127; ProParcelAggregated=4. There are 4 polygons in orignal data (landuse.shp) with same PIN=7220130000. Parcel aggregated correctly. PolyID=424000047083; ProcTaxrollFlattened=2. There are 2 polygons in original data with PIN=3025130007. These each produced a tax record that. They were flattened correctly. ProcessNameFlattened=3. There are 3 polygons in Parcel table with PolyIDs=424000002744, 424000008736, 424000032257. CURRENT_OW=ALVARADO ORCHARD with PINs=3827280013, 3827282001, 3827273009. Name flattened correctly. |
Tables
| Name | Notes |
| landuse.dbf |
Attribute Normalization
| Table Name | Attribute | Common Field | Normalized Field | Normalization Process |
| landuse.dbf | CURRENT_OW | Owner_Name | Name.Name | Direct; Owner |
| landuse.dbf | DATE_CREAT | Create_Date | SourceCreationDate | Direct |
| landuse.dbf | DEEDED_ACR | Acres_Tabular | TabularAcres | Direct |
| landuse.dbf | DOR_CODE | Land_Use_Code | StateLandUseCode | First two (left) characters; FME substring extract (0,1) |
| landuse.dbf | E911 | Parcel_Address | SiteAddressFull | Direct; Used if SITUS is NULL. |
| landuse.dbf | E911_ADD | Parcel_Address_House | SiteAddressNumber | Direct |
| landuse.dbf | E911_ROAD | Parcel_Address_Street | SiteAddressStreetFullName | Direct |
| landuse.dbf | HTTP | URL | AssessorURL | Direct |
| landuse.dbf | IMPP_MARKE | Market_Value_Improvements | MarketValueImprovements | Direct |
| landuse.dbf | IMPR_USE_V | Taxable_Value_Improvements | TaxableValueImprovements | Direct |
| landuse.dbf | LAND_MARKE | Market_Value_Land | MarketValueLand | Direct |
| landuse.dbf | LAND_USE_V | Taxable_Value_Land | TaxableValueLand | Direct |
| landuse.dbf | LAST_DATE | Edit_Update_Date | SourceRevisionDate | Direct |
| landuse.dbf | LEGAL | Legal_Description | LegalDescription | Direct |
| landuse.dbf | MAIL1 | Owner_Address_1 | AddressLine1 | Direct |
| landuse.dbf | MAIL_2 | Owner_Address_2 | AddressLine2 | Direct |
| landuse.dbf | MAIL_3 | Owner_Address_City_State | AddressCity | Where MAIL_3 is not NULL, split on comma. Take first = AddressCity; second =AddressState |
| landuse.dbf | MAIL_3 | Owner_Address_City_State | AddressState | Where MAIL_3 is not NULL, split on comma. Take first = AddressCity; second =AddressState |
| landuse.dbf | MAP__ | Township_Range_Section | Township | Where MAP__ is not NULL, split on hyphen, take first as Township; second as Range; last as Section |
| landuse.dbf | MAP__ | Township_Range_Section | Range | Where MAP__ is not NULL, split on hyphen, take first as Township; second as Range; last as Section |
| landuse.dbf | MAP__ | Township_Range_Section | Section | Where MAP__ is not NULL, split on hyphen, take first as Township; second as Range; last as Section |
| landuse.dbf | PCROP_MV | Market_Value_Crop | MarketValueCrop | Direct |
| landuse.dbf | PCROP_UV | Taxable_Value_Crop_Land | TaxableValueCrop | Direct |
| landuse.dbf | PIN | Parcel_ID | SourceParcelID | Direct |
| landuse.dbf | PROPERTY_C | Property_Type | PropertyType | Direct |
| landuse.dbf | SITUS | Parcel_Address_All | SiteAddressFull | Removed leading zeros on number and '\' |
| landuse.dbf | TCA | Tax_Code_Area | TaxCodeArea | Direct |
| landuse.dbf | TOTAL_MARK | Market_Value_Total | MarketValueTotal | Direct |
| landuse.dbf | TOTAL_USE_ | Taxable_Value | TaxableValueTotal | Direct |
| landuse.dbf | ZIP | Owner_Address_Zip | AddressZip | Direct |
