Shapefiles do not officially support storing nulls:
http://resources.esri.com/help/9.3/ArcGISDesktop/com/Gp_ToolRef/geoprocessing_tool_reference/geoprocessing_considerations_for_shapefile_output.htm
However, on inspecting the DBF contents via `ogrinfo` with GDAL 2.1 or
2.2, both zeroes and nulls display, so some unofficial support exists.
GDAL 2.2 added support for distinguishing between "unset" fields and those
explicitly set to null:
https://trac.osgeo.org/gdal/wiki/rfc67_nullfieldvalues
Adding null support should be possible by either checking before casting
the value with OGR `IsFieldSetAndNotNull` on GDAL 2.2+ or checking with
OGR `IsFieldSet` on older GDAL versions:
https://www.gdal.org/classOGRFeature.html#a260b925400b72914eb1b8cc9a3bf4029
--
Ticket URL: <https://code.djangoproject.com/ticket/30020>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/30020#comment:1>
* owner: nobody => Kathryn Killebrew
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/30020#comment:2>
* cc: claude@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/30020#comment:3>
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/10760 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/30020#comment:4>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/30020#comment:5>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"75d627888bf42f8de6064a0bd665c98c0df66c55" 75d6278]:
{{{
#!CommitTicketReference repository=""
revision="75d627888bf42f8de6064a0bd665c98c0df66c55"
Fixed #30020 -- Fixed reading nulls with LayerMapping.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30020#comment:6>