Part 2: Address Data Content
<Previous> <Home> <Up>
Search the Address Standard
| Element Name | AddressReferenceSystem |
|---|---|
| Other common names for this element | A set of rules and geometries that define how addresses are assigned along thoroughfares and/or within a given area (Address Reference System Extent). At minimum, an Address Reference System must specify where Complete Address Number sequences begin and how Complete Address Numbers are assigned along the length of thoroughfares governed by the Address Reference System. Address Reference Systems typically provide rules governing left-right parity of Complete Address Numbers, assignment of Street Names and street types, use of directionals and quadrants, and other aspects of address assignment. An Address Reference System is designated by its Address Reference System Name (required). Additional business rules for an Address Reference System are described in the Address Reference System Rules. |
| Definition Source | New |
| Data Type | Abstract |
| 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 (eg, locally, from standard, other) | Refer to Component Elements |
| Example | Address Reference System Name: Metro City Address Grid Address Reference System Axis Point Of Beginning:
Address Reference System Axis:
Address Reference System Axis Point Of Beginning:
Address Reference System Axis:
Address Reference System Rules: Written information about parity, street naming conventions, numbering intervals, grids, and other business rules. (Contains elements including Address Reference System Block Rules, Address Reference System Numbering Rules, Address Reference System Street Naming Rules, Address Reference System Street Type Directional And Modifier Rules, Address Reference System Place Name State Country And Zip Code Rules Address Reference System Authority: Name of agency (municipality, county, other) that has authority over the scheme's business rules, extent and other parameters. |
| Notes/Comments | 1. Address Reference System Extents may overlap. 2. There are three broad types of Address Reference Systems: Axial, linear non-axial and area based. * Axial The Address Reference System is based on streets or geometric lines whichform the basis for address numbering. The axes are often oriented more or less at 90 degrees to each other to define quadrants or directionals. The grid may be defined by topography, rivers, rail lines or other features. This is by far the most common type in the United States; Chicago is but one of many clear examples. * Linear Non-axial. Each thoroughfare has its own beginning point for Complete Address Numbers, independent of the other thoroughfares in the Address Reference System. This is common, for example, in rural areas where the road network is sparse and street segments are long. This term may also apply to places where the address numbers are not based on thoroughfares at all. * Area-based. An Address Reference System may not be based on street geometry, but number assignment is done according to chronology (when a structure was addressed), or parcel or lot numbers. 3. A jurisdiction may have more than one addressing scheme within its area, and its Address Reference System(s) may change over time. Occasionally addresses from different schemes are intermingled along the same block face, which complicates the assignment of an address range to that block face. This may be the result of annexation of developed properties with existing addresses from one jurisdiction to another. |
| XML Tag | < AddressReferenceSystem> |
| XML Model | <xsd:complexType id="AddressReferenceSystem" > <xsd:sequence> <xsd:element id="AddressReferenceSystemID" type="addr_type:AddressReferenceSystemId_type" maxOccurs="1" minOccurs="1"/> <xsd:element id="AddressReferenceSystemName" type="addr_type:AddressReferenceSystemName_type" maxOccurs="1" minOccurs="1"/> <xsd:element id="AddressReferenceSystemAuthority" type="addr_type:AddressReferenceSystemAuthority_type" maxOccurs="1" minOccurs="0"/> <xsd:element id="AddressReferenceSystemExtent" type="addr_type:AddressReferenceSystemExtent_type" maxOccurs="1" minOccurs="0"/> <xsd:element id="AddressReferenceSystemType" type="addr_type:AddressReferenceSystemType_type" maxOccurs="1" minOccurs="0"/> <xsd:element id="AddressReferenceSystemRules" type="addr_type:AddressReferenceSystemRules_type" maxOccurs="1" minOccurs="0"/> <xsd:element id="AddressReferenceSystemAxis" type="addr_type:AddressReferenceSystemAxis_type" maxOccurs="1" minOccurs="0"/> <xsd:element id="AddressReferenceSystemAxisPointOfBeginning" type="addr_type:AddressReferenceSystemAxisPointOfBeginning_type" maxOccurs="1" minOccurs="0"/> <xsd:element id="AddressReferenceSystemGridAngle" type="addr_type:AddressReferenceSystemGridAngle_type" maxOccurs="1" minOccurs="0"/> < xsd:element id="AddressReferenceSystemReferencePolyline" type="addr_type:AddressReferenceSystemReferencePolyline_type" maxOccurs="unbounded" minOccurs="0"/> <xsd:element id="AddressReferenceSystemRangeBreakpoint" type="addr_type:AddressReferenceSystemRangeBreakpoint_type" maxOccurs="1" minOccurs="0"/> <xsd:element id="AddressReferenceSystemRangeBreakline" type="addr_type:AddressReferenceSystemRangeBreakline_type" maxOccurs="unbounded" minOccurs="0"/> <xsd:element id="AddressReferenceSystemReferenceDocumentCitation" type="addr_type:AddressReferenceSystemReferenceDocumentCitation_type" maxOccurs="unbounded" minOccurs="0"/> </xsd:sequence> </xsd:complexType> |
| XML Example | <AddressReferenceStstem> <AddressReferenceSystemID>MCAG Unified</AddressReferenceSystemId> <AddressReferenceSystemName>Metro City Address Grid</AddressReferenceSystemName> <AddressReferenceSystemType>Grid</AddressReferenceSystemType> </AddressReferenceSystem> |
| Quality Measures | Address Reference System Rules Measure |
| Quality Notes |
| Element Name | AddressReferenceSystemAuthority |
|---|---|
| Other common names for this element | |
| Definition | The name of the authority or jurisdiction responsible for the creation and/or maintenance of an Address Reference System for a given area. |
| Definition Source | New |
| Data Type | characterString |
| Existing Standards for this Element | None |
| Domain of Values for this Element | None. |
| Source of Values | Local |
| How Defined | Defined locally |
| Example | City of Orono, ME; Commander, Bolling Air Force Base, Washington, DC |
| Notes/Comments | The agency responsible for creating or maintaining an Address Reference System may or may not be the same as the Address Authority responsible for assigning and maintaining the addresses in a given area. |
| XML Tag | < AddressReferenceSystemAuthority> |
| XML Model | <xsd:simpleType id="AddressReferenceSystemAuthority_type"> <xsd:restriction base="xsd:string" /> </xsd:simpleType> |
| XML Example | <AddressReferenceSystemAuthority>Commander, Bolling Air Force Base</AddressReferenceSystemAuthority> <AddressReferenceSystemAuthority>City of Orono</AddressReferenceSystemAuthority> |
| Quality Measure | Tabular Domain Measure |
| Quality Notes |
| Element Name | AddressReferenceSystemAxis |
|---|---|
| Other common names for this element | |
| Definition | The line that defines the points of origin for address numbering along thoroughfares that intersect it, or which are numbered in parallel to streets that intersect it. It may be a road, another geographic feature, or an imaginary line. |
| Definition Source | New |
| Data Type | Geometry (Multicurve), as defined in the Open Geospatial Consortium's "OpenGIS(R) Geography Markup Language (GML) Encoding Standard" version: 3.2.1 (see Part 6 for a complete citation) |
| Existing Standards for this Element | None |
| Domain of Values for this Element | Locally defined |
| Source of Values | Local |
| How Defined | Defined locally, often by ordinance and encoded in terms of a spatial referencing systems, described in the file-level metadata per FGDC's Content Standard for Digital Geospatial Metadata |
| Example | Address Reference System Axis:
|
| Notes/Comments | 1. An Address Reference System Axis creates the beginning point for assigning Complete Address Numbers to thoroughfares that cross it, and it may guide the assignment of Complete Address Numbers along parallel thoroughfares. 2. An Address Reference System Axis is typically a road, but it may also be a line derived from a Public Land Survey System (PLSS) grid or a river (common in riverfront cities), a rail line, or an imaginary line (e.g. the east-west centerline of the national mall in Washington, DC). 3. Axis lines may cross, radiate or branch. 4. It may also provide a "measuring device" for the extension of numbers along parallel streets, especially where there is a gap in development within an Address Reference System. 5. Axis lines may also define quadrants or areas in which certain directionals may be required for street names and addresses. |
| XML Tag | < AddressReferenceSystemAxis> |
| XML Model | <xsd:complexType id="AddressReferenceSystemAxis_type"> <xsd:complexContent> <xsd:restriction base="gml:MultiCurveType"> </xsd:restriction> </xsd:complexContent> </xsd:complexType> |
| XML Example | <AddressReferenceSystemAxis> <gml:MultiCurve> <gml:curveMember> <gml:Curve> <gml:segments> <gml:LineStringSegment> <gml:posList>1000 15000 20000 15000 </gml:posList> </gml:LineStringSegment> </gml:segments>/gml:Curve> </gml:curveMember> </gml:MultiCurve> </AddressReferenceSystemAxis> |
| Quality Measures | Address Reference System Axes Point Of Beginning Measure |
| Quality Notes |
| Element Name | AddressReferenceSystemAxisPointOfBeginning |
|---|---|
| Other common names for this element | Axis Origin Point |
| Definition | Coordinate location of the beginning point of address numbering along an Address Reference System Axis. |
| Definition Source | New |
| Data Type | Geometry (Point) as defined in the Open Geospatial Consortium's "OpenGIS(R) Geography Markup Language (GML) Encoding Standard" version: 3.2.1 (see Part 6 for a complete citation) |
| Existing Standards for this Element | N/A |
| Domain of Values for this Element | Coordinate location of the beginning point for address numbers along an address axis. |
| Source of Values | Source of spatial data collection. |
| How Defined (eg, locally, from standard, other) | Point location defined locally, often by ordinance, and encoded in terms of a spatial referencing system, described in file-level metadata per FGDC's Content Standard for Geospatial Metadata. |
| Example | Definition For Washington DC: The US Capitol Building (point of origin for North, South, and East Capitol Streets and the Capitol Mall, which divide DC into four quadrants, NW, NE, SE, and SW). Address numbers increase along those four axes as one travels away from the Capitol Building, and all other streets are addressed more or less in parallel with one of the axis streets, and every address must include a quadrant designation. Element :
|
| Notes/Comments | The origin point for an Address Reference System Axis may be the same or may differ from the origin point for other Address Reference System Axis lines in the same Address Reference System. |
| XML Tag | < AddressReferenceSystemAxisPointOfBeginning> |
| XML Model | <xsd:complexType id="AddressReferenceSystemAxisPointOfBeginning_type"> <xsd:complexContent> <xsd:extension base="gml:PointType"></xsd:extension> </xsd:complexContent> </xsd:complexType> |
| XML Example | <AddressReferenceSystemAxisPointOfBeginning> <gml:Point> <gml:pos>15000,15000</gml:pos> </gml:Point> </AddressReferenceSystemAxisPointOfBeginning> |
| Quality Measures | Address Reference System Axes Point Of Beginning Measure |
| Quality Notes | If the Address Reference System Rules specifies that the Address Reference System Axis Point Of Beginning for one Address Reference System Axis is at the intersection of another Address Reference System Axis, then use Address Reference System Axes Point Of Beginning Measure. |
| Element Name | AddressReferenceSystemBlockRules |
|---|---|
| Other common names for this element | |
| Definition | The rules defining blocks, block ranges, and block breaks used in assigning address numbers in an Address Reference System. |
| Definition Source | New |
| Data Type | characterString |
| Existing Standards for this Element | None |
| Domain of Values for this Element | Locally defined |
| Source of Values | Local |
| How Defined | Defined locally, often by ordinance and encoded in terms of a spatial referencing systems, described in the file-level metadata per FGDC's Content Standard for Digital Geospatial Metadata |
| Example | 1. "A block is defined as a street segment between its points of intersection with other street segments at either end." 2. A block shall contain 100 address numbers, and shall begin with the 00 value on one side, and the 01 value on the other side." 3. "A block shall be defined as one mile along a single street regardless of the intersection of the street with any other streets." |
| Notes/Comments | Parity, meaning the definition of which side of a street shall be given the odd numbers and which side the even numbers in a range is defined in the Address Range Parity element. |
| XML Tag | < AddressReferenceSystemBlockRules> |
| XML Model | <xsd:simpleType id="AddressReferenceSystemBlockRules_type"> <xsd:restriction base="xsd:string" /> </xsd:simpleType> |
| XML Example | <AddressReferenceSystemBlockRules>A block is defined as a street segment between its points of intersection with other street segments at either end.</AddressReferenceSystemBlockRules> |
| Quality Measures | See Address Reference System Rules Measure. |
| Quality Notes |
| Element Name | AddressReferenceSystemExtent |
|---|---|
| Other common names for this element | |
| Definition | Boundary of the area(s) within which an Address Reference System is used. |
| Definition Source | New |
| Data Type | Geometry (Multisurface), as defined in the Open Geospatial Consortium's "OpenGIS(R) Geography Markup Language (GML) Encoding Standard" version: 3.2.1 (see Part 6 for a complete citation) |
| Existing Standards for this Element | NA |
| Domain of Values for this Element | Coordinate values within the geometric areal extent of the Address Reference System |
| Source of Values | Source of spatial data collection. |
| How Defined (eg, locally, from standard, other) | Locally defined. |
| Examples | Address Reference System Extent:
|
| Notes/Comments | An Address Reference System may include the entire area of a city or county jurisdiction, or it may only include a portion thereof. Military bases, and some university campuses are addressed under Address Reference Systems that are maintained by the Base Commander for military bases, and by the State Department of Education (or the University system) for campuses. These often exist within the boundaries of a city, and are within county areas as well, but have their own schemes. Each Address Reference System is defined geographically, and should not (although many do so) overlap other Address Reference Systems that are in current use. Historical Address Reference System extents may be maintained, especially where an area under a county Address Reference System has been annexed into a city. The city may choose to maintain the county's numbering, and it will be useful, if additional development occurs, to have access to the previous Address Reference System to insure correct and consistent addressing with it. |
| XML Tag | < AddressReferenceSystemExtent> |
| XML Model | <xsd:complexType id="AddressReferenceSystemExtent_type"> <xsd:complexContent> <xsd:restriction base="gml:MultiSurfaceType"/ > </xsd:complexContent> </xsd:complexType> |
| XML Example | <AddressReferenceSystemExtent> <gml:MultiSurface> <gml:surfaceMember> <gml:Polygon> <gml:exterior> <gml:LinearRing> <gml:posList>1000 1000 1000 25000 20000 1000 20000 25000 1000 1000</gml:posList> </gml:LinearRing> </gml:exterior> </gml:Polygon> </gml:surfaceMember> </gml:MultiSurface> </AddressReferenceSystemExtent> |
| Quality Measures | None |
| Quality Notes | Check the boundary against the Address Reference System Rules. |
| Element Name | AddressReferenceSystemGridAngle | |
|---|---|---|
| Other common names for this element | ||
| Definition | The degree to which a specific, named address grid is tilted off a north/south or east/west orientation. | |
| Definition Source | New | |
| Data Type | Character | |
| Existing Standards for this Element | None | |
| Domain of Values for this Element | Locally defined | |
| Source of Values | Local | |
| How Defined | Defined locally, often by ordinance and encoded in relationship to an address referencing systems, described in the file-level metadata per FGDC's Content Standard for Digital Geospatial Metadata | |
| Example | Address Reference System Grid Angle "The City of Motown grid is tilted at 32 degrees to true north." |
|
| Notes/Comments | 1. An Address Reference System Grid Angle describes the angle at which an address grid or reference system consisting of mainly rectangular blocks is tilted or skewed from a true north-south orientation. Such tilting occurs for a number of reasons, including grids based on natural features which are at an angle to the cardinal directions, railroads and major highways that traverse the address reference system at an angle, or other local factors. The angle may have an effect on what directionals are used, and may create confusion when the directionals are referencing the grid rather than the actual compass directions. This attribute will be useful in developing correct assumptions concerning the assignment and quality assurance testing of directionals within the address reference system. | |
| XML Tag | < AddressReferenceSystemGridAngle> |
|
| XML Model | <xsd:simpleType id="AddressReferenceSystemGridAngle_type"> <xsd:restriction base="xsd:double" /> </xsd:simpleType> |
|
| XML Example | <AddressReferenceSystemGridAngle> 66.5 </AddressReferenceSystemGridAngle> | |
| Quality Measures | AddressReferenceSystemRulesMeasure | |
| Quality Notes | ||
| Element Name | AddressReferenceSystemID |
|---|---|
| Other common names for this element | |
| Definition | A unique identifier of the Address Reference System. |
| Definition Source | New |
| Data Type | Integer |
| Existing Standards for this Element | None |
| Domain of Values for this Element | Locally defined |
| Source of Values | Local |
| How Defined (eg, locally, from standard, other) | Locally |
| Examples | For examples, see the Complex Element: Address Reference System. |
| Notes/Comments | The Address Reference System ID provides a reliable attribute to link an individual address record or a group of address records to a specific Address Reference System. This attribute identifies the specific rules that should be used in evaluating the address record. The Address Reference System ID must be unique to the Address Authority. |
| XML Tag | < AddressReferenceSystemID> |
| XML Model | <xsd:simpleType id="AddressReferenceSystemId_type"> <xsd:restriction base="xsd:integer" /> </xsd:simpleType> |
| XML Example | <AddressReferenceSystemID>55</AddressReferenceSystemId> |
| Element Name | AddressReferenceSystemName |
|---|---|
| Other common names for this element | |
| Definition | The name of an address system. |
| Definition Source | New |
| Data Type | characterString |
| Existing Standards for this Element | None |
| Domain of Values for this Element | Locally defined |
| Source of Values | Local |
| How Defined (eg, locally, from standard, other) | Locally |
| Examples | For examples, see the Complex Element: Address Reference System. |
| Notes/Comments | In some cases, the Address Reference System Name may simply be the city or county name, such as "Town of Fairplay Address Reference System." In other cases, it may provide a name for the address reference system for a smaller area within a jurisdiction, such as "Boulder County Mountain Addressing System." |
| XML Tag | < AddressReferenceSystemName> |
| XML Model | <xsd:simpleType id="AddressReferenceSystemName_type"> <xsd:restriction base="xsd:string" /> </xsd:simpleType> |
| XML Example | <AddressReferenceSystemName>Mountain Addressing Scheme</AddressReferenceSystemName> <AddressReferenceSystemName>pre-1990 System</AddressReferenceSystemName> |
| Quality Measures | Tabular Domain Measure |
| Quality Notes | Where geometry for the address reference system is available, the boundaries should be checked as well to support spatial queries. |
| Element Name | Address Reference System Numbering Rules |
|---|---|
| Other common names for this element | |
| Definition | The rules for assigning address numbers along a thoroughfare, including parity (odd/even side definition), and numbering increment distance and value. |
| Definition Source | New |
| Data Type | characterString |
| Existing Standards for this Element | None |
| Domain of Values for this Element | Locally defined. |
| Source of Values | Local |
| How Defined | Defined locally |
| Example | Address Numbering Rules: Odd numbers are on the south and west, and even numbers on the north and east sides of all streets. There will be one address increment allocated every 5.28 feet, resulting in 1000 addresses possible in each mile of road. The addresses will increase by a value of one unit at each increment. |
| Notes/Comments | 1. In assigning addresses it is important to know which side of a street should be assigned odd numbers, and which even. 2.Additionally, the distance between numbers should be specified. In some cases, this is given as a number of feet or meters, while in others, it is given as a number of addresses per block or per mile. 3. The amount by which the address number is to be increased at each increment should be defined. In many cases the next sequential number is used, e.g. 1, 3, 5, etc., while in other cases, the increment may be 2 units, 4 units or any other number determined appropriate by the Address Reference System Authority. 4. If any specific numbers are to be prohibited for local reasons, these should be identified here as well. 5. The rules for how blocks are numbered and where breaks occur are listed in the Address Reference System Block Rules element. |
| XML Tag | < AddressReferenceSystemNumberingRules> |
| XML Model | <xsd:simpleType id="AddressReferenceSystemNumberingRules_type"> <xsd:restriction base="xsd:string" /> </xsd:simpleType> |
| XML Example | <AddressReferenceSystemNumberingRules> 1. In assigning addresses it is important to know which side of a street should be assigned odd numbers, and which even. 2.Additionally, the distance between numbers should be specified. In some cases, this is given as a number of feet or meters, while in others, it is given as a number of addresses per block or per mile. 3. The amount by which the address number is to be increased at each increment should be defined. In many cases the next sequential number is used, e.g. 1, 3, 5, etc., while in other cases, the increment may be 2 units, 4 units or any other number determined appropriate by the Address Reference System Authority. </AddressReferenceSystemNumberingRules> |
| Quality Measures | See Address Reference System Rules Measure. |
| Quality Notes |
| Element Name | AddressReferenceSystemPlaceNameStateCountryAndZipCodeRules |
|---|---|
| Other common names for this element | |
| Definition | Rules for the use of place names, state names, country names, and ZIP Codes within the jurisdiction of an Address Authority. |
| Definition Source | New |
| Data Type | characterString |
| Existing Standards for this Element | Existing Rules for State Name abbreviations and Country Name abbreviations (see those elements for citations). |
| Domain of Values for this Element | Locally defined |
| Source of Values | Local |
| How Defined | Defined locally, often by ordinance and regulation |
| Example | 1. "All addresses within the Extent of this Address Reference System shall have the Municipal Place Name of "Anytown" and the State Name of "OHIO"." 2. "The following community Place Names may be used within this Address Reference System Extent: New Hope, Pine Level, Red Oak Village. The areas of these communities are shown on the map attached to the Address Ordinance for Any County." |
| Notes/Comments | The combinations of place names with state names, and ZIP Codes are defined by the Address Authority for all areas within Address Reference System Extent. For all areas outside the Extent, which are found in the mailing addresses used by a local government, or other user, the USPS is usually the best source of the proper association of a place name (community, city or place) with a State Name, and ZIP Code. For Country Names, rules usually specify how a Country Name will be used (fully spelled out, abbreviated, etc.) may be documented here. Further information on the standards and rules that are applied to State Names and Country Names are found in the element descriptions. |
| XML Tag | < AddressReferenceSystemPlaceNameStateCountryAndZipCodeRules> |
| XML Model | <xsd:simpleType id="AddressReferenceSystemPlaceNameStateCountryAndZipCodeRules_type"> <xsd:restriction base="xsd:string" /> </xsd:simpleType> |
| XML Example | <AddressReferenceSystemPlaceNameStateCountryAndZipCodeRules> 1. "All addresses within the Extent of this Address Reference System shall have the Municipal Place Name of "Anytown" and the State Name of "OHIO"." 2. "The following community Place Names may be used within this Address Reference System Extent: New Hope, Pine Level, Red Oak Village. The areas of these communities are shown on the map attached to the Address Ordinance for Any County." </AddressReferenceSystemPlaceNameStateCountryAndZipCodeRules> |
| Quality Measures | See Address Reference System Rules Measure. |
| Quality Notes |
| Element Name | AddressReferenceSystemRangeBreakpoint |
|---|---|
| Other common names for this element | |
| Definition | A point along a street or other thoroughfare within an Address Reference System where an address range beginning and/or endpoint is located. |
| Definition Source | New |
| Data Type | Geometry (Point), as defined in the Open Geospatial Consortium's "OpenGIS(R) Geography Markup Language (GML) Encoding Standard" version: 3.2.1 (see Part 6 for a complete citation) |
| 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 Range Span, Address Range Side, Address Range Parity, Address Reference System Range Breakline |
| How Defined | By Address Reference System rules |
| Example | Address Reference System Range Breakpoint:
|
| Notes/Comments | 1. Address Reference System Range Breakpoints may occur at intersections, or they may be defined by distances, or address number increments. They represent the point at which one address range is ended, and another begins. This is usually defined at the break from one series of 100 to the next, where ranges are defined as 100-199, 200-299, etc. In an axial type Address Reference System, where a grid of streets is formed, these breakpoint almost always occur at intersections. Where an axial system is based on other geometry, such as township/range/section lines, they may occur at the point where one unit ends and the next begins (e.g. a section line, or township or range line). In a non-axial system, ranges are normally based on distance (e.g. 1000 numbers per mile), and the breakpoints may be identified by their distance from the 0 point for the road. 2. Address Reference System Range Breakpoints may be connected within the Address Reference System Extent to other points having the same value (connecting all the points that represent the breakpoint between the 100-199 Address Range and the 200-299 Address Range) to create an Address Reference System Range Breakline. Such Address Reference System Range Breaklines are useful in assignment of new addresses, and in quality review of existing references to determine whether or not they fall within the Address Range with which they are associated. For further information on Address Reference System Range Breaklines, refer to the element. |
| XML Tag | < AddressReferenceSystemRangeBreakpoint> |
| XML Model | <xsd:complexType id="AddressReferenceSystemRangeBreakpoint_type"> <xsd:complexContent> <xsd:extension base="gml:PointType"> </xsd:extension> </xsd:complexContent> </xsd:complexType> |
| XML Example | <AddressReferenceSystemRangeBreakpoint> <gml:Point> <gml:pos>15000,15000</gml:pos> </gml:Point> </AddressReferenceSystemRangeBreakpoint> |
| Quality Measures | See Address Reference System Rules Measure. |
| Quality Notes |
| Element Name | AddressReferenceSystemRangePolygon |
|---|---|
| Other common names for this element | |
| Definition | A polygon created by connecting the Address Reference System Range Breaklines with the same value within an Address Reference System |
| Definition Source | New |
| Data Type | Geometry (Multisurface), as defined in the Open Geospatial Consortium's "OpenGIS(R) Geography Markup Language (GML) Encoding Standard" version: 3.2.1 (see Part 6 for a complete citation) |
| Existing Standards for this Element | None |
| Domain of Values for this Element | Based on range values in Address Reference System. |
| Source of Values | Local jurisdiction |
| Attributes Associated with this Element | Address Reference System Range Breakpoint, Address Reference System Range Breakline, Address Reference System Reference Polyline |
| How Defined | |
| Example | Address Reference System Range Polygon:
|
| Notes/Comments | The Address Reference System Range Polygon provides address assignment and quality assurance personnel with a means of identifying which ranges apply within a given area of an Address Reference System. In axial (or grid) type systems, with roughly rectangular blocks, these polygons should create an area of a long band where all of the addresses are or should be within a given block range. However, in less regular topography, or where the street pattern is more irregular, these polygons may be less coherent. They must not overlap. The lines are constructed in an axial system by connecting all of the Address Reference System Range Breaklines that have identical values and extending the polygon to the Address Reference System Range Breakline with the next higher value (for example those that represent the beginning of the "1200" block, and where the low values are 1200 and 1201 for left low and right low.) |
| XML Tag | < AddressReferenceSystemRangePolygon> |
| XML Model | <xsd:complexType id="AddressReferenceSystemRangePolygon_type"> <xsd:complexContent> <xsd:restriction base="gml:MultiSurfaceType"> </xsd:restriction> </xsd:complexContent> </xsd:complexType> |
| XML Example | <AddressReferenceSystemRangePolygon> <gml:MultiSurface> <gml:surfaceMember> <gml:Polygon> <gml:exterior> <gml:LinearRing> <gml:posList>1000 1000 1000 25000 20000 1000 20000 25000 1000 1000</gml:posList> </gml:LinearRing> </gml:exterior> </gml:Polygon> </gml:surfaceMember> </gml:MultiSurface> </AddressReferenceSystemRangePolygon> |
| Quality Measures | See Address Reference System Rules Measure. |
| Quality Notes |
| Element Name | AddressReferenceSystemReferenceDocumentCitation |
|---|---|
| Other common names for this element | Address Ordinance, Address Manual |
| Definition | A bibliographic reference to an ordinance, map, manual, or other document in which the rules governing an Address Reference System are written. |
| Definition Source | New |
| Data Type | characterString |
| Existing Standards for this Element | None |
| Domain of Values for this Element | Locally defined |
| Source of Values | Local |
| How Defined | Defined locally |
| Example | "Rules for the Anytown Address Reference System are found in the Anytown Address Ordinance, Chapter 15, Sections 1-29, of the Anytown Municipal Code (www.ci.anytown.na.us)" |
| Notes/Comments | The citation should be used initially, until all of the rules are documented within the Address Reference System Rules elements. However, once all of the rules are documented, the citation must be maintained to provide valuable source information for users. |
| XML Tag | < AddressReferenceSystemReferenceDocumentCitation> |
| XML Model | <xsd:simpleType id="AddressReferenceSystemReferenceDocumentCitation_type"> <xsd:restriction base="xsd:string" /> </xsd:simpleType> |
| XML Example | <AddressReferenceSystemReferenceDocumentCitation> "Rules for the Anytown Address Reference System are found in the Anytown Address Ordinance, Chapter 15, Sections 1-29, of the Anytown Municipal Code (www.ci.anytown.na.us)" </AddressReferenceSystemReferenceDocumentCitation> |
| Quality Measures | None |
| Quality Notes |
| Element Name | AddressReferenceSystemRules |
|---|---|
| Other common names for this element | Addressing Rules |
| Definition | The rules by which address numbers, street names and other components of a thoroughfare address are determined. |
| Definition Source | New |
| Data Type | characterString |
| Existing Standards for this Element | None |
| Domain of Values for this Element | Locally defined, see component elements |
| Source of Values | Local |
| How Defined | Defined locally, often by ordinance and encoded in terms of a spatial referencing system, described in the file-level metadata per FGDC's Content Standard for Digital Geospatial Metadata |
| Example | See component elements. |
| Notes/Comments | The rules are dependent upon the type of Address Reference System, and may also be explicitly provided in the component elements of Address Reference System Rules, or they may be referenced in the Address Reference System Reference Document Citation. |
| XML Tag | < AddressReferenceSystemRules> |
| XML Model | <xsd:complexType id="AddressReferenceSystemRules_type"> <xsd:sequence> <xsd:element id="AddressReferenceSystemBlockRules" type="addr_type:AddressReferenceSystemBlockRules_type" minOccurs="0" maxOccurs="unbounded"></xsd:element> <xsd:element id="AddressReferenceSystemNumberingRules" type="addr_type:AddressReferenceSystemNumberingRules_type" minOccurs="0" maxOccurs="unbounded"></xsd:element> <xsd:element id="AddressReferenceSystemStreetNamingRules" type="addr_type:AddressReferenceSystemStreetNamingRules_type" minOccurs="0" maxOccurs="unbounded"></xsd:element> <xsd:element id="AddressReferenceSystemStreetTypeDirectionalAndModfierRules" type="addr_type:AddressReferenceSystemStreetTypeDirectionalAndModifierRules_type" minOccurs="0" maxOccurs="unbounded"></xsd:element> <xsd:element id="AddressReferenceSystemPlaceNameStateCountyAndZipCodeRules" type="addr_type:AddressReferenceSystemPlaceNameStateCountryAndZipCodeRules_type" minOccurs="0" maxOccurs="unbounded"></xsd:element> <xsd:element id="AddressReferenceSystemSubaddressRules" type="addr_type:AddressReferenceSystemSubaddressRules_type" minOccurs="0" maxOccurs="unbounded"></xsd:element> </xsd:sequence> </xsd:complexType> |
| Element Name | AddressReferenceSystemStreetNamingRules |
|---|---|
| Other common names for this element | |
| Definition | The rules for the selection and use of street names within an Address Reference System |
| Definition Source | New |
| Data Type | characterString |
| Existing Standards for this Element | None |
| Domain of Values for this Element | Locally defined |
| Source of Values | Local |
| How Defined | Defined locally, often by ordinance or regulation |
| Example | 1. Street names shall not be duplicated within the extent of the City of Anywhere Address Reference System. 2. Streets running north-south shall be numbered, beginning at Main Street, and shall be called Avenues, while streets running east-west shall be given letter names (e.g. A, B, C) and shall be Streets. 3. Street names that are vulgar, profane, obscene, or contain racial, ethnic, religious or sexual terms shall not be permitted. 4. Streets within a subdivision shall have a theme, such as animals, birds, flowers, trees, etc. to unify the street naming and give the subdivision identity. |
| Notes/Comments | Specific street naming rules are helpful in maintaining unique street names and preserving existing patterns of street names that were historically established. |
| XML Tag | < AddressReferenceSystemStreetNamingRules> |
| XML Model | <xsd:simpleType id="AddressReferenceSystemStreetNamingRules_type"> <xsd:restriction base="xsd:string" /> </xsd:simpleType> |
| XML Example | <AddressReferenceSystemStreetNamingRules> 1. Street names shall not be duplicated within the extent of the City of Anywhere Address Reference System. 2. Streets running north-south shall be numbered, beginning at Main Street, and shall be called Avenues, while streets running east-west shall be given letter names (e.g. A, B, C) and shall be Streets. 3. Street names that are vulgar, profane, obscene, or contain racial, ethnic, religious or sexual terms shall not be permitted. 4. Streets within a subdivision shall have a theme, such as animals, birds, flowers, trees, etc. to unify the street naming and give the subdivision identify. </AddressReferenceSystemStreetNamingRules> |
| Quality Measures | See Address Reference System Rules Measure. |
| Quality Notes | See Address Reference System Rules Measure. |
| Element Name | AddressReferenceSystemStreetTypeDirectionalAndModifierRules |
|---|---|
| Other common names for this element | |
| Definition | Rules pertaining to the use of street types (suffix and prefix), directionals (prefix and suffix), and modifiers (prefix and suffix) of street names. |
| Definition Source | New |
| Data Type | characterString |
| Existing Standards for this Element | None |
| Domain of Values for this Element | Locally defined |
| Source of Values | Local |
| How Defined | Defined locally, often by ordinance or regulation |
| Example | 1. Only those street types included in the Anytown Address Reference System list of street types may be used in Anytown. 2. Prefix types may be used. 3. Only the words "Old" and "New" may be used as Pre-Modifiers. The words "Extended", "Bypass" and "Overpass" may be used as post-modifiers. |
| Notes/Comments | 1. Many communities have specific rules about the street types that are permitted, and further rules about the functional classes of streets to which various types can be applied. For example, the type "Boulevard" may only be used with a primary arterial, while "Court" may only be used with a short (one block) cul-de-sac or dead-end road. Additionally, the use of prefix types (e.g. "Avenue B", or "Calle San Antonio") is regulated in some places. 2.The use of directionals is often complex. In some Axial Address Reference Systems, quadrants are defined for specific areas bounded by the Axes. In others, the part of the area in which a street is located is described by "North" or "West". The Address Reference System provides that these rules and the areas described for the use of directionals can be documented. 3. Modifiers are words that are separated from the name by either types or directionals. The use of these may be regulated by local rules which are documented in this element. 4. The U.S. Postal Service, in Publication 28 provides a list of recognized street types, and directional values. The USPS does not recognize prefix types, and includes them with the Street Name (not recommended by this Standard), and also requires that any street type not included in Appendix C1 of Publication 28 be incorporated into the Street Name (also not recommended by this Standard). Modifiers are also not recognized separately by the USPS. For mailing purposes, the Complete Street Name element concatenates all of the parts of a Street Name, and is compatible with USPS standards. |
| XML Tag | < AddressReferenceSystemStreetTypeDirectionalAndModifierRules> |
| XML Model | <xsd:simpleType id="AddressReferenceSystemStreetTypeDirectionalAndModifierRules_type"> <xsd:restriction base="xsd:string" /> </xsd:simpleType> |
| XML Example | <AddressReferenceSystemStreetTypeDirectionalAndModifierRules> 1. Only those street types included in the Anytown Address Reference System list of street types may be used in Anytown. 2. Prefix types may be used. 3. Only the words "Old" and "New" may be used as Pre-Modifiers. The words "Extended", "Bypass" and "Overpass" may be used as post-modifiers. </AddressReferenceSystemStreetTypeDirectionalAndModifierRules> |
| Quality Measures | See Address Reference System Rules Measure. |
| Quality Notes |
| Element Name | AddressReferenceSystemSubaddressRules |
|---|---|
| Other common names for this element | |
| Definition | Rules that are applied to the addressing of areas within structures as subaddresses (units, suites, apartments, spaces, etc.) within a given Address Reference System |
| Definition Source | New |
| Data Type | characterString |
| Existing Standards for this Element | None |
| Domain of Values for this Element | Locally defined |
| Source of Values | Local |
| How Defined | Defined locally, often by ordinance or procedures manual. |
| Example | 1. Apartments are addressed using a four digit number where the first number represents the building, the second number the floor on which the unit is located, and the third and fourth numbers the individual apartment unit. 2. In a multi-story building, suites will be numbered in a clockwise manner from the elevator lobby, using even numbers on the right hand side, and odd numbers on the left hand side of the hallway. If the hallway is a single corridor, then the numbers will be assigned from one end of the structure to the other, in the same direction as the addresses on the street on which the building is addressed. |
| Notes/Comments | The rules for subaddresses may include the methods by which subaddresses are applied in a given situation. The rules may also specify the words that are allowed to identify subaddress types, such as unit, suite, space, apartment, and to prohibit the use of others. |
| XML Tag | < AddressReferenceSystemSubaddressRules> |
| XML Model | <xsd:simpleType id="AddressReferenceSystemSubaddressRules_type"> <xsd:restriction base="xsd:string" /> </xsd:simpleType> |
| XML Example | <AddressReferenceSystemSubaddressRules> 1. Apartments are addressed using a four digit number where the first number represents the building, the second number the floor on which the unit is located, and the third and fourth numbers the individual apartment unit. 2. In a multi-story building, suites will be numbered in a clockwise manner from the elevator lobby, using even numbers on the right hand side, and odd numbers on the left hand side of the hallway. If the hallway is a single corridor, then the numbers will be assigned from one end of the structure to the other, in the same direction as the addresses on the street on which the building is addressed. </AddressReferenceSystemSubaddressRules> |
| Quality Measures | See Address Reference System Rules Measure. |
| Quality Notes |
| Element Name | AddressReferenceSystemType |
|---|---|
| Other common names for this element | |
| Definition | The category of address reference system in use. The type of reference system determines and guides the assignment of numbers within the Address Reference System Extent. |
| Definition Source | New |
| Data Type | characterString |
| Existing Standards for this Element | None |
| Domain of Values for this Element | Yes: Axial, Linear Non-Axial, Area Based |
| Source of Values | FGDC Address Data Content Standard, Part One |
| How Defined | Local determination |
| Example | The Address Reference System for the District of Columbia is an axial (grid) system. |
| Notes/Comments | 1. An Address Reference System Type identifies the overall classification of the reference system. 2. The types include: a) Axial systems based on setting forth a framework consisting of streets, or other geometric lines to identify address numbering rules. Axial type systems include: i) grids based on either the street pattern, a geographic set of lines such as those forming the Public Land Survey System Grid, longitude and latitude lines or similar lines. ii) Radial patterns organized around primary arterial streets originating at a central point. b) Linear Non-axial systems, often found in areas of complex terrain where streets do not tend to travel in straight lines for any distance. i) Distance based systems in which each road has a defined starting point, and ii) Other types of linear organizational constructs that create a logical framework in which addresses are assigned. c) Area-based systems where the address numbers in a specified area are assigned by a non-geometric method, including chronological (where a number is assigned in the order in which a building or property is created regardless of its location), or by lot numbers (where these are not arranged in the usual sequential patterns found in axial and linear non-axial systems), or other means. 3. Some of these systems may have sub-types. In grid systems, some provide for 100 numbers per "block", others are numbered sequentially without regard for block breaks. In places with radial street patterns, axis streets or lines may originate at one or more places. In some cases a grid or radial pattern may extend beyond its original area, and be expanded in an outlying area using numbering that is continued from the original area. 4. The basis for numbering within any of these systems is created as an attribute of the system. Numbering rules are documented in the Address Reference System Numbering Rules element. These rules are expected to be applied consistently throughout the extent of the reference system, although in practice this is often not true. Additional information on Address Reference Systems may be found in the Address Reference Systems Introduction. |
| XML Tag | < AddressReferenceSystemType> |
| XML Model | <xsd:simpleType id="AddressReferenceSystemType_type"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="Axial"></xsd:enumeration> <xsd:enumeration value="Grid"></xsd:enumeration> <xsd:enumeration value="Radial"></xsd:enumeration> <xsd:enumeration value="Linear Non-Axial"></xsd:enumeration> <xsd:enumeration value="Distance"></xsd:enumeration> <xsd:enumeration value="Area Based"></xsd:enumeration> </xsd:restriction> </xsd:simpleType> |
| XML Example | <AddressReferenceSystemType>Grid</AddressReferenceSystemType> |
| Quality Measure | Tabular Domain Measure |
| Quality Notes |
| Element Name | AddressReferenceSystemRangeBreakline |
|---|---|
| Other common names for this element | |
| Definition | A line connecting the Address Reference System Range Breakpoints with the same value within an Address Reference System |
| Definition Source | New |
| Data Type | Geometry (Multicurve), as defined in the Open Geospatial Consortium's "OpenGIS(R) Geography Markup Language (GML) Encoding Standard" version: 3.2.1 (see Part 6 for a complete citation) |
| Existing Standards for this Element | None |
| Domain of Values for this Element | Based on range values in Address Reference System. |
| Source of Values | Local jurisdiction |
| Attributes Associated with this Element | |
| How Defined | |
| Example | Address Reference System Range Breakline:
|
| Notes/Comments | The Address Reference System Range Breakline provides address assignment and quality assurance personnel with a means of identifying which ranges apply within a given area of an Address Reference System. In axial (or grid) type systems, with roughly rectangular blocks, these lines should be relatively straight and parallel. However, in less regular topography, or where the street pattern is more irregular, these lines may converge or diverge. They should not cross. The lines are constructed in an axial system by connecting all of the Address Reference System Range Breakpoints that have identical values (for example those that represent the beginning of the "1200" block, and where the low values are 1200 and 1201 for left low and right low.) |
| XML Tag | < AddressReferenceSystemRangeBreakline> |
| XML Model | <xsd:complexType id="AddressReferenceSystemRangeBreakline_type"> <xsd:complexContent> <xsd:restriction base="gml:MultiCurveType"> </xsd:restriction> </xsd:complexContent> </xsd:complexType> |
| XML Example | <AddressReferenceSystemRangeBreakline> <gml:MultiCurve> <gml:curveMember> <gml:Curve> <gml:segments> <gml:LineStringSegment> <gml:posList>1000 15000 20000 15000 </gml:posList> </gml:LineStringSegment> </gml:segments>/gml:Curve> </gml:curveMember> </gml:MultiCurve> </AddressReferenceSystemRangeBreakline> |
| Quality Measures | See Address Reference System Rules Measure. |
| Quality Notes |
| Element Name | AddressReferenceSystemReferencePolyline |
|---|---|
| Other common names for this element | |
| Definition | A street, geometric line, or other line used to measure address number assignment intervals and ranges within an Address Reference System. The Address Reference System Reference Polyline may consist of a beginning point, one or more segments of a street centerline, geographically identified line, such as a line of latitude or longitude, a land-division based line, such as a township, range, or section line, or an imaginary line constructed for the purpose of allocating address ranges and address numbers. |
| Definition Source | New |
| Data Type | Geometry (Multicurve), as defined in the Open Geospatial Consortium's "OpenGIS(R) Geography Markup Language (GML) Encoding Standard" version: 3.2.1 (see Part 6 for a complete citation) |
| 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 Range Side, Address Range Parity, Address Range Span, Address Range Type, Address Reference System Range Breakpoint, Address Reference System Range Breakline |
| How Defined | Locally |
| Example | Address Reference System Reference Polyline:
|
| Notes/Comments | Theoretically, every street or other access route to an address within an Address Reference System can be construed as an Address Reference System Reference Polyline. However, in practice, where a framework of axes exists, a selection of major through streets is often used to identify breaks in address ranges, and to assist in locating the correct Address Range for a given local street. Every Complete Address Number is related to an Address Reference System Reference Polyline. 1. In an axial type Address Reference System, all Address Reference System Reference Polylines are, or could, by extension, be connected to one of the Address Reference System Axis lines. Each of the Address Reference System Reference Polylines has its Point of Beginning at the vertex of its intersection with the axis. 2. In a non-axial Address Reference System, a specific Point of Beginning is defined by the Address Reference System Authority for each Address Reference System Reference Polyline at the point where numbering for that polyline is commenced. |
| XML Tag | < AddressReferenceSystemReferencePolyline> |
| XML Model | <xsd:complexType id="AddressReferenceSystemReferencePolyline_type"> <xsd:complexContent> <xsd:restriction base="gml:MultiCurveType"></xsd:restriction> </xsd:complexContent> </xsd:complexType> |
| XML Example | <AddressReferenceSystemReferencePolyline> <gml:MultiCurve> <gml:curveMember> <gml:Curve> <gml:segments> <gml:LineStringSegment> <gml:posList>1000 15000 20000 15000 </gml:posList> </gml:LineStringSegment> </gml:segments>/gml:Curve> </gml:curveMember> </gml:MultiCurve> </AddressReferenceSystemReferencePolyline> |
| Quality Measures | See Address Reference System Rules Measure. |
| Quality Notes |