Calculating Proportionate Itersecting Areas Using St_intersect

Analyze spatial attribute distribution with precision using area-weighted interpolation logic.

What is Calculating Proportionate Intersecting Areas using ST_Intersect?

In the world of Geographic Information Systems (GIS), specifically when working with spatial databases like PostGIS, calculating proportionate intersecting areas using st_intersect is a fundamental technique for data disaggregation. It is the process of estimating how much of a specific attribute (like population, number of households, or total sales) belongs to a new geometric boundary based on the physical overlap between two layers.

Analysts use this method when their data is stored in one set of boundaries (e.g., Zip Codes) but they need to report it in another (e.g., City Council Districts). By using the ST_Area and ST_Intersection functions, we can mathematically distribute values proportional to the area covered. A common misconception is that ST_Intersects (the boolean check) and ST_Intersection (the geometry result) are the same; in reality, for calculating proportionate intersecting areas using st_intersect, we use the boolean check to filter records and the geometry function to calculate the actual overlap area.

Mathematical Formula and Explanation

The calculation follows the logic of area-weighted interpolation. It assumes that the attribute value is uniformly distributed across the source polygon’s area.

The Core Formula:

Result Value = (Area of Intersection / Area of Source Polygon) × Total Attribute Value

Variable	Meaning	Unit	Typical Range
Source Area	Total area of the primary polygon	sq m / sq km	> 0
Intersection Area	Area overlapping with the target	sq m / sq km	0 to Source Area
Attribute Value	The quantity being distributed	Count / Currency	Any positive number
Proportion Factor	Ratio of overlap to source	Ratio (0-1)	0.00 to 1.00

Table 1: Variables used in area-weighted spatial interpolation calculations.

Practical Examples (Real-World Use Cases)

Example 1: Population in a Flood Zone

Imagine a Census Tract with a total area of 500,000 square meters and a population of 2,500 people. A flood zone map shows an intersection of 100,000 square meters within that tract. To estimate the people at risk:

• Proportion: 100,000 / 500,000 = 0.20 (20%)
• Result: 2,500 × 0.20 = 500 people.

This allows emergency planners to utilize calculating proportionate intersecting areas using st_intersect for rapid risk assessment.

Example 2: Retail Revenue Distribution

A shopping district generates $10 million in annual tax revenue across 2 square kilometers. A new urban renewal project covers 0.5 square kilometers of that district. The estimated revenue contribution of the project area is:

• Proportion: 0.5 / 2.0 = 0.25 (25%)
• Result: $10,000,000 × 0.25 = $2,500,000.

How to Use This Calculator

1. Enter Source Area: Provide the total area of your base polygon. You can get this in PostGIS using ST_Area(geom).
2. Enter Intersection Area: Provide the area of the overlap. In SQL, this is ST_Area(ST_Intersection(geom_a, geom_b)).
3. Input Attribute Value: Enter the number you want to split (e.g., total population, total cost).
4. Review Results: The calculator updates in real-time to show the proportioned value and the remaining value in the original polygon.

Key Factors That Affect Results

When calculating proportionate intersecting areas using st_intersect, several technical and geographic factors influence accuracy:

• Coordinate Reference Systems (CRS): Always use a projected coordinate system (like UTM) rather than a geographic one (Degrees) to ensure area calculations are in meaningful units like square meters.
• Homogeneity Assumption: This method assumes the attribute is spread evenly. If 90% of a population lives in 10% of a tract, area-weighting will be highly inaccurate.
• Geometry Validity: “Self-intersecting” polygons can cause ST_Intersection to fail or return incorrect areas. Use ST_IsValid to check your data.
• Precision and Snapping: Tiny gaps between boundaries (slivers) can result in missed intersections or double-counting.
• Scale and Resolution: High-resolution boundaries provide more accurate intersection areas than generalized, low-resolution outlines.
• Edge Effects: Polygons at the edge of a study area might have “clipped” attributes that don’t represent the true total.

Frequently Asked Questions (FAQ)

What is the difference between ST_Intersects and ST_Intersection?

ST_Intersects is a boolean function that returns true if two geometries touch or overlap. ST_Intersection returns the actual geometry of the overlap. For calculating proportionate intersecting areas using st_intersect, you use both: one to find the records and the other to find the area.

Can this be used for calculating cost distribution?

Yes, area-weighted interpolation is frequently used in land valuation and environmental cost assessment when features span multiple administrative boundaries.

Why is my result returning zero?

Check if your geometries are in the same CRS. If one is in EPSG:4326 (Degrees) and the other in EPSG:3857 (Meters), the intersection will likely fail or produce a zero area.

Is this the most accurate method for population?

Not necessarily. Dasymetric mapping, which uses land-cover data to refine where people actually live, is more accurate but requires significantly more data.

Does the order of geometries matter in ST_Intersection?

The geometry of the intersection is the same regardless of order, but for calculating proportionate intersecting areas using st_intersect, the denominator in your ratio must match the “Source” geometry you are proportioning from.

What unit should I use for area?

Consistency is key. Whether it is square meters, square feet, or hectares, ensure all area inputs use the same unit.

How do I handle sliver polygons?

Analysts often use a small buffer or a minimum area threshold to ignore tiny, insignificant intersections caused by digitizing errors.

Does this work for 3D geometries?

PostGIS ST_Intersection works primarily on 2D footprints. For 3D proportionate analysis, you would need to calculate volumetric intersections.

Related Tools and Internal Resources

• PostGIS Spatial Join Guide – Learn how to join tables based on spatial relationships.
• GIS Data Normalization – Techniques for ensuring your spatial data is clean and consistent.
• SQL Geometry Functions – A reference for common spatial SQL commands.
• Spatial Buffer Analysis – Calculate areas of influence around geographic features.
• Overlay Analysis Methods – Comparative look at Union, Intersect, and Identity.
• Mapping Database Best Practices – Optimizing PostGIS for performance and accuracy.