Reference GIS QuerySet API Reference Spatial Lookups
All examples in the reference below are given for geometry fields and inputs, but the lookups can be used the same way with rasters on both sides.
728 sections in Django 5.2 Search all versions →
Reference GIS QuerySet API Reference Spatial Lookups
All examples in the reference below are given for geometry fields and inputs, but the lookups can be used the same way with rasters on both sides.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, MariaDB, MySQL, SpatiaLite, PGRaster (Native) Tests if the geometry or raster field’s bounding box completely contains the lookup geometry’s bounding box.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, MariaDB, MySQL, SpatiaLite, PGRaster (Native) Tests if the geometry field’s bounding box overlaps the lookup geometry’s bounding box.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, MariaDB, MySQL, SpatiaLite, PGRaster (Native) Tests if the geometry field’s bounding box is completely contained by the lookup geometry’s bounding box.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, Oracle, MariaDB, MySQL, SpatiaLite, PGRaster (Bilateral) Tests if the geometry field spatially contains the lookup geometry.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, PGRaster (Bilateral) Returns true if the lookup geometry intersects the interior of the geometry field, but not the boundary (or exterior).
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, Oracle, MySQL, PGRaster (Bilateral), SpatiaLite Tests if no point in the geometry field is outside the lookup geometry.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, Oracle, MySQL, PGRaster (Bilateral), SpatiaLite Tests if no point in the lookup geometry is outside the geometry field.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, MariaDB, MySQL, SpatiaLite, PGRaster (Conversion) Tests if the geometry field spatially crosses the lookup geometry.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, Oracle, MariaDB, MySQL, SpatiaLite, PGRaster (Bilateral) Tests if the geometry field is spatially disjoint from the lookup geometry.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, Oracle, MariaDB, MySQL, SpatiaLite, PGRaster (Conversion) Tests if the geometry field is spatially equal to the lookup geometry.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, Oracle, MariaDB, MySQL, SpatiaLite, PGRaster (Bilateral) Tests if the geometry field is “equal” to the lookup geometry. On Oracle, MySQL, and SpatiaLite, it tests spatial equality, while on PostGIS it tests equality of bounding boxes.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, Oracle, MariaDB, MySQL, SpatiaLite, PGRaster (Bilateral) Tests if the geometry field spatially intersects the lookup geometry.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS Tests if the geometry is empty. Example:
Reference GIS QuerySet API Reference Spatial Lookups
Availability: MySQL, PostGIS, Oracle, SpatiaLite Tests if the geometry is valid. Example: | Backend | SQL Equivalent | | --- | --- | | MySQL, PostGIS, SpatiaLite | ST_IsValid(poly) | | Oracle | SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(poly, 0.05) = 'TRUE' |
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, Oracle, MariaDB, MySQL, SpatiaLite, PGRaster (Bilateral) Tests if the geometry field spatially overlaps the lookup geometry.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, MariaDB, Oracle, SpatiaLite, PGRaster (Conversion) Tests if the geometry field is spatially related to the lookup geometry by the values given in the given pattern.
Reference GIS QuerySet API Reference Spatial Lookupsrelate
On these spatial backends the intersection pattern is a string comprising nine characters, which define intersections between the interior, boundary, and exterior of the geometry field and the lookup geometry.
Reference GIS QuerySet API Reference Spatial Lookupsrelate
Here the relation pattern is comprised of at least one of the nine relation strings: TOUCH, OVERLAPBDYDISJOINT, OVERLAPBDYINTERSECT, EQUAL, INSIDE, COVEREDBY, CONTAINS, COVERS, ON, and ANYINTERACT. Multiple strings may be combined with the logical Boolean operator OR, for example, 'inside+touch'.
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, Oracle, MariaDB, MySQL, SpatiaLite Tests if the geometry field spatially touches the lookup geometry.