BKFS Assessment Data Dictionary

The purpose of this data dictionary is to chronicle the standards according to which the data we present to our clients is formatted.

The reason an attempt at standardized formatting is made is so that our clients can more easily conduct the searches they need to do, and also so that we can provide more accurate and more flexible selections from the main database for our Bulk Sales customers.

When any uncertainty as to proper data format is encountered, the above purposes should govern any decisions made.

Field No.	Field Name	Length	From	To	Data Type
1	State (Postal Code)	2	0001	0002	A

Description: Two-letter standard postal abbreviation. See p. 53-54 of the USPS Postal Addressing Standards book, Publication #28 dated 8/95.

State Abbreviations
Alabama AL Alaska AK Arizona AZ Arkansas AR California CA Colorado CO Delaware DE Dist/Columbia DC Florida FL Georgia GA Hawaii HI Idaho ID Illinois IL Indiana IN Iowa IA Kansas KS Kentucky KY	Maine ME Maryland MD Massachusetts MA Michigan MI Connecticut CT Minnesota MN Mississippi MS Missouri MO Montana MT Nebraska NE Nevada NV New Hampshire NH New Jersey NJ New Mexico NM New York NY North Carolina NC North Dakota ND	Louisiana LA Ohio OH Oklahoma OK Oregon OR Pennsylvania PA Rhode Island RI South Carolina SC South Dakota SD Tennessee TN Texas TX Utah UT Vermont VT Virginia VA Washington WA West Virginia WV Wisconsin WI Wyoming WY

Other Valid Postal Codes
Guam	GU	Military overseas	AP
Virgin Islands	VI	Foreign countries	XX
Puerto Rico	PR

FIPS Codes exist for nations other than the United States. See this index.

Sample Instruction:

Move "PA" to State (1).

Field No.	Field Name	Length	From	To	Data Type
2	County Name	25	0003	0027	A

Description: This field contains the jurisdiction name which is usually the name of the county. In some cases the jurisdiction or area covered is something other than a county. In Virginia, for example, there are many independent cities. These cities are not part of any county but may have the same name as a county (i.e., City of Fairfax and Fairfax County.) In these cases an identifier is added to the non-county name in order to differentiate it from a county with the same name. The City of Fairfax is entered as Fairfax City while Fairfax County is entered as Fairfax. The identifier is always added after the name. No abbreviations are used for either the name or the identifier. The word County is never used as an identifier.

The Lexis-Nexis reference on the identities of taxing jurisdictions and the spelling of their names is the county database index.

Examples:

Jurisdiction	LAN-2
City of Virginia Beach, VA	Virginia Beach City
Virginia Beach [County]	Virginia Beach
St John, VI	St John Island

Jurisdictions requiring an identifier:
Maryland	Baltimore City
Missouri	St Louis City
Virginia	Alexandria City Chesapeake City Fairfax City Falls Church City Fredericksburg City Hampton City Manassas City Manassas Park City Newport News City Norfolk City Portsmouth City Richmond City Roanoke City Suffolk City Virginia Beach City
Virgin Islands	St Croix Island St John Island St Thomas Island
Wisconsin	Racine City

Sample Instructions:

Move "Columbia" to County Name [2]

Move "Alexandria City" to County Name [2].

Field No.	Field Name	Length	From	To	Data Type
3	APN-A	45	0028	0072	A

Description: Assessor's Parcel Number or Parcel Identification Number. This is an arbitrary parcel identifier assigned by the county Assessor to simplify identification and expedite the locating of parcels. It is usually composed of map-book/page/parcel and sub-parcel numbers. However, it varies in its format from county to county. Some states use the section/township/range as part of the APN, or a Map Number and Parcel reference, others use a Section, Block and Lot identifier, and still others have switched over to a geographically-oriented plane coordinate system.

This field must be filled - LAN-2 records lacking data in this field will not go on line.

Examples:

Midland, TX
Prince William, VA
Clark, NV

Re-format this field to duplicate as closely as possible the county format, so that inquiries to the county made by users of our system will make sense to the county personnel. For the exact format used by a county, a screen-print or printout from the county's own system is the best reference.

Examples:

County	Source	LAN-2
Sussex, DE	"1300118001501"	"130-0118-001501"
Black Hawk, IA	"871101101001"	"8711-01-101-001"
Nassau, NY	"1" "001" "34" " E" "0001" "0" "" ""	) ) ) ) 8 fields ) ) ) )	"1-001-34- E- -0001-0"

Use leading zeros or spaces to maintain the integrity of the format.

Example: (Alamance, NC)

" 3 1 5"	becomes	"003-001 -005"
" 3 18B168 "	becomes	"003-018B-168"
"205 35A 21UU"	becomes	"205-035A-021UU"

Sample Instructions:

Retain any leading space and move Parcel Number (7) to APN-A (3), formatting as noted below. For those records in which (3) is not unique, append two spaces and the contents of Community Identifier (4) to (3).

The format for the parcel number is "nnnn-nnn-nnn", in which the first (4-byte) sub-field denotes geographic location, the second (3-byte) sub-field denotes a parcel number within that geographic location, and the last (3-byte) sub-field is an optional extension which occurs as a result of a lot split or subdivision.

String the contents of the following fields, retaining leading zeros and separating the contents of each adjacent pair with a dash, and move the result to APN-A (3) AND ALSO to Legal Assessor’s Map Reference (70):

Map 1 (1)
Map 2 (2)
Block (3)
Parcel (4)

NOTE: The format of the LAN-2 data is "nn-nn-nn-nnn". in which the first two groups of numbers denote the map. This county's maps come in two different scales: 1:400 and 1:100. If the second group of numbers (byte positions 4-5) = "00", then the map is in 1:400 scale. If these bytes have a value greater than zero, then the map is in 1:100 scale and the numbers tell what page of the map the property is on. The entire identifying number is also used as an Assessor's map number.

Field No.	Field Name	Length	From	To	Data Type
4	Duplicate APN/ Multiple Address ID	2	0073	0074	A

Description: This field contains sequence numbers assigned to parcels having the same APN and different property addresses, owner names or sometimes even land use. The purpose is to uniquely identify each parcel despite their having the same APN.

The data in this field is created by a programming routine run as part of the conversion process. The analyst indicates when this routine is needed.

In the final LAN-2 file, records for which this field  0 will be most often be marked "MA" (Multiple Address) or "MO" (Multiple Owner) in Record Type [93]. The only record type not used in conjunction with this field is "DR" (Duplicate Record).

Example:

Source Data	Contents of LAN-2 Field
APN	Address	APN-A [3]	Duplicate APN [4]	Record Type [93]
501-03-100	101 Main St.	501-03-100	01	MA
501-03-100	101 A Main St	501-03-100	02	MA
501-03-100	101 B Main St	501-03-100	03	MA
501-03-100	101 C Main St	501-03-100	04	MA
501-03-100	101 D Main St	501-03-100	05	MA

Sample Instruction:

Match on PropertyID (2) to the Prop File. Records with multiple matches to the Prop File indicate multiple Owners for the same parcel. For duplicate records move “MO” to Record Type [93] and Increment Duplicate APN [4] to preserve uniqueness.

Field No.	Field Name	Length	From	To	Data Type
5	Property Address Source Flag	1	0075	0075	A

Description: This field contains a letter code which tells how the contents of various property address fields were derived. Valid codes are:

blank	Default
M	Full situs address was created from the mailing address.
P	Partial situs address (city, state & ZIP only) was created from the mailing address.
S	Mailing address was created from the situs address (SFR ONLY)
H	Situs house number created from mailing address if the property street name = mail street name and the property shows an improvement value.
D	Full situs address pulled from the matching Deed/SAM(LAN-1) record.
5	Situs address was provided on the 2005 Assessment Source File.(ONLY applies to Orange County CA)
O	Situs address was manually corrected(ONLY applies after approval from lead or senior analyst)
B	FULL situs address created from mailing address, based on the following criteria (no on- line display): Full Street Address [13] = [blank] Standardized Land Use Code [73] = "10xx" Improvement value (assessed or market) > zero Mail Full Street Address [30] begins with a number Valid mail city name per analyst-supplied list Mail state = the state of the property Mail Care-of Name [22] = [blank] No vesting indicators of artificial persons

When pulling situs info from the previous edition the following codes apply:

A	If Prop Address Source Flag [5] was blank in the previous edition, meaning situs came from source, or S, meaning Mailing was created from situs, then move A.
F	If [5] was M in the previous edition, meaning that the Full situs address was created from the mailing address and Field [36] Owner Occupied = “Y” then move F.
F	If [5] was H in the previous edition, meaning that the Situs house number was created from mailing address if the property street name = mail street name; then move F.
C	If [5] was P in the previous edition, meaning that the Partial situs address (city, state & ZIP only) was created from the mailing address AND there is NO property Street Address, City and ZIP available in the current source file, then move C.
5	If [5] was 5 in the previous edition, meaning the situs address was provided on the 2005 Assessment Source File, then move “5”.(ONLY applies to Orange County CA)
L	If [5] was D in the previous edition, meaning the situs address was populated from a LAN1 or SAM record, then move “L”.
X	If [5] was O in the previous edition, meaning the situs address was manually corrected, then move “X”.

If Prop Address Source Flag [5] is B, meaning that the Full situs was created from mailing based on special criteria, then do not pull situs data forward.

Sample Instructions:

Compare the street address portion of (55) with the contents of Owner Address (6). On match of first two words, move "P" to Property Address Source Flag [5].

Populate PROPERTY CITY, STATE and ZIP code fields from corresponding mail address according to current general instructions.

Last updated 20-Apr-10

Field No.	Field Name	Length	From	To	Data Type
6	House Number	7	0076	0082	A

Description: This field contains the number location of the property as commonly used in an address.

Example: 3550 W. Temple St., Los Angeles, CA 90004

Vacant land, especially in rural areas, will usually not have house numbers: in these cases this field will contain blanks.

Example: RR2, Lost Hills Road, Idria, CA

In some areas, house numbers may include a direction designation.

Example: 123N456 Main St.

Sample Instruction:

Move the contents of Property House Number (421) to House Number [6]

Field No.	Field Name	Length	From	To	Data Type
7	House Alpha	6	0083	0088	A

Description: This field contains the upper limit of the house number range, fractions, or the alphabetic extension of the house number. Any leading hyphen in the input field is dropped.

Example:

Source	LAN-2 (7)
123 - 189 Main Street	189
143-45 Main Street	145
184 & 186 Main Street	186
101-A Main Street	A

Sample Instructions:

If (16) contains "H", move "½" to House Alpha [7].

Move Property Location 4 (18) to House Alpha [7].

Field No.	Field Name	Length	From	To	Data Type
8	Street Direction - Left	2	0089	0090	A

Description: This field contains directional indicators in the property address which occur prior to the name of the street itself.

The valid directional indicators are: N, S, E, W, NE, NW, SE, and SW

Example: 3550 W. Temple Street, Los Angeles, CA 90004

Sample Instructions:

If Property Location 2 (16) contains an alpha directional indicator ("W", "S", etc.), move this indicator to Street Direction Left [8].

Field No.	Field Name	Length	From	To	Data Type
9	Street Name	30	0091	0120	A

Description: This field contains the name of the street. Do not abbreviate this data.

Example: 3550 W. Temple Street, Los Angeles, CA 90004

Sample Instructions:

Move the remainder of (15) to Street Name [9]. In cases of numbered farm or county roads, do not move leading zeros attached to the road number.

Move the contents of Property Street Nm (418) to Street Name [9]

Field No.	Field Name	Length	From	To	Data Type
10	Street Suffix	4	0121	0124	A

Description: This field contains the recommended USPS standardized suffix abbreviations as contained in Publication #28, dated 8/95 and extracted in part below.

ALY	=	Alley	FT	=	Fort	PKY	=	Parkway
ANX	=	Annex	FWY	=	Freeway	PIKE	=	Pike
ARC	=	Arcade	GDNS	=	Gardens	PL	=	Place
AVE	=	Avenue	GTWY	=	Gateway	PLZ	=	Plaza
BCH	=	Beach	GLN	=	Glen	PT	=	Point
BDWK	=	Boardwalk	GRN	=	Green	RDG	=	Ridge
BND	=	Bend	HBR	=	Harbor	RIV	=	River
BLF	=	Bluff	HTS	=	Heights	RD	=	Road
BLVD	=	Boulevard	HWY	=	Highway	RT	=	Route
BR	=	Branch	HL	=	Hill	ROW	=	Row
BRG	=	Bridge	HOLW	=	Hollow	RUN	=	Run
BYP	=	Bypass	INLT	=	Inlet	SHR	=	Shore
CPE	=	Cape	ISS	=	Island(s)	SKWY	=	Skyway
CYN	=	Canyon	ISLE	=	Isle	SQ	=	Square
CSWY	=	Causeway	JCT	=	Junction	ST	=	Street
CTR	=	Center	KY	=	Key(s)	TER	=	Terrace
CIR	=	Circle	KNLS	=	Knolls	THWY	=	Throughway
CLST	=	Cluster	LK	=	Lake	TRCE	=	Trace
COR	=	Corner	LNDG	=	Landing	TRFY	=	Trafficway
CRDR	=	Corridor	LN	=	Lane	TRL	=	Trail
CT	=	Court	LOOP	=	Loop	TUN	=	Tunnel
CV	=	Cove	MALL	=	Mall	TPKE	=	Turnpike
CRK	=	Creek	MNR	=	Manor	VLY	=	Valley
CRES	=	Crescent	MT	=	Mount	VIEW	=	View
CRV	=	Curve	MTN	=	Mountain	VLG	=	Village
DR	=	Drive	NOOK	=	Nook	VIS	=	Vista
EXPY	=	Expressway	OVAL	=	Oval	WALK	=	Walk
EXT	=	Extension	PARK	=	Park	WAY	=	Way
FRST	=	Forest	PASS	=	Pass	XING	=	Crossing
FRK	=	Fork	PATH	=	Path

Sample Instructions:

Move the contents of Property Street Type (419) to Street Suffix [10]

From Property Location 1 (15) strip valid street suffix material, conform to USPS standard, and move to Street Suffix [10]. Note that many of the addresses take the format "Fm Rd nnnnn" or "County Rd nnnnn", in which cases the "Rd" would not be a suffix.

Field No.	Field Name	Length	From	To	Data Type
11	Street Direction - Right	2	0125	0126	A

Description: Some street addresses will contain a directional indicator after the street suffix. The valid directional indicators are N, S, E, W, NE, NW, SE, and SW.

Examples:

123 Fourth Street North [would convert to N]

465 E Main Street W

Sample Instruction:

Also from (15) strip valid directional indicators occurring at the end of the data string (ex.: "Loop 00250 N") and move to Street Dir. Right [11].

Field No.	Field Name	Length	From	To	Data Type
12	Unit Number	6	0127	0132	A

Description: This field contains the suite, unit, or apartment number which is part of the valid situs address. This is common with condominiums, apartments, townhomes, co-ops, etc., both residential and commercial.

The data in this field may be alpha, numeric, or a combination of both. The number can be preceded by an indicator ("Apt.", "#", etc.): when formatting source data for this field, move only the number, not the indicator. Where two or more numbers are present, string them separated by a hyphen.

Examples:

Source	LAN-2 [12]
"Unit 5"; "#5", "Apt. 5", "Suite 5", etc.	5
"Building A, Suite 900"	A-900
"Trump Tower Penthouse"	PH

The conversion table below provides some of the more common ways in which unit numbers may be identified. This conversion table is provided here to assist in recognizing this data in the source files: no conversion is done to populate LAN-2 fields.

APT	=	Apartment	STE	=	Suite	SPC	=	Space
BLDG	=	Building	STOP	=	Stop	UPPR	=	Upper
DEPT	=	Department	TRLR	=	Trailer	SIDE	=	Side
FL	=	Floor	UNIT	=	Unit	REAR	=	Rear
HNGR	=	Hanger	BSMT	=	Basement	PH	=	Penthouse
LOT	=	Lot	FRNT	=	Front
PIER	=	Pier	LBBY	=	Lobby
RM	=	Room	LOWR	=	Lower
SLIP	=	Slip	OFC	=	Office

Sample Instruction:

Move the contents of Property Unit Number (422) to Unit Number [12].

Field No.	Field Name	Length	From	To	Data Type
13	Full Street Add. (non-fielded)	60	0133	0192	A

Description: The full situs address of the property is always moved to this field. When the source files contain fielded situs address information only, the contents of the situs address source fields are concatenated and moved to the individual, parsed fields and then concatenated and moved to this field. Rural routes are considered to be property addresses.

Sample Instructions:

Eliminating extra spaces, concatenate as follows and move to Full Street Address [13]:

Property House Number (421) [space] Property Direction (420) [space] Property Street Nm (418) [space] Property Unit Number (422)

Concatenate [6] through [11] and move the result to Full Street Address [13]. Separate the contents of each pair of adjacent fields with a single space.

Move the contents of E-911 Street Address (99) to Full Street Address [13]. Do not move if (99) begins with "PO".

Field No.	Field Name	Length	From	To	Data Type
14	City Name	30	0193	0222	A

Description: This field contains the name of the city or municipality where the property is located. The name of the city is NOT abbreviated for this field: where necessary, convert from abbreviated source data. However, when the city name is commonly shortened, this field is populated with the shortened version. When in doubt, consult the way the county formats the city name.

Examples:

Source	LAN-2 [14]
LA	Los Angeles
NY	New York
S San Francisco	South San Francisco
St Louis	St Louis

Sample Instruction:

Move PROP_CITY (7) to City Name [14].
If a move to [14] was made, populate Prop State [15] with “SC”.
Florence SC Ed 4
Populate PROPERTY CITY, STATE and ZIP code fields from corresponding mail address according to current general instructions.

Field No.	Field Name	Length	From	To	Data Type
15	State	2	0223	0224	A

Description: Two-letter standard postal abbreviation (see field #1), included here to complete the property address. Do not populate this field for records which do not contain property addresses.

Sample Instruction:

Move PROP_CITY (7) to City Name [14].
If a move to [14] was made, populate Prop State [15] with “SC”.
Florence SC Ed 4

Populate PROPERTY CITY, STATE and ZIP code fields from corresponding mail address according to current general instructions.

Field No.	Field Name	Length	From	To	Data Type
16	Property ZIP Code	5	0225	0229	N

Description: This data may be obtained from the assessed owner's mailing address for owner-occupied properties. Postal codes for foreign countries are not in the format nnnnn, and should be strung to the end of Full Street Address [13].

Sample Instruction:

Populate PROPERTY CITY, STATE and ZIP code fields from corresponding mail address according to current general instructions

Field No.	Field Name	Length	From	To	Data Type
17	Property ZIP+4	4	0230	0233	N

Description: This is the four-digit extension to the postal ZIP code for the property address. It is not always available.

Sample Instruction:

If Prop ZIP Code [16] > 0 & if [M31](6:4) > 0, move [M31](6:4) to Prop ZIP + 4 [17].

Field No.	Field Name	Length	From	To	Data Type
18	Assessee Owner Name	80	0234	0313	A

Description: This field contains the name of the assessed property owner as of the tax lien date. The name is usually moved exactly as shown in the current Assessor's Tax Roll. The formats in which this data comes from the source varies from county to county: some typical source data formats are:

LAST NAME FIRST NAME MI 2ND FIRST NAME MI

(JONES FRED A WILMA B)

LAST NAME FIRST NAME MI LAST NAME 2ND FIRST NAME MI

(JONES FRED A JONES WILMA B)

FIRST NAME MI LAST NAME 2ND FIRST NAME MI

(FRED A JONES WILMA B)

FIRST NAME MI LAST NAME 2ND FIRST NAME MI LAST NAME

(FRED A JONES WILMA B JONES)

The individual names may or may not be separated by commas or ampersands in the source data: treatment of "junior’s, "aka"s, "II"s, etc., varies from county to county.

NOTE: This field accepts the name of the buyer under a Contract of Sale. See the pages for 2nd Owner Name [19] and Assessee Owner Vesting Code [20] for how the name of seller and the vesting code are handled in this situation.

NOTE: Please see the list of source data indicators for criteria you can use to separate owners' names, "care-of" names, and other types of names more precisely.

Sample Instructions:

Strip any text enclosed in parentheses and move the remaining contents of (5) to Assessee Owner Name [18].

For those same records, also move the contents of (4) to Assessee Owner Name [18]. Replace any embedded virgule ("/") with a single space.

Field No.	Field Name	Length	From	To	Data Type
19	2nd Owner Name	60	314	373	A

Description: This field is used for additional assessed owners' names, when provided by the county, for spouses' names when these can be separated during processing, or for DBAs, FKAs, NKAs, T/As, FBOs, etc., where available. As in (18), and names are usually moved to this field exactly as shown in the current Assessor's Tax Roll. When second names are fielded separately in the source files, handling of vesting indicators, corporate ownership, etc., is also as for (18).

NOTE: This field accepts the name of the seller under a Contract of Sale. See the pages for Assessee Owner Name [18] and Assessee Owner Vesting Code [20] for how the name of buyer and the vesting code are handled in this situation.

NOTE: Please see the list of source data indicators for criteria you can use to separate owners' names, "care-of" names, and other types of names more precisely.

Sample Instruction:

For those records in which (5) begins with "dba", move the contents of (5) to 2nd Owner Name [19].

For those records in which the contents of (7) were not already moved, move the contents of (7) to 2nd Owner's Name [19]. Strip any leading ampersands.

Field No.	Field Name	Length	From	To	Data Type
20	Assessee Owner Vesting Code	2	0374	0375	A

Description: This field either identifies how the assessed owner took title (vesting) or describes the type of entity (ID), based on the following conversion:

AK	Also known as (a/k/a)	JV	Joint venture
CO	Company/Corporation	LE	Life estate
CP	Community Property	LV	Living trust
CT	Contract owner	MI	Minor/guardian
DB	Doing business as (d/b/a)	MM	Married man/sole and separate property
EA	Etal (and others)	MW	Married woman/sole and separate property
ES	Estate	PA	Partnership
EU	Et ux (and wife)	RT	Revocable trust
EX	Executor	SM	Single/unmarried man
FK	Formerly known as (f/k/a)	SO	Sole Owner
FM	Family trust	SW	Single/unmarried woman
GV	Government	TC	Tenants in common
HH	Her husband (St Louis County)	TE	Tenants by the entirety
HW	Husband and wife	TN	Tenant
IR	Irrevocable trust	TR	Trustee/conservator
TD	Transfer on Death	TS	Trustees
JS	Joint tenants with right of survivorship	WD	Widow/widower
JT	Joint tenancy	TX	Tax Payer

NOTE: The "CT" code (Contract Owner) should never be overwritten by other content in this field. See the pages for Assessee Owner Name [18] and 2nd Owner Name [19] for how the names of seller and buyer under a Contract of Sale are handled.

See the summary of vesting selection criteria.

Sample Instruction:

Also make the following moves to Assessee Owner Vesting Code [20]:

If (12) or (13) ends with	Then move to [20]
"Partnership"	PA
a valid company indicator ("Co.", "Inc.", "Corp", etc., spelled out or abbreviated with or without periods)	CO
"Family Trust"	FM
"Revocable Trust"	RT
"Irrevocable Trust"	IR
"Living Trust"	LV
"Trust" or "as Trustee"	TR
"Life Estate" or "Life Est"	ES
"Et Al", "Etal", or "+ Etal"	EA (strip the "+")

Owner Mail Street Addr 1 (5) is a new field for this file and contains the owner's name if the owner is not a real person (i.e., if the owner is a company, a government entity, etc.). NOTE: The owner's name for some records for which the owner is not a real person are still listed in (4). Process the contents of (5) as follows:

If (5) ends with or contains a valid company indicator ("Co", "Inc", "LLC", "Assoc", "Corp", "Ltd", etc., spelled out or abbreviated), move "CO" to Assessee Owner Vesting Code [20].

If (5) ends with "Trust", "(TR)", or "(TRS)" or begins with "TR[space]", "TRS[space]", "Trustee", or "Trustees", move "TR" to [20].

If (5) ends with "Partnership" or "Prship", move "PA" to [20].

If (5) = "Buncombe County" or begins with "Town of" or "The Town of", move "GV" to [20].

Field No.	Field Name	Length	From	To	Data Type
21	Tax Account Number	30	0376	0405	A/N

Description: This field accepts the tax account number assigned by the County.

Sample Instruction:

Move Account (6) to Tax Account Number [21].

McClain OK Ed 9

Field No.	Field Name	Length	From	To	Data Type
22	Mail Care-of Name	60	0406	0465	A

Description: When the sources file gives the owner's mailing address as "care of" another party (typically a business, an accountant, an attorney, etc.), the "care-of" name is extracted and moved to this field. Any leading "care-of" indicator ("c/o", "%", etc.) is stripped.

NOTE: Please see the list of source data indicators for criteria you can use to separate owners' names, "care-of" names, and other types of names more precisely.

Sample Instruction:

If (7) begins with a valid "care-of" indicator ("c/o", "%", "attn", etc.), strip the indicator and move the remainder to Mail Care Of Name [22].

Field No.	Field Name	Length	From	To	Data Type
23-34	Assessee Mailing Address (12 fields)	178	0466	0643	A/N

Description: These fields contain the address where the current tax bill is sent each year. Formatting will vary greatly from county to county. Whenever possible, the mailing address data is fielded the same way as the property address (see fields 6-17) and also moved to Mail City, State & ZIP (89).

For foreign mailing addresses only, Mail State Code (32) = "XX" and Assessee Mail ZIP Code (33) and Assessee Mail ZIP+4 (34) = [blank], even if postal code data is given. When possible, the foreign country and postal code should be strung to Assessee Mail Full Street Address (30).

Source files will sometimes contain a field flagging records for which mail to the assessed owner was returned by the post office as undeliverable. Use the property address if available, if not use the undeliverable mail address.

Note that mailing addresses are never constructed from situs addresses.

Sample Instruction:

Move the contents of Owner Address (6) to Mail Full Street Address (30).

Move the contents of Address (14) to Mail Full Street Address (30).

Move the contents of City (15) to Assessee Mail City Name (31).

Move the contents of State (16) to Assessee Mail State Code (32). (Conform to USPS standard before moving.) Do not move if (16) contains numeric characters or = "ON".

Move the contents of ZIP (17) to Assessee Mail ZIP Code (33).

From Owner State (8), move those contents which conform to USPS standard state abbreviations to Assessee Mail State (32). For those records in which the contents of (8) are not moved, DO NOT move ZIP Code information (next step).

Move the contents of Owner ZIP (9) to Assessee Mail ZIP Code (33), except as noted in the above step.

Process the contents of Mail City/State (12) as follows:

A) Move the first 23 bytes to Assessee Mail City Name (31). Do not move "Unknown".
B) Move the last two bytes to Assessee Mail State Code (32). Do not move "0H" [(zero)H], "A", "C", "C2", "CC", "CN", "D", "E", "GS", "PG", "RD", or "SS".

Move the first 5 bytes of Mail ZIP (13) to Assessee Mail ZIP Code (33).

Move the last 4 bytes of (13) to Assessee Mail ZIP+4 (34)

Process the contents of Post Office (13) as follows:

Strip state abbreviations, conform to USPS standard and move to Assessee Mail State Code (32).

Strip any trailing commas from the city name and move to Assessee Mail City Name (31).

If [16] is a unit #, move to MAIL UNIT-NUMBER. Move spaces to [16].

If [20] <> "TAX FORECLOSURE", if [18] > spaces & does not contain any alphabetic character, then, move [18] to MAIL STREET HOUSE-NUMBER, move [19] to MAIL STREET DIRECTION-LEFT if its a valid direction, move [20] to MAIL STREET NAME(Extract other component to respective output field if present. See sample #3 & #4) , move [21] to MAIL STREET SUFFIX(see sample #4), move [23] to MAIL UNIT-NUMBER(suppress "#" & left justify). Otherwise, concatenate [18] thru [23] to MAIL FULL STREET ADDRESS.

Field No.	Field Name	Length	From	To	Data Type
35	State Land Use Code	10	0644	0653	A/N

Description: This field contains the land use code used by the state for land use classification. Only populate this field if this code is different from County Land Use Code [72].

Field No.	Field Name	Length	From	To	Data Type
36	Owner-occupied	1	0654	0654	A

Description: Owner-occupancy of residential property is indicated by a "Y" in this field if EITHER:

Description: Owner-occupancy of residential property is indicated by a "Y" in this field if EITHER:

A) Tax Exemption Codes [42] contains "D" OR CA Homeowner’s Exemption [41] = “H”OR B) Full Street Address [13] and Mail Full Street Address [30] match (first 10 bytes) AND IF Standardized Land Use Code [73] = 1001-1009, 1013, 1014, 1016, 1017, 1999, 1101, 1102, 1103, or 1110 AND IF Assessed Improvement Value [38] or Market Value Improvements [95] > zero AND IF Assessee Owner Vesting Code [20] is not = GV, PA, ES, or CO.

Note that the conditions of land use, improvement value, and vesting codes apply to all parcels flagged as owner-occupied.

This means that in order to be flagged as owner-occupied, a record must have EITHER a homestead exemption or an address match AND must meet all the other requirements above.

This logic is to be applied AFTER land use has been enhanced by moving SLUC "1999" to output if the existing SLUC = "1000" and a homestead exemption is present OR if land use is not indicated (blank) but bedrooms, bathrooms, etc., are shown.

Presumed owner-occupancy is indicated by a "B" in this field for records in which no exemption or address match exists but there is reason to believe that the owner of the property does in fact live there. The determination to use this code is made on a case-by-case basis.

If the above conditions are not fulfilled, this field should be blank.

Sample Instruction:

Populate Owner Occupied [36] with "Y" if EITHER of the following conditions are met:

If TAX_COMM Exempt Flag (43) = "S1", "S2", "S3", or S4", OR

If the first 5 bytes of Mail Full Street Address [30] match the first 5 bytes of Full Street Address [13]

AND IF

Standardized Land Use Code [73] = 1001-1009, 1013, 1014, 1016, 1017, 1999, 1101, 1102, 1103, or 1110

AND IF

Assessed Improvement Value [38] > 0

AND IF

Assessee Owner Vesting Code [20] is not = GV, PA, ES, or CO.
Apply the latest Owner Occupied routine.

Field No.	Field Name	Length	From	To	Data Type
37	Assessed Land Value	10	0655	0664	N

Description: This is the assessed value of the land only, as reported on the County tax or assessment roll, before any exemptions are taken. Where appraised values only are given and the formula for calculating the assessed value is known, the assessed values may be derived from appraisal.

Sample Instruction:

Move the contents of Curr Appr LV (29) to Assessed Land Value (37).

Divide the contents of Market Value Land (94) by 2 and move the result to Assessed Land Value (37).

Field No.	Field Name	Length	From	To	Data Type
38	Assessed Improvement Value	10	0665	0674	N

Description: This is the assessed value of the improvements only, as reported on the County tax or assessment roll, before any exemptions are taken. Where appraised values only are given and the formula for calculating the assessed value is known, the assessed values may be derived from appraisal. If the source data does not include a total assessed value for all improvements on the property, this is calculated by summing the values given for the separate improvements.

Sample Instruction:

Sum the contents of Curr Appr HV (30) and Curr Appr BV (31) and move the result to Assessed Improvement Value (38).

Divide the contents of Market Value Improvement (95) by 2 and move the result to Assessed Improvement Value (38).

Field No.	Field Name	Length	From	To	Data Type
39	Total Assessed Value	11	0675	0685	N

Description: This field contains the total current assessed value of the land and improvements. The figures in this field are given before any exemptions are taken.

Calculate this field by adding Assessed Land Value [37] and Assessed Improvement Value [38], however note that occasionally the county will also factor in deferred assessed values, agricultural assessed values (crops), etc. Care should be taken to ensure that the total assessed values in the LAN-2 database corresponds to the total assessed values in the county records.

Sample Instruction:

Sum the contents of (29), (30) and (31) and move the result to Total Assessed Value (39).

Divide the contents of Total Market Value (96) by 2 and move the result to Total Assessed Value (39).

Field No.	Field Name	Length	From	To	Data Type
40	Assessment Year	4	0686	0689	N

Description: This is the year in which the tax lien derived from the assessments given in fields 37-39 was levied. If this is a fiscal year (e.g.; March 1995 – February 1996), the earlier of the two years would be used (1995).

Sometimes we receive source files which do not provide any assessed values, or in which the assessed values are updated so infrequently (i.e.; every ten years) that the year the value was established may be misleading. In these cases, the assessment year is considered to be the year we obtained the current file from the taxing jurisdiction or the year the owners of record on the file were certified. When this is done, our documentation should state clearly how the assessment year values were created.

Sample Instruction:

Move "1997" to Assessment Year (40).

Field No.	Field Name	Length	From	To	Data Type
41	Calif.Homeowner's Exemption	1	0690	0690	A

Description: If the property has received a California State Homeowner's Exemption, this field should = "H" (default = [blank]).

A homeowner's exemption is not the same as a homestead, or a homestead exemption.

Sample Instruction:

If [51] or [52] or [53] or [54] = "10", move "H" to CALIF. HOMEOWNER'S EXEMPTION.

Field No.	Field Name	Length	From	To	Data Type
42	Tax Exemption Codes	4	0691	0694	A

Description: This field reports the tax exemptions to which the owners of the property are entitled. Exemptions are usually based on either the use of the property (e.g.; church, cemetery, school) or a factor of ownership (e.g.; veteran, Native American, disabled, senior citizen). In some jurisdictions, agricultural deferments of real estate taxes are given. These are not reported here.

Tax exemptions reported in the source file are converted per the table below and the results strung in this field. The format is AAAA, with no separation between individual codes. The default value is [blank].

A	Agricultural	L	Library/museum	R	Religious/church
Q	Charity/frat. org.	I	Low income	F	Senior citizen
C	Cemetery	M	Miscellaneous	S	School/college
B	Disabled (general)	Y	Native American	E	Tax exempt
G	Government	N	Non-profit	V	Veteran
K	Head of h'hold	O	Orphanage	W	Welfare
H	Historical	J	Partial exemption	Z	Widow/widower
D	Homestead	P	Public utilities	X	Railroad
T	Hospital/medical	U	Redev. agency

Sample Instruction:

Populate Tax Exemption Code (42) as follows:

If source Field #	Contains	Then Append	To the contents of LAN-2 Field #
(45)	"S"	"F"	(42)
(45)	"H"	"D"	(42)
(47)	>0	"B"	(42)
(49)	"E"	"E"	(42)

Do not separate individual codes within (42) with commas or spaces.

Convert the contents of Exemption Code (65) per the following table to populate Tax Exemption Codes (42). When more than one code is moved for a single record, string the codes without separation.

If (65) Contains	Which means	Then move To (42)
1	Homestead exemption	D
3	Under appeal w/homestead exempt.	[no move]
4	Under appeal	[no move]
5	Exempted by DOR (Dept/Revenue)	E
6	Owned by city or town	G
7	Owned by county, public service districts, schools, etc.	G
8	SC State, Highway Dept, state colleges & tech schools	G
9	Fed government, USA, SC & regional housing authority	G
A	[no conversion noted]	[no move]
F	[no conversion noted]	[no move]
S	Exempted from taxes – solid waste fee only	J
T	Exempted from taxes & solid waste fee – special sewer service fee only	J
U	Utility – returns filed with DOR	P
X	[no conversion noted]	[no move]

Field No.	Field Name	Length	From	To	Data Type
43	Tax Rate Code Area	18	0695	0712	A

Description: This field contains information about the taxing entities levying against the property. Typically, this information will be available in one of two forms: either a geographic breakdown of the county into taxing jurisdictions or a listing of those entities within whose tax boundaries the property exists. Either of these forms may be given as codes or set forth in narrative form.

Availability and formatting of this data varies widely from county to county: consequently, this field may be filled by a single narrative statement of the taxing entity or tax district or, at the other extreme, a series of codes separated by commas which more-than-fill the field. Show as many codes as possible.

Sample Instruction: String "Tax District" + [the contents of Tax District (9)] and move to Tax Rate Code Area (43).

Move the contents of Tax District (64) to Tax Rate Code Area (43).

Field No.	Field Name	Length	From	To	Data Type
44	Tax Amount	10	0713	0722	N

Description: This field contains the amount of tax on the property expressed in dollars and cents. In some states such as California, tax amounts are not available at the same time the Assessment Roll is certified. Decisions are made on a county-by-county basis to wait for the tax amount.

NOTE: In cases where you have a gross and a net tax amount, net tax amount takes precedence over gross tax amounts.
The tax amount field should reflect what the tax payer was billed for the Tax Year (45).
The format for this field is 9(8)v99.

Sample Instructions:

Move the contents of Curr Tax Due (37) to Tax Amount [44].

Move the sum of the following fields to TAX AMOUNT [44]:
Tot Due 1 (15)
Tot Due 2 (31)
Move "2002" to TAX YEAR [45] if [44] is populated.
Medina OH Ed 9

Field No.	Field Name	Length	From	To	Data Type
45	Tax Year	4	0723	0726	N

Description: This is the year in which the amount shown in Tax Amount [44] was levied.

Sample Instruction:

Move the contents of Tax Year (7) to Tax Year [45].

Move the sum of the following fields to TAX AMOUNT [44]:
Tot Due 1 (15)
Tot Due 2 (15)
Move "2002" to TAX YEAR [45] if [44] is populated.
Medina OH Ed 9

Field No.	Field Name	Length	From	To	Data Type
46	Tax Delinquent Year	4	0727	0730	N

Description: This is the year in which the property tax became delinquent (unpaid).

Sample Instruction:

Move Tax Del Year (7) to Tax Delinquent Year (46).

Field No.	Field Name	Length	From	To	Data Type
47	Recorder's Document Number	20	0731	0750	A

Description: This is a sequential number assigned to documents at the time of recording for the purposes of identification and to establish the order of recording. Recorders will usually assign either a document number or a book-and-page (see fields 48-49) to accomplish this. One county uses book and instrument number, but this is not usual. From county to county, document numbers may begin daily, monthly, or yearly with number 1 and from there run consecutively until the end of their established numbering time period.

Usually, the source file will report the document establishing the most recent change of ownership. Occasionally the document reported will simply be the most recent document affecting that property.

Sample Instruction:

If source [5] > "0", then move [5] to Lan-2 Document Number [47].

Field No.	Field Name	Length	From	To	Data Type
48	Recorder's Book Number	10	0751	0760	A

Description: This is the first half of a sequential numbering system by which recorded documents may be uniquely identified and the order of recording established. Recorders will usually assign either a book-and page or a document number (see field 47) to accomplish this. One county uses book and instrument number, but this is not usual.

Typically, book numbers will begin with 1 and run consecutively to the present. Some counties use a system in which the book number represents the date (in various formats). Formatting may also include letters or other designations either before or after the numbers. Some counties maintain several sets of recording books, one set for each class of document. Thus, Plat Books would contain maps of real property locations, while Deed Books would contain property ownership recordings. In some jurisdictions this breaks down further and it is necessary to state which type of book is being referenced (this can be abbreviated according to the county's usage).

Usually, the source file will report the document establishing the most recent change of ownership. Occasionally the document reported will simply be the most recent document affecting that property.

In the source file, book numbers may be termed liber numbers ("liber" is Latin for "book").

Sample Instruction:

Move the first 4 bytes of Deed Book/Page (21) to Recorder's Book Number (48). Move the last 4 bytes to Recorder's Page Number (49). Ignore records in which (21) = "0999-0999": note that "0999" may be a valid page number, but it is not a valid book.

Field No.	Field Name	Length	From	To	Data Type
49	Recorder's Page Number	10	0761	0770	A

Description: This is the second half of a sequential numbering system by which recorded documents may be uniquely identified and the order of recording established. Recorders will usually assign either a book-and page or a document number (see field 47) to accomplish this.

Typically, page numbers will begin with 1 for each recording book, and run consecutively to the end of that book. Usually, the source file will report the document establishing the most recent change of ownership. Occasionally the document reported will simply be the most recent document affecting that property.

In the source file, page numbers may be termed folio numbers ("folio" is Latin for "page").

Sample Instruction:

Strip leading zeros and move the contents of Deed Page 1 (93) to Recorder's Page Number (49). Do not move [blank] values: move nothing if Recorder's Book Number (48) = [blank].

Field No.	Field Name	Length	From	To	Data Type
50	Recording Date	8	0771	0778	N

Description: This is the date on which a document was recorded (it is not usually the actual sale date, as recording does not usually occur on the same date as the sale.)

This field is formatted MMDDYYYY: when the day of recording is not given in the source file, the output format should be MM00YYYY. When both a recording data and a sale date are available in a source file, use the recording date. If only a sale date is available, use the sale date.

Sample Instruction:

Convert the contents of Sale Date (22) to MMDD19YY format and move to Recording Date (50).

String the following together and move result to Recording Date (50):

The contents of Sale Month (17)

The contents of Sale Day (18)

The string "19", and

The contents of Sale Year (19)

Move nothing to (50) if the contents of any of these fields = [zeros].

Field No.	Field Name	Length	From	To	Data Type
51	Document Type	25	0779	0803	A

Description: This field contains a code for the type of document used to establish ownership of the property. The source file may provide this information in coded or narrative form. Depending on the content of the source file, the decision to use the source file codes, the source file description, or our two-letter code (see conversion table below) is made on a county-by-county basis.

This field can be populated even if sale price and/or document numbers are not available if the information available serves to more clearly establish how ownership was created.

AD	Administrator's Deed	GF	Gift Deed
AF	Affidavit	GR	Ground lease
AG	Agreement of Sale	IT	Interfamily transfer & dissolution
AS	Assignment Deed	ID	Individual Deed
CD	Condominium Deed	JT	Joint Tenancy Deed
CO	Conservator's Deed	LA	Legal action / court order
CP	Corporation Deed	LD	Land Contract
CR	Correction Deed	OT	Other [use minimally]
CS	Contract of Sale	PA	Public Auction
DC	Declaration	PD	Partnership Deed
DE	Deed	PR	Personal Representative's Deed
DG	Deed of Guardian	QC	Quitclaim Deed
DJ	Affidavit/Death of Joint Tenant	RC	Receiver's Deed
DL	Deed in Lieu of Foreclosure	RD	Redemption Deed
EX	Executor's Deed	RR	Re-recorded document *
FC	Foreclosure	SD	Sheriff's Deed
GD	Grant Deed	TD	Trustee's Deed [seller = beneficiary]
WD	Warranty Deed

* A document is usually re-recorded to correct an error or to establish the correct recording sequence among two or more documents.

Sample Instruction:

Process the contents of Sale Inst (296) as follows and move result to Doc Type (51):

For contents which match the Standard Document Type Code conversion table, move the result of the standard conversion.

For contents beginning with "W", move "WD".

For "DP", move "Deed under power".

For "RW", move "Right of Way".

For all other non-[blank] records, move "OT".

Field No.	Field Name	Length	From	To	Data Type
52	Sale Price	10	0804	0813	N

Description: Sale price greater than $500.00 is entered in whole dollars only. Availability will vary from county to county. Often the reported sale price is not the actual sale price, and so cannot be used to establish market value [see Sale Price Code (53)].

Field is used only when a corresponding recording date is available.

Sample Instruction:

Ignore values in Sale Price (16) in which the first byte  0: also ignore records for which this field < 500. Of those remaining, strip leading zeros and move remainder to Sales Price (52) and also move "A" to Sales Price Code (53). Values in (16) are formatted 9(11)V99.

Move Sale Price (299) if greater than $500 to Sales Price (52).

Field No.	Field Name	Length	From	To	Data Type
53	Sale Price Code	1	0814	0814	A

Description: Because the sale price reported in the source file is not always the actual dollar amount paid for a property, we need to be able to tell our customers how the reported sale price was derived. The following codes are used to do this:

D	Reported sale price = full price (recorded document states actual amount)
F	Reported sale price = full amount computer from transfer tax (on recorded document)
P	Reported sale price = partial amount computed from transfer tax (on recorded document)
U	Reported sale price computed from transfer tax with no indication of whether tax was paid on full or partial consideration (on recorded document)
A	Reported sale price = full amount (from file with no confirmation)
X	Sale price not available (recorded document states not a matter of public record)
Q	Assessor qualified as a comparable sale

Sample Instruction:

Ignore values in First Hist Price (23) in which the first byte  0: also ignore records for which this field < 500. Of those remaining, strip leading zeros and move remainder to Prior Sales Price (55) and also move "A" to Sales Price Code (53). Values in (23) are formatted 9(11)V99.

Field No.	Field Name	Length	From	To	Data Type
54	Prior Sale Date	8	0815	0822	N

Description: This is the date of sale for that sale immediately prior to the most recent one.

Sample Instruction:

For those records in which the contents of First Hist Price (23) 500, move the contents of First Date (24) to Prior Sales Date (54). The contents of (24) are formatted mmddyy: insert the string "19" between byte positions 4 and 5 prior to moving.

Field No.	Field Name	Length	From	To	Data Type
55	Prior Sale Price	10	0823	0832	A

Description: This is the price paid by the previous owner of the property.

Use only when a corresponding recording date is available.

Sample Instruction:

Ignore values in First Hist Price (23) in which the first byte  0: also ignore records for which this field < 500. Of those remaining, strip leading zeros and move remainder to Prior Sales Price (55) and also move "A" to Sales Price Code (53). Values in (23) are formatted 9(11)V99.

Field No.	Field Name	Length	From	To	Data Type
56	Prior Sale Price Code	1	0833	0833	A

Description: The code in this field indicates whether the reported prior sale amount is

F	Full
P	Partial
C	Confirmed
U	Unknown
A	Assessor
Q	Qualified
D	Deed
X	Not available

Sample Instruction:

If [S26] > 0 & >= 500, move [S26] to PRIOR SALES PRICE & move "A" to PRIOR SALES CODE. [S26] is 9(9) packed

Field No.	Field Name	Length	From	To	Data Type
57	Legal Lot Code	2	0834	0835	A

Description: This code identifies records for which the lot(s) in question are either multiple or partial, as opposed to single. The valid codes for this field are:

P	Portion of a single lot
M	More than one lot
MP	Multiple with a portion of one or more lots

Examples:	Source	LAN-2 (57)
The north half of lot A	P
Lots A and B	M
Lot A and the north half of lot B	MP

The default is [blank].

Sample Instruction:

If (75) begins with "LT" or "LTS", move the subsequent value(s) to Legal Lot Number (58). Note that the lot numbers may be numeric or alpha characters. Also note that if the leading string is "LTS", there may be two or more lot number values separated by spaces, commas, ampersands, or plus signs. If the leading string is "LTS", also move "M" to Legal Lot Code (57).

If the contents of (5) include a single lot number (e.g.: "Lot 2"), move the number of the lot to Legal Lot Number (58). If more than one lot number is indicated ("Lots 4-5-6", etc.), move all numeric values and also move "M" to Legal Lot Code (57). Do not truncate mid-word.

Field No.	Field Name	Length	From	To	Data Type
58	Legal Lot Number	7	0836	0842	A

Description: The actual lot number(s) covered by the record, such as any lot in a tract or subdivision. If there is more than one lot, enter as many numbers as will fill the field, separating adjacent numbers with a comma or an ampersand. Use a dash to indicate ranges of lot numbers.

Examples:	Source	LAN-2 (58)
Lot A, Block 12, Tract 12696A	12
Lots 14, 15, 16 and 18	14-16,18
Lots 24 through 28 and lot A	24-28,A

When extracting lot numbers from narrative legal descriptions, beware of the possibility that more than one type of lot may be mentioned in the legal. Besides the actual lots being described, there are also "parent" lot numbers which describe parcels of land from which the lot(s) we're interested in were derived.

Example:"… lot 12 of the subdivision of Lot A …"
(lot 12 is the one we want)

Sample Instruction:

If (75) begins with "LT" or "LTS", move the subsequent value(s) to Legal Lot Number (58). Note that the lot numbers may be numeric or alpha characters. Also note that if the leading string is "LTS", there may be two or more lot number values separated by spaces, commas, ampersands, or plus signs. If the leading string is "LTS", also move "M" to Legal Lot Code (57).

If the contents of (5) include a single lot number (e.g.: "Lot 2"), move the number of the lot to Legal Lot Number (58). If more than one lot number is indicated ("Lots 4-5-6", etc.), move all numeric values and also move "M" to Legal Lot Code (57). Do not truncate mid-word.

Field No.	Field Name	Length	From	To	Data Type
59	Legal Land Lot	10	0843	0852	A

Description: A Land Lot is a mapping term used in a survey system unique to Georgia, usually a subset of a district [see Legal District (62)]. Move land lot designations as stated in the source file, using commas, ampersands and dashes to indicate multiple land lots or ranges of land lots.

Sample Instruction:

Extract and move to Legal: Land Lot (59) those portions of (428) which designate Land Lot numbers. These will be found in the initial byte strings in the field: they will begin with "LL", followed by a space, a dash, or no separator, and then one or more numerical values. separated by commas, spaces, ampersands, and/or dashes.

Field No.	Field Name	Length	From	To	Data Type
60	Legal Block	7	0853	0859	A

Description: "Block" is the term used to describe the next largest classification of subdivided property, after "lot", in most legal descriptions. Move block designations as stated in the source file; however, be aware that some legal descriptions will include "block" designations in descriptions of larger tracts of land from which the parcel you're working with was subdivided [see Legal Lot Number (58) for an example of this].

Sample Instruction:

Move the first numerical word following the string "BLK" to Legal Block (60).

Field No.	Field Name	Length	From	To	Data Type
61	Legal Section	7	0860	0866	A

Description: "Section" is the term used to describe the next largest classification of urban land, after "block", in some urban legal descriptions. Move section designations as stated in the source file; however, be aware that in counties having both urban and rural areas, rural legal descriptions may also contain "section" terminology that has nothing to do with urban sections. See Legal Sec/Twn/Rng/Mer (68) for a description of this other usage of the word.

Sample Instruction:

If [P1](8:2) > "00", move to LEGAL: SECTION.

Field No.	Field Name	Length	From	To	Data Type
62	Legal District	12	0867	0878	A

Description: This field is used to provide the (usually numeric) code designation of the district within which the parcel is located.

The narrative name of the district should be moved to Legal City, Municipality, Township [64].

In a Georgia county this field is used for the map district number that corresponds with the land lot number.

Sample Instruction:

Convert BOROUGH (13) according to the table below and populate Legal: District [62] & Legal: City/Mun/Twn [64].

Move source to [62]	Move to [64]
"CH" or "CHR"	"Chuckatuck Borough"
"CY" or "CYR"	"Cypress Borough"
"HN" or "HNR"	"Holy Neck Borough"
"NM" or "NMR"	"Nansemond Borough"
"SH" or "SHR"	"Sleepy Hole Borough"
"SU" or "SUR"	"Suffolk Borough"
"WH" or "WHR"	"Whaleyville Borough"

Suffolk, VA Ed12

Field No.	Field Name	Length	From	To	Data Type
63	Legal Unit	6	0879	0884	A

Description: Subdivision unit number

Sample Instruction:

Extract the "unit number" bytes (1:23-1:24) and move to Legal Unit Number (63).

Field No.	Field Name	Length	From	To	Data Type
64	Legal City / Municipality / Township	30	0885	0914	A

Description: This field contains the name of the municipal jurisdiction within which the property is located. In Pennsylvania counties this may be stated as township, boro, or ward, and is an essential part of the legal description. Usually the narrative version of the contents of Legal District [62].

Sample Instruction:

Convert BOROUGH (13) according to the table below and populate Legal: District [62] & Legal: City/Mun/Twn [64].

Move source to [62]	Move to [64]
"CH" or "CHR"	"Chuckatuck Borough"
"CY" or "CYR"	"Cypress Borough"
"HN" or "HNR"	"Holy Neck Borough"
"NM" or "NMR"	"Nansemond Borough"
"SH" or "SHR"	"Sleepy Hole Borough"
"SU" or "SUR"	"Suffolk Borough"
"WH" or "WHR"	"Whaleyville Borough"

Suffolk, VA Ed12

Field No.	Field Name	Length	From	To	Data Type
65	Legal Subdivision Name	40	0915	0954	A

Description: This field contains the name of the subdivision or plat or tract within which the property is located. If the name is not available and the number is, use the number.

Sample Instruction:

Move the contents of Subdivision Name (98) to Legal Subdivision Name (65).

Field No.	Field Name	Length	From	To	Data Type
66	Legal Phase No.	7	0955	0961	A

Description: This field generally refers to the phase number of a subdivision or tract development.

Field No.	Field Name	Length	From	To	Data Type
67	Legal Tract No.	10	0962	0971	A

Description: This field contains the number of the tract within which the property is located.

Example: Lot 44, Block 12, Tract 24680

Sample Instruction:

If (75) begins with "TR[space]", move the numeric value(s) that immediately follow this string to Legal Tract Number (67).

Field No.	Field Name	Length	From	To	Data Type
68	Legal Sec/Township/Range/Meridian	30	0972	1001	A

Description: The government performed a survey of most of the nation in the last century. As part of this survey, the country was divided into sectionalized land: regional monuments (mountain peaks, etc.) were used as base points for systems of grids that covered the surrounding areas. The horizontal lines running through the reference landmarks are called meridians, the vertical ranks of squares in these grids are called ranges, the horizontal ranks are called townships, and within each square (nominally six miles on a side) are 36 sections.

The following link shows a map with the STR states and metes and bounds states.
US Sec/Twn/Rng.

Unsubdivided tracts of land are still legally described in terms of these sections, townships and ranges. The source format may vary, but it is generally in the form Section nn Township nn(N/S) Range nn(E/W). A typical sectionalized land legal description would read "S22 T5n R16w". The LAN-2 Standard is SEC nn TWN nn(N/S) RNG nn(E/W).

Within this field, the sectionalized legal information is laid out as follows:

Byte Position	Contents	Format
1-18	Detail within section	directional + fractional indicators showing progressively larger areas within the section Example: n2 of sw4 (north half of southwest quarter)
19-20	Section number	Numeric; usually between 1-36
21-23	Township number	Numeric with a north/south suffix
24-26	Range number	Numeric with an east/west suffix
27-30	Meridian	Four-letter abbreviation Example: "MDBM" = "Mount Diablo Base and Meridian")

Example:
Source:	S2 NW4 SW4 S25 T9n R13w SBBM (south half of the northwest quarter of the southwest quarter of Section 25, Township 9 north, Range 13 west, San Bernardino Base and Meridian)
LAN-2:	S2 of NW4 of SW4 25 9n 13w SBBM

Sample Instruction:

Isolate those records in which any of the legal description fields Legal 1(9) through Legal 10 (18) contains only one instance of the string "SEC nn TnN RnnE". Note that the string may or may not contain spaces between the elements or between the alpha and numeric portions of the elements. For those records, conform that string to LAN-2 standard format (SEC nn TWN nnN RNG nnE) and move to Legal Sec/Twn/Rng/Mer (68).

Concatenate the geographical location fields (44) through (49) as follows to populate Legal Sec/Twn/Rng/Mer (68):

Loc Portion Code (44)	LAN-2(68)
"ALL"	"All of" at beginning of output string
"MOR"	"more" at end of output string
"PT"	"Part of" at beginning of output string

Plus the contents of Section brkdwn 1 (45)
Plus the contents of Section brkdwn 2 (46)
Plus the contents of Section (47)[contents]"S"
Plus the contents of Township (48)[contents]"T"
Plus the contents of Range (49)[contents]"R"

Examples:
"All of NW4 NE4 S 15 T 22 R 61"
"W2 SE4 S 15 T 22 R 61 more"
"Part of E2 NW4 S 15 T 22 R 61"

Field No.	Field Name	Length	From	To	Data Type
69	Legal Brief Description	125	1002	1126	A

Description: In this field is strung whatever narrative legal description is given in the source file, exactly as given, whether or not detailed data is extracted to populate other LAN-2 fields.

Sample Instruction:

Concatenate Legal 1(9) through Legal 10 (18), eliminating extra spaces, up to an output length of 125 bytes. Move result to Legal Brief Description (69). Do not truncate output mid-word.

String the contents of (73), (74), and (75), eliminating extra internal spaces and separating the contents of each pair of fields with a single space, and move the result to Legal Brief Description (69).

Field No.	Field Name	Length	From	To	Data Type
70	Legal Assessor's Map Ref.	15	1127	1141	A

Description: This field contains the Assessor's Map reference, which may or may not be the same as either the APN or the legal map references. This is the map number assigned to the parcel by the Tax Assessor.

The valid codes for the different types of maps are:

PM	Parcel Map	MB	Map Book, Plat or Volume
PG	Page number	MAP	Maps
MP	Misc. maps	LB	Liber
PAT	Patents	FO	Folio

Sample Instruction:

Extract the contents of (73) from the first [space] to the first [space][space]. Then, eliminate leading zeros from the two words before and after the slash. Label these two words "BK" and "PG" and string the result to the end of Legal Assessor's Map Reference (70). For example:

Source CP 0093/00970 PP S 112/005

becomes LAN-2 (70) Bk 93 Pg 970

Source CP S-638/5B PP 094/0200

becomes LAN-2 (70) Bk S-638 Pg 5B

Note that many records will have no data after the words being extracted.

Field No.	Field Name	Length	From	To	Data Type
71	County Land Use Description	45	1142	1186	A

Description: This field contains the literal land use description unique to each county assessment file, edited to ensure user-friendly terminology without losing regional or local reference.

The contents of this field are usually converted, along with the contents of (72), to the standardized land use codes found in (73).

When the source file(s) contain more than one type of land use data, use the most detailed. Use "land use" in favor of "property classification" or "zoning". Land use generally shows details of how the property is actually used, while property classification is a general, allowable category.

Sample Instruction:

Convert the contents of Property Type (19) according to the Land Use Conversion Table. Move the contents of (19) to County Land Use Code (72), the narrative description from the table to County Land Use Description (71), and the Standardized Use Code to Standardized Land Use Code (73).

Note that land use may vary among the records having the same parcel number. The land use noted on the primary record is established by how the property was first used historically, with other uses (noted on subsidiary records) coming later in time.

Field No.	Field Name	Length	From	To	Data Type
72	County Land Use Code	8	1187	1194	A

Description: This field contains the land use code used by the county for land use classification. These codes are usually numeric, but sometimes they are alphanumeric. The data in this field is left-justified.

The contents of this field are usually converted, along with the contents of (71), to the standardized land use codes found in (73).

Sample Instruction:

Convert the contents of Property Type (27) per the following table and make moves as indicated.

If (27) Contains	Standardized Land Use Code	Description
1000	1000	Residential
2000	2000	Commercial
3000	5000	Industrial
4000	7000	Agricultural
4500	7001	Hobby farm
7000	4000	Recreational
8nnn	8504	Centrally assessed
9000	9200	Government
9001	9202	Agricultural society
9002	9202	Horticultural society
9003	9203	School
9004	9101	Church
9005	9110	Charitable organization
9006	9108	Cemetery
9500	9200	Government

Move the contents of (27) to County Land Use Code (72).
Move the Standardized Land Use Code to Standardized Land Use Code (73).
Move the Description to County Land Use Description (71).

Field No.	Field Name	Length	From	To	Data Type
73	Standardized Land Use Code	4	1195	1198	N

Description: This field contains the Lexis-Nexis Standardized Land Use Code as found on the Land Use Code Conversion Table.

The contents of this field are the result of the conversion of the County's land use code, as reported in (71) and (72).

The standardized land use code "1999" is used to denote parcels that are presumed to be residential but which have no such designation in the source file. The use of this code is done on a county-by-county basis, as needed.

Personal property codes were added as 05xx in 2005.

Sample Instruction:

Convert the contents of Property Type (27) per the following table and make moves as indicated.

If (27) Contains	Standardized Land Use Code	Description
1000	1000	Residential
2000	2000	Commercial
3000	5000	Industrial
4000	7000	Agricultural
4500	7001	Hobby farm
7000	4000	Recreational
8nnn	8504	Centrally assessed
9000	9200	Government
9001	9202	Agricultural society
9002	9202	Horticultural society
9003	9203	School
9004	9101	Church
9005	9110	Charitable organization
9006	9108	Cemetery
9500	9200	Government

Move the contents of (27) to County Land Use Code (72).
Move the Standardized Land Use Code to Standardized Land Use Code (73).
Move the Description to County Land Use Description (71).

Field No.	Field Name	Length	From	To	Data Type
74	Timeshare Code	1	1199	1199	N

Description: If the property is a timeshare property, enter "Y" in this field: otherwise, leave blank.

Sample Instruction:

Convert the contents of Land Use Code (27) per the Land Use Codes Conversion Table and make moves as indicated.

For those records in which (27) = "108", also move "Y" to Timeshare Code (74).

Field No.	Field Name	Length	From	To	Data Type
75	Zoning	25	1200	1224	A

Description: This field contains the actual city zoning, unique to each incorporated area. The data may be narrative or coded.

Sample Instruction:

Move the contents of Zoning (29) to Zoning (75).

Field No.	Field Name	Length	From	To	Data Type
76	Lot Size or Area	14	1225	1238	A

Description: This field contains the total area measurement of the land. Depending on how this data is presented in the source file and on how large the parcel is, the contents of this field may be expressed in one or more of the following four ways:

Acreage	9(6).999"AC"	convert to square feet when < 1
Square feet	9(8)"SF"	convert to acres when  43,560
Dimensions	9999X9999	may convert to SF for rectilinear lots
Front feet	9999(.99)"FF"	(decimals OK)

If a lot size measurement is available in more than one format in the source file, use the above hierarchy to determine the best way to present it in the LAN-2 file.

There may be parcels that for various reasons are taxed at more than one rate: when such is the case, there may be more than one record for a single parcel, each record representing the land assessed at one tax rate. Acreage, land values (assessed or market), tax rate code areas, and land use may vary from one record to the next, within the same parcel of property. Whether the specific data is summed for a single parcel or treated as record-specific will vary from county to county.

Sample Instruction:

Move Lot Sq Ft (104) to Lot Size or Area (76), expressing as sq ft for values < 43,560 and as acres for values 43,560.

For those records in which (76) = [blank], eliminate leading zeros and move the contents of Lot Width (102) and Lot Depth (103), expressing the result in the format "nnnnXnnnn".

Move the contents of New Tot Acres (25) to Lot Size or Area (76), converting values < 1.00 to square feet. The data in (25) is formatted 9(7)V99.

Texas counties only - Whenever the county only provides lot size expressed in acreage and the acreage field has more than 3 decimal positions:

Lot size in square feet should be calculated for parcels that are less than an acre, so that the more accurate value in square feet can be moved to Field (76) and Field (131). For parcels where the lot size is 1 or more acres, the actual acreage value (exceeding 3 decimal positions) can be moved to Field (76) since this is not a numeric field; and square feet entered into Field (131) should be calculated using the county's actual acreage value.

In both cases, Field (152) Lot Size in Acres will be left BLANK, whenever the county value exceeds 3 decimal positions (not equal to zero) since we do not want to round or truncate the value.

Field No.	Field Name	Length	From	To	Data Type
77	Building Area	9	1239	1247	N

Description: This field contains the total square footage of improvements on the property and is valid for all types of improved land. Do not move values less than 100 or greater than 1,000,000 SF.

When there is more than one building on a parcel, there may be more than one card for that parcel. In such a case, building areas are not normally summed into one value.

In files where multiple building areas are given for a structure and for which the extended output record layout fields (LAN-2.2) are not used, the preferred data for this field is living area for residential structures and total area for all others. For all extractions, the type of area moved to output is coded in Building Area Code (111).

Sample Instruction:

Move the contents of Living Area (27) to Building Area (77).

For those records in which Ground Floor Area (62) > 0 and Story Height (46) = 1(.)0, move the contents of (62) to Building Area (77).

Field No.	Field Name	Length	From	To	Data Type
78	Year Built	4	1248	1251	N

Description: This field applies to all types of improvements. If the source file only contains "effective year built" or "year remodeled" for any record, that figure may be used.

Sample Instruction:

Move the data in the following source fields to the corresponding LAN-2 fields:
AYB (118) to Year Built (78) (ignore values = "1000" and any >"1996").
EYB (119) to Year Built (78) if (78) is not already populated (ignore values = "1000" and any greater than "1996").

Move the contents of Effective Age (26) to Year Built (78).

Strip leading zero and move Age-Dwell (29) to Year Built (78).

For those records in which Year Built (78) = [blank], strip leading zero from Remodel-Dwell (30), prefix the result with the string "19", and move to (78).

Field No.	Field Name	Length	From	To	Data Type
79	No of Buildings	3	1252	1254	N

Description: This field contains the total number of buildings or structures on a single parcel as reported in the Assessment Roll.

When a multiple-APN condition exists, this field will reflect the total number of buildings or structures on all records sharing the same APN. This total is not always the same as the total number of records: occasionally, records will be created for reasons other than to accommodate additional structures on the property.

Sample Instruction:

The highest contents of Building Number (59) for all records pertaining to a single parcel of property will be the number of buildings there are on the property. This number will not always be the same as the number of cards [as in (6)] for the parcel, as there may be unimproved areas which have their own cards.

For each parcel, move the highest contents of (59) to No. of Buildings (79).

Move the contents of New Tot Buildings (27) to No. of Buildings (79).

For records which have identical contents in (4), count the total number of records (including the MP) that also show an improvement value [Fair Market Bldg Value (14) > zero] and move this number to No. of Buildings (79).

Field No.	Field Name	Length	From	To	Data Type
80	No of Stories	5	1255	1259	A

Description: This field contains the number of stories for the main structure on the property, either as a numerical value as reported on the source file (1, 1.5, 2, 2.5, etc.) or as one of the following codes:

S/L	Split level	4/L	4 split levels	1+A	1 story with attic
B/L	Bi-level	3/L	3 split levels	1+B	1 story with basement
S/E	Split entry	S/F	split foyer	2+B	2 stories with basement

Other valid codes include any number followed by a "+" (1+, 2+, etc., to indicate reported fractional stories less than ½) and an attic/basement combination, as in 2+AB.

Sample Instruction:

Move Number Stories (128) to No of Stories (80) (ignore "0000" and note that the source field has an implied decimal).

Move the contents of Story Height (46) to No. of Stories (80). Field (46) is in the format 9V9.

Field No.	Field Name	Length	From	To	Data Type
81	No of Units	4	1260	1263	N

Description: This field is primarily used for reporting the number of units in apartment buildings: it may also be used to report the number of rooms in hotels and motels, the number of seats in theatres and auditoriums, etc., as reported on the Assessment Roll.

Sample Instruction:

Move the contents of Living Units (30) to No. of Units (81).

For those records in which Refinement Code (6) = "1BR", "2BR", "3BR", "EFF", or "SHR", move the contents of Number of Units (7) to No. of Units (81).

Field No.	Field Name	Length	From	To	Data Type
82	Total # Rooms	2	1264	1265	N

Description: This field contains the result of a physical room count. Counties will occasionally report hotel and motel capacity in terms of number of rooms, however, see (81) for reporting of this. Do not move values > 99.

Sample Instruction:

Move the contents of Total Rooms (50) to Total # Rooms (82).

Field No.	Field Name	Length	From	To	Data Type
83	No of Bedrooms	2	1266	1267	N

Description: This field contains the result of a physical bedroom (with closet) count for residential properties only. Do not move values > 20.

Sample Instruction:

Move the contents of Bedrooms (51) to No. of Bedrooms (83).

For records in which the subject property is a single-family residence (Use Code (18) = "01xx" or "6810"), process the data in Bdrm Bath Res/Comm/Apt (115) as follows:

Add the contents of bytes 1-3 and move to No of Bedrooms (83).

Field No.	Field Name	Length	From	To	Data Type
84	No of Baths	4	1268	1271	N

Description: This field contains the result of a physical bathroom count for residential properties only. Do not move values > 20.

The format for this data is 99v99. Decimal conversions of fractions are:

Full bath	1.00
¾ bath	.75
½ bath	.50
¼ bath	.25

Sample Instruction:

Move the contents of Full Baths (53) to No. of Baths (84).

For records in which the subject property is a single-family residence (Use Code (18) = "01xx" or "6810"), add the contents of bytes 4-6 in Bdrm Bath Res/Comm/Apt (115) and move to No of Baths (84).

Strip leading zeros and move Baths (102) to No. of Baths (84).

Field No.	Field Name	Length	From	To	Data Type
85	No of Partial Baths	2	1272	1273	N

Description: When given in the source file, residential partial bath counts are moved to this field. Do not move if > 20. If the county provides separate fields for Full & Partial baths, the physical count of full baths would be entered in Full Baths (84), and the physical count of partial baths (1/4, 1/2 & 3/4) would be entered in this Field.

Sample Instruction:

Move the contents of Half Baths (54) to Partial Bath Count (85).

For records in which the subject property is a single-family residence (Use Code (18) = "01xx" or "6810"), process the data in Bdrm Bath Res/Comm/Apt (115) as follows:

Add the contents of bytes 7-9 and move to Partial Bath Count (85).

Field No.	Field Name	Length	From	To	Data Type
86	Garage Type (Parking)	1	1274	1274	A

Description: The type of parking available on the property is converted per the table below and the resulting one-letter code moved to this field. Valid codes are:

A	Attached garage	N	None
B	Built-in	O	Open
C	Carport	P	Paved/surfaced
D	Detached garage	R	Ramp
E	Pole	S	Parking structure
F	Offsite	T	Tuckunder
G	Garage	U	Underground/basement
K	Unimproved	V	Covered
L	Parking lot	Y	Yes
M	Mixed

The default is [blank]

Sample Instruction:

There are eight groups of five fields each which detail information on additions made to the property: these groups begin with Add Lower 1 (80) and continue through Size 8 (119). Within each five-field group, we will only be interested in the first four fields: Add Lower (#), 1st Add (#), 2nd Add (#), and 3rd Add (3).

If any of these fields contains "FG", "MG", or "BG", move "Y" to Garage Type (86). If any of these fields contains "CP", move "C" to (86).

Field No.	Field Name	Length	From	To	Data Type
87	Garage - # of Cars	4	1275	1278	N

Description: This field contains the number of cars which the existing parking facilities can accommodate. When this data is available in the source file, it usually comes in one of two formats:

Count-	This is the actual count of the number of parking spaces available, and should be moved directly to this field.
SqFt-	This is the measure of the available parking area. Convert to "number of cars" count by estimating square-feet-per-car: 200 SF = 1 car; 400 SF = 2 cars, 720 SF = 3 cars, etc.

The following is the LAN-2 Standard to convert square feet to Number of Cars:
If garage-size is > 199 and < 400, move 1 to [87]
If garage-size is > 399 and < 720, move 2 to [87]
If garage-size > 719, compute [87] = 3 + rounded((garage-size - 720) / 320)
Check calculations with this link Garage Size Calculator

Sample Instructions:

Move Garage_Cars (15) to Garage Size [87] as follows:

If (15)	Then move
Contains	to [87]
2	2
3	3

If Detached Garage (72) is populated, move “D” to Garage Type [86] and populate Garage Size [87] according to the below formula:
1-Multiply the numbers separated by "X".
(72) =12X32
Multiply 12 and 32 = 384
(72) =12X40
Multiply 12 and 40 = 480
2-Calculate the product for number of cars per the LAN-2 Standard.
384 = 1 in [87]
480 = 2 in [87]
Convert Garage_SF (22) to Garage Size [87] per the LAN-2 Standard.
Examples:
(22) = 378
[87] = 1
(22)= 623
[87] = 2
When "M" is moved to Garage Type [86], convert all values in (22) and move the sum to [87].

Examples:
Parcel_Number (1) = 01-02-548-001
(22) = 545, which converts to 2 cars
Parcel_Number (1) = 01-02-548-001
(22) = 258, which converts to 1 car
[87] = 3
Please note that each value in the square feet field should be converted to number of cars before moving the sum to [87]. Summing the square feet values first, may result in error.

Field No.	Field Name	Length	From	To	Data Type
88	Pool	1	1279	1279	A

Description: This field indicates the presence or absence of swimming pools and spas, as this information is available from the source file. This field is only applicable to residential (SFR, condo, townhouse, PUD, duplex, apartments, etc.), hotel/motel property, etc.

The data in the source file is converted per the following table and the resulting code moved to this field:

A	Above ground pool	P	Pool (yes)
B	Pool and spa or hot tub (both)	S	Spa or Hot Tub (only)
H	Heated pool	C	Community pool or spa
L	Solar heated	I	Indoor swimming pool
V	Vinyl in-ground pool	E	Enclosed pool

Sample Instruction:

If Pool (28) = "Y", move "P" to Pool (88).

Inspect the XF Description (173), (185), (197), (209), (221), (233), (245), (257), (269), (281) fields and process as follows:

If any of these fields contain	Then move to (88)
"POOL/CON"	"P"
"POOL/VINYL"	"V"
"SPA/TUB"	"S"

If for any single record these fields are found to contain "SPA/TUB" and either "POOL/CON" or "POOL/VINYL", then move "B" to Pool (88).

If Notes (332) is found to contain the string "POOL" and if Pool (88) contains no data, move "P" to (88): if (88) contains "S", then overwrite (88) with "B".

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
89	Mail City, State & ZIP	50	1280	1329	A

Description: If the source file only contains an unparsed version of the assessed owner's mailing address, that address is moved to this field. If the source file breaks the address down, the address elements are moved each to its own individual field and also in concatenated form to this field.

Sample Instruction:

Populate MAIL CITY, STATE, ZIP [89] from MAIL CITY [31], MAIL STATE [32], MAIL ZIP [33] and MAIL ZIP+4 [34]. Ensure that [31], [32] and [33] are all present before moving to [89].
Anderson TX Ed 1
Do not populate Mail City/State/Zip [89] unless Mail City Name [31], Mail State [32] and Mail Zip Code [33] are all > blank.

Field No.	Field Name	Length	From	To	Data Type
90	FIPS Code	5	1330	1334	N

Description: The FIPS code is a five-digit numeric designation which is unique for each county in the country. The codes are assigned by the Department of Commerce and are available in Federal Information Processing Standards (FIPS) Publication 6-4.

Comparable codes will be used for Canada and other foreign countries.

Sample Instruction:

Move "42037" to FIPS Code (90).

Field No.	Field Name	Length	From	To	Data Type
91	Tape Cut Date	6	1335	1340	N

Description: This is the date on which our tape was generated from the source (county) database, if known. If the date is not known, we use the date we received the source file.

The date is provided so that our customers will have some idea of how current our information is.

The format is MMYYYY.

Sample Instruction:

Move "101997" to Tape Cut Date (91).

Field No.	Field Name	Length	From	To	Data Type
92	Census Tract	6	1341	1346	N

Description: Format 9999v99 (implied decimal)

Sample Instructions:

Unpack [VN31], if > 0, move to CENSUS TRACT. source field formatted as 9(4) packed. See dictionary for output format.

If DETAIL DESCR (5) begins with “CENSUS TRACT 2”, drop the text, remove the decimal and move the numbers to CENSUS TRACT [92]. Only move Census Tracts that begin with “2”.
Example: (5) = “CENSUS TRACT 2019.01” converts to [92] = “201901”.
Alexandria City VA Ed 13

Field No.	Field Name	Length	From	To	Data Type
93	Record Type	2	1347	1348	A

Description: This field contains a code which identifies the type of ownership for each parcel. The valid codes are:

EM	Easement
LH	Leasehold
MH	Mobile home
MI	Mineral rights
MR	Multi-account record *
PP	Personal property
SR	Surface rights
TM	Timber rights

*	Our online data will contain the following disclaimer for these records: The values indicated in this record are the sum of multiple parcels associated with the owner's account.

The valid codes for the duplicate APN routine are:

MO	Multiple owner
DR	Duplicate record (drop from online)
MP	Master parcel (for which duplicate records have been dropped) **
MA	Multiple addresses
SP	Split parcel

**	Our online data will contain the following disclaimer for these records: This assessment property record has been compiled from only one (1) of several improvement records as reported by the county. Therefore, the physical description of the property is incomplete.

Sample Instruction:

The leasehold indicator (byte positions 16-18) is normally zero. Leasehold numbering begins at 025 in this sub-field and continues sequentially as far as necessary to accommodate the number of leaseholds present. If the vesting is shown to be a leasehold (i.e.; if the contents of bytes 16-18 > 0), move "LH" to Record Type (93).

NOTE (info only): The county will typically tax a leasehold separately from the underlying real property even though the two are owned by the same person. Mobile homes are taxed as real property.

Field No.	Field Name	Length	From	To	Data Type
94	Market Value: Land	10	1349	1358	N

Description: This field contains the market value of the land only. The data may be available from one of three possible sources:

A)	A statement of the market value of the land in the source file
B)	The appraised value of the land, as stated in the source file
C)	The sale price (only if unimproved property and the price reported in the source file is the full price paid)

Note that for (B) and (C), the market value of the property will be tied to a year – either the appraisal year or the year of sale – which will be moved to Market Value Year (97).

Sample Instruction:

Populate Market Value Land (94) from the first of the following source fields found to have data:

Over Land (179)
Farm Land (178)
Incm Land (177)
CALP Land (176)

Move the contents of Fair Market Land Value (12) to Market Value Land (94).

Multiply the contents of Last Yr Land Val (63) by .35 and move the result to Market Value Land (94).

Field No.	Field Name	Length	From	To	Data Type
95	Market Value: Improvement	10	1359	1368	N

Description: This field contains the market value of the improvements only. The data may be available from one of three possible sources:

A)	A statement of the market value of the improvements in the source file
B)	The appraised value of the improvements, as stated in the source file
C)	The sale price (only if ownership of the underlying land is different and the price reported in the source file is the full price paid)

Note that for (B) and (C), the market value of the property will be tied to a year – either the appraisal year or the year of sale – which will be moved to Market Value Year (97).

Sample Instruction:

Populate Market Value Land (94) from the first of the following source fields found to have data:

Over Land (179)
Farm Land (178)
Incm Land (177)
CALP Land (176)

Move the contents of Fair Market Bldg Value (14) to Market Value Improvement (95).

Field No.	Field Name	Length	From	To	Data Type
96	Total Market Value	11	1369	1379	N

Description: This field contains the total market value of the parcel, including land, improvements, and future farm productivity, and any other component set forth in the source file as being part of total value.

Note that the market value of the property will be tied to a year – either the appraisal year, the year of revaluation or the year of sale – which will be moved to Market Value Year [97].

Sample Instruction:

Sum Market Value Land [94] and Market Value Improvement [95] and move the result to Total Market Value [96].

Move BLD_AND_LAND_MKT_TOTAL (27) to Total Market Value [96] and “2003” to Market Value Year [97].
NOTE: Florence revaluates property every 5 years the last being done in 2003.
Florence SC Ed 4

Field No.	Field Name	Length	From	To	Data Type
97	Market Value Year	4	1380	1383	N

Description: This field contains the year that the market value of the property was established. Normally, this is a constant year for all records with a market value > zero, although there are cases in which the county file contains the year each parcel was physically appraised. In such cases we move the market value year specific to each parcel, resulting in several different values per county.

Sample Instruction:

Move "2008" to Market Value Year [97].

Move BLD_AND_LAND_MKT_TOTAL (27) to Total Market Value [96] and “2003” to Market Value Year [97].
NOTE: Florence revaluates property every 5 years the last being done in 2003.
Florence SC Ed 4

Field No.	Field Name	Length	From	To	Data Type
98	Building Class	1	1384	1384	A

Description: This field contains the Fire Insurance Building Classification Code used for commercial and industrial buildings. The valid codes are:

A	Buildings having fireproofed structural steel frames carrying all wall, floor and roof loads. Wall, floor and roof structures are built of non-combustible materials.
B	Buildings having fireproofed reinforced concrete frames carrying all wall floor and roof loads which are all non-combustible.
C	Buildings having exterior walls built of a non-combustible material such as brick, concrete, block or poured concrete. Interior partitions and roof structures are built of combustible materials. Floor may be concrete or wood frame.
D	Buildings having wood or wood and steel frames.
S	Specialized buildings that do not fit in any of the above categories.

Note that these codes are a building industry standard and that consequently, most counties that give this information will use the above codes without conversion.

Sample Instruction:

Move Structure Class 1 (159) to BUILDING CLASS.

Field No.	Field Name	Length	From	To	Data Type
99	Style	1	1385	1385	A

A	A-Frame	X	Custom	Y	Log Cabin/ Rustic	J	Ranch\Rambler
B	Bungalow	S	Dome	Q	Mansion	K	Spanish
C	Cape Cod	E	English	M	Mediterranean	2	Traditional
D	Colonial	F	French Provincial	I	Modern	L	Tudor
N	Conventional	G	Georgian	U	Unfinished/Under Construction	O	Other
T	Contemporary	H	Highrise	P	Prefab, Modular
W	Cottage	Z	Historical	R	Raised Ranch	V	Victorian

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
100	Type Construction	1	1386	1386	A

Description: This field contains a single-letter code telling the type of construction used in the primary improvement on the property. This information is not always available in the source file.

Valid codes are:

A	Adobe	H	Heavy	Q	Metal
B	Brick	L	Light	R	Steel
C	Concrete	M	Log	S	Stone
D	Concrete block	N	Manufactured	T	Tilt-up (pre-cast concrete)
E	Dome	X	Mixed	W	Wood
F	Frame	P	Masonry	O	Other

Sample Instruction: (NOTE that this instruction is in error. This instruction converts data that should be moved directly without conversion to Building Class (98). The example does show the general idea of converting source codes to valid content for this field.)

Populate Type Construction (100) from Structure Class 1 (159) as follows:

If (159) Contains	Which means	Then move to (100)
A	Fireproofed steel	R
B	Reinforced concrete	C
C	Masonry wall-bearing	P
D	Wood framed	W
S	Pre-engineered steel	R

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
101	Exterior Walls	1	1387	1387	A

Description: This field contains a single-letter code telling the type of exterior walls used in the primary improvement on the property. This information is not always available in the source file.

Valid codes are:

T	Adobe	G	Concrete block	S	Siding (alum/vinyl)
A	Asbestos shingle	H	Glass	L	Stucco
B	Brick	I	Log	M	Tile
C	Brick Veneer	Y	Masonry	N	Tilt-up (pre-cast concrete)
D	Block	J	Metal	W	Marble
F	Concrete	V	Shingle (not wood)	P	Wood shingle
E	Composition	K	Rock, stone	Q	Wood
R	Wood siding	O	Other	X	Combination

Sample Instruction:

Convert Ext Wall 1 (104) per the following table and move to Exterior Walls (101).

If (104) contains	Which means	Move	If (104) contains	Which means	Move
1	Siding minimum	S	15	Board & batten	Q
2	Corrugated metal	J	16	Wood shingle/log	P
3	Composition/wallboard	E	17	Cedar/redwood siding	R
4	Single siding	S	18	Siding maximum	S
5	Asbestos shingle	A	19	Utility brick	B
6	Board & batten	Q	20	Common brick	B
7	Corrugated asbestos	O	21	Face brick	B
8	Masonite	O	22	Stone	K
9	Wood	Q	23	Corrugated metal	J
10	Aluminum/vinyl	S	24	Prefab metal	J
11	Concrete block	G	25	Reinforced concrete	F
12	Stucco on conc block	L	26	Precast panel	N
13	Stucco on tile or wood	L	27	Prefinished metal	J
14	Siding average	S	28	Glass/thermopane	H

For those records in which (101) contains no data after this step and Ext Wall 2 (105) contains data, convert (105) per the above table to further populate (101).

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
102	Foundation	1	1388	1388	A

Description: This field contains a single-letter code telling the type of foundation found in the primary improvement on the property. This information is not always available in the source file.

Valid codes are:

A	Concrete	T	Footing	L	Pilings
K	Concrete block	D	Masonry	R	Retaining wall
B	Crawl/raised	F	Mud sill	S	Slab
C	Crossed walls	W	Wood	G	Stone
E	Earth	P	Piers	O	Other

Sample Instruction:

Process the data in Foundation (72) to populate Foundation (102) as follows:

If (72) Contains	Which means	Then move to (102)
1	Concrete walls	A
2	Cement block walls	K
3	Brick walls	O
4	Stone walls	G
5	Piers	P
6	Other	O

Other values may be ignored.

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
103	Roof Cover	1	1389	1389	A

Description: This field contains a single-letter code telling the type of roof cover found in the primary improvement on the property. This information is not always available in the source file.

Valid codes are:

L	Aluminum	G	Gravel/rock	F	Slate
B	Built Up	I	Bermuda	T	Tile
A	Asbestos	Y	Gypsum	S	Steel
P	Asphalt	J	Masonite/cement shake	H	Tar & gravel
C	Composition	E	Metal	U	Urethane
Shingle	K	Fiberglass	W	Wood
D	Concrete	R	Roll composition	M	Wood shake/shingle
V	Shingle (not wood)	O	Other

Sample Instruction:

Convert Rf Cover (107) per the following table and move to Roof Cover (103).

If (107) contains	which means	Move to (103)	If (107) contains	which means	Move to (103)
1	Minimum roofing	O	7	Concrete/clay tile	D
2	Rolled composition	R	8	Cedar shake	M
3	Asphalt/comp shingle	C	9	Enamel metal/copper	E
4	Tar & gravel	H	10	Wood shingle	M
5	Rubber	U	11	Slate	F
6	Asbestos shingle	A	12	Metal	E

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
104	Heating	1	1390	1390	A

Description: This field contains a single-letter code telling the type of heating system found in the primary improvement on the property. This information is not always available in the source file.

Valid codes are:

A	Baseboard	H	Heat pump	T	Solar
C	Central	J	Hot water	R	Space/suspended
Q	Coal	N	None	P	Steam
B	Electric	E	Oil	V	Vent
D	Forced air	I	Geo-Thermal	W	Wood burning
F	Floor/wall	L	Partial	Y	Yes
K	Gas	X	Propane	Z	Zone
G	Gravity	M	Radiant	S	Convection

O Other

Sample Instruction:

If Heat 1 (161) >5, move "Y" to Heating (104).

Convert the contents of Heat System (67) as follows and move the result to Heating (104):

If (67) contains	Then move to Heating (104)
ELECTRIC	B
HEAT PUMP	H
HOT WATER	J
NONE	N
SOLAR	T
WARM AIR	D

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
105	Air conditioning	1	1391	1391	A

Description: This field contains a single-letter code telling the type of air conditioning system found in the primary improvement on the property. This information is not always available in the source file.

Valid codes are:

C	Central	F	Office only	V	Ventilation
Q	Chilled water	I	Geo-Thermal	W	Wall
E	Evaporative cooler	P	Partial	L	Window/unit
N	None	R	Refrigeration	Y	Yes
K	Packaged Unit	O	Other

Sample Instruction:

Convert AC Type (114) per the following table and move to Air Conditioning (105).

If (114) Contains	which means	Then move to (105)
1	None	N
2	Wall unit	W
3	Central	C
4	Packaged rooftop	E
5	Chilled water	Q

If AC 1 (162) >5, move "Y" to Air Conditioning (105).

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
106	Elevator	1	1392	1392	A

Description: This field contains the actual number of elevators (if available) or one of the following:

Y	Yes
E	Escalator
N	No

The default for this field is [blank].

Sample Instruction:

There are eight sets of two fields each that detail extra features of the property. These are Feature Type 1 (43), Feature Type 2 (45) … Feature Type 8 (57). Convert the contents of these fields and make moves to (106) as follows:

If any of these fields contain	Then move
ELEV* [* = wild card]	Y
ESCALATOR*	E

Field No.	Field Name	Length	From	To	Data Type
107	Fireplace	1	1393	1393	A

Description: This field contains the actual number of fireplaces (if available) or "Y" for Yes. The default for this field is [blank].

A source file will sometimes include faux (fake) fireplaces in the total count.

Sample Instruction:

Convert Fireplace Flag (120) per the table below and move result to Fireplace (107):

If (120) =	"1"	move	"N".
"2", "5", or "7"	move	"Y".
"3" or "6"	move	"1".
"4"	move	"2".

Strip leading zeros and move Fireplace (101) to Fireplace (107). For those records in which the value of (101) >0 and the value of FPStacks (100) = "0", move "0" to (107).

If the contents of Frplc Stacks (58) > 0, move "Y" to Fireplace (107).

Move the contents of Frplc Open (59) to Fireplace (107). Overwrite as needed.

Field No.	Field Name	Length	From	To	Data Type
108	Basement	1	1394	1394	A

Description: This field contains a single-letter code telling the type of basement found in the primary improvement on the property. This information is not always available in the source file.

Valid codes are:

P	Partial basement	Y/B	Basement (not specified)
F	Full basement	L	Daylight, partial
D	Daylight, full	U	Unfinished basement
I	Improved basement (finished)	N	No basement

Sample Instruction:

Convert the contents of Basement (64) and move as indicated:

If (64) contains	Then move to Basement (108)
CRAWL	N
FULL	F
NONE	N
PART	P

If Finbsmt (74) contains "1", "2", or "3", move "P" to Basement (108). If (74) contains "4", move "F" to (108).

Field No.	Field Name	Length	From	To	Data Type
109	Edition number	2	1395	1396	N

Description: This field contains the numerical edition, beginning with "01".

Sample Instruction:

Move "01" to Edition Number (109).

Field No.	Field Name	Length	From	To	Data Type
110	Country Code	3	1397	1399	N

Description: The country code of the parcel. Defaults to 'blank' for the United States and Virgin Islands. Canada is country code '001'. Additional codes will be added in the future, as needed.

Sample Instruction:

Move "001" to Country Code (110).

Field No.	Field Name	Length	From	To	Data Type
111	Building Area Indicator	1	1400	1400	A/N

Description: Identifies the value moved to BUILDING AREA [77]. Some examples are living area, basement area, 1st floor area. When a county provides multiple areas, the preferred value to move to BUILDING AREA [77] is Living Area.

When the source files contain other types of areas, these can be specified in the seven pairs of "Building Area" and "Building Area Indicator" fields numbered 133-146.

1	First floor
B	Base
E	Heated
J	Adjusted
K	Finished
L	Living
M	Perimeter
R	Gross
T	Total

Sample Instruction:

Move live_fsqft (11) to Building Area [77]. If Standard Land Use Code [73] = “10xx” then move “L” to Building Area Ind [111] else move “T”.

Field No.	Field Name	Length	From	To	Data Type
112-123	[filler]	1	1401	1472	N/A

Field No.	Field Name	Length	From	To	Data Type
124	Assessee(Owner) Name Ind.	1	1473	1473	A
125	2nd Assessee(Owner) Name Ind.	1	1474	1474	A
126	Mail Care-Of Name Indicator	1	1475	1475	A

Description: Lan2.2 fields 124-126 are used to indicate the predominate pattern of names for lan2 fields 18, 19, & 22 respectively.

[124] will not be populated if Owner Name [18] is "Not Available from the County". If 2nd Owner Name [19] and/or Mail Care-of Name [22] are blank [125] and/or [126] will also be blank.
Valid codes are:
1 = fielded as First Name Middle Initial Last Name - from a single source field
2 = fielded as Last Name, First Name Middle Initial. - from a single source field
3 = fielded as last name, first name middle initial. - from separate source fields
N = No pattern to names

Sample Instructions:

Move "2" to Assessee(Owner) Name Ind [124].
When 2nd Owner Name [19] is populated move "2" to 2nd Assessee(Owner) Name Ind [125].
When Mail Care-of Name [22] is populated "1" to Mail Care-Of Name Indicator [126].
Inyo CA Ed 16

Field No.	Field Name	Length	From	To	Data Type
127	Assessee(Owner) Name Type	1	1476	1476	A
128	2nd Owner Name Type	1	1477	1477	A
129	Mail Care Of Name Type	1	1478	1478	A

Description: Indicate whether the names associated with a parcel are individuals, businesses, or government.

B	Business
G	Government
I	Individual

Field No.	Field Name	Length	From	To	Data Type
130	Certification Date	8	1479	1486	N

Description: The date that the file was certified by the County. This date will be provided by LA.

Sample Instructions:

Move "01012009" to Certification Date [130].

Field No.	Field Name	Length	From	To	Data Type
131	Lot Size - Square Feet	9	1487	1495	N

Description: This field contains the total area measurement of the land in square feet. If the lot size is provided by the county assessor in acres, this field will be show the conversion to square feet.
This field should be expressed numerically with no implied decimal 9(9).
This field will contain the area in Square Feet only as opposed to Lot Size [76] which can be populated several different ways. Click on the link for the differences.

TEXAS counties only - Whenever the county only provides lot size expressed in acreage and the acreage field has more than 3 decimal positions: Lot size in square feet should be calculated for parcels that are less than an acre, so that the more accurate value in square feet can be moved to Lot Size (76) and Lot Size-Square Feet (131). For parcels where the lot size is 1 or more acres, the actual acreage value (exceeding 3 decimal positions) can be moved to Field (76) since this is not a numeric field; and square feet entered into Field (131) should be calculated using the county's actual acreage value. In both cases, Lot Size-Acres (152) will be left BLANK, whenever the county value exceeds 3 decimal positions (not equal to zero) since we do not want to round or truncate the value.

Sample Instructions:

Move Lot Sq Ft (104) to Lot Size or Area [76], expressing as sq ft for values < 43,560 and as acres for values 43,560.
A) Move Lot Sq Ft (104) to Lot Size - Square Feet [131] as is.

Move the contents of New Tot Acres (25) to Lot Size or Area (76), converting values < 1.00 to square feet. The data in (25) is formatted 9(7)V99.
A) Convert New Tot Acres (25) to Square Feet and move the result to Lot Size - Square Feet [131].

Field No.	Field Name	Length	From	To	Data Type
132	Building Quality	2	1496	1497	A

Description: This field contains a code reflecting the quality of a building. Usually comes as a grade from the county.
The following are valid grades translated from those codes provided by the County:
A
A-
A+
B
B-
B+
C
C-
C+
D
D-
D+

E

E-

E+

Field No.	Field Name	Length	From	To	Data Type
133	Floor Cover	2	1498	1499	A

Description: This field contains a code reflecting the type of flooring used in improvements on the property.
2 Codes can be moved to this field. The following table is listed in order of priority. If 3 or more floor coverings are provided by the county, move the highest priority code to the first byte and "X" to the second byte.

Valid Codes:

G	Granite
F	Floating Floor/Laminate (i.e. Pergo)
M	Marble
N	Stone
Q	Parquet
R	Ceramic
S	Slate
T	Tile
W	Finished Wood (previously coded as just ‘wood”)
Z	Terrazzo
P	Carpet
C	Concrete
B	Brick
V	Vinyl
L	Linoleum
E	Covered
A	Asbestos
H	Cork
D	Dirt/Earth/Soil
I	Plywood
X	Combination

NOTE: If the county provides a percent of the floor covering, give priority to the covering with the highest percentage. If percentages are equal the table is listed by priority.
Example:
Floor1 Type (33) = Carpet
Floor1 Pct (34) = 70
Floor2 Type (35) = Marble
Floor2 Pct (36) = 15
Floor3 Type (37) = Wood
Floor3 Pct (38) = 15
Floor4 Type (39) =
Floor4 Pct (40) =
Floor Cover [133] = PM

Sample Instructions:

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
134	# of Plumbing Fixtures	3	1500	1502	N

Description: This is a numerical field identifying the number of plumbing features reported by the county assessor in the primary building/improvement on the property.

Sample Instructions:

Move number_fixtures (38) to # of Plumbing Fixtures [134].

Field No.	Field Name	Length	From	To	Data Type
135	Building Area 1	8	1503	1510	N
136	Building Area 1 Indicator	2	1511	1512	A/N
137	Building Area 2	8	1513	1520	N
138	Building Area 2 Indicator	2	1521	1522	A/N
139	Building Area 3	8	1523	1530	N
140	Building Area 3 Indicator	2	1531	1532	A/N
141	Building Area 4	8	1533	1540	N
142	Building Area 4 Indicator	2	1541	1542	A/N
143	Building Area 5	8	1543	1550	N
144	Building Area 5 Indicator	2	1551	1552	A/N
145	Building Area 6	8	1553	1560	N
146	Building Area 6 Indicator	2	1561	1562	A/N
147	Building Area 7	8	1563	1570	N
148	Building Area 7 Indicator	2	1571	1572	A/N

Description: Allow for identifying building area for up to seven building features, such as garage, porch, basement. The area of the feature moves to Building Area and a two-digit code describing the feature moves to Building Area Indicator. Do not move dimensional areas to the area fields. Calculate Square Feet and move that value. Do not populate an Indicator field if no value can be moved to an area field.

The first byte of Building Area Indicator represents the feature (basement, garage, attic) and the 2nd byte indicates whether the feature is finished or unfinished. The 2nd byte is optional and will only be used where the county identifies features as finished or unfinished. The second byte may also be used if the county specifies the type of porch (open, enclosed, screened).

For counties that provide more than seven (7) Building Area values, we have separated the areas into Primary and Secondary Areas, with a priority sequence for each grouping. This will insure that we capture the most significant areas before running out of space.

First Byte	PRIMARY BUILDING AREAS-Should be moved in order of priority, before proceeding to the Secondary building areas 1-9 = Floor # Y = HALF STORY (3/4 Story) B = BASE U = UPPER STORY W = LOWER/BASEMENT A = ATTIC L = LIVING E = HEATED J = ADJUSTED I = EFFECTIVE K = FINISHED T = TOTAL R = GROSS M = PERIMETER SECONDARY BUILDING AREAS G = GARAGE C = CARPORT PG = PORCH-GLASS ENCLOSED** PE = PORCH-ENCLOSED** PC = PORCH-COVERED** PS = PORCH-SCREENED** PO = PORCH-OPEN** P = PORCH/STOOP** H = CHATAHOOCHIE (PORCH)** PR = PORTICO (DRIVE UNDER) N = CANOPY/AWNING BZ = BREEZEWAY D = BALCONY/OVERHANG F = LOFT GX = Garage Apartment FG = LOFT-GARAGE V = LOBBY/VESTIBULE Z = MEZZANINE O = OFFICE Q = MANUFACTURING X = APARTMENT (Can also be used as “1X,2X,3X etc.. to indicate floor areas) S = UTILITY/STORAGE Room** Helpful Definitions: Canopy - A protective roof-like covering, often of canvas, mounted on a frame over a walkway or door. Awning - A roof-like structure, often made of canvas or plastic, that serves as a shelter, as over a storefront, window, door, or deck. Breezeway - A roofed, open-sided passageway connecting two structures, such as a house and a garage. Balcony - a balcony is suspended over an open space (think of the Pope speaking at the Vatican or Mardi Gras revelers in New Orleans). A balcony would be on an upper floor **Attached to main structure only
Second Byte	F = FINISHED U = UNFINISHED

Example: A residential parcel with heated area of 1234, garage area of 567, finished basement area of 454 and unfinished basement area of 780 would be moved as follows.

Building Area 1	1234
Building Area 1 Indicator	E
Building Area 2	567
Building Area 2 Indicator	G
Building Area 3	454
Building Area 3 Indicator	WF
Building Area 4	780
Building Area 4 Indicator	WU

Sample Instructions:

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
149	Effective Year Built	4	1573	1576	N

Description: The date that reflects the condition of an improvement. It is the same or later than Year Built.
NOTE: If the county does not provide the effective year built, use remodel year.

Sample Instructions:
Move Remodel Year (63) to Effective Year Built [149].

Field No.	Field Name	Length	From	To	Data Type
150	Heating Fuel Type	1	1577	1577	A/N

Description: The type of heating fuel (oil, gas, solar). Some counties may also provide a heating system type, which moves to Heating [104].

N	None
O	Oil
G	Gas
S	Solar
E	Electric
C	Coal
W	Wood
P	Propane
I	Geo-Thermal

Sample Instructions:

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
151	Air Conditioning Type	1	1578	1578	A/N

Description: The type of air conditioning. Some counties may also provide an air conditioning method or system, which moves to Air Conditioning [105].

W	Chilled Water
C	Evaporative Cooler
R	Refrigeration
V	Ventilation
I	Geo-Thermal

Sample Instructions:

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
152	Lot Size - Acres	10	1579	1588	N

Description: This field contains the total area measurement of the land in acres. If the lot size is provided by the county assessor in square feet, this field will contain a conversion of square feet to acres.
This field should be expressed numerically with an implied decimal of 3 (7v3).
This field will contain the area in Acres only as opposed to Lot Size [76] which can be populated several different ways. Click on the link for the differences.

TEXAS counties only - Whenever the county only provides lot size expressed in acreage and the acreage field has more than 3 decimal positions: Lot size in square feet should be calculated for parcels that are less than an acre, so that the more accurate value in square feet can be moved to Lot Size (76) and Lot Size-Square Feet (131). For parcels where the lot size is 1 or more acres, the actual acreage value (exceeding 3 decimal positions) can be moved to Field (76) since this is not a numeric field; and square feet entered into Field (131) should be calculated using the county's actual acreage value. In both cases, Lot Size-Acres (152) will be left BLANK, whenever the county value exceeds 3 decimal positions (not equal to zero) since we do not want to round or truncate the value.

Sample Instructions:

Move Lot Sq Ft (104) to Lot Size or Area [76], expressing as sq ft for values < 43,560 and as acres for values 43,560.
A) Convert Lot Sq Ft (104) to acres and move the result Lot Size - Acres [152].

Move the contents of New Tot Acres (25) to Lot Size or Area (76), converting values < 1.00 to square feet. The data in (25) is formatted 9(7)V99.
A) Move New Tot Acres (25) to Lot Size - Acres [152].

Field No.	Field Name	Length	From	To	Data Type
153	Mortgage Lender Name	40	1589	1628	A/N

Description: The name of the company or individual that holds the mortgage, as provided by the County Assessor.

Sample Instructions:

Field No.	Field Name	Length	From	To	Data Type
154	Interior Walls	1	1629	1629	A

Description: This field contains a code reflecting the composition of the interior walls.
Valid codes are:

G	Gypsum Board/Drywall/ Sheetrock	M	Cement Board
B	Brick	U	Unfinished
S	Stone	W	Wood
C	Concrete	P	Plaster
L	Log	T	Metal
D	Block	E	Glass
N	Composition	F	Finished/Painted
R	Paneling	V	Vinyl
H	Decorative/Custom	I	Masonry
Y	Minimum/Plywood	O	Other

Sample Instructions:

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
155 156 157 158 159 160	School/Tax District 1 School/Tax District Ind. 1 School/Tax District 2 School/Tax District Ind. 2 School/Tax District 3 School/Tax District Ind. 3	15 1 15 1 15 1	1630 1645 1646 1661 1662 1677	1644 1645 1660 1661 1676 1677	A/N A/N A/N A/N A/N A/N

Description: Identifies school and/or tax districts. These fields will be used in different ways, depending on the data provided by the county. If the county provides three or fewer districts, the School/Tax District field will contain the name or description of the district, and an identifying code will move to School/Tax District Indicator. If there are multiple districts, as in many Texas counties, as many districts as possible will move to the three school/tax district fields.

The following are listed in order of priority:

S	School
T	Tax
F	Fire
N	Sanitation
C	Conservation
D	Drainage
R	Transportation
W	Waste Management
M	Municipality
A	Water
H	Historical
L	Special Services
P	Public Improvement
U	Utility
X	Miscellaneous

Sample Instructions:

Move current school district (5) to School/Tax Dist 1 [154] and “S” to School/Tax Dist 1 Ind [155].

Calhoun MI Ed 2

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
161	Site Influence	2	1678	1679	A

Description: Identifies features or characteristics of a location which might influence the value or desirability of a parcel, such as waterfront or traffic patterns. The field can contain up to two codes.

A	Freeway Proximity
B	Waterfront-Beach(Ocean, River or Lake)
C	Contamination site
D	Cul-de-sac
E	Corner
F	Negative View (poor, bad, etc)
G	Average View
H	Historical
K	No View (not a default, this is when (if) the county clearly states that the parcel has no view)
L	Lake View
M	Mountain View
N	Waterfront-Canal
O	Ocean View
P	Airport Proximity
R	Railroad Proximity
S	Major Street/Thoroughfare
T	High traffic area
U	River View
V	View-not specified
W	Waterfront-not specified
J	Adjacent to Golf course (specific to when the assessor refers to land use or site influence as “golf course”)
Z	Flood Plain/Flood Zone
Q	Green Belt
I	School Proximity

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
162	Amenities	5	1680	1684	A

Description: Identifies the extra selling features that add to the value of property, such as a tennis court or golf course. This data is provided by the county, but typically does not indicate the size of the Amenity. This field can contain up to five codes.

If more than 5 codes are available see Amenities 2 [170]. Up to five more codes can be moved to this field.
The valid codes, in the order of priority are as follows:

R	RV Parking
G	Golf Course/Green
B	Boat dock/Ramp/Slip
J	Boat Lift/Davits
T	Tennis court
C	Clubhouse
A	Alarm System
V	Central Vacuum System
S	Automatic Sprinkler System (irrigation)
Q	Handicap Ramp/Accessible
E	Intercom System
I	Fire Sprinkler System
N	Wine Cellar
D	Wet Bar
H	Audio Sound System
K	Outdoor Kitchen/Fireplace
L	Storm or Tornado Shelter/Cellar
X	Storm/Security Shutters
F	Safe Room/Panic Room
U	Overhead Door
2	Mobile Home Hookup
W	Water Feature
Y	Koi Pond
1	Arbor/Pergola
O	Basketball/Sport Court
3	Sauna/Steam Room

Sample Instruction:

MATCH XTRA FEATURE NAME (3) TO THE FOLLOWING TABLE, IF MATCH MOVE CODE TO AMENITIES [162]. STRING 'B' AND 'T' IF BOTH FOUND.

INPUT	CODE
DOCKWWP	B
DOCKWCP	B
TENCTAP	T
TENCTCL	T
TENCTCO	T

Broward FL Ed 10

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
163	OTHER IMPR BLDG IND 1	2	1685	1686	A
164	OTHER IMPR BLDG IND 2	2	1687	1688	A
165	OTHER IMPR BLDG IND 3	2	1689	1690	A
166	OTHER IMPR BLDG IND 4	2	1691	1692	A
169	OTHER IMPR BLDG IND 5	2	1722	1723	A

Description: These fields are defined as buildings not attached to the main building/house and other improvements as designated including: Wood Deck, Patio Screened, Patio, Pool Size and Loading Platform. The size or measurement of these will be indicated in Other Impr Bldg Area [171-5] when provided by the county.
The valid codes, in the order of priority are as follows:

V	Pool Size (see Pool [88] for Pool Code)
N	Patio-Screened
T	Patio
TR	Terrace
D	Wood Deck
W	Synthetic Deck
L	Stable
A	Barn
AR	Arena
S	Storage Bldg
E	Shed
U	Utility Bldg
SP	Shop/Workshop
HG	Hangar
F	Boathouse/Boat storage
G	Greenhouse
H	Pool House/Cabana
B	Bath house
Z	Gazebo
PA	Pavilion
K	Kennel
C	Cabin/Cottage
X	Guest House
J	Lean-to
Q	Quonset
R	Granary/Grain Bin
I	Silo
Y	Loading Platform
HH	Hog House
M	Milkhouse/Milking Parlor
PH	Pump House/Well House
O	Pole Structure
P	Poultry house

Sample Instruction:

Inspect imprv_det_type_cd (5) for the codes using table below and make moves to Other Buildings [162].

Code (5)	Move to [163]
STG	S
SH	D
SA	S
PB	O
Begins with "MB"	S
GR	G
BN	A

Lamar TX Ed 3

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
167	Neighborhood Code	9	1693	1701	A/N

Description: Indicates the neighborhood or geographic area of a parcel. This is a county-provided code. More information can be found at the following link: Neighborhood Codes

Sample Instructions:

Move NEIGHBORHOOD (18) to Neighborhood Code [163].
Miami-Dade FL Ed 15

Field No.	Field Name	Length	From	To	Data Type
168	Condo Project/Building Name	20	1702	1721	A/N

Description: The name of a condominium building or complex and/or building name or complex.

Field No.	Field Name	Length	From	To	Data Type
170	Amenities 2	5	1724	1728	A

Description: If more than five codes can be moved to Amenities [162] use this field for up to five additional codes.

The valid codes, in the order of priority are as follow:

R	RV Parking
G	Golf Course/Green
B	Boat dock/Ramp/Slip
J	Boat Lift/Davits
T	Tennis court
C	Clubhouse
A	Alarm System
V	Central Vacuum System
S	Automatic Sprinkler System (irrigation)
Q	Handicap Ramp/Accessible
E	Intercom System
I	Fire Sprinkler System
N	Wine Cellar
D	Wet Bar
H	Audio Sound System
K	Outdoor Kitchen/Fireplace
L	Storm or Tornado Shelter/Cellar
X	Storm/Security Shutters
F	Safe Room/Panic Room
U	Overhead Door
2	Mobile Home Hookup
W	Water Feature
Y	Koi Pond
1	Arbor/Pergola
O	Basketball/Sport Court
3	Sauna/Steam Room

Sample Instruction:

MATCH XTRA FEATURE NAME (3) TO THE FOLLOWING TABLE, IF MATCH MOVE CODE TO AMENITIES [162]. STRING 'B' AND 'T' IF BOTH FOUND.

INPUT	CODE
DOCKWWP	B
DOCKWCP	B
TENCTAP	T
TENCTCL	T
TENCTCO	T

Broward FL Ed 10

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
171 172 173 174 175	OTHER IMPR BLDG AREA 1 OTHER IMPR BLDG AREA 2 OTHER IMPR BLDG AREA 3 OTHER IMPR BLDG AREA 4 OTHER IMPR BLDG AREA 5	9 9 9 9 9	1729 1738 1747 1756 1765	1737 1746 1755 1764 1773	A/N A/N A/N A/N A/N

Description: Contains the measurements of their respective Buildings and Improvements described in Other Impr Bldg Ind [163-9]. This value will usually be square feet, but may be given as dimensions.

Sample Instruction:

Inspect imprv_det_type_cd (5) for the codes using table below and make moves to Other Buildings [162].

Code (5)	Move to [163]
STG	S
SH	D
SA	S
PB	O
Begins with "MB"	S
GR	G
BN	A

Lamar TX Ed 3

Field No.	Field Name	Length	From	To	Data Type
176	Other Rooms	5	1774	1778	A

Description: This field describes the rooms within the main building/house, if provided by the county. You can move up to five (5) codes per parcel.

The valid codes, in order of priority are:

F	Family Room/Den
S	Sun Room/Solarium/Florida
A	Lanai
M	Media Room/Home Theater
X	Exercise/Home Gym
N	Bonus Room
U	Study/Library
T	Great Room
C	Cellar
B	Breakfast Nook
O	Home Office
D	Mud Room
L	Laundry Room
Y	Utility Room
G	Game Room/Recreation
H	Hobby/Craft/Sewing
I	Sitting Room
R	Atrium

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
177	Extra Features Area 1	9	1779	1787	A/N
178	Extra Feature Area 1 Ind	2	1788	1789	A
181	Extra Features Area 2	9	1792	1800	A/N
182	Extra Feature Area 2 Ind	2	1801	1802	A
183	Extra Features Area 3	9	1803	1811	A/N
184	Extra Feature Area 3 Ind	2	1812	1813	A
185	Extra Features Area 4	9	1814	1822	A/N
186	Extra Feature Area 4 Ind	2	1823	1824	A

Description: Allow for identifying areas for up to 4 extra features, such as driveways, fences, paving. An exterior feature potentially adds value to the property, but is NOT a building or attribute that has been designated under Other Buildings/Improvements (Fields #163-166 and 169). The area of the feature moves to Extra Features Area, expressed in square feet and/or dimensions, and a one or two-digit code describing the feature moves to Extra Features Area Indicator. Also, it is not necessary for this field to be populated to populate the Indicator fields.

The first byte of Extra Feature Indicator represents the feature (driveway, fence, paving) and the 2nd byte, if present, indicates the specific type of feature.
The Valid codes to describe these Extra Features, in order of priority are:

BB	Billboard/Sign
BH	Bulkhead/Sea Wall
C	Courtyard
D	Driveway
DA	Driveway Asphalt
DB	Driveway Bomanite
DC	Driveway Chat
DK	Driveway Brick
DO	Driveway Concrete
DP	Driveway Paver
DR	Driveway Gravel
DT	Driveway Tile
E	Enclosure (generic)
F	Fence
FC	Chain Link Fence
PA	Asphalt Paving
PC	Concrete Paving
PV	Pavers
RS	Railroad Spur/Switch
RW	Retaining Wall
S	Sidewalk
SE	Screen Enclosure (not specified)
SW	Skyway
T	Cell Site, Tower, Antenna
W	Brick/Rock/Masonry Wall

Example: A residential parcel with a concrete driveway of 10 X 30, and a chain link fence with a perimeter of 550 feet, would be moved as follows:

Extra Feature Area 1	10 X 30
Extra Feature Area 1 Indicator	DO
Extra Feature Area 2	550
Extra Feature Area 2 Indicator	FC

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
179	Topography	1	1790	1790	A

Description: Contains code representing the physical (including man-made) or natural features of the land.

Valid Codes:

H	High Elevation
A	Above Street Level
B	Below Street Level
S	Steep
L	Low Elevation
P	Swampy
R	Rolling
W	Wooded
Y	Brushy
Q	Marsh
M	Mountain
O	Rocky
I	Hilly
E	Level Grade
X	Mixed

Field No.	Field Name	Length	From	To	Data Type
180	Roof Type	1	1791	1791	A

Description: The architectural style of the roof (gable, mansard, etc).

F	Flat
S	Shed
G	Gable or Hip
W	Wood Truss
T	Sawtooth
M	Mansard
L	Gambrel
I	Irregular / Cathedral
D	Dome
R	Rigid Frame Bar Joist
E	Steel Frame / Truss
B	Bowstring truss
C	Reinforced Concrete
P H A	Prestressed Concrete Hip Gable

Sample Instructions:

Use the table below to convert the values in rooftypedescr (35) to populate Roof Type [180]

If (35) is	Move to [180]
BOW	B
FLAT	F
GABLE	G
GAMBREL	L
HIP	G
IRREGULAR	I
MANSARD	M
SAWTOOTH	T
SHED	S

Adair OK Ed 1

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
187	Old/Alternate APN	31	1825	1855	A/N

Description: This field will list the APN previously used by the county to identify the property. In addition, an alternate APN can be moved to this field when available. In case of a conflict, the OLD APN supersedes the Alternate APN since this field is meant to provide a way to tie back to previous editions. This field will only be populated for a period of years, not to exceed five, after the county assessor has changed its parcel numbering system.

Field No.	Field Name	Length	From	To	Data Type
188	Building Condition	1	1856	1856	A

Description: This field contains a code reflecting the condition of a building as determined by the county assessor. To the extent possible the code will match the code, or its closest translation to the coding system used by the assessor.
Valid Codes:

E	Excellent
G	Good
V	Average
F	Fair
P	Poor
U	Unsound

Field No.	Field Name	Length	From	To	Data Type
189	Lot Size - Frontage Feet	10	1857	1866	N

Description: This field provides the frontage measurement of the property when provided by the county assessor.
This field should be expressed numerically with an implied decimal of 1 (9v1).
This field will contain the area in Frontage Feet only as opposed to Lot Size [76] which can be populated several different ways. Click on the link for the differences.

The county may provide both an actual and effective frontage. Give priority to the actual frontage. Here is some additional info:

All residential non-waterfront properties are normally described as using an actual frontage and depth shown in feet. The area is recorded in either square feet, (if under one acre) or in acres (if over one acre).

Actual Frontage:

The frontage is the portion of the lot that abuts the roadway.

If the frontage abuts a curved roadway, the arc measurement is used.

If the property is a corner lot, the shortest side or the municipally addressed side of the lot is the frontage.

Actual Depth:

The depth is normally the distance from the front boundary of the lot to the rear boundary of the lot.

If the opposing depths of the lot (i.e. side boundaries) are not exactly equal, the depth will typically not be shown on the assessment notice.

Actual Area:

The lot size described in either acres or square feet.

If the property is irregular in shape:

Effective Frontage is calculated by averaging the frontage and the rear lot line;

Effective Depth is calculated by averaging the sidelines; and

Effective Lot Size is the product of the Effective Frontage and the Effective Depth.

The following examples illustrate MPAC’s procedure for calculating Effective Frontage and/or Effective Depth and Effective Area:

Example #1

Example #2

Example #3

Example #4

Sample Instructions:

Move Frontage (95) to Lot Size - Frontage Feet [189].

Field No.	Field Name	Length	From	To	Data Type
190	Lot Size - Depth Feet	10	1867	1876	N

Description: This field provides the depth measurement of the property when provided by the county assessor.
This field should be expressed numerically with an implied decimal of 1 (9v1).
This field will contain the area in Depth Feet only as opposed to Lot Size [76] which can be populated several different ways. Click on the link for the differences.

The county may provide both an actual and effective depth. Give priority to the actual depth. Here is some additional info:

All residential non-waterfront properties are normally described as using an actual frontage and depth shown in feet. The area is recorded in either square feet, (if under one acre) or in acres (if over one acre).

Actual Frontage:

The frontage is the portion of the lot that abuts the roadway.

If the frontage abuts a curved roadway, the arc measurement is used.

If the property is a corner lot, the shortest side or the municipally addressed side of the lot is the frontage.

Actual Depth:

The depth is normally the distance from the front boundary of the lot to the rear boundary of the lot.

If the opposing depths of the lot (i.e. side boundaries) are not exactly equal, the depth will typically not be shown on the assessment notice.

Actual Area:

The lot size described in either acres or square feet.

If the property is irregular in shape:

Effective Frontage is calculated by averaging the frontage and the rear lot line;

Effective Depth is calculated by averaging the sidelines; and

Effective Lot Size is the product of the Effective Frontage and the Effective Depth.

The following examples illustrate MPAC’s procedure for calculating Effective Frontage and/or Effective Depth and Effective Area:

Example #1

Example #2

Example #3

Example #4

Sample Instructions:

Move Depth (96) to Lot Size - Depth Feet [190].

Field No.	Field Name	Length	From	To	Data Type
191	Comments (SUMMARY OF DR RECORDS)	120	1877	1996	A/N

Description: Additional information regarding a parcel. This information may come from a comments field provided by the county or can be information added by the analyst. If Duplicate Records are present, this field contains a Summary of DR records and should contain the Impr # and any available physical characteristics.

Sample Instructions:

Concatenate “Mobile Home-“ “Make:” + mh_make (65), “Serial Number:” + mh_serial (68) and “Title:” + mh_title (69) and move the result to Comments [169].
NOTE: If any of the 3 fields are blank don’t move it, but the other 1 or 2 fields can still be moved.
Examples:
(65) = Blairhouse
(68) = 8370X
(69) = A045600H
[169] = Mobile Home-Make: Blairhouse, Serial Number: 8370X, Title: A045600H
(65) = Vintage
(68) = EM9217
(69) = blank
[169] = Mobile Home-Make: Vintage, Serial Number: EM9217
(65) = blank
(68) = P162440
(69) = A070598C
[169] = Mobile Home-Serial Number: P162440, Title: A070598C
Carter OK Ed 1

Field No.	Field Name	Length	From	To	Data Type
192	Water	1	1997	1997	A

Description: Contains codes representing the water system for the property.

Valid Codes:

C	Cistern
M	Municipal/Public
N	None
S	Spring
W	Well
Y	Yes, but not specified

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
193	Sewer	1	1998	1998	A

Description: Contains codes representing the waste disposal/sewage system for the property.

Valid Codes:

M	Municipal/Public
N	None
R	Storm
S	Septic
Y	Yes, but not specified

Last updated 22-Mar-10

Field No.	Field Name	Length	From	To	Data Type
194	New Record Type (Legal Description)	2	1999	2000	A/N

Description: Additional breakdown of Record Type [93]. Indicates whether a record is a "DR" record, a "multiple owner" record, etc.

[blank]	Master Record (not one of the specific types listed below)
DR	Duplicate Record, drop from online
MA	Multiple Addresses
MO	Multiple Owners
MP	Multiple APN records online. *Disclaimer: this assessment property record has been compiled from only one (1) of several improvement records as reported by the county. Therefore, the physical description of the property may be incomplete.
SP	Split Parcel
LX	Legal Extension Record Indicator. The "X" represents a number, L1, L2, etc. Depending on the number of Legal Extension Records.
PX	PCR Extension Record Indicator. The "X" represents a number, P0, P1, P2, etc. Depending on the number of PCRs Extension Records.(No Longer Used)
OX	Owner Extension Record Indicator. The "X" represents a number, O1, O2, O3, etc. Depending on the number of Owner Extension Records. To utilize these records, instruct Manila to create them as needed to accommodate owner names that would otherwise overfill Assessee Owner Name [18] and 2nd Owner Name [19]. The first owner names would still populate these fields; the rest would move to the extension records for names.