Spatial Data Catalog
Learn more by reading the GIS FAQ 🗺
Layer information
Layer Name | food_facilities |
Subject Category | Administration |
Title | Food Facilities - Multiple Classes - For King County |
Feature Count | 10270 |
Feature Type | Point |
Published Date | Quarterly |
Spatial reference | NAD 1983 HARN StatePlane Washington North FIPS 4601 Feet |
Open Data Availability | Yes |
Place Keywords | Washington State, Pacific NW, King County, WA |
Theme Keywords | Bakeries, Food Facilities, School Kitchens, Admin, Restaurants, Grocery Stores |
Supplemental Information | None |
Attribute information
OBJECTID
From ESRI |
Description
Internal feature number. DomainSequential unique whole numbers that are automatically generated. |
FEATURE_ID
From King County |
Description
Unique identifier for each record Domain1 to 133827 by 1 |
ESITE
From King County |
Description
Unique identifier from ADDRESS_POINT database Domain1-7 digit value as text or '0000000' if unknown |
CODE
From King County |
Description
Coded Value Domain lookup value Domain350 - Food facility |
NAME
From Public Health - King County and Seattle |
Description
Name of restaurant or other food facility DomainUppercase alpha |
ABB_NAME
From King County |
Description
Abbreviated name for feature DomainMixed text |
SEAT_CAP
From Public Health - King County and Seattle |
Description
Size (seating capacity) when appropriate DomainBakery - Bakery Bed and Breakfast - Bed and Breakfast Catering Operation - Caterer Non-Profit Institution - Charitable Organization Mobile Food Service - Commissary for Mobile FSE Grocery - Grocery Limited Food Services - Limited Food Services Meat/Sea Food - Meat and Seafood Mobile FS - Mobile FS School Kitchen - School Kitchen Seating 0-12 - Seating capacity up to 12 Seating 13-50 - Seating capacity from 13 to 50 Seating 51-150 - Seating Capacity from 51 to 150 Seating 151-250 - Seating Capacity from 151 to 250 Seating > 250 - Seating > 250 |
RISK
From Public Health - King County and Seattle |
Description
Risk category of facility when appropriate DomainNo risk info - No Risk Information I - Low Risk - Cold holding - Limited food preparation. Requires one routine inspection per year. II - Medium Risk - No Cook Step Food Preparation. One routine inspection per year and either 2nd inspection or education visit III - High Risk - Same day service or complex food preparation. Requires 2 routine inspections per year and one education visit Risk II&III - Combination Risk Category 1 and 3 |
ADDRESS
From Public Health - King County and Seattle |
Description
Full street address of facility DomainAddress number and uppercase street name; non-standard abbreviations |
PHONE
From Public Health - King County and Seattle |
Description
Area code and phone number of facility DomainNULL or form (###) ###-#### |
ZIPCODE
From Public Health - King County and Seattle |
Description
5 digit zipcode of facility Domain5 digits as string |
CITY
From Public Health - King County and Seattle |
Description
City where facility is located DomainMixed case full city name |
Shape
From ESRI |
Description
Feature geometry. DomainCoordinates defining the features. |
RECORD_ID
From Public Health - King County and Seattle |
Description
Record identifier if facility is a chain DomainAlpha numeric string |
FACILITY_NAME
From Public Health - King County and Seattle |
Description
Facility name if a chain or housing a chain DomainUppercase string; may be same as Chain Name or different |
CHAIN_NAME
From Public Health - King County and Seattle |
Description
Name of chain if facility is a chain DomainUppercase string; may be same as Facility Name or different |
CHAIN_ESTABLISHMENT
From Public Health - King County and Seattle |
Description
Whether facility is chain or not DomainEither NULL (not a chain) or Y (Yes) |
SITE_ADDRESS
From Public Health - King County and Seattle |
Description
Full street address of chain home location DomainAddress number and uppercase name; non-standard abbreviations |
Purpose
Provides one view of all the food facilities that are within the inspection area.
RESTAURANT_INSPECTIONS_POINT provides these same locations but is a one to many database as a single food location may have multiple records in that inspections database.
In the FOOD_FACILITIES_POINT layer each facility appears only one time for greater ease of use.
In addition, the inspection attributes that are part of the RESTAURANT_INSPECTIONS_POINT layer are not included in the FOOD_FACILITIES_POINT layer.
Abstract
Unique selection, by food facility name, from the King County Dept of Health Restaurant Inspection database (RESTAURANT_INSPECTIONS_POINT).
Includes information whether facility is part of food chain.
This featureclass is part of the COMMON_INTEREST_POINT layer as a unique domain within that database..
Contact information
Maintained by | Department of Public Health |
Primary |
Daniel Casey
dcasey@kingcounty.gov |
Constraints
Access |
None |
Use |
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. |
Change history
7/7/2014 |
Updated with current information from RESTAURANT_INSPECTIONS_POINT. Per standard script - AddNewCommonInterestFeatures.py |
8/17/2012 |
Data records where downloaded from http://info.kingcounty.gov/health/ehs/foodsafety/inspections/search.aspx Individual alpha record sets were appended and reformatted for delimiter conformance. Python scripts were used to assemble data tables, join information about restaurant chain, and create a spatial featureclass from tabular coordinate data. Data is loaded directly from the DPH database except in that the DESCRIPTION field which contains both Seating Capacity and Risk information is broken (parsed) into two separate fields: SEAT_CAP and RISK. Frequency analysis is used to create unique list of Program Identifier (facility name) with associated attributes that is passed to the Common Interest project area for uploading to tables to create new records in COMMON_INTEREST_POINT and a new FOOD_FACILITY featureclass. This process is performed three times a year - April, August and December - unless documented otherwise with a unique process step. |
Update 3 |
A frequency table is created from the RESTAURANT_INSPECTIONS_POINT database. This unique list is then joined with restaurant chain information and the composite table is then exported to a csv file in a schema compatible with COMMON_INTEREST_POINT. This list is loaded to COMMON_INTEREST_POINT and the associated COMMON_INTEREST_FF (business table attributes). Standard COMMON INTEREST routines are run to create the child featureclass, FOOD_FACILITIES_POINT. |