The Geodatabase to Shapefile Warning Tool examines feature classes in input file geodatabases for characteristics and data that would be lost or altered if it were transformed into a shapefile. Checks include:
1) large files (feature classes with more than 255 fields or over 2GB), 2) field names longer than 10 characters
string fields longer than 254 characters, 3) date fields with time values 4) NULL values, 5) BLOB, guid, global id, and raster field types, 6) attribute domains or subtypes, and 7) annotation or topology

The results of this inspection are written to a text file ("warning_report_[geodatabase_name]") in the directory where the geodatabase is located. A section at the top provides a list of feature classes and information about the geodatabase as a whole. The report has a section for each valid feature class that returned a warning, with a summary of possible warnings and then more details about issues found.

The tool can process multiple file geodatabases at once. A separate text file report will be created for each geodatabase. The toolbox was created using ArcGIS Pro 3.7.11.

For more information about this and other related tools, explore the Geospatial Data Curation toolkit

This ArcGIS model inserts a file name into a feature class attribute table. The tool allows an user to identify features by a field that reference the name of the original file. It is useful when an user have to merge multiple feature classes and needs to identify which layer the features come from.

There are many ways to create spatial data. In this tutorial, you'll use an editing tool to draw features on an imagery basemap. The features you create will be saved in a feature class in your project geodatabase.Estimated time: 30 minutesSoftware requirements: ArcGIS Pro

Notice: this is not 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. Heat Severity is a reclassified version of Heat Anomalies raster which is also published on this site. This data is generated from 30-meter 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 National Hydrography Dataset Plus High Resolution (NHDplus High Resolution) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US Geological Survey, NHDPlus High Resolution provides mean annual flow and velocity estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.For more information on the NHDPlus High Resolution dataset see the User’s Guide for the National Hydrography Dataset Plus (NHDPlus) High Resolution.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territoriesGeographic Extent: The Contiguous United States, Hawaii, portions of Alaska, Puerto Rico, Guam, US Virgin Islands, Northern Marianas Islands, and American SamoaProjection: Web Mercator Auxiliary Sphere Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: USGSUpdate Frequency: AnnualPublication Date: July 2022This layer was symbolized in the ArcGIS Map Viewer and while the features will draw in the Classic Map Viewer the advanced symbology will not. Prior to publication, the network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original dataset. No data values -9999 and -9998 were converted to Null values.What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS OnlineAdd this layer to a map in the map viewer. The layer or a map containing it can be used in an application. Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute.Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map.Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class.Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of the ArcGIS 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.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

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

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We converted the photointerpreted data into a GIS-usable format employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM) projection, Zone 16, using North American Datum of 1983 (NAD83). To produce a polygon vector layer for use in ArcGIS, we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format using ArcGIS (Version 9.2, © 2006 Environmental Systems Research Institute, Redlands, California). In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map attribute codes (both map class codes and physiognomic modifier codes) to the polygons, and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer of INDU and immediate environs. At this stage, the map layer has only map attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map class names, physiognomic definitions, link to NVC association and alliance codes), we produced a feature class table along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature class layers produced from this project, including vegetation sample plots, accuracy assessment sites, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.

This data includes offices where Forest Service employees work or where IT equipment is housed. There is no Personally Identifiable Information (PII) data in this dataset, nor telework locations. It includes owned, leased and shared offices. Shared offices are buildings owned or leased by another entity (i.e. a university, other federal agency, etc.) but one or more Forest Service employee(s) work at the building or IT equipment is housed at the building.Depicts the spatial locations for Office locations from the Forest Service CIO Asset Management Office. It includes owned, leased and shared offices. Data is collected, maintained and stewarded by the CIO Asset Management Office. EDW data loading tools extract the office location data from the CIO Asset Mgt. database. Latitude and longitude values are validated and then converted to spatial point data. Spatial point data and associated attributed data describing the office location are inserted into the Office Location Feature class in the Enterprise Data Warehouse. Changes to the Office Location data are checked daily by EDW data loading tools. Data is updated weekly. Data is visible at all scales and zoom levels. Metadata and Downloads.

Laatste update: 10 maart 2025In ArcGIS Pro is het mogelijk bijlagen te exporteren vanuit een feature class en deze lokaal op te slaan. Er bestaat echter geen standaard geoprocessing tool waarmee de bijlagen van alle features in één keer geëxporteerd kunnen worden. In dit artikel wordt uitgelegd hoe een script tool gebruikt kan worden om dit voor elkaar te krijgen.Voor het batch exporteren van bijlagen vanuit een feature class kan een script tool worden aangemaakt op basis van een Pythonscript. Hieronder wordt stapsgewijs beschreven hoe deze tool gemaakt en gebruikt kan worden. Deze stappen zijn ook in de volgende video zichtbaar:

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We developed 75 map classes (including map-class phases) to map the SLBE and environs. Of these 75 map classes, 67 represent natural/semi-natural vegetation types within the NVCS, four represent cultural vegetation types (agriculture and developed) within the NVCS, and four represent non-vegetation features (open water, barren land). To assign meaningful information to each polygon (e.g., map-class names, physiognomic definitions, links to NVCS types), we produced a feature-class table, along with other supportive tables, and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature-class layers produced from this project, including vegetation sample plots, accuracy assessment (AA) sites, aerial photo locations, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.

Abstract Built up area polygons represent where buildings are clustered together, such as urban areas. Layer can be used for activities such as monitoring urban grown, or responding to natural disasters. Product has been designed for AUSTopo - Australian Digital Topographic Map Series 250k. Built up area polygons designed for the AUSTopo - Australian Digital Topographic Map Series 250k. Feature class attributes include polygon area (in m2) and feature type (Builtup Area). This dataset provides valuable insights into the built environment of towns and cities, and serves as a crucial resource for urban planners, researchers, policymakers, and developers. Currency Date modified: 31 August 2023 Modification frequency: None Data extent Spatial extent North: -10.15° South: -43.44° East: 153.64° West: 113.42° Temporal extent From 1 January 2013 to 1 January 2018 Source information Catalog entry: Built Up Areas Dataset This dataset is generated from a publicly-available dataset: Bing Building Footprints, using the 'Delineate Built Up Area' tool in ArcGIS Pro. More information on the original source dataset can be found here. Lineage statement Dataset was generated by using the Bing Building Footprints of Australia (October 2020) dataset as an input. Built Up Area layer was created using the Delineate Built Up Areas tool in ArcGIS Pro in April 2023. This layer was produced as part of the update of AUSTopo - Australian Digital Topographic Map Series 250k. This dataset extracted on or before 4 SEPTEMBER 2023. This dataset has been projected from GDA2020 to Web Mercator as part of the Digital Atlas of Austalia project. Minor changes to symbology have been performed only as neccessary to meet the requirements of this project. Data dictionary All layers

Attribute name Description

Object ID Unique identifier for the area polygon

Area (sq. m) Measured area of the built-up region

Feature Type All features in this set are "Builtup Area"

SHAPE_Length Internal - length of the polygon perimeter

SHAPE_Area Internal - area of the generated polygon

Contact Geoscience Australia, clientservices@ga.gov.au

This dataset represents a water shortage vulnerability analysis performed by DWR using modified PLSS sections pulled from the Well Completion Report PLSS Section Summaries. The attribute table includes water shortage vulnerability indicators and scores from an analysis done by CA Department of Water Resources, joined to modified PLSS sections. Several relevant summary statistics from the Well Completion Reports are included in this table as well. This data is from the 2024 analysis.

Water Code Division 6 Part 2.55 Section 8 Chapter 10 (Assembly Bill 1668) effectively requires California Department of Water Resources (DWR), in consultation with other agencies and an advisory group, to identify small water suppliers and “rural communities” that are at risk of drought and water shortage. Following legislation passed in 2021 and signed by Governor Gavin Newsom, the Water Code Division 6, Section 10609.50 through 10609.80 (Senate Bill 552 of 2021) effectively requires the California Department of Water Resources to update the scoring and tool periodically in partnership with the State Water Board and other state agencies. This document describes the indicators, datasets, and methods used to construct this deliverable.  This is a statewide effort to systematically and holistically consider water shortage vulnerability statewide of rural communities, focusing on domestic wells and state small water systems serving between 4 and 14 connections. The indicators and scoring methodology will be revised as better data become available and stake-holders evaluate the performance of the indicators, datasets used, and aggregation and ranking method used to aggregate and rank vulnerability scores. Additionally, the scoring system should be adaptive, meaning that our understanding of what contributes to risk and vulnerability of drought and water shortage may evolve. This understanding may especially be informed by experiences gained while navigating responses to future droughts.”

A spatial analysis was performed on the 2020 Census Block Groups, modified PLSS sections, and small water system service areas using a variety of input datasets related to drought vulnerability and water shortage risk and vulnerability. These indicator values were subsequently rescaled and summed for a final vulnerability score for the sections and small water system service areas. The 2020 Census Block Groups were joined with ACS data to represent the social vulnerability of communities, which is relevant to drought risk tolerance and resources. These three feature datasets contain the units of analysis (modified PLSS sections, block groups, small water systems service areas) with the model indicators for vulnerability in the attribute table. Model indicators are calculated for each unit of analysis according to the Vulnerability Scoring documents provided by Julia Ekstrom (Division of Regional Assistance).

All three feature classes are DWR analysis zones that are based off existing GIS datasets. The spatial data for the sections feature class is extracted from the Well Completion Reports PLSS sections to be aligned with the work and analysis that SGMA is doing. These are not true PLSS sections, but a version of the projected section lines in areas where there are gaps in PLSS. The spatial data for the Census block group feature class is downloaded from the Census. ACS (American Communities Survey) data is joined by block group, and statistics calculated by DWR have been added to the attribute table. The spatial data for the small water systems feature class was extracted from the State Water Resources Control Board (SWRCB) SABL dataset, using a definition query to filter for active water systems with 3000 connections or less. None of these datasets are intended to be the authoritative datasets for representing PLSS sections, Census block groups, or water service areas. The spatial data of these feature classes is used as units of analysis for the spatial analysis performed by DWR.

These datasets are intended to be authoritative datasets of the scoring tools required from DWR according to Senate Bill 552. Please refer to the Drought and Water Shortage Vulnerability Scoring: California's Domestic Wells and State Smalls Systems documentation for more information on indicators and scoring. These estimated indicator scores may sometimes be calculated in several different ways, or may have been calculated from data that has since be updated. Counts of domestic wells may be calculated in different ways. In order to align with DWR SGMO's (State Groundwater Management Office) California Groundwater Live dashboards, domestic wells were calculated using the same query. This includes all domestic wells in the Well Completion Reports dataset that are completed after 12/31/1976, and have a 'RecordType' of 'WellCompletion/New/Production or Monitoring/NA'.

Please refer to the Well Completion Reports metadata for more information. The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standard version 3.4, dated September 14, 2022. DWR makes no warranties or guarantees — either expressed or implied— as to the completeness, accuracy, or correctness of the data.

DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. Comments, problems, improvements, updates, or suggestions should be forwarded to GIS@water.ca.gov.

The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses. For more information on the NHDPlus dataset see the NHDPlus v2 User Guide.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territories not including Alaska.Geographic Extent: The United States not including Alaska, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaProjection: Web Mercator Auxiliary Sphere Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: EPA and USGSUpdate Frequency: There is new new data since this 2019 version, so no updates planned in the futurePublication Date: March 13, 2019Prior to publication, the NHDPlus network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the NHDPlus Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, On or Off Network (flowlines only), Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original NHDPlus dataset. No data values -9999 and -9998 were converted to Null values for many of the flowline fields.What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS OnlineAdd this layer to a map in the map viewer. The layer is limited to scales of approximately 1:1,000,000 or larger but a vector tile layer created from the same data can be used at smaller scales to produce a webmap that displays across the full range of scales. The layer or a map containing it can be used in an application. Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute. Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map. Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class. Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of the ArcGIS 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.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

Abstract

This dataset was derived from provided by Geoscience Australia and the Queensland Department of Natural Resources and Mining. You can find a link to the source dataset in the Lineage Field in this metadata statement. The History Field in this metadata statement describes how this dataset was derived.

This dataset contains a set of feature classes containing GIS point data and attributes derived from tabular GAB_hydrochem_QCedforCSGwaters11mapNO_CONFIDENTIAL.xlsx

• GUID: (8e5cade2-c95a-45ec-9e6e-39b136d2b6d6).

The feature classes are split up according to each bore assigned aquifer extent using ArcGIS GIS processes to produce point, contour and raster data surfaces.

Prior to being converted into GIS Feature Class, the source data had been through a quality assurance and validation process to ensure the reliability of chemistry sample values as well as to check the assigned aquifer formation for each bore.

Purpose

This dataset was created to display groundwater chemistry information spatially for each individual aquifer in the Surat Basin subregion. Information may be displayed as point data, or interpolated to display as contour and raster surfaces.

Dataset History

This dataset was created by converting tabular bore data to GIS feature class point data.

The conversion was done using ArcCatalog.

For each Aquifer in the source dataset - GUID: 8e5cade2-c95a-45ec-9e6e-39b136d2b6d6 (sheets were split up by aquifer formation name) a new point Feature Class was created.

Using ArcGIS GIS processesand tools, these point feature classes were derived: pH, Alkalinity and Total Dissolved Solids (TDS) for each aquifer extent.

These point feature classes were processed using ArcGIS tools to create pH, Alkalinity and TDS (Hydrochemistry) grids.

Contour feature class were derived from the grids.

The grids and contours were clipped to its own aquifer extent.

Dataset Citation

Bioregional Assessment Programme (XXXX) MBC Aquifer Hydrochemistry v01. Bioregional Assessment Derived Dataset. Viewed 11 April 2016, http://data.bioregionalassessments.gov.au/dataset/dc1435a3-ada3-46fc-af17-d2c0d49a929b.

Dataset Ancestors

• Derived From Surface Geology of Australia, 1:1 000 000 scale, 2012 edition

• Derived From GABATLAS - Adori-Springbok Aquifer - Thickness and Extent

• Derived From Gippsland Project Boundary

• Derived From Bioregional Assessment areas v04

• Derived From GABATLAS - Evergreen-Poolowanna Aquitard and Equivalents - Thickness and Extent

• Derived From Natural Resource Management (NRM) Regions 2010

• Derived From GABATLAS - Birkhead-Walloon Aquitard - Thickness and Extent

• Derived From GABATLAS - Precipice Aquifer & Equivalents - Thickness and Extent

• Derived From GABATLAS - Rolling Downs Aquitard - Thickness and Extent

• Derived From Geoscience Australia, National Collaborative Framework Hydrochemical Characterisation Project - Surat Basin Hydrochemistry Spreadsheets

• Derived From Bioregional Assessment areas v03

• Derived From QLD Geological Digital Data - QLD Geology, Structural Framework, November 2012

• Derived From GABATLAS - Cadna-owie-Hooray Aquifer and Equivalents - Thickness and Extent

• Derived From Bioregional Assessment areas v01

• Derived From GEODATA TOPO 250K Series 3, File Geodatabase format (.gdb)

• Derived From GEODATA TOPO 250K Series 3

• Derived From NSW Catchment Management Authority Boundaries 20130917

• Derived From Victoria - Seamless Geology 2014

• Derived From GABATLAS - Hutton Aquifer and Equivalents - Thickness and Extent

• Derived From Geological Provinces - Full Extent

• Derived From Bioregional Assessment areas v02

These data represent all roads within Colorado State Parks where public access is allowed. This is a complete dataset of all public roads within Colorado State Parks and is updated as roads are built, re-routed, or abolished. Occasionally, some roads outside of the boundaries of Colorado State Parks are included to help depict the best route to access various parcels.Initial database work was completed in May 2011 by Tom Williams, under the direction of Matt Schulz, Parks GIS Coordinator. This feature class was created by combining all individual public road shapefiles from the L/parks/work/xxx/themes/roads directory of each park. First, a new standard for roads was created using the NRPA standard for roads as a background (L:\parks\standards\themes\infrastr\Roads_Geodatabase_Standards_20110308.xlsx). A set of coded value domains were created in the geodatabase that was going to house the data to ensure data quality as the data was edited in the future. The final desired fields and all possible fields from the shapefiles were added into a new feature class and then each individual park shapefile was added to the created feature class using the "Append" tool. All fields were condensed into the final desired fields and entries were changed to match the domain for that field. Some information was put into the COMMENTS field so it was not lost in the transition. NOTE FOR FURTHER EDITS: When editing, a drop down pick list will appear for each entry if the field has a domain assigned to it. You must populate using the pick list or you can fill in multiple entries at once by using the field calculator and using the code instead of the code description. Please view the Supplemental Details to see the codes and descriptions.State Forest State Park: Winter Roads were integrated, "Plowed" field = YES

Data in this Address_Points layer was loaded from the interim Building_Points_Joined layer, the result of a spatial join performed between Building_Points (centroids) and Parcels.The Building_Points layer was created on 11/ 08/2013 using the Feature to Point geoprocessing tool; input feature class was Building_Footprints_2010.Process outline:Create a copy of Building_Footprints_2010 in a local, file geodatabasePerform Feature to Point on copy of Building_Footprints_2010; result - Building_PointsPerform spatial join of Parcels to Building_Points; give each point the attribute values of the parcel within which it fallsAdd fields to Building_Points_Joined (FULLNAME, ADDRNUMSUF, ADDRCLASS) and calculate based on values in other attribute fieldsFULLNAME values are the result of a function which concacatenated, then trimmed, using STREET_DIR, STREET_NAM, STREET_TYP from the Parcels table.ADDRNUMSUF values are the result of a parsing operation in which '1/2' addresses were split from applicable HOUSE values. ADDRCLASS values resulted from a calculation based on the Parcels' BLDG_TYPE field.Data loaded to SiteAddressPoint feature class in a local gdb, sourced by Building_Points_Joined.SiteAddressPoint feature class copied to vector.GIS sdeSITEADDID calculated by GENERATE_ID value method using the DynamicValue table.On_Create rule established for SITEADDID when new features are created.Municipality calculated by INTERSECTING_FEATURE value method using the Dynamic Value table.CAPTUREMETH populated with value 'Other' to match the PointCollectionMethoddomain for that field.ZIP will require calculation when a reliable ZIP Codes layer has been secured. Questions? Contact Us

Ce modèle numérique d'altitude (MNT) a été créé à partir du jeu de données de terrain principal (MTD) de Hakai au moyen de l'outil « MNT to raster » dans ArcGIS for Desktop d'ESRI à l'aide d'une méthode d'échantillonnage Natural Neighbour. Le DEM a été créé en mode natif à une résolution de 3 m. Ce DEM a été fixé à une zone tampon à 10 m du rivage. Une combinaison de différentes altitudes autour de l'île a été utilisée pour créer le rivage.

Le MNT qui en résulte est un modèle d'élévation hydroaplati en terre nue et donc considéré comme « topographiquement complet ». Chaque pixel représente l'altitude en mètres au-dessus du niveau moyen de la mer de la terre nue à cet endroit. Le système de référence vertical est le « Système de référence géodésique vertical canadien 1928 » (CGVD28).

Hakai a produit des DEM à différentes résolutions de manière native directement à partir du MTD des données LiDAR. Pour vos recherches, veuillez utiliser le produit de résolution approprié parmi ceux produits par Hakai. Afin de maintenir l'homogénéité, il n'est pas recommandé de procéder à un suréchantillonnage ou à une mise à l'échelle supérieure à partir de produits de résolution supérieure car cela pourrait introduire et propager des erreurs de différentes grandeurs dans les analyses en cours ; veuillez utiliser des produits déjà disponibles, et si vous avez besoin d'une résolution non disponible, contactez data@hakai.org afin d'obtenir un DEM produit directement à partir du MTD.

Les DEM topographiquement complets suivants ont été produits en mode natif à partir du DTM par Hakai :

MNE topographiquement complète de 3 m. Ce produit a été utilisé pour produire les ensembles de données hydrologiques de Hakai (cours d'eau et bassins versants) DEM Topographiquement complet de 20 m. Compatible avec les mesures du couvert végétal de Hakai et les rasters associés. MNT topographiquement complet de 25 m. Compatible avec les produits de données TRIM BCGov. DEM Topographiquement complet de 30 m. Compatible avec les produits STRM.

Création du jeu de données de terrain principal

Nuages de points LiDAR issus de missions effectuées en 2012 et 2014 au-dessus de l'île Calvert où ils ont été chargés (XYZ uniquement) dans une classe d'entités ponctuelles d'une géodatabase ESRI.

Seul le sol (classe 2) renvoie l'endroit où il est chargé dans la géodatabase.

Le « jeu de données de MNT » ESRI a été créé dans la même géodatabase à l'aide des points LiDAR en tant que points de masse intégrés.

Les lacs et les étangs TEM Plus avec des valeurs d'altitude moyennes au-dessus des miroirs des plans d'eau ont été utilisés comme lignes de rupture de remplacement dur pour obtenir un hydroaplatissement.

La géométrie d'emprise minimale de toutes les étendues de fichiers LAS contigus a été utilisée comme masque de découpe souple lors de la création du jeu de données de MNT en tant que limite de projet.

Le système de coordonnées horizontales et le datum utilisés pour le jeu de données de MNT sont : UTM Zone 9 NAD1983 ; le système de référence vertical a été défini sur CGVD28. Les deux systèmes de référence correspondent au système de référence natif des nuages de points LiDAR.

L'espacement minimal des points défini pendant la création du jeu de données de MNT a été défini sur 1.