You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a intended hack. The OGR CSV reader will not accept CSV files whose
header line doesn't contain a field separator, hence the write side adds this
extra column.
That said the historical limitation of the reader not to accept headers with
one field should probably be changed.
Expected behavior and actual behavior.
For CSV output with a single field an additional comma is added at the end of the first line containing the field names.
From Even via the mailing list https://lists.osgeo.org/pipermail/gdal-dev/2019-October/050884.html
Steps to reproduce the problem.
ogr2ogr -f csv my.csv bdry_counpy2.shp -select CTY_NAME
Produces
GDAL version and provenance
GDAL 3.0.1 (x64 Windows build from GIS Internals)
The text was updated successfully, but these errors were encountered: