Corrected docs regarding MySQL support of Length GIS function.
This commit is contained in:
parent
45d65fc3f2
commit
33421ed10c
|
@ -359,19 +359,19 @@ Returns ``True`` if its value is a valid geometry and ``False`` otherwise.
|
||||||
<https://postgis.net/docs/ST_Length.html>`__, SpatiaLite
|
<https://postgis.net/docs/ST_Length.html>`__, SpatiaLite
|
||||||
|
|
||||||
Accepts a single geographic linestring or multilinestring field or expression
|
Accepts a single geographic linestring or multilinestring field or expression
|
||||||
and returns its length as an :class:`~django.contrib.gis.measure.Distance`
|
and returns its length as a :class:`~django.contrib.gis.measure.Distance`
|
||||||
measure. On MySQL, a raw float value is returned when the coordinates
|
measure.
|
||||||
are geodetic.
|
|
||||||
|
|
||||||
On PostGIS and SpatiaLite, when the coordinates are geodetic (angular), you can
|
On PostGIS and SpatiaLite, when the coordinates are geodetic (angular), you can
|
||||||
specify if the calculation should be based on a simple sphere (less
|
specify if the calculation should be based on a simple sphere (less
|
||||||
accurate, less resource-intensive) or on a spheroid (more accurate, more
|
accurate, less resource-intensive) or on a spheroid (more accurate, more
|
||||||
resource-intensive) with the ``spheroid`` keyword argument.
|
resource-intensive) with the ``spheroid`` keyword argument.
|
||||||
|
|
||||||
|
MySQL doesn't support length calculations on geographic SRSes.
|
||||||
|
|
||||||
.. versionchanged:: 1.11
|
.. versionchanged:: 1.11
|
||||||
|
|
||||||
In older versions, a raw value was returned on MySQL when used on
|
In older versions, a raw value was returned on MySQL.
|
||||||
projected SRS.
|
|
||||||
|
|
||||||
``LineLocatePoint``
|
``LineLocatePoint``
|
||||||
===================
|
===================
|
||||||
|
|
Loading…
Reference in New Issue