{"title":"API Basisdata GeoDjango","version":"4.2","locale":"id","docname":"ref/contrib/gis/db-api","url":"/id/4.2/ref/contrib/gis/db-api/","canonical":"https://djangodocs.dev/id/4.2/ref/contrib/gis/db-api/","summary":"GeoDjango saat ini menyediakan backend basisdata spasial berikut: django.contrib.gis.db.backends.postgis`, django.contrib.gis.db.backends.mysql…","html":"

API Basisdata GeoDjangoLink to this heading#

\n
\n

Backend SpasialLink to this heading#

\n

GeoDjango saat ini menyediakan backend basisdata spasial berikut:

\n\n
\n

Batasan Spasial MySQLLink to this heading#

\n

Django supports spatial functions operating on real geometries available in\nmodern MySQL versions. However, the spatial functions are not as rich as other\nbackends like PostGIS.

\n
\n
\n

Dukungan RasterLink to this heading#

\n

RasterField saat ini hanya diterapkan untuk backend PostGIS. Pencarian spasial tersedia untuk bidang raster, tetapi fungsi basisdata spasial dan pengumpulan tidak diterapkan untuk bidang taster.

\n
\n
\n
\n

Membuat dan Menyimpan Model dengan Bidang GeometriLink to this heading#

\n

Here is an example of how to create a geometry object (assuming the Zipcode\nmodel):

\n
Python console
>>> from zipcode.models import Zipcode\n>>> z = Zipcode(code=77096, poly="POLYGON(( 10 10, 10 20, 20 20, 20 15, 10 10))")\n>>> z.save()\n
\n

GEOSGeometry objects may also be used to save geometric models:

\n
Python console
>>> from django.contrib.gis.geos import GEOSGeometry\n>>> poly = GEOSGeometry("POLYGON(( 10 10, 10 20, 20 20, 20 15, 10 10))")\n>>> z = Zipcode(code=77096, poly=poly)\n>>> z.save()\n
\n

Moreover, if the GEOSGeometry is in a different coordinate system (has a\ndifferent SRID value) than that of the field, then it will be implicitly\ntransformed into the SRID of the model's field, using the spatial database's\ntransform procedure:

\n
Python console
>>> poly_3084 = GEOSGeometry(\n...     "POLYGON(( 10 10, 10 20, 20 20, 20 15, 10 10))", srid=3084\n... )  # SRID 3084 is 'NAD83(HARN) / Texas Centric Lambert Conformal'\n>>> z = Zipcode(code=78212, poly=poly_3084)\n>>> z.save()\n>>> from django.db import connection\n>>> print(\n...     connection.queries[-1]["sql"]\n... )  # printing the last SQL statement executed (requires DEBUG=True)\nINSERT INTO "geoapp_zipcode" ("code", "poly") VALUES (78212, ST_Transform(ST_GeomFromWKB('\\\\001 ... ', 3084), 4326))\n
\n

Thus, geometry parameters may be passed in using the GEOSGeometry object, WKT\n(Well Known Text [1]), HEXEWKB (PostGIS specific -- a WKB geometry in\nhexadecimal [2]), and GeoJSON (see RFC 7946). Essentially, if the\ninput is not a GEOSGeometry object, the geometry field will attempt to\ncreate a GEOSGeometry instance from the input.

\n

Untuk informasi lebih membuat obyek GEOSGeometry mengacu pada GEOS tutorial 1.

\n
\n
\n

Membuat dan Menyimpan Model dengan Bidang RasterLink to this heading#

\n

Ketika membuat model raster, bidang raster akan secara jelas merubah masukan kedalam GDALRaster.

\n

Here is an example of how to create a raster object from a raster file\nvolcano.tif (assuming the Elevation model):

\n
Python console
>>> from elevation.models import Elevation\n>>> dem = Elevation(name="Volcano", rast="/path/to/raster/volcano.tif")\n>>> dem.save()\n
\n

GDALRaster objects may also be used to save\nraster models:

\n
Python console
>>> from django.contrib.gis.gdal import GDALRaster\n>>> rast = GDALRaster(\n...     {\n...         "width": 10,\n...         "height": 10,\n...         "name": "Canyon",\n...         "srid": 4326,\n...         "scale": [0.1, -0.1],\n...         "bands": [{"data": range(100)}],\n...     }\n... )\n>>> dem = Elevation(name="Canyon", rast=rast)\n>>> dem.save()\n
\n

Note that this equivalent to:

\n
Python console
>>> dem = Elevation.objects.create(\n...     name="Canyon",\n...     rast={\n...         "width": 10,\n...         "height": 10,\n...         "name": "Canyon",\n...         "srid": 4326,\n...         "scale": [0.1, -0.1],\n...         "bands": [{"data": range(100)}],\n...     },\n... )\n
\n
\n
\n

Pencarian SpasialLink to this heading#

\n

Jenis-jenis pencarian GeoDjango mungkin digunakan dengan metode pengelola lain seperti filter(), exclude(), dll. Bagaimanapun, jenis-jenis pencarian unik pada GeoDjango hanya tersedia pada bidang-bidang spasial.

\n

Penyaring pada bidang 'biasa' (misalnya CharField) mungkin dirantai dengan itu pada bidang geografis. Pencarian geografis menerima masukan geometri dan raster pada kedua sisi dan jenis masukan dapat digabung dengan bebas.

\n

Struktur umum dari pencarian geografis akan digambarkan dibawah ini. Acuan lengkap dapat ditemukan dalam spatial lookup reference1.

\n
\n

Pencarian GeometriLink to this heading#

\n

Geographic queries with geometries take the following general form (assuming\nthe Zipcode model used in the API Model GeoDjango):

\n
Text
>>> qs = Zipcode.objects.filter(<field>__<lookup_type>=<parameter>)\n>>> qs = Zipcode.objects.exclude(...)\n
\n

Sebagai contoh:

\n
Python console
>>> qs = Zipcode.objects.filter(poly__contains=pnt)\n>>> qs = Elevation.objects.filter(poly__contains=rst)\n
\n

Dalam kasus ini, poly adalah bidang geofgrafis, contains 1 adalah jenis pencarian spasial, pnt adalah parameter (yang mungkin berupa obyek GEOSGeometry atau string dari GeoJSON , WKT, atau HEXEWKB), dan rst adalah sebuah obyek GDALRaster.

\n
\n
\n

Pencarian RasterLink to this heading#

\n

Sintaksis pencarian raster mitip pada sintaksis untuk geometri. Perbedaan hanya bahwa peta indesk dapat ditentukan sebagai input tambahan. Jika tidak ada pita indeks ditentukan, pita pertama digunakan secara awalan (indeks 0). Dalam kasus itu sintaksis mirip ke sintaksis untuk pencarian geometri.

\n

Untuk menentukan pita indeks, sebuah parameter tambahan dapat ditentukan pada kedua sisi dari pencarian. Pada sisi tangan kiri, sintaksis garis bawah ganda digunakan peta indeks. Pada sisi tangan kanan, tuple dari raster dan pita indeks dapat ditentukan.

\n

This results in the following general form for lookups involving rasters\n(assuming the Elevation model used in the API Model GeoDjango):

\n
Text
>>> qs = Elevation.objects.filter(<field>__<lookup_type>=<parameter>)\n>>> qs = Elevation.objects.filter(<field>__<band_index>__<lookup_type>=<parameter>)\n>>> qs = Elevation.objects.filter(<field>__<lookup_type>=(<raster_input, <band_index>)\n
\n

Sebagai contoh:

\n
Python console
>>> qs = Elevation.objects.filter(rast__contains=geom)\n>>> qs = Elevation.objects.filter(rast__contains=rst)\n>>> qs = Elevation.objects.filter(rast__1__contains=geom)\n>>> qs = Elevation.objects.filter(rast__contains=(rst, 1))\n>>> qs = Elevation.objects.filter(rast__1__contains=(rst, 1))\n
\n

Pada sisi tangan kiri dari contoh, rast adalah bidang raster geografis dan contains 1 adalah jenis pencarian spasial. Pada sisi tangan kanan, geom adalah masukan geometri dan rst adalah sebuah obyek GDALRaster. Pinta indeks awalan pada 0 dalam permintaan dua pertama dan disetel menjadi 1 pada lainnya.

\n

Selagi semuan pencarian spasial dapat digunakan dengan obyek raster pada kedua sisi tidak semua penghubung pokok asli menerima masukan raster. Untuk kasus-kasus dimana penghubung mengharapkan masukan geometri, raster adalah secara otomatis dirubah kegeometri. itu adalah penting menjaga ini dalam pikiran ketika manafsirkan hasil pencarian.

\n

Jenis dari dukungan raster terdaftar untuk semua pencarian dalam compatibility table 1. Pencarian melibatkan raster saat ini hanya tersedia untuk backend PostGIS.

\n
\n
\n
\n

Permintaan JarakLink to this heading#

\n
\n

Kata PengantarLink to this heading#

\n

Perhitungan jarak dengan data spasial adalah rumit karena, sayangnya, Bumi tidak datar. Beberpa permintaan jarak dengan bidang dalam sistem kordinat geografis mungkin harus dinyatakan berbeda karena batasan dalam PostGIS. Silahkan lihat dokumentasi Memilih sebuah SRID section in the API Model GeoDjango untuk lebih rinci.

\n
\n
\n

Pencarian JarakLink to this heading#

\n

Ketersediaan: PostGIS, MariaDB, MySQL, Oracle, SpatiaLite, PGRaster (Asli)

\n

Pencarian jarak berikut tersedia:

\n\n\n

Pencarian jarak meliputi parameter tuple.

\n
    \n

  1. Geometri atau raster untuk perhitungan dasar dari; dan

    2. \n

  2. Sejumlah atau obyek Distance mengandung jarak.

    3. \n
\n

Jika obyek Distance digunakan, itu mungkin dinyatakan dalam satuan apapun (SQL dibangkitkan akan menggunakan unit untuk merubah ke bidang tersebut); sebaliknya parameter numerik dianggap berada dalam satuan dari bidang.

\n\n

Sebagai contoh, mari kita katakan kami memiliki sebuah model SouthTexasCity (dari GeoDjango distance tests ) pada sebuah sistem kordinat sah diproyeksikan untuk kota-kota dalam Texas selatan:

\n
Code
from django.contrib.gis.db import models\n\n\nclass SouthTexasCity(models.Model):\n    name = models.CharField(max_length=30)\n    # A projected coordinate system (only valid for South Texas!)\n    # is used, units are in meters.\n    point = models.PointField(srid=32140)\n
\n

Then distance queries may be performed as follows:

\n
Python console
>>> from django.contrib.gis.geos import GEOSGeometry\n>>> from django.contrib.gis.measure import D  # ``D`` is a shortcut for ``Distance``\n>>> from geoapp.models import SouthTexasCity\n# Distances will be calculated from this point, which does not have to be projected.\n>>> pnt = GEOSGeometry("POINT(-96.876369 29.905320)", srid=4326)\n# If numeric parameter, units of field (meters in this case) are assumed.\n>>> qs = SouthTexasCity.objects.filter(point__distance_lte=(pnt, 7000))\n# Find all Cities within 7 km, > 20 miles away, and > 100 chains away (an obscure unit)\n>>> qs = SouthTexasCity.objects.filter(point__distance_lte=(pnt, D(km=7)))\n>>> qs = SouthTexasCity.objects.filter(point__distance_gte=(pnt, D(mi=20)))\n>>> qs = SouthTexasCity.objects.filter(point__distance_gte=(pnt, D(chain=100)))\n
\n

Raster queries work the same way by replacing the geometry field point with\na raster field, or the pnt object with a raster object, or both. To specify\nthe band index of a raster input on the right hand side, a 3-tuple can be\npassed to the lookup as follows:

\n
Python console
>>> qs = SouthTexasCity.objects.filter(point__distance_gte=(rst, 2, D(km=7)))\n
\n

Dimana pita dengan indeks 2 (pita ketiga) dari raster rst akan digunakan untuk pencarian.

\n
\n
\n
\n

Tabel KesesuaianLink to this heading#

\n
\n

Pencarian SpasialLink to this heading#

\n

Tabel berikut menyediakan ringkasan dari apa pencarian spasial tersedia untuk setiap backend basisdata spasial. Pencarian PostGIS Raster (PGRaster) dibagi kedalam tiga kategori digambarkan dalam raster lookup details 1: dukungan asal n, dukungan asal bilateral B, dan dukungan perubahan geometri C.

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Jenis Pencarian

PostGIS

Oracle

MariaDB

MySQL [4]

SpatiaLite

PGRaster

bbcontains

X

X

X

X

N

bboverlaps

X

X

X

X

N

contained

X

X

X

X

N

contains

X

X

X

X

X

B

contains_properly

X

B

coveredby

X

X

X

B

covers

X

X

X

B

crosses

X

X

X

X

C

disjoint

X

X

X

X

X

B

distance_gt

X

X

X

X

X

N

distance_gte

X

X

X

X

X

N

distance_lt

X

X

X

X

X

N

distance_lte

X

X

X

X

X

N

dwithin

X

X

X

B

equals

X

X

X

X

X

C

exact

X

X

X

X

X

B

intersects

X

X

X

X

X

B

isempty

X

isvalid

X

X

X

X

overlaps

X

X

X

X

X

B

relate

X

X

X

X

C

same_as

X

X

X

X

X

B

touches

X

X

X

X

X

B

within

X

X

X

X

X

B

left

X

C

right

X

C

overlaps_left

X

B

overlaps_right

X

B

overlaps_above

X

C

overlaps_below

X

C

strictly_above

X

C

strictly_below

X

C

\n
\n
\n
\n

Fungsi basisdataLink to this heading#

\n

Tabel berikut menyediakan ringkasan dari apa fungsi-fungsi basisdata khusus-geografis tersedia pada setiap backend spasial.

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Fungsi

PostGIS

Oracle

MariaDB

MySQL

SpatiaLite

Area

X

X

X

X

X

AsGeoJSON

X

X

X

X

X

AsGML

X

X

X

AsKML

X

X

AsSVG

X

X

AsWKB

X

X

X

X

X

AsWKT

X

X

X

X

X

Azimuth

X

X (LWGEOM/RTTOPO)

BoundingCircle

X

X

Centroid

X

X

X

X

X

Difference

X

X

X

X

X

Distance

X

X

X

X

X

Envelope

X

X

X

X

X

ForcePolygonCW

X

X

FromWKB

X

X

X

X

X

FromWKT

X

X

X

X

X

GeoHash

X

X

X (LWGEOM/RTTOPO)

Intersection

X

X

X

X

X

IsEmpty

X

IsValid

X

X

X

X

Length

X

X

X

X

X

LineLocatePoint

X

X

MakeValid

X

X (LWGEOM/RTTOPO)

MemSize

X

NumGeometries

X

X

X

X

X

NumPoints

X

X

X

X

X

Perimeter

X

X

X

PointOnSurface

X

X

X

X

Reverse

X

X

X

Scale

X

X

SnapToGrid

X

X

SymDifference

X

X

X

X

X

Transform

X

X

X

Translate

X

X

Union

X

X

X

X

X

\n
\n
\n
\n

Fungsi KumpulanLink to this heading#

\n

Tabel-tabel berikut menyediakan ringkasan dari apa fungsi-fungsi pengumpulan GIS-khusus tersedia pada setiap backend spasial. harap catcat bahwa MySQL tidak mendukung apapun dari pengumpulan ini, dan dengan demikian tidak disertakan dari tabel.

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Kumpulan

PostGIS

Oracle

SpatiaLite

Collect

X

X

Extent

X

X

X

Extent3D

X

MakeLine

X

X

Union

X

X

X

\n
\n

Catatan kaki

\n\n
\n
","rootId":"geodjango-database-api","toc":[{"title":"Backend Spasial","anchor":"module-django.contrib.gis.db.backends","children":[{"title":"Batasan Spasial MySQL","anchor":"mysql-spatial-limitations","children":[]},{"title":"Dukungan Raster","anchor":"raster-support","children":[]}]},{"title":"Membuat dan Menyimpan Model dengan Bidang Geometri","anchor":"creating-and-saving-models-with-geometry-fields","children":[]},{"title":"Membuat dan Menyimpan Model dengan Bidang Raster","anchor":"creating-and-saving-models-with-raster-fields","children":[]},{"title":"Pencarian Spasial","anchor":"spatial-lookups","children":[{"title":"Pencarian Geometri","anchor":"geometry-lookups","children":[]},{"title":"Pencarian Raster","anchor":"raster-lookups","children":[]}]},{"title":"Permintaan Jarak","anchor":"distance-queries","children":[{"title":"Kata Pengantar","anchor":"introduction","children":[]},{"title":"Pencarian Jarak","anchor":"distance-lookups","children":[]}]},{"title":"Tabel Kesesuaian","anchor":"compatibility-tables","children":[{"title":"Pencarian Spasial","anchor":"spatial-lookup-compatibility","children":[]},{"title":"Fungsi basisdata","anchor":"database-functions","children":[]},{"title":"Fungsi Kumpulan","anchor":"aggregate-functions","children":[]}]}],"breadcrumbs":[{"docname":"ref/index","title":"Acuan API","url":"/id/4.2/ref/"},{"docname":"ref/contrib/index","title":"Paket contrib","url":"/id/4.2/ref/contrib/"},{"docname":"ref/contrib/gis/index","title":"GeoDjango","url":"/id/4.2/ref/contrib/gis/"}],"prev":{"docname":"ref/contrib/gis/model-api","title":"API Model GeoDjango","url":"/id/4.2/ref/contrib/gis/model-api/"},"next":{"docname":"ref/contrib/gis/forms-api","title":"API Formulir GeoDjango","url":"/id/4.2/ref/contrib/gis/forms-api/"},"formats":{"html":"/id/4.2/ref/contrib/gis/db-api/","markdown":"/id/4.2/ref/contrib/gis/db-api.md","json":"/id/4.2/ref/contrib/gis/db-api.json"},"source":"https://github.com/django/django/blob/stable/4.2.x/docs/ref/contrib/gis/db-api.txt","official":"https://docs.djangoproject.com/id/4.2/ref/contrib/gis/db-api/","inVersions":["6.1","6.0","5.2","5.1","5.0","4.2","4.1","4.0","3.2","3.1","3.0","2.2","2.1","2.0","1.11","1.10","1.9"],"inLocales":["en","zh-hans","fr","ja","id","it","pt-br","ko","es","el","pl"]}