This dataset contains both large (A0) printable maps of the Torres Strait broken into six overlapping regions, based on a clear sky, clear water composite Sentinel 2 composite imagery and the imagery used to create these maps. These maps show satellite imagery of the region, overlaid with reef and island boundaries and names. Not all features are named, just the more prominent features. This also includes a vector map of Ashmore Reef and Boot Reef in Coral Sea as these were used in the same discussions that these maps were developed for. The map of Ashmore Reef includes the atoll platform, reef boundaries and depth polygons for 5 m and 10 m.

This dataset contains all working files used in the development of these maps. This includes all a copy of all the source datasets and all derived satellite image tiles and QGIS files used to create the maps. This includes cloud free Sentinel 2 composite imagery of the Torres Strait region with alpha blended edges to allow the creation of a smooth high resolution basemap of the region.

The base imagery is similar to the older base imagery dataset: Torres Strait clear sky, clear water Landsat 5 satellite composite (NERP TE 13.1 eAtlas, AIMS, source: NASA).

Most of the imagery in the composite imagery from 2017 - 2021.

Method: The Sentinel 2 basemap was produced by processing imagery from the World_AIMS_Marine-satellite-imagery dataset (not yet published) for the Torres Strait region. The TrueColour imagery for the scenes covering the mapped area were downloaded. Both the reference 1 imagery (R1) and reference 2 imagery (R2) was copied for processing. R1 imagery contains the lowest noise, most cloud free imagery, while R2 contains the next best set of imagery. Both R1 and R2 are typically composite images from multiple dates.

The R2 images were selectively blended using manually created masks with the R1 images. This was done to get the best combination of both images and typically resulted in a reduction in some of the cloud artefacts in the R1 images. The mask creation and previewing of the blending was performed in Photoshop. The created masks were saved in 01-data/R2-R1-masks. To help with the blending of neighbouring images a feathered alpha channel was added to the imagery. The processing of the merging (using the masks) and the creation of the feathered borders on the images was performed using a Python script (src/local/03-merge-R2-R1-images.py) using the Pillow library and GDAL. The neighbouring image blending mask was created by applying a blurring of the original hard image mask. This allowed neighbouring image tiles to merge together.

The imagery and reference datasets (reef boundaries, EEZ) were loaded into QGIS for the creation of the printable maps.

To optimise the matching of the resulting map slight brightness adjustments were applied to each scene tile to match its neighbours. This was done in the setup of each image in QGIS. This adjustment was imperfect as each tile was made from a different combinations of days (to remove clouds) resulting in each scene having a different tonal gradients across the scene then its neighbours. Additionally Sentinel 2 has slight stripes (at 13 degrees off the vertical) due to the swath of each sensor having a slight sensitivity difference. This effect was uncorrected in this imagery.

Single merged composite GeoTiff: The image tiles with alpha blended edges work well in QGIS, but not in ArcGIS Pro. To allow this imagery to be used across tools that don't support the alpha blending we merged and flattened the tiles into a single large GeoTiff with no alpha channel. This was done by rendering the map created in QGIS into a single large image. This was done in multiple steps to make the process manageable.

The rendered map was cut into twenty 1 x 1 degree georeferenced PNG images using the Atlas feature of QGIS. This process baked in the alpha blending across neighbouring Sentinel 2 scenes. The PNG images were then merged back into a large GeoTiff image using GDAL (via QGIS), removing the alpha channel. The brightness of the image was adjusted so that the darkest pixels in the image were 1, saving the value 0 for nodata masking and the boundary was clipped, using a polygon boundary, to trim off the outer feathering. The image was then optimised for performance by using internal tiling and adding overviews. A full breakdown of these steps is provided in the README.md in the 'Browse and download all data files' link.

The merged final image is available in export\TS_AIMS_Torres Strait-Sentinel-2_Composite.tif.

Change Log: 2023-03-02: Eric Lawrey Created a merged version of the satellite imagery, with no alpha blending so that it can be used in ArcGIS Pro. It is now a single large GeoTiff image. The Google Earth Engine source code for the World_AIMS_Marine-satellite-imagery was included to improve the reproducibility and provenance of the dataset, along with a calculation of the distribution of image dates that went into the final composite image. A WMS service for the imagery was also setup and linked to from the metadata. A cross reference to the older Torres Strait clear sky clear water Landsat composite imagery was also added to the record.

22 Nov 2023: Eric Lawrey Added the data and maps for close up of Mer. - 01-data/TS_DNRM_Mer-aerial-imagery/ - preview/Torres-Strait-Mer-Map-Landscape-A0.jpeg - exports/Torres-Strait-Mer-Map-Landscape-A0.pdf Updated 02-Torres-Strait-regional-maps.qgz to include the layout for the new map.

Source datasets: Complete Great Barrier Reef (GBR) Island and Reef Feature boundaries including Torres Strait Version 1b (NESP TWQ 3.13, AIMS, TSRA, GBRMPA), https://eatlas.org.au/data/uuid/d2396b2c-68d4-4f4b-aab0-52f7bc4a81f5

Geoscience Australia (2014b), Seas and Submerged Lands Act 1973 - Australian Maritime Boundaries 2014a - Geodatabase [Dataset]. Canberra, Australia: Author. https://creativecommons.org/licenses/by/4.0/ [license]. Sourced on 12 July 2017, https://dx.doi.org/10.4225/25/5539DFE87D895

Basemap/AU_GA_AMB_2014a/Exclusive_Economic_Zone_AMB2014a_Limit.shp The original data was obtained from GA (Geoscience Australia, 2014a). The Geodatabase was loaded in ArcMap. The Exclusive_Economic_Zone_AMB2014a_Limit layer was loaded and exported as a shapefile. Since this file was small no clipping was applied to the data.

Geoscience Australia (2014a), Treaties - Australian Maritime Boundaries (AMB) 2014a [Dataset]. Canberra, Australia: Author. https://creativecommons.org/licenses/by/4.0/ [license]. Sourced on 12 July 2017, http://dx.doi.org/10.4225/25/5539E01878302 Basemap/AU_GA_Treaties-AMB_2014a/Papua_New_Guinea_TSPZ_AMB2014a_Limit.shp The original data was obtained from GA (Geoscience Australia, 2014b). The Geodatabase was loaded in ArcMap. The Papua_New_Guinea_TSPZ_AMB2014a_Limit layer was loaded and exported as a shapefile. Since this file was small no clipping was applied to the data.

AIMS Coral Sea Features (2022) - DRAFT This is a draft version of this dataset. The region for Ashmore and Boot reef was checked. The attributes in these datasets haven't been cleaned up. Note these files should not be considered finalised and are only suitable for maps around Ashmore Reef. Please source an updated version of this dataset for any other purpose. CS_AIMS_Coral-Sea-Features/CS_Names/Names.shp CS_AIMS_Coral-Sea-Features/CS_Platform_adj/CS_Platform.shp CS_AIMS_Coral-Sea-Features/CS_Reef_Boundaries_adj/CS_Reef_Boundaries.shp CS_AIMS_Coral-Sea-Features/CS_Depth/CS_AIMS_Coral-Sea-Features_Img_S2_R1_Depth5m_Coral-Sea.shp CS_AIMS_Coral-Sea-Features/CS_Depth/CS_AIMS_Coral-Sea-Features_Img_S2_R1_Depth10m_Coral-Sea.shp

Murray Island 20 Sept 2011 15cm SISP aerial imagery, Queensland Spatial Imagery Services Program, Department of Resources, Queensland This is the high resolution imagery used to create the map of Mer.

Marine satellite imagery (Sentinel 2 and Landsat 8) (AIMS), https://eatlas.org.au/data/uuid/5d67aa4d-a983-45d0-8cc1-187596fa9c0c - World_AIMS_Marine-satellite-imagery

Data Location: This dataset is filed in the eAtlas enduring data repository at: data\custodian\2020-2029-AIMS\TS_AIMS_Torres-Strait-Sentinel-2-regional-maps. On the eAtlas server it is stored at eAtlas GeoServer\data\2020-2029-AIMS.

World Countries Generalized represents generalized boundaries for the countries of the world as of August 2022. The generalized political boundaries improve draw performance and effectiveness at a global or continental level. This layer is best viewed out beyond a scale of 1:5,000,000.This layer's geography was developed by Esri and sourced from Garmin International, Inc., the U.S. Central Intelligence Agency (The World Factbook), and the National Geographic Society for use as a world basemap. It is updated annually as country names or significant borders change.

The Mid-Century Map (World Edition) web map provides a customized world basemap symbolized with a unique "Mid-Century" style. It takes its inspiration from the art and advertising of the 1950's with unique fonts. The symbols for cities and capitals have an atomic slant to them. The map data includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, and administrative boundaries.This basemap, included in the ArcGIS Living Atlas of the World, uses the Mid-Century vector tile layer.The vector tile layer in this web map is built using the same data sources used for other Esri Vector Basemaps. For details on data sources contributed by the GIS community, view the map of Community Maps Basemap Contributors. Esri Vector Basemaps are updated monthly.Use this MapThis map is designed to be used as a basemap for overlaying other layers of information or as a stand-alone reference map. You can add layers to this web map and save as your own map. If you like, you can add this web map to a custom basemap gallery for others in your organization to use in creating web maps. If you would like to add this map as a layer in other maps you are creating, you may use the tile layer referenced in this map.

Have you ever wanted to create your own maps, or integrate and visualize spatial datasets to examine changes in trends between locations and over time? Follow along with these training tutorials on QGIS, an open source geographic information system (GIS) and learn key concepts, procedures and skills for performing common GIS tasks – such as creating maps, as well as joining, overlaying and visualizing spatial datasets. These tutorials are geared towards new GIS users. We’ll start with foundational concepts, and build towards more advanced topics throughout – demonstrating how with a few relatively easy steps you can get quite a lot out of GIS. You can then extend these skills to datasets of thematic relevance to you in addressing tasks faced in your day-to-day work.

The North Carolina State and County Boundary vector polygon data provides location information for North Carolina State and County Boundary lines derived from the best available survey and/or Geographic Information System (GIS) data. Sources for information are the North Carolina Geodetic Survey (NCGS), NC Department of Transportation (NCDOT), United States Geological Survey (USGS), and field surveys conducted by licensed surveyors in North Carolina and neighboring states that have been approved and recorded in their respective counties. North Carolina Geodetic Survey assists counties on a cooperative basis (NC General Statute 153A-18) in defining and monumenting the location of uncertain or disputed boundaries as established by law. Some counties have completed boundary surveys for at least a portion of their county boundary. However, the majority of county boundaries have not been surveyed and are represented by the best currently available data from GIS sources, including NCDOT county maps (which originally came from the USGS) and updated county parcel maps.

This specialized location dataset delivers detailed information about marina establishments. Maritime industry professionals, coastal planners, and tourism researchers can leverage precise location insights to understand maritime infrastructure, analyze recreational boating landscapes, and develop targeted strategies.

How Do We Create Polygons? -All our polygons are manually crafted using advanced GIS tools like QGIS, ArcGIS, and similar applications. This involves leveraging aerial imagery and street-level views to ensure precision. -Beyond visual data, our expert GIS data engineers integrate venue layout/elevation plans sourced from official company websites to construct detailed indoor polygons. This meticulous process ensures higher accuracy and consistency. -We verify our polygons through multiple quality checks, focusing on accuracy, relevance, and completeness.

What's More? -Custom Polygon Creation: Our team can build polygons for any location or category based on your specific requirements. Whether it’s a new retail chain, transportation hub, or niche point of interest, we’ve got you covered. -Enhanced Customization: In addition to polygons, we capture critical details such as entry and exit points, parking areas, and adjacent pathways, adding greater context to your geospatial data. -Flexible Data Delivery Formats: We provide datasets in industry-standard formats like WKT, GeoJSON, Shapefile, and GDB, making them compatible with various systems and tools. -Regular Data Updates: Stay ahead with our customizable refresh schedules, ensuring your polygon data is always up-to-date for evolving business needs.

Unlock the Power of POI and Geospatial Data With our robust polygon datasets and point-of-interest data, you can: -Perform detailed market analyses to identify growth opportunities. -Pinpoint the ideal location for your next store or business expansion. -Decode consumer behavior patterns using geospatial insights. -Execute targeted, location-driven marketing campaigns for better ROI. -Gain an edge over competitors by leveraging geofencing and spatial intelligence.

Why Choose LocationsXYZ? LocationsXYZ is trusted by leading brands to unlock actionable business insights with our spatial data solutions. Join our growing network of successful clients who have scaled their operations with precise polygon and POI data. Request your free sample today and explore how we can help accelerate your business growth.

This dataset contains shapefile boundaries for CA State, counties and places from the US Census Bureau's 2023 MAF/TIGER database. Current geography in the 2023 TIGER/Line Shapefiles generally reflects the boundaries of governmental units in effect as of January 1, 2023.

New political and administrative boundaries Shapefile of Nepal. Downloaded and republished from the Survey Department website.

Reason for Selection Protected natural areas in urban environments provide urban residents a nearby place to connect with nature and offer refugia for some species. Because beaches in Puerto Rico and the U.S. Virgin Islands are open to the public, beaches also provide important outdoor recreation opportunities for urban residents, so we include beaches as parks in this indicator. Input Data

Southeast Blueprint 2023 subregions: Caribbean
Southeast Blueprint 2023 extent
National Oceanic and Atmospheric Administration (NOAA) National Centers for Environmental Information (NCEI) Coastal Relief Model, accessed 11-22-2022
Protected Areas Database of the United States (PAD-US) 3.0: VI, PR, and Marine Combined Fee Easement
Puerto Rico Protected Natural Areas 2018 (December 2018 update): Terrestrial and marine protected areas (PACAT2018_areas_protegidasPR_TERRESTRES_07052019.shp, PACAT2018_areas_protegidasPR_MARINAS_07052019.shp) 
2020 Census Urban Areas from the Census Bureau’s urban-rural classification; download the data, read more about how urban areas were redefined following the 2020 census
OpenStreetMap data “multipolygons” layer, accessed 3-14-2023

A polygon from this dataset is considered a park if the “leisure” tag attribute is either “park” or “nature_reserve”, and considered a beach if the value in the “natural” tag attribute is “beach”. OpenStreetMap describes leisure areas as “places people go in their spare time” and natural areas as “a wide variety of physical geography, geological and landcover features”. Data were downloaded in .pbf format and translated ton an ESRI shapefile using R code. OpenStreetMap® is open data, licensed under the Open Data Commons Open Database License (ODbL) by the OpenStreetMap Foundation (OSMF). Additional credit to OSM contributors. Read more on the OSM copyright page.

TNC Lands - Public Layer, accessed 3-8-2023
U.S. Virgin Islands beaches layer (separate vector layers for St. Croix, St. Thomas, and St. John) provided by Joe Dwyer with Lynker/the NOAA Caribbean Climate Adaptation Program on 3-3-2023 (contact jdwyer@lynker.com for more information)

Mapping Steps

Most mapping steps were completed using QGIS (v 3.22) Graphical Modeler.
Fix geometry errors in the PAD-US PR data using Fix Geometry. This must be done before any analysis is possible.
Merge the terrestrial PR and VI PAD-US layers.
Use the NOAA coastal relief model to restrict marine parks (marine polygons from PAD-US and Puerto Rico Protected Natural Areas) to areas shallower than 10 m in depth. The deep offshore areas of marine parks do not meet the intent of this indicator to capture nearby opportunities for urban residents to connect with nature.
Merge into one layer the resulting shallow marine parks from marine PAD-US and the Puerto Rico Protected Natural Areas along with the combined terrestrial PAD-US parks, OpenStreetMap, TNC Lands, and USVI beaches. Omit from the Puerto Rico Protected Areas layer the “Zona de Conservación del Carso”, which has some policy protections and conservation incentives but is not formally protected.
Fix geometry errors in the resulting merged layer using Fix Geometry.
Intersect the resulting fixed file with the Caribbean Blueprint subregion.
Process all multipart polygons to single parts (referred to in Arc software as an “explode”). This helps the indicator capture, as much as possible, the discrete units of a protected area that serve urban residents.
Clip the Census urban area to the Caribbean Blueprint subregion.
Select all polygons that intersect the Census urban extent within 1.2 miles (1,931 m). The 1.2 mi threshold is consistent with the average walking trip on a summer day (U.S. DOT 2002) used to define the walking distance threshold used in the greenways and trails indicator. Note: this is further than the 0.5 mi distance used in the continental version of the indicator. We extended it to capture East Bay and Point Udall based on feedback from the local conservation community about the importance of the park for outdoor recreation.
Dissolve all the park polygons that were selected in the previous step.
Process all multipart polygons to single parts (“explode”) again.
Add a unique ID to the selected parks. This value will be used to join the parks to their buffers.
Create a 1.2 mi (1,931 m) buffer ring around each park using the multiring buffer plugin in QGIS. Ensure that “dissolve buffers” is disabled so that a single 1.2 mi buffer is created for each park.
Assess the amount of overlap between the buffered park and the Census urban area using overlap analysis. This step is necessary to identify parks that do not intersect the urban area, but which lie within an urban matrix. This step creates a table that is joined back to the park polygons using the UniqueID.
Remove parks that had ≤2% overlap with the urban areas when buffered. This excludes mostly non-urban parks that do not meet the intent of this indicator to capture parks that provide nearby access for urban residents. Note: In the continental version of this indicator, we used a threshold of 10%. In the Caribbean version, we lowered this to 2% in order to capture small parks that dropped out of the indicator when we extended the buffer distance to 1.2 miles.
Calculate the GIS acres of each remaining park unit using the Add Geometry Attributes function.
Join the buffer attribute table to the previously selected parks, retaining only the parks that exceeded the 2% urban area overlap threshold while buffered. 
Buffer the selected parks by 15 m. Buffering prevents very small parks and narrow beaches from being left out of the indicator when the polygons are converted to raster.
Reclassify the polygons into 7 classes, seen in the final indicator values below. These thresholds were informed by park classification guidelines from the National Recreation and Park Association, which classify neighborhood parks as 5-10 acres, community parks as 30-50 acres, and large urban parks as optimally 75+ acres (Mertes and Hall 1995).
Export the final vector file to a shapefile and import to ArcGIS Pro.
Convert the resulting polygons to raster using the ArcPy Polygon to Raster function. Assign values to the pixels in the resulting raster based on the polygon class sizes of the contiguous park areas.
Clip to the Caribbean Blueprint 2023 subregion.
As a final step, clip to the spatial extent of Southeast Blueprint 2023. 

Note: For more details on the mapping steps, code used to create this layer is available in the Southeast Blueprint Data Download under > 6_Code. Final indicator values Indicator values are assigned as follows: 6 = 75+ acre urban park 5 = >50 to <75 acre urban park 4 = 30 to <50 acre urban park 3 = 10 to <30 acre urban park 2 = 5 to <10 acre urban park 1 = <5 acre urban park 0 = Not identified as an urban park Known Issues

This indicator does not include park amenities that influence how well the park serves people and should not be the only tool used for parks and recreation planning. Park standards should be determined at a local level to account for various community issues, values, needs, and available resources. 
This indicator includes some protected areas that are not open to the public and not typically thought of as “parks”, like mitigation lands, private easements, and private golf courses. While we experimented with excluding them using the public access attribute in PAD, due to numerous inaccuracies, this inadvertently removed protected lands that are known to be publicly accessible. As a result, we erred on the side of including the non-publicly accessible lands.
This indicator includes parks and beaches from OpenStreetMap, which is a crowdsourced dataset. While members of the OpenStreetMap community often verify map features to check for accuracy and completeness, there is the potential for spatial errors (e.g., misrepresenting the boundary of a park) or incorrect tags (e.g., labelling an area as a park that is not actually a park). However, using a crowdsourced dataset gives on-the-ground experts, Blueprint users, and community members the power to fix errors and add new parks to improve the accuracy and coverage of this indicator in the future.

Other Things to Keep in Mind

This indicator calculates the area of each park using the park polygons from the source data. However, simply converting those park polygons to raster results in some small parks and narrow beaches being left out of the indicator. To capture those areas, we buffered parks and beaches by 15 m and applied the original area calculation to the larger buffered polygon, so as not to inflate the area by including the buffer. As a result, when the buffered polygons are rasterized, the final indicator has some areas of adjacent pixels that receive different scores. While these pixels may appear to be part of one contiguous park or suite of parks, they are scored differently because the park polygons themselves are not actually contiguous. 
The Caribbean version of this indicator uses a slightly different methodology than the continental Southeast version. It includes parks within a 1.2 mi distance from the Census urban area, compared to 0.5 mi in the continental Southeast. We extended it to capture East Bay and Point Udall based on feedback from the local conservation community about the importance of the park for outdoor recreation. Similarly, this indicator uses a 2% threshold of overlap between buffered parks and the Census urban areas, compared to a 10% threshold in the continental Southeast. This helped capture small parks that dropped out of the indicator when we extended the buffer distance to 1.2 miles. Finally, the Caribbean version does not use the impervious surface cutoff applied in the continental Southeast

This dataset is provided by the WMS service at https://geomap.gsmma.gov.tw/mapguide/mapagent/mapagent.fcgi?version1.0.0&formatimage/png. Please add the URL shown in the downloaded file to GIS software (such as QGIS) and then you can select this layer from the directory.

Georeferenced (to WGS1984) and cropped set of about 820 historic maps of Burma at a scale of 1 inch per mile (63,360) covering about 75% of the country. Those topographic maps, originally produced and published by the Great Trigonometrical Survey of India between 1899 and 1946, have been scanned and shared with the public as part of the "Old Survey Of India Maps” Community under a CC BY 4.0 International Licence. Many of these maps are reprints of earlier maps produced before the war. Most mapsheets are early editions (edition 1 or edition 2).

Each of the 820 map sheet scans was georeferenced using the Latitude-Longitude corner coordinates in Everest 1830 projection. Those map sheets were cropped, keeping only the map area - to allow a seamless mosaic without the mapframe overlapping adjacent map sheets when several map sheets are put together in a GIS. Those cropped map sheets were projected from Everest 1830 to WGS1984 (EPSG4326) - standard GPS - projection to make them easier to use and combine with other GIS data.

Those map sheets can be loaded directly in any GIS such as QGIS or ESRI ArcGIS as well as Google Earth.

• The mm_OI_JBv2024 folder contains the cropped end georeferenced map sheets in jpg-format as well as accompagning georeference and metadata incl.
  
  • The mm_OI_JBv2024_kmlLinks contains kml files to easily load the mapsheets into Google Earth
  • The mm_historicOI_EPSG4326.gdb contains an ESRI mosaic dataset to easily load all mapsheets into ArcGIS
• The mm_OI_JBv2024_scanMaps folder contains the uncropped original map scans (renamed though) in jpg-format.
• The mm_topoOI_JBv7_masterlist.xlsx is a masterlist cataloguing all map sheets for easier use and matching them with the original source files as shared as part of the "Old Survey Of India Maps" (e.g. to identify new mapsheets should new maps be released)
• The indexMaps folder contains small scale index maps to locate the map sheets using their map sheet Grid-Letter-nomenclature

All georeferenced map scans are based on maps shared by John Brown via Zenodo

• https://zenodo.org/records/8040798 (63k Maps of Burma, version 7, Published June 14, 2023)
• https://zenodo.org/records/10463372 (63k Maps of Burma--additional 1--20240105, version 1, Published January 5, 2024)

The file naming convention is to first give the number of the 4 degree x 4 degree block followed by the letter (A to P) of the sixteen 1 degree x 1 degree blocks in each 4 degree block eg. 38 D, and this is followed by a number from 1 to 16 to indicate the number of the map in the 1 degree block.

This Number Letter Number designation is followed by the map series type either OI (contains a LCC grid) or OILatLon (only has a Lat-Lon grid), followed by the edition and year of the edition, followed by the date of publication/print. If the information is not available an "X" (for edition) or "0000" (for an unknown year) is used. A best-guess approach was used if the edition and print year and version information was ambiguous.

The files as shared via the "Old Survey Of India Maps" have been renamed to standardize the file naming, sometimes correcting them and to make them unique in the case several editions of the same map sheet were available.

A topographical index produced by the Survey of India is provided to assist the viewer in selecting a particular map of interest.

Dataset for: Bedding scale correlation on Mars in western Arabia Terra

A.M. Annex et al.

Data Product Overview

This repository contains all source data for the publication. Below is a description of each general data product type, software that can load the data, and a list of the file names along with the short description of the data product.

HiRISE Digital Elevation Models (DEMs).

HiRISE DEMs produced using the Ames Stereo Pipeline are in geotiff format ending with ‘*X_0_DEM-adj.tif’, the “X” prefix denotes the spatial resolution of the data product in meters. Geotiff files are able to be read by free GIS software like QGIS.

HiRISE map-projected imagery (DRGs).

Map-projected HiRISE images produced using the Ames Stereo Pipeline are in geotiff format ending with ‘*0_Y_DRG-cog.tif’, the “Y” prefix denotes the spatial resolution of the data product in centimeters. Geotiff files are able to be read by free GIS software like QGIS. The DRG files are formatted as COG-geotiffs for enhanced compression and ease of use.

3D Topography files (.ply).

Traingular Mesh versions of the HiRISE/CTX topography data used for 3D figures in “.ply” format. Meshes are greatly geometrically simplified from source files. Topography files can be loaded in a variety of open source tools like ParaView and Meshlab. Textures can be applied using embedded texture coordinates.

3D Geological Model outputs (.vtk)

VTK 3D file format files of model output over the spatial domain of each study site. VTK files can be loaded by ParaView open source software. The “block” files contain the model evaluation over a regular grid over the model extent. The “surfaces” files contain just the bedding surfaces as interpolated from the “block” files using the marching cubes algorithm.

Geological Model geologic maps (geologic_map.tif).

Geologic maps from geological models are standard geotiffs readable by conventional GIS software. The maximum value for each geologic map is the “no-data” value for the map. Geologic maps are calculated at a lower resolution than the topography data for storage efficiency.

Beds Geopackage File (.gpkg).

Geopackage vector data file containing all mapped layers and associated metadata including dip corrected bed thickness as well as WKB encoded 3D linestrings representing the sampled topography data to which the bedding orientations were fit. Geopackage files can be read using GIS software like QGIS and ArcGIS as well as the OGR/GDAL suite. A full description of each column in the file is provided below.

    Column
    Type
    Description




    uuid
    String
    unique identifier


    stratum_order
    Real
    0-indexed bed order


    section
    Real
    section number


    layer_id
    Real
    bed number/index


    layer_id_bk
    Real
    unused backup bed number/index


    source_raster
    String
    dem file path used


    raster
    String
    dem file name


    gsd
    Real
    ground sampling distant for dem


    wkn
    String
    well known name for dem


    rtype
    String
    raster type


    minx
    Real
    minimum x position of trace in dem crs


    miny
    Real
    minimum y position of trace in dem crs


    maxx
    Real
    maximum x position of trace in dem crs


    maxy
    Real
    maximum y position of trace in dem crs


    method
    String
    internal interpolation method


    sl
    Real
    slope in degrees


    az
    Real
    azimuth in degrees


    error
    Real
    maximum error ellipse angle


    stdr
    Real
    standard deviation of the residuals


    semr
    Real
    standard error of the residuals


    X
    Real
    mean x position in CRS


    Y
    Real
    mean y position in CRS


    Z
    Real
    mean z position in CRS


    b1
    Real
    plane coefficient 1


    b2
    Real
    plane coefficient 2


    b3
    Real
    plane coefficient 3


    b1_se
    Real
    standard error plane coefficient 1


    b2_se
    Real
    standard error plane coefficient 2


    b3_se
    Real
    standard error plane coefficient 3


    b1_ci_low
    Real
    plane coefficient 1 95% confidence interval low


    b1_ci_high
    Real
    plane coefficient 1 95% confidence interval high


    b2_ci_low
    Real
    plane coefficient 2 95% confidence interval low


    b2_ci_high
    Real
    plane coefficient 2 95% confidence interval high


    b3_ci_low
    Real
    plane coefficient 3 95% confidence interval low


    b3_ci_high
    Real
    plane coefficient 3 95% confidence interval high


    pca_ev_1
    Real
    pca explained variance ratio pc 1


    pca_ev_2
    Real
    pca explained variance ratio pc 2


    pca_ev_3
    Real
    pca explained variance ratio pc 3


    condition_number
    Real
    condition number for regression


    n
    Integer64
    number of data points used in regression


    rls
    Integer(Boolean)
    unused flag


    demeaned_regressions
    Integer(Boolean)
    centering indicator


    meansl
    Real
    mean section slope


    meanaz
    Real
    mean section azimuth


    angular_error
    Real
    angular error for section


    mB_1
    Real
    mean plane coefficient 1 for section


    mB_2
    Real
    mean plane coefficient 2 for section


    mB_3
    Real
    mean plane coefficient 3 for section


    R
    Real
    mean plane normal orientation vector magnitude


    num_valid
    Integer64
    number of valid planes in section


    meanc
    Real
    mean stratigraphic position


    medianc
    Real
    median stratigraphic position


    stdc
    Real
    standard deviation of stratigraphic index


    stec
    Real
    standard error of stratigraphic index


    was_monotonic_increasing_layer_id
    Integer(Boolean)
    monotonic layer_id after projection to stratigraphic index


    was_monotonic_increasing_meanc
    Integer(Boolean)
    monotonic meanc after projection to stratigraphic index


    was_monotonic_increasing_z
    Integer(Boolean)
    monotonic z increasing after projection to stratigraphic index


    meanc_l3sigma_std
    Real
    lower 3-sigma meanc standard deviation


    meanc_u3sigma_std
    Real
    upper 3-sigma meanc standard deviation


    meanc_l2sigma_sem
    Real
    lower 3-sigma meanc standard error


    meanc_u2sigma_sem
    Real
    upper 3-sigma meanc standard error


    thickness
    Real
    difference in meanc


    thickness_fromz
    Real
    difference in Z value


    dip_cor
    Real
    dip correction


    dc_thick
    Real
    thickness after dip correction


    dc_thick_fromz
    Real
    z thickness after dip correction


    dc_thick_dev
    Integer(Boolean)
    dc_thick <= total mean dc_thick


    dc_thick_fromz_dev
    Integer(Boolean)
    dc_thick <= total mean dc_thick_fromz


    thickness_fromz_dev
    Integer(Boolean)
    dc_thick <= total mean thickness_fromz


    dc_thick_dev_bg
    Integer(Boolean)
    dc_thick <= section mean dc_thick


    dc_thick_fromz_dev_bg
    Integer(Boolean)
    dc_thick <= section mean dc_thick_fromz


    thickness_fromz_dev_bg
    Integer(Boolean)
    dc_thick <= section mean thickness_fromz


    slr
    Real
    slope in radians


    azr
    Real
    azimuth in radians


    meanslr
    Real
    mean slope in radians


    meanazr
    Real
    mean azimuth in radians


    angular_error_r
    Real
    angular error of section in radians


    pca_ev_1_ok
    Integer(Boolean)
    pca_ev_1 < 99.5%


    pca_ev_2_3_ratio
    Real
    pca_ev_2/pca_ev_3


    pca_ev_2_3_ratio_ok
    Integer(Boolean)
    pca_ev_2_3_ratio > 15


    xyz_wkb_hex
    String
    hex encoded wkb geometry for all points used in regression

Geological Model input files (.gpkg).

Four geopackage (.gpkg) files represent the input dataset for the geological models, one per study site as specified in the name of the file. The files contain most of the columns described above in the Beds geopackage file, with the following additional columns. The final seven columns (azimuth, dip, polarity, formation, X, Y, Z) constituting the actual parameters used by the geological model (GemPy).

    Column
    Type
    Description




    azimuth_mean
    String
    Mean section dip azimuth 


    azimuth_indi
    Real
    Individual bed azimuth


    azimuth
    Real
    Azimuth of trace used by the geological model


    dip
    Real
    Dip for the trace used by the geological mode


    polarity
    Real
    Polarity of the dip vector normal vector 


    formation
    String
    String representation of layer_id required for GemPy models


    X
    Real
    X position in the CRS of the sampled point on the trace


    Y
    Real
    Y position in the CRS of the sampled point on the trace


    Z
    Real
    Z position in the CRS of the sampled point on the trace

Stratigraphic Column Files (.gpkg).

Stratigraphic columns computed from the Geological Models come in three kinds of Geopackage vector files indicated by the postfixes _sc, rbsc, and rbssc. File names include the wkn site name.

sc (_sc.gpkg).

Geopackage vector data file containing measured bed thicknesses from Geological Model joined with corresponding Beds Geopackage file, subsetted partially. The columns largely overlap with the the list above for the Beds Geopackage but with the following additions

    Column
    Type
    Description




    X
    Real
    X position of thickness measurement


    Y
    Real
    Y position of thickness measurement


    Z
    Real
    Z position of thickness measurement


    formation
    String
    Model required string representation of bed index


    bed thickness (m)
    Real
    difference of bed elevations


    azimuths
    Real
    azimuth as measured from model in degrees


    dip_degrees
    Real
    dip as measured from model in

This layer presents the Universal Transverse Mercator (UTM) zones of the world. The layer symbolizes the 6-degree wide zones employed for UTM projection.To download the data for this layer as a layer package for use in ArcGIS desktop applications, refer to World UTM Zones Grid.

This is a series of datasets covering the State of Queensland displaying hydrographic features. Features are attributed with source information, perennially, hierarchy and names where available. Watercourses are connected and flow directed. Connectors flow through waterbodies to create a linear network for hydrological modelling. Datasets include: - Watercourses, Canals, Lakes - natural waterbodies, Reservoirs - man-made waterbodies, Flats including saline coastal flats, swamps, Pondage areas including aquaculture, settling ponds, Waterfalls

Reason for SelectionProtected natural areas in urban environments provide urban residents a nearby place to connect with nature and offer refugia for some species. They help foster a conservation ethic by providing opportunities for people to connect with nature, and also support ecosystem services like offsetting heat island effects (Greene and Millward 2017, Simpson 1998), water filtration, stormwater retention, and more (Hoover and Hopton 2019). In addition, parks, greenspace, and greenways can help improve physical and psychological health in communities (Gies 2006). Urban park size complements the equitable access to potential parks indicator by capturing the value of existing parks.Input DataSoutheast Blueprint 2024 extentFWS National Realty Tracts, accessed 12-13-2023Protected Areas Database of the United States(PAD-US):PAD-US 3.0national geodatabase -Combined Proclamation Marine Fee Designation Easement, accessed 12-6-20232020 Census Urban Areas from the Census Bureau’s urban-rural classification; download the data, read more about how urban areas were redefined following the 2020 censusOpenStreetMap data “multipolygons” layer, accessed 12-5-2023A polygon from this dataset is considered a beach if the value in the “natural” tag attribute is “beach”. Data for coastal states (VA, NC, SC, GA, FL, AL, MS, LA, TX) were downloaded in .pbf format and translated to an ESRI shapefile using R code. OpenStreetMap® is open data, licensed under theOpen Data Commons Open Database License (ODbL) by theOpenStreetMap Foundation (OSMF). Additional credit to OSM contributors. Read more onthe OSM copyright page.2021 National Land Cover Database (NLCD): Percentdevelopedimperviousness2023NOAA coastal relief model: volumes 2 (Southeast Atlantic), 3 (Florida and East Gulf of America), 4 (Central Gulf of America), and 5 (Western Gulf of America), accessed 3-27-2024Mapping StepsCreate a seamless vector layer to constrain the extent of the urban park size indicator to inland and nearshore marine areas <10 m in depth. The deep offshore areas of marine parks do not meet the intent of this indicator to capture nearby opportunities for urban residents to connect with nature. Shallow areas are more accessible for recreational activities like snorkeling, which typically has a maximum recommended depth of 12-15 meters. This step mirrors the approach taken in the Caribbean version of this indicator.Merge all coastal relief model rasters (.nc format) together using QGIS “create virtual raster”.Save merged raster to .tif and import into ArcPro.Reclassify the NOAA coastal relief model data to assign areas with an elevation of land to -10 m a value of 1. Assign all other areas (deep marine) a value of 0.Convert the raster produced above to vector using the “RasterToPolygon” tool.Clip to 2024 subregions using “Pairwise Clip” tool.Break apart multipart polygons using “Multipart to single parts” tool.Hand-edit to remove deep marine polygon.Dissolve the resulting data layer.This produces a seamless polygon defining land and shallow marine areas.Clip the Census urban area layer to the bounding box of NoData surrounding the extent of Southeast Blueprint 2024.Clip PAD-US 3.0 to the bounding box of NoData surrounding the extent of Southeast Blueprint 2024.Remove the following areas from PAD-US 3.0, which are outside the scope of this indicator to represent parks:All School Trust Lands in Oklahoma and Mississippi (Loc Des = “School Lands” or “School Trust Lands”). These extensive lands are leased out and are not open to the public.All tribal and military lands (“Des_Tp” = "TRIBL" or “Des_Tp” = "MIL"). Generally, these lands are not intended for public recreational use.All BOEM marine lease blocks (“Own_Name” = "BOEM"). These Outer Continental Shelf lease blocks do not represent actively protected marine parks, but serve as the “legal definition for BOEM offshore boundary coordinates...for leasing and administrative purposes” (BOEM).All lands designated as “proclamation” (“Des_Tp” = "PROC"). These typically represent the approved boundary of public lands, within which land protection is authorized to occur, but not all lands within the proclamation boundary are necessarily currently in a conserved status.Retain only selected attribute fields from PAD-US to get rid of irrelevant attributes.Merged the filtered PAD-US layer produced above with the OSM beaches and FWS National Realty Tracts to produce a combined protected areas dataset.The resulting merged data layer contains overlapping polygons. To remove overlapping polygons, use the Dissolve function.Clip the resulting data layer to the inland and nearshore extent.Process all multipart polygons (e.g., separate parcels within a National Wildlife Refuge) to single parts (referred to in Arc software as an “explode”).Select all polygons that intersect the Census urban extent within 0.5 miles. We chose 0.5 miles to represent a reasonable walking distance based on input and feedback from park access experts. Assuming a moderate intensity walking pace of 3 miles per hour, as defined by the U.S. Department of Health and Human Service’s physical activity guidelines, the 0.5 mi distance also corresponds to the 10-minute walk threshold used in the equitable access to potential parks indicator.Dissolve all the park polygons that were selected in the previous step.Process all multipart polygons to single parts (“explode”) again.Add a unique ID to the selected parks. This value will be used in a later step to join the parks to their buffers.Create a 0.5 mi (805 m) buffer ring around each park using the multiring plugin in QGIS. Ensure that “dissolve buffers” is disabled so that a single 0.5 mi buffer is created for each park.Assess the amount of overlap between the buffered park and the Census urban area using “overlap analysis”. This step is necessary to identify parks that do not intersect the urban area, but which lie within an urban matrix (e.g., Umstead Park in Raleigh, NC and Davidson-Arabia Mountain Nature Preserve in Atlanta, GA). This step creates a table that is joined back to the park polygons using the UniqueID.Remove parks that had ≤10% overlap with the urban areas when buffered. This excludes mostly non-urban parks that do not meet the intent of this indicator to capture parks that provide nearby access for urban residents. Note: The 10% threshold is a judgement call based on testing which known urban parks and urban National Wildlife Refuges are captured at different overlap cutoffs and is intended to be as inclusive as possible.Calculate the GIS acres of each remaining park unit using the Add Geometry Attributes function.Buffer the selected parks by 15 m. Buffering prevents very small and narrow parks from being left out of the indicator when the polygons are converted to raster.Reclassify the parks based on their area into the 7 classes seen in the final indicator values below. These thresholds were informed by park classification guidelines from the National Recreation and Park Association, which classify neighborhood parks as 5-10 acres, community parks as 30-50 acres, and large urban parks as optimally 75+ acres (Mertes and Hall 1995).Assess the impervious surface composition of each park using the NLCD 2021 impervious layer and the Zonal Statistics “MEAN” function. Retain only the mean percent impervious value for each park.Extract only parks with a mean impervious pixel value <80%. This step excludes parks that do not meet the intent of the indicator to capture opportunities to connect with nature and offer refugia for species (e.g., the Superdome in New Orleans, LA, the Astrodome in Houston, TX, and City Plaza in Raleigh, NC).Extract again to the inland and nearshore extent.Export the final vector file to a shapefile and import to ArcGIS Pro.Convert the resulting polygons to raster using the ArcPy Feature to Raster function and the area class field.Assign a value of 0 to all other pixels in the Southeast Blueprint 2024 extent not already identified as an urban park in the mapping steps above. Zero values are intended to help users better understand the extent of this indicator and make it perform better in online tools.Use the land and shallow marine layer and “extract by mask” tool to save the final version of this indicator.Add color and legend to raster attribute table.As a final step, clip to the spatial extent of Southeast Blueprint 2024.Note: For more details on the mapping steps, code used to create this layer is available in theSoutheast Blueprint Data Downloadunder > 6_Code.Final indicator valuesIndicator values are assigned as follows:6= 75+ acre urban park5= 50 to <75 acre urban park4= 30 to <50 acre urban park3= 10 to <30 acre urban park2=5 to <10acreurbanpark1 = <5 acre urban park0 = Not identified as an urban parkKnown IssuesThis indicator does not include park amenities that influence how well the park serves people and should not be the only tool used for parks and recreation planning. Park standards should be determined at a local level to account for various community issues, values, needs, and available resources.This indicator includes some protected areas that are not open to the public and not typically thought of as “parks”, like mitigation lands, private easements, and private golf courses. While we experimented with excluding them using the public access attribute in PAD, due to numerous inaccuracies, this inadvertently removed protected lands that are known to be publicly accessible. As a result, we erred on the side of including the non-publicly accessible lands.The NLCD percent impervious layer contains classification inaccuracies. As a result, this indicator may exclude parks that are mostly natural because they are misclassified as mostly impervious. Conversely, this indicator may include parks that are mostly impervious because they are misclassified as mostly

Notice: this is not the latest Heat Island Anomalies image service. For 2023 data visit https://tpl.maps.arcgis.com/home/item.html?id=e89a556263e04cb9b0b4638253ca8d10.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. This 30-meter raster was derived from Landsat 8 imagery band 10 (ground-level thermal sensor) from the summer of 2021, with patching from summer of 2020 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): 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.

Notice: this is 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 2023.To explore previous versions of the data, visit the links below:Full Range Heat Anomalies - USA 2022Full Range Heat Anomalies - USA 2021Full Range Heat Anomalies - USA 2020Federal 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 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.

Reason for SelectionHardbottom provides an anchor for important seafloor habitats such as deep-sea corals, plants, and sponges. Hardbottom is also sometimes associated with chemosynthetic communities that form around cold seeps or hydrothermal vents. In these unique ecosystems, micro-organisms that convert chemicals into energy form the base of complex food webs (Love et al. 2013). Hardbottom and associated species provide important habitat structure for many fish and invertebrates (NOAA 2018). Hardbottom areas serve as fish nursery, spawning, and foraging grounds, supporting commercially valuable fisheries like snapper and grouper (NCDEQ 2016).According to Dunn and Halpin (2009), “hardbottom habitats support high levels of biodiversity and are frequently used as a surrogate for it in marine spatial planning.” Artificial reefs arealso known to provide additional habitat that is quickly colonized to provide a suite of ecosystem services commonly associated with naturally occurring hardbottom (Wu et al. 2019). We did not include active oil and gas structures as human-created hardbottom. Although they provide habitat, because of their temporary nature, risk of contamination, and contributions to climate change, they do not have the same level of conservation value as other artificial structures.Input DataSoutheast Blueprint 2024 extentSoutheast Blueprint 2024 subregionsCoral & hardbottomusSEABED Gulf of America sediments, accessed 12-14-2023; download the data; view and read more about the data on the National Oceanic and Atmospheric Administration (NOAA) Gulf of Mexico Atlas (select Physical --> Marine geology --> 1. Dominant bottom types and habitats)Bureau of Ocean Energy Management (BOEM) Gulf of America, seismic water bottom anomalies, accessed 12-20-2023The Nature Conservancy’s (TNC)South Atlantic Bight Marine Assessment(SABMA); chapter 3 ofthe final reportprovides more detail on the seafloor habitats analysisNOAA deep-sea coral and sponge locations, accessed 12-20-2023 on theNOAA Deep-Sea Coral & Sponge Map PortalFlorida coral and hardbottom habitats, accessed 12-19-2023Shipwrecks & artificial reefsNOAA wrecks and obstructions layer, accessed 12-12-2023 on theMarine CadastreLouisiana Department of Wildlife and Fisheries (LDWF) Artificial Reefs: Inshore Artificial Reefs, Nearshore Artificial Reefs, Offshore and Deepwater Artificial Reefs (Google Earth/KML files), accessed 12-19-2023Texas Parks and Wildlife Department (TPWD) Artificial Reefs, accessed 12-19-2023; download the data fromThe Artificial Reefs Interactive Mapping Application(direct download from interactive mapping application)Mississippi Department of Marine Resources (MDMR) Artificial Reef Bureau: Inshore Reefs, Offshore Reefs, Rigs to Reef (lat/long coordinates), accessed 12-19-2023Alabama Department of Conservation and Natural Resources (ADCNR) Artificial Reefs: Master Alabama Public Reefs v2023 (.xls), accessed 12-19-2023Florida Fish and Wildlife Conservation Commission (FWC):Artificial Reefs in Florida(.xlsx), accessed 12-19-2023Defining inland extent & split with AtlanticMarine Ecoregions Level III from the Commission for Environmental Cooperation North American Environmental Atlas, accessed 12-8-20212023NOAA coastal relief model: volumes 2 (Southeast Atlantic), 3 (Florida and East Gulf of America), 4 (Central Gulf of America), and 5 (Western Gulf of America), accessed 3-27-2024National Oceanic and Atmospheric Administration (NOAA)Characterizing Spatial Distributions of Deep-sea Corals and Hardbottom Habitats in the U.S. Southeast Atlantic;read the final report; data shared prior to official release on 2-4-2022 by Matt Poti with the NOAA National Centers for Coastal Ocean Science (NCCOS) (matthew.poti@noaa.gov)Predictive Modeling and Mapping of Hardbottom Seafloor Habitats off the Southeast U.S: unpublished NOAA data anddraft final report entitled Assessment of Benthic Habitats for Fisheries Managementprovided on 1-28-2021 by Matt Poti with NOAA NCCOS (matthew.poti@noaa.gov)Mapping StepsNote: Most of the mapping steps were accomplished using the graphical modeler in QGIS 3.34. Individual models were created to combine data sources and assign ranked values. These models were combined in a single model to assemble all the data sources and create a summary raster.Create a seamless vector layer to constrain the extent of the Atlantic coral and hardbottom indicator to marine and estuarine areas <1 m in elevation. This defines how far inland it extends.Merge together all coastal relief model rasters (.nc format) using the create virtual raster tool in QGIS.Save the merged raster to .tif format and import it into ArcPro.Reclassify the NOAA coastal relief model data to assign a value of 1 to areas from deep marine to 1 m elevation. Assign all other areas (land) a value of 0.Convert the raster produced above to vector using the raster to polygon tool.Clip to the 2024 Blueprint subregions using the pairwise clip tool.Hand-edit to remove terrestrial polygons (one large terrestrial polygon and the Delmarva peninsula).Dissolve the resulting data layer to produce a seamless polygon defining marine and estuarine areas <1 m in elevation.Hand-edit to select all but the main marine polygon and delete.Define the extent of the Gulf version of this indicator to separate it from the Atlantic. This split reflects the extent of the different datasets available to represent coral and hardbottom habitat in the Atlantic and Gulf, rather than a meaningful ecological transition.Use the select tool to select the Florida Keys class from the Level III marine ecoregions (“NAME_L3 = "Florida Keys"“).Buffer the “Florida Keys” Level III marine ecoregion by 2 km to extend it far enough inland to intersect the inland edge of the <1 m elevation layer.Reclassify the two NOAA Atlantic hardbottom suitability datasets to give all non-NoData pixels a value of 0. Combine the reclassified hardbottom suitability datasets to define the total extent of these data. Convert the raster extent to vector and dissolve to create a polygon representing the extent of both NOAA hardbottom datasets.Union the buffered ecoregion with the combined NOAA extent polygon created above. Add a field and use it to dissolve the unioned polygons into one polygon. This leaves some holes inside the polygon, so use the eliminate polygon part tool to fill in those holes, then convert the polygon to a line.Hand-edit to extract the resulting line between the Gulf and Atlantic.Hand-edit to use this line to split the <1 m elevation layer created earlier in the mapping steps to create the separation between the Gulf and Atlantic extent.From the BOEM seismic water bottom anomaly data, extract the following shapefiles: anomaly_confirmed_relic_patchreefs.shp, anomaly_Cretaceous.shp, anomaly_relic_patchreefs.shp, seep_anomaly_confirmed_buried_carbonate.shp, seep_anomaly_confirmed_carbonate.shp, seep_anomaly_confirmed_organisms.shp, seep_anomaly_positives.shp, seep_anomaly_positives_confirmed_gas.shp, seep_anomaly_positives_confirmed_oil.shp, seep_anomaly_positives_possible_oil.shp, seep_anomaly_confirmed_corals.shp, seep_anomaly_confirmed_hydrate.shp.To create a class of confirmed BOEM features, merge anomaly_confirmed_relic_patchreefs.shp, seep_anomaly_confirmed_organisms.shp, seep_anomaly_confirmed_corals.shp, and seep_anomaly_confirmed_hydrate.shp and assign a value of 6.To create a class of predicted BOEM features, merge the remaining extracted shapefiles and assign a value of 3.From usSEABED sediments data, use the field “gom_domnc” to extract polygons: rock (dominant and subdominant) receives a value of 2 and gravel (dominant and subdominant) receives a value of 1.From the wrecks database, extract locations having “high” and “medium” confidence (positionQuality = “high” and positionQuality = “medium”). Buffer these locations by 150 m and assign a value of 4. The buffer distance used here, and later for coral locations, follows guidance from the Army Corps of Engineers for setbacks around artificial reefs and fish havens (Riley et al. 2021).Merge artificial reef point locations from FL, AL, MS and TX. Buffer these locations by 150 m. Merge this file with the three LA artificial reef polygons and assign a value of 5.From the NOAA deep-sea coral and sponge point locations, select all points. Buffer the point locations by 150 m and assign a value of 7.From the FWC coral and hardbottom dataset polygon locations, fix geometries, reproject to EPSG=5070, then assign coral reefs a value of 7, hardbottom a value of 6, hardbottom with seagrass a value of 6, and probable hardbottom a value of 3. Hand-edit to remove an erroneous hardbottom polygon off of Matagorda Island, TX, resulting from a mistake by Sheridan and Caldwell (2002) when they digitized a DOI sediment map. This error is documented on page 6 of the Gulf of Mexico Fishery Management Council’s5-Year Review of the Final Generic Amendment Number 3.From the TNC SABMA data, fix geometries and reproject to EPSG=5070, then select all polygons with TEXT_DESC = "01. mapped hard bottom area" and assign a value of 6.Union all of the above vector datasets together—except the vector for class 6 that combines the SABMA and FL data—and assign final indicator values. Class 6 had to be handled separately due to some unexpected GIS processing issues. For overlapping polygons, this value will represent the maximum value at a given location.Clip the unioned polygon dataset to the buffered marine subregions.Convert both the unioned polygon dataset and the separate vector layer for class 6 using GDAL “rasterize”.Fill NoData cells in both rasters with zeroes and, using Extract by Mask, mask the resulting raster with the Gulf indicator extent. Adding zero values helps users better understand the extent of this indicator and to make this indicator layer perform better in online tools.Use the raster calculator to evaluate the maximum value among

CONTINENTAL SUBREGIONSThe continental portion of the Southeast Blueprint is composed of 15 Southeast states and the surrounding marine environment to the end of U.S. waters in the Atlantic Ocean and Gulf of America. We further subdivide the continental area into subregions as described below.Input DataU.S. Environmental Protection Agency (EPA) Level IV Ecoregions shapefile with state boundaries (EPA L4), accessed 12-8-2021U.S. Geological Survey (USGS)Watershed Boundary Dataset (WBD), accessed 12-8-2021: HUC4s;download the data2021 Census TIGER/Lines State boundary, accessed 12-8-2021National Oceanic and Atmospheric Administration (NOAA)U.S. Maritime Limits and Boundaries,accessed 9-20-2023Marine Ecoregions Level IIIfrom the Commission for Environmental Cooperation North American Environmental Atlas, accessed 12-8-2021Southeast Blueprint 2023 extentSoutheast Blueprint 2023 subregionsMapping StepsNote: For more details on the mapping steps, code used to create this layer is available in theSoutheast Blueprint Data Downloadunder > 6_Code. Generally, we used the following mapping steps.Inland ContinentalDo some initial grouping of the EPA ecoregions to make larger ecoregions. Usually, we grouped by Level III ecoregions; sometimes we went down to the Level IV ecoregions to make smoother, larger ecoregions.The EPA ecoregions include some “islands” where part of an ecoregion is not contiguous with the rest. Because we need contiguous subregions to use in running Zonation, identify those “islands” and assign them to the contiguous ecoregion that surrounds them. In addition, some ecoregions have long, finger-like, “peninsulas” that protrude from the ecoregion. Sometimes we assigned these to the surrounding ecoregion to make smoother edges.Union together the modified EPA ecoregions and HUC4 watershed layers and reclassify to assign subregions to unique combinations of EPA ecoregions and HUC4 watersheds.For the “islands” and “peninsulas” mentioned above, we made exceptions to the above rules and assigned those polygons to the subregion that surrounds them.Use the Census TIGER/Lines state boundaries to remove HUC4 areas that extend beyond the Southeast Blueprint extent (i.e., states not part of SECAS). This removes some coastal water areas in the Northeast United States that are outside the Southeast Blueprint area.Marine ContinentalFrom the NOAA maritime limits and boundaries layer, select the lines from the U.S. Exclusive Economic Zone (EEZ) that define the outer limit of the U.S. offshore marine waters in the Atlantic Ocean and Gulf of America.Intersect the EEZ lines with the inland continental subregions to create a large marine polygon bounded by the coastal edge of the inland subregion and the EEZ. In the vast majority of the coastline, the coastal boundaries of the inland subregions are defined by HUC4s. In a tiny area of south Texas, the coastal boundary is instead defined by EPA Level III Ecoregions, and minor hand-editing is required to make the EEZ intersect with the subregional boundary there.From the marine ecoregions layer, pull out the South Florida/Bahamian Atlantic Level 1 marine ecoregion.Use that selected South Florida ecoregion to split the bigger marine subregion created above into three distinct subregions: Gulf of America, Atlantic, and South Florida Marine.Literature CitedCommission for Environmental Cooperation. 2009. Marine Ecoregions of North America, 2008.Vector digital data.Montréal, Québec, Canada. [http://www.cec.org/north-american-environmental-atlas/marine-ecoregions-level-iii/].Flanders Marine Institute (2019). Maritime Boundaries Geodatabase: Maritime Boundaries and Exclusive Economic Zones (200NM), version 11. Available online at [https://www.marineregions.org/]. [https://doi.org/10.14284/386].Moilanen, A., I. Kohonen, P. Lehtinen, I. Kivistö, J. Jalkanen, E. Virtanen, H. Kujala.March 2024. Zonation 5 v2.0 User Manual. [https://github.com/zonationteam/Zonation5/releases/download/v2.0/manual_and_example_setups.zip].Southeast Conservation Adaptation Strategy (SECAS). 2021. South Atlantic Extent and Subregions 2021. [https://www.sciencebase.gov/catalog/item/61002b01d34ef8d7055c7db2].U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Spatial Data Collection and Products Branch. TIGER/Line Shapefile, 2021, U.S. Current State and Equivalent National. 2021. [https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-line-file.html].U.S. Environmental Protection Agency. Level IV Ecoregions of the Conterminous United States. U.S. EPA Office of Research & Development (ORD) - National Health and Environmental Effects Research Laboratory (NHEERL). Corvallis, OR. Published April 16, 2013. [https://www.epa.gov/eco-research/level-iii-and-iv-ecoregions-continental-united-states].U.S. Geological Survey (USGS). National Watershed Boundary Dataset in FileGDB 10.1 format. Published July 28, 2020. [https://www.usgs.gov/national-hydrography/watershed-boundary-dataset].CARIBBEAN SUBREGIONThe Caribbean portion of the Southeast Blueprint is composed of Puerto Rico, the U.S. Virgin Islands, and a subset of the surrounding marine environment.It was intended to cover as broad a swath as possible of the terrestrial, freshwater, and marine environments of Puerto Rico and the U.S. Virgin Islands given the data available.The Caribbean subregion serves as its own Zonation zone and is not further aggregated or subdivided.Input DataThe Nature Conservancy’s (TNC)Caribbean benthic habitat maps, accessed 12-21-2022:read a press release about the data;read a scientific journal article about the data;request to download the dataNational Oceanic and Atmospheric Administration (NOAA) National Centers for Environmental Information (NCEI) Coastal Relief Model (Vol.9 - Puerto Rico), accessed 11-22-2022NOAA U.S. Maritime Limits and Boundaries, accessed 11-22-2022NOAA Continuously Updated Shoreline Product(CUSP), accessed 1-18-2023;read a 1-page factsheet about CUSP; view and download CUSP data in theNOAA Shoreline Data Explorer (to download, select “Download CUSP by Region” and select Southeast Caribbean)LANDFIRE 2020 (version 2.2.0) Puerto Rico, US Virgin Islands: Existing Vegetation Type (EVT)Mapping StepsProcessing steps were performed in the QGIS v3.22 graphical modeler.Prepare the TNC benthic data by merging together the U.S. Virgin Islands and Puerto Rico layers into one dataset using the DGDAL Merge utility. Using the Reclassify utility, reclassify the TNC benthic classes into a single class representing the extent of the TNC benthic analysis.Prepare the coastal relief data by importing the NetCDF file using the Import NetCDF function. Reclassify the coastal relief data to assign a value of 0 to elevations ranging from -10,000 to 0 and a value of 1 to elevations ranging from 0.0001 to 1,500. This separates out all land areas, which have an elevation >0.Prepare the U.S. maritime limits and boundaries data by selecting the marine boundaries for Puerto Rico and the U.S. Virgin Islands. Select all lines with a REGION field value of “Puerto Rico and U.S. Virgin Islands”. Hand-edit the marine boundary lines to create marine boundary polygons.Fill in the holes in the marine boundary polygons, which represent land areas, using the Delete Holes utility. This creates a layer representing the combined land and sea jurisdiction of Puerto Rico and the U.S. Virgin Islands.Clip the processed coastal relief data to the Puerto Rico and the U.S. Virgin Islands land and sea jurisdiction layer using the GDAL Clip utility. This step removes data in the British Virgin Islands, creating an elevation layer that distinguishes land and sea areas within Puerto Rico and the U.S. Virgin Islands.Combine the U.S. Caribbean elevation layer with the TNC benthic data to create a preliminary extent using the Raster Boolean OR utility. The resulting layer includes all land pixels with an elevation >0 in NOAA’s coastal relief model and all sea pixels assessed in TNC’s benthic habitat layer.Convert that layer to vector using the GRASS Raster to Vector utility and extract the desired TNC benthic and land areas from the background values using Select by Attribute.The resulting layer has gaps in coverage between the land and TNC benthic ocean values. Remove holes <1,000,000 m2 (247 acres) using the Delete Holes utility.Use hand-digitizing to further modify the extent to include areas captured in the CUSP shoreline dataset. Use the CUSP line data to create a polygon covering Isla Desecheo, which was not included in the coastal relief model.Cricket Rock, Dutchcap Key, Cockroach Island, Mona Island and Isla Monita were all excluded from the coastal relief model but did have a marine extent included in the benthic habitat data. Guided by the CUSP shoreline data, hand-edit each of the polygons for these small islands to fill in the land areas.Convert the final vector dataset to raster using the GDAL Vector to Raster utility in QGIS and snap to the extent and cell size of the LANDFIRE 2020 EVT raster.Note: For more details on the mapping steps, code used to create this layer is available in theSoutheast Blueprint Data Downloadunder > 6_Code.Literature CitedFlanders Marine Institute (2019). Maritime Boundaries Geodatabase: Maritime Boundaries and Exclusive Economic Zones (200NM), version 11. Available online athttps://www.marineregions.org/. [https://doi.org/10.14284/386].LANDFIRE, Earth Resources Observation and Science Center (EROS), U.S. Geological Survey. Published August 1, 2022. LANDFIRE 2020 Existing Vegetation Type (EVT) Puerto Rico US Virgin Islands. LF 2020, raster digital data. Sioux Falls, SD. [https://www.landfire.gov].National Geophysical Data Center, 2005. U.S. Coastal Relief Model - Puerto Rico. National Geophysical Data Center, NOAA. Accessed November 22, 2022. [https://www.ncei.noaa.gov/products/coastal-relief-model].National Oceanic and Atmospheric Administration (NOAA), National Ocean