API Model GeoDjangoLink to this heading
This document explores the details of the GeoDjango Model API. Throughout this section, we'll be using the following geographic model of a ZIP code and of a Digital Elevation Model as our examples:
from django.contrib.gis.db import models
class Zipcode(models.Model):
code = models.CharField(max_length=5)
poly = models.PolygonField()
class Elevation(models.Model):
name = models.CharField(max_length=100)
rast = models.RasterField()
Jenis Bidang SpasialLink to this heading
Bidang-bidang spasial terdiri dari deretan dari jenis bidang geometri dan satu jenis bidang raster. Setiap jenis-jenis bidang geometri sesuai pada spesifikasi OpenGIS Simple Features [1]. Tidak ada standar untuk data raster.
GeometryFieldLink to this heading
- class GeometryFieldLink to this definition
Kelas dasar untuk bidang geometri.
PointFieldLink to this heading
- class PointFieldLink to this definition
Menyimpan Point.
LineStringFieldLink to this heading
- class LineStringFieldLink to this definition
Menyimpan LineString.
PolygonFieldLink to this heading
- class PolygonFieldLink to this definition
Menyimpan Polygon.
MultiPointFieldLink to this heading
- class MultiPointFieldLink to this definition
Menyimpan MultiPoint.
MultiLineStringFieldLink to this heading
- class MultiLineStringFieldLink to this definition
Menyimpan MultiLineString.
MultiPolygonFieldLink to this heading
- class MultiPolygonFieldLink to this definition
Menyimpan MultiPolygon.
GeometryCollectionFieldLink to this heading
- class GeometryCollectionFieldLink to this definition
Menyimpan GeometryCollection.
RasterFieldLink to this heading
- class RasterFieldLink to this definition
Menyimpan GDALRaster.
RasterField saat ini hanya diterapkan untuk backend PostGIS.
Pilihan Bidang SpasialLink to this heading
Sebagai tambahan pada Pilihan bidang biasa tersedia untuk bidang model Django, bidang-bidang spasial mempunyai pilihan tambahan berikut. Semua adalah pilihan.
sridLink to this heading
- BaseSpatialField.sridLink to this definition
Setel SRID [2] (Spatial Reference System Identity) dari bidang geometri pada nilai diberikan. Awalan pada 4326 (juga dikenal sebagai WGS84, satuan-satuan adalah dalam derajat dari garis bujur dan garis lintang).
Memilih sebuah SRIDLink to this heading
Choosing an appropriate SRID for your model is an important decision that the developer should consider carefully. The SRID is an integer specifier that corresponds to the projection system that will be used to interpret the data in the spatial database. [3] Projection systems give the context to the coordinates that specify a location. Although the details of geodesy are beyond the scope of this documentation, the general problem is that the earth is spherical and representations of the earth (e.g., paper maps, web maps) are not.
Most people are familiar with using latitude and longitude to reference a location on the earth's surface. However, latitude and longitude are angles, not distances. In other words, while the shortest path between two points on a flat surface is a straight line, the shortest path between two points on a curved surface (such as the earth) is an arc of a great circle. [4]
Thus, additional computation is required to obtain distances in planar units (e.g., kilometers and miles). Using a geographic coordinate system may introduce complications for the developer later on. For example, SpatiaLite does not have the capability to perform distance calculations between geometries using geographic coordinate systems, e.g. constructing a query to find all points within 5 miles of a county boundary stored as WGS84. [5]
Portions of the earth's surface may projected onto a two-dimensional, or Cartesian, plane. Projected coordinate systems are especially convenient for region-specific applications, e.g., if you know that your database will only cover geometries in North Kansas, then you may consider using projection system specific to that region. Moreover, projected coordinate systems are defined in Cartesian units (such as meters or feet), easing distance calculations.
Sumber daya Tambahan:
spatialreference.org: A database of spatial reference systems.
The State Plane Coordinate System: A website covering the various projection systems used in the United States. Much of the U.S. spatial data encountered will be in one of these coordinate systems rather than in a geographic coordinate system such as WGS84.
spatial_indexLink to this heading
- BaseSpatialField.spatial_indexLink to this definition
Defaults to True. Creates a spatial index for the given geometry
field.
Pilihan Bidang GeometriLink to this heading
Ada pilihan tambahan tersedia untuk bidang Geometri. Semua pilihan berikut adalah pilihan.
dimLink to this heading
- GeometryField.dimLink to this definition
This option may be used for customizing the coordinate dimension of the geometry field. By default, it is set to 2, for representing two-dimensional geometries. For spatial backends that support it, it may be set to 3 for three-dimensional support.
geographyLink to this heading
- GeometryField.geographyLink to this definition
If set to True, this option will create a database column of
type geography, rather than geometry. Please refer to the
geography type section below for more
details.
max_geom_collectionsLink to this heading
- GeometryField.max_geom_collectionsLink to this definition
This option is forwarded to the form field generated for this model
field, bounding how many geometry collections may be contained in submitted
WKB/WKT inputs before raising ValueError. Since spatial field
assignments are lazy, it is also checked when values are accessed, e.g. when
saving an instance, but not when read from a database. It defaults to 198.
Jenis GeografiLink to this heading
The geography type provides native support for spatial features represented
with geographic coordinates (e.g., WGS84 longitude/latitude). [6]
Unlike the plane used by a geometry type, the geography type uses a spherical
representation of its data. Distance and measurement operations
performed on a geography column automatically employ great circle arc
calculations and return linear units. In other words, when ST_Distance
is called on two geographies, a value in meters is returned (as opposed
to degrees if called on a geometry column in WGS84).
Karena perhitungan geografis melibatkan matematika lebih, hanya bagian dari pencarian spasial PostGIS tersedia untuk jenis geografi. Secara praktik, ini berarti bahwa sebagai tambahan pada distance lookups hanya berikut tambahan spatial lookups tersedia untuk kolom geografi:
Jika anda butuh menggunakan pencarian spasial atau pengumpulan yang tidak mendukung jenis geografi sebagai masukan, anda dapat menggunakan fungsi basisdata Cast untuk merubah kolom geografi menjadi jenis geometri dalam permintaan:
from django.contrib.gis.db.models import PointField
from django.db.models.functions import Cast
Zipcode.objects.annotate(geom=Cast("geography_field", PointField())).filter(
geom__within=poly
)
For more information, the PostGIS documentation contains a helpful section on determining when to use geography data type over geometry data type.
Catatan kaki