The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.

Vector polygon map data of property parcels from Denver, Colorado containing 231,961 features.

Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.

Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.

Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

A polygonal representation of the City and County of Denver's jurisdictional boundary. This datasets also includes all enclaves administered by other jurisdications that are located within the City and County of Denver's boundary.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The Address Range/Feature Name Relationship File contains a record for each address range/linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute that can be used to link to the Address Range Relationship File (addr.dbf). The linear feature name is identified by the linear feature identifier (LINEARID) attribute which can be used to link to the Feature Names Relationship File (featnames.dbf).

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

Creates four districts with rural county constituencies. Only splits counties near the Denver metro area, plus a portion of El Paso next to Woodland Park. Max deviance.My focus was on low deviation numbers, resulting in a few odd boundaries which could be adjusted:* D2 portion of El Paso County could switch to D5, adding ~2600 deviation.* D2 portion east of Brighton could shift west, adding <1000 deviation.* With higher deviation, the D1/D6/D7 boundaries near southwest Denver could more closely match county boundaries.* Moffat County might be better aligned with D3 than D2, but this would add 13,000 deviation. Maybe shift Baca & Las Animas Counties to D6 and extend D2 into southwest Douglas and west Fremont Counties?Plan Information Plan name: North, East, Southwest, Central Description: Creates four districts with rural county constituencies. Only splits counties near the Denver metro area, plus a portion of El Paso next to Woodland Park. Max deviance <1200. Non-Denver municipalities only split at exclaves.Plan Objectives(1) Keep population deviation as low as possible.(2) Only deviate from county boundaries around the Denver metro area, plus US-24 adjacent to Woodland Park.(3) Don't split municipalities or CDPs, except exclaves (to keep districts contiguous) and the edges of Denver (to keep within population target).A variation on this map could relax goal #2 in order to put Moffat in CD-3, Baca & Las Animas in CD-6, and extend CD-2 into western Fremont and southwest Douglas Counties.Area/perimeter ratio for CD-2 could be increased by putting Brighton in CD-4 and the Weld County I-25 corridor in CD-2. Alternatively, Brighton could be in CD-8 if Thornton was split between CD-8 and CD-2.

Infrastructure, such as roads, airports, water and energy transmission and distribution facilities, sewage treatment plants, and many other facilities, is vital to the sustainability and vitality of any populated area. Rehabilitation of existing and development of new infrastructure requires three natural resources: natural aggregate (stone, sand, and gravel), water, and energy http://rockyweb.cr.usgs.gov/frontrange/overview.htm.

The principal goals of the U.S. Geological Survey (USGS) Front Range Infrastructure Resources Project (FRIRP) were to develop information, define tools, and demonstrate ways to: (1) implement a multidisciplinary evaluation of the distribution and quality of a region's infrastructure resources, (2) identify issues that may affect availability of resources, and (3) work with cooperators to provide decision makers with tools to evaluate alternatives to enhance decision-making. Geographic integration of data (geospatial databases) can provide an interactive tool to facilitate decision-making by stakeholders http://rockyweb.cr.usgs.gov/frontrange/overview.htm.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edges refer to the linear topological primitives that make up the MTS. The All Lines shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines shapefile are available in relationship (.dbf) files that users must download separately. The All Lines shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

A polygonal representation of the Assessment Map Index for the City and County of Denver.

Disclaimer

ACCESS CONSTRAINTS:

None.

USE CONSTRAINTS:

The City and County of Denver is not responsible and shall not be liable to the user for damages of any kind arising out of the use of data or information provided by the City and County of Denver, including the installation of the data or information, its use, or the results obtained from its use.

ANY DATA OR INFORMATION PROVIDED BY THE City and County of Denver IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Data or information provided by the City and County of Denver shall be used and relied upon only at the user's sole risk, and the user agrees to indemnify and hold harmless the City and County of Denver, its officials, officers and employees from any liability arising out of the use of the data/information provided.

NOT FOR ENGINEERING PURPOSES

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

This dataset is a point feature representing range points within the City and County of Denver. Range points are termini for range lines, which serve as offsets to right-of-way lines and block lines. Range points are typically located below surface streets.

This is a comment on the preliminary Congressional Commission redistricting map. Along with providing feedback on that map, it offers a draft alternative that better meets the criteria of the Colorado Constitution. As background, I participated in redistricting initiatives in South Bend, Indiana, in the mid-1980s and for Indiana legislative seats after the 1990 census. I didn’t engage with redistricting during the rest of my 20-year military career. After retiring, and while serving as Public Trustee for El Paso County, I participated in redistricting efforts at the county and city level. I also stood for El Paso County Clerk in 2010. I have lived in Colorado since 2000. The draft alternative map is created using Dave’s Redistricting App (DRA) and can be found at https://davesredistricting.org/join/346f297c-71d1-4443-9110-b92e3362b105. I used DRA because it was more user-friendly in that it allows selection by precinct and by city or town, while the tool provided by the commission seems to allow only selection by census block (or larger clusters). The two tools also use slightly different population estimates, but this will be resolved when the 2020 data are released in August. These comments acknowledge that any map created using estimated populations will need to change to account for the actual census data.

Description of Draft Alternative

    My process started by

identifying large-scale geographic communities of interest within Colorado: the Western Slope/mountain areas, the Eastern Plains, Colorado Springs/El Paso County, the North Front Range, and Denver Metro. Two smaller geographic communities of interest are Pueblo and the San Luis Valley—neither is nearly large enough to sustain a district and both are somewhat distinct from their neighboring communities of interest. A choice thus must be made about which other communities of interest to group them with. El Paso County is within 0.3% of the optimal population, so it is set as District 5. The true Western Slope is not large enough to sustain a district, even with the obvious addition of Jackson County. Rather than including the San Luis Valley with the Western Slope, the preliminary commission map extends the Western Slope district to include all of Fremont County (even Canon City, Florence, and Penrose), Clear Creek County, and some of northern Boulder County. The draft alternative District 3 instead adds the San Luis Valley, the Upper Arkansas Valley (Lake and Chaffee Counties, and the western part of Fremont County), Park and Teller Counties, and Custer County. The draft alternative District 4 is based on the Eastern Plains. In the south, this includes the rest of Fremont County (including Canon City), Pueblo, and the Lower Arkansas Valley. In the north, this includes all of Weld County, retaining it as an intact political subdivision. This is nearly enough population to form a complete district; it is rounded out by including the easternmost portions of Adams and Arapahoe Counties. All of Elbert County is in this district; none of Douglas County is. The draft alternative District 2 is placed in the North Front Range and includes Larimer, Boulder, Gilpin, and Clear Creek Counties. This is nearly enough population to form a complete district, so it is rounded out by adding Evergreen and the rest of Coal Creek in Jefferson County. The City and County of Denver (and the Arapahoe County enclave municipalities of Glendale and Holly Hills) forms the basis of draft alternative District 1. This is a bit too large to form a district, so small areas are shaved off into neighboring districts: DIA (mostly for compactness), Indian Creek, and part of Marston. This leaves three districts to place in suburban Denver. The draft alternative keeps Douglas County intact, as well as the city of Aurora, except for the part that extends into Douglas County. The map prioritizes the county over the city as a political subdivision. Draft alternative District 6, anchored in Douglas County, extends north into Arapahoe County to include suburbs like Centennial, Littleton, Englewood, Greenwood Village, and Cherry Hills Village. This is not enough population, so the district extends west into southern Jefferson County to include Columbine, Ken Caryl, and Dakota Ridge. The northwestern edge of this district would run along Deer Creek Road, Pleasant Park Road, and Kennedy Gulch Road. Draft alternative District 8, anchored in Aurora, includes the rest of western Arapahoe County and extends north into Adams County to include Commerce City, Brighton (except the part in Weld County), Thornton, and North Washington. In the draft alternative, this district includes a sliver of Northglenn east of Stonehocker Park. While this likely would be resolved when final population totals are released, this division of Northglenn is the most notable division of a city within a single county other than the required division of Denver. Draft alternative District 7 encompasses what is left: The City and County of Broomfield; Westminster, in both Jefferson and Adams Counties; Federal Heights, Sherrelwood, Welby, Twin Lakes, Berkley, and almost all of Northglenn in western Adams County; and Lakewood, Arvada, Golden, Wheat Ridge, Morrison, Indian Hills, Aspen Park, Genesee, and Kittredge in northern Jefferson County. The border with District 2 through the communities in the western portion of Jefferson County would likely be adjusted after final population totals are released.

Comparison of Maps

Precise Population Equality
    The preliminary commission

map has exact population equality. The draft alternative map has a variation of 0.6% (4,239 persons). Given that the maps are based on population estimates, and that I left it at the precinct and municipality level, this aspect of the preliminary map is premature to pinpoint. Once final population data are released, either map would need to be adjusted. It would be simple to tweak district boundaries to achieve any desired level of equality. That said, such precision is a bit of a fallacy: errors in the census data likely exceed the 0.6% in the draft map, the census data will be a year out of date when received, and relative district populations will fluctuate over the next 10 years. Both the “good-faith effort†and “as practicable†language leave room for a bit of variance in service of other goals. The need to “justify any variance†does not mean “no variance will be allowed.†For example, it may be better to maintain unity in a community of interest or political subdivision rather than separate part of it for additional precision. The major sticking point here is likely to be El Paso County: given how close it seems to be to the optimal district size, will it be worth it to divide the county or one of its neighbors to achieve precision? The same question would be likely to apply among the municipalities in Metro Denver.

Contiguity
    The draft alternative map

meets this requirement. The preliminary commission map violates the spirit if not the actual language of this requirement. While its districts are connected by land, the only way to travel to all parts of preliminary Districts 3 and 4 without leaving the districts would be on foot. There is no road connection between the parts of Boulder County that are in District 3 and the rest of that district in Grand County without leaving the district and passing through District 2 in either Gilpin or Larimer Counties. There also is no road connection between some of the southwestern portions of Mineral County and the rest of District 4 without passing through Archuleta or Hinsdale Counties in District 3.

Voting Rights Act
    The preliminary staff

analysis assumes it would be possible to create a majority-minority district; they are correct, it can be done via a noncompact district running from the west side of Denver up to Commerce City and Brighton and down to parts of northeastern Denver and northern Aurora. Such a district would go against criteria for compactness, political subdivisions, and even other definitions of communities of interest. Staff asserts that the election of Democratic candidates in this area suffices for VRA. Appendix B is opaque regarding the actual non-White or Hispanic population in each district, but I presume that if they had created a majority-minority district they would have said so. In the draft alternative map, District 8 (Aurora, Commerce City, Brighton, and Thornton) has a 39.6% minority population and District 1 (Denver) has a 34.9% minority population. The proposals are similar in meeting this criterion.

Communities of Interest
    Staff presented a long list

of communities of interest. While keeping all of these intact would be ideal, drawing a map requires compromises based on geography and population. Many communities of interest overlap with each other, especially at their edges. This difficulty points to a reason to focus on existing subdivisions (county, city, and town boundaries): those boundaries are stable and overlap with shared public policy concerns. The preliminary commission map chooses to group the San Luis Valley, as far upstream as Del Norte and Creede, with Pueblo and the Eastern Plains rather than with the Western Slope/Mountains. To balance the population numbers, the preliminary commission map thus had to reach east in northern and central Colorado. The commission includes Canon City and Florence

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

This dataset is an index of Public Land Survey System (PLSS) Township, Range, and Section lines containing the City and County of Denver.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national filewith no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent dataset, or they can be combined to cover the entire nation. The Area Hydrography Shapefile contains the geometry and attributes of both perennial and intermittent area hydrography features, including ponds, lakes, oceans, swamps (up to the U.S. nautical three-mile limit), glaciers, and the area covered by large rivers, streams, and/or canals that are represented as double-line drainage. Single-line drainage water features can be found in the Linear Hydrography Shapefile (LINEARWATER.shp). Linear water features includes single-line drainage water features and artificial path features, where they exist, that run through double-line drainage features such as rivers, streams, and/or canals, and serve as a linear representation of these features.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national filewith no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent dataset, or they can be combined to cover the entire nation. The Area Hydrography Shapefile contains the geometry and attributes of both perennial and intermittent area hydrography features, including ponds, lakes, oceans, swamps (up to the U.S. nautical three-mile limit), glaciers, and the area covered by large rivers, streams, and/or canals that are represented as double-line drainage. Single-line drainage water features can be found in the Linear Hydrography Shapefile (LINEARWATER.shp). Linear water features includes single-line drainage water features and artificial path features, where they exist, that run through double-line drainage features such as rivers, streams, and/or canals, and serve as a linear representation of these features.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up the MTS. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces shapefile.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national filewith no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independentdata set, or they can be combined to cover the entire nation. The Address Range / Feature Name Relationship File (ADDRFN.dbf) contains a record for each address range / linear feature name relationship. The purpose of this relationship file is to identify all street names associated with each address range. An edge can have several feature names; an address range located on an edge can be associated with one or any combination of the available feature names (an address range can be linked to multiple feature names). The address range is identified by the address range identifier (ARID) attribute that can be used to link to the Address Ranges Relationship File (ADDR.dbf). The linear feature name is identified by the linear feature identifier (LINEARID) attribute that can be used to link to the Feature Names Relationship File (FEATNAMES.dbf).