The 2020 cartographic boundary KMLs are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. The cartographic boundary files include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The generalized boundaries of most incorporated places in this file are based on those as of January 1, 2020, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The generalized boundaries of all CDPs based on those delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

County wide map with Indiana State House boundaries 36" x 48" (E size).Base map layers include Streets, Hydrology, Parks, Schools, Railroads, Excluded Cities, Hospitals, Airfields, some recreation features, Address Grid and Township boundaries.

LANDSURVEY_COUNTY_POLY_IN is a 1:24,000-scale polygon shapefile, originally with a projection of Universal Transverse Mercator (UTM) North American Datum (NAD) 1983 zone 16. After republishing this shapefile by the IGIO, this data is with a projection of WGS84.This shapefile was derived from a predecessor coverage named "IN_LANDSURVEY." IN_LANDSURVEY is a digital representation of land survey features as represented on the USGS 1:24,000 digital raster graphic (DRG) series. ESRI ArcEdit 8.1 and ESRI ArcView 3.2 were used to extract the following shapefiles from IN_LANDSURVEY: LANDSURVEY_COUNTY_LINE_IN, LANDSURVEY_COUNTY_POLY_IN, LANDSURVEY_SECTIONS_LINE_IN, LANDSURVEY_SECTIONS_POLY_IN, LANDSURVEY_STATE_LINE_IN, LANDSURVEY_STATE_POLY_IN, LANDSURVEY_TOWNSHIPS_LINE_IN, and LANDSURVEY_TOWNSHIPS_POLY_IN.

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 TIGER/Line shapefiles include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2021, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

This dataset was developed to provide accurate street centerlines for Indiana, as part of Indiana's annual GIS Data harvest Data Sharing Initiative (IDSI) of the Indiana Geographic Information Office (IGIO).This data layer is an Esri file geodatabase polyline feature class that contains street centerlines maintained by county agencies in Indiana. It was released by the Indiana Geographic Information Office (IGIO) on February 1, 2022. The IGIO compiled the data as part of the Indiana Data Harvest program between the Indiana Geographic Information Council (IGIC) and all Indiana counties to provide the most accurate framework data for the citizens of Indiana. These layers include address points, street centerlines, land parcels, and governmental boundaries.

The 2015 cartographic boundary KMLs are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. The records in this file allow users to map the parts of Urban Areas that overlap a particular county. After each decennial census, the Census Bureau delineates urban areas that represent densely developed territory, encompassing residential, commercial, and other nonresidential urban land uses. In general, this territory consists of areas of high population density and urban land use resulting in a representation of the "urban footprint." There are two types of urban areas: urbanized areas (UAs) that contain 50,000 or more people and urban clusters (UCs) that contain at least 2,500 people, but fewer than 50,000 people (except in the U.S. Virgin Islands and Guam which each contain urban clusters with populations greater than 50,000). Each urban area is identified by a 5-character numeric census code that may contain leading zeroes. The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are as of January 1, 2010.

Indiana Orthophotography and DEM Download Story AppOrthoimagery: Indiana's newest digital imagery was collected from 2016 to 2019. The map on the right shows acquisition by year and the image resolution.Digital Elevation Data: Indiana's newest digital elevation data is being collected from 2016 to 2019. The map on the right shows acquisition by year. All data collected meets USGS QL-2 accuracy standards. More information

The State of Indiana Geographic Information Office (GIO) has published a State-wide Elevation Catalog consisting of Digital Elevation Model (DEM) files from 2005, 2011-2013, and 2016-2020 in Cloud-Optimized GeoTIFF (COG) format on the AWS Registry of Open Data Account. These COG formatted files support the dynamic imagery services available from the GIO ESRI-based imagery solution. The Open Data on AWS is a repository of publicly available datasets for access from AWS resources. These datasets are owned and maintained by the Indiana GIO. These images are licensed by Creative Commons 0 (CC0). Cloud Optimized GeoTIF behaves as a GeoTIFF in all products; however, the optimization becomes apparent when incorporating them into web services.

From the 2019 TIGER/Line Technical Documentation: The Census Bureau obtains school district boundaries, names, local education agency codes, grade ranges, and school district levels annually from state education officials. The Census Bureau collects this information for the primary purpose of providing the U.S. Department of Education with annual estimates of the number of children aged 5 through 17 in families in poverty within each school district, county, and state. 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. The 2023 118th Congressional District TIGER/Line Shapefiles include separate shapefiles for elementary, secondary, and unified school districts. The 2020 shapefiles contain information from the 2020 school year (i.e., districts in operation as of January 1, 2020). Unified school districts provide education to children of all school ages. In general, if there is a unified school district, no elementary or secondary school district exists. If there is an elementary school district, the secondary school district may or may not exist. In addition to regular functioning school districts, the TIGER/Line Shapefiles contain pseudoschool districts.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk Information And supporting data used to develop the risk data. The primary risk; classificatons used are the 1-percent-annual-chance flood event, the 0.2-percent- annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the UTM projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.

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.

A dataset listing Indiana counties by population for 2024.

Polygon file representing the Indiana State House district boundaries in Indianapolis and Marion County, Indiana.Data projection: NAD 1983 StatePlane Indiana East FIPS 1301 (US Feet)

Indiana's Statewide Lidar data is produced at 1.5-meter average post spacing for all 92 Indiana Counties covering more than 36,420 square miles. New Lidar data was captured except where previously captured Lidar data exists, or the participating County bought-up to a higher resolution of 1.0-meter average post spacing Lidar data. Existing Lidar data exists for: Porter, Steuben, Noble, De Kalb, Allen, Madison, Delaware, Hendricks, Marion, Hancock, Morgan, Johnson, Shelby, Monroe, and portions of Vermillion, Parke, Vigo, Clay, Sullivan, Knox, Gibson, and Posey. These existing Lidar datasets were seamlessly integrated into this new statewide dataset. From this seamless Lidar product a statewide 5-foot post spacing hydro-flattened DEM product was created and is also available. See the FGDC Metadata provided for more details.

This statewide project is divided into three geographic areas captured over a 3-year period (2011-2013):
Area 1 (2011) Indiana central counties: St. Joseph, Elkhart, Starke, Marshall, Kosciusko, Pulaski, Fulton, Cass, Miami, Wabash, Carroll, Howard, Clinton, Tipton, Boone, Hendricks, Marion, Morgan, Johnson, Monroe, Brown, Bartholomew, Lawrence, Jackson, Orange, Washington, Crawford, and Harrison.

Area 2 (2012) Indiana eastern counties: LaGrange, Steuben, Noble, DeKalb, Whitley, Allen, Huntington, Wells, Adams, Grant, Blackford, Jay, Hamilton, Madison, Delaware, Randolph, Hancock, Henry, Wayne, Shelby, Rush, Fayette, Union, Decatur, Franklin, Jennings, Ripley, Dearborn, Ohio, Scott, Jefferson, Switzerland, Clark, and Floyd.

Area 3 (2013) Indiana western counties: Lake, Porter, LaPorte, Newton, Jasper, Benton, White, Warren, Tippecanoe, Fountain, Montgomery, Vermillion, Parke, Putnam, Vigo, Clay, Owen, Sullivan, Greene, Knox, Daviess, Martin, Gibson, Pike, Dubois, Posey, Vanderburgh, Warrick, Spencer, and Perry.

Funders of OpenTopography Hosting of the Indiana Statewide Lidar and DEM data: USDA NRCS, Indiana, ISPLS Foundation, Indiana Geographic Information Office, Indiana Office of Technology, Indiana Geological Survey, Surdex Corporation, Vectren Energy Delivery, Indiana, Woolpert, Inc., and Individual IGIC Member Donations from Jim Stout, Jeff McCann, Cele Morris, Becky McKinley, Phil Worrall, and Andy Nicholson.

To explore a web map of topographic differencing for the entire state of Indiana click here

Mature Support Notice: This item is in mature support as of June 2021. A replacement item has not been identified at this time.This map presents land cover and detailed topographic maps for the United States. It uses the USA Topographic Map service. The map includes the National Park Service (NPS) Natural Earth physical map at 1.24km per pixel for the world at small scales, i-cubed eTOPO 1:250,000-scale maps for the contiguous United States at medium scales, and National Geographic TOPO! 1:100,000 and 1:24,000-scale maps (1:250,000 and 1:63,000 in Alaska) for the United States at large scales. The TOPO! maps are seamless, scanned images of United States Geological Survey (USGS) paper topographic maps.The maps provide a very useful basemap for a variety of applications, particularly in rural areas where the topographic maps provide unique detail and features from other basemaps.To add this map service into a desktop application directly, go to the entry for the USA Topo Maps map service. Tip: Here are some famous locations as they appear in this web map, accessed by including their location in the URL that launches the map:Grand Canyon, ArizonaGolden Gate, CaliforniaThe Statue of Liberty, New YorkWashington DCCanyon De Chelly, ArizonaYellowstone National Park, WyomingArea 51, Nevada

The 2024 Hamilton County High-Resolution 2D and 3D Land Cover Dataset provides an accurate and detailed representation of land cover across the entire county.The 2024 Hamilton County High-Resolution 2D and 3D Land Cover Dataset delivers an accurate and comprehensive representation of land cover throughout the county. Developed using Ecopia's advanced AI-driven feature extraction technology, this dataset makes use of 3-inch resolution aerial imagery and additional geospatial data sources such as lidar to provide precise land cover classifications at a high granularity.The resulting vector dataset is available at a 3-inch resolution, enabling detailed spatial analysis and supporting a range of governmental applications, including urban planning, environmental management, infrastructure development, and emergency response. All mapping products associated with this project are prepared and delivered in North American Datum 1983 (NAD83) 2011, Indiana State Plane Coordinate System, East Zone (EPSG 6459).Purpose: This dataset is intended to support key GIS activities aimed at enhancing county operations and decision-making, including hydrological modeling, urban planning, emergency response, infrastructure development, and environmental management. The data has undergone rigorous QA/QC processes to ensure accuracy and consistency across all land cover classifications.

The 2D vector land cover dataset includes:Bare LandBridgeBuildingDrivewayForestGrassOpen WaterParkingPavementRailwayRoadShrubSidewalkSports Field (Recreation Area) – PavedSports Field (Recreation Area) - UnpavedSwimming PoolTree Canopy The 3D vector land cover dataset includes:BridgeBuildingTree CanopyBridgeBuildingTree Canopy

This dataset contains County Boundary Lines for the Commonwealth of Kentucky. State boundary along Ohio River has been updated to reflect the Supreme Court Case regarding a boundary dispute between Kentucky, Indiana and Ohio in 1980 (Ohio v. Kentucky, 444 U.S. 335 (1980)).Online Linkage: https://ky.box.com/v/kymartian-KyBnds-County

Polygon file representing the Indiana State Senate boundaries within Indianapolis and Marion County, Indiana.Data projection: NAD 1983 StatePlane Indiana East FIPS 1301 (US Feet)

The 2022 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. 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.

description: The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the State Plane projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12000.; abstract: The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the State Plane projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12000.