This resource contains the test data for the GeoServer OGC Web Services tutorials for various GIS applications including ArcGIS Pro, ArcMap, ArcGIS Story Maps, and QGIS. The contents of the data include a polygon shapefile, a polyline shapefile, a point shapefile, and a raster dataset; all of which pertain to the state of Utah, USA. The polygon shapefile is of every county in the state of Utah. The polyline is of every trail in the state of Utah. The point shapefile is the current list of GNIS place names in the state of Utah. The raster dataset covers a region in the center of the state of Utah. All datasets are projected to NAD 1983 Zone 12N.

Florida Ecological Greenways Network 2021 (layer name fegn2021_polygon): This vector layer was created from the original raster grid version (fegn2021) created by the University of Florida Center for Landscape Conservation Planning to provide an ecological component to the Statewide Greenways System plan developed by the Department of Environmental Protection, Office of Greenways and Trails (OGT). The FEGN guides OGT ecological greenway conservation efforts and promotes public awareness of the need for and benefits of a statewide ecological greenways network. It is also used as the primary data layer to inform the Florida Forever and other state and regional land acquisition programs regarding the location of the most important wildlife and ecological corridors and large, intact landscapes in the state. The FEGN identifies areas of opportunity for protecting a statewide network of ecological hubs (large areas of ecological significance) and linkages designed to maintain large landscape-scale ecological functions including priority species habitat and ecosystem services throughout the state. Inclusion in the FEGN means the area is either part of a large landscape-scale “hub”, or an ecological corridor connecting two or more hubs. Hubs indicate core landscapes that are large enough to maintain populations of wide-ranging or fragmentation-sensitive species including black bear or panther and areas that are more likely to support functional ecosystem services. Highest priorities indicate the most significant hubs and corridors in relation to completing a functionally connected statewide ecological network, but all priority levels have conservation value. FEGN Priorities 1, 2, and 3 are the most important for protecting a ecologically functional connected statewide network of public and private conservation lands, and these three priority levels (P1, P2, and P3) are now called the Florida Wildlife Corridor as per the Florida Wildlife Corridor legislation passed and signed into law by the Florida Legislature and Governor and 2021, which makes protection of these wildlife and ecological hubs and corridors a high priority as part of a strategic plan for Florida’s future. To accomplish this goal, we need robust state, federal, and local conservation land protection program funding for Florida Forever, Rural and Family Lands Protection Program, Natural Resources Conservation Service easements and incentives, federal Land and Waters Conservation Fund, payments for ecosystem services, etc.For more information http://conservation.dcp.ufl.edu/fegnproject/

For complete collection of data and models, see https://doi.org/10.21942/uva.c.5290546.Original model developed in 2016-17 in ArcGIS by Henk Pieter Sterk (www.rfase.org), with minor updates in 2021 by Stacy Shinneman and Henk Pieter Sterk. Model used to generate publication results:Hierarchical geomorphological mapping in mountainous areas Matheus G.G. De Jong, Henk Pieter Sterk, Stacy Shinneman & Arie C. Seijmonsbergen. Submitted to Journal of Maps 2020, revisions made in 2021.This model creates tiers (columns) of geomorphological features (Tier 1, Tier 2 and Tier 3) in the landscape of Vorarlberg, Austria, each with an increasing level of detail. The input dataset needed to create this 'three-tier-legend' is a geomorphological map of Vorarlberg with a Tier 3 category (e.g. 1111, for glacially eroded bedrock). The model then automatically adds Tier 1, Tier 2 and Tier 3 categories based on the Tier 3 code in the 'Geomorph' field. The model replaces the input file with an updated shapefile of the geomorphology of Vorarlberg, now including three tiers of geomorphological features. Python script files and .lyr symbology files are also provided here.

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 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

In the United States, the federal government manages approximately 28% of the land in the United States. Most federal lands are west of the Mississippi River, where almost half of the land by area is managed by the federal government. Federal lands include 193 million acres managed by the US Forest Service in 154 National Forests and 20 National Grasslands, Bureau of Land Management lands that cover 247 million acres in Alaska and the Western United States, 150 million acres managed for wildlife conservation by the US Fish and Wildlife Service, 84 million acres of National Parks and other lands managed by the National Park Service, and over 30 million acres managed by the Department of Defense. The Bureau of Reclamation manages a much smaller land base than the other agencies included in this layer but plays a critical role in managing the country's water resources. The agencies included in this layer are:Bureau of Land ManagementDepartment of DefenseNational Park ServiceUS Fish and Wildlife ServiceUS Forest ServiceDataset SummaryPhenomenon Mapped: United States federal lands managed by six federal agenciesGeographic Extent: 50 United States and the District of Columbia, Puerto Rico, US Virgin Islands, Guam, American Samoa, and Northern Mariana Islands. The layer also includes National Monuments and Wildlife Refuges in the Pacific Ocean, Atlantic Ocean, and the Caribbean Sea.Data Coordinate System: WGS 1984Visible Scale: The data is visible at all scales but draws best at scales greater than 1:2,000,000Source: BLM, DOD, USFS, USFWS, NPS, PADUS 3.0Publication Date: Various - Esri compiled and published this layer in May 2025. See individual agency views for data vintage.There are six layer views available that were created from this service. Each layer uses a filter to extract an individual agency from the service. For more information about the layer views or how to use them in your own project, follow these links:USA Bureau of Land Management LandsUSA Department of Defense LandsUSA National Park Service LandsUSA Fish and Wildlife Service LandsUSA Forest Service LandsWhat can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "federal lands" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "federal lands" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shapefile or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.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.

The Digital Geologic-GIS Map of Santa Rosa Island, California is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (sris_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (sris_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (sris_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (chis_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (chis_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (sris_geology_metadata_faq.pdf). Please read the chis_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: American Association of Petroleum Geologists. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (sris_geology_metadata.txt or sris_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

In the United States, the federal government manages lands in significant parts of the country. These lands include 193 million acres managed by the US Forest Service in the nation's 154 National Forests and 20 National Grasslands, Bureau of Land Management lands that cover 247 million acres in Alaska and the Western United States, 150 million acres managed for wildlife conservation by the US Fish and Wildlife Service, 84 million acres of National Parks and other lands managed by the National Park Service and over 30 million acres managed by the Department of Defense. The Bureau of Reclamation manages a much smaller land base than the other agencies included in this layer but plays a critical role in managing the country's water resources.The agencies included in this layer are:Bureau of Land ManagementBureau of ReclamationDepartment of DefenseNational Park ServiceUS Fish and Wildlife ServiceUS Forest ServiceDataset SummaryPhenomenon Mapped: United States lands managed by six federal agencies Coordinate System: Web Mercator Auxiliary SphereExtent: 50 United States plus Puerto Rico, US Virgin Islands, Guam, American Samoa, and Northern Mariana Islands. The layer also includes National Monuments and Wildlife Refuges in the Pacific Ocean, Atlantic Ocean, and the Caribbean Sea.Visible Scale: The data is visible at all scales but draws best at scales greater than 1:2,000,000Source: BLM, DoD, USFS, USFWS, NPS, PADUS 2.1Publication Date: Various - Esri compiled and published this layer in May 2022. See individual agency views for data vintage.There are six layer views available that were created from this service. Each layer uses a filter to extract an individual agency from the service. For more information about the layer views or how to use them in your own project, follow these links:USA Bureau of Land Management LandsUSA Bureau of Reclamation LandsUSA Department of Defense LandsUSA National Park Service LandsUSA Fish and Wildlife Service LandsUSA Forest Service LandsWhat can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "federal lands" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "federal lands" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shapefile or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.

A 2D Hydraulic model (HEC-RAS) for below Tuttle Creek Reservoir at the confluence of the Kansas River and the Big Blue River near Manhattan, KS is presented. Model geometry is based on United States Geological Survey (USGS) 3DEP data (2015), with underwater bathymetry “burned” in using cross-sections sampled in the field in April of 2023. The model was calibrated based on water surface measured during data collection. The hydraulic simulations correspond to streamflows during which fish monitoring data were collected by researchers at Kansas State University (L. Rowley and K. Gido, to be published). Results from the hydraulic model, coupled with a sediment transport model, will be used to study fish and macroinvertabrate ecological response to streamflow. Methods The following is a summary of data utilized for developing a bathymetric terrain for 2D hydraulic modeling using HEC-RAS. Data used for model calibration and validation is also discussed.

Available Data Cross-section elevation data were collected by the United States Army Corps of Engineers (USACE) Kansas City District at approximately 200-foot to 1000-foot increments at the confluence of the Big Blue River and the Kansas River near Manhattan, Kansas. The following equipment was used by two complete surveying teams: • Ohmex SonarMite single beam echo sounder SFX @ 200khz, • Ohmex SonarMite single beam echo sounder DFX @ 28kHz & 200kHZ, • Trimble R12i 0096 & 0098, • Trimble R8 1984 & 6282

The cross-section elevation data were collected by boat and supplemented by hand-carried, pole-mounted Trimbles on April 10 to 14, 2023. The USGS gage on the Big Blue River near Manhattan, KS (06887000) had an average discharge of 425 cfs during the field collection time period (Figure 1). A USGS gage downstream of the confluence, Kansas River at Wamego, KS (06887500) shows an average discharge of 780 cfs at the same time period (Figure 2).

Figure 1 (Refer to supplemental information file). USGS gage Big Blue R NR Manhattan, KS – 06887000 discharge data for the week of April 11, 2023 – April 15, 2023. The average flow was taken as 425 cfs.

Figure 2 (Refer to supplemental information file). USGS gage Kansas River at Wamego, KS (06887500) discharge data for the week of April 11, 2023 – April 15, 2023. The average flow was taken as 780 cfs. Wamego, KS is downstream of the Big Blue River and Kansas River confluence and represents combined flow for both tributaries.

Figure 3 (Refer to supplemental information file). Map of bathymetric cross-sections collected in April 2023 near Manhattan, KS. Arrows show flow direction. Inset is the data collection location relative to the state of Kansas.

Terrain The field data collection featured 56 cross-sections. HEC-RAS 6.3.1 was utilized to create a bathymetric surface by interpolating 1-D cross-sections, while a 1-m resolution USGS 3DEP terrain (2015) was used for the floodplain and surrounding areas. A more recent USGS 3DEP (2018) data was available but featured higher stream flow than the 2015 data collection and therefore, more of the channel was submerged. Overall, the difference between 2015 and 2018 had a mean deviation of ~0.04 feet, with a majority of the differences in the channel ranging between +/-0.5 feet. Islands in this reach are unvegetated and prone to movement, and therefore the exact channel form is uncertain. However, it is assumed that relative island areas are consistent throughout the reach, and 2015 LiDAR was used to delineate the most island area as possible.

To build the bathymetric terrain, a similar process as what was discussed in Harris et al. (2023), field collected data were imported into ArcGIS Pro 3.0 as a point shapefile. To preserve georeferencing, the point shapefile was segmented into groups of 3-4 cross-sections and these cross-sections were interpolated into mini-surfaces using the Inverse Distance Weighted (IDW) spatial analysis tool. These mini-surfaces were brought into HEC-RAS and cross-sections were drawn to intersect with these field surveyed locations. The 1-D cross-sections were then used to create a TIFF for the entire channel area. The 1D interpolation captures the channel centerline between measured cross-sections but meanders and channel widening may not be covered by the interpolated channel. The channel raster was broken into its component objects or “exploded”, in ArcGIS Pro using the Raster to Point tool. The points were then interpolated using the Inverse-Distance-Weighted interpolation tool (IDW). This creates a terrain that covers meanders and channel expansion while maintaining fidelity to the original channel raster.

Areas where the terrain was inundated at the time of LiDAR data collection are “flat” and referred to as a hydro-flattened surface. The Slope tool in ArcMap was used to delineate these hydro-flattened areas and a shapefile tracing unsubmerged islands was used. The IDW surface was clipped to the hydro-flattened extents and then mosaicked with the original 3DEP terrain to create a seamless bathymetric and topographic surface.

The field data collected in April 2023 (Figure 3) required supplemental information to cover a fish monitoring instance upstream of the bridge at Pillsbury Drive/177. In September 2021, the USACE Kansas City District collected sediment samples with XY-georeference and depth measurements. The LiDAR hydro-flattened surface was used to estimate the energy grade slope from the new cross-section to the recent field monitoring extents. The model scenario or “plan” on the April 2023 extents was run at a similar flow as was occurring in September 2021. The combination of water surface elevation at that flow (780 cfs), the energy grade slope in the 3DEP data and field measured depth in 2021 were used to estimate the elevation at the channel bed.

Land Cover Land cover was delineated using the Multi-Resolution Land Characteristic (MRLC) Consortium’s 2019 National Land Cover Data (NLCD) (MRLC 2016). Fifteen types of landcover were identified for this study area by the NLCD: Hay-Pasture, Shrub-Scrub, Developed Low Intensity, Developed Medium Intensity, Cultivated Crops, Deciduous Forest, Herbaceous, Develop Open Space, Developed High Intensity, Woody Wetlands, Emergent Herbaceous Wetland, Open Water, Mixed Forest, Barren Land, and Evergreen Forest. Manning’s n values were selected based on a range of n values along with a “Suggested Initial n” provided by Krest Engineers (2021) (Table 1). Table 1. A table representing a range of Manning’s n values, a suggested Manning’s n value, and percent imperviousness for each NLCD land cover type. (Krest Engineers, 2021)

Model Settings The 2D HEC-RAS mesh was set to 40-feet square, with breaklines to orient cell edges along areas of steep elevation change or to support model convergence. Boundary conditions were placed at three locations in the 2D flow area: the inflow of the Big Blue River (boundary condition type: flow hydrograph), the upstream end of the Kanas River (flow hydrograph), and the downstream end of the Kanas River (normal depth). An energy grade slope was given as 0.0005 ft/ft for the Big Blue River and 0.0003 ft/ft for the Kansas River. Advanced time step control adjustments were implemented using Courant’s Criterion, with a minimum Courant of 0.75 and a maximum of 3.

Calibration The suggested value from Krest Engineers (2021) was the initial Manning’s n used for each land cover type (Table 1). The hydraulic model was then run, and the Manning’s n was changed to better conform to water surface elevations observed during field data collection. Flows corresponding to the field collection dates were 415 cfs for the Big Blue River and 360 cfs for the Kansas River. These streamflows were determined by cross-referencing the field collection dates (April 10 to 14, 2023) to continuous monitoring data available from USGS at gages Big Blue R NR Manhattan, KS (06887000) and Kansas R at Fort Riley, KS (06879100). The 2D model simulation results were compared to the field-measured water surface elevations at each channel cross-section with the ArcGIS Zonal Statistics as Table tool. Model improvement was determined by calculating the Root Mean Square Error (RMSE) of the simulated water surface elevation to the field observed water surface elevation, and the Manning’s n values resulting in the lowest error were selected. Following calibration, the model has overall RMSE of 0.29 ft for depth. The final Manning’s n values used for all the following simulations are included in Table 2.

Land Cover

Mannings n

Open Water

0.025

Emergent Herbaceous Wetlands

0.05

Woody Wetlands

0.045

Herbaceous

0.025

Mixed Forest

0.08

Evergreen Forest

0.08

Deciduous Forest

0.1

Scrub-Shrub

0.07

Hay-Pasture

0.025

Cultivated Crops

0.02

Baren Land

0.023

Developed, Open Space

0.03

Developed, Low Intensity

0.06

Developed, Medium Intensity

0.08

Developed, High Intensity

0.12

Table 2. The selected Manning’s n per Landcover classification after calibration

Simulations Apart from the calibration simulations, further simulations were conducted to match additional fish data collection from July 17 – 21, 2023 and October 2- 6, 2023. USGS gages, Big Blue R NR Manhattan, KS (06887000) and Kansas R at Fort Riley, KS (06879100), were used to find the discharge rates (in cfs) during those fish sampling periods. While discharge was consistent throughout the weeks for some gages (Figures 4 and 7), others showed differences greater than 10% or 100 cfs (Figures 5 and 6). The gages that showed significant differences were divided into two sub-simulations for the lower and higher flows during that week.

USGS Streamflow Data for July 17 - 21, 2023

HEC RAS Scenario Description River Simulation Flow (cfs)

July_KS_LF July lower flow Big

Karst hydrologic systems are important resources in the state of Tennessee, both as drinking water resources and as centers for possible biological diversity. These systems are susceptible to contamination due to the inherent connectivity between surface water and groundwater systems in karst systems. A partnership between the U.S. Geological Survey (USGS) and Tennessee Department of Environment and Conservation (TDEC) was formed to investigate karst spring systems across the state utilizing fluorescent groundwater tracing, particularly in areas where these resources may be used as drinking water sources. In fall 2021, USGS and TDEC staff identified possible vulnerabilities or complexities that may exist within karst spring systems based upon maturity of karst development, underlying geology, and uncertainties related to estimated recharge areas. Based upon initial research, several study areas were selected and fieldwork started in March 2022. In Water Year 2024 (10/1/2023-9/30/2024) dye tracing was conducted in the communities of Caryville, Lafayette, Morristown, Mount Pleasant, and Vanleer. Collectively these communities span multiple physiographic regions including the Western and Eastern Highland Rim, and the Valley and Ridge Province. Each of these communities rely on karst groundwater as a drinking water source. Additionally, these are all areas where the hydrology has been significantly altered by karst processes and thus the groundwater pathways are complex and unpredictable. This data release contains shapefiles of injection locations, monitoring sites, and dye traces conducted during the 2024 Water Year throughout Tennessee in communities that utilize karst groundwater as a drinking water source. All files were created in ArcGIS Pro and each shapefile contains associated attributes for the features contained within. Layer files are included with the datasets to match symbology found in figures in the accompanying report. All shapefiles and layers were created and modified in ArcGIS software. For a full description of the methods used to create these files, see Process Steps in the metadata file, "TN_WY24_Metadata.xml”. Data within each child item of this data release are named with a two-letter abbreviation unique for the community where the tracing occurred and the water year when the work was conducted (e.g. LF24). Abbreviations for the communities are as follows: CR = Caryville, LF = Lafayette, MR = Morristown, MP = Mount Pleasant, and VN = Vanleer.

Please note that this dataset is not an official City of Toronto land use dataset. It was created for personal and academic use using City of Toronto Land Use Maps (2019) found on the City of Toronto Official Plan website at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/official-plan-maps-copy, along with the City of Toronto parcel fabric (Property Boundaries) found at https://open.toronto.ca/dataset/property-boundaries/ and Statistics Canada Census Dissemination Blocks level boundary files (2016). The property boundaries used were dated November 11, 2021. Further detail about the City of Toronto's Official Plan, consolidation of the information presented in its online form, and considerations for its interpretation can be found at https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/official-plan/ Data Creation Documentation and Procedures Software Used The spatial vector data were created using ArcGIS Pro 2.9.0 in December 2021. PDF File Conversions Using Adobe Acrobat Pro DC software, the following downloaded PDF map images were converted to TIF format. 9028-cp-official-plan-Map-14_LandUse_AODA.pdf 9042-cp-official-plan-Map-22_LandUse_AODA.pdf 9070-cp-official-plan-Map-20_LandUse_AODA.pdf 908a-cp-official-plan-Map-13_LandUse_AODA.pdf 978e-cp-official-plan-Map-17_LandUse_AODA.pdf 97cc-cp-official-plan-Map-15_LandUse_AODA.pdf 97d4-cp-official-plan-Map-23_LandUse_AODA.pdf 97f2-cp-official-plan-Map-19_LandUse_AODA.pdf 97fe-cp-official-plan-Map-18_LandUse_AODA.pdf 9811-cp-official-plan-Map-16_LandUse_AODA.pdf 982d-cp-official-plan-Map-21_LandUse_AODA.pdf Georeferencing and Reprojecting Data Files The original projection of the PDF maps is unknown but were most likely published using MTM Zone 10 EPSG 2019 as per many of the City of Toronto's many datasets. They could also have possibly been published in UTM Zone 17 EPSG 26917 The TIF images were georeferenced in ArcGIS Pro using this projection with very good results. The images were matched against the City of Toronto's Centreline dataset found here The resulting TIF files and their supporting spatial files include: TOLandUseMap13.tfwx TOLandUseMap13.tif TOLandUseMap13.tif.aux.xml TOLandUseMap13.tif.ovr TOLandUseMap14.tfwx TOLandUseMap14.tif TOLandUseMap14.tif.aux.xml TOLandUseMap14.tif.ovr TOLandUseMap15.tfwx TOLandUseMap15.tif TOLandUseMap15.tif.aux.xml TOLandUseMap15.tif.ovr TOLandUseMap16.tfwx TOLandUseMap16.tif TOLandUseMap16.tif.aux.xml TOLandUseMap16.tif.ovr TOLandUseMap17.tfwx TOLandUseMap17.tif TOLandUseMap17.tif.aux.xml TOLandUseMap17.tif.ovr TOLandUseMap18.tfwx TOLandUseMap18.tif TOLandUseMap18.tif.aux.xml TOLandUseMap18.tif.ovr TOLandUseMap19.tif TOLandUseMap19.tif.aux.xml TOLandUseMap19.tif.ovr TOLandUseMap20.tfwx TOLandUseMap20.tif TOLandUseMap20.tif.aux.xml TOLandUseMap20.tif.ovr TOLandUseMap21.tfwx TOLandUseMap21.tif TOLandUseMap21.tif.aux.xml TOLandUseMap21.tif.ovr TOLandUseMap22.tfwx TOLandUseMap22.tif TOLandUseMap22.tif.aux.xml TOLandUseMap22.tif.ovr TOLandUseMap23.tfwx TOLandUseMap23.tif TOLandUseMap23.tif.aux.xml TOLandUseMap23.tif.ov Ground control points were saved for all georeferenced images. The files are the following: map13.txt map14.txt map15.txt map16.txt map17.txt map18.txt map19.txt map21.txt map22.txt map23.txt The City of Toronto's Property Boundaries shapefile, "property_bnds_gcc_wgs84.zip" were unzipped and also reprojected to EPSG 26917 (UTM Zone 17) into a new shapefile, "Property_Boundaries_UTM.shp" Mosaicing Images Once georeferenced, all images were then mosaiced into one image file, "LandUseMosaic20211220v01", within the project-generated Geodatabase, "Landuse.gdb" and exported TIF, "LandUseMosaic20211220.tif" Reclassifying Images Because the original images were of low quality and the conversion to TIF made the image colours even more inconsistent, a method was required to reclassify the images so that different land use classes could be identified. Using Deep learning Objects, the images were re-classified into useful consistent colours. Deep Learning Objects and Training The resulting mosaic was then prepared for reclassification using the Label Objects for Deep Learning tool in ArcGIS Pro. A training sample, "LandUseTrainingSamples20211220", was created in the geodatabase for all land use types as follows: Neighbourhoods Insitutional Natural Areas Core Employment Areas Mixed Use Areas Apartment Neighbourhoods Parks Roads Utility Corridors Other Open Spaces General Employment Areas Regeneration Areas Lettering (not a land use type, but an image colour (black), used to label streets). By identifying the letters, it then made the reclassification and vectorization results easier to clean up of unnecessary clutter caused by the labels of streets. Reclassification Once the... Visit https://dataone.org/datasets/sha256%3A3e3f055bf6281f979484f847d0ed5eeb96143a369592149328c370fe5776742b for complete metadata about this dataset.

This layer features special areas of interest (AOIs) that have been contributed to Esri Community Maps using the new Community Maps Editor app. The data that is accepted by Esri will be included in selected Esri basemaps, including our suite of Esri Vector Basemaps, and made available through this layer to export and use offline. Export DataThe contributed data is also available for contributors and other users to export (or extract) and re-use for their own purposes. Users can export the full layer from the ArcGIS Online item details page by clicking the Export Data button and selecting one of the supported formats (e.g. shapefile, or file geodatabase (FGDB)). User can extract selected layers for an area of interest by opening in Map Viewer, clicking the Analysis button, viewing the Manage Data tools, and using the Extract Data tool. To display this data with proper symbology and metadata in ArcGIS Pro, you can download and use this layer file.Data UsageThe data contributed through the Community Maps Editor app is primarily intended for use in the Esri Basemaps. Esri staff will periodically (e.g. weekly) review the contents of the contributed data and either accept or reject the data for use in the basemaps. Accepted features will be added to the Esri basemaps in a subsequent update and will remain in the app for the contributor or others to edit over time. Rejected features will be removed from the app.Esri Community Maps Contributors and other ArcGIS Online users can download accepted features from this layer for their internal use or map publishing, subject to the terms of use below.

This online repository consists if the data used for the BSc thesis/project of Ivo van Middelkoop. It consists of a ArcGIS Project file (ArcGIS Pro BSc Project 2022 Ivo van Middelkoop.aprx) and an Excel worksheet file (Excel data BSc Project 2022 Ivo van Middelkoop.xlsx). The ArcGIS Project file was used to create shapefiles through a sea-level fluctuation model to make maps about paleo coastline reconstructions. The Excel worksheet file was used to analyse the output data coming from the ArcGIS Project file. The topic of this BSc project: How did the sea-level rise following the Late Pleistocene impact the connectivity over time between Sumatra and Borneo?

This repository is openly accessible to everyone. The copyright is owned by Ivo van Middelkoop and Dr. Kenneth F. Rijsdijk

The U.S. Defense Department oversees the USA"s armed forces and manages over 30 million acres of land. With over 2.8 million service members and civilian employees the department is the world"s largest employer.Dataset SummaryPhenomenon Mapped: Lands managed by the U.S. Department of DefenseGeographic Extent: United States, Guam, Puerto RicoData Coordinate System: WGS 1984Visible Scale: The data is visible at all scalesSource: DOD Military Installations Ranges and Training Areas layer. Publication Date: May 2025This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Department of Defense lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "department of defense" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "department of defense" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.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.

The state of Tennessee is divided into 805 individual 7.5-minute topographic quadrangle maps. The Tennessee Department of Environment and Conservation (TDEC) maintains an archive of paper maps that were utilized for estimating groundwater well locations. Each well location was plotted by hand and marked with corresponding water well data. These hand-plotted locations represent the most accurate spatial information for each well but exist solely in paper format. To create the shapefile of the well location data for this data release, individual paper maps were scanned and georeferenced. From these georeferenced map images (GRI), the hand-plotted well locations were digitized into a shapefile of point data using ArcGIS Pro. The shapefile is contained in "TN_waterwell.zip," which contains locations for 8,826 points from the first 200 7.5-minute quadrangles in Tennessee (sorted alphabetically) from Adair 438NW through Harriman 123NE. While some spring locations are included in this dataset, it does not provide a comprehensive collection of spring data. Attribute data includes quad name, drawing number, and hand-written identification data that was transcribed from the topographic maps. Latitude and longitude coordinates (decimal degrees) were populated. Data projection is USA Contiguous Albers Equal Area Conic USGS (meters). A table of attribute data is included in this data release as "TN_waterwells_table.xlsx." Detailed descriptions of the attributes can be found in the accompanying metadata file named "TN_waterwells_metadata.xml."

The Climate Adaptation Science Centers (CASCs) partner with natural and cultural resource managers, tribes and indigenous communities, and university researchers to provide science that helps fish, wildlife, ecosystems, and the communities they support adapt to climate change. The CASCs provide managers and stakeholders with information and decision-making tools to respond to the effects of climate change. While each CASC works to address specific research priorities within their respective region, CASCs also collaborate across boundaries to address issues within shared ecosystems, watersheds, and landscapes. These shapefiles represent the 9 CASC regions and the national CASC that comprise the CASC network, highlighting the consortium institutions that make up each region.The shapefiles were produced in ArcGIS Pro but any geospatial software can be used to view the shapefiles (ArcGIS, QGIS, etc).

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

Karst is a landscape where the hydrology of surface water systems is intricately connected to groundwater systems through the development of conduits and solutional opening in soluble bedrock, such as limestone, marble, or dolomite. This connectivity can present challenges to preserving water quality and quantity for karst aquifers, as activities that occur in karst areas can often have a direct impact to groundwater quality. Agency personnel responsible for managing karst areas must understand the karst landscapes that drain to springs and caves to properly preserve groundwater quality. Oregon Caves National Monument and Preserve is in Josephine County, Oregon approximately 11 miles east of the community of Cave Junction. The Monument and Preserve protect 4,554 acres of conifer-dominated forests, meadows, streams, and multiple cave systems. From 2021 to 2024, the U.S. Geological Survey along with personnel from Oregon Caves National Monument and Preserve conducted a dye tracing investigation seeking to delineate recharge areas for two karst systems, Oregon Caves and Cave Next Door. Additionally, the study sought to determine if there were any hydrologic connections between these two karst systems. A total of eight dye injections were conducted, delineating a recharge area for each of the two karst systems, confirming hydrologic connections among different streams within the Oregon Caves system, and identifying previously undocumented resurgences for the stream in Oregon Caves. This data release contains shapefiles that relate to dye injection locations, monitoring sites, dye traces, and delineated recharge areas. All files were created in ArcGIS Pro and each shapefile contains associated attributes for the features contained within. Layer files are included with the datasets to match symbology found in figures in the accompanying report. All shapefiles and layer files were created and modified in ArcGIS software. For a full description of the methods to create these files, see Process Steps in "ORCA_Metdata.xml" metadata file.

The Digital Geologic-GIS Map of Mount Rainier National Park, Washington is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (mora_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (mora_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (mora_geology.gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (mora_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (mora_geology_metadata_faq.pdf). Please read the mora_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: http://www.google.com/earth/index.html. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (mora_geology_metadata.txt or mora_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:62,500 and United States National Map Accuracy Standards features are within (horizontally) 31.8 meters or 104.2 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm). The GIS data projection is NAD83, UTM Zone 10N, however, for the KML/KMZ format the data is projected upon export to WGS84 Geographic, the native coordinate system used by Google Earth.

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