djangodocs.org

1413 sections across all versions Narrow to Django 6.0 (current) →

coveredby

Reference GIS QuerySet API Reference Spatial Lookups

Availability: PostGIS, Oracle, MariaDB, MySQL, PGRaster (Bilateral), SpatiaLite Tests if no point in the geometry field is outside the lookup geometry.

4.2 5.0 5.1 5.2 6.0

covers

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.

4.2 5.0 5.1 5.2 6.0

disjoint

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.

4.2 5.0 5.1 5.2 6.0

equals

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.

4.2 5.0 5.1 5.2 6.0

exact, same_as

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.

4.2 5.0 5.1 5.2 6.0

geom_type

Reference GIS QuerySet API Reference Spatial Lookups

New in Django 6.0. Availability: PostGIS, Oracle 23c+, MariaDB, MySQL, SpatiaLite Returns the geometry type of the geometry field.

6.0

overlaps

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.

4.2 5.0 5.1 5.2 6.0

relate

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.

4.2 5.0 5.1 5.2 6.0

Oracle

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'.

4.2 5.0 5.1 5.2 6.0

within

Reference GIS QuerySet API Reference Spatial Lookups

Availability: PostGIS, Oracle, MariaDB, MySQL, SpatiaLite, PGRaster (Bilateral) Tests if the geometry field is spatially within the lookup geometry.

4.2 5.0 5.1 5.2 6.0

left

Reference GIS QuerySet API Reference Spatial Lookups

Availability: PostGIS, PGRaster (Conversion) Tests if the geometry field’s bounding box is strictly to the left of the lookup geometry’s bounding box. Example: PostGIS equivalent:

4.2 5.0 5.1 5.2 6.0

right

Reference GIS QuerySet API Reference Spatial Lookups

Availability: PostGIS, PGRaster (Conversion) Tests if the geometry field’s bounding box is strictly to the right of the lookup geometry’s bounding box. Example: PostGIS equivalent:

4.2 5.0 5.1 5.2 6.0

overlaps_left

Reference GIS QuerySet API Reference Spatial Lookups

Availability: PostGIS, PGRaster (Bilateral) Tests if the geometry field’s bounding box overlaps or is to the left of the lookup geometry’s bounding box. Example: PostGIS equivalent:

4.2 5.0 5.1 5.2 6.0