Notice: this is the latest Heat Island Severity image service.This layer contains the relative heat severity for every pixel for every city in the United States, including Alaska, Hawaii, and Puerto Rico. This 30-meter raster was derived from Landsat 8 imagery band 10 (ground-level thermal sensor) from the summer of 2023.To explore previous versions of the data, visit the links below:Heat Severity - USA 2022Heat Severity - USA 2021Heat Severity - USA 2020Heat Severity - USA 2019Federal 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 Trust for Public Land, running on the Descartes Labs platform through the Descartes Labs API for Python. The Descartes Labs platform allows for extremely fast retrieval and processing of imagery, which makes it possible to produce heat island data for all cities in the United States in a relatively short amount of time.What can you do with this layer?This layer has query, identify, and export image services available. Since it is served as an image service, it is not necessary to download the data; the service itself is data that can be used directly in any Esri geoprocessing tool that accepts raster data as input.In order to click on the image service and see the raw pixel values in a map viewer, you must be signed in to ArcGIS Online, then Enable Pop-Ups and Configure Pop-Ups.Using the Urban Heat Island (UHI) Image ServicesThe data is made available as an image service. There is a processing template applied that supplies the yellow-to-red or blue-to-red color ramp, but once this processing template is removed (you can do this in ArcGIS Pro or ArcGIS Desktop, or in QGIS), the actual data values come through the service and can be used directly in a geoprocessing tool (for example, to extract an area of interest). Following are instructions for doing this in Pro.In ArcGIS Pro, in a Map view, in the Catalog window, click on Portal. In the Portal window, click on the far-right icon representing Living Atlas. Search on the acronyms “tpl” and “uhi”. The results returned will be the UHI image services. Right click on a result and select “Add to current map” from the context menu. When the image service is added to the map, right-click on it in the map view, and select Properties. In the Properties window, select Processing Templates. On the drop-down menu at the top of the window, the default Processing Template is either a yellow-to-red ramp or a blue-to-red ramp. Click the drop-down, and select “None”, then “OK”. Now you will have the actual pixel values displayed in the map, and available to any geoprocessing tool that takes a raster as input. Below is a screenshot of ArcGIS Pro with a UHI image service loaded, color ramp removed, and symbology changed back to a yellow-to-red ramp (a classified renderer can also be used): A typical operation at this point is to clip out your area of interest. To do this, add your polygon shapefile or feature class to the map view, and use the Clip Raster tool to export your area of interest as a geoTIFF raster (file extension ".tif"). In the environments tab for the Clip Raster tool, click the dropdown for "Extent" and select "Same as Layer:", and select the name of your polygon. If you then need to convert the output raster to a polygon shapefile or feature class, run the Raster to Polygon tool, and select "Value" as the field.Other Sources of Heat Island InformationPlease see these websites for valuable information on heat islands and to learn about exciting new heat island research being led by scientists across the country:EPA’s Heat Island Resource CenterDr. Ladd Keith, University of ArizonaDr. Ben McMahan, University of Arizona Dr. Jeremy Hoffman, Science Museum of Virginia Dr. Hunter Jones, NOAA Daphne Lundi, Senior Policy Advisor, NYC Mayor's Office of Recovery and ResiliencyDisclaimer/FeedbackWith nearly 14,000 cities represented, checking each city's heat island raster for quality assurance would be prohibitively time-consuming, so 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). 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 Digital Surficial Geologic-GIS Map of the Stroudsburg Quadrangle, New Jersey and Pennsylvania is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (stro_surficial_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (stro_surficial_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (stro_surficial_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (dewa_surficial_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (dewa_surficial_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (stro_surficial_geology_metadata_faq.pdf). Please read the dewa_surficial_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Pennsylvania Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (stro_surficial_geology_metadata.txt or stro_surficial_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This layer is part of Hamilton City Council's Wastewater Dataset.If you wish to download and consume this entire dataset - click on the link for the file format(s) of your choosing: CAD (DWG) Please note that the links above may change at any time. For best practice, please refer to this page for the correct links. If any of the links are above are not functioning, please let us know at gis@hcc.govt.nz. This Wastewater dataset contains the following layers: Wastewater Abandoned Main (A wastewater main that is still in the ground, but is now disused and no longer forms part of the active network) Wastewater Abandoned Manhole (A wastewater manhole that is still in the ground but is now disused and no longer forms part of the active network) Wastewater Asbuilts (Plans showing the location and alignment of basic wastewater infrastructure as it was actually constructed on site, as provided by the contractor or their representatives Data has not yet been fully incorporated into the Council GIS or asset management system) Wastewater Main (A pipe that receives wastewater from domestic and industrial sources and directs it toward the wastewater treatment plant) Wastewater Manhole (An underground structure built over an opening in a pipe for the purpose of allowing operators or equipment access to the inside of the pipe) Wastewater Node (A junction point in a pipe It can be a structure) Wastewater Pump Station (A facility that raises wastewater from areas too low to drain by gravity, into existing pipes) Wastewater Service Line (A gravity or pressure flow pipeline connecting a building’s wastewater system to a wastewater main) Wastewater Storage Unit (A device used to contain or store effluent) Wastewater Valve (A wastewater valve is used to shut off or regulate the flow of wastewater) Hamilton City Council 3 Waters data is derived from the Council’s GIS (ArcGIS) dataset. The GIS dataset is synchronised with asset data contained in the Council’s Asset Management (IPS) database. A subset of the GIS dataset has been made available for download. This GIS dataset is currently updated weekly which in turn dynamically updates to the WLASS open data site. Any questions pertaining to this data should be directed to the City Waters Asset Information Team at CityWatersAssetInfo@hcc.govt.nz Hamilton City Council does not make any representation or give any warranty as to the accuracy or exhaustiveness of the data released for public download. Levels, locations and dimensions of works depicted in the data may not be accurate due to circumstances not notified to Council. A physical check should be made on all levels, locations and dimensions before starting design or works. Hamilton City Council shall not be liable for any loss, damage, cost or expense (whether direct or indirect) arising from reliance upon or use of any data provided, or Council's failure to provide this data. While you are free to crop, export and re-purpose the data, we ask that you attribute the Hamilton City Council and clearly state that your work is a derivative and not the authoritative data source. Please include the following statement when distributing any work derived from this data: ‘This work is derived entirely or in part from Hamilton City Council data; the provided information may be updated at any time, and may at times be out of date, inaccurate, and/or incomplete.'
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset is available for download from: Wetlands (File Geodatabase).
Wetlands in California are protected by several federal and state laws, regulations, and policies. This layer was extracted from the broader land cover raster from the CA Nature project which was recently enhanced to include a more comprehensive definition of wetland. This wetlands dataset is used as an exclusion as part of the biological planning priorities in the CEC 2023 Land-Use Screens.
This layer is featured in the CEC 2023 Land-Use Screens for Electric System Planning data viewer.
For more information about this layer and its use in electric system planning, please refer to the Land Use Screens Staff Report in the CEC Energy Planning Library.
Change Log
Version 1.1 (January 26, 2023)
Attribution-NonCommercial-ShareAlike 3.0 (CC BY-NC-SA 3.0)https://creativecommons.org/licenses/by-nc-sa/3.0/
License information was derived automatically
This land cover data set is derived from the original raster based Globcover global archive. It has been post-processed to generate a vector version at national extent with the LCCS regional legend (22 classes worldwide). The database can be analyzed in the GLCN software Advanced Database Gateway (ADG), which provides a user-friendly interface and advanced functionalities to breakdown the LCCS classes in their classifiers for further aggregations and analysis.
The data set is intended for free public access.
The shape file's attributes contain the following fields: -Area (sqm) -Perimeter (m) -ID -Gridcode (Globcover cell value) -LCCCode (unique LCCS code)
You can download a zip archive containing: -the shape file (.shp) -the ArcGis layer file with global legend (.lyr) -the ArcView 3 legend file (.avl) -the LCCS legend table (.xls)
Supplemental Information:
This land cover product is a vector version (ESRI shape) of the Globcover archive that was published in 2008 as result of an initiative launched in 2004 by the European Space Agency (ESA). Globcover is currently the most recent (2005) and resoluted (300 m) datasets on land cover globally. Given the need of this valuable information for environmental studies, natural resources management and policy formulation, through activities of the Global Land Cover Network (GLCN) programme, the Globcover has been reprocessed to generate databases at national extent that can be analyzed through the Advanced Database Gateway software (ADG) by GLCN. ADG is a cross-cutting interrogation software that allows the easy and fast recombination of land cover polygons according to the individual end-user requirements. Aggregated land cover classes can be generated not only by name, but also using the set of existing classifiers. ADG uses land cover data with a Land Cover Classification System (LCCS) legend. The ADG software is available for download on the GLCN web site at http://www.glcn.org/sof_7_en.jsp
Contact points:
Metadata Contact: FAO-Data
Resource Contact: Antonio Martucci
Data lineage:
This land cover database is provided as ESRI shape file (vector format) and derives from reprocessing the raster based global archive, Globcover. Globcover database has undergone the following process: a) vectoralization at the national extent using ESRI ArcGis (arcinfo) 9.3; b) topological reconstruction (custom AML scripts launched inside ArcGis-arcinfo 9.3); c) simplification of areas according to a minimum mapping unit of 0.1 skim (10 ha) (custom AML scripts launched inside ArcGis-arcinfo 9.3); application of the FAO/UNEP Land Cover Classification System (LCCS) legend (24 classes globally); final processing to assure full compatibility with the GLCN software Advanced Database Gateway (ADG).
Online resources:
Attribution 3.0 (CC BY 3.0)https://creativecommons.org/licenses/by/3.0/
License information was derived automatically
Abstract This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied. This dataset was sourced from the Queensland Department of Natural Resources and Mines in 2012. Information provided by the Department describes the dataset as follows: This data was originally provided on DVD and contains the converted shapefiles, layer files, raster images and project .mxd files used on the Queensland geology …Show full descriptionAbstract This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied. This dataset was sourced from the Queensland Department of Natural Resources and Mines in 2012. Information provided by the Department describes the dataset as follows: This data was originally provided on DVD and contains the converted shapefiles, layer files, raster images and project .mxd files used on the Queensland geology and structural framework map. The maps were done in ArcGIS 9.3.1 and the data stored in file geodatabases, topology created and validated. This provides greater data quality by performing topological validation on the feature's spatial relationships. For the purposes of the DVD, shapefiles were created from the file geodatabases and for MapInfo users MapInfo .tab and .wor files. The shapefiles on the DVD are a revision of the 1975 Queensland geology data, and are both are available for display, query and download on the department's online GIS application. The Queensland geology map is a digital representation of the distribution or extent of geological units within Queensland. In the GIS, polygons have a range of attributes including unit name, type of unit, age, lithological description, dominant rock type, and an abbreviated symbol for use in labelling the polygons. The lines in this dataset are a digital representation of the position of the boundaries of geological units and other linear features such as faults and folds. The lines are attributed with a description of the type of line represented. Approximately 2000 rock units were grouped into the 250 map units in this data set. The digital data was generalised and simplified from the Department's detailed geological data and was captured at 1:500 000 scale for output at 1:2 000 000 scale. In the ESRI version, a layer file is provided which presents the units in the colours and patterns used on the printed hard copy map. For Map Info users, a simplified colour palette is provided without patterns. However a georeferenced image of the hard copy map is included and can be displayed as a background in both Arc Map and Map Info. The geological framework of Queensland is classified by structural or tectonic unit (provinces and basins) in which the rocks formed. These are referred to as basins (or in some cases troughs and depressions) where the original form and structure are still apparent. Provinces (and subprovinces) are generally older basins that have been strongly tectonised and/or metamorphosed so that the original basin extent and form are no longer preserved. Note that intrusive and some related volcanic rocks that overlap these provinces and basins have not been included in this classification. The map was compiled using boundaries modified and generalised from the 1:2 000 000 Queensland Geology map (2012). Outlines of subsurface basins are also shown and these are based on data and published interpretations from petroleum exploration and geophysical surveys (seismic, gravity and magnetics). For the structural framework dataset, two versions are provided. In QLD_STRUCTURAL_FRAMEWORK, polygons are tagged with the name of the surface structural unit, and names of underlying units are imbedded in a text string in the HIERARCHY field. In QLD_STRUCTURAL_FRAMEWORK_MULTI_POLYS, the data is structured into a series of overlapping, multi-part polygons, one for each structural unit. Two layer files are provided with the ESRI data, one where units are symbolised by name. Because the dataset has been designed for units display in the order of superposition, this layer file assigns colours to the units that occur at the surface with concealed units being left uncoloured. Another layer file symbolises them by the orogen of which they are part. A similar set of palettes has been provided for Map Info. Dataset History Details on the source data can be found in the xml file associated with data layer. Data in this release *ESRI.shp and MapInfo .tab files of rock unit polygons and lines with associated layer attributes of Queensland geology *ESRI.shp and MapInfo .tab files of structural unit polygons and lines with associated layer attributes of structural framework *ArcMap .mxd and .lyr files and MapInfo .wor files containing symbology *Georeferenced Queensland geology map, gravity and magnetic images *Queensland geology map, structural framework and schematic diagram PDF files *Data supplied in geographical coordinates (latitude/longitude) based on Geocentric Datum of Australia - GDA94 Accessing the data Programs exist for the viewing and manipulation of the digital spatial data contained on this DVD. Accessing the digital datasets will require GIS software. The following GIS viewers can be downloaded from the internet. ESRI ArcExplorer can be found by a search of www.esriaustralia.com.au and MapInfo ProViewer by a search on www.pbinsight.com.au collectively ("the websites"). Metadata Metadata is contained in .htm files placed in the root folder of each vector data folder. For ArcMap users metadata for viewing in ArcCatalog is held in an .xml file with each shapefile within the ESRI Shapefile folders. Disclaimer The State of Queensland is not responsible for the privacy practices or the content of the websites and makes no statements, representations, or warranties about the content or accuracy or completeness of, any information or products contained on the websites. Despite our best efforts, the State of Queensland makes no warranties that the information or products available on the websites are free from infection by computer viruses or other contamination. The State of Queensland disclaims all responsibility and all liability (including without limitation, liability in negligence) for all expenses, losses, damages and costs you might incur as a result of accessing the websites or using the products available on the websites in any way, and for any reason. The State of Queensland has included the websites in this document as an information source only. The State of Queensland does not promote or endorse the websites or the programs contained on them in any way. WARNING: The Queensland Government and the Department of Natural Resources and Mines accept no liability for and give no undertakings, guarantees or warranties concerning the accuracy, completeness or fitness for the purposes of the information provided. The consumer must take all responsible steps to protect the data from unauthorised use, reproduction, distribution or publication by other parties. Please view the 'readme.html' and 'licence.html' file for further, more complete information Dataset Citation Geological Survey of Queensland (2012) Queensland geology and structural framework - GIS data July 2012. Bioregional Assessment Source Dataset. Viewed 07 December 2018, http://data.bioregionalassessments.gov.au/dataset/69da6301-04c1-4993-93c1-4673f3e22762.
The Digital Geologic-GIS Map of the Mammoth Cave Quadrangle, Kentucky is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (macv_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (macv_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (macv_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (maca_abli_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (maca_abli_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (macv_geology_metadata_faq.pdf). Please read the maca_abli_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (macv_geology_metadata.txt or macv_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).
Soil is the foundation of life on earth. More living things by weight live in the soil than upon it. It determines what crops we can grow, what structures we can build, what forests can take root.This layer contains the chemical soil variable nitrogen (nitrogen).Nitrogen is an essential nutrient for sustaining life on Earth. Nitrogen is a core component of amino acids, which are the building blocks of proteins, and of nucleic acids, which are the building blocks of genetic material (RNA and DNA).This layer is a general, medium scale global predictive soil layer suitable for global mapping and decision support. In many places samples of soils do not exist so this map represents a prediction of what is most likely in that location. The predictions are made in six depth ranges by soilgrids.org, funded by ISRIC based in Wageningen, Netherlands.Each 250m pixel contains a value predicted for that area by soilgrids.org from best available data worldwide. Data for nitrogen are provided at six depth ranges from the surface to 2 meters below the surface. Each variable and depth range may be accessed in the layer's multidimensional properties.Dataset SummaryPhenomenon Mapped: Total nitrogen (N) in g/kgCell Size: 250 metersPixel Type: 32 bit float, converted from online data that is 16 Bit Unsigned IntegerCoordinate System: Web Mercator Auxiliary Sphere, projected via nearest neighbor from goode's homolosine land (250m)Extent: World land area except AntarcticaVisible Scale: All scales are visibleNumber of Columns and Rows: 160300, 100498Source: Soilgrids.orgPublication Date: May 2020Data from the soilgrids.org mean predictions for nitrogen were used to create this layer. You may access nitrogen values in one of six depth ranges. To select one choose the depth variable in the multidimensional selector in your map client.Mean depth (cm)Actual depth range of data-2.50-5cm depth range-105-15cm depth range-22.515-30cm depth range-4530-60cm depth range-8060-100cm depth range-150100-200cm depth rangeWhat can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map: In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "world soils soilgrids" in the search box and browse to the layer. Select the layer then click Add to Map. In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "world soils soilgrids" in the search box, browse to the layer then click OK.In ArcGIS Pro you can use the built-in raster functions or create your own to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro.Online you can filter the layer to show subsets of the data using the filter button and the layer's built-in raster functions.This layer is part of the Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.More information about soilgrids layersAnswers to many questions may be found at soilgrids.org (ISRIC) frequently asked questions (faq) page about the data.To make this layer, Esri reprojected the expected value of ISRIC soil grids from soilgrids' source projection (goode's land WKID 54052) to web mercator projection, nearest neighbor, to facilitate online mapping. The resolution in web mercator projection is the same as the original projection, 250m. But keep in mind that the original dataset has been reprojected to make this web mercator version.This multidimensional soil collection serves the mean or expected value for each soil variable as calculated by soilgrids.org. For all other distributions of the soil variable, be sure to download the data directly from soilgrids.org. The data are available in VRT format and may be converted to other image formats within ArcGIS Pro.Accessing this layer's companion uncertainty layerBecause data quality varies worldwide, the uncertainty of the predicted value varies worldwide. A companion uncertainty layer exists for this layer which you can use to qualify the values you see in this map for analysis. Choose a variable and depth in the multidimensional settings of your map client to access the companion uncertainty layer.
This dataset has been superseded by a new edition (2nd edition) available here: https://data.gns.cri.nz/metadata/srv/eng/catalog.search#/metadata/647B1A4A-5E23-4FEE-80D0-260C6A6F49EC. This dataset contains the 1:1 000 000 faults data for New Zealand. The dataset is a product of the Geological Map of New Zealand 1: 1 000 000 project and was produced by GNS Science. It represents the most current mapping of surface or near surface fault traces for New Zealand in a single dataset at a scale of 1:1 000 000. The dataset is stored in an ESRI vector geodatabase and exported to ArcGIS Server. The dataset comprises arcs with each arc having attributes describing the type of fault, its name, age and activity, and the sense of movement and cumulative slip. It complies with the GeoSciML Portrayal standard for ShearDisplacementStructureView. The outcrop surface (map horizon) on which the features are mapped is the Earth surface. The fields required by the GeoSciML Portrayal standard were populated using the CGI Controlled Vocabulary (2012-11). The data should not be used at scales beyond that for which it was prepared. The spatial accuracy is estimated to be no better than +/- 1000 m. The dataset is available for purchase as feature classes in ESRI file geodatabase and shapefile GIS formats and freely consumable as a layer in Web Map Services and Web Feature Services from ArcGIS Server.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This layer is part of Hamilton City Council's Freshwater Dataset.If you wish to download and consume this entire dataset - click on the link for the file format(s) of your choosing: CAD (DWG)
Please note that the links above may change at any time. For best practice, please refer to this page for the correct links.
If any of the links are above are not functioning, please let us know at gis@hcc.govt.nz.
This Water (Freshwater) dataset contains the following layers:
Water Valve (A tap on a main that controls the flow of water along that main) Water Service Valve (A tap on a service line that controls the flow of water along that line) Water Service Line/Connection (A pipe that delivers water from the main to a building for consumption) Water Meter (A device that measures and displays the amount of water passing through the associated main or service line) Water Main Offset (A point along a main indicating the distance of the main from another known point such as the property boundary or kerb) Water Main Crossover Junction (The junction of one or more pipes where the pipes do not intersect - aka crossover junction) Water Main Abandoned (A water main that is still in the ground, but is now disused and no longer forms part of the active network) Water Hydrant (A tap supplying access to high-pressure water to fight fires, flush pipes and fill water trucks) Water Chamber MH (An opening/structure in a water chamber for the purpose of allowing operators or equipment access to the inside of the chamber) Water Chamber (A chamber on a water main (except bulk mains) containing operational or monitoring devices such as valves or flow meters) Water BM Chamber (A chamber on a water bulk main containing operational devices such as valves or flow meters) Water BM AV Chamber (A chamber on a water bulk main containing an air valve) Water Backflow Device (A device which prevents the accidental backflow of contaminated water into the water system) Water Asbuilts (Plans showing the location and alignment of basic water infrastructure as it was constructed on site, as provided by the contractor or their representatives. Data has not yet been fully incorporated into the Council GIS or asset management system)
Hamilton City Council 3 Waters data is derived from the Council’s GIS (ArcGIS) dataset. The GIS dataset is synchronised with asset data contained in the Council’s Asset Management (IPS) database. A subset of the GIS dataset has been made available for download.
This GIS dataset is currently updated weekly which in turn dynamically updates to the WLASS open data site. Any questions pertaining to this data should be directed to the City Waters Asset Information Team at CityWatersAssetInfo@hcc.govt.nz
Hamilton City Council does not make any representation or give any warranty as to the accuracy or exhaustiveness of the data released for public download. Levels, locations and dimensions of works depicted in the data may not be accurate due to circumstances not notified to Council. A physical check should be made on all levels, locations and dimensions before starting design or works.
Hamilton City Council shall not be liable for any loss, damage, cost or expense (whether direct or indirect) arising from reliance upon or use of any data provided, or Council's failure to provide this data.
While you are free to crop, export and re-purpose the data, we ask that you attribute the Hamilton City Council and clearly state that your work is a derivative and not the authoritative data source. Please include the following statement when distributing any work derived from this data:
‘This work is derived entirely or in part from Hamilton City Council data; the provided information may be updated at any time, and may at times be out of date, inaccurate, and/or incomplete.'
Buildings are the foundation of any 3D city; they create a realistic visual context for understanding the built environment. This rule can help you quickly create 3D buildings using your existing 2D building footprint polygons. Create buildings for your whole city or specific areas of interest. Use the buildings for context surrounding higher-detail buildings or proposed future developments.Already have existing 3D buildings? Check out the Textured Buildings from Mass by Building Type rule.What you getA Rule Package file named Building_FromFootprint_Textured_ByLandUse.rpk Rule works with a polygon layerGet startedIn ArcGIS Pro Use this rule to create Procedural Symbols, which are 3D symbols drawn on 2D features Create 3D objects (Multipatch layer) for sharing on the webShare on the web via a Scene LayerIn CityEngine:CityEngine File Navigator HelpParametersBuilding Type: Eave_Height: Height from the ground to the eave, units controlled by the Units parameterFloor_Height: Height of each floor, units controlled by the Units parameterLand_Use: Use on the land and type of building, this helps in assigning appropriate building texturesRoof_Form: Style of the building roof (Gable, Hip, Flat, Green)Roof_Height: Height from the eave to the top of the roof, units controlled by the Units parameterDisplay:Color_Override: Setting this to True will allow you to define a specific color using the Override_Color parameter, and will disable photo-texturing.Override_Color: Allows you to specify a building color using the color palette. Note: you must change the Color_Override parameter from False to True for this parameter to take effect.Transparency: Sets the amount of transparency of the feature Units:Units: Controls the measurement units in the rule: Meters | FeetNote: You can hook up the rule parameters to attributes in your data by clicking on the database icon to the right of each rule parameter. The database icon will change to blue when the rule parameter is mapped to an attribute field. The rule will automatically connect when field names match rule parameter names. Use layer files to preserve rule configurations unique to your data.For those who want to know moreThis rule is part of a the 3D Rule Library available in the Living Atlas. Discover more 3D rules to help you perform your work.Learn more about ArcGIS Pro in the Getting to Know ArcGIS Pro lesson
The Unpublished Digital Geologic-GIS Map of the French Gulch 15' Quadrangle, California is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (freg_geology.gdb), a 10.1 ArcMap (.mxd) map document (freg_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (whis_geology.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.txt) and FAQ (.pdf) formats, and a GIS readme file (whis_geology_gis_readme.pdf). Please read the whis_geology_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O'Meara (stephanie.omeara@colostate.edu; see contact information below). The data is also available as a 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. Google Earth software is available for free at: http://www.google.com/earth/index.html. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (freg_geology_metadata.txt or freg_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:62,500 and United States National Map Accuracy Standards features are within (horizontally) 31.8 meters or 104.2 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 10N, however, for the KML/KMZ format the data is projected upon export to WGS84 Geographic, the native coordinate system used by Google Earth. The data is within the area of interest of Whiskeytown National Recreation Area.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Abstract This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied. Resource contains an ArcGIS …Show full descriptionAbstract This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied. Resource contains an ArcGIS file geodatabase raster for the National Vegetation Information System (NVIS) Major Vegetation Groups - Australia-wide, present extent (FGDB_NVIS4_1_AUST_MVG_EXT). Related datasets are also included: FGDB_NVIS4_1_KEY_LAYERS_EXT - ArcGIS File Geodatabase Feature Class of the Key Datasets that make up NVIS Version 4.1 - Australia wide; and FGDB_NVIS4_1_LUT_KEY_LAYERS - Lookup table for Dataset Key Layers. This raster dataset provides the latest summary information (November 2012) on Australia's present (extant) native vegetation. It is in Albers Equal Area projection with a 100 m x 100 m (1 Ha) cell size. A comparable Estimated Pre-1750 (pre-european, pre-clearing) raster dataset is available: - NVIS4_1_AUST_MVG_PRE_ALB. State and Territory vegetation mapping agencies supplied a new version of the National Vegetation Information System (NVIS) in 2009-2011. Some agencies did not supply new data for this version but approved re-use of Version 3.1 data. Summaries were derived from the best available data in the NVIS extant theme as at June 2012. This product is derived from a compilation of data collected at different scales on different dates by different organisations. Please refer to the separate key map showing scales of the input datasets. Gaps in the NVIS database were filled by non-NVIS data, notably parts of South Australia and small areas of New South Wales such as the Curlewis area. The data represent on-ground dates of up to 2006 in Queensland, 2001 to 2005 in South Australia (depending on the region) and 2004/5 in other jurisdictions, except NSW. NVIS data was partially updated in NSW with 2001-09 data, with extensive areas of 1997 data remaining from the earlier version of NVIS. Major Vegetation Groups were identified to summarise the type and distribution of Australia's native vegetation. The classification contains different mixes of plant species within the canopy, shrub or ground layers, but are structurally similar and are often dominated by a single genus. In a mapping sense, the groups reflect the dominant vegetation occurring in a map unit where there are a mix of several vegetation types. Subdominant vegetation groups which may also be present in the map unit are not shown. For example, the dominant vegetation in an area may be mapped as dominated by eucalypt open forest, although it contains pockets of rainforest, shrubland and grassland vegetation as subdominants. The (related) Major Vegetation Subgroups represent more detail about the understorey and floristics of the Major Vegetation Groups and are available as separate raster datasets: - NVIS4_1_AUST_MVS_EXT_ALB - NVIS4_1_AUST_MVS_PRE_ALB A number of other non-vegetation and non-native vegetation land cover types are also represented as Major Vegetation Groups. These are provided for cartographic purposes, but should not be used for analyses. For further background and other NVIS products, please see the links on http://www.environment.gov.au/erin/nvis/index.html. The current NVIS data products are available from http://www.environment.gov.au/land/native-vegetation/national-vegetation-information-system. Purpose For use in Bioregional Assessment land classification analyses Dataset History NVIS Version 4.1 The input vegetation data were provided from over 100 individual projects representing the majority of Australia's regional vegetation mapping over the last 50 years. State and Territory custodians translated the vegetation descriptions from these datasets into a common attribute framework, the National Vegetation Information System (ESCAVI, 2003). Scales of input mapping ranged from 1:25,000 to 1:5,000,000. These were combined into an Australia-wide set of vector data. Non-terrestrial areas were mostly removed by the State and Territory custodians before supplying the data to the Environmental Resources Information Network (ERIN), Department of Sustainability Environment Water Population and Communities (DSEWPaC). Each NVIS vegetation description was written to the NVIS XML format file by the custodian, transferred to ERIN and loaded into the NVIS database at ERIN. A considerable number of quality checks were performed automatically by this system to ensure conformity to the NVIS attribute standards (ESCAVI, 2003) and consistency between levels of the NVIS Information Hierarchy within each description. Descriptions for non-vegetation and non-native vegetation mapping codes were transferred via CSV files. The NVIS vector (polygon) data for Australia comprised a series of jig-saw pieces, eachup to approx 500,000 polygons - the maximum tractable size for routine geoprocesssing. The spatial data was processed to conform to the NVIS spatial format (ESCAVI, 2003; other papers). Spatial processing and attribute additions were done mostly in ESRI File Geodatabases. Topology and minor geometric corrections were also performed at this stage. These datasets were then loaded into ESRI Spatial Database Engine as per the ERIN standard. NVIS attributes were then populated using Oracle database tables provided by custodians, mostly using PL/SQL Developer or in ArcGIS using the field calculator (where simple). Each spatial dataset was joined to and checked against a lookup table for the relevant State/Territory to ensure that all mapping codes in the dominant vegetation type of each polygon (NVISDSC1) had a valid lookup description, including an allocated MVG. Minor vegetation components of each map unit (NVISDSC2-6) were not checked, but could be considered mostly complete. Each NVIS vegetation description was allocated to a Major Vegetation Group (MVG) by manual interpretation at ERIN. The Australian Natural Resources Atlas (http://www.anra.gov.au/topics/vegetation/pubs/native_vegetation/vegfsheet.html) provides detailed descriptions of most Major Vegetation Groups. Three new MVGs were created for version 4.1 to better represent open woodland formations and forests (in the NT) with no further data available. NVIS vegetation descriptions were reallocated into these classes, if appropriate: Unclassified Forest Other Open Woodlands Mallee Open Woodlands and Sparse Mallee Shublands (Thus there are a total of 33 MVGs existing as at June 2012). Data values defined as cleared or non-native by data custodians were attributed specific MVG values such as 25 - Cleared or non native, 27 - naturally bare, 28 - seas & estuaries, and 99 - Unknown. As part of the process to fill gaps in NVIS, the descriptive data from non-NVIS sources was also referenced in the NVIS database, but with blank vegetation descriptions. In general. the gap-fill data comprised (a) fine scale (1:250K or better) State/Territory vegetation maps for which NVIS descriptions were unavailable and (b) coarse-scale (1:1M) maps from Commonwealth and other sources. MVGs were then allocated to each description from the available desciptions in accompanying publications and other sources. Parts of New South Wales, South Australia, QLD and the ACT have extensive areas of vector "NoData", thus appearing as an inland sea. The No Data areas were dealt with differently by state. In the ACT and SA, the vector data was 'gap-filled' and attributed using satellite imagery as a guide prior to rasterising. Most of these areas comprised a mixture of MVG 24 (inland water) and 25 (cleared), and in some case 99 (Unknown). The NSW & QLD 'No Data' areas were filled using a raster mask to fill the 'holes'. These areas were attributed with MVG 24, 26 (water & unclassified veg), MVG 25 (cleared); or MVG 99 Unknown/no data, where these areas were a mixture of unknown proportions. Each spatial dataset with joined lookup table (including MVG_NUMBER linked to NVISDSC1) was exported to a File Geodatabase as a feature class. These were reprojected into Albers Equal Area projection (Central_Meridian: 132.000000, Standard_Parallel_1: -18.000000, Standard_Parallel_2: -36.000000, Linear Unit: Meter (1.000000), Datum GDA94, other parameters 0). Each feature class was then rasterised to a 100m raster with extents to a multiple of 1000 m, to ensure alignment. In some instances, areas of 'NoData' had to be modelled in raster. For example, in NSW where non-native areas (cleared, water bodies etc) have not been mapped. The rasters were then merged into a 'state wide' raster. State rasters were then merged into this 'Australia wide' raster dataset. November 2012 Corrections Closer inspection of the original 4.1 MVG Extant raster dataset highlighted some issues with the raster creation process which meant that raster pixels in some areas did not align as intended. These were corrected, and the new properly aligned rasters released in November 2012. Dataset Citation Department of the Environment (2012) Australia - Present Major Vegetation Groups - NVIS Version 4.1 (Albers 100m analysis product). Bioregional Assessment Source Dataset. Viewed 10 July 2017, http://data.bioregionalassessments.gov.au/dataset/57c8ee5c-43e5-4e9c-9e41-fd5012536374.
This layer is part of Hamilton City Council's Freshwater Dataset.If you wish to download and consume this entire dataset - click on the link for the file format(s) of your choosing: FGDB/File Geodatabase Shapefile Excel CAD (DWG) Please note that the links above may change at any time. For best practice, please refer to this page for the correct links. If any of the links are above are not functioning, please let us know at gis@hcc.govt.nz. This Water (Freshwater) dataset contains the following layers: Water Valve (A tap on a main that controls the flow of water along that main) Water Service Valve (A tap on a service line that controls the flow of water along that line) Water Service Line/Connection (A pipe that delivers water from the main to a building for consumption) Water Meter (A device that measures and displays the amount of water passing through the associated main or service line) Water Main Offset (A point along a main indicating the distance of the main from another known point such as the property boundary or kerb) Water Main Crossover Junction (The junction of one or more pipes where the pipes do not intersect - aka crossover junction) Water Main Abandoned (A water main that is still in the ground, but is now disused and no longer forms part of the active network) Water Hydrant (A tap supplying access to high-pressure water to fight fires, flush pipes and fill water trucks) Water Chamber MH (An opening/structure in a water chamber for the purpose of allowing operators or equipment access to the inside of the chamber) Water Chamber (A chamber on a water main (except bulk mains) containing operational or monitoring devices such as valves or flow meters) Water BM Chamber (A chamber on a water bulk main containing operational devices such as valves or flow meters) Water BM AV Chamber (A chamber on a water bulk main containing an air valve) Water Backflow Device (A device which prevents the accidental backflow of contaminated water into the water system) Water Asbuilts (Plans showing the location and alignment of basic water infrastructure as it was constructed on site, as provided by the contractor or their representatives. Data has not yet been fully incorporated into the Council GIS or asset management system) Hamilton City Council 3 Waters data is derived from the Council’s GIS (ArcGIS) dataset. The GIS dataset is synchronised with asset data contained in the Council’s Asset Management (IPS) database. A subset of the GIS dataset has been made available for download. This GIS dataset is currently updated weekly which in turn dynamically updates to the WLASS open data site. Any questions pertaining to this data should be directed to the City Waters Asset Information Team at CityWatersAssetInfo@hcc.govt.nz Hamilton City Council does not make any representation or give any warranty as to the accuracy or exhaustiveness of the data released for public download. Levels, locations and dimensions of works depicted in the data may not be accurate due to circumstances not notified to Council. A physical check should be made on all levels, locations and dimensions before starting design or works. Hamilton City Council shall not be liable for any loss, damage, cost or expense (whether direct or indirect) arising from reliance upon or use of any data provided, or Council's failure to provide this data. While you are free to crop, export and re-purpose the data, we ask that you attribute the Hamilton City Council and clearly state that your work is a derivative and not the authoritative data source. Please include the following statement when distributing any work derived from this data: ‘This work is derived entirely or in part from Hamilton City Council data; the provided information may be updated at any time, and may at times be out of date, inaccurate, and/or incomplete.'
The Digital Geomorphic-GIS Map of Cumberland Island National Seashore, Georgia is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (cuis_geomorphology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro 3.X map file (.mapx) file (cuis_geomorphology.mapx) and individual Pro 3.X layer (.lyrx) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (cuis_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (cuis_geomorphology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (cuis_geomorphology_metadata_faq.pdf). Please read the cuis_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: RWParkinson Inc. and MDA Information Systems, Inc. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (cuis_geomorphology_metadata.txt or cuis_geomorphology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:60,000 and United States National Map Accuracy Standards features are within (horizontally) 30.5 meters or 100 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS Pro, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).
The Digital Bedrock Geologic-GIS Map of Stones River National Battlefield and Vicinity, Tennessee is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (stri_bedrock_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (stri_bedrock_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (stri_bedrock_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (stri_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (stri_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (stri_bedrock_geology_metadata_faq.pdf). Please read the stri_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Tennessee Division of Geology. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (stri_bedrock_geology_metadata.txt or stri_bedrock_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual _location as presented by this dataset. Users of this data should thus not assume the _location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).
The Digital Geologic-GIS Map of the Mud Creek Quadrangle, Colorado is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (mucr_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (mucr_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (yuho_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (yuho_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (mucr_geology_metadata_faq.pdf). Please read the yuho_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (mucr_geology_metadata.txt or mucr_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS Pro, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).
The Digital Geologic-GIS Map of Mammoth Cave National Park and Vicinity, Kentucky is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (maca_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (maca_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (maca_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (maca_abli_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (maca_abli_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (maca_geology_metadata_faq.pdf). Please read the maca_abli_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey and Kentucky Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (maca_geology_metadata.txt or maca_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual _location as presented by this dataset. Users of this data should thus not assume the _location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).
The Unpublished Digital Geologic-GIS Map of the West Shasta Copper-Zinc District, California is composed of GIS data layers and GIS tables in a 10.1 file geodatabase (wscz_geology.gdb), a 10.1 ArcMap (.mxd) map document (wscz_geology.mxd), individual 10.1 layer (.lyr) files for each GIS data layer, an ancillary map information document (whis_geology_gis_readme.pdf) which contains source map unit descriptions, as well as other source map text, figures and tables, metadata in FGDC text (.txt) and FAQ (.pdf) formats, and a GIS readme file (whis_geology_gis_readme.pdf). Please read the whis_geology_gis_readme.pdf for information pertaining to the proper extraction of the file geodatabase and other map files. To request GIS data in ESRI 10.1 shapefile format contact Stephanie O'Meara (stephanie.omeara@colostate.edu; see contact information below). The data is also available as a 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. Google Earth software is available for free at: http://www.google.com/earth/index.html. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (wscz_geology_metadata.txt or wscz_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual _location as presented by this dataset. Users of this data should thus not assume the _location of features is exactly where they are portrayed in Google Earth, ArcGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data projection is NAD83, UTM Zone 10N, however, for the KML/KMZ format the data is projected upon export to WGS84 Geographic, the native coordinate system used by Google Earth. The data is within the area of interest of Whiskeytown National Recreation Area.
Notice: this is not the latest Heat Island Severity image service. For 2023 data, visit https://tpl.maps.arcgis.com/home/item.html?id=db5bdb0f0c8c4b85b8270ec67448a0b6. This layer contains the relative heat severity for every pixel for every city in the United States, including Alaska, Hawaii, and Puerto Rico. This 30-meter raster was derived from Landsat 8 imagery band 10 (ground-level thermal sensor) from the summer of 2022, patched with data from 2021 where necessary.Federal statistics over a 30-year period show extreme heat is the leading cause of weather-related deaths in the United States. Extreme heat exacerbated by urban heat islands can lead to increased respiratory difficulties, heat exhaustion, and heat stroke. These heat impacts significantly affect the most vulnerable—children, the elderly, and those with preexisting conditions.The purpose of this layer is to show where certain areas of cities are hotter than the average temperature for that same city as a whole. Severity is measured on a scale of 1 to 5, with 1 being a relatively mild heat area (slightly above the mean for the city), and 5 being a severe heat area (significantly above the mean for the city). The absolute heat above mean values are classified into these 5 classes using the Jenks Natural Breaks classification method, which seeks to reduce the variance within classes and maximize the variance between classes. Knowing where areas of high heat are located can help a city government plan for mitigation strategies.This dataset represents a snapshot in time. It will be updated yearly, but is static between updates. It does not take into account changes in heat during a single day, for example, from building shadows moving. The thermal readings detected by the Landsat 8 sensor are surface-level, whether that surface is the ground or the top of a building. Although there is strong correlation between surface temperature and air temperature, they are not the same. We believe that this is useful at the national level, and for cities that don’t have the ability to conduct their own hyper local temperature survey. Where local data is available, it may be more accurate than this dataset. Dataset SummaryThis dataset was developed using proprietary Python code developed at The Trust for Public Land, running on the Descartes Labs platform through the Descartes Labs API for Python. The Descartes Labs platform allows for extremely fast retrieval and processing of imagery, which makes it possible to produce heat island data for all cities in the United States in a relatively short amount of time.What can you do with this layer?This layer has query, identify, and export image services available. Since it is served as an image service, it is not necessary to download the data; the service itself is data that can be used directly in any Esri geoprocessing tool that accepts raster data as input.In order to click on the image service and see the raw pixel values in a map viewer, you must be signed in to ArcGIS Online, then Enable Pop-Ups and Configure Pop-Ups.Using the Urban Heat Island (UHI) Image ServicesThe data is made available as an image service. There is a processing template applied that supplies the yellow-to-red or blue-to-red color ramp, but once this processing template is removed (you can do this in ArcGIS Pro or ArcGIS Desktop, or in QGIS), the actual data values come through the service and can be used directly in a geoprocessing tool (for example, to extract an area of interest). Following are instructions for doing this in Pro.In ArcGIS Pro, in a Map view, in the Catalog window, click on Portal. In the Portal window, click on the far-right icon representing Living Atlas. Search on the acronyms “tpl” and “uhi”. The results returned will be the UHI image services. Right click on a result and select “Add to current map” from the context menu. When the image service is added to the map, right-click on it in the map view, and select Properties. In the Properties window, select Processing Templates. On the drop-down menu at the top of the window, the default Processing Template is either a yellow-to-red ramp or a blue-to-red ramp. Click the drop-down, and select “None”, then “OK”. Now you will have the actual pixel values displayed in the map, and available to any geoprocessing tool that takes a raster as input. Below is a screenshot of ArcGIS Pro with a UHI image service loaded, color ramp removed, and symbology changed back to a yellow-to-red ramp (a classified renderer can also be used): A typical operation at this point is to clip out your area of interest. To do this, add your polygon shapefile or feature class to the map view, and use the Clip Raster tool to export your area of interest as a geoTIFF raster (file extension ".tif"). In the environments tab for the Clip Raster tool, click the dropdown for "Extent" and select "Same as Layer:", and select the name of your polygon. If you then need to convert the output raster to a polygon shapefile or feature class, run the Raster to Polygon tool, and select "Value" as the field.Other Sources of Heat Island InformationPlease see these websites for valuable information on heat islands and to learn about exciting new heat island research being led by scientists across the country:EPA’s Heat Island Resource CenterDr. Ladd Keith, University of ArizonaDr. Ben McMahan, University of Arizona Dr. Jeremy Hoffman, Science Museum of Virginia Dr. Hunter Jones, NOAA Daphne Lundi, Senior Policy Advisor, NYC Mayor's Office of Recovery and ResiliencyDisclaimer/FeedbackWith nearly 14,000 cities represented, checking each city's heat island raster for quality assurance would be prohibitively time-consuming, so The Trust for Public Land checked a statistically significant sample size for data quality. The sample passed all quality checks, with about 98.5% of the output cities error-free, but there could be instances where the user finds errors in the data. These errors will most likely take the form of a line of discontinuity where there is no city boundary; this type of error is caused by large temperature differences in two adjacent Landsat scenes, so the discontinuity occurs along scene boundaries (see figure below). The Trust for Public Land would appreciate feedback on these errors so that version 2 of the national UHI dataset can be improved. Contact Dale.Watt@tpl.org with feedback.
Notice: this is the latest Heat Island Severity image service.This layer contains the relative heat severity for every pixel for every city in the United States, including Alaska, Hawaii, and Puerto Rico. This 30-meter raster was derived from Landsat 8 imagery band 10 (ground-level thermal sensor) from the summer of 2023.To explore previous versions of the data, visit the links below:Heat Severity - USA 2022Heat Severity - USA 2021Heat Severity - USA 2020Heat Severity - USA 2019Federal 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 Trust for Public Land, running on the Descartes Labs platform through the Descartes Labs API for Python. The Descartes Labs platform allows for extremely fast retrieval and processing of imagery, which makes it possible to produce heat island data for all cities in the United States in a relatively short amount of time.What can you do with this layer?This layer has query, identify, and export image services available. Since it is served as an image service, it is not necessary to download the data; the service itself is data that can be used directly in any Esri geoprocessing tool that accepts raster data as input.In order to click on the image service and see the raw pixel values in a map viewer, you must be signed in to ArcGIS Online, then Enable Pop-Ups and Configure Pop-Ups.Using the Urban Heat Island (UHI) Image ServicesThe data is made available as an image service. There is a processing template applied that supplies the yellow-to-red or blue-to-red color ramp, but once this processing template is removed (you can do this in ArcGIS Pro or ArcGIS Desktop, or in QGIS), the actual data values come through the service and can be used directly in a geoprocessing tool (for example, to extract an area of interest). Following are instructions for doing this in Pro.In ArcGIS Pro, in a Map view, in the Catalog window, click on Portal. In the Portal window, click on the far-right icon representing Living Atlas. Search on the acronyms “tpl” and “uhi”. The results returned will be the UHI image services. Right click on a result and select “Add to current map” from the context menu. When the image service is added to the map, right-click on it in the map view, and select Properties. In the Properties window, select Processing Templates. On the drop-down menu at the top of the window, the default Processing Template is either a yellow-to-red ramp or a blue-to-red ramp. Click the drop-down, and select “None”, then “OK”. Now you will have the actual pixel values displayed in the map, and available to any geoprocessing tool that takes a raster as input. Below is a screenshot of ArcGIS Pro with a UHI image service loaded, color ramp removed, and symbology changed back to a yellow-to-red ramp (a classified renderer can also be used): A typical operation at this point is to clip out your area of interest. To do this, add your polygon shapefile or feature class to the map view, and use the Clip Raster tool to export your area of interest as a geoTIFF raster (file extension ".tif"). In the environments tab for the Clip Raster tool, click the dropdown for "Extent" and select "Same as Layer:", and select the name of your polygon. If you then need to convert the output raster to a polygon shapefile or feature class, run the Raster to Polygon tool, and select "Value" as the field.Other Sources of Heat Island InformationPlease see these websites for valuable information on heat islands and to learn about exciting new heat island research being led by scientists across the country:EPA’s Heat Island Resource CenterDr. Ladd Keith, University of ArizonaDr. Ben McMahan, University of Arizona Dr. Jeremy Hoffman, Science Museum of Virginia Dr. Hunter Jones, NOAA Daphne Lundi, Senior Policy Advisor, NYC Mayor's Office of Recovery and ResiliencyDisclaimer/FeedbackWith nearly 14,000 cities represented, checking each city's heat island raster for quality assurance would be prohibitively time-consuming, so 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). 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.