Decode Table for Values in item LAKEWASHINGTON in table PARCEL_EXTR

Metadata also available as - [Outline]

Frequently anticipated questions:


What does this data set describe?

Title:
Decode Table for Values in item LAKEWASHINGTON in table PARCEL_EXTR
Abstract:
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 - View: Lake Washington (LAKEWASHINGTON) in business table Parcel (PARCEL_EXTR). There are 4 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.
Supplemental_Information: <http://www5.kingcounty.gov/sdc/Metadata.aspx?Layer=parcel_extr>
  1. How should this data set be cited?

    County, King, 20120801, Decode Table for Values in item LAKEWASHINGTON in table PARCEL_EXTR: King County, King County, WA.

    Online Links:

    • None

  2. What geographic area does the data set cover?

  3. What does it look like?

    Not Applicable (Not Applicable)
    Not Applicable

  4. Does the data set describe conditions during a particular time period?

    Beginning_Date: 01-Jan-2006
    Ending_Date: 11-Dec-2012
    Currentness_Reference: publication date

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: tabular digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

    2. What coordinate system is used to represent geographic features?

  7. How does the data set describe geographic features?

    PLIBRARY.PROPERTY.xxxx224220
    Table (Source: King County Assessments)

    OBJECTID
    System-generated primary key (Source: Esri)

    Unique integer value

    LUTYPE
    Integer value describing related records in LOOKUP_EXTR table (Source: King County Assessments)

    Integer value

    CODE_NUMBER
    Value that relates to value in business table item (Source: King County Assessments)

    ValueDefinition
    1Fair
    2Average
    3Good
    4Excellent

    CODE_TEXT
    CODE_NUMBER is relate value, so CODE TEXT is not used (Source: King County Assessments)

    Empty string

    DESCRIPTION
    Decode meaning of CODE_NUMBER value (Source: King County Assessments)

    ValueDefinition
    FAIR1
    AVERAGE2
    GOOD3
    EXCELLENT4

    Entity_and_Attribute_Overview:
    No additional attributes are stored beyond LUTYPE (the relationship to the master LOOKUP_EXTR table), the CODE_NUMBER (or CODE_TEXT), and the DESCRIPTION.
    Entity_and_Attribute_Detail_Citation: King County Assessments


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    King County Assessments

  3. To whom should users address questions about the data?

    King County GIS Center
    Attn: Frank Whitman
    GIS Analyst
    201 S Jackson St, Suite 706
    Seattle, WA 98104
    US

    206-263-3780 (voice)


Why was the data set created?

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 KCA58_LAKEWASHINGTON_PARCEL.


How was the data set created?

  1. From what previous works were the data drawn?

  2. How were the data generated, processed, and modified?

    Date: 01-Oct-2012 (process 1 of 1)
    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).

  3. What similar or related data should the user be aware of?


How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

    Based on data dictionary provided by King County Assessments. Values in table have not been validated against a frequency of the values in the business table item supported by this coded-value-domain.

  2. How accurate are the geographic locations?

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

    For a given KCA business table, all items with associated decode values in the master LOOKUP_EXTR are decoded. However, since not all KCA business tables are maintained in the enterprise spatial data warehouse, not all possible decode relationships are present.

  5. How consistent are the relationships among the observations, including topology?

    Each CODE_NUMBER or CODE_TEXT value has one and only one DESCRIPTION value. If relate item in table is numeric, then CODE_NUMBER is populated and CODE_TEXT is blank. Likewise, if relate item in table is string, then CODE_TEXT is populated and CODE_NUMBER will be blank. This allows the schema of all table to be identical.


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: None
Use_Constraints:
King County data are made available with the understanding that they shall be used exclusively by the obtainer or his/her authorized agents. Digital products may not be reproduced or redistributed in any form or by any means without the express written authorization of King County. Users are encouraged to appropriately evaluate and display the Margin of Error when analyzing and mapping this data.

  1. Who distributes the data set? (Distributor 1 of 1)

    KCGIS Center
    Attn: Cheryl Wilder
    Data Sales Coordinator
    201 S Jackson St, Suite 700
    Seattle, WA 98104
    US

    206-263-5220 (voice)

  2. What's the catalog number I need to order this data set?

    /plibrary2/property/shapes/table/kca58_lakewashington_parcel.dbf

  3. What legal disclaimers am I supposed to read?

    King County disclaims any warranty of use of any digital product or data beyond that for which it was designed.

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 27-Dec-2012
Metadata author:
King County GIS Center
Attn: Mike Leathers
GIS Data Coordinator
201 S Jackson St, Suite 706
Seattle, WA 98104
US

206-263-4867 (voice)
firstname.lastname@kingcounty.gov

Metadata standard:
FGDC Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)


Generated by mp version 2.9.12 on Sat Apr 06 04:14:04 2019