[GRASS-dev] [GRASS GIS] #2193: v.in.ogr does not handle columns named 2D_lenght and 3D_lenght

GRASS GIS trac at osgeo.org
Wed May 1 15:13:28 PDT 2019


#2193: v.in.ogr does not handle columns named 2D_lenght and 3D_lenght
-------------------------+-------------------------------------------------
  Reporter:  wenzeslaus  |      Owner:  grass-dev@…
      Type:  defect      |     Status:  new
  Priority:  minor       |  Milestone:  7.0.7
 Component:  Vector      |    Version:  svn-trunk
Resolution:              |   Keywords:  v.in.ogr, r.in.gdal, import,
                         |  database, columns
       CPU:  All         |   Platform:  All
-------------------------+-------------------------------------------------

Comment (by mmetz):

 Replying to [comment:5 martinl]:
 > Still relevant?

 Yes.

 Column names not starting with a letter are still not SQL compliant.
 Alternative column names can be provided with the `columns` option. Maybe
 the mechanism of automatically renaming columns needs to be removed
 because 1) it is not working, 2) the user does not know if and how columns
 have been renamed. Better have the user provide new column names if need
 be.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/2193#comment:6>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list