[Gdal-dev] OGR returns wrong floating values for shapefiles (and integer as real, in error)

Maciej Sieczka tutey at o2.pl
Wed Oct 25 05:57:46 EDT 2006

Frank Warmerdam wrote:
> Maciej Sieczka wrote:
>> Frank Warmerdam wrote:

>>> Because Shapelib does not have a 64bit integer type, it automatically
>>> treats integer fields that are potentially to large to fit in a 32bit
>>> integer as floating point.  This isn't a great approach and causes a
>>> number of problems,

>> One of which is that after v.out.ogr->v.in.ogr one gets his previous
>> integer fields imported as double floating point.

>>> but it isn't completely without reason.

>> But is that planned to be fixed?

> It is a known problem that I hope to address eventually but there is no
> timeline for a fix.

What about the other issue - could OGR output the

Z_BREACH (Real) =      101.583309999999997


Z_BREACH (Real) =      101.58331


I don't think it is just me accustomed to the latter form. It is more
human readable and shorter, cleaner. Users would like it I believe.


More information about the Gdal-dev mailing list