The ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) Project Package includes all of the layers that are in the NTIA Permitting and Environmental Information Application as well as the APPEIT Tool which will allow users to input a project area and determine what layers from the application overlap with it. An overview of the project package and the APPEIT tool is provided below. User instructions on how to use the tool are available here. Instructions now include how to customize the tool by adding your own data. A video explaining how to use the Project Package is also available here. Project Package OverviewThis map package includes all of the layers from the NTIA Permitting and Environmental Information Application. The layers included are all feature services from various Federal and State agencies. The map package was created with ArcGIS Pro 3.4.0. The map package was created to allow users easy access to all feature services including symbology. The map package will allow users to avoid downloading datasets individually and easily incorporate into their own GIS system. The map package includes three maps.1. Permitting and Environmental Information Application Layers for GIS Analysis - This map includes all of the map tabs shown in the application, except State Data which is provided in another tab. This map includes feature services that can be used for analysis with other project layers such as a route or project area. 2. Permitting and Environmental Information Application Layers – For Reference Only - This map includes layers that cannot be used for analysis since they are either imagery or tile layers.3. State Data - Reference Only - This map includes all relevant state data that is shown in the application.The NTIA Permitting and Environmental Information Application was created to help with your permitting planning and environmental review preparation efforts by providing access to multiple maps from publicly available sources, including federal review, permitting, and resource agencies. The application should be used for informational purposes only and is intended solely to assist users with preliminary identification of areas that may require permits or planning to avoid potentially significant impacts to environmental resources subject to the National Environmental Policy Act (NEPA) and other statutory requirements. Multiple maps are provided in the application which are created from public sources. This application does not have an exhaustive list of everything you need for permitting or environmental review for a project but is an initial starting point to see what might be required.APPEIT Tool OverviewThe Department of Commerce’s National Telecommunications and Information Administration (NTIA) is providing the ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) to help federal broadband grant recipients and subgrantees identify permits and environmental factors as they plan routes for their broadband deployments. Identifying permit requirements early, initiating pre-application coordination with permitting agencies, and avoiding environmental impacts help drive successful infrastructure projects. NTIA’s public release of the APPEIT tool supports government-wide efforts to improve permitting and explore how online and digital technologies can promote efficient environmental reviews. This Esri ArcGIS Pro tool is included in the map package and was created to support permitting, planning, and environmental review preparation efforts by providing access to data layers from publicly available sources, including federal review, permitting, and resource agencies. An SOP on how to use the tool is available here. For the full list of APPEIT layers, see Appendix Table 1 in the SOP. The tool is comprised of an ArcGIS Pro Project containing a custom ArcGIS Toolbox tool, linked web map shared by the NTIA’s National Broadband Map (NBAM), a report template, and a Tasks item to guide users through using the tool. This ArcGIS Pro project and its contents (maps and data) are consolidated into this (.ppkx) project file. To use APPEIT, users will input a project area boundary or project route line in a shapefile or feature class format. The tool will return as a CSV and PDF report that lists any federal layers from the ArcGIS Pro Permitting and Environmental Information Web Map that intersect the project. Users may only input a single project area or line at a time; multiple projects or project segments will need to be screened separately. For project route lines, users are required to specify a buffer distance. The buffer distance that is used for broadband projects should be determined by the area of anticipated impact and should generally not exceed 500 feet. For example, the State of Maryland recommends a 100-foot buffer for broadband permitting. The tool restricts buffers to two miles to ensure relevant results. DisclaimerThis document is intended solely to assist federal broadband grant recipients and subgrantees in better understanding Infrastructure Investment and Jobs Act (IIJA) broadband grant programs and the requirements set forth in the Notice of Funding Opportunity (NOFO) for this program. This document does not and is not intended to supersede, modify, or otherwise alter applicable statutory or regulatory requirements, the terms and conditions of the award, or the specific application requirements set forth in the NOFO. In all cases, statutory and regulatory mandates, the terms and conditions of the award, the requirements set forth in the NOFO, and follow-on policies and guidance, shall prevail over any inconsistencies contained in this document. NTIA’s ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) should be used for informational purposes only and is intended solely to assist users with preliminary identification of broadband deployments that may require permits or planning to avoid potentially significant impacts to environmental resources subject to the National Environmental Policy Act (NEPA) and other statutory requirements. The tool is not an exhaustive or complete resource and does not and is not intended to substitute for, supersede, modify, or otherwise alter any applicable statutory or regulatory requirements, or the specific application requirements set forth in any NTIA NOFO, Terms and Conditions, or Special Award Condition. In all cases, statutory and regulatory mandates, and the requirements set forth in NTIA grant documents, shall prevail over any inconsistencies contained in these templates. The tool relies on publicly available data available on the websites of other federal, state, local, and Tribal agencies, and in some instances, private organizations and research institutions. Layers identified with a double asterisk include information relevant to determining if an “extraordinary circumstance” may warrant more detailed environmental review when a categorical exclusion may otherwise apply. While NTIA continues to make amendments to its websites to comply with Section 508, NTIA cannot ensure Section 508 compliance of federal and non-federal websites or resources users may access from links on NTIA websites. All data is presented “as is,” “as available” for informational purposes. NTIA does not warrant the accuracy, adequacy, or completeness of this information and expressly disclaims liability for any errors or omissions. Please e-mail NTIAanalytics@ntia.gov with any questions.

This dataset provides comprehensive information on road intersection pedestrian crashes recognised as "high-low" outliers within the City of Cape Town. It includes detailed records of all intersection crashes and their corresponding crash attribute combinations, which were prevalent in at least 10% of the total "high-low" outlier pedestrian road intersection crashes for the years 2017, 2018, 2019, and 2021. The dataset is meticulously organised according to support metric values, ranging from 0,10 to 0,021, with entries presented in descending order.Data SpecificsData Type: Geospatial-temporal categorical dataFile Format: Excel document (.xlsx)Size: 37,8 KBNumber of Files: The dataset contains a total of 624 association rulesDate Created: 24th May 2024MethodologyData Collection Method: The descriptive road traffic crash data per crash victim involved in the crashes was obtained from the City of Cape Town Network InformationSoftware: ArcGIS Pro, PythonProcessing Steps: Following the spatio-temporal analyses and the derivation of "high-low" outlier fishnet grid cells from a cluster and outlier analysis, all the road intersection pedestrian crashes that occurred within the "high-low" outlier fishnet grid cells were extracted to be processed by association analysis. The association analysis of these crashes was processed using Python software and involved the use of a 0,10 support metric value. Consequently, commonly occurring crash attributes among at least 10% of the "high-low" outlier road intersection pedestrian crashes were extracted for inclusion in this dataset.Geospatial InformationSpatial Coverage:West Bounding Coordinate: 18°20'EEast Bounding Coordinate: 19°05'ENorth Bounding Coordinate: 33°25'SSouth Bounding Coordinate: 34°25'SCoordinate System: South African Reference System (Lo19) using the Universal Transverse Mercator projectionTemporal InformationTemporal Coverage:Start Date: 01/01/2017End Date: 31/12/2021 (2020 data omitted)

This dataset provides comprehensive information on road intersection crashes recognised as "high-high" clusters within the City of Cape Town. It includes detailed records of all intersection crashes and their corresponding crash attribute combinations, which were prevalent in at least 5% of the total "high-high" cluster road intersection crashes for the years 2017, 2018, 2019, and 2021. The dataset is meticulously organised according to support metric values, ranging from 0,05 to 0,0235, with entries presented in descending order.Data SpecificsData Type: Geospatial-temporal categorical dataFile Format: Excel document (.xlsx)Size: 499 KBNumber of Files: The dataset contains a total of 7186 association rulesDate Created: 23rd May 2024MethodologyData Collection Method: The descriptive road traffic crash data per crash victim involved in the crashes was obtained from the City of Cape Town Network InformationSoftware: ArcGIS Pro, PythonProcessing Steps: Following the spatio-temporal analyses and the derivation of "high-high" cluster fishnet grid cells from a cluster and outlier analysis, all the road intersection crashes that occurred within the "high-high" cluster fishnet grid cells were extracted to be processed by association analysis. The association analysis of these crashes was processed using Python software and involved the use of a 0,05 support metric value. Consequently, commonly occurring crash attributes among at least 5% of the "high-high" cluster road intersection crashes were extracted for inclusion in this dataset.Geospatial InformationSpatial Coverage:West Bounding Coordinate: 18°20'EEast Bounding Coordinate: 19°05'ENorth Bounding Coordinate: 33°25'SSouth Bounding Coordinate: 34°25'SCoordinate System: South African Reference System (Lo19) using the Universal Transverse Mercator projectionTemporal InformationTemporal Coverage:Start Date: 01/01/2017End Date: 31/12/2021 (2020 data omitted)

The data illustrates the expanded “Urbanized Area” for the Municipal Separate Storm Sewer System (MS4) program from the 2020 census data. "Urbanized area" means a place and the adjacent densely populated territory that together have a minimum population of 50,000 people, as defined by the United States bureau of the census and as determined by the latest available decennial census. The data is provided to the Michigan Department of Environment, Great Lakes, and Energy (EGLE) by the United States Environmental Protection Agency. The urbanized area is the regulated area for municipalities that are regulated under the MS4 program, including but not limited to cities, township, and villages."2020 Census Populations of 50K or more" and "Automatically Designated Areas" was provided by US EPA in July 2023 and combined with Michigan Open GIS Data (Minor Civil Divisions: Cities, Townships and Villages) using ESRI's ArcGIS Pro Software. Tools used include Pairwise Intersect, Merge, Pairwise Erase, and manual editing to combine the two layers.Please contact the individuals below with any questions.Christe Alwin: ALWINC@michigan.gov (point of contact)Patrick Klein: kleinp3@michigan.gov (creator)FIELD NAMEDESCRIPTIONNameShort name of the municipality (Lansing)LabelThe municipalities full name (City of Lansing)TypeThe type of municipality (city, township, or village)SQMILEArea of the shape in Square MilesACRESArea of the shape in AcresPublished in June 2024. Learn more about EGLE's Municipal Storm Water Program.Additional information describing Part 21 Wastewater Discharge Permits.

The data illustrates the “Urbanized Area” for the Municipal Separate Storm Sewer System (MS4) program from the 2010 census. "Urbanized area" means a place and the adjacent densely populated territory that together have a minimum population of 50,000 people, as defined by the United States bureau of the census and as determined by the latest available decennial census. The data is provided to the Michigan Department of Environment, Great Lakes, and Energy (EGLE) by the United States Environmental Protection Agency. The urbanized area is the regulated area for municipalities that are regulated under the MS4 program, including but not limited to cities, township, and villages."2020 Census Populations of 50K or more" and "Automatically Designated Areas" was provided by US EPA in July 2023 and combined with Michigan Open GIS Data (Minor Civil Divisions: Cities, Townships and Villages) using ESRI's ArcGIS Pro Software. Tools used include Pairwise Intersect, Merge, Pairwise Erase, and manual editing to combine the two layers.Please contact the individuals below with any questions.Christe Alwin: ALWINC@michigan.gov (point of contact)Patrick Klein: kleinp3@michigan.gov (creator)

FIELD NAME

DESCRIPTION

Name

Short name of the municipality (Lansing)

Label

The municipalities full name (City of Lansing)

Type

The type of municipality (city, township, or village)

SQMILEArea of the shape in Square Miles

ACRES

Area of the shape in Acres

Published in June 2024. Learn more about EGLE's Municipal Storm Water Program.Additional information describing Part 21 Wastewater Discharge Permits.

This dataset provides comprehensive information on unsignalled road intersection crashes recognised as "high-low" clusters within the City of Cape Town. It includes detailed records of all intersection crashes and their corresponding crash attribute combinations, which were prevalent in at least 10% of the total "high-high" cluster unsignalled road intersection crashes resulting for the years 2017, 2018 and 2019. The dataset is meticulously organised according to support metric values, ranging from 0,10 to 0,223, with entries presented in descending order.Data SpecificsData Type: Geospatial-temporal categorical dataFile Format: Excel document (.xlsx)Size: 57,4 KB Number of Files: The dataset contains a total of 1050 association rulesDate Created: 24th May 2024MethodologyData Collection Method: The descriptive road traffic crash data per crash victim involved in the crashes was obtained from the City of Cape Town Network InformationSoftware: ArcGIS Pro, PythonProcessing Steps: Following the spatio-temporal analyses and the derivation of "high-low" outlier fishnet grid cells from a cluster and outlier analysis, all the unsignalled road intersection crashes that occurred within the "high-low" outlier fishnet grid cells were extracted to be processed by association analysis. The association analysis of these crashes was processed using Python software and involved the use of a 0,05 support metric value. Consequently, commonly occurring crash attributes among at least 10% of the "high-low" outlier unsignalled road intersection crashes were extracted for inclusion in this dataset.Geospatial InformationSpatial Coverage:West Bounding Coordinate: 18°20'EEast Bounding Coordinate: 19°05'ENorth Bounding Coordinate: 33°25'SSouth Bounding Coordinate: 34°25'SCoordinate System: South African Reference System (Lo19) using the Universal Transverse Mercator projectionTemporal InformationTemporal Coverage:Start Date: 01/01/2017End Date: 31/12/2019

This dataset provides comprehensive information on road intersection pedestrian crashes recognised as "high-high" clusters within the City of Cape Town. It includes detailed records of all intersection crashes and their corresponding crash attribute combinations, which were prevalent in at least 10% of the total "high-high" cluster pedestrian road intersection crashes for the years 2017, 2018, 2019, and 2021.The dataset is meticulously organised according to support metric values, ranging from 0,10 to 0,13, with entries presented in descending order.Data SpecificsData Type: Geospatial-temporal categorical dataFile Format: Excel document (.xlsx)Size: 15,0 KBNumber of Files: The dataset contains a total of 162 association rulesDate Created: 24th May 2024MethodologyData Collection Method: The descriptive road traffic crash data per crash victim involved in the crashes was obtained from the City of Cape Town Network InformationSoftware: ArcGIS Pro, PythonProcessing Steps: Following the spatio-temporal analyses and the derivation of "high-high" cluster fishnet grid cells from a cluster and outlier analysis, all the road intersection pedestrian crashes that occurred within the "high-high" cluster fishnet grid cells were extracted to be processed by association analysis. The association analysis of these crashes was processed using Python software and involved the use of a 0,10 support metric value. Consequently, commonly occurring crash attributes among at least 10% of the "high-high" cluster road intersection pedestrian crashes were extracted for inclusion in this dataset.Geospatial InformationSpatial Coverage:West Bounding Coordinate: 18°20'EEast Bounding Coordinate: 19°05'ENorth Bounding Coordinate: 33°25'SSouth Bounding Coordinate: 34°25'SCoordinate System: South African Reference System (Lo19) using the Universal Transverse Mercator projectionTemporal InformationTemporal Coverage:Start Date: 01/01/2017End Date: 31/12/2021 (2020 data omitted)

AnalysisFEMA's National Flood Hazard Layer (NFHL) and the CDC's Social Vulnerability Index (SVI) were cross referenced to produce a Place Vulnerability Analysis for Hudson County, NJ. Using ArcGIS Pro, the location of interest (Hudson County) was first determined and the Flood Hazard and SVI layers were clipped to this extent. A new feature class, intersecting the two, was then created using the Intersect Tool. The output of this process was the Hudson County Place Vulnerability Layer. Additional Layers were added to the map to assess important special needs infrastructure, community lifelines, and additional hazard risks within the most vulnerable areas of the county.LayersWildfire Hazard Potential: Shows the average wildfire hazard potential for the US on a scale of 1-5. The layer was obtained using ESRI's Living Atlas. Source: https://napsg.maps.arcgis.com/home/item.html?id=ce92e9a37f27439082476c369e2f4254 NOAA Storm Events Database 1950-2021: Shares notable storm events throughout the US recorded by NOAA between the years of 1950-2021. The layer was obtained using ESRI's Living Atlas. Source: https://gisanddata.maps.arcgis.com/home/item.html?id=88cc0d5e55f343c28739af1a091dfc91 Category 1 Hurricane Storm Surge: Includes the expected Inundation Height of areas within the US should a Category 1 Hurricane hit the area. The layer was obtained using the ArcGIS Online Portal. Source: https://gisanddata.maps.arcgis.com/home/item.html?id=49badb9332f14079b69cfa49b56809dc Category 2 Hurricane Storm Surge: Includes the expected Inundation Height of areas within the US should a Category 2 Hurricane hit the area. The layer was obtained using the ArcGIS Online Portal. Source: https://gisanddata.maps.arcgis.com/home/item.html?id=b4e4f410fe9746d5898d98bb7467c1c2 Category 3 Hurricane Storm Surge: Includes the expected Inundation Height of areas within the US should a Category 3 Hurricane hit the area. The layer was obtained using the ArcGIS Online Portal. Source: https://gisanddata.maps.arcgis.com/home/item.html?id=876a38efe537489fb3bc6b490519117f U.S. Sea Level Rise Projections: Shows different sea level rise projections within the United States. The layer was obtained via ESRI's Living Atlas. Source: https://gisanddata.maps.arcgis.com/home/item.html?id=8943e6e91c304ba2997d83b597e32861Power Plants: Includes all New Jersey power plants about 1 Megawatt capacity. The layer was obtained via the NJDEP Bureau of GIS website. Source: https://njdep.maps.arcgis.com/home/item.html?id=282eb9eb22cc40a99ed509a7aa9f7c90Solid & Hazardous Waste Facilities: Includes hazardous waste facilities, medical waste facilities, incinerators, recycling facilities, and landfill sites within New Jersey. Obtained via the NJDEP Bureau of GIS website. Source: https://njdep.maps.arcgis.com/home/item.html?id=896615180fb04d8eafda0df9df9a1d73Solid Waste Landfill Sites over 35 Acres: Includes solid waste landfill sites in New Jersey that are larger than 35 acres. Obtained via the NJDEP Bureau of GIS website. Source: https://gisanddata.maps.arcgis.com/home/item.html?id=2b4eab598df94ffabaa8d92e3e46deb4NJ Transit Rail Lines: A layer showing segments of the NJ Transit Rail System and terminals. Data was obtained via the NJ Transit GIS Department. Source: https://www.arcgis.com/home/item.html?id=e6701817be974795aecc7f7a8cc42f79Medical Emergency Response Structures: Contains emergency response centers within the U.S. based off National Geospatial Data Asset data from the U.S. Geological Survey. The layer was obtained using ESRI's Living Atlas. Source: https://gisanddata.maps.arcgis.com/home/item.html?id=2c36dbb008844081b017da6fd3d0d28bSchools: Shows the location of New Jersey schools, including public, private and charter schools. Obtained via the New Jersey Office of GIS. Source: https://njdep.maps.arcgis.com/home/item.html?id=d8223610010a4c3887cfb88b904545ffChild Care Centers: Shows the location of active child care centers in New Jersey. The layer was obtained via the NJ Bureau of GIS website. Source: https://njdep.maps.arcgis.com/home/item.html?id=0bc9fe070d4c49e1a6555c3fdea15b8aNursing Homes: A layer containing the locations of nursing homes and assisted care facilities in the United States. Obtained via the HIFLD website. Source: https://gisanddata.maps.arcgis.com/home/item.html?id=78c58035fb3942ba82af991bb4476f13cCDC's Social Vulnerability Index (SVI) - ATSDR's Geospatial Research, Analysis & Services Program (GRASP) has created a tool to help emergency response planners and public health officials identify and map the communities that will most likely need support before, during, and after a hazardous event. The Social Vulnerability Index (SVI) uses U.S. Census data to determine the social vulnerability of every census tract. The SVI ranks each census tract on 15 social factors, including poverty, lack of vehicle access, and crowded housing, and groups them into four related themes. Source: https://gisanddata.maps.arcgis.com/home/item.html?id=05709059044243ae9b42f469f0e06642

This dataset offers a detailed inventory of road intersections and their corresponding suburbs within Cape Town, meticulously curated to highlight instances of high pedestrian crash counts resulting in serious injuries observed in "high-high" cluster and "high-low" outlier fishnet grid cells across the years 2017, 2018 and 2019. To enhance its utility, the dataset meticulously colour-codes each month associated with elevated crash occurrences, providing a nuanced perspective. Furthermore, the dataset categorises road intersections based on their placement within "high-high" clusters (marked with pink tabs) or "high-low" outlier cells (indicated by red tabs). For ease of navigation, the intersections are further organised alphabetically by suburb name, ensuring accessibility and clarity.Data SpecificsData Type: Geospatial-temporal categorical data with numeric attributesFile Format: Word document (.docx)Size: 231 KBNumber of Files: The dataset contains a total of 245 road intersection records (7 "high-high" clusters and 238 "high-low" outliers)Date Created: 21st May 2024MethodologyData Collection Method: The descriptive road traffic crash data per crash victim involved in the crashes was obtained from the City of Cape Town Network InformationSoftware: ArcGIS Pro, Open Refine, Python, SQLProcessing Steps: The raw road traffic crash data underwent a comprehensive refining process using Python software to ensure its accuracy and consistency. Following this, duplicates were eliminated to retain only one entry per crash incident. Subsequently, the data underwent further refinement with Open Refine software, focusing specifically on isolating unique crash descriptions for subsequent geocoding in ArcGIS Pro. Notably, during this process, only the road intersection crashes were retained, as they were the only incidents with spatial definitions.Once geocoded, road intersection crashes that involved a pedestrian with a severe or fatal injury type were extracted so that subsequent spatio-temporal analyses would focus on these crashes only. The spatio-temporal analysis methods by which these pedestrian crashes were analysed included spatial autocorrelation, hotspot analysis, and cluster and outlier analysis. Leveraging these methods, road intersections with pedestrian crashes that resulted in a severe injury identified as either "high-high" clusters or "high-low" outliers were extracted for inclusion in the dataset.Geospatial InformationSpatial Coverage:West Bounding Coordinate: 18°20'EEast Bounding Coordinate: 19°05'ENorth Bounding Coordinate: 33°25'SSouth Bounding Coordinate: 34°25'SCoordinate System: South African Reference System (Lo19) using the Universal Transverse Mercator projectionTemporal InformationTemporal Coverage:Start Date: 01/01/2017End Date: 31/12/2019

This dataset offers a detailed inventory of road intersections and their corresponding suburbs within Cape Town, meticulously curated to highlight instances of high crash counts observed in "high-high" cluster and "high-low" outlier fishnet grid cells across the years 2017, 2018, 2019, and 2021. To enhance its utility, the dataset meticulously colour-codes each month associated with elevated crash occurrences, providing a nuanced perspective. Furthermore, the dataset categorises road intersections based on their placement within "high-high" clusters (marked with pink tabs) or "high-low" outlier cells (indicated by red tabs). For ease of navigation, the intersections are further organised alphabetically by suburb name, ensuring accessibility and clarity.Data SpecificsData Type: Geospatial-temporal categorical data with numeric attributesFile Format: Word document (.docx)Size: 602 KBNumber of Files: The dataset contains a total of 625 road intersection records (606 "high-high" cluster and 19 "high-low" outliers)Date Created: 21st May 2024MethodologyData Collection Method: The descriptive road traffic crash data per crash victim involved in the crashes was obtained from the City of Cape Town Network InformationSoftware: ArcGIS Pro, Open Refine, Python, SQLProcessing Steps: The raw road traffic crash data underwent a comprehensive refining process using Python software. Following this, duplicate crash records were eliminated to retain only one entry per crash. Subsequently, the data underwent further refinement with Open Refine software, focusing specifically on isolating unique crash descriptions for subsequent geocoding in ArcGIS Pro. Notably, during this process, only the road intersection crashes were retained, as they were the only crashes that were able to be spatially defined.Once geocoded, the road traffic crash data underwent rigorous spatio-temporal analyses, encompassing spatial autocorrelation, hotspot analysis, and cluster and outlier analysis. Leveraging these methods, road intersections identified as either "high-high" clusters or "high-low" outliers were extracted for inclusion in the dataset.Geospatial InformationSpatial Coverage:West Bounding Coordinate: 18°20'EEast Bounding Coordinate: 19°05'ENorth Bounding Coordinate: 33°25'SSouth Bounding Coordinate: 34°25'SCoordinate System: South African Reference System (Lo19) using the Universal Transverse Mercator projectionTemporal InformationTemporal Coverage:Start Date: 01/01/2017End Date: 31/12/2021 (2020 data omitted)

This dataset provides comprehensive information on road intersection crashes involving motorcycles (Motor tricycle, Motorcycle: under 125cc, Motorcycle: Above 125cc, Quadru-cycle) that have resulted in injuries recognised as "high-high" clusters within the City of Cape Town. It includes detailed records of all intersection crashes and their corresponding crash attribute combinations, which were prevalent in 33% of the total "high-high" cluster motorcycle road intersection crashes resulting in injuries for the years 2017, 2018, 2019, and 2021. Data SpecificsData Type: Geospatial-temporal categorical dataFile Format: Excel document (.xlsx)Size: 37,4 KBNumber of Files: The dataset contains a total of 576 association rulesDate Created: 23rd May 2024MethodologyData Collection Method: The descriptive road traffic crash data per crash victim involved in the crashes was obtained from the City of Cape Town Network InformationSoftware: ArcGIS Pro, PythonProcessing Steps: Following the spatio-temporal analyses and the derivation of "high-high" cluster fishnet grid cells from a cluster and outlier analysis, all the road intersection crashes involving a motorcycle resulting in injuries that occurred within the "high-high" cluster fishnet grid cells were extracted to be processed by association analysis. The association analysis of the "high-high" cluster road intersection motorcycle crashes was processed using Python software and involved the use of a 0,30 support metric value. Consequently, commonly occurring crash attributes among at least 33% of the "high-high" cluster road intersection motorcycle crashes resulting in injuries were extracted for inclusion in this dataset.Geospatial InformationSpatial Coverage:West Bounding Coordinate: 18°20'EEast Bounding Coordinate: 19°05'ENorth Bounding Coordinate: 33°25'SSouth Bounding Coordinate: 34°25'SCoordinate System: South African Reference System (Lo19) using the Universal Transverse Mercator projectionTemporal InformationTemporal Coverage:Start Date: 01/01/2017End Date: 31/12/2021 (2020 data omitted)

Reason for SelectionProtected natural areas in urban environments provide urban residents a nearby place to connect with nature and offer refugia for some species. Because beaches in Puerto Rico and the U.S. Virgin Islands are open to the public, beaches also provide important outdoor recreation opportunities for urban residents, so we include beaches as parks in this indicator.Input DataSoutheast Blueprint 2023 subregions: CaribbeanSoutheast Blueprint 2023 extentNational Oceanic and Atmospheric Administration (NOAA) National Centers for Environmental Information (NCEI) Coastal Relief Model, accessed 11-22-2022Protected Areas Database of the United States (PAD-US) 3.0: VI, PR, and Marine Combined Fee EasementPuerto Rico Protected Natural Areas 2018 (December 2018 update): Terrestrial and marine protected areas (PACAT2018_areas_protegidasPR_TERRESTRES_07052019.shp, PACAT2018_areas_protegidasPR_MARINAS_07052019.shp) 2020 Census Urban Areas from the Census Bureau’s urban-rural classification; download the data, read more about how urban areas were redefined following the 2020 censusOpenStreetMap data “multipolygons” layer, accessed 3-14-2023A polygon from this dataset is considered a park if the “leisure” tag attribute is either “park” or “nature_reserve”, and considered a beach if the value in the “natural” tag attribute is “beach”. OpenStreetMap describes leisure areas as “places people go in their spare time” and natural areas as “a wide variety of physical geography, geological and landcover features”. Data were downloaded in .pbf format and translated ton an ESRI shapefile using R code. OpenStreetMap® is open data, licensed under the Open Data Commons Open Database License (ODbL) by the OpenStreetMap Foundation (OSMF). Additional credit to OSM contributors. Read more on the OSM copyright page. TNC Lands - Public Layer, accessed 3-8-2023U.S. Virgin Islands beaches layer (separate vector layers for St. Croix, St. Thomas, and St. John) provided by Joe Dwyer with Lynker/the NOAA Caribbean Climate Adaptation Program on 3-3-2023 (contact jdwyer@lynker.com for more information)Mapping StepsMost mapping steps were completed using QGIS (v 3.22) Graphical Modeler.Fix geometry errors in the PAD-US PR data using Fix Geometry. This must be done before any analysis is possible.Merge the terrestrial PR and VI PAD-US layers.Use the NOAA coastal relief model to restrict marine parks (marine polygons from PAD-US and Puerto Rico Protected Natural Areas) to areas shallower than 10 m in depth. The deep offshore areas of marine parks do not meet the intent of this indicator to capture nearby opportunities for urban residents to connect with nature.Merge into one layer the resulting shallow marine parks from marine PAD-US and the Puerto Rico Protected Natural Areas along with the combined terrestrial PAD-US parks, OpenStreetMap, TNC Lands, and USVI beaches. Omit from the Puerto Rico Protected Areas layer the “Zona de Conservación del Carso”, which has some policy protections and conservation incentives but is not formally protected.Fix geometry errors in the resulting merged layer using Fix Geometry.Intersect the resulting fixed file with the Caribbean Blueprint subregion.Process all multipart polygons to single parts (referred to in Arc software as an “explode”). This helps the indicator capture, as much as possible, the discrete units of a protected area that serve urban residents.Clip the Census urban area to the Caribbean Blueprint subregion.Select all polygons that intersect the Census urban extent within 1.2 miles (1,931 m). The 1.2 mi threshold is consistent with the average walking trip on a summer day (U.S. DOT 2002) used to define the walking distance threshold used in the greenways and trails indicator. Note: this is further than the 0.5 mi distance used in the continental version of the indicator. We extended it to capture East Bay and Point Udall based on feedback from the local conservation community about the importance of the park for outdoor recreation.Dissolve all the park polygons that were selected in the previous step.Process all multipart polygons to single parts (“explode”) again.Add a unique ID to the selected parks. This value will be used to join the parks to their buffers.Create a 1.2 mi (1,931 m) buffer ring around each park using the multiring buffer plugin in QGIS. Ensure that “dissolve buffers” is disabled so that a single 1.2 mi buffer is created for each park.Assess the amount of overlap between the buffered park and the Census urban area using overlap analysis. This step is necessary to identify parks that do not intersect the urban area, but which lie within an urban matrix. This step creates a table that is joined back to the park polygons using the UniqueID.Remove parks that had ≤2% overlap with the urban areas when buffered. This excludes mostly non-urban parks that do not meet the intent of this indicator to capture parks that provide nearby access for urban residents. Note: In the continental version of this indicator, we used a threshold of 10%. In the Caribbean version, we lowered this to 2% in order to capture small parks that dropped out of the indicator when we extended the buffer distance to 1.2 miles.Calculate the GIS acres of each remaining park unit using the Add Geometry Attributes function.Join the buffer attribute table to the previously selected parks, retaining only the parks that exceeded the 2% urban area overlap threshold while buffered. Buffer the selected parks by 15 m. Buffering prevents very small parks and narrow beaches from being left out of the indicator when the polygons are converted to raster.Reclassify the polygons into 7 classes, seen in the final indicator values below. These thresholds were informed by park classification guidelines from the National Recreation and Park Association, which classify neighborhood parks as 5-10 acres, community parks as 30-50 acres, and large urban parks as optimally 75+ acres (Mertes and Hall 1995).Export the final vector file to a shapefile and import to ArcGIS Pro.Convert the resulting polygons to raster using the ArcPy Polygon to Raster function. Assign values to the pixels in the resulting raster based on the polygon class sizes of the contiguous park areas.Clip to the Caribbean Blueprint 2023 subregion.As a final step, clip to the spatial extent of Southeast Blueprint 2023. Note: For more details on the mapping steps, code used to create this layer is available in the Southeast Blueprint Data Download under > 6_Code. Final indicator valuesIndicator values are assigned as follows:6 = 75+ acre urban park5 = >50 to <75 acre urban park4 = 30 to <50 acre urban park3 = 10 to <30 acre urban park2 = 5 to <10 acre urban park1 = <5 acre urban park0 = Not identified as an urban parkKnown IssuesThis indicator does not include park amenities that influence how well the park serves people and should not be the only tool used for parks and recreation planning. Park standards should be determined at a local level to account for various community issues, values, needs, and available resources. This indicator includes some protected areas that are not open to the public and not typically thought of as “parks”, like mitigation lands, private easements, and private golf courses. While we experimented with excluding them using the public access attribute in PAD, due to numerous inaccuracies, this inadvertently removed protected lands that are known to be publicly accessible. As a result, we erred on the side of including the non-publicly accessible lands.This indicator includes parks and beaches from OpenStreetMap, which is a crowdsourced dataset. While members of the OpenStreetMap community often verify map features to check for accuracy and completeness, there is the potential for spatial errors (e.g., misrepresenting the boundary of a park) or incorrect tags (e.g., labelling an area as a park that is not actually a park). However, using a crowdsourced dataset gives on-the-ground experts, Blueprint users, and community members the power to fix errors and add new parks to improve the accuracy and coverage of this indicator in the future.Other Things to Keep in MindThis indicator calculates the area of each park using the park polygons from the source data. However, simply converting those park polygons to raster results in some small parks and narrow beaches being left out of the indicator. To capture those areas, we buffered parks and beaches by 15 m and applied the original area calculation to the larger buffered polygon, so as not to inflate the area by including the buffer. As a result, when the buffered polygons are rasterized, the final indicator has some areas of adjacent pixels that receive different scores. While these pixels may appear to be part of one contiguous park or suite of parks, they are scored differently because the park polygons themselves are not actually contiguous. The Caribbean version of this indicator uses a slightly different methodology than the continental Southeast version. It includes parks within a 1.2 mi distance from the Census urban area, compared to 0.5 mi in the continental Southeast. We extended it to capture East Bay and Point Udall based on feedback from the local conservation community about the importance of the park for outdoor recreation. Similarly, this indicator uses a 2% threshold of overlap between buffered parks and the Census urban areas, compared to a 10% threshold in the continental Southeast. This helped capture small parks that dropped out of the indicator when we extended the buffer distance to 1.2 miles. Finally, the Caribbean version does not use the impervious surface cutoff applied in the continental Southeast because the landcover data available in the Caribbean does not assess percent impervious in a comparable way.Disclaimer: Comparing with Older Indicator VersionsThere are numerous problems with using Southeast Blueprint