gvSIG bugs #2694: Numeric types management of PostGIS tables - Application: gvSIG desktop - gvSIG

gvSIG bugs #2694

Numeric types management of PostGIS tables

Added by Antonio Falciano almost 10 years ago. Updated about 9 years ago.

Status:

Closed

% Done:

Priority:

Normal

Spent time:

Assignee:

José Badía

Category:

Database

Target version:

2.2.0-2302 (rev. org.gvsig.desktop-2.0.89)

Severity:

Major

Add-on version:

gvSIG version:

2.1.0

Add-on build:

gvSIG build:

2237

Add-on resolve version:

Operative System:

Add-on resolve build:

Keywords:

postgis, width, length, precision

Proyecto:

Has patch:

Hito:

Add-on name:

Unknown

Description

PostGIS Integer values are read (and converted) in gvSIG as Double ones with length 11 and precision 10.
Example: add the spatial_ref_sys PostGIS table and convert it to DBF: the auth_srid field is converted from integer to double (11,10).
Instead, PostGIS Numeric values seem to be converted as Double with length 18 and precision 1.

For instance, this is how GDAL/OGR converts fields without an explicit width:

* Integer fields without an explicit width are treated as width 11.
* Real (floating point) fields without an explicit width are treated as width 24 with 15 decimal places of precision.
* String fields without an assigned width are treated as 80 characters.

(Source: http://www.gdal.org/drv_shapefile.html)

Related issues