2
0

functions.txt 20 KB

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