Reference GDAL API OGR Geometries
classOGRGeomType(type_input) : This class allows for the representation of an OGR geometry type in any of several ways:
654 sections in Django 4.2 Search all versions →
Reference GDAL API OGR Geometries
classOGRGeomType(type_input) : This class allows for the representation of an OGR geometry type in any of several ways:
Reference GIS QuerySet API Reference Spatial Lookups
This lookup requires a tuple parameter, (geom, pattern); the form of pattern will depend on the spatial backend:
Reference GIS QuerySet API Reference
Availability: PostGIS, Oracle, MariaDB, MySQL, SpatiaLite, PGRaster (Native) For an overview on performing distance queries, please refer to the distance queries introduction.
Reference
… Data Geographic Models Importing Spatial Data Spatial Queries Putting your data on the map GeoDjango Installation Overview Requirements Installation Troubleshooting Platform-specific instructions GeoDjango Model API Spatial Field Types Spatial Field Options Geometry Field Options GeoDjango Database API Spatial Backends Creating …
Reference GeoDjango Tutorial Spatial Queries
When doing spatial queries, GeoDjango automatically transforms geometries if they’re in a different coordinate system.
Reference PostgreSQL specific model fields Range Fields
classIntegerRangeField(**options) : Stores a range of integers. Based on an IntegerField. Represented by an int4range in the database and a django.db.backends.postgresql.psycopg_any.NumericRange in Python.
Reference PostgreSQL specific model fields Range Fields
classBigIntegerRangeField(**options) : Stores a range of large integers. Based on a BigIntegerField. Represented by an int8range in the database and a django.db.backends.postgresql.psycopg_any.NumericRange in Python.
Reference PostgreSQL specific model fields Range Fields
classDateRangeField(**options) : Stores a range of dates. Based on a DateField. Represented by a daterange in the database and a django.db.backends.postgresql.psycopg_any.DateRange in Python.
Reference django-admin and manage.py Available commands
--format FORMAT Specifies the serialization format (e.g., json or xml) for fixtures read from stdin. --exclude EXCLUDE, -e EXCLUDE Excludes loading the fixtures from the given applications and/or models (in the form of app_label or app_label.ModelName).
Reference The Forms API More granular output
If no widget is specified, then the field’s default widget will be used. BoundField.css_classes(extra_classes=None) : When you use Django’s rendering shortcuts, CSS classes are used to indicate required form fields or fields that contain errors.
Reference Widgets
In the following example, the years attribute is set for a SelectDateWidget: See the Built-in widgets for more information about which widgets are available and which arguments they accept.
Reference Widgets Customizing widget instances
In a nutshell, you will need to subclass the widget and either define a “Media” inner class or create a “media” property. These methods involve somewhat advanced Python programming and are described in detail in the Form Assets topic guide.
Reference Widgets Built-in widgetsSelector and checkbox widgets
classRadioSelect : - template_name: 'django/forms/widgets/radio.html' - option_template_name: 'django/forms/widgets/radio_option.html'
Reference
There are a number of built-in expressions (documented below) that can be used to help you write queries. Expressions can be combined, or in some cases nested, to form more complex computations.
Reference Model field reference Field types
As with other fields, you can change the maximum length using the max_length argument. The default form widget for this field is a ClearableFileInput.
Reference Model field reference Relationship fieldsManyToManyField
ForeignKey.limit_choices_to : Sets a limit to the available choices for this field when this field is rendered using a ModelForm or the admin (by default, all objects in the queryset are available to choose).
Reference Model field reference
When using [`model forms`](../../topics/forms/modelforms.md#django.forms.ModelForm), the `Field` needs to know which form field it should be represented by: `formfield(form_class=None,choices_form_class=None,**kwargs)` : Returns the default [`django.forms.Field`](../forms/fields.md#django.forms.Field) of this field for [`ModelForm`](../../topics/forms/modelforms.md#django.forms.ModelForm). By default, if both `form_class` and `choices_form_class` are `None`, it uses [`CharField`](../forms/fields.md#django.forms.CharField).
Reference QuerySet API reference QuerySet APIMethods that return new QuerySets
This means that for a large QuerySet a large ‘IN’ clause could be generated, which, depending on the database, might have performance problems of its own when it comes to parsing or executing the SQL query.
Reference Request and response objects StreamingHttpResponse objects
HttpRequest.body : The raw HTTP request body as a bytestring. This is useful for processing data in different ways than conventional HTML forms: binary images, XML payload etc. For processing conventional form data, use HttpRequest.POST.
Reference Request and response objects
This is necessary because some HTML form elements, notably <select multiple>, pass multiple values for the same key. The QueryDicts at request.POST and request.GET will be immutable when accessed in a normal request/response cycle.