This data set includes cities in the United States, Puerto Rico and the U.S. Virgin Islands. These cities were collected from the 1970 National Atlas of the United States. Where applicable, U.S. Census Bureau codes for named populated places were associated with each name to allow additional information to be attached. The Geographic Names Information System (GNIS) was also used as a source for additional information. This is a revised version of the December, 2003, data set.

This layer is sourced from maps.bts.dot.gov.

The 2020 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. A consolidated city is a unit of local government for which the functions of an incorporated place and its county or minor civil division (MCD) have merged. This action results in both the primary incorporated place and the county or MCD continuing to exist as legal entities, even though the county or MCD performs few or no governmental functions and has few or no elected officials. Where this occurs, and where one or more other incorporated places in the county or MCD continue to function as separate governments, even though they have been included in the consolidated government, the primary incorporated place is referred to as a consolidated city. The Census Bureau classifies the separately incorporated places within the consolidated city as place entities and creates a separate place (balance) record for the portion of the consolidated city not within any other place. The generalized boundaries of the consolidated cities in this file are based on those as of January 1, 2020, as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

This map layer includes cities and towns in Oregon. These cities were clipped from a larger dataset of cities collected from the 1970 National Atlas of the United States. Where applicable, U.S. Census Bureau codes for named populated places were associated with each name to allow additional information to be attached. The Geographic Names Information System (GNIS) was also used as a source for additional information. This is a revised version of the December 2003 map layer.

The Digital City Map (DCM) data represents street lines and other features shown on the City Map, which is the official street map of the City of New York. The City Map consists of 5 different sets of maps, one for each borough, totaling over 8000 individual paper maps. The DCM datasets were created in an ongoing effort to digitize official street records and bring them together with other street information to make them easily accessible to the public. The Digital City Map (DCM) is comprised of seven datasets; Digital City Map, Street Center Line, City Map Alterations, Arterial Highways and Major Streets, Street Name Changes (areas), Street Name Changes (lines), and Street Name Changes (points). All of the Digital City Map (DCM) datasets are featured on the Streets App All previously released versions of this data are available at BYTES of the BIG APPLE- Archive

Important Note: This item is in mature support as of June 2023 and will retire in December 2025. A new version of this item is available for your use.The layers going from 1:1 to 1:1.5M present the 2010 Census Urbanized Areas (UA) and Urban Clusters (UC). A UA consists of contiguous, densely settled census block groups (BGs) and census blocks that meet minimum population density requirements (1000 people per square mile (ppsm) / 500 ppsm), along with adjacent densely settled census blocks that together encompass a population of at least 50,000 people. A UC consists of contiguous, densely settled census BGs and census blocks that meet minimum population density requirements, along with adjacent densely settled census blocks that together encompass a population of at least 2,500 people, but fewer than 50,000 people. The dataset covers the 50 States plus the District of Columbia within United States. The layer going over 1:1.5M presents the urban areas in the United States derived from the urban areas layer of the Digital Chart of the World (DCW). It provides information about the locations, names, and populations of urbanized areas for conducting geographic analysis on national and large regional scales. To download the data for this layer as a layer package for use in ArcGIS desktop applications, refer to USA Census Urban Areas.

This layer presents the locations of major cities within the United States with populations of approximately 10,000 or greater, state capitals, and the national capital. Major Cities are locations containing population totals from the 2020 Census.The points represent U.S. Census Places polygons sourced from U.S. Census Bureau 2020 TIGER FGDB (National Sub-State). Attribute fields include 2020 total population from the U.S. Census Public Law 94 data that symbolize the city points using these six classifications: Class Population Range 5 2,500 – 9,999 6 10,000 – 49,999 7 50,000 – 99,999 8 100,000 – 249,999 9 250,000 – 499,999 10 500,000 and overThis ready-to-use layer can be used in ArcGIS Pro and in ArcGIS Online and its configurable apps, dashboards, StoryMaps, custom apps, and mobile apps. The data can also be exported for offline workflows. Cite the 'U.S. Census Bureau' when using this data.

This data set includes cities in the United States, Puerto Rico and the U.S. Virgin Islands. These cities were collected from the 1970 National Atlas of the United States. Where applicable, U.S. Census Bureau codes for named populated places were associated with each name to allow additional information to be attached. The Geographic Names Information System (GNIS) was also used as a source for additional information. This is a revised version of the December, 2003, data set.

This layer is sourced from maps.bts.dot.gov.

This dataset is part of the Geographical repository maintained by Opendatasoft. This dataset contains data for places and equivalent entities in United States of America.This layer 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. Processors and tools are using this data. Enhancements Add ISO 3166-3 codes. Simplify geometries to provide better performance across the services. Add administrative hierarchy.

Housing Demographics in the 2010 CensusThis feature layer contains demographics about housing as reported by the U.S. Census Bureau (USCB) in the 2010 U.S. Census. These attributes cover topics such as owner status of housing units (vacant, owner, renter), count of residents per housing unit, and housing unit by householder age. A small subset of attributes from the 2000 Census are also included as reference.Per the Census, "Also known as the Population and Housing Census, the Decennial U.S. Census is designed to count every resident in the United States. It is mandated by Article I, Section 2 of the Constitution and takes place every 10 years. The data collected by the decennial census determine the number of seats each state has in the U.S. House of Representatives and is also used to distribute hundreds of billions of dollars in federal funds to local communities."Four layers are available: state, county, census tract, and census block group. Each layer contains the same set of demographic attributes. Each geography level has a viewing range optimal for the geography size, and the map has increasing detail as you zoom in to smaller areas. Only one geography is in view at any time.Housing Demographics 2010 CensusData currency: 2010Data modification: NoneData source: Explore Census DataFor more information: Households and Families: 2010For feedback, please contact: ArcGIScomNationalMaps@esri.comData Processing notes:State and county boundaries are simplified representations offered from the Census Bureau's 2010 MAF/TIGER databaseTract and block group boundaries are 2010 TIGER boundaries with select water area boundaries erased (coastlines and major water bodies)Field names and aliases are processed by Esri as created for the ArcGIS Platform.For a list of fields and alias names, access the following excel document.U.S. Census BureauPer USCB, "the Census Bureau is the federal government’s largest statistical agency. We are dedicated to providing current facts and figures about America’s people, places, and economy. Federal law protects the confidentiality of all the information the Census Bureau collects."

This dataset contains information about the demographics of all US cities and census-designated places with a population greater or equal to 65,000. This data comes from the US Census Bureau's 2015 American Community Survey. This product uses the Census Bureau Data API but is not endorsed or certified by the Census Bureau.

Notice: this is not the latest Heat Island Severity image service. For 2023 data, visit https://tpl.maps.arcgis.com/home/item.html?id=db5bdb0f0c8c4b85b8270ec67448a0b6. This layer contains the relative heat severity for every pixel for every city in the United States. This 30-meter raster was derived from Landsat 8 imagery band 10 (ground-level thermal sensor) from the summers of 2018 and 2019.Federal statistics over a 30-year period show extreme heat is the leading cause of weather-related deaths in the United States. Extreme heat exacerbated by urban heat islands can lead to increased respiratory difficulties, heat exhaustion, and heat stroke. These heat impacts significantly affect the most vulnerable—children, the elderly, and those with preexisting conditions.The purpose of this layer is to show where certain areas of cities are hotter than the average temperature for that same city as a whole. Severity is measured on a scale of 1 to 5, with 1 being a relatively mild heat area (slightly above the mean for the city), and 5 being a severe heat area (significantly above the mean for the city). The absolute heat above mean values are classified into these 5 classes using the Jenks Natural Breaks classification method, which seeks to reduce the variance within classes and maximize the variance between classes. Knowing where areas of high heat are located can help a city government plan for mitigation strategies.This dataset represents a snapshot in time. It will be updated yearly, but is static between updates. It does not take into account changes in heat during a single day, for example, from building shadows moving. The thermal readings detected by the Landsat 8 sensor are surface-level, whether that surface is the ground or the top of a building. Although there is strong correlation between surface temperature and air temperature, they are not the same. We believe that this is useful at the national level, and for cities that don’t have the ability to conduct their own hyper local temperature survey. Where local data is available, it may be more accurate than this dataset. Dataset SummaryThis dataset was developed using proprietary Python code developed at The Trust for Public Land, running on the Descartes Labs platform through the Descartes Labs API for Python. The Descartes Labs platform allows for extremely fast retrieval and processing of imagery, which makes it possible to produce heat island data for all cities in the United States in a relatively short amount of time.What can you do with this layer?This layer has query, identify, and export image services available. Since it is served as an image service, it is not necessary to download the data; the service itself is data that can be used directly in any Esri geoprocessing tool that accepts raster data as input.Using the Urban Heat Island (UHI) Image ServicesThe data is made available as an image service. There is a processing template applied that supplies the yellow-to-red or blue-to-red color ramp, but once this processing template is removed (you can do this in ArcGIS Pro or ArcGIS Desktop, or in QGIS), the actual data values come through the service and can be used directly in a geoprocessing tool (for example, to extract an area of interest). Following are instructions for doing this in Pro.In ArcGIS Pro, in a Map view, in the Catalog window, click on Portal. In the Portal window, click on the far-right icon representing Living Atlas. Search on the acronyms “tpl” and “uhi”. The results returned will be the UHI image services. Right click on a result and select “Add to current map” from the context menu. When the image service is added to the map, right-click on it in the map view, and select Properties. In the Properties window, select Processing Templates. On the drop-down menu at the top of the window, the default Processing Template is either a yellow-to-red ramp or a blue-to-red ramp. Click the drop-down, and select “None”, then “OK”. Now you will have the actual pixel values displayed in the map, and available to any geoprocessing tool that takes a raster as input. Below is a screenshot of ArcGIS Pro with a UHI image service loaded, color ramp removed, and symbology changed back to a yellow-to-red ramp (a classified renderer can also be used): Other Sources of Heat Island InformationPlease see these websites for valuable information on heat islands and to learn about exciting new heat island research being led by scientists across the country:EPA’s Heat Island Resource CenterDr. Ladd Keith, University of Arizona Dr. Ben McMahan, University of Arizona Dr. Jeremy Hoffman, Science Museum of Virginia Dr. Hunter Jones, NOAADaphne Lundi, Senior Policy Advisor, NYC Mayor's Office of Recovery and ResiliencyDisclaimer/FeedbackWith nearly 14,000 cities represented, checking each city's heat island raster for quality assurance would be prohibitively time-consuming, so The Trust for Public Land checked a statistically significant sample size for data quality. The sample passed all quality checks, with about 98.5% of the output cities error-free, but there could be instances where the user finds errors in the data. These errors will most likely take the form of a line of discontinuity where there is no city boundary; this type of error is caused by large temperature differences in two adjacent Landsat scenes, so the discontinuity occurs along scene boundaries (see figure below). The Trust for Public Land would appreciate feedback on these errors so that version 2 of the national UHI dataset can be improved. Contact Dale.Watt@tpl.org with feedback.

Incorporated PlacesThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau, displays Incorporated Places (legal entities). Per USCB, "The legal designations, powers, and functions of incorporated places vary from state to state. Incorporated places include cities, towns (except in New England, New York, and Wisconsin where the Census Bureau recognizes towns as MCDs for census purposes), boroughs (except in Alaska, where the Census Bureau recognizes boroughs as equivalents of counties, and New York, where the Census Bureau recognizes the five boroughs that constitute New York City as MCDs), villages, and other lesser known identifiers."Trenton, New JerseyData currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Incorporated Places) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 88 (Series Information for Census Tract State-based TIGER/Line Shapefiles, Current)OGC API Features Link: (Incorporated Places) copy this link to embed it in OGC Compliant viewersFor more information, please visit: Series Information for Place State-based TIGER/Line Shapefiles, CurrentFor feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets

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 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, 2017, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:

• Metadata is missing or incomplete for some layers at this time and will be continuously improved.
  
• We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.

Purpose

County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, coastal buffers are removed, leaving the land-based portions of jurisdictions. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system
• Place Name: CDTFA incorporated (city) or county name
• County: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

Accuracy

CDTFA"s source data notes the following about accuracy:

City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI =

This point shapefile depicts cities and towns in the United States, Puerto Rico, and the United States Virgin Islands. A city or town is a place with a recorded population, usually with at least one central area that provides commercial activities. Cities are generally larger than towns; no distinction is made between cities and towns in this map layer. This layer is part of the 2014 National Transportation Atlas Database.

The 2019 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 generalized boundaries for counties and equivalent entities are as of January 1, 2010.

The 2020 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. The records in this file allow users to map the parts of the 116th Congressional Districts that overlap a particular county. Congressional Districts are the 435 areas from which people are elected to the U.S. House of Representatives. After the apportionment of congressional seats among the states based on census population counts, each state is responsible for establishing congressional districts for the purpose of electing representatives. Each congressional district is to be as equal in population to all other congressional districts in a state as practicable. The 116th Congress is seated from January 2019 to 2021. The cartographic boundary files for the District of Columbia, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands) each contain a single record for the non-voting delegate district in these areas. The boundaries of all other congressional districts reflect information provided to the Census Bureau by the states by May 1, 2018. 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 mostly as of January 1, 2020, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

IntroductionClimate Central’s Surging Seas: Risk Zone map shows areas vulnerable to near-term flooding from different combinations of sea level rise, storm surge, tides, and tsunamis, or to permanent submersion by long-term sea level rise. Within the U.S., it incorporates the latest, high-resolution, high-accuracy lidar elevation data supplied by NOAA (exceptions: see Sources), displays points of interest, and contains layers displaying social vulnerability, population density, and property value. Outside the U.S., it utilizes satellite-based elevation data from NASA in some locations, and Climate Central’s more accurate CoastalDEM in others (see Methods and Qualifiers). It provides the ability to search by location name or postal code.The accompanying Risk Finder is an interactive data toolkit available for some countries that provides local projections and assessments of exposure to sea level rise and coastal flooding tabulated for many sub-national districts, down to cities and postal codes in the U.S. Exposure assessments always include land and population, and in the U.S. extend to over 100 demographic, economic, infrastructure and environmental variables using data drawn mainly from federal sources, including NOAA, USGS, FEMA, DOT, DOE, DOI, EPA, FCC and the Census.This web tool was highlighted at the launch of The White House's Climate Data Initiative in March 2014. Climate Central's original Surging Seas was featured on NBC, CBS, and PBS U.S. national news, the cover of The New York Times, in hundreds of other stories, and in testimony for the U.S. Senate. The Atlantic Cities named it the most important map of 2012. Both the Risk Zone map and the Risk Finder are grounded in peer-reviewed science.Back to topMethods and QualifiersThis map is based on analysis of digital elevation models mosaicked together for near-total coverage of the global coast. Details and sources for U.S. and international data are below. Elevations are transformed so they are expressed relative to local high tide lines (Mean Higher High Water, or MHHW). A simple elevation threshold-based “bathtub method” is then applied to determine areas below different water levels, relative to MHHW. Within the U.S., areas below the selected water level but apparently not connected to the ocean at that level are shown in a stippled green (as opposed to solid blue) on the map. Outside the U.S., due to data quality issues and data limitations, all areas below the selected level are shown as solid blue, unless separated from the ocean by a ridge at least 20 meters (66 feet) above MHHW, in which case they are shown as not affected (no blue).Areas using lidar-based elevation data: U.S. coastal states except AlaskaElevation data used for parts of this map within the U.S. come almost entirely from ~5-meter horizontal resolution digital elevation models curated and distributed by NOAA in its Coastal Lidar collection, derived from high-accuracy laser-rangefinding measurements. The same data are used in NOAA’s Sea Level Rise Viewer. (High-resolution elevation data for Louisiana, southeast Virginia, and limited other areas comes from the U.S. Geological Survey (USGS)). Areas using CoastalDEM™ elevation data: Antigua and Barbuda, Barbados, Corn Island (Nicaragua), Dominica, Dominican Republic, Grenada, Guyana, Haiti, Jamaica, Saint Kitts and Nevis, Saint Lucia, Saint Vincent and the Grenadines, San Blas (Panama), Suriname, The Bahamas, Trinidad and Tobago. CoastalDEM™ is a proprietary high-accuracy bare earth elevation dataset developed especially for low-lying coastal areas by Climate Central. Use our contact form to request more information.Warning for areas using other elevation data (all other areas)Areas of this map not listed above use elevation data on a roughly 90-meter horizontal resolution grid derived from NASA’s Shuttle Radar Topography Mission (SRTM). SRTM provides surface elevations, not bare earth elevations, causing it to commonly overestimate elevations, especially in areas with dense and tall buildings or vegetation. Therefore, the map under-portrays areas that could be submerged at each water level, and exposure is greater than shown (Kulp and Strauss, 2016). However, SRTM includes error in both directions, so some areas showing exposure may not be at risk.SRTM data do not cover latitudes farther north than 60 degrees or farther south than 56 degrees, meaning that sparsely populated parts of Arctic Circle nations are not mapped here, and may show visual artifacts.Areas of this map in Alaska use elevation data on a roughly 60-meter horizontal resolution grid supplied by the U.S. Geological Survey (USGS). This data is referenced to a vertical reference frame from 1929, based on historic sea levels, and with no established conversion to modern reference frames. The data also do not take into account subsequent land uplift and subsidence, widespread in the state. As a consequence, low confidence should be placed in Alaska map portions.Flood control structures (U.S.)Levees, walls, dams or other features may protect some areas, especially at lower elevations. Levees and other flood control structures are included in this map within but not outside of the U.S., due to poor and missing data. Within the U.S., data limitations, such as an incomplete inventory of levees, and a lack of levee height data, still make assessing protection difficult. For this map, levees are assumed high and strong enough for flood protection. However, it is important to note that only 8% of monitored levees in the U.S. are rated in “Acceptable” condition (ASCE). Also note that the map implicitly includes unmapped levees and their heights, if broad enough to be effectively captured directly by the elevation data.For more information on how Surging Seas incorporates levees and elevation data in Louisiana, view our Louisiana levees and DEMs methods PDF. For more information on how Surging Seas incorporates dams in Massachusetts, view the Surging Seas column of the web tools comparison matrix for Massachusetts.ErrorErrors or omissions in elevation or levee data may lead to areas being misclassified. Furthermore, this analysis does not account for future erosion, marsh migration, or construction. As is general best practice, local detail should be verified with a site visit. Sites located in zones below a given water level may or may not be subject to flooding at that level, and sites shown as isolated may or may not be be so. Areas may be connected to water via porous bedrock geology, and also may also be connected via channels, holes, or passages for drainage that the elevation data fails to or cannot pick up. In addition, sea level rise may cause problems even in isolated low zones during rainstorms by inhibiting drainage.ConnectivityAt any water height, there will be isolated, low-lying areas whose elevation falls below the water level, but are protected from coastal flooding by either man-made flood control structures (such as levees), or the natural topography of the surrounding land. In areas using lidar-based elevation data or CoastalDEM (see above), elevation data is accurate enough that non-connected areas can be clearly identified and treated separately in analysis (these areas are colored green on the map). In the U.S., levee data are complete enough to factor levees into determining connectivity as well.However, in other areas, elevation data is much less accurate, and noisy error often produces “speckled” artifacts in the flood maps, commonly in areas that should show complete inundation. Removing non-connected areas in these places could greatly underestimate the potential for flood exposure. For this reason, in these regions, the only areas removed from the map and excluded from analysis are separated from the ocean by a ridge of at least 20 meters (66 feet) above the local high tide line, according to the data, so coastal flooding would almost certainly be impossible (e.g., the Caspian Sea region).Back to topData LayersWater Level | Projections | Legend | Social Vulnerability | Population | Ethnicity | Income | Property | LandmarksWater LevelWater level means feet or meters above the local high tide line (“Mean Higher High Water”) instead of standard elevation. Methods described above explain how each map is generated based on a selected water level. Water can reach different levels in different time frames through combinations of sea level rise, tide and storm surge. Tide gauges shown on the map show related projections (see just below).The highest water levels on this map (10, 20 and 30 meters) provide reference points for possible flood risk from tsunamis, in regions prone to them.

NCED is currently involved in researching the effectiveness of anaglyph maps in the classroom and are working with educators and scientists to interpret various Earth-surface processes. Based on the findings of the research, various activities and interpretive information will be developed and available for educators to use in their classrooms. Keep checking back with this website because activities and maps are always being updated. We believe that anaglyph maps are an important tool in helping students see the world and are working to further develop materials and activities to support educators in their use of the maps.

This website has various 3-D maps and supporting materials that are available for download. Maps can be printed, viewed on computer monitors, or projected on to screens for larger audiences. Keep an eye on our website for more maps, activities and new information. Let us know how you use anaglyph maps in your classroom. Email any ideas or activities you have to ncedmaps@umn.edu

Anaglyph paper maps are a cost effective offshoot of the GeoWall Project. Geowall is a high end visualization tool developed for use in the University of Minnesota's Geology and Geophysics Department. Because of its effectiveness it has been expanded to 300 institutions across the United States. GeoWall projects 3-D images and allows students to see 3-D representations but is limited because of the technology. Paper maps are a cost effective solution that allows anaglyph technology to be used in classroom and field-based applications.

Maps are best when viewed with RED/CYAN anaglyph glasses!

A note on downloading: "viewable" maps are .jpg files; "high-quality downloads" are .tif files. While it is possible to view the latter in a web-browser in most cases, the download may be slow. As an alternative, try right-clicking on the link to the high-quality download and choosing "save" from the pop-up menu that results. Save the file to your own machine, then try opening the saved copy. This may be faster than clicking directly on the link to open it in the browser.

World Map: 3-D map that highlights oceanic bathymetry and plate boundaries.

Continental United States: 3-D grayscale map of the Lower 48.

Western United States: 3-D grayscale map of the Western United States with state boundaries.

Regional Map: 3-D greyscale map stretching from Hudson Bay to the Central Great Plains. This map includes the Western Great Lakes and the Canadian Shield.

Minnesota Map: 3-D greyscale map of Minnesota with county and state boundaries.

Twin Cities: 3-D map extending beyond Minneapolis and St. Paul.

Twin Cities Confluence Map: 3-D map highlighting the confluence of the Mississippi and Minnesota Rivers. This map includes most of Minneapolis and St. Paul.

Minneapolis, MN: 3-D topographical map of South Minneapolis.

Bassets Creek, Minneapolis: 3-D topographical map of the Bassets Creek watershed.

North Minneapolis: 3-D topographical map highlighting North Minneapolis and the Mississippi River.

St. Paul, MN: 3-D topographical map of St. Paul.

Western Suburbs, Twin Cities: 3-D topographical map of St. Louis Park, Hopkins and Minnetonka area.

Minnesota River Valley Suburbs, Twin Cities: 3-D topographical map of Bloomington, Eden Prairie and Edina area.

Southern Suburbs, Twin Cities: 3-D topographical map of Burnsville, Lakeville and Prior Lake area.

Southeast Suburbs, Twin Cities: 3-D topographical map of South St. Paul, Mendota Heights, Apple Valley and Eagan area.

Northeast Suburbs, Twin Cities: 3-D topographical map of White Bear Lake, Maplewood and Roseville area.

Northwest Suburbs, Mississippi River, Twin Cities: 3-D topographical map of North Minneapolis, Brooklyn Center and Maple Grove area.

Blaine, MN: 3-D map of Blaine and the Mississippi River.

White Bear Lake, MN: 3-D topographical map of White Bear Lake and the surrounding area.

Maple Grove, MN: 3-D topographical mmap of the NW suburbs of the Twin Cities.

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