functions.txt 24 KB

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