{"title":"API Formulir GeoDjango","version":"1.10","locale":"id","docname":"ref/contrib/gis/forms-api","url":"/id/1.10/ref/contrib/gis/forms-api/","canonical":"https://djangodocs.dev/id/1.10/ref/contrib/gis/forms-api/","summary":"GeoDjango provides some specialized form fields and widgets in order to visually display and edit geolocalized data on a map.","html":"

API Formulir GeoDjangoLink to this heading#

\n

GeoDjango provides some specialized form fields and widgets in order to visually\ndisplay and edit geolocalized data on a map. By default, they use\nOpenLayers-powered maps, with a base WMS layer provided by Metacarta.

\n
\n

Argumen bidangLink to this heading#

\n

In addition to the regular form field arguments,\nGeoDjango form fields take the following optional arguments.

\n
\n

sridLink to this heading#

\n
\n
\nField.sridLink to this definition#
\n

This is the SRID code that the field value should be transformed to. For\nexample, if the map widget SRID is different from the SRID more generally\nused by your application or database, the field will automatically convert\ninput values into that SRID.

\n
\n\n
\n
\n

geom_typeLink to this heading#

\n
\n
\nField.geom_typeLink to this definition#
\n

You generally shouldn't have to set or change that attribute which should\nbe setup depending on the field class. It matches the OpenGIS standard\ngeometry name.

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

Kelas-kelas bidang formulirLink to this heading#

\n
\n

GeometryFieldLink to this heading#

\n
\n
\nclass GeometryFieldLink to this definition#
\n
\n\n
\n
\n

PointFieldLink to this heading#

\n
\n
\nclass PointFieldLink to this definition#
\n
\n\n
\n
\n

LineStringFieldLink to this heading#

\n
\n
\nclass LineStringFieldLink to this definition#
\n
\n\n
\n
\n

PolygonFieldLink to this heading#

\n
\n
\nclass PolygonFieldLink to this definition#
\n
\n\n
\n
\n

MultiPointFieldLink to this heading#

\n
\n
\nclass MultiPointFieldLink to this definition#
\n
\n\n
\n
\n

MultiLineStringFieldLink to this heading#

\n
\n
\nclass MultiLineStringFieldLink to this definition#
\n
\n\n
\n
\n

MultiPolygonFieldLink to this heading#

\n
\n
\nclass MultiPolygonFieldLink to this definition#
\n
\n\n
\n
\n

GeometryCollectionFieldLink to this heading#

\n
\n
\nclass GeometryCollectionFieldLink to this definition#
\n
\n\n
\n
\n
\n

Form widgetsLink to this heading#

\n

GeoDjango form widgets allow you to display and edit geographic data on a\nvisual map.\nNote that none of the currently available widgets supports 3D geometries, hence\ngeometry fields will fallback using a simple Textarea widget for such data.

\n
\n

Widget attributesLink to this heading#

\n

GeoDjango widgets are template-based, so their attributes are mostly different\nfrom other Django widget attributes.

\n
\n
\nBaseGeometryWidget.geom_typeLink to this definition#
\n

The OpenGIS geometry type, generally set by the form field.

\n
\n\n
\n
\nBaseGeometryWidget.map_heightLink to this definition#
\n
\n\n
\n
\nBaseGeometryWidget.map_widthLink to this definition#
\n

Height and width of the widget map (default is 400x600).

\n
\n\n
\n
\nBaseGeometryWidget.map_sridLink to this definition#
\n

SRID code used by the map (default is 4326).

\n
\n\n
\n
\nBaseGeometryWidget.display_rawLink to this definition#
\n

Boolean value specifying if a textarea input showing the serialized\nrepresentation of the current geometry is visible, mainly for debugging\npurposes (default is False).

\n
\n\n
\n
\nBaseGeometryWidget.supports_3dLink to this definition#
\n

Indicates if the widget supports edition of 3D data (default is False).

\n
\n\n
\n
\nBaseGeometryWidget.template_nameLink to this definition#
\n

The template used to render the map widget.

\n
\n\n

You can pass widget attributes in the same manner that for any other Django\nwidget. For example:

\n
Code
from django.contrib.gis import forms\n\nclass MyGeoForm(forms.Form):\n    point = forms.PointField(widget=\n        forms.OSMWidget(attrs={'map_width': 800, 'map_height': 500}))\n
\n
\n
\n

Widget classesLink to this heading#

\n

BaseGeometryWidget

\n
\n
\nclass BaseGeometryWidgetLink to this definition#
\n

Ini adalah sebuah widget dasar jelas mengandung logika dibutuhkan oleh sub kelas. Anda tidak dapat secara langsung menggunakan widget ini untuk bidang geometri. Cata bahwa pembangunan dari widget GeoDjango berdasarkan pada sebuah cetakan, dicirikan oleh atribut kelas template_name.

\n
\n\n

OpenLayersWidget

\n
\n
\nclass OpenLayersWidgetLink to this definition#
\n

This is the default widget used by all GeoDjango form fields.\ntemplate_name is gis/openlayers.html.

\n

OpenLayersWidget dan OSMWidget menggunakan berkas openlayers.js ditempatkan pada situs jaringan openlayers.org. Ini bekerja untuk penggunaan dasar selama pengembangan, tetapi tidak sesuai untuk penyebaran produksi ketika openlayers.org/api/ tidak ada jaminan naik dan berjalan pada peladen lambat. Anda karena itu disarankan men subkelaskan widget ini untuk menentukan versi anda sendiri dari berkas openlayers.js di sifat js dari kelas Media sebelah dalam (lihat Assets as a static definition). Anda dapat menyimpan salinan dari openlayers.js tailored to your needs pada peladen anda sendiri atau mengacu ke salinan dari content-delivery network seperti https://cdnjs.com/. Ini akan juga mengizinkan anda melayani berkas JavaScript menggunakan protokol https jika dibutuhkan.

\n
\n\n

OSMWidget

\n
\n
\nclass OSMWidgetLink to this definition#
\n

This widget uses an OpenStreetMap base layer (Mapnik) to display geographic\nobjects on.\ntemplate_name is gis/openlayers-osm.html.

\n

The OpenLayersWidget note about JavaScript file hosting above also\napplies here. See also this FAQ answer about https access to map\ntiles.

\n
\n\n
\n
","rootId":"module-django.contrib.gis.forms","toc":[{"title":"Argumen bidang","anchor":"field-arguments","children":[{"title":"srid","anchor":"srid","children":[]},{"title":"geom_type","anchor":"geom-type","children":[]}]},{"title":"Kelas-kelas bidang formulir","anchor":"form-field-classes","children":[{"title":"GeometryField","anchor":"geometryfield","children":[]},{"title":"PointField","anchor":"pointfield","children":[]},{"title":"LineStringField","anchor":"linestringfield","children":[]},{"title":"PolygonField","anchor":"polygonfield","children":[]},{"title":"MultiPointField","anchor":"multipointfield","children":[]},{"title":"MultiLineStringField","anchor":"multilinestringfield","children":[]},{"title":"MultiPolygonField","anchor":"multipolygonfield","children":[]},{"title":"GeometryCollectionField","anchor":"geometrycollectionfield","children":[]}]},{"title":"Form widgets","anchor":"module-django.contrib.gis.widgets","children":[{"title":"Widget attributes","anchor":"widget-attributes","children":[]},{"title":"Widget classes","anchor":"widget-classes","children":[]}]}],"breadcrumbs":[{"docname":"ref/index","title":"Acuan API","url":"/id/1.10/ref/"},{"docname":"ref/contrib/index","title":"Paket contrib","url":"/id/1.10/ref/contrib/"},{"docname":"ref/contrib/gis/index","title":"GeoDjango","url":"/id/1.10/ref/contrib/gis/"}],"prev":{"docname":"ref/contrib/gis/db-api","title":"API Basisdata GeoDjango","url":"/id/1.10/ref/contrib/gis/db-api/"},"next":{"docname":"ref/contrib/gis/geoquerysets","title":"Acuan API GeoQuerySet","url":"/id/1.10/ref/contrib/gis/geoquerysets/"},"formats":{"html":"/id/1.10/ref/contrib/gis/forms-api/","markdown":"/id/1.10/ref/contrib/gis/forms-api.md","json":"/id/1.10/ref/contrib/gis/forms-api.json"},"source":"https://github.com/django/django/blob/stable/1.10.x/docs/ref/contrib/gis/forms-api.txt","official":"https://docs.djangoproject.com/id/1.10/ref/contrib/gis/forms-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","fr","ja","id","pt-br","es","el","pl"]}