Selon Uffe Kousgaard <[email protected]>: > 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?
Yes, this is a known issue that should be fixed in a future version (GDAL 2.0 ?) when support for 64bit integers is added ( http://trac.osgeo.org/gdal/wiki/rfc31_ogr_64) . There's no software workaround on OGR side for now. > > > Regards > Uffe Kousgaard > > _______________________________________________ > gdal-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/gdal-dev > _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
