functions.txt 20 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549
  1. =============================
  2. Geographic Database Functions
  3. =============================
  4. .. module:: django.contrib.gis.db.models.functions
  5. :synopsis: Geographic Database Functions
  6. The functions documented on this page allow users to access geographic database
  7. functions to be used in annotations, aggregations, or filters in Django.
  8. Example::
  9. >>> from django.contrib.gis.db.models.functions import Length
  10. >>> Track.objects.annotate(length=Length('line')).filter(length__gt=100)
  11. Not all backends support all functions, so refer to the documentation of each
  12. function to see if your database backend supports the function you want to use.
  13. If you call a geographic function on a backend that doesn't support it, you'll
  14. get a ``NotImplementedError`` exception.
  15. Function's summary:
  16. ================== ======================== ====================== ======================= ================== =====================
  17. Measurement Relationships Operations Editors Output format Miscellaneous
  18. ================== ======================== ====================== ======================= ================== =====================
  19. :class:`Area` :class:`Azimuth` :class:`Difference` :class:`ForcePolygonCW` :class:`AsGeoJSON` :class:`IsValid`
  20. :class:`Distance` :class:`BoundingCircle` :class:`Intersection` :class:`ForceRHR` :class:`AsGML` :class:`MemSize`
  21. :class:`Length` :class:`Centroid` :class:`SymDifference` :class:`MakeValid` :class:`AsKML` :class:`NumGeometries`
  22. :class:`Perimeter` :class:`Envelope` :class:`Union` :class:`Reverse` :class:`AsSVG` :class:`NumPoints`
  23. .. :class:`LineLocatePoint` :class:`Scale` :class:`GeoHash`
  24. .. :class:`PointOnSurface` :class:`SnapToGrid`
  25. .. :class:`Transform`
  26. .. :class:`Translate`
  27. ================== ======================== ====================== ======================= ================== =====================
  28. ``Area``
  29. ========
  30. .. class:: Area(expression, **extra)
  31. *Availability*: `MySQL
  32. <https://dev.mysql.com/doc/refman/en/gis-polygon-property-functions.html#function_area>`__,
  33. Oracle, `PostGIS <https://postgis.net/docs/ST_Area.html>`__, SpatiaLite
  34. Accepts a single geographic field or expression and returns the area of the
  35. field as an :class:`~django.contrib.gis.measure.Area` measure.
  36. MySQL and SpatiaLite without LWGEOM don't support area calculations on
  37. geographic SRSes.
  38. ``AsGeoJSON``
  39. =============
  40. .. class:: AsGeoJSON(expression, bbox=False, crs=False, precision=8, **extra)
  41. *Availability*: `MySQL
  42. <https://dev.mysql.com/doc/refman/en/spatial-geojson-functions.html#function_st-asgeojson>`__ (≥ 5.7.5),
  43. `PostGIS <https://postgis.net/docs/ST_AsGeoJSON.html>`__, SpatiaLite
  44. Accepts a single geographic field or expression and returns a `GeoJSON
  45. <http://geojson.org/>`_ representation of the geometry. Note that the result is
  46. not a complete GeoJSON structure but only the ``geometry`` key content of a
  47. GeoJSON structure. See also :doc:`/ref/contrib/gis/serializers`.
  48. Example::
  49. >>> City.objects.annotate(json=AsGeoJSON('point')).get(name='Chicago').json
  50. {"type":"Point","coordinates":[-87.65018,41.85039]}
  51. ===================== =====================================================
  52. Keyword Argument Description
  53. ===================== =====================================================
  54. ``bbox`` Set this to ``True`` if you want the bounding box
  55. to be included in the returned GeoJSON.
  56. ``crs`` Set this to ``True`` if you want the coordinate
  57. reference system to be included in the returned
  58. GeoJSON. Ignored on MySQL.
  59. ``precision`` It may be used to specify the number of significant
  60. digits for the coordinates in the GeoJSON
  61. representation -- the default value is 8.
  62. ===================== =====================================================
  63. ``AsGML``
  64. =========
  65. .. class:: AsGML(expression, version=2, precision=8, **extra)
  66. *Availability*: Oracle, `PostGIS <https://postgis.net/docs/ST_AsGML.html>`__,
  67. SpatiaLite
  68. Accepts a single geographic field or expression and returns a `Geographic Markup
  69. Language (GML)`__ representation of the geometry.
  70. Example::
  71. >>> qs = Zipcode.objects.annotate(gml=AsGML('poly'))
  72. >>> print(qs[0].gml)
  73. <gml:Polygon srsName="EPSG:4326"><gml:OuterBoundaryIs>-147.78711,70.245363 ...
  74. -147.78711,70.245363</gml:OuterBoundaryIs></gml:Polygon>
  75. ===================== =====================================================
  76. Keyword Argument Description
  77. ===================== =====================================================
  78. ``precision`` Specifies the number of significant digits for the
  79. coordinates in the GML representation -- the default
  80. value is 8. Ignored on Oracle.
  81. ``version`` Specifies the GML version to use: 2 (default) or 3.
  82. ===================== =====================================================
  83. __ https://en.wikipedia.org/wiki/Geography_Markup_Language
  84. ``AsKML``
  85. =========
  86. .. class:: AsKML(expression, precision=8, **extra)
  87. *Availability*: `PostGIS <https://postgis.net/docs/ST_AsKML.html>`__, SpatiaLite
  88. Accepts a single geographic field or expression and returns a `Keyhole Markup
  89. Language (KML)`__ representation of the geometry.
  90. Example::
  91. >>> qs = Zipcode.objects.annotate(kml=AsKML('poly'))
  92. >>> print(qs[0].kml)
  93. <Polygon><outerBoundaryIs><LinearRing><coordinates>-103.04135,36.217596,0 ...
  94. -103.04135,36.217596,0</coordinates></LinearRing></outerBoundaryIs></Polygon>
  95. ===================== =====================================================
  96. Keyword Argument Description
  97. ===================== =====================================================
  98. ``precision`` This keyword may be used to specify the number of
  99. significant digits for the coordinates in the KML
  100. representation -- the default value is 8.
  101. ===================== =====================================================
  102. __ https://developers.google.com/kml/documentation/
  103. ``AsSVG``
  104. =========
  105. .. class:: AsSVG(expression, relative=False, precision=8, **extra)
  106. *Availability*: `PostGIS <https://postgis.net/docs/ST_AsSVG.html>`__, SpatiaLite
  107. Accepts a single geographic field or expression and returns a `Scalable Vector
  108. Graphics (SVG)`__ representation of the geometry.
  109. ===================== =====================================================
  110. Keyword Argument Description
  111. ===================== =====================================================
  112. ``relative`` If set to ``True``, the path data will be implemented
  113. in terms of relative moves. Defaults to ``False``,
  114. meaning that absolute moves are used instead.
  115. ``precision`` This keyword may be used to specify the number of
  116. significant digits for the coordinates in the SVG
  117. representation -- the default value is 8.
  118. ===================== =====================================================
  119. __ https://www.w3.org/Graphics/SVG/
  120. ``Azimuth``
  121. ===========
  122. .. class:: Azimuth(point_a, point_b, **extra)
  123. *Availability*: `PostGIS <https://postgis.net/docs/ST_Azimuth.html>`__,
  124. SpatiaLite (LWGEOM)
  125. Returns the azimuth in radians of the segment defined by the given point
  126. geometries, or ``None`` if the two points are coincident. The azimuth is angle
  127. referenced from north and is positive clockwise: north = ``0``; east = ``π/2``;
  128. south = ``π``; west = ``3π/2``.
  129. ``BoundingCircle``
  130. ==================
  131. .. class:: BoundingCircle(expression, num_seg=48, **extra)
  132. *Availability*: `PostGIS <https://postgis.net/docs/ST_MinimumBoundingCircle.html>`__,
  133. `Oracle <https://docs.oracle.com/database/121/SPATL/sdo_geom-sdo_mbc.htm#SPATL1554>`_
  134. Accepts a single geographic field or expression and returns the smallest circle
  135. polygon that can fully contain the geometry.
  136. The ``num_seg`` parameter is used only on PostGIS.
  137. ``Centroid``
  138. ============
  139. .. class:: Centroid(expression, **extra)
  140. *Availability*: `MySQL
  141. <https://dev.mysql.com/doc/refman/en/gis-polygon-property-functions.html#function_st-centroid>`__,
  142. `PostGIS <https://postgis.net/docs/ST_Centroid.html>`__, Oracle, SpatiaLite
  143. Accepts a single geographic field or expression and returns the ``centroid``
  144. value of the geometry.
  145. ``Difference``
  146. ==============
  147. .. class:: Difference(expr1, expr2, **extra)
  148. *Availability*: `MySQL
  149. <https://dev.mysql.com/doc/refman/en/spatial-operator-functions.html#function_st-difference>`__,
  150. `PostGIS <https://postgis.net/docs/ST_Difference.html>`__, Oracle, SpatiaLite
  151. Accepts two geographic fields or expressions and returns the geometric
  152. difference, that is the part of geometry A that does not intersect with
  153. geometry B.
  154. ``Distance``
  155. ============
  156. .. class:: Distance(expr1, expr2, spheroid=None, **extra)
  157. *Availability*: `MySQL
  158. <https://dev.mysql.com/doc/refman/en/spatial-relation-functions-object-shapes.html#function_st-distance>`__,
  159. `PostGIS <https://postgis.net/docs/ST_Distance.html>`__, Oracle, SpatiaLite
  160. Accepts two geographic fields or expressions and returns the distance between
  161. them, as a :class:`~django.contrib.gis.measure.Distance` object. On MySQL, a raw
  162. float value is returned when the coordinates are geodetic.
  163. On backends that support distance calculation on geodetic coordinates, the
  164. proper backend function is automatically chosen depending on the SRID value of
  165. the geometries (e.g. `ST_DistanceSphere
  166. <https://postgis.net/docs/ST_DistanceSphere.html>`__ on PostGIS).
  167. When distances are calculated with geodetic (angular) coordinates, as is the
  168. case with the default WGS84 (4326) SRID, you can set the ``spheroid`` keyword
  169. argument to decide if the calculation should be based on a simple sphere (less
  170. accurate, less resource-intensive) or on a spheroid (more accurate, more
  171. resource-intensive).
  172. In the following example, the distance from the city of Hobart to every other
  173. :class:`~django.contrib.gis.db.models.PointField` in the ``AustraliaCity``
  174. queryset is calculated::
  175. >>> from django.contrib.gis.db.models.functions import Distance
  176. >>> pnt = AustraliaCity.objects.get(name='Hobart').point
  177. >>> for city in AustraliaCity.objects.annotate(distance=Distance('point', pnt)):
  178. ... print(city.name, city.distance)
  179. Wollongong 990071.220408 m
  180. Shellharbour 972804.613941 m
  181. Thirroul 1002334.36351 m
  182. ...
  183. .. note::
  184. Because the ``distance`` attribute is a
  185. :class:`~django.contrib.gis.measure.Distance` object, you can easily express
  186. the value in the units of your choice. For example, ``city.distance.mi`` is
  187. the distance value in miles and ``city.distance.km`` is the distance value
  188. in kilometers. See :doc:`measure` for usage details and the list of
  189. :ref:`supported_units`.
  190. ``Envelope``
  191. ============
  192. .. class:: Envelope(expression, **extra)
  193. *Availability*: `MySQL
  194. <https://dev.mysql.com/doc/refman/en/gis-general-property-functions.html#function_st-envelope>`__,
  195. `PostGIS <https://postgis.net/docs/ST_Envelope.html>`__, SpatiaLite
  196. Accepts a single geographic field or expression and returns the geometry
  197. representing the bounding box of the geometry.
  198. ``ForcePolygonCW``
  199. ==================
  200. .. class:: ForcePolygonCW(expression, **extra)
  201. .. versionadded:: 2.1
  202. *Availability*: `PostGIS <https://postgis.net/docs/ST_ForcePolygonCW.html>`__,
  203. SpatiaLite
  204. Accepts a single geographic field or expression and returns a modified version
  205. of the polygon/multipolygon in which all exterior rings are oriented clockwise
  206. and all interior rings are oriented counterclockwise. Non-polygonal geometries
  207. are returned unchanged.
  208. ``ForceRHR``
  209. ============
  210. .. class:: ForceRHR(expression, **extra)
  211. .. deprecated:: 2.1
  212. Use :class:`ForcePolygonCW` instead.
  213. *Availability*: `PostGIS <https://postgis.net/docs/ST_ForceRHR.html>`__
  214. Accepts a single geographic field or expression and returns a modified version
  215. of the polygon/multipolygon in which all of the vertices follow the
  216. right-hand rule.
  217. ``GeoHash``
  218. ===========
  219. .. class:: GeoHash(expression, precision=None, **extra)
  220. *Availability*: `MySQL
  221. <https://dev.mysql.com/doc/refman/en/spatial-geohash-functions.html#function_st-geohash>`__ (≥ 5.7.5),
  222. `PostGIS <https://postgis.net/docs/ST_GeoHash.html>`__, SpatiaLite (LWGEOM)
  223. Accepts a single geographic field or expression and returns a `GeoHash`__
  224. representation of the geometry.
  225. The ``precision`` keyword argument controls the number of characters in the
  226. result.
  227. __ https://en.wikipedia.org/wiki/Geohash
  228. ``Intersection``
  229. ================
  230. .. class:: Intersection(expr1, expr2, **extra)
  231. *Availability*: `MySQL
  232. <https://dev.mysql.com/doc/refman/en/spatial-operator-functions.html#function_st-intersection>`__,
  233. `PostGIS <https://postgis.net/docs/ST_Intersection.html>`__, Oracle, SpatiaLite
  234. Accepts two geographic fields or expressions and returns the geometric
  235. intersection between them.
  236. ``IsValid``
  237. ===========
  238. .. class:: IsValid(expr)
  239. *Availability*: `MySQL
  240. <https://dev.mysql.com/doc/refman/en/spatial-convenience-functions.html#function_st-isvalid>`__ (≥ 5.7.5),
  241. `PostGIS <https://postgis.net/docs/ST_IsValid.html>`__, Oracle, SpatiaLite (LWGEOM)
  242. Accepts a geographic field or expression and tests if the value is well formed.
  243. Returns ``True`` if its value is a valid geometry and ``False`` otherwise.
  244. ``Length``
  245. ==========
  246. .. class:: Length(expression, spheroid=True, **extra)
  247. *Availability*: `MySQL
  248. <https://dev.mysql.com/doc/refman/en/gis-linestring-property-functions.html#function_st-length>`__,
  249. Oracle, `PostGIS <https://postgis.net/docs/ST_Length.html>`__, SpatiaLite
  250. Accepts a single geographic linestring or multilinestring field or expression
  251. and returns its length as a :class:`~django.contrib.gis.measure.Distance`
  252. measure.
  253. On PostGIS and SpatiaLite, when the coordinates are geodetic (angular), you can
  254. specify if the calculation should be based on a simple sphere (less
  255. accurate, less resource-intensive) or on a spheroid (more accurate, more
  256. resource-intensive) with the ``spheroid`` keyword argument.
  257. MySQL doesn't support length calculations on geographic SRSes.
  258. ``LineLocatePoint``
  259. ===================
  260. .. class:: LineLocatePoint(linestring, point, **extra)
  261. *Availability*: `PostGIS <https://postgis.net/docs/ST_LineLocatePoint.html>`__,
  262. SpatiaLite
  263. Returns a float between 0 and 1 representing the location of the closest point on
  264. ``linestring`` to the given ``point``, as a fraction of the 2D line length.
  265. ``MakeValid``
  266. =============
  267. .. class:: MakeValid(expr)
  268. *Availability*: `PostGIS <https://postgis.net/docs/ST_MakeValid.html>`__,
  269. SpatiaLite (LWGEOM)
  270. Accepts a geographic field or expression and attempts to convert the value into
  271. a valid geometry without losing any of the input vertices. Geometries that are
  272. already valid are returned without changes. Simple polygons might become a
  273. multipolygon and the result might be of lower dimension than the input.
  274. ``MemSize``
  275. ===========
  276. .. class:: MemSize(expression, **extra)
  277. *Availability*: `PostGIS <https://postgis.net/docs/ST_MemSize.html>`__
  278. Accepts a single geographic field or expression and returns the memory size
  279. (number of bytes) that the geometry field takes.
  280. ``NumGeometries``
  281. =================
  282. .. class:: NumGeometries(expression, **extra)
  283. *Availability*: `MySQL
  284. <https://dev.mysql.com/doc/refman/en/gis-geometrycollection-property-functions.html#function_st-numgeometries>`__,
  285. `PostGIS <https://postgis.net/docs/ST_NumGeometries.html>`__, Oracle,
  286. SpatiaLite
  287. Accepts a single geographic field or expression and returns the number of
  288. geometries if the geometry field is a collection (e.g., a ``GEOMETRYCOLLECTION``
  289. or ``MULTI*`` field). Returns 1 for single geometries.
  290. On MySQL, returns ``None`` for single geometries.
  291. ``NumPoints``
  292. =============
  293. .. class:: NumPoints(expression, **extra)
  294. *Availability*: `MySQL
  295. <https://dev.mysql.com/doc/refman/en/gis-linestring-property-functions.html#function_st-numpoints>`__,
  296. `PostGIS <https://postgis.net/docs/ST_NPoints.html>`__, Oracle, SpatiaLite
  297. Accepts a single geographic field or expression and returns the number of points
  298. in a geometry.
  299. On MySQL, returns ``None`` for any non-``LINESTRING`` geometry.
  300. ``Perimeter``
  301. =============
  302. .. class:: Perimeter(expression, **extra)
  303. *Availability*: `PostGIS <https://postgis.net/docs/ST_Perimeter.html>`__,
  304. Oracle, SpatiaLite
  305. Accepts a single geographic field or expression and returns the perimeter of the
  306. geometry field as a :class:`~django.contrib.gis.measure.Distance` object.
  307. ``PointOnSurface``
  308. ==================
  309. .. class:: PointOnSurface(expression, **extra)
  310. *Availability*: `PostGIS <https://postgis.net/docs/ST_PointOnSurface.html>`__,
  311. Oracle, SpatiaLite
  312. Accepts a single geographic field or expression and returns a ``Point`` geometry
  313. guaranteed to lie on the surface of the field; otherwise returns ``None``.
  314. ``Reverse``
  315. ===========
  316. .. class:: Reverse(expression, **extra)
  317. *Availability*: `PostGIS <https://postgis.net/docs/ST_Reverse.html>`__, Oracle,
  318. SpatiaLite
  319. Accepts a single geographic field or expression and returns a geometry with
  320. reversed coordinates.
  321. ``Scale``
  322. =========
  323. .. class:: Scale(expression, x, y, z=0.0, **extra)
  324. *Availability*: `PostGIS <https://postgis.net/docs/ST_Scale.html>`__, SpatiaLite
  325. Accepts a single geographic field or expression and returns a geometry with
  326. scaled coordinates by multiplying them with the ``x``, ``y``, and optionally
  327. ``z`` parameters.
  328. ``SnapToGrid``
  329. ==============
  330. .. class:: SnapToGrid(expression, *args, **extra)
  331. *Availability*: `PostGIS <https://postgis.net/docs/ST_SnapToGrid.html>`__,
  332. SpatiaLite
  333. Accepts a single geographic field or expression and returns a geometry with all
  334. points snapped to the given grid. How the geometry is snapped to the grid
  335. depends on how many numeric (either float, integer, or long) arguments are
  336. given.
  337. =================== =====================================================
  338. Number of Arguments Description
  339. =================== =====================================================
  340. 1 A single size to snap both the X and Y grids to.
  341. 2 X and Y sizes to snap the grid to.
  342. 4 X, Y sizes and the corresponding X, Y origins.
  343. =================== =====================================================
  344. ``SymDifference``
  345. =================
  346. .. class:: SymDifference(expr1, expr2, **extra)
  347. *Availability*: `MySQL
  348. <https://dev.mysql.com/doc/refman/en/spatial-operator-functions.html#function_st-symdifference>`__,
  349. `PostGIS <https://postgis.net/docs/ST_SymDifference.html>`__, Oracle,
  350. SpatiaLite
  351. Accepts two geographic fields or expressions and returns the geometric
  352. symmetric difference (union without the intersection) between the given
  353. parameters.
  354. ``Transform``
  355. =============
  356. .. class:: Transform(expression, srid, **extra)
  357. *Availability*: `PostGIS <https://postgis.net/docs/ST_Transform.html>`__,
  358. Oracle, SpatiaLite
  359. Accepts a geographic field or expression and a SRID integer code, and returns
  360. the transformed geometry to the spatial reference system specified by the
  361. ``srid`` parameter.
  362. .. note::
  363. What spatial reference system an integer SRID corresponds to may depend on
  364. the spatial database used. In other words, the SRID numbers used for Oracle
  365. are not necessarily the same as those used by PostGIS.
  366. ``Translate``
  367. =============
  368. .. class:: Translate(expression, x, y, z=0.0, **extra)
  369. *Availability*: `PostGIS <https://postgis.net/docs/ST_Translate.html>`__,
  370. SpatiaLite
  371. Accepts a single geographic field or expression and returns a geometry with
  372. its coordinates offset by the ``x``, ``y``, and optionally ``z`` numeric
  373. parameters.
  374. ``Union``
  375. =========
  376. .. class:: Union(expr1, expr2, **extra)
  377. *Availability*: `MySQL
  378. <https://dev.mysql.com/doc/refman/en/spatial-operator-functions.html#function_st-union>`__,
  379. `PostGIS <https://postgis.net/docs/ST_Union.html>`__, Oracle, SpatiaLite
  380. Accepts two geographic fields or expressions and returns the union of both
  381. geometries.