Elements

AddressNumberPrefix

Element Name	AddressNumberPrefix
Other common names for this element	Street Number Prefix, Building Number Prefix, House Number Prefix, Site Number Prefix, Structure Number Prefix
Definition	The portion of the Complete Address Number which precedes the Address Number itself.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	None
Domain of Values for this Element	Can be created locally from existing values
Source of Values	Local
How Defined	Locally
Example	N6W2 3001 Bluemound Road A 19 Calle 11 194-0 3 Fiftieth Avenue Milepost 1303 Alaska Highway
Notes/Comments	1. This element is not found in most Complete Address Numbers. When found, it should be separated from the Address Number so that the Address Number can be maintained as an integer for sorting and quality control tests. 2. Informally an Address Number and Address Number Prefix may be written with or without a space between them. Within this standard, the default assumption is that an empty space separates elements unless stated otherwise. The Attached Element can be used to indicate where the assumed space between the Address Number and Address Number Prefix has been omitted within an address file (see Attached Element for additional notes). 3. If a hyphen appears between an Address Number Prefix and an Address Number, the hyphen is included in the Address Number Prefix. 4. Milepost numbers are often used to specify locations on limited-access roads such as interstate highways, and along highways and country roads where addressable features are too sparse to assign address numbers. Where it is useful to treat these as addresses, treat "Milepost" (or "Kilometer", in Puerto Rico) as an Address Number Prefix, and the milepost number as the Address Number.
XML Tag	< AddressNumberPrefix >
XML Model	<xsd:complexType id="AddressNumberPrefix_type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute id="Separator" type="addr_type:Separator_type" /> </xsd:extension> </xsd:simpleContent> </xsd:complexType>
XML Example	<CompleteAddressNumber> <AddressNumberPrefix Separator=" ">N6W2</AddressNumberPrefix> <AddressNumber>3001</AddressNumber> </CompleteAddressNumber> <CompleteAddressNumber> <AddressNumberPrefix Separator=" ">A</AddressNumberPrefix> <AddressNumber>19</AddressNumber> </CompleteAddressNumber>
Quality Measures	AddressNumberFishbonesMeasure RangeDomainMeasure SpatialDomainMeasure TabularDomainMeasure
Quality Notes	Address number prefixes can include map-based information as grid coordinates, references to survey systems or references to sections of a subdivision or housing complex. Where a tabular domain of values are available the prefix can be tested against it. The measure chosen will depend on the type of domain involved. See the introduction to this section for a information on which measures to use.

AddressNumber

Element Name	AddressNumber
Other common names for this element	Street Number, Building Number, House Number, Site Number, Structure Number
Definition	The numeric identifier for a land parcel, house, building or other location along a thoroughfare or within a community.
Definition Source	New
Data Type	Integer
Existing Standards for this Element	None
Domain of Values for this Element	Can be created locally.
Source of Values	Local jurisdiction
Attributes Associated with this Element	Address Number Parity
How Defined	Based on local address ranges associated with individual streets and blocks.
Example	123 Main Street N4W6 123 Oak Road 123 B Highway 88
Notes/Comments	1. The Address Number is defined as an integer to support address sorting, parity (even/odd) definition, and in/out of address range tests. 2. The Address Number must be converted to a characterString when it is combined with the prefix and suffix into a Complete Address Number. 3. Some addresses may contain letters, fractions, hyphens, decimals and other non-integer content within the Complete Address Number. Those non-integer elements should be placed in the Address Number Prefix if they appear before the Address Number, or in the Address Number Suffix if they follow the Address Number. For example, if the New York City hyphenated address 194-03 50th Avenue, New York, NY 11365 were to be parsed rather than represented as a Complete Address Number: ---the Address Number Prefix would be "194-0" (including the hyphen and the leading "0"), ---the Address Number would be 3 (converted to text in constructing the Complete Address Number), ---and the Address Number Suffix would be "1/2". 4. Special care should be taken with records where the Address Number is 0 (zero). Occasionally zero is issued as a valid address number (e.g. Zero Prince Street, Alexandria, VA 22314) or it can be imputed (1/2 Fifth Avenue, New York, NY 10003 (for which the Address Number would be 0 and the Address Number Suffix would be "1/2")). More often, though, zero is shown because the Address Number is either missing or non-existent, and null value has been converted to zero. 5. Address Numbers vs. Address "Letters". In rare instances, thoroughfare addresses may be identified by letters instead of numbers (for example, "A" Main Street, "B" Main Street, "C" Main Street, "AA" Main Street, "AB" Main Street, etc.) A few thousand such cases have been verified in Puerto Rico, and others may be found elsewhere. In such cases, the letter(s) cannot be treated as an Address Number, because an Address Number must be an integer. The letter(s) also cannot be an Address Number Prefix or Address Number Suffix, because neither of those can be created except in conjunction with an Address Number. Instead, the letter(s) should be treated a Subaddress Identifier in an Unnumbered Thoroughfare Address. (For example: Complete Street Name = "Calle Sanchez", Complete Subaddress Identifier = "AB", Complete Place Name = "Mayaguez" State Name = "PR"). As an alternative, the address may be classified in the General Address Class and treated accordingly.
XML Tag	< AddressNumber >
XML Model	<xsd:simpleType id="AddressNumber_type"> <xsd:restriction base="xsd:string"> <xsd:pattern value='[0-9]+' /> </xsd:restriction> </xsd:simpleType>
XML Example	<CompleteAddressNumber> <AddressNumber>1234</AddressNumber> </CompleteAddressNumber>
Quality Measures	Data Type Measure Spatial Domain Measure Range Domain Measure Address Number Fishbones Measure
Quality Notes	The Address Number element is specified as an integer. Data Type Measure is helpful when testing data held in staging tables with variable character fields. Additional tests for the address number require association with a street name.

AddressNumberSuffix

Element Name	AddressNumberSuffix
Other common names for this element	Street Number Suffix, Building Number Suffix, House Number Suffix, Fractional Street Number (USPS), Structure Number Suffix
Definition	The portion of the Complete Address Number which follows the Address Number itself.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	None
Domain of Values for this Element	Can be created locally from existing values
Source of Values	Local
How Defined	Locally
Example	123 1/2 Main Street 121 E E Street B317 A Calle 117 Milepost 34.4 (Address Number Suffix = decimal portion only)
Notes/Comments	1. This element is not found in most Complete Address Numbers. When found, it should be separated from the Address Number so that the Address Number can be maintained as an integer for sorting and quality control tests. 2. Informally an Address Number and Address Number Suffix may be written with or without a space between them. Within this standard, the default assumption is that an empty space separates elements unless stated otherwise. The Attached Element can be used to indicate where the assumed space between the Address Number and Address Number Suffix has been omitted within an address file (see Attached Element for additional notes). 3. If a hyphen appears between the Address Number and the Address Number Suffix, the hyphen is included in the Address Number Suffix. 4. When milepost Complete Address Numbers include decimal fractions, the integer portion of the milepost number is treated as the Address Number, and the fraction (including the decimal point) is treated as an Address Number Suffix. (See Complete Address Number for additional notes on milepost address numbers.)
XML Tag	< AddressNumberSuffix >
XML Model	<xsd:complexType id="AddressNumberSuffix_type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute id="Separator" type="addr_type:Separator_type" /> </xsd:extension> </xsd:simpleContent> </xsd:complexType>
XML Example	<CompleteAddressNumber> <AddressNumber>123</AddressNumber> <AddressNumberSuffix Separator=" ">1/2</AddressNumberSuffix> </CompleteAddressNumber> <CompleteAddressNumber> <AddressNumber>456</AddressNumber> <AddressNumberSuffix Separator=" ">B</AddressNumberSuffix> </CompleteAddressNumber> <CompleteAddressNumber> <AddressNumber>317</AddressNumber> <AddressNumberSuffix Separator=" ">A</AddressNumberSuffix> </CompleteAddressNumber>
Quality Measures	TabularDomainMeasure SpatialDomainMeasure Address Number Fishbones Measure
Quality Notes	1. Address number suffixes can include references to sections of a subdivision or housing complex. Where a tabular domain of values are available the prefix can be tested against it. 2. When geometry for both the address point and and a real Address Number Suffix are available the Spatial Domain Measure can be used to measure tests whether the addressed location is within a polygon describing a map-based Address Number Suffix. 3. Use Address Number Fishbones Measure when geometry for both the address point and a linear spatial domain for Address Number Suffix are available. This measure tests whether the addressed location is along a line describing a map-based Address Number Suffix.

CompleteAddressNumber

Element Name	CompleteAddressNumber
Other common names for this element	Complete street number, full street number, Primary Address Number (USPS), Street Number (USPS), House Number (USPS, Census TIGER)
Definition	An Address Number, alone or with an Address Number Prefix and/or Address Number Suffix, that identifies a location along a thoroughfare or within a community.
Syntax	{ Address Number Prefix } + { Address Number *} + { Address Number Suffix }
Definition Source	New
Data Type	characterString
Existing Standards for this Element	Refer to component simple elements
Domain of Values for this Element	Refer to component simple elements
Source of Values	Refer to component simple elements
How Defined (eg, locally, from standard, other)	Refer to component simple elements
Example	123 Main Street 123 A Main Street 123 1/2 Main Street 0 Prince Street, Alexandria VA 22314 0 1/2 Fifth Avenue, New York, NY 10003 210 East 400 South, Salt Lake City, UT 84111 Milepost 240 Parks Highway Alaska Milepost 72.9 Interstate 84, Wasco County, OR Kilometer 0.5 Carretera 917, Urbanizacion April Gardens, Las Piedras PR 00771 Kilometer 2 Hectometer 7 Carretera 175, Barrio San Antonio, Caguas, Puerto Rico 00725 N89W16758 Appleton Avenue, Menomonee Falls, WI 53051 W63N645 Washington Avenue, Cedarburg, WI 53012 5-5415 Kuhio Highway, Hanalei, HI 96714 194-03 1/2 50th Avenue, New York, NY 11365 A 19 Calle 11, Toa Alta, Puerto Rico
Notes/Comments	1. The Address Number element is required to compose a Complete Address Number. The other elements are optional. 2. The Address Number must be converted from integer to characterString when constructing the Complete Address Number. 3. The great majority of Complete Address Numbers are simple integers. Infrequently the integer is followed by an alphanumeric Address Number Suffix, typically a letter or a fraction. Even more rarely the integer is preceded by an alphanumeric Address Number Prefix. In addition to the typical numbering format, four special-case formats are found in the United States: Milepost addresses, grid-style address numbers, hyphenated address numbers, and other Address Number Prefix letters or symbols. 4. Milepost Complete Address Numbers (Example: "Milepost 240"). Road mileposts are sometimes used to specify locations along highways and similar roads. Mileposts are often used to locate, for example, crash sites, emergency call boxes, bridge locations, inspection stations, roadside rest stops, railroad crossings, highway exits, park and campground entrances, RV parks, and truck stops. Milepost addresses should be parsed as follows: ---"Milepost" (or equivalent word or phrase, such as "kilometer" or 'Mile Marker") is an Address Number Prefix ---The milepost number (integer part only) is an Address Number ---Tenths, if given, are an Address Number Suffix, including the decimal point. ---The road name or highway route number is a Complete Street Name, and parsed accordingly Note that, in Puerto Rico, road measurements are given in kilometers (km), which are sometimes divided into hectometers (hm). 5. Grid-style Complete Address Numbers (Example: "N89W16758"). In certain communities in and around southern Wisconsin, Complete Address Numbers include a map grid cell reference preceding the Address Number. In the examples above, "N89W16758" should be read as "North 89, West 167, Address Number 58". "W63N645" should be read as "West 63, North, Address Number 645." The north and west values specify a locally-defined map grid cell within which the address is located. Local knowledge is needed to know when the grid reference stops and the Address Number begins. 6. Hyphenated Complete Address Numbers (Example: "5-5415"). In some areas (notably certain parts of New York City, southern California, and Hawaii), Complete Address Numbers often include hyphens. Hyphenated Complete Address Numbers should not be confused with Two Number Address Ranges. The former is a single Complete Address Number while the latter includes two Complete Address Numbers. 7. Hyphenated Complete Address Numbers can be parsed so that the number indicating the site or structure is the Address Number, and the remainder (including the hyphen) is the Address Number Prefix or Address Number Suffix. 8. In parts of New York City, hyphenated Complete Address Numbers follow a more complex set of rules. The number to the left of the hyphen indicates the "block" (conceptually--the number does not always change at street intersections and sometimes it changes within a single block face). The number to the right of the hyphen indicates the site or house number within the "block". If the Address Number is less than ten, it is written with a leading zero, as in 194-03 1/2 above. (Additional leading zeros may be added to either number to provide for correct sorting if the entire Complete Address Number is treated as a characterString with the hyphen included.) Within the address standard, these numbers can be constructed and parsed as follows: a. The left-side number (194), the hyphen and the leading 0 form the Address Number Prefix element (text). b. The right-side number (3) is the Address Number (integer), converted to a characterString upon conversion to Complete Address Number with the leading zero(s) added from the Address Number Prefix. c. The suffix, if any (such as the "1/2" in 194-03 1/2), is an Address Number Suffix. 9. Other Address Number Prefix Letters or Symbols. In Puerto Rico, Address Numbers are commonly preceded by an Address Number Prefix letter (e.g. "A 19"). In Portland, OR, negative Address Numbers have been assigned in an area along the west bank of the Willamette River. The minus sign is represented as a leading zero ("0121" and "121" are two different Complete Address Numbers). In such cases the leading zero should be treated as an Address Number Prefix. 10. Zero as a Complete Address Number. Special care should be taken with records where the Address Number is 0 (zero). Occasionally zero is issued as a valid address number (e.g. 0 Prince Street, Alexandria, VA 22314) or it can be imputed (1/2 Fifth Avenue, New York, NY 10003, for which the Address Number would be 0 and the Address Number Suffix would be "1/2"). More often, though, the Address Number is either missing or non-existent, and null value has been converted to zero. 11. Address Numbers vs. Address "Letters". In rare instances, thoroughfare addresses may be identified by letters instead of numbers (for example, "A" Main Street, "B" Main Street, "C" Main Street, "AA" Main Street, "AB" Main Street, etc.) A few thousand such cases have been verified in Puerto Rico, and others may be found elsewhere. In such cases, the letter(s) cannot be treated as an Address Number, because an Address Number must be an integer. The letter(s) also cannot be an Address Number Prefix or Address Number Suffix, because neither of those can be created except in conjunction with an Address Number. Instead, the letter(s) should be treated a Subaddress Identifier in an Unnumbered Thoroughfare Address. (For example: Complete Street Name = "Calle Sanchez",Complete Subaddress Identifier = "AB", Complete Place Name = "Mayaguez" State Name = "PR"). As an alternative, the address may be classified in the General Address Class and treated accordingly.
XML Tag	< CompleteAddressNumber >
XML Model	<xsd:complexType id="CompleteAddressNumber_type"> <xsd:sequence> <xsd:element id="AddressNumberPrefix" type="addr_type:AddressNumberPrefix_type" minOccurs="0" maxOccurs="1" /> <xsd:element id="AddressNumber" type="addr_type:AddressNumber_type" minOccurs="1" maxOccurs="1" /> <xsd:element id="AddressNumberSuffix" type="addr_type:AddressNumberSuffix_type" minOccurs="0" maxOccurs="1" /> </xsd:sequence> <xsd:attribute id="AddressNumberParity" type="addr_type:AddressNumberParity_type" /> <xsd:attribute id="AttachedElement" type="addr_type:AttachedElement_type" /> </xsd:complexType>
XML Exmample	<CompleteAddressNumber> <AddressNumber>55</AddressNumber> <AddressNumberSuffix Separator="">1/2</AddressNumberSuffix> </CompleteAddressNumber> <CompleteAddressNumber> <AddressNumberPrefix Separator="">MILEPOST</AddressNumberPrefix> <AddressNumber>72.9</AddressNumber> </CompleteAddressNumber>
Quality Measures	PatternSequenceMeasure
Quality Notes

CompleteLandmarkName

Element Name	CompleteLandmarkName
Other common names for this element
Definition	One or more Landmark Names which identify a relatively permanent feature of the manmade landscape that has recognizable identity within a particular cultural context.
Syntax	A series of one or more Landmark Names. If more than one are listed, the Element Sequence Number can be used to show the order in which they should be listed.
Definition Source	Adapted from U.S. Board on Geographic Names, "Principles, Policies, Procedures," (Online Edition (revised), 2003, as posted May 17, 2006 at http://geonames.usgs.gov/docs/pro_pol_pro.pdf ), p. 48, definition of "geographic name".
Data Type	characterString
Existing Standards for this Element	None, but see GNIS Feature ID
Domain of Values for this Element	Can be created locally from existing values
Source of Values	Local
How Defined (eg, locally, from standard, other)	Locally
Examples	University of Washington, Seattle, WA Suzallo Library, University of Washington, Seattle, WA Statue of Liberty, New York, NY Statue of Liberty, Liberty Island, New York, NY Yosemite National Park, CA Camp Curry, Yosemite National Park, CA
Notes/Comments	1. Landmark names often refer to extensive areas, which may contain smaller named landmarks. In these cases the landmark name may function as a single "master address" containing multiple subordinate addresses. The Complete Landmark Name provides for the inclusion of multiple Landmark Names in an address. 2. Where multiple Landmark Names are given, they are typically ordered from smallest to largest. The Element Sequence Number can be used to indicate the sequence in which the Landmark Names should be ordered. 4. The U.S. Board on Geographic Names has compiled and standardized names for many landmarks in the Geographic Names Information System (GNIS). Local authorities are encouraged to review the GNISFeature ID for more information on the use of the GNIS ID and Landmark Names. Where a complete landmark name consists of more than one landmark name, the GNIS Code for the smallest unit of the complete landmark name should be used to provide the most specific reference.
XML Tag	< CompleteLandmarkName >
XML Model	<xsd:complexType id="CompleteLandmarkName_type"> <xsd:sequence> <xsd:element id="LandmarkName" type="addr_type:LandmarkName_type" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> <xsd:attribute id="Separator" type="addr_type:Separator_type" /> </xsd:complexType>
XML Example	<CompleteLandmark Separator=","> <LandmarkName ElementSequenceNumber="1">CAMP CURRY</LandmarkName> <LandmarkName ElementSequenceNumber="2">YOSEMITE NATIONAL PARK</LandmarkName> </CompleteLandmark>
Quality Measures	RepeatedElementUniquenessMeasure ComplexElementSequenceNumberMeasure PatternSequenceMeasure
Quality Notes

CompletePlaceName

Element Name	CompletePlaceName
Other common names for this element	See Place Name
Definition	One or more Place Names which identify an area, sector, or development (such as a neighborhood or subdivision in a city, or a rural settlement in unincorporated area); incorporated municipality or other general-purpose local governmental unit; county; or region within which the address is physically located; or the name given by the U.S. Postal Service to the post office from which mail is delivered to the address.
Syntax	A series of one or more Place Names. If more than one is listed, the Place Name Type can be used to specify the type for each Place Name (e.g., community, municipal, postal, county, region) and the Element Sequence Number can be used to show the order in which they should be listed.
Definition Source	See Place Name
Data Type	characterString
Existing Standards for this Element	No single controlling authority, but the Geographic Names Information System (GNIS) attempts to include and standardize the names of all populated places and incorporated local governments (see GNISFeature ID). For USPS Post Office names, the controlling authority is the USPS "City State File" as referenced in Section 221 of USPS Publication 28
Domain of Values for this Element	None (but see existing standards above)
Source of Values	Local (but see existing standards above)
How Defined (eg, locally, from standard, other)	Locally.
Examples	Ajo, Pima County, AZ (unincorporated community in Pima County, AZ) Portola Valley, CA (incorporated town) Birmingham, AL (city) Salt Lake City, UT (city) Queens, New York, NY (New York City borough) Orleans Parish, LA (county) FPO AA (overseas military postal delivery) New Hope Community, Shelby County, AL (unincorporated community Shelby County, AL) Capitol Hill, Washington, DC (neighborhood in Washington, DC) Wailuku, Maui, HI Edgewater Park, Bronx, New York, NY (neighborhood in New York City) Sector La Frontera, Barrio Cotui, San German, PR (Puerto Rican sector) Urbanizacion Altagracia, Toa Baja, PR (Puerto Rican urbanizacion) Jardines Los Almendros, Municipio Maunabo, PR (Puerto Rican urbanization) Parcelas Nuevas, Barrio Rincon, Cidra, PR (Puerto Rican parcelas)
Notes/Comments	1. "Place name" can mean different things to different people in different contexts. It may name a community, an incorporated local government, a post office, a county, or a region. For many thoroughfare and landmark addresses, a different place name may be used by an emergency dispatcher directing an ambulance, a local government official assessing local taxes or eligibility for services, a postal clerk, or a business providing contact information on its website. 2. For some purposes an address may require more than one place name (e.g., "Wailuku, Maui", "New Hope, Shelby County", "Parcelas Nuevas, Barrio Rincon, Cidra" ). This is discouraged in postal addresses, but it may be necessary in other contexts, (e.g., to provide both the municipality and county for an address). The Complete Place Name provides for inclusion of multiple Place Names in the address. 3. Where multiple Place Names are given, they are typically ordered from smallest to largest. The Element Sequence Number can be used to indicate the sequence in which the Place Names should be ordered. 4. This standard provides the Place Name Type attribute to allow the use of different place names with the same address for different purposes. Five types are defined: community, municipal, postal, county, and regional. Others may be added. Additional explanation is given under Place Name and Place Name Type. 5. The difference between a place and a landmark is not always clear and distinct. As a general principle, a landmark is under a single use or ownership or control, while places are not. Thus a place generally includes numerous separate addresses, while a landmark, even if it covers an extensive area, might be considered to be a single "master address" (often containing multiple subordinate addresses). These general principles apply to most cases and are useful as general distinctions, but exceptions and marginal cases are easily found. 6. The U.S. Board of Geographic Names has assigned GNISFeature ID's to all place names that have been registered and accepted by the Board. Within the address standard, GNISFeature ID's may be associated with Place Names to facilitate standardization and unambiguous communication. See GNISFeature ID for more information.
XML Tag	< CompletePlaceName >
XML Model	<xsd:complexType id="CompletePlaceName_type"> <xsd:sequence> <xsd:element id="PlaceName" type="addr_type:PlaceName_type" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> <xsd:attribute id="Separator" type="addr_type:Separator_type" /> </xsd:complexType>
XML Example	<CompletePlaceName> <PlaceName Place Name Type="USPSPlaceName"> Ajo </PlaceName> </CompletePlaceName> <CompletePlaceName> <PlaceName Place Name Type="County" > Shelby </PlaceName> </CompletePlaceName> <CompletePlaceName> <PlaceName Place Name Type="USPS" > Washington </PlaceName> </CompletePlaceName> <CompletePlaceName> <PlaceName Place Name Type="Community" > Urbanizacion Los Olmos </PlaceName> </CompletePlaceName> <CompletePlaceName> <PlaceName Place Name Type="Community">Queens</PlaceName> <PlaceName Place Name Type="Municipal">New York</PlaceName> </CompletePlaceName>
Quality Measures	RepeatedElementUniquenessMeasure ComplexElementSequenceNumberMeasure Pattern Sequence Measure
Quality Notes

CompleteStreetName

Element Name	CompleteStreetName
Other common names for this element	Street name, Road name, Full name (Census TIGER)
Definition	Official name of a thoroughfare as assigned by a governing authority, or an alternate (alias) name that is used and recognized.
Syntax	{ Street Name Pre Modifier } + { Street Name Pre Directional } + { Street Name Pre Type } + { Separator Element } + { Street Name *} + { Street Name Post Type } + { Street Name Post Directional } + { Street Name Post Modifier }
Definition Source	New
Data Type	characterString
Existing Standards for this Element	Refer to Component Elements
Domain of Values for this Element	Local domain of values for Complete Street Name. Refer to component elements for domains governing individual elements.
Source of Values	Locally determined
How Defined (eg, locally, from standard, other)	Locally determined
Example	All of the following are complete street names: Main Street North Main Street North Main Street Extended Avenue B Old Avenue B North Broadway Kentucky State Highway 67 North Parkway Boulevard of the Allies Alameda de las Pulgas East 400 South
Notes/Comments	1.CompleteStreetName Components. A Complete Street Name is composed from eight simple elements, which, if used, must appear in the following order: Street Name Pre Modifier, Street Name Pre Directional, Street Name Pre Type, Separator Element, Street Name, Street Name Post Type, Street Name Post Directional, and Street Name Post Modifier. Each of these elements is defined and described elsewhere in the standard. 2. Required Element: The Street Name element is required to compose a Complete Street Name. The other elements are optional. 3. Parsing: Parsing is the process of resolving a Complete Street Name into its component simple elements. Usually parsing is straightforward: there is a one-word Street Name, a Street Name Post Type, and perhaps a one-word Street Name Pre Directional or a Street Name Post Directional. For example: Main Street: Street Name = "Main"; Street Name Post Type = "Street" North Main Street Street Name Pre Directional = "North"; Street Name = "Main"; Street Name Post Type = "Street" Main Street North Street Name = "Main"; Street Name Post Type = "Street"; Street Name Post Directional = "North" 3a. Parsing: Street Name Pre Type and Separator Element. Occasionally the type word precedes the Street Name: Avenue C: Street Name Pre Type = "Avenue"; Street Name = "C" Even more rarely, the Street Name Pre Type is separated from the Street Name by a prepositional phrase. The Prepositional phrase is classified as a Separator Element. Within Complete Street Names, Separator Elements occur only immediately following Street Name Pre Types. These are rare in English-language Complete Street Names, but they are common in Spanish, French, and Italian (Alameda de las Pulgas, Rue des Fleurs). Example: Boulevard of the Allies: Street Name Pre Type = "Boulevard"; Separator Element = "of the"; Street Name = "Allies"; 3b. Parsing: Street Name Pre Modifiers and Street Name Post Modifiers. Occasional Complete Street Names include words that normally are a part of the Street Name, but are separated from the Street Name by directional or type words. These are classified as Street Name Pre Modifiers or Street Name Post Modifiers. Examples: Old North Main Street: Street Name Pre Modifier = "Old"; Street Name Pre Directional = "North"; Street Name = "Main"; Street Name Post Type = "Street" Main Street Extended: Street Name = "Main"; Street Name Post Type = "Street"; Street Name Post Modifier = "Extended" Finally, words such as "The" and "Old" may be parsed as Street Name Pre Modifiers when they precede the Street Name but must be excluded from it so that the Street Name will be placed properly in a sorted alphanumeric list. Example: "Old China Springs Road" might be parsed in either of two ways by the local Address Authority: Old China Springs Road (parsing 1): Street Name Pre Modifier = "Old"; Street Name = "China Springs"; Street Name Post Type = "Road" (if the name is to be listed as "China Springs Road, Old") Old China Springs Road (parsing 2): Street Name = "Old China Springs"; Street Name Post Type = "Road" (if the name is to be listed under "Old", or if the Street Name element is not used for creating sorted Complete Street Name lists) 3c. Complete Street Names That Do not Follow The Typical Pattern. Note 4 describes the logical process for parsing typical Complete Street Names. Certain unusual Complete Street Names do not follow the typical pattern. They are special cases or complex names, and parsing as described in Note 4 below will not result in a properly parsed set of elements. These special cases and complex names are explained in Notes 5 and 6 below. 4. Parsing Procedures for Typical Street Names In practice, most Address Authorities and users will use a commercial or locally-developed parsing program to parse and standardize the parts of each street name. However, most commercially available parsers follow the USPS definitions and procedures, which differ in significant respects from those of this standard. For example, the USPS model does not recognize Street Name Pre Types as a separate element; they are combined into Street Name. It also does not recognize or allow for either Street Name Pre Modifiers or Street Name Post Modifiers, and does not provide guidance on how to handle them in parsing. The specific differences are discussed more fully in the Postal Addressing Profile of this Standard. It is critical that an Address Authority that plans to parse a dataset containing Complete Street Names be aware of these differences. If a USPS parser is used, the Authority must either revise the parser to comply with this standard, or review the results carefully to insure that all component parts have been properly parsed. Many of the tests in the Data Quality part of this standard can be used for such a review. The parsing procedure described in this note illustrates the logic of breaking Complete Street Names into their component parts and for identifying special cases and complex names as they are found. Notes 5 and 6 provide guidance on the special cases and complex names where these procedures will not result in a properly parsed set of Street Name elements. a. The parser examines the Complete Street Name. If the Complete Street Name includes only one word, then by definition that word is the Street Name. The remaining procedures apply to Complete Street Names with more than one word. b. The parser then locates the type words (if any) and the directional words (if any) in relation to the other words. The other words are most likely Street Name words, but they might also be Street Name Pre Modifiers, Street Name Post Modifiers. or Separator Element words. (If there are no other words--that is, if the Complete Street Name is comprised entirely of directional words and type words--the parser should set that Complete Street Name aside as a special case.) c. The parser then takes the words in order from right to left (that is, from last to first). d. If the last word is a directional word, it is parsed as a Street Name Post Directional. (If the last two words are directional words, then the parser sets that Complete Street Name aside as a special case.) e. If the last word is a type word, it is parsed as a Street Name Post Type. Or, if the second-to-last word is a type word, and the last word is a Street Name Post Directional, then it parses the second-to-last word as a Street Name Post Type. (If the two type words are found together, then the parser sets that Complete Street Name aside as a special case.) f. If there is only one word that is neither a type word nor a directional word, it is parsed as the Street Name. If there is more than one such word, and together they form a continuous phrase, the phrase is parsed as the Street Name. (The word or phrase may or may not be followed by a Street Name Post Type and/or a Street Name Post Directional.) g. If a directional and/or a type word precedes the Street Name word(s), it is parsed as a Street Name Pre Directional or a Street Name Pre Type, respectively. Note that the Street Name Pre Directional always precedes the Street Name Pre Type. (If two or more type words, or two or more directional words, are found to precede the Street Name, then the parser sets that Complete Street Name aside as a special case.) h. If a prepositional phrase immediately follows a Street Name Pre Type, then it is removed from the Street Name. It is a Separator Element. i. If there is more than one non-type, non-directional word, and they do not form a continuous phrase, then the parser separates them from the Street Name by a type or directional word. If a non-type, non-directional word occurs: --Before a Street Name Pre Directional or Street Name Pre Type, it is a Street Name Pre Modifier. --After a Street Name Pre Directional or Street Name Pre Type (or Separator Element), or before a Street Name Post Directional or Street Name Post Type, it is part of the Street Name. --After a Street Name Post Directional or Street Name Post Type, it is a Street Name Post Modifier. --Between a Street Name Pre Directional and a Street Name Pre Type, or between a Street Name Post Directional and a Street Name Post Type, the parser sets that Complete Street Name aside as a special case. j. If a Street Name begins with a word such as "The" or "Old", and the Street Name is not preceded by a Street Name Pre Type or a Street Name Pre Directional, and the Address Authority prefers to remove it from the Street Name so that the Street Name can be used as the list word in creating a sorted alphanumeric list of Complete Street Names, then the word may be placed in the Street Name Pre Modifier. k. Having classified all the words into elements, the parser verifies that each element occurs no more than once, and in the correct order: Street Name Pre Modifier, Street Name Pre Directional, Street Name Pre Type, Separator Element, Street Name, Street Name Post Type, Street Name Post Directional, and Street Name Post Modifier. If any elements are repeated or out of order, the parser sets that Complete Street Name aside as a special case. l. Lastly the special cases are examined to determine their correct parsing, based on knowledge of the local Address Reference System and the origin of the particular Complete Street Name. Determine the Street Name first, and then decide how to parse the remaining words. m. The end result is a list of valid Complete Street Names, with the correct parsing for each, and a list of valid values for each street name element. 5. Special Cases 5.1. Numbered Local Government, County, State, and U.S. Roads and Highways 5.1a. Description: Numbered (or, occasionally, lettered) jurisdictional route names include a Street Name Pre Type and the route identifier ("Highway 101", "Route AA"). The names may also include the jurisdiction name and the administrative type of road, which should also be included in the Street Name Pre Type. 5.1b. Examples: (see USPS Publication 28 Appendix F for additional examples) Township Road 20: Street Name Pre Type = "Township Road"; Street Name = "20" County Road 88: Street Name Pre Type = "County Road"; Street Name = "88" Kentucky State Highway 67: Street Name Pre Type = "Kentucky State Highway"; Street Name = "67" US Route 40: Street Name Pre Type = "US Route"; Street Name = "40" Texas Farm-to-Market Road 2168: Street Name Pre Type = "Texas Farm-to-Market Road"; Street Name = "2168" 5.1c. Procedure: Parse the Street Name Pre Type and all qualifier words, including jurisdictional name (e.g., "Township", "County", "Kentucky State") and administrative type (e.g., "Farm-to-Market"), into the Street Name Pre Type. Place only the number or letters identifying the individual thoroughfare into the Street Name. 5.2. Streets Named for Places, Landmarks, Persons, Corporations or Similar Entities 5.2aDescription: If a street is named for a place, landmark, person, corporation, event, etc., the full name is included in the Street Name. If the full name includes type or directional words, the Complete Street Name can be ambiguous.--that is, the Complete Street Name can be parsed in more than one way, and the correct parsing cannot be determined from the Complete Street Name itself. 5.2b. Example 1: North Lake Street Parsing 1: Street Name = "North Lake"; Street Name Post Type = "Street" Parsing 2: Street Name Pre Directional = "North"; Street Name = "Lake"; Street Name Post Type = "Street" Analysis: If the street is named for North Lake, a geographic feature in the area, then parsing 1 is correct. If South Lake Street is the southern portion of Lake Street, then parsing 2 is correct. Example 2: West Virginia Avenue Parsing 1: Street Name = "West Virginia"; Street Name Post Type = "Avenue" Parsing 2: Street Name Pre Directional = "West"; Street Name = "Virginia"; Street Name Post Type = "Avenue" Analysis: If West Virginia Avenue is named for the state of West Virginia, then "West" is part of the Street Name, and parsing 1 is correct. However, if it is not named for the state, then the word West is considered a Street Name Pre Directional, and parsing 2 is correct. Example 3: Old North Church Road Parsing 1: Street Name = "Old North Church"; Street Name Post Type = "Road" Parsing 2: Street Name Pre Modifier = "Old"; Street Name Pre Directional = "North"; Street Name = "Church"; Street Name Post Type = "Road" Analysis: If the street was named for a church called Old North Church then the entire name belongs in the Street Name, and parsing 1 is correct. However, if the street is a section of Church Road, with the predirectional North, and is perhaps an old alignment which has been replaced, then parsing 2 is correct, placing Church alone as the Street Name, North as the Street Name Pre Directional, and Old as the Street Name Pre Modifier. 5.2c. Procedure: If there is doubt, confer with the local Address Authority (or historian) to determine whether the Complete Street Name includes the name of a place, landmark, person, corporation, event, etc.. If so, then place the full name in the Street Name (including any type or directional words in the name), and then parse following the procedure for typical street names. If not, parse the Complete Street Name following the procedure for typical street names. 5.3. Double-directional Grid Street Names without Street Types 5.3a. Description: In Utah, and some areas of Indiana, Complete Street Names often include both a Street Name Pre Directional and a Street Name Post Directional and a numeric Street Name, but do not contain either a Street Name Pre Type or a Street Name Post Type. The Complete Address Number and the Complete Street Name together give a grid position. 5.3b. Example: 210 East 400 South: Complete Address Number = "210"; Street Name Pre Directional = "East"; Street Name = "400"; Street Name Post Directional = "South" CompleteStreetName = "East 400 South" 5.3c. Procedure: Parse the first number as the Complete Address Number, the first directional as the Street Name Pre Directional, the second number as the Street Name, and the second directional as the Street Name Post Directional. 6. Complete Street Names that Do Not Conform to the Typical Pattern The 2010 TIGER file includes over 2.1 million different Complete Street Names. A pattern analysis of the names suggests that well over 95% of them can be parsed unambiguously using the standard rules and special cases described above. The exceptions can be parsed in more than one way, because either: 1. The Complete Street Name includes multiple type or directional words where one word is expected, or 2. The name, directional and type words do not occur in the expected order. Parsing of such names is complicated by the fact the directional words and type words also are often used in or as Street Names. The exceptions fall into four pattern-types, each discussed more fully below: 1. Complete Street Names composed entirely of directional and street type words (e.g. "East Circle Drive") 2. Complete Street Names with two or more type words preceding or following the Street Name (e.g. "C Street Terrace") 3. Complete Street Names with two or more directional words preceding or following the Street Name (e.g. "North South Avenue") 4. Complex Complete Street Names (e.g. "Flaming Gorge Alternate Loop 2 Road") In such cases, the Address Authority should determine the correct parsing, based on knowledge of the local Address Reference System and the origin of the particular Complete Street Name. The Address Authority should document the correct wording and parsing of the name in the record-level metadata, so that it can be done consistently over time. In determining the parsing, the Address Authority should first determine the Street Name, and then decide how to parse the remaining words. (The Address Authority may prefer to parse the name so that the resulting Street Name element can be used as the listword in creating a sorted alphanumeric list of Complete Street Names.) If authoritative guidance is not available, and parsing must be done anyway, include a comment in the metadata stating that the parsing is presumed but not authoritative. 6.1. Complete Street Names Composed Entirely of Directional and Street Type Words 6.1a Description: In these cases, the Address Authority must determine which of the type or directional words in the Complete Street Name is the Street Name, and which are either Street Name Pre Types, Street Name Pre Directionals , Street Name Post Types, or Street Name Post Directionals. In some cases with multiple type or directional words, the Street Name Pre Modifier and/or the Street Name Post Modifier may also be required to manage all of the given words. 6.1b. Examples: Court Place; Avenue North; Park Lane Circle 6.2. Complete Street Names with Two or More Type Words Preceding or Following the Street Name 6.2a Description: To parse these Complete Street Names, determine if the type word(s) closest to the Street Name actually form part of the Street Name. If so, parse the word(s) as part of the Street Name. If multiple type words occur outside the Street Name, and they occur consecutively, then all of those words are placed in the Street Name Pre Type (if they precede the Street Name) or the Street Name Post Type (if they follow the Street Name). If the type words are not consecutive--that is, they are separated by a directional or other word--then the type word(s) that are separated are placed in the Street Name Pre Modifier (if they precede the Street Name Pre Type) or the Street Name Post Modifier (if they follow the Street Name Post Type). These determinations are made by the Address Authority based on its knowledge of the local Address Reference System and the origin of the Complete Street Name. 6.2b Examples: Charles Lane Boulevard: Street Name = "Charles Lane"; Street Name Post Type = "Boulevard" ("Lane" can be used as a type word, but here it is part of the Street Name because it was named for a person, "Charles Lane".) Tenth Street Bypass: Street Name = "Tenth"; Street Name Post Type = "Street Bypass" (Consecutive type words that follow the Street Name are included in the Street Name Post Type) Lee Highway Access Road: Street Name = "Lee"; Street Name Post Type = "Highway Access Road" (Consecutive type words that follow the Street Name are included in the Street Name Post Type) Bypass Highway 22: Street Name Pre Type = "Bypass Highway"; Street Name = "22" (Consecutive type words that precede the Street Name are included in the Street Name Pre Type) Bypass North Highway 22: Street Name Pre Modifier = "Bypass"; Street Name Pre Directional = "North"; Street Name Pre Type = "Highway"; Street Name = "22"; Street Name Pre Type = "Highway"; ("Bypass" and "Highway" do not occur consecutively) 6.3. Complete Street Names with Two or More Directional Words Preceding or Following the Street Name 6.3a Description: Where two directional words occur together before or after the Street Name, the Address Authority must determine whether one or both of the two directional words are actually part of the Street Name, or whether the Complete Street Name includes multiple consecutive pre- or post-directional words. If the Complete Street Name includes multiple consectutive pre- or post-directional words, then all but one are modifiers. 6.3b. Examples: North West Virginia Avenue, where the street was named for the State of West Virginia: parse "North" as a Street Name Pre Directional, and West as part of the Street Name. East West Highway, where "East West" is known locally to be the Street Name: parse "East West" as the Street Name, with no Street Name Pre Directional. North East 14th Street, where North and East are properly separated (and not a mistyping of the quadrant designator "Northeast"): parse the word closest to the Street Name as a Street Name Pre Directional, and the preceding word as a Street Name Pre Modifier. "Pharr Court North Northeast", a Street Name Post Directional followed by a a quadrant designator: parse the quadrant designator as a Street Name Post Modifier. 6.4. Complex Complete Street Names 6.4a Description: These Complete Street Names include multiple type and/or directional words interspersed with other words or out of the expected order. In parsing these, use best judgment in determining the Street Names, based on knowledge of the local Address Reference System and the origin of the Complete Street Name. Then determine the parsing of the remaining words into types, directionals, and/or modifiers. 6.4b. Examples: 6th Avenue Frontage Road East Piper Road Farm Access Road Extended 87th Street South Frontage Road East Loop 1604 North Access Road US Highway 127 Loop 1 Connector US Highway 23 - Kentucky 122 Connector Road 7. Local Discretion in Parsing Complete Street Names. To provide for consistent and efficient address data exchange, data providers should fit a Complete Street Name into the standard pattern or special cases given in Notes 4 and 5 where possible, and parse the name according to standard procedure. Where that is not possible, limited local parsing discretion is allowed as provided in Note 6. 8. Complete List of Street Names and Alias Street Names Each Address Authority should establish a domain of values for each street name element, and compose from that a lookup table of valid Complete Street Names, for use in validating addresses and diagnosing street name errors. Official and alternate and names can be distinguished by the Official Status attribute. Note that alternate and alias names often apply to only a portion of a thoroughfare. For example, US Route 50 in the District of Columbia is an alias for some, but not all, of 14th Street Northwest. Because the relationship between official and alias names changes street segment by street segment, street name relationships cannot be managed fully without reference to a street network model that defines the segments. 9. Creating Sorted Alphabetical and Alphanumeric Lists of Complete Street Names Address Authorities may wish to create a sorted alphabetical list of Complete Street Names (or an alphanumeric list, if the list includes numbered Complete Street Names). Whether and how this is done is a local matter and outside the scope of this standard. One common method is to list the Complete Street Names in order of the Street Name element. Another common method is to list the Complete Street Names in order of Street Name Pre Type, if present, and then by Street Name. If no simple rule works for all Complete Street Names, the Address Authority may create a look-up table that assigns a particular listword to each Complete Street Name. In addition, if a Street Name begins with a word (such as "The" or "Old") that would cause the Complete Street Name to be listed out of its expected order, the Address Authority may separate that word from the Street Name and place it in the Street Name Pre Modifier. 10. Abbreviations To avoid confusion, this standard requires that all words in a Complete Street Name be recorded and stored fully spelled out. Abbreviations can create ambiguity. (For example: "E Street": Is it E Street, or is it really East Street?) Various inconsistent sets of street type abbreviations are in use, for various purposes, and none is exhaustive. Therefore street name words should be recorded and stored unabbreviated, and linked to look-up tables of abbreviations so that the proper set of abbreviations can be applied in views or export routines when needed for special purposes such as mailing labels or 9-1-1 files. For postal addressing, USPS Publication 28 prefers the use of USPS standard abbreviations for Street Name Pre Directionals, Street Name Post Directionals, and Street Name Post Types. USPS standard abbreviations are recognized within the Postal Addressing Profile of this standard.
XML Tag	< CompleteStreetName >
XML Model	<xsd:complexType id="CompleteStreetName_type"> <xsd:sequence> <xsd:element id="StreetNamePreModifier" type="addr_type:StreetNamePreModifier_type" minOccurs="0" maxOccurs="1" /> <xsd:element id="StreetNamePreDirectional" type="addr_type:StreetNamePreDirectional_type" minOccurs="0" maxOccurs="1" /> <xsd:element id="StreetNamePreType" type="addr_type:StreetNamePreType_type" minOccurs="0" maxOccurs="1" /> <xsd:element id="StreetName" type="addr_type:StreetName_type" minOccurs="1" maxOccurs="1" /> <xsd:element id="StreetNamePostType" type="addr_type:StreetNamePostType_type" minOccurs="0" maxOccurs="1" /> <xsd:element id="StreetNamePostDirectional" type="addr_type:StreetNamePostDirectional_type" minOccurs="0" maxOccurs="1" /> <xsd:element id="StreetNamePostModifier" type="addr_type:StreetNamePostModifier_type" minOccurs="0" maxOccurs="1" /> </xsd:sequence> <xsd:attribute id="AttachedElement" type="addr_type:AttachedElement_type" /> </xsd:complexType>
XML Example	<CompleteStreetName> <StreetNamePreDirectional>NORTH</StreetNamePreDirectional> <StreetName>MAIN</StreetName> <StreetNamePostType>STREET</StreetNamePostType> <StreetNamePostModifier>EXTENDED</StreetNamePostModifier> </CompleteStreetName> <CompleteStreetName> <StreetNamePreModifier>OLD</StreetNamePreModifier> <StreetNamePreType>AVENUE</StreetNamePreType> <StreetName>B</StreetName> <StreetNamePostDirectional>NORTH</StreetNamePostDirectional> </CompleteStreetName>
Quality Measures	TabularDomainMeasure DuplicateStreetNameMeasure PatternSequenceMeasure
Quality Notes	Note that if tabular and/or domains are maintained for Complete Street Name elements at both levels, simple and complex, quality control checks should be run for simple element components before testing the complex element domain.

CompleteSubaddress

Element Name	CompleteSubaddress
Other common names for this element	See Subaddress Element
Definition	One or more Subaddress Elements that identify a subaddress within an addressed feature. A subaddress is a separate, identifiable portion of a feature, the whole of which is identified by a: --- Complete Address Number and Complete Street Name (in the case of a Numbered Thoroughfare Address) --- Two Complete Address Numbers, separated by a hyphen, and followed by a Complete Street Name (in the case of a Two Number Address Range) --- Complete Street Name (in the case of an Unnumbered Thoroughfare Address) --- Complete Landmark Name (in the case of a Landmark Address) --- Complete Address Number and Complete Landmark Name or Complete Place Name (in the case of a Community Address) --- USPS Box or USPS Address (in the case of a USPSPostal Delivery Box or USPSPostal Delivery Route address; for these classes, PMB (private mail box) is the only Subaddress Type permitted.)
Syntax	A series of one or more Subaddress Elements. If more than one are listed, the Element Sequence Number can be used to show the order in which they should be listed.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	None
Domain of Values for this Element	None
Source of Values	N/A
How Defined (eg, locally, from standard, other)	N/A
Attributes Associated with this Element	Element Sequence Number
Example	1. 123 Main Street, Apartment 101 2. 1000 Aviation Road, Building 4, Wing 7, Floor 6, Corridor Zero, Office 2B 3. Metro Airport, Terminal A, Gate C27 4. Average Suburban Office Park, Building 12, Mezzanine, Suite 200 5. 800 West Mountain Road, Building 6, Suite 450 7. 740 Park Avenue, Apartment 15/16B 8. 1324-26 Calle Amapolas, Apartamento 103 9. Five-Star Hotel, East Tower, Penthouse 9. U.S. Dept. of Agriculture Building, Wing 7, Room 324 10. General Hospital, Cardiac Wing, Room 224 11. U.S. Department of Commerce Building, Room 6056 (Floor 6, Corridor Zero, Room 56) 12. Pentagon, Room 3D126 (Third floor, D ring, First corridor, Room 26) 13. RR 1 Box 12 PMB 596 14. 10 Main Street Suite 11 PMB 234
Notes/Comments	1. Complete Subaddresses and their component elements pertain to a wide variety of residential, and commercial buildings, from single basement apartments to multi-stucture office parks, as well as countless specialized structures such as airports, piers, warehouses, manufacturing plants, and stadiums. Complete Subaddresses are typically designated by the property owner, and addressing authorities usually have no responsibility for compiling or verifiying them. However, this is changing as address verification becomes more important for government purposes such as security, emergency response, and verification of eligibility for voting, school attendance, and public services. 2. Usually Complete Subaddresses follow a pattern of Building-Floor-Room (or Doorway), but due to the wide variety of cases no general rule can be given. In composing the Complete Subaddress, the Subaddress Elements should be ordered from largest to smallest, or in the order one would encounter them in navigating from outside the site to the designated subaddress. If desired, use the Element Sequence Number to indicate the sequence in which the Subaddress Elements should be ordered.
XML Tag	< CompleteSubaddress >
XML Model	<xsd:complexType id="CompleteSubaddress_type"> <xsd:sequence> <xsd:element id="SubaddressElement" type="addr_type:SubaddressElement_type" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType>
XML Example	<CompleteSubaddress> <SubaddressElement Element Sequence Number="1" Subaddress Component Order="1" > <SubaddressType>Building</SubaddressType> <SubaddressIdentifier>A</SubaddressIdentifier> </SubaddressElement> <SubaddressElement Element Sequence Number="2" Subaddress Component Order="1" > <SubaddressType>Floor</SubaddressType> <SubaddressIdentifier>7</SubaddressIdentifier> </SubaddressElement> </CompleteSubaddress>
Quality Measures	RepeatedElementUniquenessMeasure ComplexElementSequenceNumberMeasure PatternSequenceMeasure
Quality Notes	This test for the Complete Subaddress assumes that quality tests have been run for supporting elements: Subaddress Type, Subaddress Identifier and Subaddress Element.

CornerOf

Element Name	CornerOf
Other common names for this element
Definition	A directional word describing a corner formed by the intersection of two thoroughfares.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	None
Domain of Values for this Element	Northwest, northeast, southeast, southwest North, east, south, west
Source of Values	New
How Defined (eg, locally, from standard, other)	New
Examples	Northwest corner of Scott Street and North Walnut Street, Stillwater OK South corner of North 13th Street and Q Street North, Fort Smith, AR
Notes/Comments	1. The Corner Of element specifies a particular corner of an intersection. It is used only in the Intersection Address class. 2. Corners are typically identified by the directional word corresponding most closely to the direction of a line bisecting the corner angle. 3. An intersection corner should not be taken as a substitute for a Numbered Thoroughfare Address. If desired, use the Related Address ID and the Address Relation Type to relate an intersection corner to the Numbered Thoroughfare Address(es) at that corner. 4. The phrase "corner of" should be included in the address to ensure that the corner indicator is not mistaken for part of the Complete Street Name.
XML Tag	< CornerOf >
XML Model	<xsd:complexType id="CornerOf_type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> </xsd:extension> </xsd:simpleContent> </xsd:complexType>
XML Example	<CornerOf> North </CornerOf>

CountryName

Element Name	Country Name
Other common names for this element	Nation
Definition	The name of the country in which the address is located. A country is "an independent, self-governing, political entity."
Definition Source	Country Name: New Country: Framework Data Content Standard Part 5: Governmental Unit and Other Geographic Area Boundaries," (Table 13)
Data Type	characterString
Existing Standards for this Element	ISO 3166-1: Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes
Domain of Values for this Element	ISO 3166-1 short English country names, ISO 3166-1-alpha-2 (two-letter abbreviations), or ISO 3166-1-alpha-3 (three-letter abbreviations.
Source of Values	ISO 3166-1: Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes
How Defined (eg, locally, from standard, other)	ISO 3166-1: Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes
Example	1. United States (US, USA) 2. Canada (CA, CAN) 3. Mexico (MX, MEX)
Notes/Comments	1.Although the scope of this standard is restricted to US addresses, Country Name is included for two reasons: to facilitate reconciliation with address standards of other nations, and to accommodate files which mix addresses from the US and other countries. 2. There are several standards for country names. ISO 3166-1 is specified because it is in wide use internationally, it is recognized within the the UPU address standard (and therefore by the USPS) for postal addressing, and it used by some US federal agencies for administrative purposes. 3. ISO 3166-1 provides several representations of Country Names. This standard recognizes three: the short English names, the 2-letter abbreviations (ISO 3166-1-alpha-2), and the 3-letter abbreviations (ISO 3166-1-alpha-3). 4. ISO 3166-1 is protected by ISO copyright. The ISO states, "The short country names from ISO 3166-1 and the alpha-2 codes are made available by ISO at no charge for internal use and non-commercial purposes." The ISO makes no such grant for the three-letter abbreviations. 5. The official short English names are preferred within this standard for storage and recording of Country Names because they are familiar and concise, they cannot be mistaken for US State Name abbreviations, they are required by the USPS for postal addressing, and they are made available to the public by the ISO at no cost for internal and non-commercial purposes. 6. The two-letter abbreviations are recognized but not preferred within this standard because some country name abbreviations are identical to two-letter State Name abbreviations (e.g., CA = Canada and California; CO = Colombia and Colorado). 7. The ISO three-letter abbreviations are recognized but not preferred within this standard because the ISO makes them available only by purchase, and ISO copyright terms do not permit their free use even for internal or non-commercial purposes. (However, the three-letter abbreviations are published in non-authoritative sources including Wikipedia ( http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3 ) and the United States Central Intelligence Agency's The World Factbook (Appendix D) ( https://www.cia.gov/library/publications/the-world-factbook/appendix/appendix-d.html )). 8. Part 6 of this standard gives a complete reference for ISO 3166-1 and states where the short English names and two-letter abbreviations can be found.
XML Tag	< CountryName >
XML Model	<xsd:simpleType id="CountryName_type"> <xsd:restriction base="xsd:string" /> </xsd:simpleType>
XML Example	<CountryName>CANADA</CountryName>
Quality Measures	TabularDomainMeasure SpatialDomainMeasure
Quality Notes

DeliveryAddress

Element Name	DeliveryAddress
Other common names for this element	Delivery Address Line (USPS Publication 28); Location Address Text (EPA); Mailing Address Text (EPA)
Definition	The entire address, unparsed, except for the Place Name, State Name, Zip Code, Zip Plus 4, Country Name, and, optionally, Complete Subaddress.
Syntax	The Delivery Address syntax depends on the address class. Address class syntaxes are given in the Classification Part of this standard. The Delivery Address syntax is the same as the class syntax, except that the Delivery Address excludes the Place Name, State Name, Zip Code, Zip Plus 4, Country Name, and, optionally, Complete Subaddress.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	USPS Publication 28
Domain of Values for this Element	No
Source of Values	NA
How Defined (eg, locally, from standard, other)	NA
Attributes Associated with this Element	Delivery Address Type
Example	Numbered Thoroughfare Address: 123 Dartmouth College Highway, Suite 100, Lyme, NH 03768 (Delivery Address Type = Subaddress Included) Jones Hall, 123 Dartmouth College Highway, Suite 100, Lyme, NH 03768 (Delivery Address Type = Subaddress Excluded) Intersection Address: West Street & Main Street, Newtown, CT Two Number Address Range: 1400-1420 Smith Street, West Monroe, LA 71292 Unnumbered Thoroughfare Address: East End Road, St. Croix, VI 00820 Landmark Address: Langston Housing Complex, Building 7, Apartment 290, Kansas City KS 66101 Community Address: 1234 Urbanizacion Los Olmos, Ponce PR 00731 Postal Delivery Box: PO BOX 16943, New Orleans LA 70112 USPS Postal Delivery Route: HC 68 BOX 23A, Natchez, MS USPS General Delivery: GENERAL DELIVERY, TAMPA FL 33602-9999.
Notes/Comments	1. The Delivery Address element corresponds to the Delivery Address Line defined in USPS Publication 28 (sec. 211, 231, 33, 341, and 343). 2. This element excludes Place Name, State Name, Zip Code, and Zip Plus 4 and Country Name, which together form the Place State ZIP complex element. 3. The Delivery Address typically includes the Complete Subaddress. However, there are sometimes reasons to omit or separate the Complete Subaddress from the Delivery Address. For example, the Complete Subaddress can hamper address geocoding, and contact lists often separate the Complete Subaddress from the rest of the feature address (see, e.g., the EPA Contact Information Data Standard). 4. The Delivery Address Type shows whether the Delivery Address includes or excludes the Complete Subaddress.
XML Tag	< DeliveryAddress >
XML Model	<xsd:complexType id="DeliveryAddress_type"> <xsd:extension base="xsd:string"> <xsd:attribute id="DeliveryAddressType" type="addr_type:DeliveryAddressType_type" /> </xsd:extension> </xsd:simpleContent> </xsd:complexType>
XML Example	<DeliveryAddress Delivery Address Type="Subaddress Included">123 Dartmouth College Highway, Suite 100</DeliveryAddress> <DeliveryAddress Delivery Address Type="Subaddress Excluded">123 Dartmouth College Highway, Suite 100</DeliveryAddress> <DeliveryAddress>123 Dartmouth College Highway, Suite 100</DeliveryAddress>
Quality Measures	Pattern Sequence Measure
Quality Notes

LandmarkName

Element Name	Landmark Name
Other common names for this element	Point of interest
Definition	The name of a relatively permanent feature of the manmade landscape that has recognizable identity within a particular cultural context.
Definition Source	Adapted from U.S. Board on Geographic Names, "Principles, Policies, Procedures," (Online Edition (revised), 2003, as posted May 17, 2006 at http://geonames.usgs.gov/docs/pro_pol_pro.pdf ), p. 48, definition of "geographic name".
Data Type	characterString
Existing Standards for this Element	None, but see GNIS Feature ID
Domain of Values for this Element	Can be created locally from existing values.
Source of Values	Local
How Defined (eg, locally, from standard, other)	Locally
Attributes Associated with this Element	Element Sequence Number, GNISFeature ID
Examples	1. U.S. Capitol Building 2. Empire State Building 3. Winonna Park Elementary School 4. Valley Mall 5. Yosemite National Park
Notes/Comments	1. A Landmark Name specifies a location by naming it. It does not relate the named feature to any thoroughfare system or coordinate reference system and therefore provides no information about where to find the feature. Many addresses include Landmark Names without any thoroughfare names, and as such Landmark Names form the basis for two address classes: Landmark Address and Community Address. 2. Landmark names are given to both natural and manmade features. In general, natural landmark names are not used in addresses and are therefore excluded from the scope of this standard. Thus "Yosemite National Park" could be part of an address, and therefore is within the scope of the standard, whereas "Yosemite Falls" and "Yosemite Valley" (naming the natural features) would not. 3. The difference between Landmark Name and a Place Name is not always clear and distinct. As a general principle, a landmark is under a single use or ownership or control, while places are not. Thus a landmark, even if it covers an extensive area, might be considered to be a single "master address" (often containing multiple subordinate addresses), while a place generally includes numerous separate addresses. These general principles apply to most cases and are useful as general distinctions, but exceptions and marginal cases are easily found. 4. Local address authorities may wish to compile a list of locally-recognized Landmark Names used as addresses for their convenience. Whether to do so, and if so what names to include, are implementation matters to be decided locally. 5. Most named landmarks that are used as addresses are also designated by one or more thoroughfare addresses. These should be cross-referenced to each other as Related Address IDs, using the Address Relation Type attribute to record the relationship between them. 6. Landmark Name, as used in this standard, does not imply any officially-designated historic landmark status, nor is it restricted to features having such status. 7. The U.S. Board on Geographic Names has compiled and standardized names for many landmarks in the Geographic Names Information System (GNIS), each identified by a unique GNISFeature ID. Local authorities are encouraged to review the GNISFeature ID for more information on the use of the GNIS ID with Landmark Names. 8. The U.S. Board on Geographic Names has defined 65 classes of features for use in classifying features listed in GNIS. These classes, while neither exhaustive nor necessarily definitive for addressing purposes, may provide useful guidance in distinguishing Place Names, manmade Landmark Names, and natural landmark names. ---Manmade landmark classes (the names of these features are often used in addresses and therefore generally within the scope of this standard): airport, bridge, building, canal, cemetery, church, crossing, dam, harbor, hospital, levee, locale, military, mine, oilfield, park, post office, reserve, reservoir, school, tower, trail, tunnel, well. ---PlaceName classes (the names of these features are generally Place Names within this standard): Census, civil, populated place. ---Natural landmark classes (the names of these features are generally outside the scope of this standard): arch, area, arroyo, bar, basin, bay, beach, bench, bend, cape, cave, channel, cliff, crater, falls, flat, forest, gap, glacier, gut, island, isthmus, lake, lava, pillar, plain, range, rapids, ridge, sea, slope, spring, stream, summit, swamp, valley, woods. The complete feature class definitions can be found from the GNIS Domestic Names search page. See Part 6 (U.S. Geological Survey) for a complete citation.
XML Tag	<LandmarkName>
XML Model	<xsd:complexType id="LandmarkName_type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute id="ElementSequenceNumber" type="addr_type:ElementSequenceNumber_type" /> </xsd:extension> </xsd:simpleContent> </xsd:complexType>
XML Example	<CompleteLandmark> <LandmarkName>YOSEMITE NATIONAL PARK</LandmarkName> </CompleteLandmark>
Quality Measures	UniquenessMeasure TabularDomainMeasure SpatialDomainMeasure
Quality Notes	Some landmarks will be nested within a larger one, the latter constituting a spatial domain. Similarly, a tabular domain may be associated with an outer landmark.

PlaceName

Element Name	Place Name
Other common names for this element	Unincorporated community or neighborhood: Community, neighborhood, subdivision, district, ward, borough (in, for example, New York City); Barrio, sector, urbanization, parcela, extension, mansion, reparto, villa, parque, jardine, urbanizacion place name (Puerto Rico); Census designated place, populated place (GNIS), locale (GNIS) Incorporated local government: Municipality, city, borough, town, village, township, actual city, location city, situs city, municipal place name, minor civil division, corporation, consolidated government, metropolitan government, unified government, populated place (GNIS), locale (GNIS) USPS Post Office Name: Post office, mailing city, city (as in "City, State, ZIP"), city name; APO, FPO, DPO (for overseas US military and diplomatic mail delivery) County: Parish (Louisiana); Census Area, City and Borough, and Unorganized Borough (Alaska); Municipality (Alaska and the Commonwealth of the Northern Mariana Islands), Municipio (Puerto Rico), City (Maryland, Missouri, Nevada, and Virginia), District (DC and American Samoa), Island (American Samoa and U.S. Virgin Islands) Region: Metropolitan area, metropolitan statistical area (Census), consolidated metropolitan statistical area (Census), primary metropolitan statistical area (Census)
Definition	The name of an area, sector, or development (such as a neighborhood or subdivision in a city, or a rural settlement in unincorporated area); incorporated municipality or other general-purpose local governmental unit; county or county-equivalent; or region within which the address is physically located; or a name recognized by the U.S. Postal Service for delivery of mail to the address.
Definition Source	New; partly adapted from: 1. FGDC's "Framework Data Content Standard Part 5: Governmental unit and other geographic area boundaries"; and, 2. USPS Publication 28, Section 292, "Urbanization".
Data Type	characterString
Existing Standards for this Element	No single controlling authority, but the Geographic Names Information System (GNIS) attempts to include and standardize the names of all populated places and incorporated local governments (see GNISFeature ID). For USPS Post Office names, the controlling authority is the USPS "City State File" as referenced in Section 221 of USPS Publication 28
Domain of Values for this Element	None (but see existing standards above). Can be created locally from existing values.
Source of Values	Locally determined (but see existing standards above)
How Defined (eg, locally, from standard, other)	Locally.
Attributes Associated with this Element	Place Name Type, Element Sequence Number, GNISFeature ID
Examples	Ajo, AZ (unincorporated community in Pima County, AZ) Urbanizacion Los Pinos (Puerto Rican urbanization) Barrio Miraflor (Puerto Rican barrio) Portola Valley, CA (incorporated town) Birmingham, AL (city) Salt Lake City, UT (city) Queens (New York City borough) Orleans Parish, LA (county) APO AE (overseas military postal delivery) FPO AP (overseas military postal delivery) DPO AE (overseas US State Department postal delivery)
Notes/Comments	1. "Place name" can mean different things to different people in different contexts. It may name a community, an incorporated local government, a post office, a county, or a region. For many thoroughfare and landmark addresses, a different place name may be used by an emergency dispatcher directing an ambulance, a local government official assessing local taxes or eligibility for services, a postal clerk, or a business providing contact information on its website. 2. This standard provides the Place Name Type attribute to allow the use of different place names with the same address for different purposes. Five types are defined: unincorporated community or neighborhood, incorporated local government, U.S. Post Office name, county, and region. Other types may be added. Additional explanation is given in the notes below and under Place Name Type. 3. The U.S. Board of Geographic Names has assigned GNIS Codes to all place names that have been registered and accepted by the Board. This standard provides the GNISFeature ID attribute to accommodate those codes. For more information on GNIS, see GNISFeature ID or http://geonames.usgs.gov/domestic/index.html . Notes on Community Names: 1. A community name refers to an area, sector, or development, such as a neighborhood or subdivision in a city, or a rural settlement in unincorporated area, that is not an incorporated general-purpose local government or county. The name may arise from official recognition or from popular usage. 2. Numerous different terms are used to denote different kinds of communities and community names, but the distinctions are not particularly significant in constructing addresses. An extensive list of terms and definitions can be found in "Framework Data Content Standard Part 5: Governmental unit and other geographic area boundaries," Tables 11 and 15. 3. Community names are of particular importance in Puerto Rican addresses. Street names and address ranges are repeated in many Puerto Rican municipios (county equivalents); these repeated addresses are distinguished from each other by their community name. Administratively, Puerto Rican municipios are divided into barrios and sectors. Smaller areas, such as urbanizacions and parcelas, may be recognized locally, and all of them may be used in locating an address. For postal addressing, repeated addresses are distinguished from each other by their urbanizacion or equivalent community name. For more information on postal addressing standards for Puerto Rico, see USPS Publication 28 Section 29, and USPS Addressing Standards for Puerto Rico and the Virgin Islands (especially sections 2 and 5). Notes on Municipal and County Place Names: 1. County and municipal names indicate the county and the general-purpose local government area (if any) in which the address is physically located. Local government types and terminologies vary substantially from state to state, but the distinctions are not particularly significant in constructing addresses. An extensive list of terms and definitions can be found in "Framework Data Content Standard Part 5: Governmental unit and other geographic area boundaries," Table 13. 2. Exact municipal and county names are required by public administrators for correct assessing local taxes, assignment of voting precinct, school enrollment, and provision of local government services. 3. Addresses in unincorporated portions of counties have no municipal place name by definition. 4. Many governments have a legal name and a popular name ("Saint Paul" vs. "City of Saint Paul"). For addressing, the popular name is generally preferable if it is unique within the county and state. 5. New York City is comprised of five administrative boroughs (Bronx, Brooklyn, Manhattan, Queens, and Staten Island). The boroughs are legally distinct from the five counties that are also subdivisions of New York City (Bronx, Kings, New York, Queens, and Richmond) even though the boroughs and counties have identical boundaries and two even share the same name. Notes on USPS Place Names: 1. The USPS place name is a place name listed in the USPS City State File for delivery of mail to an address. 2. USPS place names are preferred for postal operations. However, they are often not the best-suited place names for non-postal purposes such as navigation, public service delivery, and emergency response. 3. For postal purposes, the USPS strongly discourages the use of multiple place names in an address. For example, the USPS on-line ZIP finder will find a ZIP code for an address in ""Wailuku, HI," but not for "Wailuku, Maui, HI." 4. For overseas US military postal addresses, "APO" (Army Post Office) or "FPO" (Fleet Post Office) is used as the Place Name (see USPS Publication 28, Section 225.1 and 238.1). "DPO" (Diplomatic Post Office) is used as the Place Name for some overseas US State Department postal addresses (see USPS Pub 28 Sec. 239). Notes on Regional Place Names: 1. A region name refers to the region where the address is physically located. Typically this is the name of the central city within the region. For precise, systematic terms, U.S. Census Bureau terms and definitions may be applied, but popular usage is often imprecise and to some extent subjective. Businesses and residents near a regional center often use the central-city name in their address, even if the address is located some distance outside the limits of the city itself.
XML Tag	< PlaceName >
XML Model	<xsd:complexType id="PlaceName_type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute id="PlaceNameType" type="addr_type:PlaceNameType_type" /> <xsd:attribute id="ElementSequenceNumber" type="addr_type:ElementSequenceNumber_type" /> <xsd:attribute id="GNISFeatureID" type="addr_type:GNISFeatureID_type" /> </xsd:extension> </xsd:simpleContent> </xsd:complexType>
XML Example	<PlaceName>ORLEANS PARISH</PlaceName>
Quality Measures	TabularDomainMeasure SpatialDomainMeasure
Quality Notes	Some place names will be nested within a larger one, the latter constituting a spatial domain. Similarly, a tabular domain may be associated with an outer place name.

PlaceStateZIP

Element Name	PlaceStateZIP
Other common names for this element	Last Line (USPS)
Definition	The combination of Complete Place Name, State Name, Zip Code, Zip Plus 4, and Country Name within an address. Complete Place Name and State Name are mandatory; the other elements are optional.
Syntax	{ Complete Place Name } + { State Name } + { Zip Code } + { Zip Plus 4 } + { Country Name }
Definition Source	New
Data Type	characterString
Existing Standards for this Element	Refer to component elements
Domain of Values for this Element	Refer to component elements
Source of Values	Refer to component elements
How Defined	Refer to component elements
Example	1. Waterville ME 04901 2. Oxford MS 38655-4068 3. Florence, OR 4. Brattleboro, Windham County, VT
Notes/Comments	1. Place State ZIP corresponds to the Last Line (or City, State, ZIP+4 line) as defined for postal addressing purposes in USPS Publication 28 (secs 211, 33, and 341). 2. Zip Code and Zip Plus 4 are recommended but not mandatory in the Place State ZIP element.
XML Tag	< PlaceStateZIP >
XML Model	<xsd:simpleType id="PlaceStateZip_type"> <xsd:restriction base="xsd:string"> <xsd:pattern value='.*' /> </xsd:restriction> </xsd:simpleType>
XML Example	<PlaceStateZIP>Brattleboro, Windham County, VT</PlaceStateZIP>
Quality Measures	Pattern Sequence Measure
Quality Notes

SeparatorElement

Element Name	SeparatorElement
Other common names for this element
Definition	A word, phrase, or symbol used as a separator between components of a complex element or class. The Separator Element is required for Intersection Addresses and for Two Number Address Ranges, and it may be used in constructing a Complete Street Name.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	None
Domain of Values for this Element	None. Typical values may include: 1. For Two Number Address Ranges: - (hyphen)(spaces optional before or after) 2. For Intersection Addresses: "and", "at", "@", "&", and "&&" "+","-", and "y" or "con" (Spanish) each having a space before and after. 3. For Complete Street Names: If a Complete Street Name includes a prepositional phrase between a Street Name Pre Type and a Street Name, the prepositional phrase is treated as a separator: "of the", "de la", "des", etc.
Source of Values	New
How Defined (eg, locally, from standard, other)	Locally.
Example	1. Two Number Address Range (hyphen): 206 - 210 Fourth Street 2. Intersection Address ("and"): Eighth Street and Pine Street. 3. Complete Street Name :("of the", "de las" and "des") Avenue of the Americas, Alameda de las Pulgas; Rue des Etoiles.
Notes/Comments	1. Separator Elements are special words, phrases, or symbols used to separate certain component elements when composing Two Number Address Ranges, Intersection Addresses, or used in constructing a Complete Street Name. 2. The default separator, an empty space, is implicit and is not shown in the syntaxes of complex elements and classes. Where the default separator is specifically not used, the Attached Element attribute is provided to indicate that two elements are not separated with a space. 3. Two Number Address Range. In the Two Number Address Range, the hyphen separating the low and high Complete Address Numbers is a Separator Element. 4. Intersection Addresses. A Separator Element separates the Complete Street Names in an Intersection Address. Separator values include " and ", at , @ , " & ", and " && " " + "," - ", and " y " or " con " (Spanish), each having a space before and after. Other values may also be in use. Within a given dataset, one value should be used consistently. (Some address parsing software permits the use of ampersands ("&" or "&&") to signify intersection addresses. Be wary, though--in many programming languages, ampersands are reserved for other uses, which could complicate data exchange.) 5. Complete Street Name. If a prepositional phrase appears between the Street Name Pre Type and the Street Name, the prepositional phrase is a Separator Element: Avenue of the Americas, Alameda de las Pulgas, Rue des Etoiles. Such constructions are rare in English-language Complete Street Names, but they are common in Spanish- , Italian- and French-language Complete Street Names.
XML Tag	Separator
XML Model:	<xsd:simpleType id="Separator_type"> <xsd:restriction base="xsd:string"> <xsd:pattern value='.*' /> </xsd:restriction> </xsd:simpleType>
XML Example:	<IntersectionAddress Separator="and" > <CompleteStreetName> <StreetName>EIGHTH</StreetName> <StreetNamePostType>STREET</StreetNamePostType> </CompleteStreetName> <CompleteStreetName> <StreetName>PINE</StreetName> <StreetNamePostType>STREET</StreetNamePostType> </CompleteStreetName> <PlaceName PlaceNameType="USPSCommunity">ELLICOT CITY</PlaceName> <StateName>MD</StateName> <ZipCode>21043</ZipCode> </IntersectionAddress> <AddressNumberRange Separator=" - " > <CompleteAddressNumber> <AddressNumber>206</AddressNumber> </CompleteAddressNumber> <CompleteAddressNumber> <AddressNumber>210</AddressNumber> </CompleteAddressNumber> </AddressNumberRange> <CompleteStreetName> <StreetNamePreType>AVENUE</StreetNamePreType> <StreetName Separator="of the" >AMERICAS</StreetName> </CompleteStreetName> <CompleteStreetName> <StreetNamePreType>ALAMEDA</StreetNamePreType> <StreetName Separator="de las" >PULGAS</StreetName> </CompleteStreetName> <CompleteAddressNumber> <AddressNumber>61</AddressNumber> <AddressNumberSuffix Separator="-" >43</AddressNumberSuffix> </CompleteAddressNumber>
XML Notes:	This entity must be expressed as an empty string to indicate an empty string. Omitting the entity entirely indicates that a space is acceptable.

StateName

Element Name	State Name
Other common names for this element	State; Commonwealth (PA, MA, KY, VA, PR, MP); Territory (AS, GU, MP, PR, VI); District (DC); Minor Outlying Islands (UM); overseas military or diplomatic "state" (AA, AE, AP)
Definition	The names of the US states and state equivalents: the fifty US states, the District of Columbia, and all U.S. territories and outlying possessions. A state (or equivalent) is "a primary governmental division of the United States." The names may be spelled out in full or represented by their two-letter USPS or ANSI abbreviation.
Definition Source	Names and abbreviations: ANSI INCITS 38:2009, and USPS Publication 28 Appendix B Definition of 'state": Framework Data Content Standard Part 5: Governmental Unit and Other Geographic Area Boundaries," (Table 13).
Data Type	characterString
Existing Standards for this Element	ANSI INCITS 38:2009, and USPS Publication 28 Appendix B
Domain of Values for this Element	Yes
Source of Values	ANSI INCITS 38:2009, and USPS Publication 28 Appendix B
How Defined (eg, locally, from standard, other)	ANSI INCITS 38:2009, and USPS Publication 28 Appendix B
Example	Chicago, Illinois Chicago IL Dover, Delaware Dover DE Hagatna, Guam Hagatna GU APO AE Wake Island UM
Notes/Comments	1. The State Name element follows the ANSI INCITS 38:2009 standard (formerly the FIPS 5-2 standard) and USPS Publication 28 by including within the definition of State Name the fifty US states, the District of Columbia (DC), and US territories and possessions (AS, GU, MP, PR, and VI). In addition, USPS Publication 28 recognizes three overseas military and diplomatic State Name equivalents (AA, AE, and AP), which the ANSI standard does not; and the ANSI standard recognizes "UM" for US minor outlying islands, which USPS Publication 28 does not. 2. Within this standard State Names may be spelled out in full or they may be represented by their standard two-letter ANSI INCITS 38:2009 or USPS abbreviations. 3. For overseas military and diplomatic postal addresses, "AE" or "AP" or "AA" is used as the State Name. "AE" is used for armed forces and certain diplomatic posts in Europe, the Middle East, Africa, and Canada; "AP" for the Pacific; and "AA" for the Americas excluding Canada (see USPS Publication 28, Section 225.1 and Appendix B). 4. The ANSI INCITS 38:2009 standard abbreviations include the abbreviation UM for U.S. Minor Outlying Islands. These are nine small, remote islands or island groups that do not receive direct mail delivery: Midway Islands, Wake Island, Johnson Atoll, Kingman Reef, Palmyra Atoll, Jarvis Island, Howland Island, Baker Island, and Navassa Island. 5. In rare cases, the postal state and the physical location state of the address are not the same. This occurs in some communities on the borders of two states. In these cases, the physical address should be treated as the primary or official address, including the physical state name, while the postal address with its state name should be listed as an alias.
XML Tag	< StateName >
XML Model	<xsd:simpleType id="StateName_type"> <xsd:restriction base="xsd:token"> <!-- "US State and The District of Columbia" Abbreviations --> <xsd:pattern value='.*' /> </xsd:restriction> </xsd:simpleType>
XML Example	<StateName>VA</StateName> <StateName>VIRGINIA</StateName>
Quality Measures	TabularDomainMeasure SpatialDomainMeasure
Quality Notes

StreetName

Element Name	Street Name
Other common names for this element	Primary Street Name, Base Name (Census TIGER)
Definition	The portion of the Complete Street Name that identifies the particular thoroughfare (as opposed to the Street Name Pre Modifier, Street Name Post Modifier, Street Name Pre Directional, Street Name Post Directional, Street Name Pre Type, Street Name Post Type, and Separator Element (if any) in the Complete Street Name.)
Definition Source	Adapted from FGDC Draft Address Data Content Standard v. 3 (citing Census)
Data Type	characterString
Existing Standards for this Element	Section 232 of USPS Publication 28
Domain of Values for this Element	Official list of street names maintained by local authority.
Source of Values	Local
How Defined	Defined by local ordinance
Example	Main Street MacIntyre Drive Boston-Providence Turnpike Third Avenue 3rd Avenue Avenue of the Americas East 400 South
Notes/Comments	1. The Street Name is the word or words used to identify a thoroughfare or a portion thereof, excluding any types, directionals, or modifiers in the Complete Street Name. 2. Every Complete Street Name must include a Street Name. The Street Name field cannot be null in any Complete Street Name. 3. Spelling Consistency: Internal Capitalization, Apostrophes, Hyphens, Spaces Local addressing authorities are urged to follow consistent internal street naming practices, and to resolve internal street name inconsistencies, especially for internal capitalization, hyphens, and apostrophes. Example: MacIntyre, McIntyre, Mc Intyre, Mcintyre Example: Smiths Lane, Smiths Lane Example: Boston Providence Turnpike; Boston-Providence Turnpike; Rule: Follow the spelling adopted by the local street naming authority. Discussion: This standard cannot specify local naming conventions. 4. State Names Not Abbreviated When Used as Street Names: Example: Pennsylvania Avenue (not "PA Avenue") Rule: Where a Street Name is the name of a State of the United States, the Street Name must be spelled out in full, not abbreviated. 5. Numbered Streets Examples: Third Street, 3rd Street, 3 Street Rule: Use the name exactly as given by the local street naming authority. Discussion: This standard cannot specify local naming conventions. Different jurisdictions follow different practices for numbered street names. Pittsburgh spells out First through Twelfth and uses ordinal numbers (13th, 14th, etc.) for higher numbers. Washington DC uses ordinal numbers only (1st, 2nd, etc.). Other jurisdictions have their own conventions. This is a matter for local authorities to decide. 6. Inclusion of Street Type and Directional Words in Street Names Examples: Court Place, Lane Park Circle, West Virginia Avenue Discussion: Street Names may, in certain instances, contain words that are also used as Street Name Pre Directionals, Street Name Post Directionals, Street Name Pre Types, or Street Name Post Types, See Complete Street Name for a general discussion of street name parsing principles. 7. Documentation of Local Street Naming Rules Local street naming authorities typically have rules by which they assign or prohibit Street Names in their area of jurisdiction. These rules should be documented in the Address Reference System Street Naming Rules.
XML Tag	< StreetName >
XML Model	<xsd:simpleType id="StreetName_type"> <xsd:restriction base="xsd:string"> <xsd:pattern value='.*' /> </xsd:restriction> </xsd:simpleType>
XML Example	<CompleteStreetName> <StreetName>CENTRAL</StreetName> <StreetNamePostType>STREET</StreetNamePostType> <StreetNamePostDirectional>SOUTHWEST</StreetNamePostDirectional> </CompleteStreetName> <CompleteStreetName> <StreetName>BOSTON-PROVIDENCE</StreetName> <StreetNamePostType>HIGHWAY</StreetNamePostType> </CompleteStreetName>
Quality Measures	TabularDomainMeasure SpatialDomainMeasure
Quality Notes	In some cases a jurisdiction may have associated a given area with a type of street name: alpha characters, trees, flowers, birds, etc. Where such a scheme exists, along with the geometry for both the streets and the spatial domain, SpatialDomainMeasure can be used to test conformance.

StreetNamePostDirectional

Element Name	Street Name Post Directional
Other common names for this element	Postdirectional (USPS), Post Directional, Post-direction, Postdir, Suffix Directional, Suffix Direction (Census TIGER), Street Suffix (NFIRS)
Definition	A word following the Street Name that indicates the direction or position of the thoroughfare relative to an arbitrary starting point or line, or the sector where it is located.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	USPS Publication 28 Sections 233, 294 and Appendix B
Domain of Values for this Element	English: East, West, South, North, Northeast, Southeast, Southwest, Northwest Spanish: Este, Oeste, Sur, Norte; Noreste, Sureste, Suroeste, Noroeste Equivalent words in other languages
Source of Values	USPS Publication 28 Sections 233, 294 and Appendix B (unabbreviated)
How Defined	As provided by USPS Publication 28 Sections 233, 294 and Appendix B
Examples	Cherry Street North North Avenue Southwest East 400 South
Notes/Comments	1. A Street Name Post Directional is a word following the Street Name that indicates the direction or position of the thoroughfare relative to an arbitrary starting point or line, or the sector where it is located. 2. A Complete Street Name may include a Street Name Pre Directional, a Street Name Post Directional, neither, or both. 3. To avoid confusion, this standard requires that Street Name Post Directionals be recorded and stored fully spelled out. Abbreviations can cause ambiguity. For example: "N Avenue W"-- Is it "North Avenue W"? "N Avenue West"? "North Avenue West"? For this reason the standard does not recognize abbreviations for Street Name Post Directionals. If stored unabbreviated, directionals can be exported as abbreviations when needed for special purposes such as mailing labels. 4.For postal addressing, USPS Publication 28 prefers the use of USPS standard abbreviations for Street Name Post Directionals. USPS Publication 28 sections 233, 294, and Appendix B provide the USPS abbreviations for Street Name Post Directionals in English and Spanish. USPS standard abbreviations are recognized within the Postal Addressing Profile of this standard. 5. Directional words are often used as or in the Street Name (e.g. "Avenue North"). Whether a directional word should be placed in the Street Name Post Directional or the Street Name cannot always be discerned from the Complete Street Name itself. Sometimes the proper parsing must be inferred from the context of the street name, or checked with the street naming authority. See Complete Street Name notes for a discussion of this and other cases where a Complete Street Name might be parsed in more than one way. 6. Occasionally two directional words occur together in or after the Street Name (e.g. "Boulevard South Southwest", "Pharr Court South Northeast"). Only one of them can be the Street Name Post Directional. The other one might be part of the Street Name, or it may be a Street Name Post Modifier. See Complete Street Name notes for a discussion of this and other cases where a Complete Street Name might be parsed in more than one way. 7. Local street naming authorities often have rules governing the use of Street Name Post Directionals in their area of jurisdiction. These rules should be documented in their Address Reference System Street Type Directional And Modifier Rules.
XML Tag	< StreetNamePostDirectional >
XML Model	<xsd:complexType id="StreetNamePostDirectional_type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute id="Separator" type="addr_type:Separator_type"></xsd:attribute> </xsd:extension> </xsd:simpleContent> </xsd:complexType>
XML Example	<CompleteStreetName> <StreetName>CHERRY</StreetName> <StreetNamePostType>STREET</StreetNamePostType> <StreetNamePostDirectional>NORTH</StreetNamePostDirectional> </CompleteStreetName> <CompleteStreetName> <StreetName>NORTH</StreetName> <StreetNamePostType>AVENUE</StreetNamePostType> <StreetNamePostDirectional>WEST</StreetNamePostDirectional> </CompleteStreetName>
Quality Measures	TabularDomainMeasure SpatialDomainMeasure
Quality Notes	1. TabularDomainMeasure can test entries against a tabular domain. 2. In cases where an address scheme designates particular areas as corresponding with a given Street Name Post Directional and the geometry for both the streets and the address scheme's spatial domain, SpatialDomainMeasure can test the entries.

StreetNamePostModifier

Element Name	StreetNamePostModifier
Other common names for this element	Suffix Qualifier (Census TIGER)
Definition	A word or phrase in a Complete Street Name that follows and modifies the Street Name, but is separated from it by a Street Name Post Type or a Street Name Post Directional or both.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	No
Domain of Values for this Element	No
Source of Values	Local
How Defined (eg, locally, from standard, other)	Locally
Example	East End Avenue Extended Banner Fork Road Number 1 Horizon Lane West Southeast
Notes/Comments	1. A Street Name Post Modifier follows and modifies a Street Name, but is separated from the Street Name by a Street Name Post Type or a Street Name Post Directional or both. Any word or phrase of a Complete Street Name that follows the Street Name Post Directional (or that follows the Street Name Post Type, if the Complete Street Name has no Street Name Post Directional) comprises the Street Name Post Modifier. 2. If a Complete Street Name includes two or more consecutive directional words following the Street Name, the first is parsed as a Street Name Post Directional, and the rest are parsed as the Street Name Post Modifier. See Complete Street Name notes for a general discussion of Complete Street Name parsing principles. 3. Street Name Post Modifiers are not common. Census Bureau TIGER Technical Documentation (Appendix D) lists the following examples of words that are often Street Name Post Modifiers: Access, Alternate, Business, Bypass, Connector, Extended, Extension, Loop, Private, Public, Scenic, Spur, Ramp, Underpass, Overpass. (Note that most of these words are also used as Street Name Post Types). 4. USPS Publication 28 does not recognize Street Name Post Modifiers. USPS Publication 28 standards are recognized within the Postal Addressing Profile of this standard.
XML Tag	< StreetNamePostModifier >
XML Model	<xsd:complexType id="StreetNamePostModifier_type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute id="Separator" type="addr_type:Separator_type"></xsd:attribute> </xsd:extension> </xsd:simpleContent> </xsd:complexType>
XML Example	<CompleteStreetName> <StreetName>GRAND</StreetName> <StreetNamePostType>BOULEVARD</StreetNamePostType> <StreetNamePostModifier>CUTOFF</StreetNamePostModifier> </CompleteStreetName> <CompleteStreetName> <StreetName>CONCORD</StreetName> <StreetNamePostType>HIGHWAY</StreetNamePostType> <StreetNamePostModifier>EXTENSION</StreetNamePostModifier> </CompleteStreetName>
Quality Measures	TabularDomainMeasure SpatialDomainMeasure
Quality Notes	1. Where a specific set of postmodifiers are specified for use, they may be maintained as a domain and tested with TabularDomainMeasure. 2. Where a schema may designate a particular area with a Street Name Post Modifier the entries may be tested with SpatialDomainMeasure.

StreetNamePostType

Element Name	Street Name Post Type
Other common names for this element	Street Type, Street Suffix, Street Suffix Type, Suffix (USPS), Suffix Type (Census TIGER)
Definition	A word or phrase that follows the Street Name and identifies a type of thoroughfare in a Complete Street Name.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	Section 234 and Appendix C1 of USPS Publication 28 with provision for local additions
Domain of Values for this Element	USPS Publication 28 Appendix C1 with provisions for local additions.
Source of Values	Section 234 and Appendix C1 of USPS Publication 28 with provision for local additions.
How Defined	Locally
Example	Main Street MacIntyre Drive Boston-Providence Turnpike Third Avenue 3rd Avenue Avenue C Loop Tenth Street Bypass Lee Highway Access Road
Notes/Comments	1. A Street Name Post Type is a word or phrase that follows the Street Name and identifies a type of thoroughfare in a Complete Street Name. In English-language Complete Street Names, most Street Name Pre Type words are also found as Street Name Post Types. 2. A Complete Street Name usually includes either a Street Name Pre Type or a Street Name Post Type. Occasional Complete Street Names have neither ("Broadway") or both ("Avenue C Loop"). 3. Street Type words are often used as or in the Street Name (e.g. "Park Lane Circle"). Whether a type word should be placed in the Street Name Post Type or the Street Name cannot always be discerned from the Complete Street Name itself. Sometimes the proper parsing must be inferred from the context of the street name, or checked with the street naming authority. See Complete Street Name notes for a discussion of this and other cases where a Complete Street Name might be parsed in more than one way. 4. Occasionally two or more type words occur together after the Street Name (e.g., "Tenth Street Bypass"). All of the words are placed in the Street Name Post Type, unless the Address Authority has included any of them in the Street Name. If the type words are not part of the Street Name and are not separated from each other by a directional word or other word, they are all placed in the Street Name Post Type. See Complete Street Name notes for a discussion of this and other cases where a Complete Street Name might be parsed in more than one way. 5. To avoid confusion, this standard does not recognize any abbreviations for Street Name Post Types. This standard requires that Street Name Post Types be recorded and stored fully spelled out. Various inconsistent sets of abbreviations are in use, for various purposes, and none is exhaustive. USPS Publication 28 Appendix C1 contains the best-known list of street type abbreviations.National Fire Incident Reporting System (NFIRS) has a slightly different list. Local utilities might use other lists, and various software vendors have incorporated still other lists into their products.Terrace might be abbreviated as "Ter", "Terr", or "Tr". "Tr" might stand for terrace, trail, trace, or track. Any number of different abbreviation sets might be used for given operations or applications within an agency or firm. Therefore Street Name Post Types should be stored unabbreviated, and related to look-up tables of abbreviations so that the proper set of abbreviations can be applied in views or export routines when needed for specific purposes such as mailing labels or 9-1-1 files. 6. The USPS recognizes only the Street Name Post Types listed in USPS Publication 28 Appendix C1. For postal addressing, the USPS prefers that Street Name Post Types be restricted to the words and abbreviated using the standard abbreviation given in Appendix C1. USPS Publication 28 standards are recognized within the Postal Addressing Profile of this standard. 7. Local street naming authorities often have rules governing the use of Street Name Post Types in their area of jurisdiction. For example, a jurisdiction might require that a "Street" must run north-south while an "Avenue" must run east-west, or that Boulevard can only be applied to a street classified as an arterial, while Court can only be used with a cul-de-sac. Where used, such rules should be documented in the authority's Address Reference System Street Type Directional And Modifier Rules.
XML Tag	< StreetNamePostType >
XML Model	<xsd:complexType id="StreetNamePostType_type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute id="Separator" type="addr_type:Separator_type"></xsd:attribute> </xsd:extension> </xsd:simpleContent> </xsd:complexType>
XML Example	<CompleteStreetName> <StreetName>BOSTON-PROVIDENCE</StreetName> <StreetNamePostType>HIGHWAY</StreetNamePostType> </CompleteStreetName> <CompleteStreetName> <StreetNamePreType>AVENUE</StreetNamePreType> <StreetName>C</StreetName> <StreetNamePostType>LOOP</StreetNamePostType> </CompleteStreetName>

StreetNamePreDirectional

Element Name	Street Name Pre Directional
Other common names for this element	Predirectional (USPS), Prefix Direction (Census TIGER), Prefix Directional, Predir, Street Prefix (NFIRS)
Definition	A word preceding the Street Name that indicates the direction or position of the thoroughfare relative to an arbitrary starting point or line, or the sector where it is located.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	USPS Publication 28 Section 233 and 294
Domain of Values for this Element	English: East, West, South, North, Northeast, Southeast, Southwest, Northwest Spanish: Este, Oeste, Sur, Norte; Noreste, Sureste, Suroeste, Noroeste Equivalent words in other languages
Source of Values	USPS Publication 28 Sections 233 and 294 (unabbreviated)
How Defined	As provided by USPS Publication 28 Section 233 and 294
Example	North Main Street Southwest North Street East 400 South North Avenue (directional word is the Street Name, not the Street Name Pre Directional) South Carolina Avenue (directional word is part of the Street Name, not the Street Name Pre Directional)
Notes/Comments	1. A Street Name Pre Directional is a word preceding the Street Name that indicates the direction or position of the thoroughfare relative to an arbitrary starting point or line, or the sector where it is located. 2. A Complete Street Name may include a Street Name Pre Directional, a Street Name Post Directional, neither, or both. 3. To avoid confusion, this standard requires that Street Name Pre Directionals be recorded and stored fully spelled out. Abbreviations can cause ambiguity. For example: "N W Jones St": Is it Northwest Jones Street? Ned Walter Jones Street? North Walter Jones Street? For this reason the standard does not recognize abbreviations for Street Name Pre Directionals. If stored unabbreviated, directionals can be exported as abbreviations when needed for special purposes such as mailing labels. 4. For postal addressing, USPS Publication 28 prefers the use of USPS standard abbreviations for Street Name Pre Directionals. USPS Publication 28 sections 233, 294, and Appendix B provide the USPS abbreviations for Street Name Pre Directionals in English and Spanish. USPS standard abbreviations are recognized within the Postal Addressing Profile of this standard. 5. Directional words are often used as or in the Street Name (e.g. North Avenue, West Virginia Avenue). Whether a directional word should be placed in the Street Name Pre Directional or the Street Name cannot always be discerned from the Complete Street Name itself. Sometimes the proper parsing must be inferred from the context of the street name, or checked with the street naming authority. For example, if West Virginia Avenue is named for the state of West Virginia, then "West" is part of the Street Name. However, if at some point the street changes names and become East Virginia Avenue, then perhaps "Virginia" is the Street Name, and "East" and "West" are Street Name Pre Directionals. See Complete Street Name notes for a discussion of this and other cases where a Complete Street Name might be parsed in more than one way. 6. Occasionally two directional words occur together in or before the Street Name (e.g. "East North Avenue", "West South 9th Street", North West Ridge Road). Only one of them can be the Street Name Predirectional. The other one might be part of the Street Name, or a Street Name Pre Modifer. See Complete Street Name notes for a discussion of this and other cases where a Complete Street Name might be parsed in more than one way. 7. Local street naming authorities often have rules governing the use of Street Name Pre Directionals in their area of jurisdiction. These rules should be documented in their Address Reference System Street Type Directional And Modifier Rules.
XML Tag	<StreetNamePreDirectional>
XML Model	<xsd:complexType id="StreetNamePreDirectional_type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute id="Separator" type="addr_type:Separator_type"></xsd:attribute> </xsd:extension> </xsd:simpleContent> </xsd:complexType>
XML Example	<CompleteStreetName> <StreetNamePreDirectional>NORTH</StreetNamePreDirectional> <StreetName>MAIN</StreetName> <StreetNamePostType>STREET</StreetNamePostType> </CompleteStreetName>
Quality Measures	TabularDomainMeasure SpatialDomainMeasure
Quality Notes	1. TabularDomainMeasure can test entries against a tabular domain. 2. In cases where an address scheme designates particular areas as corresponding with a given Street Name Pre Directional and the geometry for both the streets and the address scheme's spatial domain, SpatialDomainMeasure can test the entries.

StreetNamePreModifier

Element Name	StreetNamePreModifier
Other common names for this element	Prefix Qualifier (Census TIGER)
Definition	A word or phrase in a Complete Street Name that 1. Precedes and modifies the Street Name, but is separated from it by a Street Name Pre Type or a Street Name Pre Directional or both, or 2. Is placed outside the Street Name so that the Street Name can be used in creating a sorted (alphabetical or alphanumeric) list of street names.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	No
Domain of Values for this Element	Can be created locally from existing values
Source of Values	Local
How Defined	Locally
Example	Old North First Street Alternate North Avenue B Old China Spring Road The Oaks Drive Northwest East 14th Street
Notes/Comments	1. A Street Name Pre Modifier precedes and modifies a Street Name, but is separated from the Street Name by a Street Name Pre Type or a Street Name Pre Directional or both. Any word or phrase of a Complete Street Name that precedes the Street Name Pre Directional (or that precedes the Street Name Pre Type, if the Complete Street Name has no Street Name Pre Directional) comprises the Street Name Pre Modifier. 2. In addition, words such as "The" and "Old" may be parsed as Street Name Pre Modifiers when they precede the Street Name but must be excluded from it so that the Street Name will be placed properly in a sorted alphanumeric list. For example, if "The Oaks Drive" should be listed as "Oaks Drive, The", then "The" may be parsed as a Street Name Pre Modifier. If, on the other hand, it should be listed as "The Oaks Drive", then "The" may be included in the Street Name. 3. If a Complete Street Name includes two or more consecutive directional words preceding the Street Name (e.g., Northwest East 14th Street) the last directional word is parsed as a Street Name Pre Directional, and the preceding directional words are parsed as the Street Name Pre Modifier. See Complete Street Name notes for a general discussion of Complete Street Name parsing principles. 4. For numbered (or, occasionally, lettered) jurisdictional routes (e.g. "Kentucky State Highway 67"), the jurisdiction name and the administrative type of road are included with the type word in the Street Name Pre Type. They are not treated as Street Name Pre Modifiers. Thus for the preceding example, Street Name Pre Type = "Kentucky State Highway"; and Street Name = "67". See Street Name Pre Type for a more complete discussion. 5. Street Name Pre Modifiers are not common. Census Bureau TIGER Technical Documentation (Appendix D) lists the following examples of words that are often Street Name Pre Modifiers : Alternate, Business, Bypass, Extended, Historic, Loop, Old, Private, Public, Spur. (Note that most of these words are also used as Street Name Pre Types). 6. USPS Publication 28 does not recognize Street Name Pre Modifiers. USPS Publication 28 standards are recognized within the Postal Addressing Profile of this standard.
XML Tag	< StreetNamePreModifier >
XML Model	<xsd:complexType id="StreetNamePreModifier_type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute id="Separator" type="addr_type:Separator_type"></xsd:attribute> </xsd:extension> </xsd:simpleContent> </xsd:complexType>
XML Example	<CompleteStreetName> <StreetNamePreModifier>OLD</StreetNamePreModifier> <StreetName>FIRST</StreetName> <StreetNamePostType>STREET</StreetNamePostType> <StreetNamePostDirectional>SOUTHWEST</StreetNamePostDirectional> </CompleteStreetName>
Quality Measures	TabularDomainMeasure SpatialDomainMeasure
Quality Notes	1. Where a specific set of premodifiers are specified for use, they may be maintained as a domain and tested with TabularDomainMeasure. 2. Where a schema may designate a particular area with a Street Name Pre Modifier the entries may be tested with SpatialDomainMeasure.

StreetNamePreType

Element Name	StreetNamePreType
Other common names for this element	Prefix type (Census TIGER), Street prefix type, Pre-type
Definition	A word or phrase that precedes the Street Name and identifies a type of thoroughfare in a Complete Street Name.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	None (Appendix C1 of USPS Publication 28 provides a useful list of Street Suffixes, but does not recognize their use for Street Name Pre Types)
Domain of Values for this Element	Yes. Although not recognized as Street Name Pre Types, Appendix C1 of USPS Publication 28 contains a useful list of Street Suffixes. Development of a list of Street Name Pre Types can incorporate Street Suffixes from USPS Publication 28 Appendix C1 with local additions.
Source of Values	Although not recognized as Street Name Pre Types, Section 234 and Appendix C of USPS Publication 28 contains a useful list of Street Types. Development of a list of Street Name Pre Types can incorporate Street Types from USPS Publication 28 with local additions.
How Defined	By local addressing authority.
Example	Avenue A Calle Aurora Avenue of the Americas Avenue at Port Imperial Alameda de las Pulgas Rue d'Armour Avenue C Loop Rhode Island Route 4 Polk County Road 14A Bypass Highway 22
Notes/Comments	1. A Street Name Pre Type is a word or phrase that precedes the Street Name and identifies a type of thoroughfare in a Complete Street Name. In English-language Complete Street Names, most Street Name Pre Type words are also found as Street Name Post Types. 2. A Complete Street Name usually includes either a Street Name Pre Type or a Street Name Post Type. Occasional Complete Street Names have neither ("Broadway") or both ("Avenue C Loop"). 3. For numbered (or, occasionally, lettered) jurisdictional routes, the Street Name Pre Type includes the type word as well as the jurisdiction name and the administrative type of road. The following examples show the parsing of jurisdictional route names: ---Highway 101: Street Name Pre Type = "Highway"; Street Name = "101" ---County Road 88: Street Name Pre Type = "County Road"; Street Name = "88" ---Rhode Island Route 4: Street Name Pre Type = "Rhode Island Route"; Street Name = "4" ---Texas Ranch-to-Market Road 2398: Street Name Pre Type = "Texas Ranch-to-Market Road"; Street Name = "2398" ---Summit County Road XX: Street Name Pre Type = "Summit County Road"; Street Name = "XX" ---United States Highway 99: Street Name Pre Type = "United States Highway"; Street Name = "99". 4. Where a state name is used in a Street Name Pre Type as shown above, it is required to be written out in full rather than abbreviated. Similarly the words "United States" must be written out for all "US" routes and highways. The word "County" used in County routes must also be written out in full. 5. If a prepositional phrase appears between the Street Name Pre Type and the Street Name, the prepositional phrase is a Separator Element: Avenue of the Americas, Alameda de las Pulgas. Such constructions are rare in English-language Complete Street Names, but they are common in Spanish-, French-, and Italian-language street names. 6. Type words are often used as or in the Street Name (e.g. "Park Lane Circle"). Whether a type word should be placed in the Street Name Pre Type or the Street Name cannot always be discerned from the Complete Street Name itself. Sometimes the proper parsing must be inferred from the context of the street name, or checked with the street naming authority. See Complete Street Name notes for a discussion of this and other cases where a Complete Street Name might be parsed in more than one way. 7. Occasionally two or more type words occur together before the Street Name (e.g., "Bypass Highway 22.") All of the words are placed in the Street Name Pre Type, unless the Address Authority has included any of them in Street Name. If the two type words are not part of the Street Name and are not separated from each other by a directional word or other word, they are all placed in the Street Name Pre Type. See Complete Street Name notes for a discussion of this and other cases where a Complete Street Name might be parsed in more than one way. 8. To avoid confusion, this standard does not recognize any abbreviations for Street Name Pre Types. This standard requires that Street Name Pre Types be recorded and stored fully spelled out. Various inconsistent sets of abbreviations are in use, for various purposes, and none is exhaustive. USPS Publication 28 Appendix C.1 contains the best-known list of street type abbreviations.The National Fire Incident Reporting System ( NFIRS) has a slightly different list. Local utilities might use other lists, and various software vendors have incorporated still other lists into their products. Terrace might be abbreviated as "Ter", "Terr", or "Tr". "Tr" might stand for terrace, trail, trace, or track. Any number of different abbreviation sets might be used for given operations or applications within an agency or firm. Therefore Street Name Pre Types should be stored unabbreviated, and related to look-up tables of abbreviations so that the proper set of abbreviations can be applied in views or export routines when needed for special purposes such as mailing labels or 9-1-1 files. 9. The USPS does not recognize the Street Name Pre Type element for standardized postal addresses. Instead, USPS Publication 28 requires that the Street Name Pre Type be combined into the Street Name, preferably unabbreviated (USPS Publication 28, Sec. 234.2, 295.2, Appendix F, Appendix H). USPS Publication 28 standards are recognized within the Postal Addressing Profile of this standard. 10. Local street naming authorities often have rules governing the use of Street Name Pre Types in their area of jurisdiction. For example, a jurisdiction might require that "Avenue" precede the Street Name if the Street Name is a letter ("Avenue C"). Where used, such rules should be documented in the Address Authority's Address Reference System Street Type Directional And Modifier Rules.
XML Tag	< StreetNamePreType >
XML Model	<xsd:complexType id="StreetNamePreType_type"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute id="Separator" type="addr_type:Separator_type"></xsd:attribute> </xsd:extension> </xsd:simpleContent> </xsd:complexType>
XML Example	<CompleteStreetName> <StreetNamePreType>AVENUE</StreetNamePreType> <StreetName>C</StreetName> <StreetNamePostType>LOOP</StreetNamePostType> </CompleteStreetName>
Quality Measures	TabularDomainMeasure SpatialDomainMeasure Related Element Value Measure
Quality Notes	1. TabularDomainMeasure can test entries against a tabular domain. 2. In cases where an Address Reference System designates particular areas as corresponding with a given Street Name Pre Type and the geometry for both the streets and the address scheme's spatial domain, SpatialDomainMeasure can test the entries. 3. In some cases a jurisdiction may have associated specific Street Name Pre Type entries with functional aspects of the road that require additional local quality measures. For example, a court may be required to be a dead end, or a boulevard limited to streets divided by a median. While these associations are beyond the scope of the standard they should be considered in planning a quality program for local addresses. Related Element Value Measure is recommended.

SubaddressElement

Element Name	SubaddressElement
Other common names for this element	Secondary address identifier (USPS, EPA)
Definition	A single combination of Subaddress Type and Subaddress Identifier (or, in some cases, a Subaddress Identifier alone), which, alone or in combination with other Subaddress Elements, distinguishes one subaddress within or between structures from another when several occur within the same feature. See Complete Subaddress for a definition of "subaddress."
Syntax	{ Subaddress Type } + { Subaddress Identifier* }
Definition Source	New
Data Type	characterString
Existing Standards for this Element	None
Domain of Values for this Element	No
Source of Values	N/A
How Defined (eg, locally, from standard, other)	N/A
Attributes Associated with this Element	Subaddress Component Order
Example	Building 4 %BR% Wing 7 %BR% North Tower %BR% Floor 6 %BR% Sixth Floor %BR% Corridor Zero %BR% Apartment 2D %BR% PMB 596 %BR% Empire Room %BR% Penthouse
Notes/Comments	1. A Subaddress Element, alone or in combination with other Subaddress Elements, forms a Complete Subaddress. 2. In English, if the Subaddress Identifier is a name or an ordinal number, the Subaddress Identifier usually but not always precedes the Subaddress Type ("North Tower," "Sixth Floor," "Empire Room,"). If the Subaddress Identifier is a cardinal number, letter designator, or alphanumeric, it typically follows the Subaddress Type ("Building 4," "Apartment 2D", "Hanger A"). Common usage is loose, and there are numerous exceptions to both rules, and patterns differ in other languages. The Subaddress Component Order can be used to indicate the order in which the Subaddress Type and Subaddress Identifier should be written. 3. Some Subaddress Elements use only one word ("Mezzanine"). In such cases, by definition the word is considered a Subaddress Identifier, and the Subaddress Type is null. Other examples (all from USPS Publication 28 Appendix C2) are: Penthouse, Lobby, Basement, Front, Rear, Upper, Lower, Side. 4. The Special case of PMB (Private Mail Box) Subaddresses. Normally a PMB (Private Mail Box), like a mailstop code and other internal mail distribution codes, pertains to the recipient and is not part of the address. However, USPS Publication 28 Section 284 states, "Exception: When the CMRA [commercial mail receiving agency] mailing address contains a secondary address element (e.g. rural route box number, suite, # or other term), the CMRA customer must use Private Mail Box (PMB) when utilizing a three line address format. Examples: --RR 1 Box 12 PMB 596 --10 Main Street Suite 11 PMB 234 " Where a PMB appears in the Delivery Address, it is treated as a Subaddress Element. PMB is the only Subaddress Type that is permitted in the USPSPostal Delivery Box or USPSPostal Delivery Route address classes.
XML Tag	< SubaddressElement >
XML Model	<xsd:complexType id="SubaddressElement_type"> <xsd:sequence> <xsd:element id="SubaddressType" type="addr_type:SubaddressType_type" maxOccurs="1" minOccurs="0" /> <xsd:element id="SubaddressIdentifier" type="addr_type:SubaddressIdentifier_type" maxOccurs="1" minOccurs="1" /> </xsd:sequence> <xsd:attribute id="ElementSequenceNumber" type="addr_type:ElementSequenceNumber_type" /> <xsd:attribute id="SubaddressComponentOrder" type="addr_type:SubaddressComponentOrder_type" /> <xsd:attribute id="Separator" type="addr_type:Separator_type" /> </xsd:complexType>
XML Example	<CompleteSubaddress> <SubaddressElement Element Sequence Number="1" Subaddress Component Order="1" > <SubaddressType>Building</SubaddressType> <SubaddressIdentifier>A</SubaddressIdentifier> </SubaddressElement> <SubaddressElement Element Sequence Number="2" Subaddress Component Order="1" > <SubaddressType>Floor</SubaddressType> <SubaddressIdentifier>7</SubaddressIdentifier> </SubaddressElement> </CompleteSubaddress>
Quality Measures	PatternSequenceMeasure
Quality Notes	Subaddress elements may follow defined schemes for particular buildings or complexes. While these associations are beyond the scope of the standard they should be considered in planning a quality program for local addresses. Note that Subaddress Element entries must be associated with an address to test any spatial associations with particular buildings or complexes, and are therefore tested at the classification level

SubaddressIdentifier

Element Name	Subaddress Identifier
Other common names for this element	Building ID, Floor ID, Apartment Number, Suite Number; Secondary unit indicator (USPS), secondary number (USPS), secondary range (USPS)
Definition	The letters, numbers, words or combination thereof used to distinguish different subaddresses of the same type when several occur within the same feature. See Complete Subaddress for a definition of "subaddress."
Definition Source	New
Data Type	characterString
Existing Standards for this Element	None
Domain of Values for this Element	Can be defined locally from existing values.
Source of Values	Local
How Defined (eg, locally, from standard, other)	Locally
Example	Building 4 Wing 7 Floor 6 Corridor Zero Apartment 2D PMB 596 Mezzanine Penthouse Basement
Notes/Comments	1. The Subaddress Identifier, in combination with the Subaddress Type, is used to designate one of several subaddresses within or between structures at a given site. 2. See Subaddress Element and Complete Subaddress for additional notes.
XML Tag	< SubaddressIdentifier >
XML Model	<xsd:simpleType id="SubaddressIdentifier_type"> <xsd:restriction base="xsd:string" /> </xsd:simpleType>
XML Example	<CompleteSubaddress> <SubaddressElement Element Sequence Number="1" Subaddress Component Order="1" > <SubaddressType>Building</SubaddressType> <SubaddressIdentifier>A</SubaddressIdentifier> </SubaddressElement> <SubaddressElement Element Sequence Number="1" Subaddress Component Order="2" > <SubaddressType>Room</SubaddressType> <SubaddressIdentifier>Empire</SubaddressIdentifier> </SubaddressElement> </CompleteSubaddress>
Quality Measures	RangeDomainMeasure TabularDomainMeasure
Quality Notes	Subaddress identifiers may follow defined schemes for particular buildings or complexes. While these associations are beyond the scope of the standard they should be considered in planning a quality program for local addresses. Note that Subaddress Identifier entries must be associated with an address to test any spatial associations with particular buildings or complexes, and are therefore tested at the classification level

SubaddressType

Element Name	Subaddress Type
Other common names for this element	Building: Tower, Block, Terminal, Hangar, Pier Multi-floor Part of a Building: Wing, Tower Floor: Level, Story Multi-unit Part of a Floor: Corridor Unit: Apartment, Suite, Room, Unit, Office, Trailer, Space, Lot, Slip, Berth Portion of a Unit: Cubicle, Seat PMB: Private Mail Box General: Secondary Address Designator (USPS), Secondary Address Unit Designator (USPS); Secondary Unit Designator (USPS); Secondary Address Identifier (EPA); Generic Occupancy Type
Definition	The type of subaddress to which the associated Subaddress Identifier applies. (In the examples, Building, Wing, Floor, etc. are types to which the Identifier refers.) See Complete Subaddress for a definition of "subaddress."
Definition Source	New
Data Type	characterString
Existing Standards for this Element	None
Domain of Values for this Element	Can be created locally from existing values
Source of Values	Local
How Defined (eg, locally, from standard, other)	Locally
Example	Building 4 Wing 7 Floor 6 Corridor Zero Apartment 2D PMB 596
Notes/Comments	1. The Subaddress Type is used with Subaddress Identifier to designate one of several structures, floors, corridors, units, etc. at a given site. It fits within the general USPS definition of a "secondary address designator" and EPA definition of a "secondary address identifier" 2. USPS Publication 28 Appendix C2 and Section 293 provide a list of common Subaddress Types with standard abbreviations. The FGDC Standard requires storing Subaddress Types fully spelled out, to avoid confusion. If stored unabbreviated, they can be exported as standard abbreviations as needed for mailing and other purposes. USPS Abbreviations are recognized within the Postal Addressing Profile of this standard. 3. PMB (Private mail box) is a special Subaddress Type. See Subaddress Element notes.
XML Tag	< SubaddressType >
XML Model	<xsd:simpleType id="SubaddressType_type"> <xsd:restriction base="xsd:string" /> </xsd:simpleType>
XML Example	<CompleteSubaddress> <SubaddressElement Element Sequence Number="1" Subaddress Component Order="1" > <SubaddressType>Building</SubaddressType> <SubaddressIdentifier>A</SubaddressIdentifier> </SubaddressElement> <SubaddressElement Element Sequence Number="2" Subaddress Component Order="2" > <SubaddressType>Room</SubaddressType> <SubaddressIdentifier>Empire</SubaddressIdentifier> </SubaddressElement> </CompleteSubaddress>
Quality Measures	TabularDomainMeasure
Quality Notes	Subaddress types may follow defined schemes for particular buildings or complexes. While these associations are beyond the scope of the standard they should be considered in planning a quality program for local addresses. Note that Subaddress Type entries must be associated with an address to test any spatial associations with particular buildings or complexes, and are therefore tested at the classification level.

USPSAddress

Element Name	USPSAddress
Other common names for this element	Postal Address
Definition	A USPS postal delivery point identified by a USPS Route and a USPS Box
Syntax	{ USPS Route } + { USPS Box }
Definition Source	New
Data Type	characterString
Existing Standards for this Element	USPS Publication 28 sections 24, 25, and 28; section 238.1 (Military Addresses); and sections 293, 295.6, and 295.7 (Puerto Rico Addresses)
Domain of Values for this Element	See Component Elements
Source of Values	USPS Publication 28 sections 24, 25, and 28; section 238.1 (Military Addresses); and sections 293, 295.6, and 295.7 (Puerto Rico Addresses)
How Defined (eg, locally, from standard, other)	See component elements
Example	RR 2 Box 223G Dardanelle AR 72834 HC 3 Box 330 Flasher ND 58535 PSC 802 Box 74 FPO AA 34058 CMR 416 Box 100 APO AE 09140-0015 Unit 2050 Box 4190 APO AP 96278-2050
Notes/Comments
XML Tag	< USPSAddress >
XML Model	<xsd:complexType id="USPSAddress_type"> <xsd:sequence> <xsd:element id="USPSRoute" type="addr_type:USPSRoute_type" maxOccurs="1" minOccurs="1"/> <xsd:element id="USPSBox" type="addr_type:USPSBox_type" maxOccurs="1" minOccurs="1"/> </xsd:sequence> </xsd:complexType>
XML Example	<USPSAddress> <USPSRoute> <USPSBoxGroupType>PSC</USPSGroupType> <USPSBOXGroupId>4</USPSGroupId> </USPSRoute> <USPSBox> <USPSBoxType>BOX</USPSBoxType> <USPSBoxId>3</USPSBoxId> </USPSBox> </USPSAddress>
Quality Measure	Pattern Sequence Measure
Quality Notes

USPSBoxGroupID

Element Name	USPSBoxGroupID
Other common names for this element	Rural route number; HC number; PSC/CMR/Unit Number
Definition	The numbers or letters distinguishing one route or distribution point from another route or distribution point of the same USPSBox Group Type.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	USPS Publication 28 sections 24, 25, and 28; section 238.1 (Military Addresses); and sections 293, 295.6, and 295.7 (Puerto Rico Addresses)
Domain of Values for this Element	Yes
Source of Values	Local Post office
How Defined (eg, locally, from standard, other)	Local Post office
Example	1. RR 4 Box 10 2. HC 2 Box 7 3. PSC 4 Box 3 4. CMR 4 Box 2 5. UNIT 475 Box 690
Notes/Comments
XML Tag	< USPSBoxGroupID >
XML Model	<xsd:simpleType id="USPSBoxGroupId_type"> <xsd:restriction base="xsd:string"> <xsd:pattern value='.*' /> </xsd:restriction> </xsd:simpleType>
XML Example	<USPSAddress> <USPSRoute> <USPSBoxGroupType>PSC</USPSGroupType> <USPSBOXGroupId>4</USPSGroupId> </USPSRoute>* <USPSBox> <USPSBoxType>BOX</USPSBoxType> <USPSBoxId>3</USPSBoxId> </USPSBox> </USPSAddress>
Quality Measures	Tabular Domain Measure Range Domain Measure
Quality Notes

USPSBoxGroupType

Element Name	USPSBoxGroupType
Other common names for this element	See domain of values below.
Definition	A name for a type of postal delivery point or route containing a group of USPS Boxes.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	USPS Publication 28 sections 24, 25, and 28; section 238.1 (Military Addresses); and sections 293, 295.6, and 295.7 (Puerto Rico Addresses)
Domain of Values for this Element	RR (Rural Route)(Obsolete terms: RD, RFD, Rural Delivery, Rural Free Delivery) HC (Contract Delivery Service Route) (Obsolete terms: Highway Contract Route, Star Route) PSC (Postal Service Center)(Overseas military postal address) CMR (Common Mail Room)(Overseas military postal address) Unit (Overseas military postal address)
Source of Values	USPS Publication 28 sections 24, 25, and 28; section 238.1 (Military Addresses); and sections 293, 295.6, and 295.7 (Puerto Rico Addresses)
How Defined (eg, locally, from standard, other)	USPS Publication 28 sections 24, 25, and 28; section 238.1 (Military Addresses); and sections 293, 295.6, and 295.7 (Puerto Rico Addresses)
Example	1. RR 4, Box 10 2. HC 2, Box 7 3. PSC 4, Box 3 4. CMR 4, Box 2 5. UNIT 475, Box 690
Notes/Comments	1. This group includes rural routes, contract service delivery routes, postal service centers, overseas military common mail rooms and military unit numbers. 2. Contract Delivery Service Routes were formerly called Highway Contract Routes, and are still abbreviated "HC".
XML Tag	< USPSBoxGroupType >
XML Model	<xsd:simpleType id="USPSBoxGroupType_type"> <xsd:restriction base="xsd:string"> <xsd:pattern value='.*' /> </xsd:restriction> </xsd:simpleType>
XML Example	<USPSAddress> <USPSRoute> <USPSBoxGroupType>PSC</USPSGroupType> <USPSBOXGroupId>4</USPSGroupId> </USPSRoute> <USPSBox> <USPSBoxType>BOX</USPSBoxType> <USPSBoxId>3</USPSBoxId> </USPSBox> </USPSAddress>
Quality Measures	TabularDomainMeasure Related Element Value Measure
Quality Notes	In cases where a specific USPSBox Group Type is associated with a given locality, Related Element Value Measure may be used to test the values.

USPSBox

Element Name	USPSBox
Other common names for this element	PO Box, Box, Post Office Box (Obsolete terms: Lockbox, Drawer, Bin, Caller, Firm Caller)
Definition	A container for the receipt of USPS mail uniquely identified by the combination of a USPSBox Type and a USPSBox ID.
Syntax	{ USPSBox Type } +{ USPSBox ID }
Definition Source	New
Data Type	characterString
Existing Standards for this Element	USPS Publication 28 sections 24, 25, and 28; section 238.1 (Military Addresses); and sections 293 and 295.6 (Puerto Rico Addresses)
Domain of Values for this Element	See component elements.
Source of Values	See component elements.
How Defined (eg, locally, from standard, other)	See component elements.
Example	PO Box 246 Hillsdale, NJ 07642 PO Box 1137 Saipan MP 96950-1137 RR 4 Box 73 Grafton WV 26354 HC 4 Box 100 Blanco TX 78606
Notes/Comments	A USPS Box location has no definite geographic relation to the location of the recipient of the mail.
XML Tag	< USPSBox >
XML Model	<xsd:complexType id="USPSBox_type"> <xsd:sequence> <xsd:element id="USPSBoxType" type="addr_type:USPSBoxType_type" maxOccurs="1" minOccurs="1"/> <xsd:element id="USPSBoxId" type="addr_type:USPSBoxId_type" maxOccurs="1" minOccurs="1"/> </xsd:sequence> </xsd:complexType>
XML Example	<USPSAddress> <USPSRoute> <USPSBoxGroupType>PSC</USPSGroupType> <USPSBOXGroupId>4</USPSGroupId> </USPSRoute> <USPSBox> <USPSBoxType>BOX</USPSBoxType> <USPSBoxId>3</USPSBoxId> </USPSBox> </USPSAddress>
Quality Measure	TabularDomainMeasure PatternSequenceMeasure
Quality Notes	In cases where the USPSBox Type and USPSBox ID have been tested, only the PatternSequenceMeasure need be used. Where the data are tested at the USPS Box level, TabularDomainMeasure will be required.

USPSBoxID

Element Name	USPSBoxID
Other common names for this element	PO Box Number; Box Number
Definition	The numbers or letters distinguishing one box from another within a post office or route.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	USPS Publication 28 sections 24, 25, and 28; section 238.1 (Military Addresses); and sections 293 and 295.6 (Puerto Rico Addresses)
Domain of Values for this Element	Yes, within each post office
Source of Values	Local post office
How Defined (eg, locally, from standard, other)	Local post office
Example	PO Box 6943 PO Box G PO Box 00145 RR 4 Box 19-1A HC 68 Box 45
Notes/Comments	1. USPSBox ID's may include numbers or letters, and may include a hyphen. 2. "Post Office Box numbers that are preceded by significant leading zeroes are identified in the ZIP+4 file by a hyphen (-) preceding the box number. Convert the hyphen into a zero on the output mailpiece." Example: Convert "PO BOX -0145" to "PO BOX 00145" on output from the ZIP+4 file. (USPS publication 28 Section 282)
XML Tag	< USPSBoxID >
XML Model	<xsd:simpleType id="USPSBoxId_type"> <xsd:restriction base="xsd:string"> <xsd:pattern value='.*' /> </xsd:restriction> </xsd:simpleType>
XML Example	<USPSBox> <USPSBoxType>PO Box</USPSBoxType> <USPSBoxID>6943</USPSBoxId> </USPSBox>
Quality Measures	TabularDomainMeasure RangeDomainMeasure
Quality Notes

USPSBoxType

Element Name	USPSBoxType
Other common names for this element	PO Box; Box (Obsolete terms: Drawer, Lockbox, Bin, Caller, Firm Caller)
Definition	The name of the class of the container used for receipt of USPS mail. USPS Publication 28 requires the use of "PO Box" or "Box" for this element.
Definition Source	New
Data Type	characterString
Existing Standards for this Element	USPS Publication 28 sections 24, 25, and 28; section 238.1 (Military Addresses); and sections 293 and 295.6 (Puerto Rico Addresses)
Domain of Values for this Element	PO Box (if used in a USPSPostal Delivery Box address). Box (if used in a USPSPostal Delivery Route address
Source of Values	USPS Publication 28 sections 24, 25, and 28; section 238.1 (Military Addresses); and sections 293 and 295.6 (Puerto Rico Addresses)
How Defined (eg, locally, from standard, other)	USPS Publication 28 sections 24, 25, and 28; section 238.1 (Military Addresses); and sections 293 and 295.6 (Puerto Rico Addresses)
Example	PO Box 6943 PO Box G PO Box 00145 RR 4 Box 19-1A HC 68 Box 45
Notes/Comments	1. In USPSPostal Delivery Box addresses, "PO Box" is required for this element. "Post Office Box addresses are output as "PO Box NN" on the mailpiece." (USPS Publication 28 section 281). 2. In USPSPostal Delivery Route addresses, "Box" is required for this element. ---"Print rural route addresses on mailpieces as "RR N Box NN". (USPS Publication 28 section 241) ---"Print highway contract route addresses on mailpieces as "HC N Box NN". (USPS Publication 28 section 251) 3. The USPSPostal Delivery Box and USPSPostal Delivery Route address classes are defined in the Classification Part of this standard.
XML Tag	< USPSBoxType >
XML Model	<xsd:simpleType id="USPSBoxType_type"> <xsd:restriction base="xsd:string"> <xsd:pattern value='.*' /> </xsd:restriction> </xsd:simpleType>
XML Example	<USPSBox> <USPSBoxType>PO Box</USPSBoxType> <USPSBoxID>6943</USPSBoxId> </USPSBox>
Quality Measures	TabularDomainMeasure RangeDomainMeasure
Quality Notes

USPSGeneralDeliveryPoint

Element Name	USPSGeneralDeliveryPoint
Other common names for this element
Definition	A central point where mail may be picked up by the addressee. Two values are permitted: "General Delivery" (for post offices), and ship's names (for overseas military addresses).
Definition Source	New
Data Type	characterString
Existing Standards for this Element	Yes
Domain of Values for this Element	Yes
Source of Values	USPS
How Defined (eg, locally, from standard, other)	USPS Publication 28 Section 26 (General Delivery Addresses); and section 238.1 (overseas military addresses)
Example	General Delivery, Tampa, FL 33602-9999 USCGC Hamilton, FPO AP 96667-3931
Notes/Comments	For general delivery addresses, USPS Publication 28 section 261 specifies, "Use the words GENERAL DELIVERY, uppercase preferred, spelled out (no abbreviation), as the Delivery Address Line on the mailpiece. Each record will carry the 9999 add-on code.
XML Tag	< USPSGeneralDeliveryPoint >
XML Model	<xsd:simpleType id="USPSGeneralDeliveryPoint_type"> <xsd:restriction base="xsd:string"> <xsd:pattern value='.*' /> </xsd:restriction> </xsd:simpleType>
XML Example	<USPSGeneralDeliveryPoint>USCGC Hamilton</USPSGeneralDeliveryPoint>
Quality Measures	Tabular Domain Measure
Quality Notes

USPSRoute

Element Name	USPSRoute
Other common names for this element	See component elements
Definition	A collection of boxes served from a single distribution point, and uniquely identified by a USPSBox Group Type and a USPSBox Group ID.
Syntax	{ USPSBox Group Type } + { USPSBox Group ID }
Definition Source	New
Data Type	characterString
Existing Standards for this Element	USPS Publication 28 sections 24, 25, and 28; section 238.1 (Military Addresses); and sections 293, 295.6, and 295.7 (Puerto Rico Addresses)
Domain of Values for this Element	See component elements
Source of Values	See component elements
How Defined (eg, locally, from standard, other)	See component elements
Example	1. RR 4 Box 10 2. HC 2 Box 7 3. PSC 4 Box 3 4. CMR 4 Box 2 5. Unit 475 Box 690
Notes/Comments	Unlike carrier routes and other USPS internal codes for mail sorting and delivery, the USPS Routes must be included in the address to provide sufficient information for delivery of mail.
XML Tag	< USPSRoute >
XML Model	<xsd:complexType id="USPSRoute_type"> <xsd:sequence> <xsd:element id="USPSBoxGroupType" type="addr_type:USPSBoxGroupType_type" maxOccurs="1" minOccurs="1"/> <xsd:element id="USPSBOXGroupId" type="addr_type:USPSBoxGroupId_type" maxOccurs="1" minOccurs="1"/> </xsd:sequence> </xsd:complexType>
XML Example	<USPSAddress> <USPSRoute> <USPSBoxGroupType>PSC</USPSGroupType> <USPSBOXGroupId>4</USPSGroupId> </USPSRoute> <USPSBox> <USPSBoxType>BOX</USPSBoxType> <USPSBoxId>3</USPSBoxId> </USPSBox> </USPSAddress>
Quality Measure	TabularDomainMeasure PatternSequenceMeasure
Quality Notes	Where USPSBox Group Type and USPSBox Group ID have been tested independently, only PatternSequenceMeasure need be tested. Where the data are tested at the USPS Route level, TabularDomainMeasure is recommended.

ZipCode

Element Name	Zip Code
Other common names for this element	ZIP5, Zone Improvement Plan
Definition	A system of 5-digit codes that identifies the individual Post Office or metropolitan area delivery station associated with an address.
Definition Source	USPS, "Quick Service Guide 800: Glossary of Postal Terms and Abbreviations in the DMM."
Data Type	characterString
Existing Standards for this Element	Yes
Domain of Values for this Element	Yes
Source of Values	USPS
How Defined (eg, locally, from standard, other)	USPS is the sole source of this information.
Example	Birmingham, AL 35305 Webster Groves, MO 63119
Notes/Comments	Strictly speaking a ZIP Code is not an area but a set of USPS delivery points served from the same post office. Delivery points with the same ZIP Code can encompass a a single building that has a very high mail volume; a portion of a city; all or parts of several municipalities; or even portions of more than more county (and, in a few cases, more than one state).
XML Tag	< ZipCode >
XML Model	<xsd:simpleType id="ZipCode_type"> <xsd:restriction base="xsd:string"> <xsd:pattern value='[0-9]{5}' /> </xsd:restriction> </xsd:simpleType>
XML Example	<ZipCode>35305</Zipcode>
Quality Measures	TabularDomainMeasure SpatialDomainMeasure
Quality Notes

ZipPlus4

Element Name	ZipPlus4
Other common names for this element	ZIP+4
Definition	A 4-digit extension of the 5-digit Zip Code (preceded by a hyphen) that, in conjunction with the Zip Code, identifies a specific range of USPS delivery addresses.
Definition Source	Adapted from USPS, "Quick Service Guide 800: Glossary of Postal Terms and Abbreviations in the DMM."
Data Type	characterString
Existing Standards for this Element	Yes
Domain of Values for this Element	Yes
Source of Values	USPS is the sole source of this information.
How Defined (eg, locally, from standard, other)	From USPS
Example	Birmingham, Alabama 35242 -3426 Webster Groves, Missouri 63119 -3212
Notes/Comments	1. Strictly speaking, the Zip Plus 4 consists of "the 5-digit ZIP Code and four additional digits that identify a specific range of USPS delivery addresses" (Quoted from USPS, "Quick Service Guide 800: Glossary of Postal Terms and Abbreviations in the DMM). However this standard separates the two components to facilitate data processing. 2. The Zip Code and the Zip Plus 4 are formatted with a hyphen between the two elements (see USPS Publication 28 Sections 343.1, 356 and Appendix A1). It is assumed in this standard that the hyphen is not stored with the Zip Plus 4 value, but is added upon export for display.
XML Tag	< ZipPlus4 >
XML Model	<xsd:simpleType id="ZipPlus4_type"> <xsd:restriction base="xsd:string"> <xsd:pattern value='[0-9]{4}' /> </xsd:restriction> </xsd:simpleType>
XML Example	<ZipCode>35242</ZipCode> <ZipPlus4>3426</ZipPlus4>
Quality Measures	TabularDomainMeasure Related Element Value Measure
Quality Notes	Related Element Value Measure is recommended to check Zip Plus 4 values against the specific street name and address range to which it is assigned.

Address Elements