|
description:
|
<DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 7 0;"><SPAN>Data Type: Dynamic. Vintage: Current. Editing of address data within the County's production Address Street Political (ASP) database, using the ASP Tools, generally occurs on a daily to weekly basis.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>The MasterAddress data consists of all base- and sub-address point features from the 'MasterAddress' feature class in the production ASP database, where sub-addresses are addresses with unit designations. </SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>The concept of base- and sub-addresses is essentially a parent-child relationship where referential integrity is employed within the database in conjunction with application logic (via the ASP Tools) to ensure no subaddress (child) may exist without an associated base (parent). Column SUBADRUNIT may be used to determine sub-addresses, as its value is null for base address features and not null for sub-addresses. </SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN STYLE="font-weight:bold;">COLUMNS (ATTRIBUTES)</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Column ADNO (address number) is the County's adress business "key" column and is unique for all base- and sub-address features. </SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Column ADRHSNO is the address house number. ADRHSNO, along with column STREET_NAME, cannot contain null values. Note the upper end of the range for legitimate house numbers within Jefferson County is ~ 36,000 (on the west axis of the Jefferson County Addressing Grid (JCAG), which extends the Denver Metropolitan Addressing Grid (DMAG)).</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Column ADRHSNOSFX is a three-character string where "1/2" is the only legitimate value. Note few addresses carry such a designation within Jefferson County.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Column STREET_DIRECTION_PREFIX is the street prefix direction.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Column STREET_NAME is the street name and may not contain null values.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Column STREET_TYPE is the street type abbreviation (if any). Jefferson County street type abbreviations conform to U.S. Post Office (USPS) standards and represent a subset of all such abbreviations deemed legitimate by the USPS. Eighteen distinct street type abbreviations are utilized within the County.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Column STREET_DIRECTION_SUFFIX is the suffix direction abbreviation (if any) for the street. </SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Column SUBADRUNIT is a seven-character unit designation for sub-addresses (addesses with units). Sub-addresses may not exist without an associated base address, and are generally carried in the County MasterAddress file only when such are associated with real property (for example, condominiums or townhomes, which exist as property records in the Assessor's parceling system and which are addressed with unit designations).</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Column ADDRESS is the full concatenated address where the individual columnar address components are separated by a space.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Column CITY_POSTAL is the post office city designation. CITY_POSTAL will carry the municipal name if the address is within a municipal boundary. Otherwise, for addrsses in unincorporated Jefferson County, the CITY_POSTAL designation is the municipal or community name for the post office for the zip code to which the address is attached. CITY_POSTAL should not be confused with CITY_MUNICIPAL which represents municipal status (the municipality in which the address resides, or unincprporated). </SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Column ZIP is the five-digit US Postal Service (USPS) zip code.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Column ADDRESS_TYPE is a textual description of the address - for example, 'BUSINESS OR COMMERCIAL', RESIDENTIAL', 'MIXED RESIDENTIAL AND BUSINESS', etc. This 'type' description is not carried in the County's production address data but derives from a lookup table, and is attached here for public convenience. In the County's normalized production MasterAddress data, a three-character ADRTYPECODE exists, so retrieving this description requires a tabular join. Note this data exists in support of Election Office business needs in the maintenance of County data in the State of Colorado Registration and Elections (SCORE) system.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Column AIN is the 13-byte parcel identification number associated with the address where AIN was formerly named either PARID or PIN in Assessor systems.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Numerous additional jurisdictional (political) columns are provided for public convenience. None are directly attached to the County's normalized production MasterAddress file, where tabular joins are required to associate these entities. See the explanation under "The Relational Nature of Addresses and Political Atrtribution" (below) for a better understanding of how address and political relations are managed in the County's Address Street Political (ASP) database. The 15 columns are: </SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>CITY_MUNICIPAL: The municipal status for the address ('UNINCORPORATED' else the city name for the municipality in which the address resides).</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>CITY_WARD: The two-character city ward designation for municipal addresses else '00' for unincorporated addresses.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>CITY_PRECINCT: The two-character city precinct designation for those cities still using such; otherwise '00'. </SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>COMMISSIONER_DISTRICT: The Commissioner District in which the address resides.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>COMMISSIONER_LIVING_IN_DIST: The name of the County Commissioner living in the commissioner district in which the address resides</SPAN><SPAN STYLE="font-weight:bold;">. ** Important: **</SPAN><SPAN>Jefferson County Commissioners are elected on an at-large basis regardless of which district is up for re-election. That is, all County registered voters participate in the election of commissioners -- not just those residing in the particular district in which the candidates reside.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>COUNTY_PRECINCT: The ten-digit county precinct designation consists of the following: Federal house {congressional} district (character 1), State senate district (characters 2-3), State house district (characters 4-5), County code (characters 6-7), Unique precinct identifier (characters 8-10).</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>FEDERAL_HOUSE_DISTRICT: The federal (congressional) house district in which the address resides.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>FEDERAL_HOUSE_REPRESENTATIVE: The name of the federal (congressional) house representative for the district.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>STATE_HOUSE_DISTRICT: The state house district in which the address resides.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>STATE_HOUSE_REPRESENTATIVE: The name of the state house representative for the district. </SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>STATE_SENATE_DISTRICT: The state senate district in which the address resides.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>STATE_SENATOR: The name of the state senator representing the district.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>RTD: The metropolitan-based Regional Transportation District (RTD) consists of many 'internal' districts noted by a letter designation.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>SJLID: A code for the South Jefferson County Local Improvement District (SJLID), which is 'SJ' if the address is within the district else null.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>TIFA: The Traffic Impact Fee Area (TIFA) designation for the address. For additional information concerning TIFA, contact the Jefferson County Planning & Zoning (P&Z) department.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Other column descriptions:</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>ADR_LONGITUDE: The longitude of the address in decimal degrees to five decimal places. Note the negative value for longitudes in the western hemisphere is not directly carried in this data but is implicitly presumed; users of these longitude values will need to explicitly state such.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>ADR_LATITUDE: The lalttude of the address in decimal degrees to five decimal places.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>ADR_ELEVATION: The elevation of the address in mean feet above sea level, per the U.S. Geological Survey (USGS) 10-meter digital elevation model (DEM) data.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>ADR_XY_META and ADR_XY_META_DESCRIPTION: A code and description describing how the eaddress is located (positioned). The domain of values for ADR_XY_META is four-fold: 'US' (user-specified), 'PC' (parcel centroid), 'PL' (parcel average of labelpoints), and 'I' (interpolated). Most address point features carry either the 'PC' or 'US' designations. 'PL' is a remnant of when the data existed in a legacy format edited using ArcInfo Workstation; no features now carry this designation. Interpolated addresses are generally those to which no parcel association is known nor do we now have other information as to where the address should be located spatially. Note interpolated addresses are in a continual process of review whereby we determine to what parcel and structure they are associated; otherwise, they are retired. It is worth noting that where ADR_XY_META is 'PC' and where multiple parcels are associated with the address, the parcel centroid location is for the primary AIN (where AINPRIORITY = '1').User-specified positioning is generally to the rooftop of the structure per DRAPP ortho-imagery. Due to the offset in the 2022 ortho-imagery relevant the 2020 through 2012 image data, addresses tied to structures seen in 2020 or prior imagery will match to such, where addresses positioned to structures per the 2022 imagery are to only new structures not seen in 2020 or prior imagery.</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>All column definitions and descriptions are available here: </SPAN><A href="file://admin.co.jeffco.us/admin/share/GIS/MetaData/Address/MasterAddress_Public_DataDictionary.pdf"><SPAN STYLE="font-weight:bold;">\\admin.co.jeffco.us\admin\share\GIS\MetaData\Address\MasterAddress_Public_DataDictionary.pdf </SPAN></A></P><P /><P STYLE="margin:0 0 7 0;"><SPAN STYLE="font-weight:bold;">THE RELATIONAL NATURE OF ADDRESSES AND POLITICAL ATTRIBUTION</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>In Jefferson County, core political or jurisdictional polygonal attributes are attached to an address point feature through the relation of an address point feature to the appropriate side of one and only one associated street feature, and to the one and only one polygonal political feature associated with the side of that street feature. This relational approach- address to matching side of street / side-of-street to matching political polygonal feature- has been employed by the County, in leu of point-in-poly spatial overlay, since the very start of County addressing operations in the 1980s. There are two primary reasons for use of this approach:</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>1) It is far easier to maintain the </SPAN></SPAN><SPAN STYLE="font-style:italic;"><SPAN>attribute accuracy</SPAN></SPAN><SPAN>of 33,000 street features relative 8,000 political polygons than it is to maintain the </SPAN><SPAN STYLE="font-style:italic;"><SPAN>spatial accuracy</SPAN></SPAN><SPAN><SPAN>of 220,000 address point features relative 8,000 polygons, and</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>2) Such a relational approach yields no ambiguity. It results in better data as well as greater confidence in our use of such.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>This relational approach to attaching jurisdictional attributes to addresses is essentially a two way join- address to street, street to political poly. Hence the County's street layer serves as the foundational cornerstone for addressing.</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>The core political attributes maintained in this fashion include city code (municipal status), city precinct, city ward, commissioner district, congressional (federal house) district, county precinct, regional transportation district (RTD), southeast Jefferson County local improvement district (SJLID), state house district, state senate district and traffice impact fee area (TIFA). Of these, only TIFA is not included in the makeup of 'ballot styles' as generated by the Elections Office. </SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Only one political element of the election ballot style is NOT determined relationally</SPAN><SPAN STYLE="font-style:italic;">: special districts</SPAN><SPAN>.. Address and tax authority (special district) correspondences are the only element of the ballot style determined through point-in-poly spatial overlay. Practical reasons drive why maintenance of address (ADNO) and tax authority (AUTHNO) relations occur spatially versus relationally: since the Assessor's Office maintains special district data independant of the County's Address Street Political (ASP) database, incorporating special district geometry in ASP's "atomic"-level 'BasePoly' polygonal data would necessitate 1) redundant data entry, 2) introduce complexities in data maintainence, and 3) require additional stafing (full-time employees, or FTEs) to do so.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN STYLE="font-weight:bold;"><SPAN>ADDRESSING BUSINESS RULES</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>The following are some of the core business rules in terms of County addressing, which are enforced applicationally through the ASP Tools and/or database-wise through Oracle: </SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>1) An address may match to (or is associated with) one side of one and only one street feature.</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>2) A side of a street feature will have one and only one associated polygonal feature (carrying political/jurisdictional attributes)</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>3) The political attributes for an address derive from the polygon associated with the side of the street feature on which the address "matches" (is associated with).</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>4) An address may not be created, or updated in terms of house number or street name attributes, unless a matching street feature exists in terms of street name and address range attribute components (as well as with correct parity).</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>5) A street feature may not be deleted or updated in terrms of street name or address range attribute components if such would "orphan" addresses.</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>6) A street feature may not be updated in terms of street name or address range attributes if such would cause an "overlap" with another street feature (potentially creating ambiguity in terms of address-street relations).</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>7) A sub-address (child) may not exist without a corresponding base (parent).</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Note many additional business rules are enforced in the County's Address Street Political (ASP) database by the ASP Tools, but the above form the foundation for overall application and database-logic.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN STYLE="font-weight:bold;"><SPAN>SPECIFICS</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>The production "ASP.MasterAddress" feature class lives in the ASPP geodatabase in SDE/Oracle and is maintained by the GIS team within the Business and Innovation Technology (BIT) division through the ASP Tools- a custom extension to ArcMap built in C#/.Net consisting of numerous toolbars and tools. This tool suite was developed expressly for maintenance of the address, street, political and ancillary data within ASPP and enforces Jefferson County's business rules for addressing. Editing of ASP's MasterAddress point data, BaseLine atomic linear and BasePoly atomic polygonal data occurs on an ad-hoc but generally daily basis. When such occurs, automated, integrated nightly Python processimg generates publication derivatives and pushes such to the County's spatial data warehouse and web applications.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>Quality assurance/quality control (QA/QC) is performed in the form of a report created by an automated Python process. That software gathers nearly 300 metrics for the address, street, political and ancillary data elements within ASPP and then performs more than 140 evaluations of those metrics, so that integrity is ensured across the numerous data relations maintained in the complex and sophisticated ASP data schema. </SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>The "MasterAddress feature class data is in State Plane Grid coordinates, Colorado Central Zone, NAD83 (US feet).</SPAN></SPAN></P></DIV></DIV></DIV> |
|
tags:
|
["address","addressmatch","association","ADNO","ASP","base","baseaddress","correspondence","feature","location","many-to-many","master","masteraddress","parcel","one-to-many","point","political","position","SCORE","street","sub","subaddress","SUBADRUNIT","type","address point feature","address type","master address","master address file","master address list","point feature"] |