This layer is a component of 2007_NAIP_COVERAGE_3.mxd.
This city boundary shapefile was extracted from Esri Data and Maps for ArcGIS 2014 - U.S. Populated Place Areas. This shapefile can be joined to 500 Cities city-level Data (GIS Friendly Format) in a geographic information system (GIS) to make city-level maps.
This map layer includes cities and towns in the United States, Puerto Rico, and the U.S. 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 a component of Populated Places.
This map layer includes cities and towns in the United States, Puerto Rico, and the U.S. Virgin Islands (NTAD 2015). 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.
© The National Atlas
The "Major Cities" layer is derived from the "World Cities" dataset provided by ArcGIS Data and Maps group as part of the global data layers made available for public use. "Major cities" layer specifically contains National and Provincial capitals that have the highest population within their respective country. Cities were filtered based on the STATUS (“National capital”, “National and provincial capital”, “Provincial capital”, “National capital and provincial capital enclave”, and “Other”). Majority of these cities within larger countries have been filtered at the highest levels of POP_CLASS (“5,000,000 and greater” and “1,000,000 to 4,999,999”). However, China for example, was filtered with cities over 11 million people due to many highly populated cities. Population approximations are sourced from US Census and UN Data. Credits: ESRI, CIA World Factbook, GMI, NIMA, UN Data, UN Habitat, US Census Bureau Disclaimer: The designations employed and the presentation of material at this site do not imply the expression of any opinion whatsoever on the part of the Secretariat of the United Nations concerning the legal status of any country, territory, city or area or of its authorities, or concerning the delimitation of its frontiers or boundaries.
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 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
This world cities layer presents the locations of many cities of the world, both major cities and many provincial capitals.Population estimates are provided for those cities listed in open source data from the United Nations and US Census.
Copy of https://www.arcgis.com/home/item.html?id=85d0ca4ea1ca4b9abf0c51b9bd34de2e This layer presents the locations of cities within the United States with populations of approximately 10,000 or greater, all state capitals, and the national capital.
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
Updates for this dataset, along with other multilayered maps on NYC Open Data, are temporarily paused while they are moved to a new mapping format. Please visit https://www.nyc.gov/site/planning/data-maps/open-data/dwn-digital-city-map.page to utilize this data in the meantime.
U.S. Census Populated Place Areas represents the 2020 U.S. Census populated place areas of the United States that include incorporated places, cities, and census designated places identified by the U.S. Census Bureau.This layer is updated annually. The geography is sourced from U.S. Census Bureau 2020 TIGER FGDB (National Sub-State) and edited using TIGER Hydrography to add a detailed coastline for cartographic purposes. Attribute fields include 2020 total population from the U.S. Census Public Law 94 data. The Population Class field values represent population ranges as follows:Population from 0 - 249Population from 250 - 499Population from 500 - 999Population from 1,000 - 2,499Population from 2,500 - 9,999Population from 10,000 - 49,999Population from 50,000 - 99,999Population from 100,000 - 249,999Population from 250,000 - 499,999Population 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.
These maps show changes in the number of heat waves per year (frequency); the average length of heat waves in days (duration); the number of days between the first and last heat wave of the year (season length); and how hot the heat waves were, compared with the local temperature threshold for defining a heat wave (intensity). These data were analyzed from 1961 to 2023 for 50 large metropolitan areas. The size of each circle indicates the rate of change per decade. Solid-color circles represent cities where the trend was statistically significant. For more information: www.epa.gov/climate-indicators
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:
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:
Point of Contact
California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov
Field and Abbreviation Definitions
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 =
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 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 Updates for this dataset, along with other multilayered maps on NYC Open Data, are temporarily paused while they are moved to a new mapping format. Please visit https://www.nyc.gov/site/planning/data-maps/open-data/dwn-digital-city-map.page to utilize this data in the meantime.
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
Updates for this dataset, along with other multilayered maps on NYC Open Data, are temporarily paused while they are moved to a new mapping format. Please visit https://www.nyc.gov/site/planning/data-maps/open-data/dwn-digital-city-map.page to utilize this data in the meantime.
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 map title is Yarmouth. Tactile map scale. 2 centimetres = 3 kilometres North arrow pointing to the north. Yarmouth and surrounding area. Atlantic Ocean is shown with a wavy symbol to indicate water. Dashed lines indicate ferry crossings to Maine, USA. Main roads, Route 101 and Route 103. A circle with a dot in the middle indicates a bus terminal west of the city. Tactile maps are designed with Braille, large text, and raised features for visually impaired and low vision users. The Tactile Maps of Canada collection includes: (a) Maps for Education: tactile maps showing the general geography of Canada, including the Tactile Atlas of Canada (maps of the provinces and territories showing political boundaries, lakes, rivers and major cities), and the Thematic Tactile Atlas of Canada (maps showing climatic regions, relief, forest types, physiographic regions, rock types, soil types, and vegetation). (b) Maps for Mobility: to help visually impaired persons navigate spaces and routes in major cities by providing information about streets, buildings and other features of a travel route in the downtown area of a city. (c) Maps for Transportation and Tourism: to assist visually impaired persons in planning travel to new destinations in Canada, showing how to get to a city, and streets in the downtown area.
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.
To better map the urban class and understand how urban lands change over time, we removed rural roads and small patches of rural development from the NLCD developed class and created four wall-to-wall maps (1992, 2001, 2006, and 2011) of urban land. Removing rural roads from the NLCD developed class involved a multi-step filtering process, data fusion using geospatial road and developed land data, and manual editing. Reference data classified as urban or not urban from a stratified random sample was used to assess the accuracy of the 2001 and 2006 urban and NLCD maps. The newly created urban maps had higher overall accuracy (98.7%) than the NLCD maps (96.2%). More importantly, the urban maps resulted in lower commission error of the urban class (23% versus 57% for the NLCD in 2006) with the trade-off of slightly inflated omission error (20% for the urban map, 16% for NLCD in 2006). The removal of approximately 230,000 km2 of rural roads from the NLCD developed class resulted in maps that better characterize the urban footprint. These urban maps are more suited to modeling applications and policy decisions that rely on quantitative and spatially explicit information regarding urban lands. Digital maps of urban land in the United States for 1992, 2001, 2006, and 2011 are available (at a 30-m pixel resolution) as four compressed 2-bit IMG files. The map year is reflected in the file name.
This layer is a component of 2007_NAIP_COVERAGE_3.mxd.