  
  * A new :doc:`GeoJSON serializer </ref/contrib/gis/serializers>` is now
    available.
  
  * The Spatialite backend now supports ``Collect`` and ``Extent`` aggregates
    when the database version is 3.0 or later.
  
  * The PostGIS 2 ``CREATE EXTENSION postgis`` and the Spatialite
    ``SELECT InitSpatialMetaData`` initialization commands are now automatically
 
</s> remove         if lookup_type == 'isnull':
            return bool(value)
        else:
 </s> add         if lookup_type == 'contains':
            # 'contains' name might conflict with the "normal" contains lookup,
            # for which the value is not prepared, but left as-is. </s> remove         return obj.get_compiler(connection=self.connection).as_sql()
 </s> add         return obj.get_compiler(connection=self.connection).as_sql(subquery=True)
* It is now allowed to include a subquery as a geographic lookup argument, for
  example ``City.objects.filter(point__within=Country.objects.filter(continent='Africa').values('mpoly'))``.

  
  * A new :doc:`GeoJSON serializer </ref/contrib/gis/serializers>` is now
    available.
  
* It is now allowed to include a subquery as a geographic lookup argument, for
  example ``City.objects.filter(point__within=Country.objects.filter(continent='Africa').values('mpoly'))``.

  * The Spatialite backend now supports ``Collect`` and ``Extent`` aggregates
    when the database version is 3.0 or later.
  
  * The PostGIS 2 ``CREATE EXTENSION postgis`` and the Spatialite
    ``SELECT InitSpatialMetaData`` initialization commands are now automatically
keep keep keep add keep keep keep keep keep
 Fixed #14483 -- Allowed using subqueries with GIS lookups 
docs/releases/1.8.txt