Subject: Re: [gdal-dev] Error reading long numbers as integer
Ralf,
I have created a ticket for the NAS reader. Long numbers (13 digits) are
read as integer. Maybe there are more drivers who have the same trouble.
Yes, this is an issue that can be potentially found in other drivers
Hello Even,
I changed the definition to String in gfs file and use the type text in
postgresql.
I've tested with:
ogr2ogr -f PGdump /vsistdout/ nas_error_strschl.xml
ogr2ogr --config PG_LIST_ALL_TABLES YES -append -f PostgreSQL PG:dbname=nas
nas_error_strschl.xml
Am Montag 06 Dezember 2010,
Kosta, Team,
Konstantin Baumann wrote:
Hi Even,
the fallback to double/real does only help if the integer could be stored in 52
bits, since the rest of the bits are reserved for the mantissa and sign =
exact up to ~15 decimal digits.
I proposed a fix 3 years ago to change the data type to
Even,
thanks for the quick help. I have tested SVN21206 and the results fit my
needs.
Am Montag 06 Dezember 2010, 20:56:14 schrieb Even Rouault:
Ralf,
I have created a ticket for the NAS reader. Long numbers (13 digits) are
read as integer. Maybe there are more drivers who have the
Hello list,
I have created a ticket for the NAS reader. Long numbers (13 digits) are read
as integer. Maybe there are more drivers who have the same trouble.
I have tested some workarounds. Changing the attribut definition in gfs file
is successful, when destination driver is PGdump or
Ralf,
I have created a ticket for the NAS reader. Long numbers (13 digits) are
read as integer. Maybe there are more drivers who have the same trouble.
Yes, this is an issue that can be potentially found in other drivers. The
situation could improve if/when RFC 31 / OGR 64bit integer is
