ogr2ogr import null values in a csv file as an empty string into postgis

[yanfuz]

I have discovered a bug for ogr2ogr command. When using ogr2ogr to import *.csv to postgis, if the csv file has null values, see below example: Longitude, latitude, sometext, type -41.95,96.78_{1 -23.80,90.31}1 -35.87,95.23,cat,0 After the import, the null (which is _{in the csv), will result in ‘’ (single quotation marks) in the postgis table.}

A similar problem can be found at here: ​http://lists.osgeo.org/pipermail/gdal-dev/2013-January/035323.html

[yanfuz]

A test code for test ogr2ogr

[Even Rouault]

You can use the EMPTY_STRING_AS_NULL=YES open option

ogr2ogr -update PG:xxxxx in.csv -oo EMPTY_STRING_AS_NULL=YES