functions.txt 24 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668
  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. SpatiaLite 5.1+
  165. Accepts a single geographic field or expression and returns the smallest circle
  166. polygon that can fully contain the geometry.
  167. The ``num_seg`` parameter is used only on PostGIS.
  168. .. versionchanged:: 5.1
  169. SpatiaLite 5.1+ support was added.
  170. ``Centroid``
  171. ============
  172. .. class:: Centroid(expression, **extra)
  173. *Availability*: MariaDB, `MySQL
  174. <https://dev.mysql.com/doc/refman/en/gis-polygon-property-functions.html#function_st-centroid>`__,
  175. `PostGIS <https://postgis.net/docs/ST_Centroid.html>`__, Oracle, SpatiaLite
  176. Accepts a single geographic field or expression and returns the ``centroid``
  177. value of the geometry.
  178. ``ClosestPoint``
  179. ================
  180. .. class:: ClosestPoint(expr1, expr2, **extra)
  181. *Availability*: `PostGIS <https://postgis.net/docs/ST_ClosestPoint.html>`__,
  182. SpatiaLite
  183. Accepts two geographic fields or expressions and returns the 2-dimensional
  184. point on geometry A that is closest to geometry B.
  185. ``Difference``
  186. ==============
  187. .. class:: Difference(expr1, expr2, **extra)
  188. *Availability*: MariaDB, `MySQL
  189. <https://dev.mysql.com/doc/refman/en/spatial-operator-functions.html#function_st-difference>`__,
  190. `PostGIS <https://postgis.net/docs/ST_Difference.html>`__, Oracle, SpatiaLite
  191. Accepts two geographic fields or expressions and returns the geometric
  192. difference, that is the part of geometry A that does not intersect with
  193. geometry B.
  194. ``Distance``
  195. ============
  196. .. class:: Distance(expr1, expr2, spheroid=None, **extra)
  197. *Availability*: MariaDB, `MySQL
  198. <https://dev.mysql.com/doc/refman/en/spatial-relation-functions-object-shapes.html#function_st-distance>`__,
  199. `PostGIS <https://postgis.net/docs/ST_Distance.html>`__, Oracle, SpatiaLite
  200. Accepts two geographic fields or expressions and returns the distance between
  201. them, as a :class:`~django.contrib.gis.measure.Distance` object. On MySQL, a raw
  202. float value is returned when the coordinates are geodetic.
  203. On backends that support distance calculation on geodetic coordinates, the
  204. proper backend function is automatically chosen depending on the SRID value of
  205. the geometries (e.g. `ST_DistanceSphere
  206. <https://postgis.net/docs/ST_DistanceSphere.html>`__ on PostGIS).
  207. When distances are calculated with geodetic (angular) coordinates, as is the
  208. case with the default WGS84 (4326) SRID, you can set the ``spheroid`` keyword
  209. argument to decide if the calculation should be based on a simple sphere (less
  210. accurate, less resource-intensive) or on a spheroid (more accurate, more
  211. resource-intensive).
  212. In the following example, the distance from the city of Hobart to every other
  213. :class:`~django.contrib.gis.db.models.PointField` in the ``AustraliaCity``
  214. queryset is calculated:
  215. .. code-block:: pycon
  216. >>> from django.contrib.gis.db.models.functions import Distance
  217. >>> pnt = AustraliaCity.objects.get(name="Hobart").point
  218. >>> for city in AustraliaCity.objects.annotate(distance=Distance("point", pnt)):
  219. ... print(city.name, city.distance)
  220. ...
  221. Wollongong 990071.220408 m
  222. Shellharbour 972804.613941 m
  223. Thirroul 1002334.36351 m
  224. ...
  225. .. note::
  226. Because the ``distance`` attribute is a
  227. :class:`~django.contrib.gis.measure.Distance` object, you can easily express
  228. the value in the units of your choice. For example, ``city.distance.mi`` is
  229. the distance value in miles and ``city.distance.km`` is the distance value
  230. in kilometers. See :doc:`measure` for usage details and the list of
  231. :ref:`supported_units`.
  232. ``Envelope``
  233. ============
  234. .. class:: Envelope(expression, **extra)
  235. *Availability*: MariaDB, `MySQL
  236. <https://dev.mysql.com/doc/refman/en/gis-general-property-functions.html#function_st-envelope>`__,
  237. `Oracle <https://docs.oracle.com/en/database/oracle/oracle-database/21/spatl/
  238. spatial-operators-reference.html#GUID-ACED800F-3435-44AA-9606-D40934A23ED0>`__,
  239. `PostGIS <https://postgis.net/docs/ST_Envelope.html>`__, SpatiaLite
  240. Accepts a single geographic field or expression and returns the geometry
  241. representing the bounding box of the geometry.
  242. ``ForcePolygonCW``
  243. ==================
  244. .. class:: ForcePolygonCW(expression, **extra)
  245. *Availability*: `PostGIS <https://postgis.net/docs/ST_ForcePolygonCW.html>`__,
  246. SpatiaLite
  247. Accepts a single geographic field or expression and returns a modified version
  248. of the polygon/multipolygon in which all exterior rings are oriented clockwise
  249. and all interior rings are oriented counterclockwise. Non-polygonal geometries
  250. are returned unchanged.
  251. ``FromWKB``
  252. ===========
  253. .. class:: FromWKB(expression, srid=0, **extra)
  254. *Availability*: MariaDB, `MySQL
  255. <https://dev.mysql.com/doc/refman/en/gis-wkb-functions.html#function_st-geomfromwkb>`__,
  256. Oracle, `PostGIS <https://postgis.net/docs/ST_GeomFromWKB.html>`__, SpatiaLite
  257. Creates geometry from `Well-known binary (WKB)`_ representation. The optional
  258. ``srid`` argument allows to specify the SRID of the resulting geometry.
  259. ``srid`` is ignored on Oracle.
  260. .. versionchanged:: 5.1
  261. The ``srid`` argument was added.
  262. ``FromWKT``
  263. ===========
  264. .. class:: FromWKT(expression, srid=0, **extra)
  265. *Availability*: MariaDB, `MySQL
  266. <https://dev.mysql.com/doc/refman/en/gis-wkt-functions.html#function_st-geomfromtext>`__,
  267. Oracle, `PostGIS <https://postgis.net/docs/ST_GeomFromText.html>`__, SpatiaLite
  268. Creates geometry from `Well-known text (WKT)`_ representation. The optional
  269. ``srid`` argument allows to specify the SRID of the resulting geometry.
  270. ``srid`` is ignored on Oracle.
  271. .. versionchanged:: 5.1
  272. The ``srid`` argument was added.
  273. ``GeoHash``
  274. ===========
  275. .. class:: GeoHash(expression, precision=None, **extra)
  276. *Availability*: MariaDB, `MySQL
  277. <https://dev.mysql.com/doc/refman/en/spatial-geohash-functions.html#function_st-geohash>`__,
  278. `PostGIS <https://postgis.net/docs/ST_GeoHash.html>`__, SpatiaLite
  279. (LWGEOM/RTTOPO)
  280. Accepts a single geographic field or expression and returns a `GeoHash`__
  281. representation of the geometry.
  282. The ``precision`` keyword argument controls the number of characters in the
  283. result.
  284. __ https://en.wikipedia.org/wiki/Geohash
  285. .. versionchanged:: 5.2
  286. MariaDB 11.7+ support was added.
  287. ``GeometryDistance``
  288. ====================
  289. .. class:: GeometryDistance(expr1, expr2, **extra)
  290. *Availability*: `PostGIS <https://postgis.net/docs/geometry_distance_knn.html>`__
  291. Accepts two geographic fields or expressions and returns the distance between
  292. them. When used in an :meth:`~django.db.models.query.QuerySet.order_by` clause,
  293. it provides index-assisted nearest-neighbor result sets.
  294. ``Intersection``
  295. ================
  296. .. class:: Intersection(expr1, expr2, **extra)
  297. *Availability*: MariaDB, `MySQL
  298. <https://dev.mysql.com/doc/refman/en/spatial-operator-functions.html#function_st-intersection>`__,
  299. `PostGIS <https://postgis.net/docs/ST_Intersection.html>`__, Oracle, SpatiaLite
  300. Accepts two geographic fields or expressions and returns the geometric
  301. intersection between them.
  302. ``IsEmpty``
  303. ===========
  304. .. class:: IsEmpty(expr)
  305. *Availability*: `PostGIS <https://postgis.net/docs/ST_IsEmpty.html>`__
  306. Accepts a geographic field or expression and tests if the value is an empty
  307. geometry. Returns ``True`` if its value is empty and ``False`` otherwise.
  308. ``IsValid``
  309. ===========
  310. .. class:: IsValid(expr)
  311. *Availability*: MariaDB, `MySQL
  312. <https://dev.mysql.com/doc/refman/en/spatial-convenience-functions.html#function_st-isvalid>`__,
  313. `PostGIS <https://postgis.net/docs/ST_IsValid.html>`__, Oracle, SpatiaLite
  314. Accepts a geographic field or expression and tests if the value is well formed.
  315. Returns ``True`` if its value is a valid geometry and ``False`` otherwise.
  316. .. versionchanged:: 5.2
  317. MariaDB 11.7+ support was added.
  318. ``Length``
  319. ==========
  320. .. class:: Length(expression, spheroid=True, **extra)
  321. *Availability*: MariaDB, `MySQL
  322. <https://dev.mysql.com/doc/refman/en/gis-linestring-property-functions.html#function_st-length>`__,
  323. Oracle, `PostGIS <https://postgis.net/docs/ST_Length.html>`__, SpatiaLite
  324. Accepts a single geographic linestring or multilinestring field or expression
  325. and returns its length as a :class:`~django.contrib.gis.measure.Distance`
  326. measure.
  327. On PostGIS and SpatiaLite, when the coordinates are geodetic (angular), you can
  328. specify if the calculation should be based on a simple sphere (less
  329. accurate, less resource-intensive) or on a spheroid (more accurate, more
  330. resource-intensive) with the ``spheroid`` keyword argument.
  331. MySQL doesn't support length calculations on geographic SRSes.
  332. ``LineLocatePoint``
  333. ===================
  334. .. class:: LineLocatePoint(linestring, point, **extra)
  335. *Availability*: `PostGIS <https://postgis.net/docs/ST_LineLocatePoint.html>`__,
  336. SpatiaLite
  337. Returns a float between 0 and 1 representing the location of the closest point on
  338. ``linestring`` to the given ``point``, as a fraction of the 2D line length.
  339. ``MakeValid``
  340. =============
  341. .. class:: MakeValid(expr)
  342. *Availability*: `PostGIS <https://postgis.net/docs/ST_MakeValid.html>`__,
  343. SpatiaLite (LWGEOM/RTTOPO)
  344. Accepts a geographic field or expression and attempts to convert the value into
  345. a valid geometry without losing any of the input vertices. Geometries that are
  346. already valid are returned without changes. Simple polygons might become a
  347. multipolygon and the result might be of lower dimension than the input.
  348. ``MemSize``
  349. ===========
  350. .. class:: MemSize(expression, **extra)
  351. *Availability*: `PostGIS <https://postgis.net/docs/ST_MemSize.html>`__
  352. Accepts a single geographic field or expression and returns the memory size
  353. (number of bytes) that the geometry field takes.
  354. ``NumGeometries``
  355. =================
  356. .. class:: NumGeometries(expression, **extra)
  357. *Availability*: MariaDB, `MySQL
  358. <https://dev.mysql.com/doc/refman/en/gis-geometrycollection-property-functions.html#function_st-numgeometries>`__,
  359. `PostGIS <https://postgis.net/docs/ST_NumGeometries.html>`__, Oracle,
  360. SpatiaLite
  361. Accepts a single geographic field or expression and returns the number of
  362. geometries if the geometry field is a collection (e.g., a ``GEOMETRYCOLLECTION``
  363. or ``MULTI*`` field). Returns 1 for single geometries.
  364. On MySQL, returns ``None`` for single geometries.
  365. ``NumPoints``
  366. =============
  367. .. class:: NumPoints(expression, **extra)
  368. *Availability*: MariaDB, `MySQL
  369. <https://dev.mysql.com/doc/refman/en/gis-linestring-property-functions.html#function_st-numpoints>`__,
  370. `PostGIS <https://postgis.net/docs/ST_NPoints.html>`__, Oracle, SpatiaLite
  371. Accepts a single geographic field or expression and returns the number of points
  372. in a geometry.
  373. On MySQL, returns ``None`` for any non-``LINESTRING`` geometry.
  374. ``Perimeter``
  375. =============
  376. .. class:: Perimeter(expression, **extra)
  377. *Availability*: `PostGIS <https://postgis.net/docs/ST_Perimeter.html>`__,
  378. Oracle, SpatiaLite
  379. Accepts a single geographic field or expression and returns the perimeter of the
  380. geometry field as a :class:`~django.contrib.gis.measure.Distance` object.
  381. ``PointOnSurface``
  382. ==================
  383. .. class:: PointOnSurface(expression, **extra)
  384. *Availability*: `PostGIS <https://postgis.net/docs/ST_PointOnSurface.html>`__,
  385. MariaDB, Oracle, SpatiaLite
  386. Accepts a single geographic field or expression and returns a ``Point`` geometry
  387. guaranteed to lie on the surface of the field; otherwise returns ``None``.
  388. ``Reverse``
  389. ===========
  390. .. class:: Reverse(expression, **extra)
  391. *Availability*: `PostGIS <https://postgis.net/docs/ST_Reverse.html>`__, Oracle,
  392. SpatiaLite
  393. Accepts a single geographic field or expression and returns a geometry with
  394. reversed coordinates.
  395. ``Scale``
  396. =========
  397. .. class:: Scale(expression, x, y, z=0.0, **extra)
  398. *Availability*: `PostGIS <https://postgis.net/docs/ST_Scale.html>`__, SpatiaLite
  399. Accepts a single geographic field or expression and returns a geometry with
  400. scaled coordinates by multiplying them with the ``x``, ``y``, and optionally
  401. ``z`` parameters.
  402. ``SnapToGrid``
  403. ==============
  404. .. class:: SnapToGrid(expression, *args, **extra)
  405. *Availability*: `PostGIS <https://postgis.net/docs/ST_SnapToGrid.html>`__,
  406. SpatiaLite
  407. Accepts a single geographic field or expression and returns a geometry with all
  408. points snapped to the given grid. How the geometry is snapped to the grid
  409. depends on how many numeric (either float, integer, or long) arguments are
  410. given.
  411. =================== =====================================================
  412. Number of Arguments Description
  413. =================== =====================================================
  414. 1 A single size to snap both the X and Y grids to.
  415. 2 X and Y sizes to snap the grid to.
  416. 4 X, Y sizes and the corresponding X, Y origins.
  417. =================== =====================================================
  418. ``SymDifference``
  419. =================
  420. .. class:: SymDifference(expr1, expr2, **extra)
  421. *Availability*: MariaDB, `MySQL
  422. <https://dev.mysql.com/doc/refman/en/spatial-operator-functions.html#function_st-symdifference>`__,
  423. `PostGIS <https://postgis.net/docs/ST_SymDifference.html>`__, Oracle,
  424. SpatiaLite
  425. Accepts two geographic fields or expressions and returns the geometric
  426. symmetric difference (union without the intersection) between the given
  427. parameters.
  428. ``Transform``
  429. =============
  430. .. class:: Transform(expression, srid, **extra)
  431. *Availability*: `PostGIS <https://postgis.net/docs/ST_Transform.html>`__,
  432. Oracle, SpatiaLite
  433. Accepts a geographic field or expression and a SRID integer code, and returns
  434. the transformed geometry to the spatial reference system specified by the
  435. ``srid`` parameter.
  436. .. note::
  437. What spatial reference system an integer SRID corresponds to may depend on
  438. the spatial database used. In other words, the SRID numbers used for Oracle
  439. are not necessarily the same as those used by PostGIS.
  440. ``Translate``
  441. =============
  442. .. class:: Translate(expression, x, y, z=0.0, **extra)
  443. *Availability*: `PostGIS <https://postgis.net/docs/ST_Translate.html>`__,
  444. SpatiaLite
  445. Accepts a single geographic field or expression and returns a geometry with
  446. its coordinates offset by the ``x``, ``y``, and optionally ``z`` numeric
  447. parameters.
  448. ``Union``
  449. =========
  450. .. class:: Union(expr1, expr2, **extra)
  451. *Availability*: MariaDB, `MySQL
  452. <https://dev.mysql.com/doc/refman/en/spatial-operator-functions.html#function_st-union>`__,
  453. `PostGIS <https://postgis.net/docs/ST_Union.html>`__, Oracle, SpatiaLite
  454. Accepts two geographic fields or expressions and returns the union of both
  455. geometries.
  456. .. _`Well-known binary (WKB)`: https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Well-known_binary
  457. .. _`Well-known text (WKT)`: https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry