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
The problem
CSV is one of the most commonly and widely used formats for exchanging tabular data across platforms. However, it is difficult to import csv files into GRASS. Currently, db.in.ogr imports csv files but transforms all columns to text. The suggested work around is to create an accompanying *.csvt file that specifies the data types for each column. This is very cumbersome, especially for files with many columns. But OGR will automatically recognize column data types if a file open option is set -oo AUTODETECT_TYPE=YES
This makes importing csv files much easier. This can be manually entered into the gdal_oo argument in db.in.ogr but this is not mentioned in the manual. It would be even better if this is the default behavior of db.in.ogr
Proposed solution
-oo AUTODETECT_TYPE=YES should be the default for importing a csv file using db.in.ogr
a "csvt" flag should be added to enable a user to create a csvt file to override this default behavior
The problem
CSV is one of the most commonly and widely used formats for exchanging tabular data across platforms. However, it is difficult to import csv files into GRASS. Currently, db.in.ogr imports csv files but transforms all columns to text. The suggested work around is to create an accompanying *.csvt file that specifies the data types for each column. This is very cumbersome, especially for files with many columns. But OGR will automatically recognize column data types if a file open option is set
-oo AUTODETECT_TYPE=YES
This makes importing csv files much easier. This can be manually entered into the gdal_oo argument in db.in.ogr but this is not mentioned in the manual. It would be even better if this is the default behavior of db.in.ogr
Proposed solution
-oo AUTODETECT_TYPE=YES should be the default for importing a csv file using db.in.ogr
a "csvt" flag should be added to enable a user to create a csvt file to override this default behavior
See #4450 for additional information
The text was updated successfully, but these errors were encountered: