functions.txt 20 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551
  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:`MakeValid` :class:`AsGML` :class:`MemSize`
  21. :class:`GeometryDistance` :class:`Centroid` :class:`SymDifference` :class:`Reverse` :class:`AsKML` :class:`NumGeometries`
  22. :class:`Length` :class:`Envelope` :class:`Union` :class:`Scale` :class:`AsSVG` :class:`NumPoints`
  23. :class:`Perimeter` :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
  31. <https://dev.mysql.com/doc/refman/en/gis-polygon-property-functions.html#function_area>`__,
  32. Oracle, `PostGIS <https://postgis.net/docs/ST_Area.html>`__, SpatiaLite
  33. Accepts a single geographic field or expression and returns the area of the
  34. field as an :class:`~django.contrib.gis.measure.Area` measure.
  35. MySQL and SpatiaLite without LWGEOM don't support area calculations on
  36. geographic SRSes.
  37. ``AsGeoJSON``
  38. =============
  39. .. class:: AsGeoJSON(expression, bbox=False, crs=False, precision=8, **extra)
  40. *Availability*: `MySQL
  41. <https://dev.mysql.com/doc/refman/en/spatial-geojson-functions.html#function_st-asgeojson>`__ (≥ 5.7.5),
  42. `PostGIS <https://postgis.net/docs/ST_AsGeoJSON.html>`__, SpatiaLite
  43. Accepts a single geographic field or expression and returns a `GeoJSON
  44. <http://geojson.org/>`_ representation of the geometry. Note that the result is
  45. not a complete GeoJSON structure but only the ``geometry`` key content of a
  46. GeoJSON structure. See also :doc:`/ref/contrib/gis/serializers`.
  47. Example::
  48. >>> City.objects.annotate(json=AsGeoJSON('point')).get(name='Chicago').json
  49. {"type":"Point","coordinates":[-87.65018,41.85039]}
  50. ===================== =====================================================
  51. Keyword Argument Description
  52. ===================== =====================================================
  53. ``bbox`` Set this to ``True`` if you want the bounding box
  54. to be included in the returned GeoJSON.
  55. ``crs`` Set this to ``True`` if you want the coordinate
  56. reference system to be included in the returned
  57. GeoJSON. Ignored on MySQL.
  58. ``precision`` It may be used to specify the number of significant
  59. digits for the coordinates in the GeoJSON
  60. representation -- the default value is 8.
  61. ===================== =====================================================
  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. __ https://www.w3.org/Graphics/SVG/
  119. ``Azimuth``
  120. ===========
  121. .. class:: Azimuth(point_a, point_b, **extra)
  122. *Availability*: `PostGIS <https://postgis.net/docs/ST_Azimuth.html>`__,
  123. SpatiaLite (LWGEOM)
  124. Returns the azimuth in radians of the segment defined by the given point
  125. geometries, or ``None`` if the two points are coincident. The azimuth is angle
  126. referenced from north and is positive clockwise: north = ``0``; east = ``π/2``;
  127. south = ``π``; west = ``3π/2``.
  128. ``BoundingCircle``
  129. ==================
  130. .. class:: BoundingCircle(expression, num_seg=48, **extra)
  131. *Availability*: `PostGIS <https://postgis.net/docs/ST_MinimumBoundingCircle.html>`__,
  132. `Oracle <https://docs.oracle.com/en/database/oracle/oracle-database/18/spatl/
  133. SDO_GEOM-reference.html#GUID-82A61626-BB64-4793-B53D-A0DBEC91831A>`_
  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. `Oracle <https://docs.oracle.com/en/database/oracle/oracle-database/18/spatl/
  196. SDO_GEOM-reference.html#GUID-646638D0-2C5F-490A-AF63-DE9B7A4C97C1__CHDJCEIH>`__,
  197. `PostGIS <https://postgis.net/docs/ST_Envelope.html>`__, SpatiaLite
  198. Accepts a single geographic field or expression and returns the geometry
  199. representing the bounding box of the geometry.
  200. .. versionchanged:: 2.2
  201. Oracle support was added.
  202. ``ForcePolygonCW``
  203. ==================
  204. .. class:: ForcePolygonCW(expression, **extra)
  205. *Availability*: `PostGIS <https://postgis.net/docs/ST_ForcePolygonCW.html>`__,
  206. SpatiaLite
  207. Accepts a single geographic field or expression and returns a modified version
  208. of the polygon/multipolygon in which all exterior rings are oriented clockwise
  209. and all interior rings are oriented counterclockwise. Non-polygonal geometries
  210. are returned unchanged.
  211. ``GeoHash``
  212. ===========
  213. .. class:: GeoHash(expression, precision=None, **extra)
  214. *Availability*: `MySQL
  215. <https://dev.mysql.com/doc/refman/en/spatial-geohash-functions.html#function_st-geohash>`__ (≥ 5.7.5),
  216. `PostGIS <https://postgis.net/docs/ST_GeoHash.html>`__, SpatiaLite (LWGEOM)
  217. Accepts a single geographic field or expression and returns a `GeoHash`__
  218. representation of the geometry.
  219. The ``precision`` keyword argument controls the number of characters in the
  220. result.
  221. __ https://en.wikipedia.org/wiki/Geohash
  222. ``GeometryDistance``
  223. ====================
  224. .. class:: GeometryDistance(expr1, expr2, **extra)
  225. .. versionadded:: 3.0
  226. *Availability*: `PostGIS <https://postgis.net/docs/geometry_distance_knn.html>`__
  227. Accepts two geographic fields or expressions and returns the distance between
  228. them. When used in an :meth:`~django.db.models.query.QuerySet.order_by` clause,
  229. it provides index-assisted nearest-neighbor result sets.
  230. ``Intersection``
  231. ================
  232. .. class:: Intersection(expr1, expr2, **extra)
  233. *Availability*: `MySQL
  234. <https://dev.mysql.com/doc/refman/en/spatial-operator-functions.html#function_st-intersection>`__,
  235. `PostGIS <https://postgis.net/docs/ST_Intersection.html>`__, Oracle, SpatiaLite
  236. Accepts two geographic fields or expressions and returns the geometric
  237. intersection between them.
  238. ``IsValid``
  239. ===========
  240. .. class:: IsValid(expr)
  241. *Availability*: `MySQL
  242. <https://dev.mysql.com/doc/refman/en/spatial-convenience-functions.html#function_st-isvalid>`__ (≥ 5.7.5),
  243. `PostGIS <https://postgis.net/docs/ST_IsValid.html>`__, Oracle, SpatiaLite (LWGEOM)
  244. Accepts a geographic field or expression and tests if the value is well formed.
  245. Returns ``True`` if its value is a valid geometry and ``False`` otherwise.
  246. ``Length``
  247. ==========
  248. .. class:: Length(expression, spheroid=True, **extra)
  249. *Availability*: `MySQL
  250. <https://dev.mysql.com/doc/refman/en/gis-linestring-property-functions.html#function_st-length>`__,
  251. Oracle, `PostGIS <https://postgis.net/docs/ST_Length.html>`__, SpatiaLite
  252. Accepts a single geographic linestring or multilinestring field or expression
  253. and returns its length as a :class:`~django.contrib.gis.measure.Distance`
  254. measure.
  255. On PostGIS and SpatiaLite, when the coordinates are geodetic (angular), you can
  256. specify if the calculation should be based on a simple sphere (less
  257. accurate, less resource-intensive) or on a spheroid (more accurate, more
  258. resource-intensive) with the ``spheroid`` keyword argument.
  259. MySQL doesn't support length calculations on geographic SRSes.
  260. ``LineLocatePoint``
  261. ===================
  262. .. class:: LineLocatePoint(linestring, point, **extra)
  263. *Availability*: `PostGIS <https://postgis.net/docs/ST_LineLocatePoint.html>`__,
  264. SpatiaLite
  265. Returns a float between 0 and 1 representing the location of the closest point on
  266. ``linestring`` to the given ``point``, as a fraction of the 2D line length.
  267. ``MakeValid``
  268. =============
  269. .. class:: MakeValid(expr)
  270. *Availability*: `PostGIS <https://postgis.net/docs/ST_MakeValid.html>`__,
  271. SpatiaLite (LWGEOM)
  272. Accepts a geographic field or expression and attempts to convert the value into
  273. a valid geometry without losing any of the input vertices. Geometries that are
  274. already valid are returned without changes. Simple polygons might become a
  275. multipolygon and the result might be of lower dimension than the input.
  276. ``MemSize``
  277. ===========
  278. .. class:: MemSize(expression, **extra)
  279. *Availability*: `PostGIS <https://postgis.net/docs/ST_MemSize.html>`__
  280. Accepts a single geographic field or expression and returns the memory size
  281. (number of bytes) that the geometry field takes.
  282. ``NumGeometries``
  283. =================
  284. .. class:: NumGeometries(expression, **extra)
  285. *Availability*: `MySQL
  286. <https://dev.mysql.com/doc/refman/en/gis-geometrycollection-property-functions.html#function_st-numgeometries>`__,
  287. `PostGIS <https://postgis.net/docs/ST_NumGeometries.html>`__, Oracle,
  288. SpatiaLite
  289. Accepts a single geographic field or expression and returns the number of
  290. geometries if the geometry field is a collection (e.g., a ``GEOMETRYCOLLECTION``
  291. or ``MULTI*`` field). Returns 1 for single geometries.
  292. On MySQL, returns ``None`` for single geometries.
  293. ``NumPoints``
  294. =============
  295. .. class:: NumPoints(expression, **extra)
  296. *Availability*: `MySQL
  297. <https://dev.mysql.com/doc/refman/en/gis-linestring-property-functions.html#function_st-numpoints>`__,
  298. `PostGIS <https://postgis.net/docs/ST_NPoints.html>`__, Oracle, SpatiaLite
  299. Accepts a single geographic field or expression and returns the number of points
  300. in a geometry.
  301. On MySQL, returns ``None`` for any non-``LINESTRING`` geometry.
  302. ``Perimeter``
  303. =============
  304. .. class:: Perimeter(expression, **extra)
  305. *Availability*: `PostGIS <https://postgis.net/docs/ST_Perimeter.html>`__,
  306. Oracle, SpatiaLite
  307. Accepts a single geographic field or expression and returns the perimeter of the
  308. geometry field as a :class:`~django.contrib.gis.measure.Distance` object.
  309. ``PointOnSurface``
  310. ==================
  311. .. class:: PointOnSurface(expression, **extra)
  312. *Availability*: `PostGIS <https://postgis.net/docs/ST_PointOnSurface.html>`__,
  313. Oracle, SpatiaLite
  314. Accepts a single geographic field or expression and returns a ``Point`` geometry
  315. guaranteed to lie on the surface of the field; otherwise returns ``None``.
  316. ``Reverse``
  317. ===========
  318. .. class:: Reverse(expression, **extra)
  319. *Availability*: `PostGIS <https://postgis.net/docs/ST_Reverse.html>`__, Oracle,
  320. SpatiaLite
  321. Accepts a single geographic field or expression and returns a geometry with
  322. reversed coordinates.
  323. ``Scale``
  324. =========
  325. .. class:: Scale(expression, x, y, z=0.0, **extra)
  326. *Availability*: `PostGIS <https://postgis.net/docs/ST_Scale.html>`__, SpatiaLite
  327. Accepts a single geographic field or expression and returns a geometry with
  328. scaled coordinates by multiplying them with the ``x``, ``y``, and optionally
  329. ``z`` parameters.
  330. ``SnapToGrid``
  331. ==============
  332. .. class:: SnapToGrid(expression, *args, **extra)
  333. *Availability*: `PostGIS <https://postgis.net/docs/ST_SnapToGrid.html>`__,
  334. SpatiaLite
  335. Accepts a single geographic field or expression and returns a geometry with all
  336. points snapped to the given grid. How the geometry is snapped to the grid
  337. depends on how many numeric (either float, integer, or long) arguments are
  338. given.
  339. =================== =====================================================
  340. Number of Arguments Description
  341. =================== =====================================================
  342. 1 A single size to snap both the X and Y grids to.
  343. 2 X and Y sizes to snap the grid to.
  344. 4 X, Y sizes and the corresponding X, Y origins.
  345. =================== =====================================================
  346. ``SymDifference``
  347. =================
  348. .. class:: SymDifference(expr1, expr2, **extra)
  349. *Availability*: `MySQL
  350. <https://dev.mysql.com/doc/refman/en/spatial-operator-functions.html#function_st-symdifference>`__,
  351. `PostGIS <https://postgis.net/docs/ST_SymDifference.html>`__, Oracle,
  352. SpatiaLite
  353. Accepts two geographic fields or expressions and returns the geometric
  354. symmetric difference (union without the intersection) between the given
  355. parameters.
  356. ``Transform``
  357. =============
  358. .. class:: Transform(expression, srid, **extra)
  359. *Availability*: `PostGIS <https://postgis.net/docs/ST_Transform.html>`__,
  360. Oracle, SpatiaLite
  361. Accepts a geographic field or expression and a SRID integer code, and returns
  362. the transformed geometry to the spatial reference system specified by the
  363. ``srid`` parameter.
  364. .. note::
  365. What spatial reference system an integer SRID corresponds to may depend on
  366. the spatial database used. In other words, the SRID numbers used for Oracle
  367. are not necessarily the same as those used by PostGIS.
  368. ``Translate``
  369. =============
  370. .. class:: Translate(expression, x, y, z=0.0, **extra)
  371. *Availability*: `PostGIS <https://postgis.net/docs/ST_Translate.html>`__,
  372. SpatiaLite
  373. Accepts a single geographic field or expression and returns a geometry with
  374. its coordinates offset by the ``x``, ``y``, and optionally ``z`` numeric
  375. parameters.
  376. ``Union``
  377. =========
  378. .. class:: Union(expr1, expr2, **extra)
  379. *Availability*: `MySQL
  380. <https://dev.mysql.com/doc/refman/en/spatial-operator-functions.html#function_st-union>`__,
  381. `PostGIS <https://postgis.net/docs/ST_Union.html>`__, Oracle, SpatiaLite
  382. Accepts two geographic fields or expressions and returns the union of both
  383. geometries.