This packaged data collection contains all of the outputs from our primary model, including the following data layers: Habitat Cores (vector polygons) Least-cost Paths (vector lines) Least-cost Corridors (raster) Least-cost Corridors (vector polygon interpretation) Modeling Extent (vector polygon) Please refer to the embedded spatial metadata and the information in our full report for details on the development of these data layers. Packaged data are available in two formats: Geodatabase (.gdb): A related set of file geodatabase rasters and feature classes, packaged in an ESRI file geodatabase. ArcGIS Pro Map Package (.mpkx): The same data included in the geodatabase, presented as fully-symbolized layers in a map. Note that you must have ArcGIS Pro version 2.0 or greater to view. See Cross-References for links to individual datasets, which can be downloaded in shapefile (.shp) or raster GeoTIFF (.tif) formats.

This packaged data collection contains two sets of two additional model runs that used the same inputs and parameters as our primary model, with the exception being we implemented a "maximum corridor length" constraint that allowed us to identify and visualize the corridors as being well-connected (≤15km) or moderately connected (≤45km). This is based on an assumption that corridors longer than 45km are too long to sufficiently accommodate dispersal. One of these sets is based on a maximum corridor length that uses Euclidean (straight-line) distance, while the other set is based on a maximum corridor length that uses cost-weighted distance. These two sets of corridors can be compared against the full set of corridors from our primary model to identify the remaining corridors, which could be considered poorly connected. This package includes the following data layers: Corridors classified as well connected (≤15km) based on Cost-weighted Distance Corridors classified as moderately connected (≤45km) based on Cost-weighted Distance Corridors classified as well connected (≤15km) based on Euclidean Distance Corridors classified as moderately connected (≤45km) based on Euclidean Distance Please refer to the embedded metadata and the information in our full report for details on the development of these data layers. Packaged data are available in two formats: Geodatabase (.gdb): A related set of file geodatabase rasters and feature classes, packaged in an ESRI file geodatabase. ArcGIS Pro Map Package (.mpkx): The same data included in the geodatabase, presented as fully-symbolized layers in a map. Note that you must have ArcGIS Pro version 2.0 or greater to view. See Cross-References for links to individual datasets, which can be downloaded in raster GeoTIFF (.tif) format.

This packaged data collection contains all of the outputs from our secondary model, which replaced habitat cores with the boundaries of the four existing coastal marten populations (known as Extant Population Areas, as defined in the USFWS Species Status Assessment v2.0) and used Linkage Mapper to produce corridors connecting these populations. This package includes the following data layers: Coastal Marten Extant Population Areas (EPAs) Least-cost Paths Connecting EPAs Least-cost Corridors Connecting EPAs Please refer to the embedded metadata and the information in our full report for details on the development of these data layers. Packaged data are available in two formats: Geodatabase (.gdb): A related set of file geodatabase rasters and feature classes, packaged in an ESRI file geodatabase. ArcGIS Pro Map Package (.mpkx): The same data included in the geodatabase, presented as fully-symbolized layers in a map. Note that you must have ArcGIS Pro version 2.0 or greater to view. See Cross-References for links to individual datasets, which can be downloaded in shapefile (.shp) or raster GeoTIFF (.tif) formats.

Homeowners in coastal environments often augment their access to estuarine ecosystems by building private docks on their personal property. Despite the commonality of docks, particularly in the Southeastern United States, few works have investigated their historical development, their distribution across the landscape, or the environmental justice dimensions of this distribution. In this study, we used historic aerial photography to track the abundance and size of docks across six South Carolina counties from the 1950s to 2016. Across our roughly 60-year study period, dock abundance grew by two orders of magnitude, the mean length of newly constructed docks doubled, and the cumulative length of docks ballooned from 34 to 560 km. Additionally, we drew on census data interpolated into consistent 2010 tract boundaries to analyze the racial and economic distribution of docks in 1994, 1999, 2011, and 2016. Racial composition, measured as the percentage of a tract’s population that was White,..., Dock data was collected via historic aerial imagery of the South Carolina coast. Pre-1990 imagery was obtained from the University of South Carolina library, 1994 and 1999 imagery was obtained from the South Carolina Department of Natural Resources, and 2011 imagery was obtained from the US Department of Agriculture National Agriculture Imagery Program’s Geospatial Data Gateway (https://nrcs.app.box.com/v/gateway/folder/19350726983). Census data was obtained from the NHGIS and Historical Housing Unit and Urbanization Database at the tract level using their crosswalk files to interpolate 1990 and 2000 data to 2010 tract geographies. Docks were tracked across decades in ArcGIS Pro and statistical models were run using R. Greater methodological detail is provided in the "Historic Infrastructure Methodology" file in the "Historic_Dock_Supplemental" folder on Zenodo. All pre-1990 images therein are reproduced with permission of the University of South Carolina library., R, ArcGIS Pro Version 2.9 or greater., # Exponential growth of private coastal infrastructure influenced by geography and race in South Carolina, USA

This data set contains ArcGIS Pro files and a CSV of every structure identified in the study. The code used to run the models can be found on the associated Zenodo page in the "Historic_Dock_Code" folder. Additional methodological information and model diagnostics can be found in the "Historic_Dock_Supplemental" folder on the associated Zenodo page. If you have any questions or requests please email Jeffrey Beauvais (he/him) at beauvais.work@gmail.com

Description of the Data and file structure

Parent folder: Historic_Dock_ArcPro_Files

Contains a geodatabase (.gdb file) with final point layers used in the analysis for dock counts, lengths, and geographic boundaries. Intermediate files were redundant and excluded but available upon request. Some folders within are empty and automatically generated by ArcGIS Pro when loading the p...

This packaged data collection contains all of the processed datasets that were used to develop the resistance surface used in our primary model. This package includes the following data layers: Roads Forested Land Cover (binned OGSI) Rivers Waterbodies Non-forested Land Cover (GNN ESLF Codes) Bays and Estuaries Potentially Suitable Land Cover on Serpentine Soils (used in post-processing of Resistance Surface) Please refer to the embedded metadata and the information in our full report for details on the acquisition and development of these data layers. Packaged data are available in two formats: Geodatabase (.gdb): A related set of file geodatabase rasters and feature classes, packaged in an ESRI file geodatabase. ArcGIS Pro Map Package (.mpkx): The same data included in the geodatabase, presented as fully-symbolized layers in a map. Note that you must have ArcGIS Pro version 2.0 or greater to view. See Cross-References for links to individual datasets, which can be downloaded in raster GeoTIFF (.tif) format.

This packaged data collection contains the two compiled input surfaces (habitat surface and resistance surface) that were used to derive habitat cores and movement corridors in our primary model. It also includes an intermediary dataset (moving window averages) that was produced by the Core Mapper tool in the process of producing habitat cores, as well as an intermediary dataset (movement cost surface) that was produced by the Linkage Mapper tool in the process of producing least-cost corridors. This package includes the following data layers: Resistance Surface Movement Cost Surface Habitat Surface Moving Window Averages A lookup table of resistance values is also included in this package. This spreadsheet contains a list of component raster data layers that were used to compile our resistance surface, the classes of data represented within each of these rasters, and the resistance value we assigned to each class. Please refer to the embedded metadata and the information in our full report for details on the development of these data layers. Packaged data are available in two formats: Geodatabase (.gdb): A related set of file geodatabase rasters and feature classes, packaged in an ESRI file geodatabase. ArcGIS Pro Map Package (.mpkx): The same data included in the geodatabase, presented as fully-symbolized layers in a map. Note that you must have ArcGIS Pro version 2.0 or greater to view. See Cross-References for links to individual datasets, which can be downloaded in raster GeoTIFF (.tif) format.

This packaged data collection contains additional "small" habitat cores that had a minimum size of 1 female marten home range (300ha), but were too small to meet the minimum size threshold of 5 female home ranges (1500ha) used to define cores in the Primary Model. This package includes the following data layers: Habitat Cores Greater Than 300ha (i.e. small cores and cores from primary model) Habitat Cores 300ha-1500ha (small cores only) Please refer to the embedded spatial metadata and the information in our full report for details on the development of these data layers. Packaged data are available in two formats: Geodatabase (.gdb): A related set of file geodatabase rasters and feature classes, packaged in an ESRI file geodatabase. ArcGIS Pro Map Package (.mpkx): The same data included in the geodatabase, presented as fully-symbolized layers in a map. Note that you must have ArcGIS Pro version 2.0 or greater to view. See Cross-References for links to individual datasets, which can be downloaded in shapefile (.shp) format.

This data contains general information about Pedestrian Network in Hong Kong. Pedestrian Network is a set of 3D line features derived from road features and road furniture from Lands Department and Transport Department. A number of attributes are associated with the pedestrian network such as spatially related street names. Besides, the pedestrian network includes information like wheelchair accessibility and obstacles to facilitate the digital inclusion for the needy. Please refer to this video to learn how to use 3D Pedestrian Network Dataset in ArcGIS Pro to facilitate your transportation analysis.The data was provided in the formats of JSON, GML and GDB by Lands Department and downloaded via GEODATA.GOV.HK website.

The original data files were processed and converted into an Esri file geodatabase. Wheelchair accessibility, escalator/lift, staircase walking speed and street gradient were used to create and build a network dataset in order to demonstrate basic functions for pedestrian network and routing analysis in ArcMap and ArcGIS Pro. There are other tables and feature classes in the file geodatabase but they are not included in the network dataset, users have to consider the use of information based on their requirements and make necessary configurations. The coordinate system of this dataset is Hong Kong 1980 Grid.

The objectives of uploading the network dataset to ArcGIS Online platform are to facilitate our Hong Kong ArcGIS users to utilize the data in a spatial ready format and save their data conversion effort.

For details about the schema and information about the content and relationship of the data, please refer to the data dictionary provided by Lands Department at https://geodata.gov.hk/gs/download-datadict/201eaaee-47d6-42d0-ac81-19a430f63952.

For details about the data, source format and terms of conditions of usage, please refer to the website of GEODATA STORE at https://geodata.gov.hk.Dataset last updated on: 2022 Oct

This layer shows poverty status by age group. 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. Poverty status is based on income in past 12 months of survey. This layer is symbolized to show the percentage of the population whose income falls below the Federal poverty line. 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): B17020, C17002Data 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.