functions.txt 22 KB

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