ST_Intersects

Return true if A intersects B. Polymorphic over input type:

(Geometry, Geometry) — topological intersection via JTS.
(Geography, Geography) — topological intersection via S2.
(Box2D, Box2D) — closed-interval bbox intersection on both axes (PostGIS && on box2d); edge- and corner-touching boxes count as intersecting. Throws IllegalArgumentException on inverted bounds. See Box2D optimization below.
(Box3D, Box3D) — closed-interval bbox intersection on all three axes (PostGIS &&& on box3d). Throws on inverted bounds on any axis.

Signatures

ST_Intersects (A: Geometry, B: Geometry)

ST_Intersects (A: Geography, B: Geography)

ST_Intersects (A: Box2D, B: Box2D)

ST_Intersects (A: Box3D, B: Box3D)

Geometry | Geography | Box2D | Box3D

required

The first input. Box2D / Box3D inputs use closed-interval semantics.

Geometry | Geography | Box2D | Box3D

required

The second input, of the same type family as A.

true if A intersects B.

SELECT ST_Intersects(ST_GeomFromWKT('LINESTRING(-43.23456 72.4567,-43.23456 72.4568)'), ST_GeomFromWKT('POINT(-43.23456 72.4567772)'))

true

Box2D example:

SELECT ST_Intersects(
    ST_MakeBox2D(ST_Point(0.0, 0.0), ST_Point(10.0, 10.0)),
    ST_MakeBox2D(ST_Point(5.0, 5.0), ST_Point(15.0, 15.0)))

true

For Box3D inputs the test covers all three axes — two boxes whose XY footprints overlap but whose Z ranges are disjoint do not intersect:

ST_Intersects(box_col, lit_box) over a Box2D column and a literal Box2D is recognized by Sedona’s spatial optimizer:

Filter pushdown. When the column is a Box2D stored in GeoParquet, the predicate translates to Parquet row-group inequalities on the xmin / ymin / xmax / ymax leaves. See Box2D filter pushdown.
Spatial join. ST_Intersects(a, b) between two Box2D columns is planned as a range or broadcast-index join. See Box2D spatial join.

⌘I