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

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 training samples were created and saved, the raster was then reclassified using the Image Classification Wizard tool in ArcGIS Pro, using the Support...

Mobile Map Packages (MMPK’s) can be used in the ESRI Field Maps app (no login required), either by direct download in the Field Maps app or by sideloading from your PC. They can also be used in desktop applications that support MMPK’s such as ArcGIS Pro, and ArcGIS Navigator. MMPK’s will expire quarterly and have a warning for the user at that time but will still function afterwards. They are updated quarterly to ensure you have the most up to date data possible.

These mobile map packages include the following national datasets along with others.

BLM Administrative Unit Boundaries & Points

BLM Public Land Survey System (PLSS)

TNM Place Names (Geographic Names)

BLM National Grazing Allotments

BLM Trails (GTLF)

BLM Recreation Point Features (RECS)

BLM Recreation Site Boundaries

BLM National Conservation Lands

BLM National Contours (TNM Derived)

BLM Surface Management Agency

ESRI Navigation Basemap Vector Tile Package (Modified)

Last updated 20250929. Contact BLM_Mobile_Apps@blm.gov with any questions, issues or suggestions.