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

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

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.

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.

The Digital Geologic-GIS Map of City of Rocks National Reserve and Vicinity, Idaho is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (ciro_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (ciro_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (ciro_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (ciro_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (ciro_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (ciro_geology_metadata_faq.pdf). Please read the ciro_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (ciro_geology_metadata.txt or ciro_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

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

The Digital Geologic-GIS Map of portions of the Cooke City Quadrangle, Wyoming and Montana is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (coci_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (coci_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (coci_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (yell_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (yell_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (coci_geology_metadata_faq.pdf). Please read the yell_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (coci_geology_metadata.txt or coci_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information

Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information

Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information

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.

USGS Structures from The National Map (TNM) consists of data to include the name, function, location, and other core information and characteristics of selected manmade facilities across all US states and territories. The types of structures collected are largely determined by the needs of disaster planning and emergency response, and homeland security organizations. Structures currently included are: School, School:Elementary, School:Middle, School:High, College/University, Technical/Trade School, Ambulance Service, Fire Station/EMS Station, Law Enforcement, Prison/Correctional Facility, Post Office, Hospital/Medical Center, Cabin, Campground, Cemetery, Historic Site/Point of Interest, Picnic Area, Trailhead, Vistor/Information Center, US Capitol, State Capitol, US Supreme Court, State Supreme Court, Court House, Headquarters, Ranger Station, White House, and City/Town Hall. Structures data are designed to be used in general mapping and in the analysis of structure related activities using geographic information system technology. Included is a feature class of preliminary building polygons provided by FEMA, USA Structures. The National Map structures data is commonly combined with other data themes, such as boundaries, elevation, hydrography, and transportation, to produce general reference base maps. The National Map viewer allows free downloads of public domain structures data in either Esri File Geodatabase or Shapefile formats. For additional information on the structures data model, go to https://www.usgs.gov/ngp-standards-and-specifications/national-map-structures-content.

The Lands pdf represent the location and project number of NMDOT Construction projects.

Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information

Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information

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.

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.

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, including Alaska, Hawaii, and Puerto Rico. This 30-meter raster was derived from Landsat 8 imagery band 10 (ground-level thermal sensor) from the summer of 2022, patched with data from 2021 where necessary.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.In order to click on the image service and see the raw pixel values in a map viewer, you must be signed in to ArcGIS Online, then Enable Pop-Ups and Configure Pop-Ups.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): A typical operation at this point is to clip out your area of interest. To do this, add your polygon shapefile or feature class to the map view, and use the Clip Raster tool to export your area of interest as a geoTIFF raster (file extension ".tif"). In the environments tab for the Clip Raster tool, click the dropdown for "Extent" and select "Same as Layer:", and select the name of your polygon. If you then need to convert the output raster to a polygon shapefile or feature class, run the Raster to Polygon tool, and select "Value" as the field.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 ArizonaDr. Ben McMahan, University of Arizona Dr. Jeremy Hoffman, Science Museum of Virginia Dr. Hunter Jones, NOAA Daphne 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.

Geologic mapping, in support of the USGS Omaha-Kansas City Geologic Mapping Project, shows the spatial distribution of artificial-fill, alluvial, eolian, and glacial deposits and bedrock in and near Omaha, Nebraska. Artificial fill deposits are mapped chiefly beneath commercial structures, segments of interstate highways and other major highways, railroad tracks, airport runways, and military facilities, and in landfills and earth fills. Alluvial deposits are mapped beneath flood plains, in stream terraces, and on hill slopes. They include flood-plain and stream-channel alluvium, sheetwash alluvium, and undivided sheetwash alluvium and stream alluvium. Wind-deposited loess forms sheets that mantle inter-stream areas and late Wisconsin terrace alluvium. Peoria Loess is younger of the two loess sheets and covers much of the inter-stream area in the map area. Loveland Loess is older and is exposed in a few small areas in the eastern part of the map area. Glacial deposits are chiefly heterogeneous, ice-deposited, clayey material (till) and minor interstratified stream-deposited sand and gravel. Except for small outcrops, glacial deposits are covered by eolian and alluvial deposits throughout most of the map area. Bedrock is locally exposed in natural exposures along the major streams and in quarries. It consists of Dakota Sandstone and chiefly limestone and shale of the Lansing and Kansas City Groups. Sand and gravel in flood plain and stream-channel alluvium in the Platte River valley are used mainly for concrete aggregate. Limestone of the Lansing and Kansas City Groups is used for road-surfacing material, rip rap, and fill material.