View In:
ArcGIS JavaScript
ArcGIS Online Map Viewer
Service Description: <div style='font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif;'><div style='margin-bottom:3rem;'><div><div style='max-width:100%; display:inherit;'><p style='margin-top:0px; margin-bottom:0px; padding-bottom:1em; font-family:"Segoe UI", Arial, sans-serif;'><font size='3'>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.</font></p><p style='margin-top:0px; margin-bottom:0px; padding-bottom:1em; font-family:"Segoe UI", Arial, sans-serif;'></p><p style='margin-top:0px; margin-bottom:0px; padding-bottom:1em; font-family:"Segoe UI", Arial, sans-serif;'><font size='3'>Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.</font></p></div></div></div></div><div style='font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;'></div><div style='margin-bottom:3rem; display:inherit; font-family:"Avenir Next W01", "Avenir Next W00", "Avenir Next", Avenir, "Helvetica Neue", sans-serif; font-size:16px;'><div style='margin-bottom:3rem; display:inherit;'></div></div>
All Layers and Tables
Has Versioned Data: false
MaxRecordCount: 2000
Supported Query Formats: JSON
Supports Query Data Elements: true
Layers:
Description: 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.Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.
Service Item Id: 14d4b6131a424af19163ca505282bc52
Copyright Text: State of Nebraska, US Census Bureau
Spatial Reference:
102100
(3857)
LatestVCSWkid(0)
Initial Extent:
XMin: -1.1012761155231694E7
YMin: 4913570.827230474
XMax: -1.0682865428520398E7
YMax: 5138928.563051244
Spatial Reference: 102100
(3857)
LatestVCSWkid(0)
Full Extent:
XMin: -1.1597342429142809E7
YMin: 4851970.933822093
XMax: -1.0585243888573058E7
YMax: 5322679.261429709
Spatial Reference: 102100
(3857)
LatestVCSWkid(0)
Units: esriMeters
Document Info:
Title: Map
Author:
Comments:
Subject:
Category:
Keywords: Nebraska,Census
AntialiasingMode: null
TextAntialiasingMode: null
Enable Z Defaults: false
Supports ApplyEdits With Global Ids: false
Support True Curves : true
Only Allow TrueCurve Updates By TrueCurveClients : true
Supports Return Service Edits Option : true
Supports Dynamic Layers: false
Child Resources:
Info
Query Data Elements
Relationships
SharedTemplates
Supported Operations:
Query
Query Contingent Values
QueryDomains
Extract Changes