mirror of
https://github.com/django/django.git
synced 2025-08-04 10:59:45 +00:00
Removed versionadded/changed annotations for 1.11.
This commit is contained in:
parent
2bd207ada0
commit
5446b72003
53 changed files with 0 additions and 489 deletions
|
@ -44,11 +44,6 @@ GeoDjango's admin site
|
|||
Link to the URL of the OpenLayers JavaScript. Defaults to
|
||||
``'https://cdnjs.cloudflare.com/ajax/libs/openlayers/2.13.1/OpenLayers.js'``.
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
Older versions default to
|
||||
``'http://openlayers.org/api/2.13.1/OpenLayers.js'``.
|
||||
|
||||
.. attribute:: modifiable
|
||||
|
||||
Defaults to ``True``. When set to ``False``, disables editing of
|
||||
|
|
|
@ -158,14 +158,6 @@ Widget classes
|
|||
``OpenLayers.js`` file `tailored to your needs`_ in the ``js`` property of
|
||||
the inner ``Media`` class (see :ref:`assets-as-a-static-definition`).
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
Older versions use ``OpenLayers.js`` from ``openlayers.org`` which
|
||||
isn't suitable for production use since it offers no guaranteed uptime
|
||||
and runs on a slow server.
|
||||
|
||||
Also, the widget nows uses OpenLayers 3 instead of OpenLayers 2.
|
||||
|
||||
.. _tailored to your needs: http://openlayers.org/en/latest/doc/tutorials/custom-builds.html
|
||||
|
||||
``OSMWidget``
|
||||
|
@ -195,10 +187,4 @@ Widget classes
|
|||
applies here. See also this `FAQ answer`_ about ``https`` access to map
|
||||
tiles.
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
OpenLayers 2.x has been dropped in favor of OpenLayers 3. If you extend
|
||||
the ``gis/openlayers-osm.html`` template, please review your custom
|
||||
template.
|
||||
|
||||
.. _FAQ answer: https://help.openstreetmap.org/questions/10920/how-to-embed-a-map-in-my-https-site
|
||||
|
|
|
@ -46,11 +46,6 @@ field as an :class:`~django.contrib.gis.measure.Area` measure.
|
|||
MySQL and SpatiaLite without LWGEOM don't support area calculations on
|
||||
geographic SRSes.
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
In older versions, a raw value was returned on MySQL when used on
|
||||
projected SRS.
|
||||
|
||||
``AsGeoJSON``
|
||||
=============
|
||||
|
||||
|
@ -118,10 +113,6 @@ Keyword Argument Description
|
|||
|
||||
__ https://en.wikipedia.org/wiki/Geography_Markup_Language
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
Oracle support was added.
|
||||
|
||||
``AsKML``
|
||||
=========
|
||||
|
||||
|
@ -201,10 +192,6 @@ polygon that can fully contain the geometry.
|
|||
|
||||
The ``num_seg`` parameter is used only on PostGIS.
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
Oracle support was added.
|
||||
|
||||
``Centroid``
|
||||
============
|
||||
|
||||
|
@ -273,11 +260,6 @@ queryset is calculated::
|
|||
in kilometers. See :doc:`measure` for usage details and the list of
|
||||
:ref:`supported_units`.
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
In older versions, a raw value was returned on MySQL when used on
|
||||
projected SRS.
|
||||
|
||||
``Envelope``
|
||||
============
|
||||
|
||||
|
@ -342,10 +324,6 @@ intersection between them.
|
|||
Accepts a geographic field or expression and tests if the value is well formed.
|
||||
Returns ``True`` if its value is a valid geometry and ``False`` otherwise.
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
SpatiaLite and Oracle support was added.
|
||||
|
||||
.. versionchanged:: 2.0
|
||||
|
||||
MySQL support was added.
|
||||
|
@ -369,10 +347,6 @@ resource-intensive) with the ``spheroid`` keyword argument.
|
|||
|
||||
MySQL doesn't support length calculations on geographic SRSes.
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
In older versions, a raw value was returned on MySQL.
|
||||
|
||||
``LineLocatePoint``
|
||||
===================
|
||||
|
||||
|
@ -399,10 +373,6 @@ a valid geometry without losing any of the input vertices. Geometries that are
|
|||
already valid are returned without changes. Simple polygons might become a
|
||||
multipolygon and the result might be of lower dimension than the input.
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
SpatiaLite support was added.
|
||||
|
||||
``MemSize``
|
||||
===========
|
||||
|
||||
|
@ -440,10 +410,6 @@ in a geometry.
|
|||
|
||||
On MySQL, returns ``None`` for any non-``LINESTRING`` geometry.
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
SpatiaLite support for non-``LINESTRING`` geometries was added.
|
||||
|
||||
``Perimeter``
|
||||
=============
|
||||
|
||||
|
|
|
@ -450,8 +450,6 @@ coordinate transformation::
|
|||
|
||||
.. classmethod:: from_gml(gml_string)
|
||||
|
||||
.. versionadded:: 1.11
|
||||
|
||||
Constructs an :class:`OGRGeometry` from the given GML string.
|
||||
|
||||
.. classmethod:: from_bbox(bbox)
|
||||
|
@ -1162,15 +1160,6 @@ blue.
|
|||
>>> rst.name # Stored in a random path in the vsimem filesystem.
|
||||
'/vsimem/da300bdb-129d-49a8-b336-e410a9428dad'
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
Added the ability to pass the ``size``, ``shape``, and ``offset``
|
||||
parameters when creating :class:`GDALRaster` objects. The parameters
|
||||
can be passed through the ``ds_input`` dictionary. This allows to
|
||||
finely control initial pixel values. The functionality is similar to
|
||||
the :meth:`GDALBand.data()<django.contrib.gis.gdal.GDALBand.data>`
|
||||
method.
|
||||
|
||||
.. versionchanged:: 2.0
|
||||
|
||||
Added the ability to read and write rasters in GDAL's memory-based
|
||||
|
|
|
@ -322,10 +322,6 @@ MySQL, PostGIS, SpatiaLite ``ST_IsValid(poly)``
|
|||
Oracle ``SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(poly, 0.05) = 'TRUE'``
|
||||
========================== ================================================================
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
Oracle and SpatiaLite support was added.
|
||||
|
||||
.. versionchanged:: 2.0
|
||||
|
||||
MySQL support was added.
|
||||
|
@ -635,10 +631,6 @@ simpler `ST_Distance <https://postgis.net/docs/ST_Distance.html>`__ function is
|
|||
used with projected coordinate systems. Rasters are converted to geometries for
|
||||
spheroid based lookups.
|
||||
|
||||
.. versionadded:: 1.11
|
||||
|
||||
Support for the ``'spheroid'`` option on SQLite was added.
|
||||
|
||||
.. versionadded:: 2.0
|
||||
|
||||
MySQL support was added.
|
||||
|
@ -746,10 +738,6 @@ Oracle ``SDO_WITHIN_DISTANCE(poly, geom, 5)``
|
|||
SpatiaLite ``PtDistWithin(poly, geom, 5)``
|
||||
========== ======================================
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
SpatiaLite support was added.
|
||||
|
||||
Aggregate Functions
|
||||
-------------------
|
||||
|
||||
|
|
|
@ -173,11 +173,6 @@ Geometries support set-like operators::
|
|||
>>> ls3 == ls2 # different SRIDs
|
||||
False
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
Older versions didn't check the ``srid`` when comparing
|
||||
``GEOSGeometry`` objects using the equality operator.
|
||||
|
||||
Geometry Objects
|
||||
================
|
||||
|
||||
|
@ -238,8 +233,6 @@ isn't provided, the SRID defaults to 4326.
|
|||
|
||||
.. classmethod:: GEOSGeometry.from_gml(gml_string)
|
||||
|
||||
.. versionadded:: 1.11
|
||||
|
||||
Constructs a :class:`GEOSGeometry` from the given GML string.
|
||||
|
||||
Properties
|
||||
|
|
|
@ -19,11 +19,6 @@ Program Description Required
|
|||
Note that older or more recent versions of these libraries *may* also work
|
||||
totally fine with GeoDjango. Your mileage may vary.
|
||||
|
||||
.. versionchanged:: 1.11
|
||||
|
||||
In older versions, GDAL is required only for SQLite. Now it's required for
|
||||
all databases.
|
||||
|
||||
..
|
||||
Libs release dates:
|
||||
GEOS 3.4.0 2013-08-11
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue