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