functions.txt 20 KB

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