ST_Contains
Introduction: Return true if A fully contains B Format:ST_Contains (A: Geometry, B: Geometry)
SQL example:
ST_Crosses
Introduction: Return true if A crosses B Format:ST_Crosses (A: Geometry, B: Geometry)
SQL example:
ST_Disjoint
Introduction: Return true if A and B are disjoint Format:ST_Disjoint (A: Geometry, B: Geometry)
SQL example:
ST_DWithin
Introduction: Returns true if ‘leftGeometry’ and ‘rightGeometry’ are within a specified ‘distance’. IfuseSpheroid is passed true, ST_DWithin uses Sedona’s ST_DistanceSpheroid to check the spheroid distance between the centroids of two geometries. The unit of the distance in this case is meter.
If useSpheroid is passed false, ST_DWithin uses Euclidean distance and the unit of the distance is the same as the CRS of the geometries. To obtain the correct result, please consider using ST_Transform to put data in an appropriate CRS.
If useSpheroid is not given, it defaults to false.
Format: ST_DWithin (leftGeometry: Geometry, rightGeometry: Geometry, distance: Double, useSpheroid: Optional(Boolean) = false)
SQL example:
ST_Equals
Introduction: Return true if A equals to B Format:ST_Equals (A: Geometry, B: Geometry)
SQL example:
ST_Intersects
Introduction: Return true if A intersects B Format:ST_Intersects (A: Geometry, B: Geometry)
SQL example:
ST_OrderingEquals
Introduction: Returns true if the geometries are equal and the coordinates are in the same order Format:ST_OrderingEquals(A: geometry, B: geometry)
SQL example:
ST_Overlaps
Introduction: Return true if A overlaps B Format:ST_Overlaps (A: Geometry, B: Geometry)
SQL example:
ST_Relate
Introduction: The first variant of the function computes and returns the Dimensionally Extended 9-Intersection Model (DE-9IM) matrix string representing the spatial relationship between the two input geometry objects. The second variant of the function evaluates whether the two input geometries satisfy a specific spatial relationship defined by the providedintersectionMatrix pattern.
It is important to note that this function is not optimized for use in spatial join operations. Certain DE-9IM relationships can hold true for geometries that do not intersect or are disjoint. As a result, it is recommended to utilize other dedicated spatial functions specifically optimized for spatial join processing.
ST_Relate(geom1: Geometry, geom2: Geometry)
ST_Relate(geom1: Geometry, geom2: Geometry, intersectionMatrix: String)
SQL Example
ST_RelateMatch
Introduction: This function tests the relationship between two Dimensionally Extended 9-Intersection Model (DE-9IM) matrices representing geometry intersections. It evaluates whether the DE-9IM matrix specified inmatrix1 satisfies the intersection pattern defined by matrix2. The matrix2 parameter can be an exact DE-9IM value or a pattern containing wildcard characters.
It is important to note that this function is not optimized for use in spatial join operations. Certain DE-9IM relationships can hold true for geometries that do not intersect or are disjoint. As a result, it is recommended to utilize other dedicated spatial functions specifically optimized for spatial join processing.
ST_RelateMatch(matrix1: String, matrix2: String)
SQL Example:
ST_Touches
Introduction: Return true if A touches B Format:ST_Touches (A: Geometry, B: Geometry)
SQL example:
ST_Within
Introduction: Return true if A is fully contained by B Format:ST_Within (A: Geometry, B: Geometry)
SQL example:
ST_Covers
Introduction: Return true if A covers B Format:ST_Covers (A: Geometry, B: Geometry)
SQL example:
ST_CoveredBy
Introduction: Return true if A is covered by B Format:ST_CoveredBy (A: Geometry, B: Geometry)
SQL example:

