This data set contains the boundaries of Missouri's 114 counties plus the boundary of the city of St. Louis. This data set was created to provide the most accurate county boundary data available for the whole state with attributes that are correct and useable.

PDF. Zoning in unincorporated areas of St. Louis County, Missouri. Map scale is 1:62500. Link to metadata.

Analysis of ‘Missouri County Boundaries Map’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/f968c780-e24f-4fae-b094-6f840423289e on 12 February 2022.

--- Dataset description provided by original source is as follows ---

This data set contains the boundaries of Missouri's 114 counties plus the boundary of the city of St. Louis. This data set was created to provide the most accurate county boundary data available for the whole state with attributes that are correct and useable.

--- Original source retains full ownership of the source dataset ---

This data set contains the boundaries of Missouri's 114 counties plus the boundary of the city of St. Louis.

This data set contains the boundaries of Missouri's 114 counties plus the boundary of the city of St. Louis.

This data set contains the boundaries of Missouri's 114 counties plus the boundary of the city of St. Louis.

Dosya Dosya geçmişi Dosya kullanımı Küresel dosya kullanımı üstveriBu SVG dosyasının PNG önizlemesinin boyutu 681 599 pi

Web app displaying 2021-YTD NIBRS crime data. Data is included for all areas that the St. Louis County Police Department and the St. Louis County Park Rangers patrol. Additionally, data is included for the following police departments in St. Louis County: Ballwin, Bel Nor, Bel Ridge, Bella Villa, Bellefontaine Neighbors, Breckenridge Hills, Brentwood, Bridgeton, Country Club Hills, Chesterfield, Clayton, Crestwood, Creve Coeur, Des Peres, Ellisville, Eureka, Frontenac, Hillsdale, Kirkwood, Ladue, Lakeshire, Moline Acres, Maplewood, Normandy, Olivette, Overland, Pagedale, Riverview, Richmond Heights, Rock Hill, Saint Louis County, Shrewsbury, St. John, Sunset Hills, Town & Country, Velda City, Webster Groves, and Woodson Terrace.The data in this map should not be compared to previous UCR Part 1 crime data provided by the department. NIBRS data is counted differently, and comparisons made between the data will not be accurate.

Web App. View historic aerials in St. Louis County, Missouri from 1937 to 2024.

This polygon shapefile provides county or county-equivalent boundaries for the conterminous United States and was created specifically for use with the data tables published as Selected Items from the Census of Agriculture for the Conterminous United States, 1950-2012 (LaMotte, 2015). This data layer is a modified version of Historic Counties for the 2000 Census of Population and Housing produced by the National Historical Geographic Information System (NHGIS) project, which is identical to the U.S. Census Bureau TIGER/Line Census 2000 file, with the exception of added shorelines. Excluded from the CAO_STCOFIPS boundary layer are Broomfield County, Colorado, Menominee County, Wisconsin, and the independent cities of Virginia with the exception of the 3 county-equivalent cities of Chesapeake City, Suffolk, and Virginia Beach. The census of agriculture was not taken in the District of Columbia for 1959, but available data indicate few if any farms in that area, the polygon was left in place to preserve the areas of the surrounding counties. Baltimore City, Maryland was combined with Baltimore County and the St. Louis City, Missouri, was combined with St. Louis County. La Paz County, Arizona was combined with Yuma County, Arizona and Cibola County, New Mexico was combined with Valencia County, New Mexico. Minor county border changes were at a level of precision beyond the scope of the data collection. A major objective of the census data tabulation is to maintain a reasonable degree of comparability of agricultural data from census to census. The tabular data collection is from 14 different censuses where definitions and data collection techniques may change over time and while the data are mostly comparable, a degree of caution should be exercised when using the data in analysis procedures. While the data are at a county-level resolution, a regional approach is more appropriate than a county-by-county analysis. The main purpose of this layer is to provide a base to generate a county raster for the allocation of agricultural census values to specific (agricultural) pixels. Vector format is provided so the raster pixel size can be user designated. References cited: LaMotte, A.E., 2015, Selected items from the Census of Agriculture at the county level for the conterminous United States, 1950-2012: U.S. Geological Survey data release, http://dx.doi.org/10.5066/F7H13016. National Historical Geographic Information System, Minnesota Population Center, 2004, Historic counties for the 2000 census of population and housing: Minneapolis, MN, University of Minnesota, accessed 03/18/2013 at http://nhgis.org

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.