[postgis-devel] [PostGIS] #326: pgsql2shp field mappings not perfect

[PostGIS]

#326: pgsql2shp field mappings not perfect
---------------------+------------------------------------------------------
 Reporter:  pramsey  |       Owner:  mcayland     
     Type:  defect   |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 1.5.0
Component:  postgis  |     Version:  trunk        
 Keywords:           |  
---------------------+------------------------------------------------------
 From postgis-users and Peter Hopfgartner
 http://postgis.refractions.net/pipermail/postgis-users/2009-
 November/025285.html

   since we right in the middle of comparing interoperability of shape
 files between some FOSS programs and ArcGIS, we encoutered also the
 following:

   gvSIG chokes on the Bigint as produced by pgsql2shp. Looking at ArcGIs
 generated files, the max length for numbers is 19, compared to 20 for
 integers and 32 for floating points as in pgsql2shp. This seems to be
 confirmed by some Borland tools, when configured for dBase III+.

   Another limit seems to be that of text fields, that must be no longer
 then 254. This is the maximum as given by ArcGIS and by the Borland tool.

   Another point is Boolean: ArcGIS seems to not allow the creation of
 boolean fields and the Borland Tool ("Database Desktop") says that
 Booleans have a length of 1.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/326>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.