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.
728 sections in Django 5.2 Search all versions →
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.
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:
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:
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:
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, PGRaster (Bilateral) Tests if the geometry field’s bounding box overlaps or is to the right of the lookup geometry’s bounding box. Example: PostGIS equivalent:
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, PGRaster (Conversion) Tests if the geometry field’s bounding box overlaps or is above the lookup geometry’s bounding box. Example: PostGIS equivalent:
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, PGRaster (Conversion) Tests if the geometry field’s bounding box overlaps or is below the lookup geometry’s bounding box. Example: PostGIS equivalent:
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, PGRaster (Conversion) Tests if the geometry field’s bounding box is strictly above the lookup geometry’s bounding box. Example: PostGIS equivalent:
Reference GIS QuerySet API Reference Spatial Lookups
Availability: PostGIS, PGRaster (Conversion) Tests if the geometry field’s bounding box is strictly below the lookup geometry’s bounding box. Example: PostGIS equivalent:
Reference GIS QuerySet API Reference
Availability: PostGIS, Oracle, MariaDB, MySQL, SpatiaLite, PGRaster (Native) For an overview on performing distance queries, please refer to the distance queries introduction.
Reference GIS QuerySet API Reference Distance Lookups
Returns models where the distance to the geometry field from the lookup geometry is greater than the given distance value.
Reference GIS QuerySet API Reference Distance Lookups
Returns models where the distance to the geometry field from the lookup geometry is greater than or equal to the given distance value.
Reference GIS QuerySet API Reference Distance Lookups
Returns models where the distance to the geometry field from the lookup geometry is less than the given distance value.
Reference GIS QuerySet API Reference Distance Lookups
Returns models where the distance to the geometry field from the lookup geometry is less than or equal to the given distance value.
Reference GIS QuerySet API Reference Distance Lookups
Returns models where the distance to the geometry field from the lookup geometry are within the given distance from one another. Note that you can only provide Distance objects if the targeted geometries are in a projected system.
Reference GIS QuerySet API Reference Distance Lookups
Django provides some GIS-specific aggregate functions. For details on how to use these aggregate functions, see the topic guide on aggregation.
Reference GIS QuerySet API Reference Distance LookupsAggregate Functions
classCollect(geo_field,filter=None)[source] Availability: PostGIS, MySQL, SpatiaLite Returns a GEOMETRYCOLLECTION or a MULTI geometry object from the geometry column.
Topic guide Aggregation Aggregations and other QuerySet clauses
Aggregates can also participate in filters. Any filter() (or exclude()) applied to normal model fields will have the effect of constraining the objects that are considered for aggregation.
Topic guide Aggregation Aggregations and other QuerySet clausesvalues()
As with the filter() clause, the order in which annotate() and values() clauses are applied to a query is significant. If the values() clause precedes the annotate(), the annotation will be computed using the grouping described by the values() clause.
Topic guide Aggregation Aggregations and other QuerySet clauses
You can also generate an aggregate on the result of an annotation. When you define an aggregate() clause, the aggregates you provide can reference any alias defined as part of an annotate() clause in the query.