django-admin.py inspectdb
When django.contrib.gis
is in your INSTALLED_APPS
, the
inspectdb
management command is overridden with one from GeoDjango.
The overridden command is spatially-aware, and places geometry fields in the
auto-generated model definition, where appropriate.
django-admin.py ogrinspect
¶The ogrinpsect
management command will inspect the given OGR-compatible
DataSource
(e.g., a shapefile) and will
output a GeoDjango model with the given model name. There’s a detailed example
of using ogrinspect
in the tutorial.
--blank
<blank_field(s)>
¶Use a comma separated list of OGR field names to add the blank=True
keyword option to the field definition. Set with true
to apply
to all applicable fields.
--decimal
<decimal_field(s)>
¶Use a comma separated list of OGR float fields to generate
DecimalField
instead of the default
FloatField
. Set to true
to apply to all
OGR float fields.
--geom-name
<name>
¶Specifies the model attribute name to use for the geometry field.
Defaults to 'geom'
.
--layer
<layer>
¶The key for specifying which layer in the OGR
DataSource
source to use.
Defaults to 0 (the first layer). May be an integer or a string identifier
for the Layer
.
--mapping
¶Automatically generate a mapping dictionary for use with
LayerMapping
.
--multi-geom
¶When generating the geometry field, treat it as a geometry collection.
For example, if this setting is enabled then a
MultiPolygonField
will be placed
in the generated model rather than
PolygonField
.
--name-field
<name_field>
¶Generates a __unicode__
routine on the model that will return the
the given field name.
--no-imports
¶Suppresses the from django.contrib.gis.db import models
import statement.
--null
<null_field(s)>
¶Use a comma separated list of OGR field names to add the null=True
keyword option to the field definition. Set with true
to apply to
all applicable fields.
--srid
¶The SRID to use for the geometry field. If not set, ogrinspect
attempts
to automatically determine of the SRID of the data source.
Jul 07, 2017