GIS Data Catalog

Decode Table for Values in item PARKOTHER in table CONDOUNIT_EXTR

View in ArcGIS Online 🔒

Learn how to get an ArcGIS Online account 🗺

Use this Data

Links How to use in ArcGIS Pro
Sharing Status	Not Public

Summary

This decode table can be used as a standard lookup table joining on the business table item it supports.

Depending whether the item supported is text or integer, the relate to the lookup table will be made on the item CODE_TEXT or CODE_NUMBER, respectively.

The value in the DESCRIPTION field provides the meaning of the code.

This table can also be converted to a geodatabase coded-value-domain (CVD), as done in the King County Spatial Data Warehouse, to present the decoded item descriptions dynamically without additional joins.

In the Spatial Data Warehouse the object exists as both a table and coded-value-domain called KCA159_PARKOTHER_CONDOUNIT.

Description

One of 80 decode (lookup) tables within the Property Schema.

This table also exists as a Coded Value Domain within the SDE Geodatabase.

This table decodes the values for the item - Parking: Other Type (parkother) in business table Condominium Unit (CONDOUNIT_EXTR).

There are 2 unique values in this decode table, enumerated in the detailed attribute section below.

Metadata for the business table can be accessed via the link in the Supplemental Information section.

Layer information

Layer Name	kca159_parkother_condounit
Subject Category	Property
Title	Decode Table for Values in item PARKOTHER in table CONDOUNIT_EXTR
Feature Count	2
Feature Type	Table
Next Update	None planned
Spatial reference	None
Control ID	1505
Place Keywords	Pacific NW, Washington State, King County, WA
Theme Keywords	Parcel, Property, Taxpayer
Supplemental Information	http://www5.kingcounty.gov/sdc/Metadata.aspx?Layer=condounit_extr

Attribute information

OBJECTID From Esri	Description System-generated primary key Domain Unique integer value
LUTYPE From King County Assessments	Description Integer value describing related records in LOOKUP_EXTR table Domain Integer value
CODE_NUMBER From King County Assessments	Description Value that relates to value in business table item Domain 1 - Hydraulic 2 - Other
CODE_TEXT From King County Assessments	Description CODE_NUMBER is relate value, so CODE TEXT is not used Domain Empty string
DESCRIPTION From King County Assessments	Description Decode meaning of CODE_NUMBER value Domain Hydraulic - 1 Other - 2

Contact information

Maintained by	KCGIS Center
Primary	KCGIS Center giscenter@kingcounty.gov

Terms of Use

License	Terms of use and copyright

Use this Data

Links How to use in ArcGIS Pro
Sharing Status	Not Public

Summary

This decode table can be used as a standard lookup table joining on the business table item it supports.

Depending whether the item supported is text or integer, the relate to the lookup table will be made on the item CODE_TEXT or CODE_NUMBER, respectively.

The value in the DESCRIPTION field provides the meaning of the code.

This table can also be converted to a geodatabase coded-value-domain (CVD), as done in the King County Spatial Data Warehouse, to present the decoded item descriptions dynamically without additional joins.

In the Spatial Data Warehouse the object exists as both a table and coded-value-domain called KCA159_PARKOTHER_CONDOUNIT.

Description

One of 80 decode (lookup) tables within the Property Schema.

This table also exists as a Coded Value Domain within the SDE Geodatabase.

This table decodes the values for the item - Parking: Other Type (parkother) in business table Condominium Unit (CONDOUNIT_EXTR).

There are 2 unique values in this decode table, enumerated in the detailed attribute section below.

Metadata for the business table can be accessed via the link in the Supplemental Information section.

Contact information

Maintained by	KCGIS Center
Primary	KCGIS Center giscenter@kingcounty.gov

Terms of use and copyright

License	Terms of use and copyright

Change history

10/1/2012	A cross reference table exists in the enterprise geodatabase (KCA_LUTYPE_XREF) to act as a control table for all KCA domains. This table maintains the relationship between source KCA tables and their corresponding posted KCGIS tables. The table was constructed by combining KCA documentation for all tables, including field names, format, and any lookup types used by fields in that table. The lookup type field relates to code and description record sets contained in the original KCA Lookup table (Lookup). This lookup type field is maintained going forward and continues to serves as key to code/description record sets within two newly created KCGIS lookup tables. These two lookup tables are created within the enterprise geodatabase to hold all code/description record sets contained in the original KCA Lookup table plus those taken from table description text documents. First, all KCA Lookup record sets with numeric codes are used to create the numeric lookup table (KCA_LOOKUP_NUMBER). This lookup table includes a LUCODE field of type Integer. Second, all character code-description record sets, taken from documentation, are used to create a text lookup table (KCA_LOOKUP_TEXT). This text lookup table includes a LUCODE field of type Text. Both lookup tables contain the original KCA lookup type field (LUTYPE). All KCA domain tables are generated via python script (CreateDomainTables.py). The cross reference table (KCA_LUTYPE_XREF) is used to identify all fields within KCA tables that utilize a domain. An individual domain table is created for each unique table-field combination in the cross reference table, if a valid KCA lookup type exists for the field. The lookup type (LUTYPE) value in the cross reference table is then used to query all of the code/description record sets from either the numeric lookup table (KCA_LOOKUP_NUMBER) or text lookup table (KCA_LOOKUP_TEXT) depending on the field format. The selected records are then written to that specific domain table. A template table is used to pre-define the attribute schema for all domain tables to ensure uniformity. All KCA domain tables follow the same naming convention: KCA(LUTYPE#)_(Field Name)_(TableName).