Spatial Operations: Buffers, Intersections, and Spatial Joins

What Are Spatial Operations?

Spatial operations are geoprocessing tools that create new data by analyzing the geometric and attribute relationships between two or more layers. Unlike a simple map visualization, a spatial operation produces a new output layer or table that answers a specific question about geography. In data science, spatial operations are how you move from raw geographic data to analytical results you can count, summarize, and report.

This lesson covers three foundational operations: buffer, intersect, and spatial join. Together they let you answer questions like "How many residential parcels fall within 500 feet of a floodplain?" — the scenario you will work through in lab today.

Buffer

A buffer creates a new polygon layer by expanding (or shrinking) each feature by a specified distance. Every point, line, or polygon in the input layer grows outward by the distance you set, producing a surrounding zone.

Key settings to document:

• Input layer — the features you are buffering (e.g., FEMA floodplain polygons)
• Distance — the radius or width of the zone (e.g., 500 feet; confirm your layer's coordinate reference system uses feet, or convert correctly)
• Dissolve result — if checked, overlapping buffer zones are merged into a single polygon; if unchecked, each feature keeps a separate buffer

Always verify the coordinate reference system (CRS) of your data before setting a distance. If your layer is in a geographic CRS using decimal degrees, a buffer distance in feet will not be interpreted correctly. Reproject to a projected CRS (such as a State Plane or UTM zone appropriate for your study area) before buffering.

Intersect

The intersect tool outputs only the area (or features) that are common to both input layers. Think of it as a logical AND: a feature must exist in Layer A and Layer B to appear in the output. Attributes from both layers are carried into the output, which is why intersect is so useful — you can query or summarize fields from either source on the combined result.

For the lab scenario, you will intersect the 500-foot floodplain buffer with the county parcel layer. Only parcels (or parcel fragments) that overlap the buffer zone will survive into the output. Parcels entirely outside the buffer are dropped.

Watch for geometry type mismatches. QGIS will warn you if you attempt to intersect incompatible geometry types. Both layers should be polygons for a standard area intersect.

Spatial Join

A spatial join transfers attributes from one layer to another based on spatial relationship rather than a shared key field. Common relationship options include:

• Intersects — features that share any area or boundary
• Contains — one feature entirely contains the other
• Within — the reverse of contains
• Nearest — joins the attribute of the closest feature (useful for points)

In practice, you often use a spatial join after an intersect when you need to count or aggregate. For example, after intersecting parcels with the buffer, a spatial join (or a "Join attributes by location" with a summary) lets you count how many parcels fall inside each buffer zone.

The Full Workflow for Today's Scenario

1. Load data — FEMA NFHL floodplain polygons and the county parcel shapefile.

2. Check and align CRS — Reproject both layers to the same projected CRS if needed.

3. Buffer — Buffer the floodplain layer by 500 feet (dissolve recommended so you get one continuous zone).

4. Intersect — Intersect the 500-foot buffer with the parcel layer to get only parcels within the zone.

5. Attribute query — Filter the intersect output to keep only parcels where the land-use field indicates residential use.

6. Summarize — Count the remaining features (use the layer's feature count or a summary statistics tool).

Document each step with: input layer name, tool name, exact settings, output layer name, and a screenshot of the intermediate result. This documentation is what makes your analysis reproducible — someone else should be able to follow your steps and get the same output.

Data Sources and Data Integrity

The FEMA National Flood Hazard Layer (NFHL) is publicly available from the FEMA Map Service Center. County parcel data is typically available from your county assessor's open-data portal. Before using any dataset:

• Confirm the data's publication or revision date — flood maps are updated on a rolling basis.
• Check that the parcel land-use codes are documented in a data dictionary so your residential filter selects the correct codes.
• Never alter source data files; always save outputs as new files with descriptive names (e.g., `floodplain_buffer_500ft.shp`, `parcels_in_buffer.shp`).

Safety and Responsible Use

GIS analysis of floodplain data can inform real property decisions, emergency planning, and insurance assessments. Present results accurately: note the source, date, and any limitations of the underlying data. Do not represent a student lab output as an official flood-risk determination. FEMA flood maps carry legal and insurance implications; always direct stakeholders to official FEMA resources for regulatory decisions.

When downloading public shapefiles, scan downloaded ZIP archives with antivirus software before extracting, and work in a dedicated project folder — never on removable media shared across machines without scanning.

Documenting for Reproducibility

A workflow diagram labels each step with: (1) input(s), (2) tool and settings, and (3) output name. Reproducibility is a core data science value — it allows peers, supervisors, and auditors to verify your work. In the peer-review activity, your partner must be able to run your documented workflow and get the same result. If they cannot, the documentation — not just the analysis — needs revision.