MapInfo Tables

 Join Table: The join table is a virtual table that links the attribue data in the assessor table to the spatial data in the parcel table. The join table contains no data itself, but accesses data in the assessor table and the parcel table by creating a SQL View. The complete listing of the join table follows:

Assessor Table: The assessor table contains the attribute (tabular) data. Most of the data comes from the Assessor's Tax Roll.

Field Name	Data Type	Description
PIDN	Char(23)	Parcel Identification Number (Primary Key)
Tax_ID	Char(9)	Secondary Tax ID number
Map	Char(6)	Subdivision Plat number
Lot	Char(6)	Subdivision Lot number
Name1	Char(35)	Owner Name
Name2	Char(35)	Secondary Owner Name
Address	Char(35)	Owner Mailing Address
City	Char(18)	"
State	Char(2)	"
Zip	Char(10)	"
Descript	Char(254)	Legal Description (short)
Area_tax	Decimal	Acreage from Tax Roll
Area_calc	Decimal	Acreage calculated from GIS parcel map geometry
Street_num	Char(10)	Physical Address - Street Number
Direction	Char(1)	Physical Address - N, S, E, W
Unit	Char(12)	Physical Address - Condo unit number
StreetName	Char(36)	Physical Address - Street Name
Acct_type	Char(15)	Account Type     Address Only     Agricultural     Commercial     Com Vacant Land     Ind Vacant Land     Non Taxable     Residential     Res Vacant Land
Lea	Char(6)	Land Economic Area
Accountno	Char(30)	Realware Account Number

 

Parcel Table: The parcel table contains the spatial (geographic) data for all subdivision lots and metes & bounds tracts.  

Field Name	Data Type	Description
PIDN	Char(23)	Parcel ID Number (foreign key into assessor table)

Easement Table: Road and levee easements.

Field Name	Data Type	Description
ID	Char(1)	R = Road, L = Levee, D = Ditch, P=Pathway
Source	Char(16)	Cogo, Digi, etc

PLS Table: Public Land Survey System Lines. 

Field Name	Data Type	Description
PLSS	Char(12)	Valid codes are listed below
Source	Char(4)	Cogo, Digi, GCDB, etc.

   

Public Land Survey System Line Codes

SECTION	Section or Township line
QUARTER_SEC	Quarter section lines
OTHER	Meander line, 1/16 section line of other aliquot division line
text	Annotations

    R_PLS Table: Public Land Survey System Regions (closed polygons).  

Field Name	Data Type	Description
Section	small integer	Section number
Township	char(3)	Township, alphanumeric ex: 41N
Range	char(4)	Range, alphanumeric ex: 117W

   

  L_TwnRng: Township and Range lines with annotations used only for overview purposes. 

Field Name	Data Type	Description
ID	small integer	no attribute data

 

Water Table: Lines for creeks and rivers, regions for Snake River and lakes.  Form 1:100,000 scale TIGER files.

Field Name	Data Type	Description
Name	char(38)	water feature name

Text Table: Annotations (road names, subdivision names, street names, etc.)

Zoning Table: Zoning district boundary polygons.  

Field Name	Data Type	Description
Zoning	Char(2)	Valid codes are listed below

 
 

Zoning District Codes

2F	NC Two Family
AC	Auto-Urban Commercial
BC	Business Conservation
BP	Business Park
MH	NC Mobile Home Park
PA	Park
PD	NC Planned Unit Development
RU	Rural
SF	NC Single Family
SP	Public / Semi-Public
SU	Suburban
TV	NC Teton Village Single Family

 

Zoverlay Table: Zoning overlay polygons.  

Field Name	Data Type	Description
Overlay	Char(3)	Valid codes are listed below

   

Zoning Overlay Codes

NRO	Natural Resource Overlay
SRO	Scenic Resource Overlay
LO	Lodging Overlay

Contours:

5 foot contours were produced from the June 1999 aerial photography. The contours are in the \DEM\5_foot_contours folder. We received 178 tiles in AutoCAD format from the photogrammetrist, which have been aggregated and converted into five MapInfo tables: Contours39N, Contours40N, Contours41N, Contours42N, and ContoursAtla. Kelly is in Contours42N. There are no contours for Buffalo Valley.

The contours have two attributes: "Elev", and "Type". Elev is the orthometric height in feet, on the North American Vertical Datum of 1929 (NAVD29), which is a fancy way of saying "elevation". The Type attribute is a three character field.

The first character of the type field is either an "X" or an "I". "X" contours are at 25 foot intervals, while "I" contours are the intermediate 5 foot contours. You can query for type "X" contours if you want to make a map showing just 25 foot contours. This would be useful when 5 foot contours are too dense.

The second character of the type field is either "O" or is blank. "O" stands for obstructed; where vegetation made it difficult for the photogrammetrist to see the ground. These contours are less reliable.

The third character of the type field is either "D" or blank. Type "D" contours are depression contours (holes).

NWI Table: National wetlands inventory digitized by the U.S. Fish & Wildlife Service.  

Field Name	Data Type	Description
Class	Char(32)	Wetland classification (incomplete)

---

The tables (or layers) that make up any given area are as follows:

Cosmetic - A standard MapInfo layer that is always available

Text - Annotations, text is not visible until you zoom in far enough to read it

Easement - Access and levee easements (no utility easements)

PLS - Public Land Survey Lines (Section, ¼ Section, meander lines, etc)

R_PLS - Public Land Survey Sections as closed polygons

L_TwnRng - Public Land Survey Township Lines & annotations

Join - This is actually two tables: the Parcel layer joined to the Assessor table

Water - Creeks, rivers, lakes; coarse detail

Water24k - Creeks, rivers, lakes; fine detail

Zoning - Zoning District Boundaries

Zoverlay - Zoning overlays (NRO and SRO)

Only the Join table is selectable when a Workspace is opened. The Zoning and Zoverlay tables are neither selectable, nor visible. Use the Layer Control to turn layers on or off, or to enable or disable selectability.