functions.txt 18 KB

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