You will learn to work with ArcPy, the Esri-developed site package that integrates Python scripts into ArcGIS Desktop.Goals Create Python scripts to perform geoprocessing tasks. Access lists of datasets and loop through lists to test for a condition. Create dynamic scripts that allow users to interactively specify their own parameter values. Create tools to share your Python scripts.

This is the Statewide seamless coverage layer for LBRS Address Points.  These LBRS datasets (Address Points and Road Centerlines) were derived from multiple sources. Those sources include counties that contract DDTI for continual maintenance of their LBRS Data (see list below) DDTI’s ODOT LBRS Road Centerline update of 2023 (counties include Clermont, Coshocton, Darke, Lake, Knox, Jefferson, Monroe, Perry, Scioto, and Summit). Additionally, other County’s data were obtained directly from their respective GIS website/portal (IE: Hamilton County: www.cagis.org - /Opendata/), or by contacting/requesting the data from each individual County directly. Once the individual datasets were gathered, analysis had to be performed to ensure each followed the proper attribution schema. Individual County’s that had non-compliant datasets were analyzed using GIS Geoprocessing tools and custom-built GIS Modeling and appended into a Master GIS Geodatabase (LBRS Attribution Schema Compliant). This data is hosted and updated on a bi-annual basis, typically in the summer (June/July) and again in the winter (December/Jan) in an attempt to maintain the most current/up to date statewide datasets for public use. List of DDTI Maintained County’s: Adams, Allen, Ashland, Ashtabula, Athens, Brown, Carroll, Champaign, Columbiana, Crawford, Defiance, Erie, Fayette, Guernsey, Hancock, Hardin, Harrison, Hocking, Huron, Jackson, Lucas, Marion, Meigs, Miami, Monroe, Morgan, Morrow, Noble, Ottawa, Paulding, Pickaway, Pike, Portage, Preble, Putnam, Ross, Sandusky, Shelby, Trumbull, Van Wert, Vinton, Washington, Wayne, Williams, Wood, Wyandot This dataset is from Winter 2023

Dataset description-br /- This dataset is a recalculation of the Copernicus 2015 high resolution layer (HRL) of imperviousness density data (IMD) at different spatial/territorial scales for the case studies of Barcelona and Milan. The selected spatial/territorial scales are the following: * a) Barcelona city boundaries * b) Barcelona metropolitan area, Àrea Metropolitana de Barcelona (AMB) * c) Barcelona greater city (Urban Atlas) * d) Barcelona functional urban area (Urban Atlas) * e) Milan city boundaries * f) Milan metropolitan area, Piano Intercomunale Milanese (PIM) * g) Milan greater city (Urban Atlas) * h) Milan functional urban area (Urban Atlas)-br /- In each of the spatial/territorial scales listed above, the number of 20x20mt cells corresponding to each of the 101 values of imperviousness (0-100% soil sealing: 0% means fully non-sealed area; 100% means fully sealed area) is provided, as well as the converted measure into squared kilometres (km2). -br /- -br /- -br /- Dataset composition-br /- The dataset is provided in .csv format and is composed of: -br /- _IMD15_BCN_MI_Sources.csv_: Information on data sources -br /- _IMD15_BCN.csv_: This file refers to the 2015 high resolution layer of imperviousness density (IMD) for the selected territorial/spatial scales in Barcelona: * a) Barcelona city boundaries (label: bcn_city) * b) Barcelona metropolitan area, Àrea metropolitana de Barcelona (AMB) (label: bcn_amb) * c) Barcelona greater city (Urban Atlas) (label: bcn_grc) * d) Barcelona functional urban area (Urban Atlas) (label: bcn_fua)-br /- _IMD15_MI.csv_: This file refers to the 2015 high resolution layer of imperviousness density (IMD) for the selected territorial/spatial scales in Milan: * e) Milan city boundaries (label: mi_city) * f) Milan metropolitan area, Piano intercomunale milanese (PIM) (label: mi_pim) * g) Milan greater city (Urban Atlas) (label: mi_grc) * h) Milan functional urban area (Urban Atlas) (label: mi_fua)-br /- _IMD15_BCN_MI.mpk_: the shareable project in Esri ArcGIS format including the HRL IMD data in raster format for each of the territorial boundaries as specified in letter a)-h). -br /- Regarding the territorial scale as per letter f), the list of municipalities included in the Milan metropolitan area in 2016 was provided to me in 2016 from a person working at the PIM. -br /- In the IMD15_BCN.csv and IMD15_MI.csv, the following columns are included: * Level: the territorial level as defined above (a)-d) for Barcelona and e)-h) for Milan); * Value: the 101 values of imperviousness density expressed as a percentage of soil sealing (0-100%: 0% means fully non-sealed area; 100% means fully sealed area); * Count: the number of 20x20mt cells corresponding to a certain percentage of soil sealing or imperviousness; * Km2: the conversion of the 20x20mt cells into squared kilometres (km2) to facilitate the use of the dataset.-br /- -br /- -br /- Further information on the Dataset-br /- This dataset is the result of a combination between different databases of different types and that have been downloaded from different sources. Below, I describe the main steps in data management that resulted in the production of the dataset in an Esri ArcGIS (ArcMap, Version 10.7) project.-br /- 1. The high resolution layer (HRL) of the imperviousness density data (IMD) for 2015 has been downloaded from the official website of Copernicus. At the time of producing the dataset (April/May 2021), the 2018 version of the IMD HRL database was not yet validated, so the 2015 version was chosen instead. The type of this dataset is raster. 2. For both Barcelona and Milan, shapefiles of their administrative boundaries have been downloaded from official sources, i.e. the ISTAT (Italian National Statistical Institute) and the ICGC (Catalan Institute for Cartography and Geology). These files have been reprojected to match the IMD HRL projection, i.e. ETRS 1989 LAEA. 3. Urban Atlas (UA) boundaries for the Greater Cities (GRC) and Functional Urban Areas (FUA) of Barcelona and Milan have been checked and reconstructed in Esri ArcGIS from the administrative boundaries files by using a Eurostat correspondence table. This is because at the time of the dataset creation (April/May 2021), the 2018 Urban Atlas shapefiles for these two cities were not fully updated or validated on the Copernicus Urban Atlas website. Therefore, I had to re-create the GRC and FUA boundaries by using the Eurostat correspondence table as an alternative (but still official) data source. The use of the Eurostat correspondence table with the codes and names of municipalities was also useful to detect discrepancies, basically stemming from changes in municipality names and codes and that created inconsistent spatial features. When detected, these discrepancies have been checked with the ISTAT and ICGC offices in charge of producing Urban Atlas data before the final GRC and FUA boundaries were defined.-br /- Steps 2) and 3) were the most time consuming, because they required other tools to be used in Esri ArcGIS, like spatial joins and geoprocessing tools for shapefiles (in particular dissolve and area re-calculator in editing sessions) for each of the spatial/territorial scales as indicated in letters a)-h). -br /- Once the databases for both Barcelona and Milan as described in points 2) and 3) were ready (uploaded in Esri ArcGIS, reprojected and their correctness checked), they have been ‘crossed’ (i.e. clipped) with the IMD HRL as described in point 1) and a specific raster for each territorial level has been calculated. The procedure in Esri ArcGIS was the following: * Clipping: Arctoolbox - Data management tools - Raster - Raster Processing - Clip. The ‘input’ file is the HRL IMD raster file as described in point 1) and the ‘output’ file is each of the spatial/territorial files. The option "Use Input Features for Clipping Geometry (optional)” was selected for each of the clipping. * Delete and create raster attribute table: Once the clipping has been done, the raster has to be recalculated first through Arctoolbox - Data management tools - Raster - Raster properties - Delete Raster Attribute Table and then through Arctoolbox - Data management tools - Raster - Raster properties - Build Raster Attribute Table; the "overwrite" option has been selected. -br /- -br /- Other tools used for the raster files in Esri ArcGIS have been the spatial analyst tools (in particular, Zonal - Zonal Statistics). As an additional check, the colour scheme of each of the newly created raster for each of the spatial/territorial attributes as per letters a)-h) above has been changed to check the consistency of its overlay with the original HRL IMD file. However, a perfect match between the shapefiles as per letters a)-h) and the raster files could not be achieved since the raster files are composed of 20x20mt cells.-br /- The newly created attribute tables of each of the raster files have been exported and saved as .txt files. These .txt files have then been copied in the excel corresponding to the final published dataset.

Soils and soil moisture greatly influence the water cycle and have impacts on runoff, flooding and agriculture. Soil type and soil particle composition (sand, clay, silt) affect soil moisture and the ability of the soil to retain water. Soil moisture is also affected by levels of evaporation and plant transpiration, potentially leading to near dryness and eventual drought.Measuring and monitoring soil moisture can ensure the fitness of your crops and help predict or prepare for flash floods and drought. The GLDAS soil moisture data is useful for modeling these scenarios and others, but only at global scales. Dataset SummaryThe GLDAS Soil Moisture layer is a time-enabled image service that shows average monthly soil moisture from 2000 to the present at four different depth levels. It is calculated by NASA using the Noah land surface model, run at 0.25 degree spatial resolution using satellite and ground-based observational data from the Global Land Data Assimilation System (GLDAS-1). The model is run with 3-hourly time steps and aggregated into monthly averages. Review the complete list of model inputs, explore the output data (in GRIB format), and see the full Hydrology Catalog for all related data and information!What can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS Desktop. The GLDAS soil moisture data is useful for modeling, but only at global scales. Time: This is a time-enabled layer. It shows the total evaporative loss during the map's time extent, or if time animation is disabled, a time range can be set using the layer's multidimensional settings. The map shows the sum of all months in the time extent. Minimum temporal resolution is one month; maximum is one year.Depth: This layer has four depth levels. By default they are summed, but you can view each using the multidimensional filter. You must disable time animation on the layer before using its multidimensional filter. It is also possible to toggle between depth layers using raster functions, accessed through the Image Display tab.Important: You must switch from the cartographic renderer to the analytic renderer in the processing template tab in the layer properties window before using this layer as an input to geoprocessing tools.This layer has query, identify, and export image services available. This layer is part of a larger collection of earth observation maps that you can use to perform a wide variety of mapping and analysis tasks.The Living Atlas of the World provides an easy way to explore the earth observation layers and many other beautiful and authoritative maps on hundreds of topics.Geonet is a good resource for learning more about earth observations layers and the Living Atlas of the World. Follow the Living Atlas on GeoNet.

Purpose and intended use - This dataset consists of information about subdivisions in Arizona and their various water providers. For general purposes, the list is intended to determine the extent of issued determinations and could be used as a starting point to estimate associated demands with issued determinations in a given area. Please note that the dataset may not necessarily yield an accurate list of committed demands for the purposes of determining physical availability of groundwater in any given area. The users of this information are strongly advised to contact the Office of Assured and Adequate Water Supply for assistance in accurately determining existing and projected water demands in a given area.Data creation methodologies, processing, and quality - This dataset was created based on the township, range, and section information from Arizona Public Land Survey System (PLSS). Tabular data associated with Assured and Adequate Water Supply (AAWS) issued determinations database were joined to individual section boundaries using available geo-processing tools within GIS. This feature class is a dissolved version of feature class LIB.aawsIssuedDeterminationData limitations - Please be aware that much of this database is legacy information and may not reflect the complete record of decision. Some information herein dates back to 1973, which predates the Department’s creation. The information electronically recorded was collected under various statutory and regulatory rule frameworks since the establishment of the Department in 1980. Thus, it is not always reflective of the information needed for the current application process. The source of the database is based on cadastral information and not necessarily the Universal Transverse Mercator (UTM) coordinates. While the department continues to correct the database as errors and omissions are detected, the entire dataset has not been fully scrutinized and may contain errors or omissions. ADWR staff continue to work to improve the accuracy of features within this dataset, however ADWR makes no claims regarding the accuracy of the dataset.Currency - This data is synced daily with ADWR’s business database as new determinations are issued.Contact - AAWS Section Manager, Water Planning and Permitting Division, (602)771-8599Use limitations - Please refer to ADWR Data Disclaimer.Attribute information - WATER_PROVIDERTOTAL_DEMANDSYSTEM_NAMESWSUBDIVISIONSUBBASINSHAPE.LENSHAPE.AREASHAPERCVD_DTOBJECTIDNO_OF_LOTSHYDRO_STUDY_AVAILABLEGWISSUED_DTFILESTATUSFILE_TYPEFILE_NOF2ND_PROVIDERF100_YREFFLUENTCOUNTYCOLORADO RIVERCAPAMA

When precipitation falls on the surface of the Earth, much of it is captured in storage (e.g. lakes, aquifers, soil moisture, snowpack, and vegetation). Precipitation that exceeds the storage capacity of the landscape becomes runoff, which flows into river systems. Overland flow is the most visible form of runoff, causing erosion and flash floods, but subsurface flow is the larger contributor in many watersheds. Subsurface flow can emerge on the surface through springs, or more commonly, seep into rivers and lakes through their banks. In urban areas, impervious land cover drastically increases the amount of surface runoff generated, which sweeps trash and urban debris into waterways and increases the likelihood and severity of flash floods. In agricultural areas, surface or subsurface runoff can carry excess salts and nutrients, especially nitrogen and phosphorus. This map contains a historical record showing the amount of runoff generated each month from March 2000 to present. It is reported in millimeters, so multiply by a surface area to calculate the total volume of runoff.Dataset SummaryThe GLDAS Runoff layer is a time-enabled image service that shows average monthly runoff from 2000 to the present measured in millimeters. It is calculated by NASA using the Noah land surface model, run at 0.25 degree spatial resolution using satellite and ground-based observational data from the Global Land Data Assimilation System (GLDAS-1). The model is run with 3-hourly time steps and aggregated into monthly averages. Review the complete list of model inputs, explore the output data (in GRIB format), and see the full Hydrology Catalog for all related data and information!What can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS Desktop. t is useful for scientific modeling, but only at global scales.Time: This is a time-enabled layer. It shows the total runoff generated during the map's time extent, or if time animation is disabled, a time range can be set using the layer's multidimensional filter. The map shows the sum of all months in the time extent. Minimum temporal resolution is one month; maximum is one year.Variables: This layer has two variables: surface flow and subsurface flow. By default the two are summed, but you can view either by itself using the multidimensional filter. You must disable time animation on the layer before using its multidimensional filter.Important: You must switch from the cartographic renderer to the analytic renderer in the processing template tab in the layer properties window before using this layer as an input to geoprocessing tools.This layer has query, identify, and export image services available. This layer is part of a larger collection of earth observation maps that you can use to perform a wide variety of mapping and analysis tasks.The Living Atlas of the World provides an easy way to explore the earth observation layers and many other beautiful and authoritative maps on hundreds of topics.Geonet is a good resource for learning more about earth observations layers and the Living Atlas of the World. Follow the Living Atlas on GeoNet.

Melting snowpack is a key part of the spring water budget in many parts of the world. Like a natural reservoir, snowpack stores winter precipitation and releases it as runoff over the course of many months. Where summer rains are scarce snowpack provides crucial base flow without which rivers might go dry. Where summer rains are torrential, this exacerbates the flooding and can lead to the loss of lives. This map contains a historical record showing the water stored in snowpack during each month from March 2000 to the present. It is not a map of snow depth, but of snow water equivalent, which is the amount of water that would be produced if all the snow melted. For fresh snow, this can be anywhere from 5% to 20% the depth of the snow, depending on temperature (snow tends to be fluffier at lower temperatures). As the snow settles and melts, it becomes more dense, up to 40% or 50% in the spring. Temperature, albedo (the reflective property of the snow), density, and volume all affect the melting rate of the snowpack. Additionally, melting rate is influenced by wind, relative humidity, air temperature and solar radiation.Dataset SummaryThe GLDAS Snowpack layer is a time-enabled image service that shows average monthly snowpack from 2000 to present, measured in millimeters of snow water equivalent. It is calculated by NASA using the Noah land surface model, run at 0.25 degree spatial resolution using satellite and ground-based observational data from the Global Land Data Assimilation System (GLDAS-1). The model is run with 3-hourly time steps and aggregated into monthly averages. Review the complete list of model inputs, explore the output data (in GRIB format), and see the full Hydrology Catalog for all related data and information!What can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS Desktop. Is useful for scientific modeling, but only at global scales. The GLDAS snowpack data is useful for modeling, but only at global scales. Time: This is a time-enabled layer. It shows the total evaporative loss during the map's time extent, or if time animation is disabled, a time range can be set using the layer's multidimensional settings. The map shows the sum of all months in the time extent. Minimum temporal resolution is one month; maximum is one year.Important: You must switch from the cartographic renderer to the analytic renderer in the processing template tab in the layer properties window before using this layer as an input to geoprocessing tools.This layer has query, identify, and export image services available. This layer is part of a larger collection of earth observation maps that you can use to perform a wide variety of mapping and analysis tasks.The Living Atlas of the World provides an easy way to explore the earth observation layers and many other beautiful and authoritative maps on hundreds of topics.Geonet is a good resource for learning more about earth observations layers and the Living Atlas of the World. Follow the Living Atlas on GeoNet.

Calculating the total volume of water stored in a landscape can be challenging. In addition to lakes and reservoirs, water can be stored in soil, snowpack, or even inside plants and animals, and tracking the all these different mediums is not generally possible. However, calculating the change in storage is easy - just subtract the water output from the water input. Using the GLDAS layers we can do this calculation for every month from January 2000 to the present day. The precipitation layer tells us the input to each cell and runoff plus evapotranspiration is the output. When the input is higher than the output during a given month, it means water was stored. When output is higher than input, storage is being depleted. Generally the change in storage should be close to the change in soil moisture content plus the change in snowpack, but it will not match up exactly because of the other storage mediums discussed above.Dataset SummaryThe GLDAS Change in Storage layer is a time-enabled image service that shows net monthly change in storage from 2000 to the present, measured in millimeters of water. It is calculated by NASA using the Noah land surface model, run at 0.25 degree spatial resolution using satellite and ground-based observational data from the Global Land Data Assimilation System (GLDAS-2.1). The model is run with 3-hourly time steps and aggregated into monthly averages. Review the complete list of model inputs, explore the output data (in GRIB format), and see the full Hydrology Catalog for all related data and information!Phenomenon Mapped: Change in Water StorageUnits: MillimetersTime Interval: MonthlyTime Extent: 2000/01/01 to presentCell Size: 28 kmSource Type: ScientificPixel Type: Signed IntegerData Projection: GCS WGS84Mosaic Projection: Web Mercator Auxiliary SphereExtent: Global Land SurfaceSource: NASAUpdate Cycle: SporadicWhat can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS for Desktop. It is useful for scientific modeling, but only at global scales.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.By applying the "Calculate Anomaly" raster function, it is possible to view these data in terms of deviation from the mean, instead of total change in storage. Mean change in storage for a given month is calculated over the entire period of record - 2000 to present.Time: This is a time-enabled layer. By default, it will show the first month from the map's time extent. Or, if time animation is disabled, a time range can be set using the layer's multidimensional settings. If you wish to calculate the average, sum, or min/max change in storage over the time extent, change the mosaic operator used to resolve overlapping pixels. In ArcGIS Online, you do this in the "Image Display Order" tab. In ArcGIS Pro, use the "Data" ribbon. In ArcMap, it is in the 'Mosaic' tab of the layer properties window. The minimum time extent is one month, and the maximum is 8 years. Important: You must switch from the cartographic renderer to the analytic renderer in the processing template tab in the layer properties window before using this layer as an input to geoprocessing tools.

Most of us understand the hydrologic cycle in terms of the visible paths that water can take such as rainstorms, rivers, waterfalls and lakes. However, an even larger volume of water flows through the air all around us in two invisible paths: evaporation and transpiration. These two paths together are referred to as evapotranpsiration (ET), and claim 61% of all terrestrial precipitation. Solar radiation, air temperature, wind speed, soil moisture, and land cover all affect the rate of evapotranspiration, which is a major driver of the global water cycle, and key component of most catchments' water budget. This map contains a historical record showing the volume of water lost to evapotranspiration during each month from March 2000 to the present.Dataset SummaryThe GLDAS Evapotranspiration layer is a time-enabled image service that shows total actual evapotranspiration monthly from 2000 to the present, measured in millimeters of water loss. It is calculated by NASA using the Noah land surface model, run at 0.25 degree spatial resolution using satellite and ground-based observational data from the Global Land Data Assimilation System (GLDAS-1). The model is run with 3-hourly time steps and aggregated into monthly averages. Review the complete list of model inputs, explore the output data (in GRIB format), and see the full Hydrology Catalog for all related data and information!What can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS for Desktop. It is useful for scientific modeling, but only at global scales. Time: This is a time-enabled layer. It shows the total evaporative loss during the map's time extent, or if time animation is disabled, a time range can be set using the layer's multidimensional settings. The map shows the sum of all months in the time extent. Minimum temporal resolution is one month; maximum is one year.Important: You must switch from the cartographic renderer to the analytic renderer in the processing template tab in the layer properties window before using this layer as an input to geoprocessing tools.This layer has query, identify, and export image services available. This layer is part of a larger collection of earth observation maps that you can use to perform a wide variety of mapping and analysis tasks.The Living Atlas of the World provides an easy way to explore the earth observation layers and many other beautiful and authoritative maps on hundreds of topics.Geonet is a good resource for learning more about earth observations layers and the Living Atlas of the World. Follow the Living Atlas on GeoNet.

Precipitation is water released from clouds in the form of rain, sleet, snow, or hail. It is the primary source of recharge to the planet's fresh water supplies. This map contains a historical record showing the volume of precipitation that fell during each month from March 2000 to the present. Snow and hail are reported in terms of snow water equivalent - the amount of water that will be produced when they melt. Dataset SummaryThe GLDAS Precipitation layer is a time-enabled image service that shows average monthly precipitation from 2000 to the present, measured in millimeters. It is calculated by NASA using the Noah land surface model, run at 0.25 degree spatial resolution using satellite and ground-based observational data from the Global Land Data Assimilation System (GLDAS-1). The model is run with 3-hourly time steps and aggregated into monthly averages. Review the complete list of model inputs, explore the output data (in GRIB format), and see the full Hydrology Catalog for all related data and information!What can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS for Desktop. It is useful for scientific modeling, but only at global scales.Time: This is a time-enabled layer. It shows the total evaporative loss during the map's time extent, or if time animation is disabled, a time range can be set using the layer's multidimensional settings. The map shows the sum of all months in the time extent. Minimum temporal resolution is one month; maximum is one year.Variables: This layer has two variables: rainfall and snowfall. By default the two are summed, but you can view either by itself using the multidimensional filter. You must disable time animation on the layer before using its multidimensional filter.Important: You must switch from the cartographic renderer to the analytic renderer in the processing template tab in the layer properties window before using this layer as an input to geoprocessing tools.This layer has query, identify, and export image services available.This layer is part of a larger collection of earth observation maps that you can use to perform a wide variety of mapping and analysis tasks.The Living Atlas of the World provides an easy way to explore the earth observation layers and many other beautiful and authoritative maps on hundreds of topics.Geonet is a good resource for learning more about earth observations layers and the Living Atlas of the World. Follow the Living Atlas on GeoNet.

When precipitation falls on the surface of the Earth, much of it is captured in storage (e.g. lakes, aquifers, soil moisture, snowpack, and vegetation). Precipitation that exceeds the storage capacity of the landscape becomes runoff, which flows into river systems. Overland flow is the most visible form of runoff, causing erosion and flash floods, but subsurface flow is the larger contributor in many watersheds. Subsurface flow can emerge on the surface through springs, or more commonly, seep into rivers and lakes through their banks. In urban areas, impervious land cover drastically increases the amount of surface runoff generated, which sweeps trash and urban debris into waterways and increases the likelihood and severity of flash floods. In agricultural areas, surface or subsurface runoff can carry excess salts and nutrients, especially nitrogen and phosphorus. This map contains a historical record showing the amount of runoff generated each month from March 200 to present. It is reported in millimeters, so multiply by a surface area to calculate the total volume of runoff.Dataset SummaryThe GLDAS Runoff layer is a time-enabled image service that shows average monthly runoff from 2000 to the present measured in millimeters. It is calculated by NASA using the Noah land surface model, run at 0.25 degree spatial resolution using satellite and ground-based observational data from the Global Land Data Assimilation System (GLDAS-2.1). The model is run with 3-hourly time steps and aggregated into monthly averages. Review the complete list of model inputs, explore the output data (in GRIB format), and see the full Hydrology Catalog for all related data and information!Phenomenon Mapped: RunoffUnits: MillimetersTime Interval: MonthlyTime Extent: 2000/01/01 to presentCell Size: 28 kmSource Type: ScientificPixel Type: Signed IntegerData Projection: GCS WGS84Mosaic Projection: Web Mercator Auxiliary SphereExtent: Global Land SurfaceSource: NASAUpdate Cycle: SporadicWhat can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS Desktop. t is useful for scientific modeling, but only at global scales.By applying the "Calculate Anomaly" processing template, it is also possible to view these data in terms of deviation from the mean. Mean runoff for a given month is calculated over the entire period of record - 2000 to present.Time: This is a time-enabled layer. By default, it will show the first month from the map's time extent. Or, if time animation is disabled, a time range can be set using the layer's multidimensional settings. If you wish to calculate the average, sum, or min/max over the time extent, change the mosaic operator used to resolve overlapping pixels. In ArcGIS Online, you do this in the "Image Display Order" tab. In ArcGIS Pro, use the "Data" ribbon. In ArcMap, it is in the 'Mosaic' tab of the layer properties window. If you do this, make sure to also select a specific variable. The minimum time extent is one month, and the maximum is 8 years. Variables: This layer has three variables: total runoff, surface flow and subsurface flow. By default total is shown, but you can select a different variable using the multidimensional filter, or by applying the relevant raster function. Important: You must switch from the cartographic renderer to the analytic renderer in the processing template tab in the layer properties window before using this layer as an input to geoprocessing tools.

Precipitation is water released from clouds in the form of rain, sleet, snow, or hail. It is the primary source of recharge to the planet's fresh water supplies. This map contains a historical record showing the volume of precipitation that fell during each month from March 2000 to the present. Snow and hail are reported in terms of snow water equivalent - the amount of water that will be produced when they melt. Dataset SummaryThe GLDAS Precipitation layer is a time-enabled image service that shows average monthly precipitation from 2000 to the present, measured in millimeters. It is calculated by NASA using the Noah land surface model, run at 0.25 degree spatial resolution using satellite and ground-based observational data from the Global Land Data Assimilation System (GLDAS-2.1). The model is run with 3-hourly time steps and aggregated into monthly averages. Review the complete list of model inputs, explore the output data (in GRIB format), and see the full Hydrology Catalog for all related data and information!Phenomenon Mapped: PrecipitationUnits: MillimetersTime Interval: MonthlyTime Extent: 2000/01/01 to presentCell Size: 28 kmSource Type: ScientificPixel Type: Signed IntegerData Projection: GCS WGS84Mosaic Projection: Web Mercator Auxiliary SphereExtent: Global Land SurfaceSource: NASAUpdate Cycle: SporadicWhat can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS for Desktop. It is useful for scientific modeling, but only at global scales.By applying the "Calculate Anomaly" processing template, it is also possible to view these data in terms of deviation from the mean. Mean precipitation for a given month is calculated over the entire period of record - 2000 to present. Time: This is a time-enabled layer. By default, it will show the first month from the map's time extent. Or, if time animation is disabled, a time range can be set using the layer's multidimensional settings. If you wish to calculate the average, sum, or min/max over the time extent, change the mosaic operator used to resolve overlapping pixels. In ArcGIS Online, you do this in the "Image Display Order" tab. In ArcGIS Pro, use the "Data" ribbon. In ArcMap, it is in the 'Mosaic' tab of the layer properties window. If you do this, make sure to also select a specific variable. The minimum time extent is one month, and the maximum is 8 years. Variables: This layer has three variables: total precipitation, rainfall and snowfall. By default total is shown, but you can select a different variable using the multidimensional filter, or by applying the relevant raster function. Important: You must switch from the cartographic renderer to the analytic renderer in the processing template tab in the layer properties window before using this layer as an input to geoprocessing tool.

Most of us understand the hydrologic cycle in terms of the visible paths that water can take such as rainstorms, rivers, waterfalls and lakes. However, an even larger volume of water flows through the air all around us in two invisible paths: evaporation and transpiration. These two paths together are referred to as evapotranpsiration (ET), and claim 61% of all terrestrial precipitation. Solar radiation, air temperature, wind speed, soil moisture, and land cover all affect the rate of evapotranspiration, which is a major driver of the global water cycle, and key component of most catchments' water budget. This map contains a historical record showing the volume of water lost to evapotranspiration globally during each month from March 2000 to the present.Dataset SummaryThe GLDAS Evapotranspiration layer is a time-enabled image service that shows total actual evapotranspiration monthly from 2000 to the present, measured in millimeters of water loss. It is calculated by NASA using the Noah land surface model, run at 0.25 degree spatial resolution using satellite and ground-based observational data from the Global Land Data Assimilation System (GLDAS-2.1). The model is run with 3-hourly time steps and aggregated into monthly averages. Review the complete list of model inputs, explore the output data (in GRIB format), and see the full Hydrology Catalog for all related data and information!Phenomenon Mapped: EvapotranspirationUnits: MillimetersTime Interval: MonthlyTime Extent: 2000/01/01 to presentCell Size: 28 kmSource Type: ScientificPixel Type: Signed IntegerData Projection: GCS WGS84Mosaic Projection: Web Mercator Auxiliary SphereExtent: Global Land SurfaceSource: NASAUpdate Cycle: SporadicWhat can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS for Desktop. It is useful for scientific modeling, but only at global scales. By applying the "Calculate Anomaly" processing template, it is also possible to view these data in terms of deviation from the mean. Mean evapotranspiration for a given month is calculated over the entire period of record - 2000 to present.Time: This is a time-enabled layer. By default, it will show the first month from the map's time extent. Or, if time animation is disabled, a time range can be set using the layer's multidimensional settings. If you wish to calculate the average, sum, or min/max over the time extent, change the mosaic operator used to resolve overlapping pixels. In ArcGIS Online, you do this in the "Image Display Order" tab. In ArcGIS Pro, use the "Data" ribbon. In ArcMap, it is in the 'Mosaic' tab of the layer properties window. The minimum time extent is one month, and the maximum is 8 years. Important: You must switch from the cartographic renderer to the analytic renderer in the processing template tab in the layer properties window before using this layer as an input to geoprocessing tools.

Soils and soil moisture greatly influence the water cycle and have impacts on runoff, flooding and agriculture. Soil type and soil particle composition (sand, clay, silt) affect soil moisture and the ability of the soil to retain water. Soil moisture is also affected by levels of evaporation and plant transpiration, potentially leading to near dryness and eventual drought.Measuring and monitoring soil moisture can ensure the fitness of your crops and help predict or prepare for flash floods and drought. The GLDAS soil moisture data is useful for modeling these scenarios and others, but only at global scales. Dataset SummaryThe GLDAS Soil Moisture layer is a time-enabled image service that shows average monthly soil moisture from 2000 to the present, measured as the millimeters of water contained within four different depth levels. It is calculated by NASA using the Noah land surface model, run at 0.25 degree spatial resolution using satellite and ground-based observational data from the Global Land Data Assimilation System (GLDAS-2.1). The model is run with 3-hourly time steps and aggregated into monthly averages. Review the complete list of model inputs, explore the output data (in GRIB format), and see the full Hydrology Catalog for all related data and information!Phenomenon Mapped: Soil MoistureUnits: MillimetersTime Interval: MonthlyTime Extent: 2000/01/01 to presentCell Size: 28 kmSource Type: ScientificPixel Type: Signed IntegerData Projection: GCS WGS84Mosaic Projection: Web Mercator Auxiliary SphereExtent: Global Land SurfaceSource: NASAUpdate Cycle: SporadicWhat can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS Desktop. The GLDAS soil moisture data is useful for modeling, but only at global scales. By applying the "Calculate Anomaly" processing template, it is also possible to view these data in terms of deviation from the mean. Mean soil moisture for a given month is calculated over the entire period of record - 2000 to present.Time: This is a time-enabled layer. By default, it will show the first month from the map's time extent. Or, if time animation is disabled, a time range can be set using the layer's multidimensional settings. If you wish to calculate the average, sum, or min/max over the time extent, change the mosaic operator used to resolve overlapping pixels. In ArcGIS Online, you do this in the "Image Display Order" tab. In ArcGIS Pro, use the "Data" ribbon. In ArcMap, it is in the 'Mosaic' tab of the layer properties window. If you do this, make sure to also select a specific variable. The minimum time extent is one month, and the maximum is 8 years. Variables: This layer has five variables, corresponding to different depth levels. By default total is shown, but you can view an individual depth level using the multidimensional filter, or by applying the relevant raster function. Important: You must switch from the cartographic renderer to the analytic renderer in the processing template tab in the layer properties window before using this layer as an input to geoprocessing tools.

The method to create the Wind Resource Area datasets is to:Query Power Plant point locations from the California Energy Commission, California Power Plants data set by operational status and capacity greater than or equal to 2 MW at each facility from the Quarterly Fuel and Energy Report, CEC-1304A. Plants tracked include those of at least 1 MW, which are considered of commercial size. A polygon was generated around the resulting operational, commercial wind facilities using the Aggregate Points geoprocessing tool with an aggregation distance of 15 survey miles. A 5 mile spatial buffer was added to the resulting polygons. The buffer does not represent information regarding environmental analysis. It is used only to depict plant concentration regions.

This feature layer was created by calculating the percentage of impervious surface within a census tract polygon using the tabulate intersection geoprocessing tool. Impervious surface data used in the analysis included is from 2015 through 2023. Updated annually as new data becomes available. If there are any questions about this data, please email dwsdGIS@detroitmi.gov

Most of us understand the hydrologic cycle in terms of the visible paths that water can take such as rainstorms, rivers, waterfalls and lakes. However, an even larger volume of water flows through the air all around us in two invisible paths: evaporation and transpiration. These two paths together are referred to as evapotranpsiration (ET), and claim 61% of all terrestrial precipitation. Solar radiation, air temperature, wind speed, soil moisture, and land cover all affect the rate of evapotranspiration, which is a major driver of the global water cycle, and key component of most catchments' water budget. This map contains a historical record showing the volume of water lost to evapotranspiration globally during each month from March 2000 to the present.Dataset SummaryThe GLDAS Evapotranspiration layer is a time-enabled image service that shows total actual evapotranspiration monthly from 2000 to the present, measured in millimeters of water loss. It is calculated by NASA using the Noah land surface model, run at 0.25 degree spatial resolution using satellite and ground-based observational data from the Global Land Data Assimilation System (GLDAS-2.1). The model is run with 3-hourly time steps and aggregated into monthly averages. Review the complete list of model inputs, explore the output data (in GRIB format), and see the full Hydrology Catalog for all related data and information!Phenomenon Mapped: EvapotranspirationUnits: MillimetersTime Interval: MonthlyTime Extent: 2000/01/01 to presentCell Size: 28 kmSource Type: ScientificPixel Type: Signed IntegerData Projection: GCS WGS84Mosaic Projection: Web Mercator Auxiliary SphereExtent: Global Land SurfaceSource: NASAUpdate Cycle: SporadicWhat can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS for Desktop. It is useful for scientific modeling, but only at global scales. By applying the "Calculate Anomaly" processing template, it is also possible to view these data in terms of deviation from the mean. Mean evapotranspiration for a given month is calculated over the entire period of record - 2000 to present.Time: This is a time-enabled layer. By default, it will show the first month from the map's time extent. Or, if time animation is disabled, a time range can be set using the layer's multidimensional settings. If you wish to calculate the average, sum, or min/max over the time extent, change the mosaic operator used to resolve overlapping pixels. In ArcGIS Online, you do this in the "Image Display Order" tab. In ArcGIS Pro, use the "Data" ribbon. In ArcMap, it is in the 'Mosaic' tab of the layer properties window. The minimum time extent is one month, and the maximum is 8 years. Important: You must switch from the cartographic renderer to the analytic renderer in the processing template tab in the layer properties window before using this layer as an input to geoprocessing tools.

This map features the GLDAS total monthly precipitation modeled globally by NASA. The map shows the monthly precipitation for the period of May 2016 to May 2018, focused on Africa. You can click the Play button on the time slider to see precipitation over time.Great parts of Northern Africa and Southern Africa, as well as the whole Horn of Africa, mainly have a hot desert climate, or a hot semi-arid climate for the wetter locations. The equatorial region near the Intertropical Convergence Zone is the wettest portion of the continent. Annually, the rain belt across the country marches northward into Sub-Saharan Africa by August, then moves back southward into south-central Africa by March.Precipitation is water released from clouds in the form of rain, sleet, snow, or hail. It is the primary source of recharge to the planet's fresh water supplies. This map contains a historical record showing the volume of precipitation that fell during each month from March 2000 to the present. Snow and hail are reported in terms of snow water equivalent - the amount of water that will be produced when they melt. Dataset SummaryThe GLDAS Precipitation layer is a time-enabled image service that shows average monthly precipitation from 2000 to the present, measured in millimeters. It is calculated by NASA using the Noah land surface model, run at 0.25 degree spatial resolution using satellite and ground-based observational data from the Global Land Data Assimilation System (GLDAS-2.1). The model is run with 3-hourly time steps and aggregated into monthly averages. A complete list of the model inputs can be seen here, and the output data (in GRIB format) is available here.Phenomenon Mapped: PrecipitationUnits: MillimetersTime Interval: MonthlyTime Extent: 2000/01/01 to presentCell Size: 28 kmSource Type: ScientificPixel Type: Signed IntegerData Projection: GCS WGS84Mosaic Projection: Web Mercator Auxiliary SphereExtent: Global Land SurfaceSource: NASAUpdate Cycle: SporadicWhat can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS for Desktop. It is useful for scientific modeling, but only at global scales.By applying the "Calculate Anomaly" processing template, it is also possible to view these data in terms of deviation from the mean, instead of total evapotranspiration. Mean evapotranspiration for a given month is calculated over the entire period of record - 2000 to present.Time: This is a time-enabled layer. It shows the total evaporative loss during the map's time extent, or if time animation is disabled, a time range can be set using the layer's multidimensional settings. The map shows the sum of all months in the time extent. Minimum temporal resolution is one month; maximum is eight years.Variables: This layer has two variables: rainfall and snowfall. By default the two are summed, but you can view either by itself using the multidimensional filter, or by applying the relevant raster function. You must disable time animation on the layer before using its multidimensional filter.Important: You must switch from the cartographic renderer to the analytic renderer in the processing template tab in the layer properties window before using this layer as an input to geoprocessing tools.

Measure and Map Access to Grocery StoresFrom the perspective of the people living in each neighborhood How do people in your city get to the grocery store? The answer to that question depends on the person and where they live. This collection of layers, maps and apps help answer the question.Some live in cities and stop by a grocery store within a short walk or bike ride of home or work. Others live in areas where car ownership is more prevalent, and so they drive to a store. Some do not own a vehicle, and rely on a friend or public transit. Others rely on grocery delivery for their needs. And, many live in rural areas far from town, so a trip to a grocery store is an infrequent event involving a long drive.This map from Esri shows which areas are within a ten minute walk (in green) or ten minute drive (in blue) of a grocery store in the United States and Puerto Rico. Darker color indicates access to more stores. Summarizing this data shows that 20% of U.S. population live within a 10 minute walk of a grocery store, and 90% of the population live within a 10 minute drive of a grocery store. Click on the map to see a summary for each state.Every census block is scored with a count of walkable and drivable stores nearby, making this a map suitable for a dashboard for any city, or any of the 50 states, DC and Puerto Rico. Two colorful layers visualize this definition of access, one for walkable access (suitable for looking at a city neighborhood by neighborhood) and one for drivable access (suitable for looking across a city, county, region or state).On the walkable layer, shades of green define areas within a ten minute walk of one or more grocery stores. The colors become more intense and trend to a blue-green color for the busiest neighborhoods, such as downtown San Francisco. As you zoom in, a layer of Census block points visualizes the local population with or without walkable access. As you zoom out to see the entire city, the map adds a light blue - to dark blue layer, showing which parts of the region fall within ten minutes' drive of one or more grocery stores. As a result, the map is useful at all scales, from national to regional, state and local levels. It becomes easier to spot grocery stores that sit within a highly populated area, and grocery stores that sit in a shopping center far away from populated areas. This view of a city begins to hint at the question: how many people have each type of access to grocery stores? And, what if they are unable to walk a mile regularly, or don't own a car? How to Use This MapUse this map to introduce the concepts of access to grocery stores in your city or town. This is the kind of map where people will want to look up their home or work address to validate what the map is saying against their own experiences. The map was built with that use in mind. Many maps of access use straight-line, as-the-crow-flies distance, which ignores real-world barriers to walkability like rivers, lakes, interstates and other characteristics of the built environment. Block analysis using a network data set and Origin-Destination analysis factors these barriers in, resulting in a more realistic depiction of access. There is data behind the map, which can be summarized to show how many people have walkable access to local grocery stores. The map includes a feature layer of population in Census block points, which are visible when you zoom in far enough. This feature layer of Census block centroids can be plugged into an app like this one that summarizes the population with/without walkable or drivable access. Lastly, this map can serve as backdrop to other community resources, like food banks, farmers markets (example), and transit (example). Add a transit layer to immediately gauge its impact on the population's grocery access. You can also use this map to see how it relates to communities of concern. Add a layer of any block group or tract demographics, such as Percent Senior Population (examples), or Percent of Households with Access to 0 Vehicles (examples). The map is a useful visual and analytic resource for helping community leaders, business and government leaders see their town from the perspective of its residents, and begin asking questions about how their community could be improved. Data sourcesPopulation data is from the 2020 U.S. Census blocks. Each census block has a count of stores within a 10 minute walk, and a count of stores within a ten minute drive. Census blocks known to be unpopulated are given a score of 0. The layer is available as a hosted feature layer. Grocery store locations are from SafeGraph, reflecting what was in the data as of September 2024. For this project, ArcGIS StreetMap Premium was used for the street network in the origin-destination analysis work, because it has the necessary attributes on each street segment to identify which streets are considered walkable, and supports a wide variety of driving parameters. The walkable access layer and drivable access layers are rasters, whose colors were chosen to allow the drivable access layer to serve as backdrop to the walkable access layer. Data PreparationArcGIS Network Analyst was used to set up a network street layer for analysis. ArcGIS StreetMap Premium was installed to a local hard drive and selected in the Origin-Destination workflow as the network data source. This allows the origins (Census block centroids) and destinations (SafeGraph grocery stores) to be connected to that network, to allow origin-destination analysis. The Census blocks layer contains the centroid of each Census block. The data allows a simple popup to be created. This layer's block figures can be summarized further, to tract, county and state levels. The SafeGraph grocery store locations were provided by SafeGraph. The source data included NAICS code 445110 and 452311 as an initial screening. The CSV file was imported using the Data Interoperability geoprocessing tools in ArcGIS Pro, where a definition query was applied to the layer to exclude any records that were not grocery stores. The final layer used in the analysis had approximately 63,000 records. In this map, this layer is included as a vector tile layer. MethodologyEvery census block in the U.S. was assigned two access scores, whose numbers are simply how many grocery stores are within a 10 minute walk and a 10 minute drive of that census block. Every census block has a score of 0 (no stores), 1, 2 or more stores. The count of accessible stores was determined using Origin-Destination Analysis in ArcGIS Network Analyst, in ArcGIS Pro. A set of Tools in this ArcGIS Pro package allow a similar analysis to be conducted for any city or other area. The Tools step through the data prep and analysis steps. Download the Pro package, open it and substitute your own layers for Origins and Destinations. Parcel centroids are a suggested option for Origins, for example. Origin-Destination analysis was configured, using ArcGIS StreetMap Premium as the network data source. Census block centroids with population greater than zero were used as the Origins, and grocery store locations were used as the Destinations. A cutoff of 10 minutes was used with the Walk Time option. Only one restriction was applied to the street network: Walkable, which means Interstates and other non-walkable street segments were treated appropriately. You see the results in the map: wherever freeway overpasses and underpasses are present near a grocery store, the walkable area extends across/through that pass, but not along the freeway. A cutoff of 10 minutes was used with the Drive Time option. The default restrictions were applied to the street network, which means a typical vehicle's access to all types of roads was factored in. The results for each analysis were captured in a Lines layer, which shows which origins are within the 10 minute cutoff of each destination over the street network, given the assumptions about that network (walking, or driving a vehicle). The Lines layer is not published but is used to count how many stores each origin has access to over the road network. The Lines layer was then summarized by census block ID to capture the Maximum value of the Destination_Rank field. A census block within 10 minutes of 3 stores would have 3 records in the Lines layer, but only one value in the summarized table, with a MAX_Destination_Rank field value of 3. This is the number of stores accessible to that census block in the 10 minutes measured, for walking and driving. These data were joined to the block centroids layer and given unique names. At this point, all blocks with zero population or null values in the MAX_Destination_Rank fields were given a store count of 0, to help the next step. Walkable and Drivable areas are calculated into a raster layer, using Nearest Neighbor geoprocessing tool on the count of stores within a 10 minute walk, and a count of stores within a ten minute drive, respectively. This tool used a 100 meter grid and interpolates the values between each census block. A census tracts layer containing all water polygons "erased" from the census tract boundaries was used as an environment setting, to help constrain interpolation into/across bodies of water. The same layer use used to "shoreline" the Nearest Neighbor results, to eliminate any interpolation into the ocean or Great Lakes. This helped but was not perfect. Notes and LimitationsThe map provides a baseline for discussing access to grocery stores in a city. It does not presume local population has the desire or means to walk or drive to obtain groceries. It does not take elevation gain or loss into account. It does not factor time of day nor weather, seasons, or other variables that affect a person's commute choices. Walking and driving are just two ways people get to a grocery store. Some people ride a bike, others take public transit, have groceries delivered, or rely on a friend with a vehicle.

Methods:This lidar derivative provides information about the bare surface of the earth. The 2-foot resolution hillshade raster was produced from the 2020 Digital Terrain Model using the hillshade geoprocessing tool in ArcGIS Pro.QL1 airborne lidar point cloud collected countywide (Sanborn)Point cloud classification to assign ground points (Sanborn)Ground points were used to create over 8,000 1-foot resolution hydro-flattened Raster DSM tiles. Using automated scripting routines within LP360, a GeoTIFF file was created for each tile. Each 2,500 x 2,500 foot tile was reviewed using Global Mapper to check for any surface anomalies or incorrect elevations found within the surface. (Sanborn)1-foot hydroflattened DTM tiles mosaicked together into a 1-foot resolution mosaiced hydroflattened DTM geotiff (Tukman Geospatial)1-foot hydroflattened DTM (geotiff) resampled to 2-foot hydro-flattened DTM using Bilinear interpolation and clipped to county boundary with 250-meter buffer (Tukman Geospatial)2-foot hillshade derived from DTM using the ESRI Spatial Analyst ‘hillshade’ function The data was developed based on a horizontal projection/datum of NAD83 (2011), State Plane, Feet and vertical datum of NAVD88 (GEOID18), Feet. Lidar was collected in early 2020, while no snow was on the ground and rivers were at or below normal levels. To postprocess the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Sanborn Map Company, Inc., utilized a total of 25 ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. An additional 125 independent accuracy checkpoints, 70 in Bare Earth and Urban landcovers (70 NVA points), 55 in Tall Grass and Brushland/Low Trees categories (55 VVA points), were used to assess the vertical accuracy of the data. These check points were not used to calibrate or post process the data.Uses and Limitations: The hillshade provides a raster depiction of the ground returns for each 2x2 foot raster cell across Santa Clara County. The layer is useful for hydrologic and terrain-focused analysis and is a helpful basemap when analyzing spatial data in relief.Related Datasets: This dataset is part of a suite of lidar of derivatives for Santa Clara County. See table 1 for a list of all the derivatives. Table 1. lidar derivatives for Santa Clara CountyDatasetDescriptionLink to DataLink to DatasheetCanopy Height ModelPixel values represent the aboveground height of vegetation and trees.https://vegmap.press/clara_chmhttps://vegmap.press/clara_chm_datasheetCanopy Height Model – Veg Returns OnlySame as canopy height model, but does not include lidar returns labelled as ‘unclassified’ (uses only returns classified as vegetation)https://vegmap.press/clara_chm_veg_returnshttps://vegmap.press/clara_chm_veg_returns_datasheetCanopy CoverPixel values represent the presence or absence of tree canopy or vegetation greater than or equal to 15 feet tall.https://vegmap.press/clara_coverhttps://vegmap.press/clara_cover_datasheetCanopy Cover – Veg Returns OnlySame as canopy height model, but does not include lidar returns labelled as ‘unclassified’ (uses only returns classified as vegetation)https://vegmap.press/clara_cover_veg_returnshttps://vegmap.press/clara_cover_veg_returns_datasheet HillshadeThis depicts shaded relief based on the Hillshade. Hillshades are useful for visual reference when mapping features such as roads and drainages and for visualizing physical geography. https://vegmap.press/clara_hillshadehttps://vegmap.press/clara_hillshade_datasheetDigital Terrain ModelPixel values represent the elevation above sea level of the bare earth, with all above-ground features, such as trees and buildings, removed. The vertical datum is NAVD88 (GEOID18).https://vegmap.press/clara_dtmhttps://vegmap.press/clara_dtm_datasheetDigital Surface ModelPixel values represent the elevation above sea level of the highest surface, whether that surface for a given pixel is the bare earth, the top of vegetation, or the top of a building.https://vegmap.press/clara_dsmhttps://vegmap.press/clara_dsm_datasheet