Have you ever wanted to create your own maps, or integrate and visualize spatial datasets to examine changes in trends between locations and over time? Follow along with these training tutorials on QGIS, an open source geographic information system (GIS) and learn key concepts, procedures and skills for performing common GIS tasks – such as creating maps, as well as joining, overlaying and visualizing spatial datasets. These tutorials are geared towards new GIS users. We’ll start with foundational concepts, and build towards more advanced topics throughout – demonstrating how with a few relatively easy steps you can get quite a lot out of GIS. You can then extend these skills to datasets of thematic relevance to you in addressing tasks faced in your day-to-day work.

Initial Data Capture: Building were originally digitized using ESRI construction tools such as rectangle and polygon. Textron Feature Analyst was then used to digitize buildings using a semi-automated polygon capture tool as well as a fully automated supervised learning method. The method that proved to be most effective was the semi-automated polygon capture tool as the fully automated process produced polygons that required extensive cleanup. This tool increased the speed and accuracy of digitizing by 40%.Purpose of Data Created: To supplement our GIS viewers with a searchable feature class of structures within Ventura County that can aid in analysis for multiple agencies and the public at large.Types of Data Used: Aerial Imagery (Pictometry 2015, 9inch ortho/oblique, Pictometry 2018, 6inch ortho/oblique) Simi Valley Lidar Data (Q2 Harris Corp Lidar) Coverage of Data:Buildings have been collected from the aerial imageries extent. The 2015 imagery coverage the south county from the north in Ojai to the south in thousand oaks, to the east in Simi Valley, and to the West in the county line with Santa Barbara. Lockwood Valley was also captured in the 2015 imagery. To collect buildings for the wilderness areas we needed to use the imagery from 2007 when we last flew aerial imagery for the entire county. 2018 Imagery was used to capture buildings that were built after 2015.Schema: Fields: APN, Image Date, Image Source, Building Type, Building Description, Address, City, Zip, Data Source, Parcel Data (Year Built, Basement yes/no, Number of Floors) Zoning Data (Main Building, Out Building, Garage), First Floor Elevation, Rough Building Height, X/Y Coordinates, Dimensions. Confidence Levels/Methods:Address data: 90% All Buildings should have an address if they appear to be a building that would normally need an address (Main Residence). To create an address, we do a spatial join on the parcels from the centroid of a building polygon and extract the address data and APN. To collect the missing addresses, we can do a spatial join between the master address and the parcels and then the parcels back to the building polygons. Using a summarize to the APN field we will be able to identify the parcels that have multiple buildings and delete the address information for the buildings that are not a main residence.Building Type Data: 99% All buildings should have a building type according to the site use category code provided from the parcel table information. To further classify multiple buildings on parcels in residential areas, the shape area field was used to identify building polygons greater than 600 square feet as an occupied residence and all other buildings less than that size as outbuildings. All parcels, inparticular parcels with multiple buildings, are subject to classification error. Further defining could be possible with extensive quality control APN Data: 98% All buildings have received APN data from their associated parcel after a spatial join was performed. Building overlapping parcel lines had their centroid derived which allowed for an accurate spatial join.Troubleshooting Required: Buildings would sometimes overlap parcel lines making spatial joining inaccurate. To fix this you create a point from the centroid of the building polygon, join the parcel information to the point, then join the point with the parcel information back to the building polygon.

Visit this website for an explanation of the parcel's assessing info: https://www.mass.gov/info-details/massgis-data-property-tax-parcels#attributes-Through a series of joins, spatial joins and select by location with various datasets, the following key attribute fields were populated in the Municipal Properties dataset.Open Space/Conservation Land Attributes are: OS_ID OS_ID is a unique ID for polygons in the open space/conservation land database, [Fee_Owner], [Level_Protection], OLI_1_INT. For an explanation of the coded values used in these fields, visit: https://www.mass.gov/info-details/massgis-data-protected-and-recreational-openspace#attributes-Zoning info for the parcel is contained within [ZONECODE], [MinLot_ac], and [SubStd_Sz]. Zonecode assigned to a parcel is based on the location of the center point of the parcel. The minimum lot size is per the Town's zoning bylaws. Parcel's smaller than the bylaws minimum lot size were assigned a 'yes' value in the Substandard Size attribute column.The attribute [vacant] was assigned a 'yes' value if the assessor's Building Value > $0.00 for the parcel OR the parcel contained one or more structures per the MassGIS structures dataset.The attribute [conserved] was assigned a 'yes' value if the parcel's center point coincided with a parcel in the Dukes County Open Space & Conservation Land dataset.The attribute [AbutPot] Abutter Potential is assigned a 'yes' value if any of the following attributes contain a 'yes' value: [AbutMuni], [AbutOS], or [AbutVacPrv].The attribute [Notes] were manually added by the GIS staff based on local knowledge.Attributes dealing with Abutters: [AbutMuni] indicates if the municipal owned parcel abuts other municipally owned parcels. 'Abuts' are any parcels that thouch (share a boundary) or are within 40ft of each other. [AbutOS] indicates if the municipal owned parcel abuts a parcel which is open space/conservation land. [AbutVacPrv] indicates if the municipal owned parcel abuts a parcel which is vacant residential land. "Vacant Residential Land" was identified by the assessor's Use Code = 1300 or 1310 for the parcel.Identifying Neighbors: All municipal parcels were buffered 40ft and dissolved together. Then that resulting multi-part dataset was 'exploded' so each distinct polygon was represented by a distinct record in the attribute table. Each polygon was assigned an ID number. This output is the "Municipal Property Clusters".Via a Spatial Join, the respective Cluster (aka group ID) was assigned to the respective municipal parcel. Similarly, by finding the (a) Vacant Residential properties and (b) Conservation Land properties that intersected with the Municipal Property Clusters, the Cluster/Group ID was assigned to the respective vacant residential properties and conservation land properties. A & B each have a distinct dataset which is included in this bundle of data.By having the Group ID in the Municipal Properties dataset and the Vacant Residential and Conservation Land datasets ...let's say a parcel has a Group ID = 3 --> then you can find the abutters by finding the other Municipal Parcels with a Group ID = 3 AND look in the Vacant Residential attribute table for Group ID = 3 AND look in the Conservation Land attribute table for Group ID = 3 --AND then you have tons of info at your fingertips regarding that municipally owned parcel and its abutting vacant properties.

Several previously published reports and geographic information system (GIS) data layers were used to code information on site attributes for each assessment plot using the spatial join tool in ArcMap. This information was used for an analysis of dieback and non-dieback habitat characteristics. The results of this analysis are presented in this table which depicts the probability of heavy to severe canopy dieback occurring at some time at a particular 30 x 30 m pixel location within the study area.

This shapefile provides a worldwide geographic division by merging the World Continents division proposed by Esri Data and Maps (2024) to the Global Oceans and Seas version 1 division proposed by the Flanders Marine Institute (2021). Though divisions of continents and oceans/seas are available, the combination of both in a single shapefile is scarce.

The Continents and Oceans/Seas shapefile was carefully processed to remove overlaps between the inputs, and to fill gaps (i.e., areas with no information) by spatially joining these gaps to neighbour polygons. In total, the original world continents input divides land areas into 8 categories (Africa, Antarctica, Asia, Australia, Europe, North America, Oceania, and South America), while the original oceans/seas input divides the oceans/seas into 10 categories (Arctic Ocean, Baltic Sea, Indian Ocean, Mediterranean Region, North Atlantic Ocean, North Pacific Ocean, South Atlantic Ocean, South China and Easter Archipelagic Seas, South Pacific Ocean, and Southern Ocean). Therefore, the resulting world geographic division has 18 possible categories.

References

Esri Data and Maps (2024). World Continents. Available online at https://hub.arcgis.com/datasets/esri::world-continents/about. Accessed on 05 March 2024.

Flanders Marine Institute (2021). Global Oceans and Seas, version 1. Available online at https://www.marineregions.org/. https://doi.org/10.14284/542. Accessed on 04 March 2024.

This specialized location dataset delivers detailed information about marina establishments. Maritime industry professionals, coastal planners, and tourism researchers can leverage precise location insights to understand maritime infrastructure, analyze recreational boating landscapes, and develop targeted strategies.

How Do We Create Polygons? -All our polygons are manually crafted using advanced GIS tools like QGIS, ArcGIS, and similar applications. This involves leveraging aerial imagery and street-level views to ensure precision. -Beyond visual data, our expert GIS data engineers integrate venue layout/elevation plans sourced from official company websites to construct detailed indoor polygons. This meticulous process ensures higher accuracy and consistency. -We verify our polygons through multiple quality checks, focusing on accuracy, relevance, and completeness.

What's More? -Custom Polygon Creation: Our team can build polygons for any location or category based on your specific requirements. Whether it’s a new retail chain, transportation hub, or niche point of interest, we’ve got you covered. -Enhanced Customization: In addition to polygons, we capture critical details such as entry and exit points, parking areas, and adjacent pathways, adding greater context to your geospatial data. -Flexible Data Delivery Formats: We provide datasets in industry-standard formats like WKT, GeoJSON, Shapefile, and GDB, making them compatible with various systems and tools. -Regular Data Updates: Stay ahead with our customizable refresh schedules, ensuring your polygon data is always up-to-date for evolving business needs.

Unlock the Power of POI and Geospatial Data With our robust polygon datasets and point-of-interest data, you can: -Perform detailed market analyses to identify growth opportunities. -Pinpoint the ideal location for your next store or business expansion. -Decode consumer behavior patterns using geospatial insights. -Execute targeted, location-driven marketing campaigns for better ROI. -Gain an edge over competitors by leveraging geofencing and spatial intelligence.

Why Choose LocationsXYZ? LocationsXYZ is trusted by leading brands to unlock actionable business insights with our spatial data solutions. Join our growing network of successful clients who have scaled their operations with precise polygon and POI data. Request your free sample today and explore how we can help accelerate your business growth.

For every address in the City of Kitchener, a GIS spatial join has been created to select the closest Park, Playground, Elementary School, etc

AT_2003_BACI_1 File Geodatabase Feature Class Thumbnail Not Available Tags There are no tags for this item. Summary There is no summary for this item. Description MD Property View 2003 A&T Database. For more information on the A&T Database refer to the enclosed documentation. This layer was edited to remove spatial outliers in the A&T Database. Spatial outliers are those points that were not geocoded and as a result fell outside of the Baltimore City Boundary; 416 spatial outliers were removed from this layer. The field BLOCKLOT2 can be used to join this layer with the Baltimore City parcel layer. Credits There are no credits for this item. Use limitations There are no access and use limitations for this item. Extent West -76.713418 East -76.526031 North 39.374429 South 39.197452

Data Source: The primary data source used for this analysis are point-level business establishment data from InfoUSA. This commercial database produced by InfoGroup provides a comprehensive list of businesses in the SCAG region, including their industrial classification, number of employees, and several additional fields. Data have been post-processed for accuracy by SCAG staff and have an effective date of 2016. Locally-weighted regression: First, the SCAG region is overlaid with a grid, or fishnet, of 1km, 2km, and ½-km per cell. At the 1km cell size, there are 16,959 cells covering the SCAG region. Using the Spatial Join feature in ArcGIS, a sum total of business establishments and total employees (i.e., not separated by industrial classification) were joined to each grid cell. Note that since cells are of a standard size, the employment total in a cell is the equivalent of the employment density. A locally-weighted regression (LWR) procedure was developed using the R Statistical Software package in order to identify subcenters.The below procedure is described for 1km grid cells, but was repeated for 2km and 1/2km cells. Identify local maxima candidates.Using R’s lwr package, each cell’s 120 nearest neighbors, corresponding to roughly 5.5 km in each direction, was explored to identify high outliers or local maxima based on the total employment field. Cells with a z-score of above 2.58 were considered local maxima candidates.Identify local maxima. LWR can result in local maxima existing within close proximity. This step used a .dbf-format spatial weights matrix (knn=120 nearest neighbors) to identify only cells which are higher than all of their 120 nearest neighbors. At the 1km scale, 84 local maxima were found, which will form the “peak” of each individual subcenter. Search adjacent cells to include as part of each subcenter. In order to find which cells also are part of each local maximum’s subcenter, we use a queen (adjacency) contiguity matrix to search adjacent cells up to 120 nearest neighbors, adding cells if they are also greater than the average density in their neighborhood. A total of 695 cells comprise subcenters at the 1km scale. A video from Kane et al. (2018) demonstrates the above aspects of the methodology (please refer to 0:35 through 2:35 of https://youtu.be/ylTWnvCCO54), with several minor differences which result in a different final map of subcenters: different years and slightly different post-processing steps for InfoUSAdata, video study covers 5-county region (Imperial county not included), and limited to 1km scale subcenters.A challenge arises in that using 1km grid cells may fail to identify the correct local maximum for a particularly large employment center whose experience of high density occurs over a larger area. The process was repeated at a 2km scale, resulting in 54 “coarse scaled” subcenters. Similarly, some centers may exist with a particularly tightly-packed area of dense employment which is not detectable at the medium, 1km scale. The process was repeated again with ½-km grid cells, resulting in 95 “fine scaled” subcenters. In many instances, boundaries of fine, medium, and coarse scaled subcenters were similar, but differences existed. The next step was to qualitatively comparing results at each scale to create the final map of 72 job centers across the region. Most centers are medium scale, but some known areas of especially employment density were better captured at the 2km scale while . Giuliano and Small’s (1991) “ten jobs per acre” threshold was used as a rough guide to test for reasonableness when choosing a larger or smaller scale. For example, in some instances, a 1km scale included much additional land which reduced job density well below 10 jobs per acre. In this instance, an overlapping or nearby 1/2km scaled center provided a better reflection of the local employment peak. Ultimately, the goal was to identify areas where job density is distinct from nearby areas. Finally, in order to serve land use and travel demand modeling purposes for Connect SoCal, job centers were joined to their nearest TAZ boundaries. While the identification mechanism described above uses a combination of point and grid cell boundaries, the job centers boundaries expressed in this layer, and used for Connect SoCal purposes, are built from TAZ geographies. In Connect SoCal, job centers are associated with one of three strategies: focused growth, coworking space, or parking/AVR.Data Field/Value description:name: Name of job center based on name of local jurisdiction(s) or other discernable feature.Focused_Gr: Indicates whether job center was used for the 2020 RTP/SCS Focused Growth strategy, 1: center was used, 0: center was not used.Cowork: Indicates whether job center was used for the 2020 RTP/SCS Co-working space strategy, 1: center was used, 0: center was not used.Park_AVR: Indicates whether job center was used for the 2020 RTP/SCS parking and average vehicle ridership (AVR) strategies, 1: center was used, 0: center was not used. nTAZ: number of Transportation Analysis Zones (TAZs) which comprise this center.emp16: Estimated number of workers within job center boundaries based on 2016 InfoUSA point-based business establishment data. Values are rounded to the nearest 1000. acres: Land area within job center boundaries based on grid-based identification mechanism (i.e., not based on TAZ boundaries shown). Values are rounded to the nearest 100.

This specialized geospatial dataset offers detailed insights into heliport locations across North America. Emergency services, aviation companies, and urban development agencies can leverage these precise center points and boundary information to enhance operational efficiency. The comprehensive data supports critical applications like emergency response routing, infrastructure planning, and aviation safety assessments. By providing exact geographical coordinates and spatial extents, Xtract.io empowers organizations to make data-driven decisions in helicopter transportation and emergency services.

How Do We Create Polygons? -All our polygons are manually crafted using advanced GIS tools like QGIS, ArcGIS, and similar applications. This involves leveraging aerial imagery and street-level views to ensure precision. -Beyond visual data, our expert GIS data engineers integrate venue layout/elevation plans sourced from official company websites to construct detailed indoor polygons. This meticulous process ensures higher accuracy and consistency. -We verify our polygons through multiple quality checks, focusing on accuracy, relevance, and completeness.

What's More? -Custom Polygon Creation: Our team can build polygons for any location or category based on your specific requirements. Whether it’s a new retail chain, transportation hub, or niche point of interest, we’ve got you covered. -Enhanced Customization: In addition to polygons, we capture critical details such as entry and exit points, parking areas, and adjacent pathways, adding greater context to your geospatial data. -Flexible Data Delivery Formats: We provide datasets in industry-standard formats like WKT, GeoJSON, Shapefile, and GDB, making them compatible with various systems and tools. -Regular Data Updates: Stay ahead with our customizable refresh schedules, ensuring your polygon data is always up-to-date for evolving business needs.

Unlock the Power of POI and Geospatial Data With our robust polygon datasets and point-of-interest data, you can: -Perform detailed market analyses to identify growth opportunities. -Pinpoint the ideal location for your next store or business expansion. -Decode consumer behavior patterns using geospatial insights. -Execute targeted, location-driven marketing campaigns for better ROI. -Gain an edge over competitors by leveraging geofencing and spatial intelligence.

Why Choose LocationsXYZ? LocationsXYZ is trusted by leading brands to unlock actionable business insights with our spatial data solutions. Join our growing network of successful clients who have scaled their operations with precise polygon and POI data. Request your free sample today and explore how we can help accelerate your business growth.

This dataset is one of several segments of a regional high detailed stream flowpath dataset. The data was separated using the TOPO 50 map series extents.The stream network was originally created for the purpose of high detailed work along rivers and streams in the Wellington region. It was started as a pilot study for the Mangatarere subcatchment of the Waiohine River for the Environmental Sciences department who was attempting to measure riparian vegetation. The data was sourced from a modelled stream network created using the 2013 LiDAR digital elevation model. Once the Mangatarere was complete the process was expanded to cover the entire region on an as needed basis for each whaitua. This dataset is one of several that shows the finished stream datasets for the Wairarapa region.The base stream network was created using a mixture of tools found in ArcGIS Spatial Analyst under Hydrology along with processes located in the Arc Hydro downloadable add-on for ArcGIS. The initial workflow for the data was based on the information derived from the help files provided at the Esri ArcGIS 10.1 online help files. The updated process uses the core Spatial Analyst tools to generate the streamlines while digital dams are corrected using the DEM Reconditioning tool provided by the Arc Hydro toolset. The whaitua were too large for processing separated into smaller units according to the subcatchments within it. In select cases like the Taueru subcatchment of the Ruamahanga these subcatchments need to be further defined to allow processing. The catchment boundaries available are not as precise as the LiDAR information which causes overland flows that are on edges of the catchments to become disjointed from each other and required manual correction.Attributes were added to the stream network using the River Environment Classification (REC) stream network from NIWA. The Spatial Join tool in Arcmap was used to add the Reach ID to each segment of the generated flow path. This ID was used to join a table which had been created by intersecting stream names (generated from a point feature class available from LINZ) with the REC subcatchment dataset. Both of the REC datasets are available from NIWA's website.

This data is utilized in the Lesson 1.1 What is Climate activity on the MI EnviroLearning Hub Climate Change page.Station data accessed was accessed from NOAA. Data was imported into ArcGIS Pro where Coordinate Table to Point was used to spatially enable the originating CSV. This feature service, which incorporates Census Designated Places from the U.S. Census Bureau’s 2020 Census Demographic and Housing Characteristics, was used to spatially join weather stations to the nearest incorporated area throughout Michigan.Email Egle-Maps@Michigan.gov for questions.Former name: MichiganStationswAvgs19912020_WithinIncoproatedArea_UpdatedName Display Name Field Name Description

STATION_ID MichiganStationswAvgs19912020_W Station ID where weather data is collected

STATION MichiganStationswAvgs19912020_1 Station name where weather data is collected

ELEVATION MichiganStationswAvgs19912020_6 Elevation above mean sea level-meters

MLY-PRCP-NORMAL MichiganStationswAvgs19912020_8 Long-term averages of monthly precipitation total-inches

MLY-TAVG-NORMAL MichiganStationswAvgs19912020_9 Long-term averages of monthly average temperature -F

OID MichiganStationswAvgs1991202_10 Object ID for weather dataset

Join_Count MichiganStationswAvgs1991202_11 Spatial join count of weather station data to specific weather station

TARGET_FID MichiganStationswAvgs1991202_12 Spatial Join ID

Current place ANSI code MichiganStationswAvgs1991202_13 Census codes for identification of geographic entities (used for join)

Geographic Identifier MichiganStationswAvgs1991202_14 Geographic identifier (used for join)

Current class code MichiganStationswAvgs1991202_15 Class (CLASSFP) code defines the current class of a geographic entity

Current functional status MichiganStationswAvgs1991202_16 Status of weather station

Area of Land (Square Meters) MichiganStationswAvgs1991202_17 Area of land in square meters

Area of Water (Square Meters) MichiganStationswAvgs1991202_18 Area of water in square meters

Current latitude of the internal point MichiganStationswAvgs1991202_19 Latitude

Current longitude of the internal point MichiganStationswAvgs1991202_20 Longitude

Name MichiganStationswAvgs1991202_21 Location name of weather station

Current consolidated city GNIS code MichiganStationswAvgs1991202_22 Geographic Names Information System for an incorporated area

OBJECTID MichiganStationswAvgs1991202_23 Object ID for point dataset

This is a collaboration between City of Los Angeles Mayor's Office, StreetsLA, and USC. To consolidate / aggregate many datasets for Street Sweeping. Task 2: to perform spatial join between Centerlines and Tracts in order to get the Median HHI from 2018 Demographics.

This dataset is one of several segments of a regional high detailed stream flowpath dataset. The data was separated using the TOPO 50 map series extents.The stream network was originally created for the purpose of high detailed work along rivers and streams in the Wellington region. It was started as a pilot study for the Mangatarere subcatchment of the Waiohine River for the Environmental Sciences department who was attempting to measure riparian vegetation. The data was sourced from a modelled stream network created using the 2013 LiDAR digital elevation model. Once the Mangatarere was complete the process was expanded to cover the entire region on an as needed basis for each whaitua. This dataset is one of several that shows the finished stream datasets for the Wairarapa region.The base stream network was created using a mixture of tools found in ArcGIS Spatial Analyst under Hydrology along with processes located in the Arc Hydro downloadable add-on for ArcGIS. The initial workflow for the data was based on the information derived from the help files provided at the Esri ArcGIS 10.1 online help files. The updated process uses the core Spatial Analyst tools to generate the streamlines while digital dams are corrected using the DEM Reconditioning tool provided by the Arc Hydro toolset. The whaitua were too large for processing separated into smaller units according to the subcatchments within it. In select cases like the Taueru subcatchment of the Ruamahanga these subcatchments need to be further defined to allow processing. The catchment boundaries available are not as precise as the LiDAR information which causes overland flows that are on edges of the catchments to become disjointed from each other and required manual correction.Attributes were added to the stream network using the River Environment Classification (REC) stream network from NIWA. The Spatial Join tool in Arcmap was used to add the Reach ID to each segment of the generated flow path. This ID was used to join a table which had been created by intersecting stream names (generated from a point feature class available from LINZ) with the REC subcatchment dataset. Both of the REC datasets are available from NIWA's website.

This layer contains Census Tracts that have been designated as Qualified Opportunity Zones and contains additional data determined by the EPA to be of interest to users who are seeking revitalization-oriented information about these tracts. Based on nominations of eligible census tracts by the Chief Executive Officers of each State, Treasury has completed its designation of Qualified Opportunity Zones. Each State nominated the maximum number of eligible tracts, per statute, and these designations are final. The statute and legislative history of the Opportunity Zone designations, under IRC § 1400Z, do not contemplate an opportunity for additional or revised designations after the maximum number of zones allowable have been designated in a State or Territory. The data in this layer was updated in January 2021. For more information on Opportunity Zones, please visit: https://www.cdfifund.gov/Pages/Opportunity-Zones.aspx

EPA has added these indicators to the QOZ tracts list:

1. Count of Superfund facilities from EPA National Priorities List (NPL). Count was generated by performing spatial join of Tract boundaries to NPL points—yielding per tract counts. Spatial Extent: all US states and territories. Source: https://www.epa.gov/superfund/superfund-data-and-reports

2. Count of Brownfields properties from EPA Assessment, Cleanup and Redevelopment Exchange System (ACRES). Count was generated by performing spatial join of Tract boundaries to ACRES points--yielding per tract counts. Spatial Extent: all US states and territories. Source: https://edap-oei-data-commons.s3.amazonaws.com/EF/GIS/EF_ACRES.csv

3. Technical Assistance Communities from EPA Office of Community Revitalization (OCR). 13 layers were merged into one; count was generated by performing spatial join of Tract boundaries to combined point layer—yielding per tract counts. Please note that technical assistance communities are often serving areas larger than a single Census tract. Please contact OCR with questions. Spatial Extent: all US states and territories. Source: https://epa.maps.arcgis.com/home/item.html?id=b8795575db194340a4ad1c251e4d6ca1

4. Lead Paint Index from Environmental Justice Screening and Mapping Tool (EJSCREEN). Block group-level values were population weighted and summed to produce a tract-level estimate. The “raw” values were converted to tract-level percentiles. Spatial Extent: all US states and Puerto Rico. Source: https://gaftp.epa.gov/EJSCREEN/2019/

5. Air Toxics Respiratory Index from EJSCREEN. Block group-level values were population weighted and summed to produce a tract-level estimate. The “raw” values were converted to tract-level percentiles. Spatial Extent: all US states and Puerto Rico. Source: https://gaftp.epa.gov/EJSCREEN/2019/

6. Demographic Index Indicator from EJSCREEN. Block group-level values were population weighted and summed to produce a tract-level estimate. The “raw” values were converted to tract-level percentiles. Spatial Extent: all US states and Puerto Rico. Source: https://gaftp.epa.gov/EJSCREEN/2019/

7. Estimated Floodplain Indicator from EPA EnviroAtlas. Floodplain raster was converted to polygon feature class; Y/N indicator was generated by performing a spatial join of Tract boundaries to the Floodplain polygons. Spatial Extent: Continental US. Source: https://gaftp.epa.gov/epadatacommons/ORD/EnviroAtlas/Estimated_floodplain_CONUS.zip

8. National Walkability Index from EPA Smart Location Tools. The National Walkability Index is a nationwide geographic data resource that ranks block groups according to their relative walkability. Tract values assigned by averaging values from block group-level table. Spatial Extent: all US states and territories. Source: EPA Office of Policy—2020 NWI update

9. Impaired Waters Indicator from EPA Office of Water (OW). Y/N indicator was generated by performing spatial joins of Tract boundaries to 3 separate impaired waters layers (point, line and polygon). Y was assigned for all intersected geographies. Extent: all US states and Puerto Rico. Source: https://watersgeo.epa.gov/GEOSPATIALDOWNLOADS/rad_303d_20150501_fgdb.zip

10. Tribal Areas Indicator from EPA. Y/N indicator was generated by performing spatial joins of Tract boundaries to 4 separate Tribal areas layers (Alaska Native Villages, Alaska Allotments, Alaska Reservations, Lower 48 Tribes). Y as assigned for all intersected geographies. Spatial Extent: Alaska and Continental US. Source: https://edg.epa.gov/data/PUBLIC/OEI/OIAA/TRIBES/EPAtribes.zip

11. Count of Resource Conservation and Recovery Act (RCRA) Corrective Action facilities. Count was generated by performing spatial join of Tract boundaries to Corrective Action points—yielding per tract counts. Spatial Extent: all US states and territories. Source: https://www.epa.gov/cleanups/cimc-web-map-service-and-more

12. Count of Toxics Release Inventory facilities from EPA. Count was generated by performing spatial join of Tract boundaries to TRI points—yielding per tract counts. Spatial Extent: all US states and territories. Source: https://edap-oei-data-commons.s3.amazonaws.com/EF/GIS/EF_TRI.csv

13. Social Vulnerability Index (SVI) Housing/Transportation Index from CDC, published in 2018. The Housing/Transportation Index includes ACS 2014-2018 data on crowding in housing and no access to vehicle, among others. County values assigned to tracts by joining Tracts to county-level table. For detailed documentation: https://svi.cdc.gov/Documents/Data/2018_SVI_Data/SVI2018Documentation.pdfSpatial Extent: all US states. Source: https://epa.maps.arcgis.com/home/item.html?id=cbd68d9887574a10bc89ea4efe2b8087

14. Low Access to Food Store Indicator from USDA Food Access Atlas. Y/N indicator was generated by performing a table join of Tracts to the Food Access table records meeting the test criteria. Spatial Extent: all US states. Source: https://www.ers.usda.gov/data-products/food-access-research-atlas/download-the-data/

15. Overall Social Vulnerability Index (SVI) from CDC. Values (RPL_THEMES) assigned by joining the Tract boundaries to source Tract-level table. Spatial Extent: All US states. Source: https://www.atsdr.cdc.gov/placeandhealth/svi/data_documentation_download.html

16. Rural Communities Indicator from USDA Economic Research Service (ERS). Source tract-level table was flagged as rural where RUCA Codes in 4-10 or 2 and 3 where area >= 400 sq. miles and pop density

This dataset is one of several segments of a regional high detailed stream flowpath dataset. The data was separated using the TOPO 50 map series extents.The stream network was originally created for the purpose of high detailed work along rivers and streams in the Wellington region. It was started as a pilot study for the Mangatarere subcatchment of the Waiohine River for the Environmental Sciences department who was attempting to measure riparian vegetation. The data was sourced from a modelled stream network created using the 2013 LiDAR digital elevation model. Once the Mangatarere was complete the process was expanded to cover the entire region on an as needed basis for each whaitua. This dataset is one of several that shows the finished stream datasets for the Wairarapa region.The base stream network was created using a mixture of tools found in ArcGIS Spatial Analyst under Hydrology along with processes located in the Arc Hydro downloadable add-on for ArcGIS. The initial workflow for the data was based on the information derived from the help files provided at the Esri ArcGIS 10.1 online help files. The updated process uses the core Spatial Analyst tools to generate the streamlines while digital dams are corrected using the DEM Reconditioning tool provided by the Arc Hydro toolset. The whaitua were too large for processing separated into smaller units according to the subcatchments within it. In select cases like the Taueru subcatchment of the Ruamahanga these subcatchments need to be further defined to allow processing. The catchment boundaries available are not as precise as the LiDAR information which causes overland flows that are on edges of the catchments to become disjointed from each other and required manual correction.Attributes were added to the stream network using the River Environment Classification (REC) stream network from NIWA. The Spatial Join tool in Arcmap was used to add the Reach ID to each segment of the generated flow path. This ID was used to join a table which had been created by intersecting stream names (generated from a point feature class available from LINZ) with the REC subcatchment dataset. Both of the REC datasets are available from NIWA's website.

This is a collaboration between City of Los Angeles Mayor's Office, StreetsLA, and USC. To consolidate / aggregate many datasets for Street Sweeping. Task 2: to perform spatial join between Centerlines and Tracts in order to get the Median HHI from 2018 Demographics.

This dataset is one of several segments of a regional high detailed stream flowpath dataset. The data was separated using the TOPO 50 map series extents.The stream network was originally created for the purpose of high detailed work along rivers and streams in the Wellington region. It was started as a pilot study for the Mangatarere subcatchment of the Waiohine River for the Environmental Sciences department who was attempting to measure riparian vegetation. The data was sourced from a modelled stream network created using the 2013 LiDAR digital elevation model. Once the Mangatarere was complete the process was expanded to cover the entire region on an as needed basis for each whaitua. This dataset is one of several that shows the finished stream datasets for the Wairarapa region.The base stream network was created using a mixture of tools found in ArcGIS Spatial Analyst under Hydrology along with processes located in the Arc Hydro downloadable add-on for ArcGIS. The initial workflow for the data was based on the information derived from the help files provided at the Esri ArcGIS 10.1 online help files. The updated process uses the core Spatial Analyst tools to generate the streamlines while digital dams are corrected using the DEM Reconditioning tool provided by the Arc Hydro toolset. The whaitua were too large for processing separated into smaller units according to the subcatchments within it. In select cases like the Taueru subcatchment of the Ruamahanga these subcatchments need to be further defined to allow processing. The catchment boundaries available are not as precise as the LiDAR information which causes overland flows that are on edges of the catchments to become disjointed from each other and required manual correction.Attributes were added to the stream network using the River Environment Classification (REC) stream network from NIWA. The Spatial Join tool in Arcmap was used to add the Reach ID to each segment of the generated flow path. This ID was used to join a table which had been created by intersecting stream names (generated from a point feature class available from LINZ) with the REC subcatchment dataset. Both of the REC datasets are available from NIWA's website.

This dataset is one of several segments of a regional high detailed stream flowpath dataset. The data was separated using the TOPO 50 map series extents.The stream network was originally created for the purpose of high detailed work along rivers and streams in the Wellington region. It was started as a pilot study for the Mangatarere subcatchment of the Waiohine River for the Environmental Sciences department who was attempting to measure riparian vegetation. The data was sourced from a modelled stream network created using the 2013 LiDAR digital elevation model. Once the Mangatarere was complete the process was expanded to cover the entire region on an as needed basis for each whaitua. This dataset is one of several that shows the finished stream datasets for the Wairarapa region.The base stream network was created using a mixture of tools found in ArcGIS Spatial Analyst under Hydrology along with processes located in the Arc Hydro downloadable add-on for ArcGIS. The initial workflow for the data was based on the information derived from the help files provided at the Esri ArcGIS 10.1 online help files. The updated process uses the core Spatial Analyst tools to generate the streamlines while digital dams are corrected using the DEM Reconditioning tool provided by the Arc Hydro toolset. The whaitua were too large for processing separated into smaller units according to the subcatchments within it. In select cases like the Taueru subcatchment of the Ruamahanga these subcatchments need to be further defined to allow processing. The catchment boundaries available are not as precise as the LiDAR information which causes overland flows that are on edges of the catchments to become disjointed from each other and required manual correction.Attributes were added to the stream network using the River Environment Classification (REC) stream network from NIWA. The Spatial Join tool in Arcmap was used to add the Reach ID to each segment of the generated flow path. This ID was used to join a table which had been created by intersecting stream names (generated from a point feature class available from LINZ) with the REC subcatchment dataset. Both of the REC datasets are available from NIWA's website.