mirror of
https://github.com/django/django.git
synced 2025-08-04 02:48:35 +00:00
Removed references to changes made in 1.2.
Thanks Florian Apolloner for the patch.
This commit is contained in:
parent
6492e8e5e6
commit
c28e700c7e
46 changed files with 22 additions and 474 deletions
|
@ -12,11 +12,7 @@ GeoDjango Database API
|
|||
Spatial Backends
|
||||
================
|
||||
|
||||
.. versionadded:: 1.2
|
||||
|
||||
In Django 1.2, support for :doc:`multiple databases </topics/db/multi-db>` was
|
||||
introduced. In order to support multiple databases, GeoDjango has segregated
|
||||
its functionality into full-fledged spatial database backends:
|
||||
GeoDjango currently provides the following spatial database backends:
|
||||
|
||||
* :mod:`django.contrib.gis.db.backends.postgis`
|
||||
* :mod:`django.contrib.gis.db.backends.mysql`
|
||||
|
|
|
@ -212,8 +212,6 @@ __ http://www.gdal.org/ogr/ogr_formats.html
|
|||
|
||||
.. attribute:: spatial_filter
|
||||
|
||||
.. versionadded:: 1.2
|
||||
|
||||
Property that may be used to retrieve or set a spatial filter for this
|
||||
layer. A spatial filter can only be set with an :class:`OGRGeometry`
|
||||
instance, a 4-tuple extent, or ``None``. When set with something
|
||||
|
@ -490,15 +488,9 @@ systems and coordinate transformation::
|
|||
|
||||
.. attribute:: coord_dim
|
||||
|
||||
.. versionchanged:: 1.2
|
||||
|
||||
Returns or sets the coordinate dimension of this geometry. For
|
||||
example, the value would be 2 for two-dimensional geometries.
|
||||
|
||||
.. note::
|
||||
|
||||
Setting this property is only available in versions 1.2 and above.
|
||||
|
||||
.. attribute:: geom_count
|
||||
|
||||
Returns the number of elements in this geometry::
|
||||
|
@ -619,8 +611,6 @@ systems and coordinate transformation::
|
|||
|
||||
.. attribute:: ewkt
|
||||
|
||||
.. versionadded:: 1.2
|
||||
|
||||
Returns the EWKT representation of this geometry.
|
||||
|
||||
.. method:: clone()
|
||||
|
|
|
@ -117,8 +117,6 @@ SpatiaLite ``Contains(poly, geom)``
|
|||
contains_properly
|
||||
-----------------
|
||||
|
||||
.. versionadded:: 1.2
|
||||
|
||||
*Availability*: PostGIS
|
||||
|
||||
Returns true if the lookup geometry intersects the interior of the
|
||||
|
@ -803,8 +801,6 @@ Geometry Editors
|
|||
|
||||
.. method:: GeoQuerySet.force_rhr(**kwargs)
|
||||
|
||||
.. versionadded:: 1.2
|
||||
|
||||
*Availability*: PostGIS
|
||||
|
||||
Returns a modified version of the polygon/multipolygon in which all
|
||||
|
@ -816,8 +812,6 @@ of the vertices follow the Right-Hand-Rule, and attaches as a
|
|||
|
||||
.. method:: GeoQuerySet.reverse_geom(**kwargs)
|
||||
|
||||
.. versionadded:: 1.2
|
||||
|
||||
*Availability*: PostGIS, Oracle
|
||||
|
||||
Reverse the coordinate order of the geometry field, and attaches as a
|
||||
|
@ -943,8 +937,6 @@ of the geometry field in each model converted to the requested output format.
|
|||
|
||||
.. method:: GeoQuerySet.geohash(precision=20, **kwargs)
|
||||
|
||||
.. versionadded:: 1.2
|
||||
|
||||
Attaches a ``geohash`` attribute to every model the queryset
|
||||
containing the `GeoHash`__ representation of the geometry.
|
||||
|
||||
|
@ -1136,8 +1128,6 @@ Example::
|
|||
|
||||
.. method:: GeoQuerySet.extent3d(**kwargs)
|
||||
|
||||
.. versionadded:: 1.2
|
||||
|
||||
*Availability*: PostGIS
|
||||
|
||||
Returns the 3D extent of the ``GeoQuerySet`` as a six-tuple, comprising
|
||||
|
@ -1224,8 +1214,6 @@ Returns the same as the :meth:`GeoQuerySet.extent` aggregate method.
|
|||
|
||||
.. class:: Extent3D(geo_field)
|
||||
|
||||
.. versionadded:: 1.2
|
||||
|
||||
Returns the same as the :meth:`GeoQuerySet.extent3d` aggregate method.
|
||||
|
||||
``MakeLine``
|
||||
|
|
|
@ -265,8 +265,6 @@ because it is not a part of the OGC specification (use the
|
|||
|
||||
.. attribute:: GEOSGeometry.hexewkb
|
||||
|
||||
.. versionadded:: 1.2
|
||||
|
||||
Returns the EWKB of this Geometry in hexadecimal form. This is an
|
||||
extension of the WKB specification that includes SRID and Z values
|
||||
that are a part of this geometry.
|
||||
|
@ -314,8 +312,6 @@ as a Python buffer. SRID and Z values are not included, use the
|
|||
|
||||
.. attribute:: GEOSGeometry.ewkb
|
||||
|
||||
.. versionadded:: 1.2
|
||||
|
||||
Return the EWKB representation of this Geometry as a Python buffer.
|
||||
This is an extension of the WKB specification that includes any SRID
|
||||
and Z values that are a part of this geometry.
|
||||
|
|
|
@ -624,8 +624,6 @@ features such as the geographic admin or KML sitemaps will not function properly
|
|||
Add Google projection to ``spatial_ref_sys`` table
|
||||
--------------------------------------------------
|
||||
|
||||
.. versionchanged:: 1.2
|
||||
|
||||
.. note::
|
||||
|
||||
If you're running PostGIS 1.4 or above, you can skip this step. The entry
|
||||
|
|
|
@ -163,8 +163,6 @@ field.
|
|||
``dim``
|
||||
-------
|
||||
|
||||
.. versionadded:: 1.2
|
||||
|
||||
.. attribute:: GeometryField.dim
|
||||
|
||||
This option may be used for customizing the coordinate dimension of the
|
||||
|
@ -180,8 +178,6 @@ three-dimensonal support.
|
|||
``geography``
|
||||
-------------
|
||||
|
||||
.. versionadded:: 1.2
|
||||
|
||||
.. attribute:: GeometryField.geography
|
||||
|
||||
If set to ``True``, this option will create a database column of
|
||||
|
|
|
@ -2,12 +2,6 @@
|
|||
Testing GeoDjango apps
|
||||
======================
|
||||
|
||||
.. versionchanged:: 1.2
|
||||
|
||||
In Django 1.2, the addition of :ref:`spatial-backends` simplified the
|
||||
process of testing GeoDjango applications. The process is now the
|
||||
same as :doc:`/topics/testing`.
|
||||
|
||||
Included in this documentation are some additional notes and settings
|
||||
for :ref:`testing-postgis` and :ref:`testing-spatialite` users.
|
||||
|
||||
|
@ -28,11 +22,9 @@ Settings
|
|||
``POSTGIS_TEMPLATE``
|
||||
^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
.. versionchanged:: 1.2
|
||||
|
||||
This setting may be used to customize the name of the PostGIS template
|
||||
database to use. In Django versions 1.2 and above, it automatically
|
||||
defaults to ``'template_postgis'`` (the same name used in the
|
||||
database to use. It automatically defaults to ``'template_postgis'``
|
||||
(the same name used in the
|
||||
:ref:`installation documentation <spatialdb_template>`).
|
||||
|
||||
.. setting:: POSTGIS_VERSION
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue