functions.txt 23 KB

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