[gdal-dev] DBF handling

[Norman Vine]

On Jan 4, 2013, at 5:37 AM, Uffe Kousgaard <uffe at routeware.dk> wrote:

> When DBF files has numeric fields with values > 2GB, processing fails and all values come out as -2147483648.
> 
> My current work-around is manually changing the fields from Numeric to Char (changing the header of the DBF), but it is really an ugly hack and spaces for padding are wrong (numeric fields are right-aligned, while char-fields are left-aligned internally).
> 
> It would be nice if at least int64 was used for integers in OGR, rather than int32. Large integers are typically used as identifiers in databases such as TomTom, OSM etc.
> 
> Has this been reported before?

This is a well known feature

see
http://www.clicketyclick.dk/databases/xbase/format/data_types.html

solution 
use something like spatialite instead of shape files 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20130104/fdb32b8a/attachment.html>