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.

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

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.

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.

Important Note: This item is in mature support as of June 2021 and is no longer updated. 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 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.

This is a map of the county warning areas by each office that serves and forecasts for the state of Indiana.

This line layer represents base flood elevations (BFEs) created from FEMA Flood Rate Insurance Maps (FIRM). BFE lines indicate the rounded whole-foot water surface elevation of the 1% annual chance flood. BFE lines are required in riverine AE zones. AE Zones are areas inundated by 1% annual chance flooding (100-year flood), for which BFEs have been determined. Of 92 counties in Indiana, 86 are included in this DFIRM data set and 62 counties have BFE information. The following 6 counties are omitted  Allen, DeKalb, Johnson, Lake, Marion, Vanderburgh. These counties will be completed as work on the IDNR project progresses. This floodplain data may be used with an associated floodplain polygon shapefile and cross sections line shapefile. IDNR documentation states -  This database is an interim version of the Digital Flood Insurance Rate Map (DFIRM) Database. It does not fully meet all DFIRM specifications as found in  Guidelines and Specifications for Flood Hazard Mapping Partners, Appendix L: Guidance for Preparing Draft Digital Data and DFIRM Database . A fully compliant product is expected in 2005. 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 specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000. The DFIRM Database presents the flood risk information depicted on the FIRM in a digital format suitable for use in electronic mapping applications. The DFIRM database is a subset of the Digital FIS database that serves to archive the information collected during the FIS.Â

From 1985 to 1994, a series of reports on coal resources of selected counties in Indiana was published as part of the Special Report series of the Indiana Geological Survey. These reports included maps showing thickness of the Danville Coal Member (Dugger Formation, Pennsylvanian). The thickness maps were based on coal-test records, mine-map notations, and interpretations of geophysical logs that are included in the files of the Indiana Geological Survey. Data points were plotted by coal geologists of the Indiana Geological Survey and thickness contours were drawn by hand. The original work maps were compiled at a scale of 0.5 inch = 1 mile (scale, 1:126,720). Following completion of the investigations, the work maps showing thickness contours were subsequently scanned and digitized, and the resulting county coverages were then compiled into a single multicounty coverage. Different thickness ranges were utilized in the various counties; these thickness ranges (given in feet) are retained in the final map. Since the completion of this shapefile, additional data on coal thicknesses in selected areas has been obtained by the Indiana Geological Survey; interested users may wish to contact the Indiana Geological Survey for information on these more up-to-date sources.

Electric Service Territories (IURC) - Shows the Electric Service Territory (EST) boundaries in Indiana, maintained by personnel of the Indiana Utility Regulatory Commission (IURC). This layer is "live" and synchronized to automatically update whenever IURC personnel establish new boundaries.The layer was created to visually represent, as accurately as possible, the electric service territories served by the regulated electric service providers in the state of Indiana, pursuant to Cause Number 42868 (Indiana Utility Regulatory Commission) to establish an online GIS mapping environment to house, edit, and display visual interpretations or electric service territory rulings filed before and ruled by the Indiana Utility Regulatory Commission. The data represented in this layer is strictly a visual aide and a best interpretation of the legally approved Electric Service Territories as ruled by the Indiana Utility Regulatory Commission (IURC). These data are not legally binding or necessarily fully representative of the legal rulings.The following is excerpted from metadata provided by the IURC: "IN THE MATTER OF THE JOINT PETITION OF ELECTRICITY SUPPLIERS FOR (1) THE ESTABLISHMENT OF THE PROCEDURES TO APPROVE SERVICE AREA BOUNDARY AGREEMENTS UNDER IC 8-1-2.3-6(2) AND SERVICE CONSENTS UNDER IC 8-1-2.3-4(A), AND (2) MODIFICATION OF THE FORM AND MAINTENANCE OF MAPS OF ASSIGNED SERVICE AREAS ESTABLISHED PURSUANT TO IC 8-1-2.3-1, ET SEQ. AND THE COMMISSION'S FEBRUARY 19, 1981 ORDER IN CAUSE NO. 36299"

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

This dataset contains County Boundary Polygons 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)).