[postgis-devel] [PostGIS] #467: shp2pgsql: command line option to cope with broken strings in dbf files

[PostGIS]

#467: shp2pgsql: command line option to cope with broken strings in dbf files
----------------------+-----------------------------------------------------
  Reporter:  agnat    |       Owner:  strk         
      Type:  patch    |      Status:  assigned     
  Priority:  medium   |   Milestone:  PostGIS 1.5.2
 Component:  postgis  |     Version:  1.5.X        
Resolution:           |    Keywords:  shp2pgsql    
----------------------+-----------------------------------------------------
Comment (by agnat):

 You could store anything <=255 bytes in a string field.
 [http://www.clicketyclick.dk/databases/xbase/format/data_types.html#DATA_TYPES
 Other sources] state that ASCII is the right encoding. However, if you say
 it's common practice to use utf-8 in dbf/shapefiles (like the geofabrik
 guys do) i'm happy. I'm a geo-noob, you're a committer.

 I used the [http://www.gadm.org/data/gadm_v1_shp.zip world file] (475MB)
 in my tests, but i guess it affects every file that uses non ascii
 characters (and that has not been fixed yet). I ''think'' the strings in
 the germany file are broken, too. But I have to verify that.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/467#comment:6>
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.