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. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The boundaries of most legal MCDs are as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

This dataset was created by TxDOT for internal purposes. TxDOT is not the authority for county boundary data for the state. These features were digitized by TxDOT from georeferenced USGS topo maps to enable the classification of roadway attributes for the purposes of satisfying federal and state reporting requirements, and to serve as a base layer for TxDOT's cartographic products. This version utilizes a generalized boundary along the coast, which is sometimes necessary for analysis in which it is important to encompass segments of roadways that travel over water. Roadways on bridges or causeways that span intracoastal waterways are not covered by detailed polygons that precisely follow the coastline, therefore a generalized boundary is needed for some types of analysis where it is important to preserve such relationships.Use at your own risk. Update Frequency: As NeededSource: Texas General Land OfficeSecurity Level: PublicOwned by TxDOT: FalseRelated LinksData Dictionary PDF [Generated 2025/03/14]

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. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2020 Census blocks nest within every other 2020 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

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. 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, 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.

The United States Census Bureau publishes geographic units used for tabulation of the 2020 Census population data in the 2020 TIGER/Line Shapefile. The geographic units, which remain constant throughout the decade, include counties, census tracts, block groups, and blocks. Fields have been added so data formatted or published by the council can be joined to the shapefile for analysis. Each Shapefile (.shp) is in a compressed file (.zip) format. Blocks.zip - Census Blocks BlockGroups.zip - Block Groups Tracts.zip - Census Tracts Counties.zip - Counties Cities.zip - Census Places (Cities) CDPs.zip - Census Designated Places Each 'Pop' file contains the 2020 Census population for the corresponding geographic level. BlocksPop.zip - Census Blocks 2020 Census Population BlockGroupPop.zip - Census Block Groups 2020 Census Population TractsPop.zip - Census Tracts 2020 Census Population CountiesPop.zip - Counties 2020 Census Population

Vector polygon map data of city limits from across the State of Texas containing 2142 features.

City limits GIS (Geographic Information System) data provides valuable information about the boundaries of a city, which is crucial for various planning and decision-making processes. Urban planners and government officials use this data to understand the extent of their jurisdiction and to make informed decisions regarding zoning, land use, and infrastructure development within the city limits.

By overlaying city limits GIS data with other layers such as population density, land parcels, and environmental features, planners can analyze spatial patterns and identify areas for growth, conservation, or redevelopment. This data also aids in emergency management by defining the areas of responsibility for different emergency services, helping to streamline response efforts during crises..

This city limits data is 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.

This site provides access to download an ArcGIS geodatabase or shapefiles for the 2017 Texas Address Database, compiled by the Center for Water and the Environment (CWE) at the University of Texas at Austin, with guidance and funding from the Texas Division of Emergency Management (TDEM). These addresses are used by TDEM to help anticipate potential impacts of serious weather and flooding events statewide. This is part of the Texas Water Model (TWM), a project to adapt the NOAA National Water Model [1] for use in Texas public safety. This database was compiled over the period from June 2016 to December 2017. A number of gaps remain (towns and cities missing address points), see Address Database Gaps spreadsheet below [4]. Additional datasets include administrative boundaries for Texas counties (including Federal and State disaster-declarations), Councils of Government, and Texas Dept of Public Safety Regions. An Esri ArcGIS Story Map [5] web app provides an interactive map-based portal to explore and access these data layers for download.

The address points in this database include their "height above nearest drainage" (HAND) as attributes in meters and feet. HAND is an elevation model developed through processing by the TauDEM method [2], built on USGS National Elevation Data (NED) with 10m horizontal resolution. The HAND elevation data and 10m NED for the continental United States are available for download from the Texas Advanced Computational Center (TACC) [3].

The complete statewide dataset contains about 9.28 million address points representing a population of about 28 million. The total file size is about 5GB in shapefile format. For better download performance, the shapefile version of this data is divided into 5 regions, based on groupings of major watersheds identified by their hydrologic unit codes (HUC). These are zipped by region, with no zipfile greater than 120mb: - North Tx: HUC1108-1114 (0.52 million address points) - DFW-East Tx: HUC1201-1203 (3.06 million address points) - Houston-SE Tx: HUC1204 (1.84 million address points) - Central Tx: HUC1205-1210 (2.96 million address points) - Rio Grande-SW Tx: HUC2111-1309 (2.96 million address points)

Additional state and county boundaries are included (Louisiana, Mississippi, Arkansas), as well as disaster-declaration status.

Compilation notes: The Texas Commission for State Emergency Communications (CSEC) provided the first 3 million address points received, in a single batch representing 213 of Texas' 254 counties. The remaining 41 counties were primarily urban areas comprising about 6.28 million addresses (totaling about 9.28 million addresses statewide). We reached the GIS data providers for these areas (see Contributors list below) through these emergency communications networks: Texas 9-1-1 Alliance, the Texas Emergency GIS Response Team (EGRT), and the Texas GIS 9-1-1 User Group. The address data was typically organized in groupings of counties called Councils of Governments (COG) or Regional Planning Commissions (RPC) or Development Councils (DC). Every county in Texas belongs to a COG, RPC or DC. We reconciled all counties' addresses to a common, very simple schema, and merged into a single geodatabase.

November 2023 updates: In 2019, TNRIS took over maintenance of the Texas Address Database, which is now a StratMap program updated annually [6]. In 2023, TNRIS also changed its name to the Texas Geographic Information Office (TxGIO). The datasets available for download below are not being updated, but are current as of the time of Hurricane Harvey.

References: [1] NOAA National Water Model [https://water.noaa.gov/map] [2] TauDEM Downloads [https://hydrology.usu.edu/taudem/taudem5/downloads.html] [3] NFIE Continental Flood Inundation Mapping - Data Repository [https://web.corral.tacc.utexas.edu/nfiedata/] [4] Address Database Gaps, Dec 2017 (download spreadsheet below) [5] Texas Address and Base Layers Story Map [https://www.hydroshare.org/resource/6d5c7dbe0762413fbe6d7a39e4ba1986/] [6] TNRIS/TxGIO StratMap Address Points data downloads [https://tnris.org/stratmap/address-points/]

Polygon layer of Texas college/university campuses. Update Frequency: As NeededSource: Other SourcesSecurity Level: PublicOwned by TxDOT: FalseRelated LinksData Dictionary PDF [Generated 2025/03/14]

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. Voting district is the generic name for geographic entities such as precincts, wards, and election districts established by State governments for the purpose of conducting elections. States participating in the 2010 Census Redistricting Data Program as part of Public Law 94-171 (1975) provided the Census Bureau with boundaries, codes, and names for their VTDs. Each VTD is identified by a 1- to 6-character alphanumeric census code that is unique within county. For the 2010 Census, Kentucky and Rhode Island are the only States that did not provide voting district boundaries as part of Phase 2 (the Voting District Project) of the Redistricting Data Program and no VTDs exist for these States in the 2020 Census data products. Note that only Montana and Oregon do not have complete coverage of VTDs for the 2020 Census.

The NOAA Office for Coastal Management (OCM) requested the creation of benthic habitat data along the southern Texas coast to support the Texas Seagrass Monitoring Program. The benthic habitat map was created from 1m ADS40 digital airborne imagery collected along the Texas coast during 2004 for the National Agriculture Imagery Program. The original raw images were reprocessed into 3-band true...

Network of Texas Railroads pulled from the Federal Railroad Administration (FRA) North American Rail Network (NARN) Rail Lines publicly available data. The data was clipped to the Texas State Boundary and queried to a records subset based on "current status or condition of rail line" as populated in the "NET" attribute. Additional fields were added and populated to adhere to TxDOT requirements and purposes.Update Frequency: 1 MonthsSource: Federal Railroad Administration (FRA)Security Level: PublicOwned by TxDOT: FalseRelated LinksFRA NARN Source DataTexas Railroads (Deprecated)Data Dictionary PDF [Generated 2025/04/29]

The Digital Geologic-GIS Map of the Yeager Creek Quadrangle, Texas is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (yeag_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (yeag_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (lyjo_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (lyjo_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (yeag_geology_metadata_faq.pdf). Please read the lyjo_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Texas Bureau of Economic Geology, University of Texas at Austin. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (yeag_geology_metadata.txt or yeag_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual _location as presented by this dataset. Users of this data should thus not assume the _location of features is exactly where they are portrayed in ArcGIS Pro, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.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) 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. Primary roads are generally divided, limited-access highways within the interstate highway system or under State management, and are distinguished by the presence of interchanges. These highways are accessible by ramps and may include some toll highways. The MAF/TIGER Feature Classification Code (MTFCC) is S1100 for primary roads. Secondary roads are main arteries, usually in the U.S. Highway, State Highway, and/or County Highway system. These roads have one or more lanes of traffic in each direction, may or may not bedivided, and usually have at-grade intersections with many other roads and driveways. They usually have both a local name and a route number. The MAF/TIGER Feature Classification Code (MTFCC) is S1200 for secondary roads.

Geospatial data about Texas ROW Centerline. Export to CAD, GIS, PDF, CSV and access via API.

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.

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 Topological Faces / Area Landmark Relationship File (FACESAL.dbf) contains a record for each face / area landmark relationship. 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 face to which a record in the Topological Faces / Area Landmark Relationship File (FACESAL.dbf) applies can be determined by linking to the Topological Faces Shapefile (FACES.shp) on the permanent topological face identifier (TFID) attribute. The area landmark to which a record in the Topological Faces / Area Landmark Relationship File (FACESAL.dbf) applies can be determined by linking to the Area Landmark Shapefile (AREALM.shp) on the area landmark identifier (AREAID) attribute. A face may be part of multiple area landmarks. An area landmark may consist of multiple faces.

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 Census Bureau includes landmarks in theMTDB for locating special features and to help enumerators during field operations. Some of the more common landmark types include area landmarks such as airports, cemeteries, parks, mountain peaks/summits, schools, and churches and other religious institutions. The Census Bureau has added landmark features to MTDB on an as-needed basis and made no attempt to ensure that all instances of a particular feature were included. The presence or absence of a landmark such as a hospital or prison does not mean that the living quarters associated with that landmark were geocoded to that census tabulation block or excluded from the census enumeration.

The Unpublished Digital Geologic-GIS Map of the Cave Creek School Quadrangle, Texas is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (ccsc_geology.gdb), a 10.1 ArcMap (.mxd) map document (ccsc_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (lyjo_geology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.txt) and FAQ (.pdf) formats, and a GIS readme file (lyjo_geology_gis_readme.pdf). Please read the lyjo_geology_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O'Meara (stephanie.omeara@colostate.edu; see contact information below). Presently, a GRI Google Earth KMZ/KML product doesn't exist for this map. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Texas Bureau of Economic Geology, University of Texas at Austin. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (ccsc_geology_metadata.txt or ccsc_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in ArcGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 14N. The data is within the area of interest of Lyndon B. Johnson National Historical Park.

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. School Districts are single-purpose administrative units within which local officials provide public educational services for the area's residents. The Census Bureau obtains the boundaries, names, local education agency codes, grade ranges, and school district levels for school districts from State officials for the primary purpose of providing the U.S. Department of Education with estimates of the number of children in poverty within each school district. This information serves as the basis for the Department of Education to determine the annual allocation of Title I funding to States and school districts. TIGER/Line Shapefiles include separate shapefiles for elementary, secondary and unified school districts. The school district boundaries are those in effect for the 2022-2023 school year, i.e., in operation as of January 1, 2023.