functions.txt 16 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456
  1. =============================
  2. Geographic Database Functions
  3. =============================
  4. .. module:: django.contrib.gis.db.models.functions
  5. :synopsis: Geographic Database Functions
  6. .. versionadded:: 1.9
  7. The functions documented on this page allow users to access geographic database
  8. functions to be used in annotations, aggregations, or filters in Django.
  9. Example::
  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 Output format Miscellaneous
  19. ================== ======================= ====================== =================== ================== =====================
  20. :class:`Area` :class:`BoundingCircle` :class:`Difference` :class:`ForceRHR` :class:`AsGeoJSON` :class:`MemSize`
  21. :class:`Distance` :class:`Centroid` :class:`Intersection` :class:`Reverse` :class:`AsGML` :class:`NumGeometries`
  22. :class:`Length` :class:`Envelope` :class:`SymDifference` :class:`Scale` :class:`AsKML` :class:`NumPoints`
  23. :class:`Perimeter` :class:`PointOnSurface` :class:`Union` :class:`SnapToGrid` :class:`AsSVG`
  24. :class:`Transform` :class:`GeoHash`
  25. :class:`Translate`
  26. ================== ======================= ====================== =================== ================== =====================
  27. ``Area``
  28. ========
  29. .. class:: Area(expression, **extra)
  30. *Availability*: MySQL, Oracle, PostGIS, SpatiaLite
  31. Accepts a single geographic field or expression and returns the area of the
  32. field as an :class:`~django.contrib.gis.measure.Area` measure. On MySQL, a raw
  33. float value is returned, as it's not possible to automatically determine the
  34. unit of the field.
  35. ``AsGeoJSON``
  36. =============
  37. .. class:: AsGeoJSON(expression, bbox=False, crs=False, precision=8, **extra)
  38. *Availability*: PostGIS, SpatiaLite
  39. Accepts a single geographic field or expression and returns a `GeoJSON
  40. <http://geojson.org/>`_ representation of the geometry. Note that the result is
  41. not a complete GeoJSON structure but only the ``geometry`` key content of a
  42. GeoJSON structure. See also :doc:`/ref/contrib/gis/serializers`.
  43. Example::
  44. >>> City.objects.annotate(json=AsGeoJSON('point')).get(name='Chicago').json
  45. {"type":"Point","coordinates":[-87.65018,41.85039]}
  46. ===================== =====================================================
  47. Keyword Argument Description
  48. ===================== =====================================================
  49. ``bbox`` Set this to ``True`` if you want the bounding box
  50. to be included in the returned GeoJSON.
  51. ``crs`` Set this to ``True`` if you want the coordinate
  52. reference system to be included in the returned
  53. GeoJSON.
  54. ``precision`` It may be used to specify the number of significant
  55. digits for the coordinates in the GeoJSON
  56. representation -- the default value is 8.
  57. ===================== =====================================================
  58. ``AsGML``
  59. =========
  60. .. class:: AsGML(expression, version=2, precision=8, **extra)
  61. *Availability*: Oracle, PostGIS, SpatiaLite
  62. Accepts a single geographic field or expression and returns a `Geographic Markup
  63. Language (GML)`__ representation of the geometry.
  64. Example::
  65. >>> qs = Zipcode.objects.annotate(gml=AsGML('poly'))
  66. >>> print(qs[0].gml)
  67. <gml:Polygon srsName="EPSG:4326"><gml:OuterBoundaryIs>-147.78711,70.245363 ...
  68. -147.78711,70.245363</gml:OuterBoundaryIs></gml:Polygon>
  69. ===================== =====================================================
  70. Keyword Argument Description
  71. ===================== =====================================================
  72. ``precision`` Not used on Oracle. It may be used to specify the number
  73. of significant digits for the coordinates in the GML
  74. representation -- the default value is 8.
  75. ``version`` Not used on Oracle. It may be used to specify the GML
  76. version used, and may only be values of 2 or 3. The
  77. default value is 2.
  78. ===================== =====================================================
  79. __ https://en.wikipedia.org/wiki/Geography_Markup_Language
  80. ``AsKML``
  81. =========
  82. .. class:: AsKML(expression, precision=8, **extra)
  83. *Availability*: PostGIS, SpatiaLite
  84. Accepts a single geographic field or expression and returns a `Keyhole Markup
  85. Language (KML)`__ representation of the geometry.
  86. Example::
  87. >>> qs = Zipcode.objects.annotate(kml=AsKML('poly'))
  88. >>> print(qs[0].kml)
  89. <Polygon><outerBoundaryIs><LinearRing><coordinates>-103.04135,36.217596,0 ...
  90. -103.04135,36.217596,0</coordinates></LinearRing></outerBoundaryIs></Polygon>
  91. ===================== =====================================================
  92. Keyword Argument Description
  93. ===================== =====================================================
  94. ``precision`` This keyword may be used to specify the number of
  95. significant digits for the coordinates in the KML
  96. representation -- the default value is 8.
  97. ===================== =====================================================
  98. __ https://developers.google.com/kml/documentation/
  99. ``AsSVG``
  100. =========
  101. .. class:: AsSVG(expression, relative=False, precision=8, **extra)
  102. *Availability*: PostGIS, SpatiaLite
  103. Accepts a single geographic field or expression and returns a `Scalable Vector
  104. Graphics (SVG)`__ representation of the geometry.
  105. ===================== =====================================================
  106. Keyword Argument Description
  107. ===================== =====================================================
  108. ``relative`` If set to ``True``, the path data will be implemented
  109. in terms of relative moves. Defaults to ``False``,
  110. meaning that absolute moves are used instead.
  111. ``precision`` This keyword may be used to specify the number of
  112. significant digits for the coordinates in the SVG
  113. representation -- the default value is 8.
  114. ===================== =====================================================
  115. __ http://www.w3.org/Graphics/SVG/
  116. ``BoundingCircle``
  117. ==================
  118. .. class:: BoundingCircle(expression, num_seg=48, **extra)
  119. *Availability*: `PostGIS <http://postgis.net/docs/ST_MinimumBoundingCircle.html>`__
  120. Accepts a single geographic field or expression and returns the smallest circle
  121. polygon that can fully contain the geometry.
  122. ``Centroid``
  123. ============
  124. .. class:: Centroid(expression, **extra)
  125. *Availability*: MySQL, PostGIS, Oracle, SpatiaLite
  126. Accepts a single geographic field or expression and returns the ``centroid``
  127. value of the geometry.
  128. ``Difference``
  129. ==============
  130. .. class:: Difference(expr1, expr2, **extra)
  131. *Availability*: MySQL (≥ 5.6.1), PostGIS, Oracle, SpatiaLite
  132. Accepts two geographic fields or expressions and returns the geometric
  133. difference, that is the part of geometry A that does not intersect with
  134. geometry B.
  135. .. versionchanged:: 1.10
  136. MySQL support was added.
  137. ``Distance``
  138. ============
  139. .. class:: Distance(expr1, expr2, spheroid=None, **extra)
  140. *Availability*: MySQL (≥ 5.6.1), PostGIS, Oracle, SpatiaLite
  141. Accepts two geographic fields or expressions and returns the distance between
  142. them, as a :class:`~django.contrib.gis.measure.Distance` object. On MySQL, a raw
  143. float value is returned, as it's not possible to automatically determine the
  144. unit of the field.
  145. On backends that support distance calculation on geodetic coordinates, the
  146. proper backend function is automatically chosen depending on the SRID value of
  147. the geometries (e.g. ``ST_Distance_Sphere`` on PostGIS).
  148. When distances are calculated with geodetic (angular) coordinates, as is the
  149. case with the default WGS84 (4326) SRID, you can set the ``spheroid`` keyword
  150. argument to decide if the calculation should be based on a simple sphere (less
  151. accurate, less resource-intensive) or on a spheroid (more accurate, more
  152. resource-intensive).
  153. In the following example, the distance from the city of Hobart to every other
  154. :class:`~django.contrib.gis.db.models.PointField` in the ``AustraliaCity``
  155. queryset is calculated::
  156. >>> from django.contrib.gis.db.models.functions import Distance
  157. >>> pnt = AustraliaCity.objects.get(name='Hobart').point
  158. >>> for city in AustraliaCity.objects.annotate(distance=Distance('point', pnt)):
  159. ... print(city.name, city.distance)
  160. Wollongong 990071.220408 m
  161. Shellharbour 972804.613941 m
  162. Thirroul 1002334.36351 m
  163. ...
  164. .. note::
  165. Because the ``distance`` attribute is a
  166. :class:`~django.contrib.gis.measure.Distance` object, you can easily express
  167. the value in the units of your choice. For example, ``city.distance.mi`` is
  168. the distance value in miles and ``city.distance.km`` is the distance value
  169. in kilometers. See :doc:`measure` for usage details and the list of
  170. :ref:`supported_units`.
  171. ``Envelope``
  172. ============
  173. .. class:: Envelope(expression, **extra)
  174. *Availability*: MySQL, PostGIS, SpatiaLite
  175. Accepts a single geographic field or expression and returns the geometry
  176. representing the bounding box of the geometry.
  177. ``ForceRHR``
  178. ============
  179. .. class:: ForceRHR(expression, **extra)
  180. *Availability*: `PostGIS <http://postgis.net/docs/ST_ForceRHR.html>`__
  181. Accepts a single geographic field or expression and returns a modified version
  182. of the polygon/multipolygon in which all of the vertices follow the
  183. right-hand rule.
  184. ``GeoHash``
  185. ===========
  186. .. class:: GeoHash(expression, **extra)
  187. *Availability*: PostGIS, SpatiaLite (≥ 4.0, LWGEOM)
  188. Accepts a single geographic field or expression and returns a `GeoHash`__
  189. representation of the geometry.
  190. .. versionchanged:: 1.10
  191. SpatiaLite support was added.
  192. __ https://en.wikipedia.org/wiki/Geohash
  193. ``Intersection``
  194. ================
  195. .. class:: Intersection(expr1, expr2, **extra)
  196. *Availability*: MySQL (≥ 5.6.1), PostGIS, Oracle, SpatiaLite
  197. Accepts two geographic fields or expressions and returns the geometric
  198. intersection between them.
  199. .. versionchanged:: 1.10
  200. MySQL support was added.
  201. ``Length``
  202. ==========
  203. .. class:: Length(expression, spheroid=True, **extra)
  204. *Availability*: MySQL, Oracle, PostGIS, SpatiaLite
  205. Accepts a single geographic linestring or multilinestring field or expression
  206. and returns its length as an :class:`~django.contrib.gis.measure.Distance`
  207. measure. On MySQL, a raw float value is returned, as it's not possible to
  208. automatically determine the unit of the field.
  209. On PostGIS and SpatiaLite, when the coordinates are geodetic (angular), you can
  210. specify if the calculation should be based on a simple sphere (less
  211. accurate, less resource-intensive) or on a spheroid (more accurate, more
  212. resource-intensive) with the ``spheroid`` keyword argument.
  213. ``MemSize``
  214. ===========
  215. .. class:: MemSize(expression, **extra)
  216. *Availability*: PostGIS
  217. Accepts a single geographic field or expression and returns the memory size
  218. (number of bytes) that the geometry field takes.
  219. ``NumGeometries``
  220. =================
  221. .. class:: NumGeometries(expression, **extra)
  222. *Availability*: MySQL, PostGIS, Oracle, SpatiaLite
  223. Accepts a single geographic field or expression and returns the number of
  224. geometries if the geometry field is a collection (e.g., a ``GEOMETRYCOLLECTION``
  225. or ``MULTI*`` field); otherwise returns ``None``.
  226. ``NumPoints``
  227. =============
  228. .. class:: NumPoints(expression, **extra)
  229. *Availability*: MySQL, PostGIS, Oracle, SpatiaLite
  230. Accepts a single geographic field or expression and returns the number of points
  231. in the first linestring in the geometry field; otherwise returns ``None``.
  232. ``Perimeter``
  233. =============
  234. .. class:: Perimeter(expression, **extra)
  235. *Availability*: PostGIS, Oracle, SpatiaLite (≥ 4.0)
  236. Accepts a single geographic field or expression and returns the perimeter of the
  237. geometry field as a :class:`~django.contrib.gis.measure.Distance` object. On
  238. MySQL, a raw float value is returned, as it's not possible to automatically
  239. determine the unit of the field.
  240. ``PointOnSurface``
  241. ==================
  242. .. class:: PointOnSurface(expression, **extra)
  243. *Availability*: PostGIS, Oracle, SpatiaLite
  244. Accepts a single geographic field or expression and returns a ``Point`` geometry
  245. guaranteed to lie on the surface of the field; otherwise returns ``None``.
  246. ``Reverse``
  247. ===========
  248. .. class:: Reverse(expression, **extra)
  249. *Availability*: PostGIS, Oracle, SpatiaLite (≥ 4.0)
  250. Accepts a single geographic field or expression and returns a geometry with
  251. reversed coordinates.
  252. ``Scale``
  253. =========
  254. .. class:: Scale(expression, x, y, z=0.0, **extra)
  255. *Availability*: PostGIS, SpatiaLite
  256. Accepts a single geographic field or expression and returns a geometry with
  257. scaled coordinates by multiplying them with the ``x``, ``y``, and optionally
  258. ``z`` parameters.
  259. ``SnapToGrid``
  260. ==============
  261. .. class:: SnapToGrid(expression, *args, **extra)
  262. *Availability*: PostGIS, SpatiaLite (≥ 3.1)
  263. Accepts a single geographic field or expression and returns a geometry with all
  264. points snapped to the given grid. How the geometry is snapped to the grid
  265. depends on how many numeric (either float, integer, or long) arguments are
  266. given.
  267. =================== =====================================================
  268. Number of Arguments Description
  269. =================== =====================================================
  270. 1 A single size to snap both the X and Y grids to.
  271. 2 X and Y sizes to snap the grid to.
  272. 4 X, Y sizes and the corresponding X, Y origins.
  273. =================== =====================================================
  274. ``SymDifference``
  275. =================
  276. .. class:: SymDifference(expr1, expr2, **extra)
  277. *Availability*: MySQL (≥ 5.6.1), PostGIS, Oracle, SpatiaLite
  278. Accepts two geographic fields or expressions and returns the geometric
  279. symmetric difference (union without the intersection) between the given
  280. parameters.
  281. .. versionchanged:: 1.10
  282. MySQL support was added.
  283. ``Transform``
  284. =============
  285. .. class:: Transform(expression, srid, **extra)
  286. *Availability*: PostGIS, Oracle, SpatiaLite
  287. Accepts a geographic field or expression and a SRID integer code, and returns
  288. the transformed geometry to the spatial reference system specified by the
  289. ``srid`` parameter.
  290. .. note::
  291. What spatial reference system an integer SRID corresponds to may depend on
  292. the spatial database used. In other words, the SRID numbers used for Oracle
  293. are not necessarily the same as those used by PostGIS.
  294. ``Translate``
  295. =============
  296. .. class:: Translate(expression, x, y, z=0.0, **extra)
  297. *Availability*: PostGIS, SpatiaLite
  298. Accepts a single geographic field or expression and returns a geometry with
  299. its coordinates offset by the ``x``, ``y``, and optionally ``z`` numeric
  300. parameters.
  301. ``Union``
  302. =========
  303. .. class:: Union(expr1, expr2, **extra)
  304. *Availability*: MySQL (≥ 5.6.1), PostGIS, Oracle, SpatiaLite
  305. Accepts two geographic fields or expressions and returns the union of both
  306. geometries.