Parcels

The parcels table contains attributes of individual parcels. Note that there may be alternative definitions of parcels, such as those based on legal boundaries or based on ownership. Most commonly used parcels are based on ownership since most relevant data (like land and improvement value) is associated with ownership records, though some applications (e.g. Honolulu) prefer using legal, or regulatory definitions. Either may be used.

Note that additional geographies may be added by the user to the parcel table, using the same approach as below. If one wanted to add a geography called Neighborhoods, for example, one would put the neighborhood_id on this table, which is an integer reflecting the primary key of a table called Neighborhoods, which would contain one record per neighborhood, with a neighborhood_id (Integer) and a neighborhood_name (String(50)).

Column Name	Data Type	Required	Description
parcel_id	Integer	Y	Unique id for parcels
parcel_id_local	String(20)	N	Users may want to store a local parcel id from the assessor's office
land_use_type_id	Integer	Y	Unique id of the land use type of the parcel
land_value	Integer	Y	Assessed value of the land on the parcel
parcel_sqft	Integer	Y	Land area of the parcel in square feet
plan_type_id	Integer	Y	Unique id of the land use plan type of the parcel (regulatory designation)
centroid_x	Integer	Y	X-coordinate of the parcel centroid, usually in a projection measured in feet
centroid_y	Integer	Y	Y-coordinate of the parcel centroid, usually in a projection measured in feet
tax_exempt_flag	Integer	N	Optional 1 if tax exempt, 0 otherwise
city_id	Integer	N	Unique id of the city in which the parcel is located
county_id	Integer	N	Unique id of the county in which the parcel is located
zone_id	Integer	Y	Unique id of the zone (as used in the travel model) in which the parcel is located
census_block_id	string	N	Optional unique id of the census block in which the parcel is located

-- PaulWaddell - 09 Dec 2009