Notice: this is not the latest Heat Island Anomalies image service.This layer contains the relative degrees Fahrenheit difference between any given pixel and the mean heat value for the city in which it is located, for every city in the contiguous United States, 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, with patching from summer of 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 or cooler than the average temperature for that same city as a whole. 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.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.

This dataset contains 50-ft contours for the Hot Springs shallowest unit of the Ouachita Mountains aquifer system potentiometric-surface map. The potentiometric-surface shows altitude at which the water level would have risen in tightly-cased wells and represents synoptic conditions during the summer of 2017. Contours were constructed from 59 water-level measurements measured in selected wells (locations in the well point dataset). Major streams and creeks were selected in the study area from the USGS National Hydrography Dataset (U.S. Geological Survey, 2017), and the spring point dataset with 18 spring altitudes calculated from 10-meter digital elevation model (DEM) data (U.S. Geological Survey, 2015; U.S. Geological Survey, 2016). After collecting, processing, and plotting the data, a potentiometric surface was generated using the interpolation method Topo to Raster in ArcMap 10.5 (Esri, 2017a). This tool is specifically designed for the creation of digital elevation models and imposes constraints that ensure a connected drainage structure and a correct representation of the surface from the provided contour data (Esri, 2017a). Once the raster surface was created, 50-ft contour interval were generated using Contour (Spatial Analyst), a spatial analyst tool (available through ArcGIS 3D Analyst toolbox) that creates a line-feature class of contours (isolines) from the raster surface (Esri, 2017b). The Topo to Raster and contouring done by ArcMap 10.5 is a rapid way to interpolate data, but computer programs do not account for hydrologic connections between groundwater and surface water. For this reason, some contours were manually adjusted based on topographical influence, a comparison with the potentiometric surface of Kresse and Hays (2009), and data-point water-level altitudes to more accurately represent the potentiometric surface. Select References: Esri, 2017a, How Topo to Raster works—Help | ArcGIS Desktop, accessed December 5, 2017, at ArcGIS Pro at http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/how-topo-to-raster-works.htm. Esri, 2017b, Contour—Help | ArcGIS Desktop, accessed December 5, 2017, at ArcGIS Pro Raster Surface toolset at http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/contour.htm. Kresse, T.M., and Hays, P.D., 2009, Geochemistry, Comparative Analysis, and Physical and Chemical Characteristics of the Thermal Waters East of Hot Springs National Park, Arkansas, 2006-09: U.S. Geological Survey 2009–5263, 48 p., accessed November 28, 2017, at https://pubs.usgs.gov/sir/2009/5263/. U.S. Geological Survey, 2015, USGS NED 1 arc-second n35w094 1 x 1 degree ArcGrid 2015, accessed December 5, 2017, at The National Map: Elevation at https://nationalmap.gov/elevation.html. U.S. Geological Survey, 2016, USGS NED 1 arc-second n35w093 1 x 1 degree ArcGrid 2016, accessed December 5, 2017, at The National Map: Elevation at https://nationalmap.gov/elevation.html.

Download In State Plane Projection Here The 2024 Parcel Fabric Data is a copy of the Lake County Chief Assessor's Office spatial dataset, consisting of separate layers which represent the boundaries for Tax Parcels, Lots, Units, Subs, Condos, Rights of Way, and Encumbrance parcels, along with points, lines, and PLSS townships for reference, which have all been captured for the 2024 Tax Year.This data is spatial in nature and does not include extensive fields of attributes to which each layer may be associated. This data is provided for use to individuals or entities with an understanding of Esri's ArcGIS Pro (specifically the Parcel Fabric), and those with access to ArcGIS Pro, which is necessary to view or manipulate the data.Casual users can find the standalone Tax Parcel Boundary Data here and Parcel Attribute Data here. Update Frequency: This dataset is updated on a yearly basis.

AbstractA continuous contour dataset at 100 m intervals for all land south of 60°S, excluding the Balleny Islands. The vertical datum of the contours is EGM2008. Contours are extracted primarily from the PGC Reference Elevation Model of Antarctica (REMA) v1.1 with certain islands filled from Copernicus WorldDEM. Further small areas are interpreted from satellite imagery, and Peter I Øy contours are from the Norwegian Polar Institute. Sources of individual line segments are contained in the attribute table and full compilation information is given in the lineage statement.Note: contours overlap the coastline in small areas, due to resolution of the data used in creation of the lines, and potential errors in coastline and/or contour data. Certain areas are known to contain erroneous data due to faults in the original DEM data.Data compiled, managed and distributed by the Mapping and Geographic Information Centre and the UK Polar Data Centre, British Antarctic Survey on behalf of the Scientific Committee on Antarctic Research.Further information and useful linksMap projection: WGS84 Antarctic Polar Stereographic, EPSG 3031. Note: by default, opening this layer in the Map Viewer will display the data in Web Mercator. To display this layer in its native projection use an Antarctic basemap.The currency of this dataset is November 2022 and will be reviewed every 6 months. This feature layer will always reflect the most recent version.For more information on, and access to other Antarctic Digital Database (ADD) datasets, refer to the SCAR ADD data catalogue.A related medium resolution dataset at 500 m intervals is also published via Living Atlas.For background information on the ADD project, please see the British Antarctic Survey ADD project page.LineageAll processing described here was performed in ArcGIS Pro version 2.6.A composite Digital Elevation Model (DEM) was created comprising of three datasets from the Reference Elevation Model of Antarctica v1.1: ‘REMA_100m_peninsula_dem_filled’, ‘REMA_100m_dem’ and ‘REMA_200m_dem_filled’. These DEMs were first converted from ellipsoidal height to height above EGM2008 geoid and then mosaicked together in respective order at 100 m spatial resolution. This 100 m DEM was smoothed by performing ‘Focal Statistics’ using a 3x3 cell size.100 m contours were extracted and all contours with a height <1m were deleted, as well as erroneous offshore contours. All contour ‘dangles’ were identified and then fixed to create a continuous dataset. They were fixed either by interpreting the correct line from satellite imagery or from ‘Copernicus WorldDEM 90m’ contours. Such lines are attributed with ‘interpreted’ in the source field and should be treated with caution. In other locations where the contours significantly overlapped the coastline, contours were redrawn/interpreted to not go offshore. In certain locations, primarily some islands on the Antarctic Peninsula, REMA data was insufficient to produce contours. In these places, contours were produced from the ‘Copernicus WorldDEM 90m’ DEM and smoothed by 300 m using a PAEK smoothing algorithm. Contours for Peter I Øy were incorporated from the Norwegian Polar Institute Data at 100 m intervals. The source of every line is written in the attribute table.All contours were merged together and lines <150 m in length were deleted. Further lines <1500 m were deleted in ‘non-mountainous’ regions, so as to avoid deleting small mountain peak contours but to still simplify the main dataset. These regions were interpreted manually using the hillshade of the DEM used to produce the contours.Original DEM sources and citations:REMA: Howat, I. M., Porter, C., Smith, B. E., Noh, M.-J., and Morin, P.: The Reference Elevation Model of Antarctica, The Cryosphere, 13, 665-674, https://doi.org/10.5194/tc-13-665-2019, 2019.Copernicus WorldDEM: produced using Copernicus WorldDEM™-90 © DLR e.V. 2010-2014 and © Airbus Defence and Space GmbH 2014-2018 provided under COPERNICUS by the European Union and ESA; all rights reserved.Norwegian Polar Institute (2014). Map data / kartdata Peter I Øy 1:50 000 (P50 Kartdata). Norwegian Polar Institute. https://doi.org/10.21334/npolar.2014.29105abcCitationPlease cite this item as: 'Gerrish, L., Fretwell, P., & Cooper, P. (2020). High resolution vector contours for Antarctica (7.3) [Data set]. UK Polar Data Centre, Natural Environment Research Council, UK Research & Innovation. https://doi.org/10.5285/4bd20a2b-df7d-46a2-acdf-5104c82ff4c7'If using for a graphic or if short on space, please cite as 'data from the SCAR Antarctic Digital Database, accessed [year]'

This ArcGIS Online hosted feature service displays perimeters from the National Incident Feature Service (NIFS) that meet ALL of the following criteria:

Pursuant to Section 7-100l of the Connecticut General Statutes, each municipality is required to transmit a digital parcel file and an accompanying assessor’s database file (known as a CAMA report), to its respective regional council of governments (COG) by May 1 annually. The dataset has combined the Parcels and Computer-Assisted Mass Appraisal (CAMA) data for 2025 into a single dataset. This dataset is designed to make it easier for stakeholders and the GIS community to use and access the information as a geospatial dataset. Included in this dataset are geometries for all 169 municipalities and attribution from the CAMA data for all but one municipality. These data were gathered from the CT municipalities by the COGs and then submitted to CT OPM. This dataset was created on September 2025 from data collected in 2024-2025. Data was processed using Python scripts and ArcGIS Pro for standardization and integration of the data. To learn more about Parcel and CAMA in CT visit our Parcels Page in the Geodata Portal.

Coordinate system:

This dataset is provided in NAD 83 Connecticut State Plane (2011) (EPSG 2234) projection as it was for 2024. Prior versions were provided at WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857).

Ownership Suppression:

The updated dataset includes parcel data for all towns across the state, with some towns featuring fully suppressed ownership information. In these instances, the owner’s name was replaced with the label "Current Owner," the co-owner’s name will be listed as "Current Co-Owner," and the mailing address will appear as the property address itself. For towns with fully suppressed ownership data, please note that no "Suppression" field was included in the submission to confirm these details and this labeling approach was implemented as the solution.

New Data Fields:

The new dataset introduces the “Property Zip” and “Mailing Zip” fields, which will display the zip codes for the owner and property.

Service URL:

In 2024, we implemented a stable URL to maintain public access to the most up-to-date data layer. Users are strongly encouraged to transition to the new service as soon as possible to ensure uninterrupted workflows. This URL will remain persistent, providing long-term stability for your applications and integrations. Once you’ve transitioned to the new service, no further URL changes will be necessary.

CAMA Notes:

The CAMA underwent several steps to standardize and consolidate the information. Python scripts were used to concatenate fields and create a unique identifier for each entry. The resulting dataset contains 1,354,720 entries and information on property assessments and other relevant attributes.

• CAMA was provided by the towns.

Spatial Data Notes:

Data processing involved merging the parcels from different municipalities using ArcGIS Pro and Python. The resulting dataset contains 1,282,833 parcels.

• No alteration has been made to the spatial geometry of the data.

• Fields that are associated with CAMA data were provided by towns.

• The data fields that have information from the CAMA were sourced from the towns’ CAMA data.

• If no field for the parcels was provided for linking back to the CAMA by the town a new field within the original data was selected if it had a match rate above 50%, that joined back to the CAMA.

• Linking fields were renamed to "Link".

• All linking fields had a census town code added to the beginning of the value to create a unique identifier per town.

• Any field that was not town name, Location, Editor, Edit Date, or a field associated back to the CAMA, was not used in the creation of this Dataset.

• Only the fields related to town name, location, editor, edit date, and link fields associated with the towns’ CAMA were included in the creation of this dataset. Any other field provided in the original data was deleted or not used.

• Field names for town (Muni, Municipality) were renamed to "Town Name".

Attributes included in the data:

• Town Name

• Owner

• Co-Owner

• Link

• Editor

• Edit Date

• Collection year – year the parcels were submitted

• Location

• Property Zip

• Mailing Address

• Mailing City

• Mailing State

• Mailing Zip

• Assessed Total

• Assessed Land

• Assessed Building

• Pre-Year Assessed Total

• Appraised Land

• Appraised Building

• Appraised Outbuilding

• Condition

• Model

• <p style='margin-bottom:1.5rem;

GIS data digitised from 2 DigitalGlobe images at a scale of 1:1000.
The features were digitised using ArcGIS Pro and were created within a topology to ensure the spatial integrity of the data. Line data include coastlines, ice fronts and grounding lines. Polygon data include continent, island, ice tongue and rock features.

The images and data are of the Bølingen Islands and surrounding area, in the Prydz Bay region of Antarctica.
(18FEB23042505-P2AS-017311657010_01_P001.TIL; 18FEB23042504-M2AS-017311657010_01_P001.TIL)
(24MAR16035205-P2AS-017311660010_01_P001.TIL; 24MAR16035205-M2AS-017311660010_01_P001.TIL)
Copyright 2024 DigitalGlobe Incorporated, Longmont CO USA 80503-6493

-- DEMO Version v0.5--***Updated to include Errors Identified in the Split line feature class tool***Introducing the Address Management Solution - an ArcGIS Pro Desktop Application Template designed to revolutionize your address data management process!With this ArcGIS Pro Project template, you can efficiently create and manage address points and road centerlines, ensuring data accuracy and completeness. Powered by custom attribute rules, data creation becomes a breeze, automatically populating mandatory fields for seamless data integration.Key Features:Address Points: Easily create new address points with attribute rules that automate the generation of related attributes for comprehensive data.Road Centerlines: Benefit from attribute rules that streamline data editing, simplifying the process of splitting and recalculating address ranges for accurate data maintenance.NG911 Ready: Align your data with the NENA GIS Data Model and National standards, ensuring compatibility and efficient integration with Next Generation 9-1-1 services.User-Friendly: The template comes with targeted training modules, guiding users through introductory, advanced, and master levels to master ArcGIS Pro's powerful address management capabilities.Statewide Dataset: Leverage our comprehensive state-wide datasets, custom domains, and dynamic labels, tailored to cater to Arizona's geographic requirements.Empower your team with the tools and knowledge needed to succeed in creating a more resilient, efficient, and reliable address management system. Download the Desktop Application Template and review the Training Materials to get started!

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.

The High Resolution Digital Elevation Model (HRDEM) product is derived from airborne LiDAR data (mainly in the south) and satellite images in the north. The complete coverage of the Canadian territory is gradually being established. It includes a Digital Terrain Model (DTM), a Digital Surface Model (DSM) and other derived data. For DTM datasets, derived data available are slope, aspect, shaded relief, color relief and color shaded relief maps and for DSM datasets, derived data available are shaded relief, color relief and color shaded relief maps. The productive forest line is used to separate the northern and the southern parts of the country. This line is approximate and may change based on requirements. In the southern part of the country (south of the productive forest line), DTM and DSM datasets are generated from airborne LiDAR data. They are offered at a 1 m or 2 m resolution and projected to the UTM NAD83 (CSRS) coordinate system and the corresponding zones. The datasets at a 1 m resolution cover an area of 10 km x 10 km while datasets at a 2 m resolution cover an area of 20 km by 20 km. In the northern part of the country (north of the productive forest line), due to the low density of vegetation and infrastructure, only DSM datasets are generally generated. Most of these datasets have optical digital images as their source data. They are generated at a 2 m resolution using the Polar Stereographic North coordinate system referenced to WGS84 horizontal datum or UTM NAD83 (CSRS) coordinate system. Each dataset covers an area of 50 km by 50 km. For some locations in the north, DSM and DTM datasets can also be generated from airborne LiDAR data. In this case, these products will be generated with the same specifications as those generated from airborne LiDAR in the southern part of the country. The HRDEM product is referenced to the Canadian Geodetic Vertical Datum of 2013 (CGVD2013), which is now the reference standard for heights across Canada. Source data for HRDEM datasets is acquired through multiple projects with different partners. Since data is being acquired by project, there is no integration or edgematching done between projects. The tiles are aligned within each project. The product High Resolution Digital Elevation Model (HRDEM) is part of the CanElevation Series created in support to the National Elevation Data Strategy implemented by NRCan. Collaboration is a key factor to the success of the National Elevation Data Strategy. Refer to the “Supporting Document” section to access the list of the different partners including links to their respective data.

This layer presents the U.S. Census County (or County Equivalent) boundaries of the United States in the 50 states and the District of Columbia, sourced from 2023 Census TIGER/Line data and includes the estimated annual population total of each County. This layer is updated annually. The geography is sourced from U.S. Census Bureau 2023 TIGER FGDB (National Sub-State) and edited using TIGER Hydrography to add a detailed coastline for cartographic purposes. Attribute fields include 2023 estimated total population from the Esri demographics team. This 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 map package includes the official Tribal areas that NTIA recognizes for their grant programs. The map package includes the following layers. Alaska Native Villages - this layer represents Alaska Native Villages and is created by Census. The layer was downloaded on Jan. 28, 2025, from here: TIGER/Line® Shapefiles.Native Hawaiian Areas - this layer represents Native Hawaiian Areas and is created by Census. The layer was downloaded on Jan. 28, 2025, from here: TIGER/Line® Shapefiles and has been filtered to only include Native Hawaiian Areas. BIA AIAN National LAR - this layer represents American Indian Lands and is created by the BIA. The layer was accessed here: BIA Access Open Data and was exported on Jan. 28, 2025. The layer was filtered to only include lands across the continental U.S. BIA AIAN LAR Supplemental - this layer is a supplemental dataset to the LAR. The layer was accessed here: BIA Access Open Data and was exported on Jan. 28, 2025.BIA AIAN Tribal Statistical Areas - this layer represents Tribal Statistical Areas located in Oklahoma. The layer was accessed here: BIA Access Open Data and was exported on Jan. 28, 2025.This map package was created on Jan. 28, 2025 and was created using ArcGIS Pro 3.4.0. If you have any questions regarding the map package please e-mail NTIAanalytics@ntia.gov.ResourcesCensus DataBIA Open DataBIA Data DisclaimerBy using this product, the user agrees to the below terms and conditions:No warranty is made by the Bureau of Indian Affairs (BIA) for the use of the data for purposes not intended by the BIA. This GIS Dataset may contain errors. There is no impact on the legal status of the land areas depicted herein and no impact on land ownership. No legal inference can or should be made from the information in this GIS Dataset. The GIS Dataset is prepared strictly for illustrative and reference purposes only and should not be used, and is not intended for legal, survey, engineering or navigation purposes. These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from source documents and/or the translation of information from source documents to the systems of record continue to exist. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.Census Use RestraintsThe TIGER/Line Shapefile products are not copyrighted however TIGER/Line and Census TIGER are registered trademarks of the U.S. Census Bureau. These products are free to use in a product or publication, however acknowledgement must be given to the U.S. Census Bureau as the source. The boundary information in the TIGER/Line Shapefiles are for statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement and they are not legal land descriptions. Coordinates in the TIGER/Line shapefiles have six implied decimal places, but the positional accuracy of these coordinates is not as great as the six decimal places suggest.

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 2019 and 2020.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): 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 Pete.Aniello@tpl.org with feedback.Terms of UseYou understand and agree, and will advise any third party to whom you give any or all of the data, that The Trust for Public Land is neither responsible nor liable for any viruses or other contamination of your system arising from use of The Trust for Public Land’s data nor for any delays, inaccuracies, errors or omissions arising out of the use of the data. The Trust for Public Land’s data is distributed and transmitted "as is" without warranties of any kind, either express or implied, including without limitation, warranties of title or implied warranties of merchantability or fitness for a particular purpose. The Trust for Public Land is not responsible for any claim of loss of profit or any special, direct, indirect, incidental, consequential, and/or punitive damages that may arise from the use of the data. If you or any person to whom you make the data available are downloading or using the data for any visual output, attribution for same will be given in the following format: "This [document, map, diagram, report, etc.] was produced using data, in whole or in part, provided by The Trust for Public Land."

The 2023 Parcel Fabric Data is a copy of the Lake County Chief Assessor's Office spatial dataset, consisting of separate layers which represent the boundaries for Tax Parcels, Lots, Units, Subs, Condos, Rights of Way, and Encumbrance parcels, along with points, lines, and PLSS townships for reference, which have all been captured for the 2023 Tax Year.This data is spatial in nature and does not include extensive fields of attributes to which each layer may be associated. This data is provided for use to individuals or entities with an understanding of Esri's ArcGIS Pro (specifically the Parcel Fabric), and those with access to ArcGIS Pro, which is necessary to view or manipulate the data.Casual users can find the standalone Tax Parcel Boundary Data here and Parcel Attribute Data here. Update Frequency: This dataset is updated on a yearly basis.

This dataset consists of topographic features across the East Antarctic coastal region, extending from 33°E to 168°E and from the coast inland to approximately 84°S in some areas.

The features were digitised using ArcGIS Pro and were created within a topology to ensure the spatial integrity of the data. Line data include coastlines, ice fronts and grounding lines. Polygon data include continent features, islands, ice shelfs, ice tongues, icebergs, rocks and lakes.

The features were digitised at a scale of 1:25,000 using Sentinel2 imagery: earthexplorer.usgs.gov, 'Copernicus Sentinel data [2023]'. Note: Individual Sentinel 2 data source images are referenced in the data attribute tables with the exception of the coastline polygon dataset which was derived from the coastline line dataset.

Grounding lines were derived from ASAID_Grounding_line_continent_Sc_dep : Rignot, E., J. Mouginot, and B. Scheuchl. 2016. MEaSUREs Antarctic Grounding Line from Differential Satellite Radar Interferometry, Version 2. Boulder, Colorado USA. NASA National Snow and Ice Data Center Distributed Active Archive Center. https://nsidc.org/data/nsidc-0498/versions/2

The ASAID data were edited using ICESat2 data: Derived Grounding Zone for Antarctic Ice Shelves, United States Antarctic Program Data Center (USAP-DC) www.usap-dc.org ; http://www.usap-dc.org/view/dataset/609469 as well as Sentinel2 imagery and The Reference Elevation Model of Antarctica version 2 (REMA 2): Howat, I. M., Porter, C., Smith, B. E., Noh, M.-J., and Morin, P., The Reference Elevation Model of Antarctica, The Cryosphere, 13, 665-674, https://doi.org/10.5194/tc-13-665-2019 , 2019 DEM(s) courtesy of the Polar Geospatial Center.

The Antarctic Iceberg Data were sourced from U.S.National Ice Centre (usicecenter.gov/Products/AntarcIcebergs) in CSV format. The CSV data used in this project is dated 3 Feb 2023. The point data were used to locate and digitise icebergs using Sentinel 2 imagery at a scale of 1:25000.

The 25K topographic features are stored in the Australian Antarctic Division Enterprise GIS and are available for download using the provided links.

This data release includes digital geographic information system (GIS) data which was extracted from the U.S. Geological Survey Professional Paper 1300, volumes 1 and 2. Included are 14 shapefiles comprised of points, lines, and polygons representing the items shown in the page size figures from the reports, and one .lyrx symbology file for use in ArcGIS Pro. Also included are 364 georeferenced images of the report figures, 332 of which are figures for individual study areas, from which the shapefiles were digitized, and 32 of which are state index maps. The georeferenced images are named with the figure number or state name, and page number from the source report. Features represented in the shapefiles include figure map extents, study areas, assessment potential areas, deposits, occurrences, mines, drill holes, wells, springs, volcanic features, sample sites, geology, and geologic structures that were shown in the report figures. The .lyrx file is included to assist in the symbolizing of the geologic structures line shapefile. The data digitized from the georeferenced figures were assumed correct, and very little accuracy checking was completed.

This layer shows Asian alone or in any combination by selected groups. This is shown by tract, county, and state boundaries. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. The numbers by detailed Asian groups do not add to the total population. This is because the detailed Asian groups are tallies of the number of Asian responses rather than the number of Asian respondents. Responses that include more than one race and/or Asian group are counted several times. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023ACS Table(s): B02001, B02011, B02018 (Not all lines of ACS table B02001 are available in this layer.)Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters).The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.