Re: [GRASS-dev] [GRASS GIS] #981: v.external db connection key missing for some GDAL drivers

[GRASS GIS]

#981: v.external db connection key missing for some GDAL drivers
-+--
 Reporter:  rblazek  |   Owner:  grass-dev@…  
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  6.4.4
Component:  Vector   | Version:  unspecified  
 Keywords:  v.external   |Platform:  Unspecified  
  Cpu:  Unspecified  |  
-+--
Changes (by neteler):

  * milestone:  6.4.0 => 6.4.4


-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #981: v.external db connection key missing for some GDAL drivers

[GRASS GIS]

#981: v.external db connection key missing for some GDAL drivers
-+--
 Reporter:  rblazek  |   Owner:  grass-dev@lists.osgeo.org
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  6.4.0
Component:  Vector   | Version:  unspecified  
 Keywords:   |Platform:  Unspecified  
  Cpu:  Unspecified  |  
-+--
 If OGR_L_GetFIDColumn does not return a column (OGR SHP driver for
 example) it is then missing in db connection info and consequently db
 operations do not work on vector created using v.external. The problem is
 here
 http://trac.osgeo.org/grass/browser/grass/trunk/lib/vector/Vlib/field.c#L8
  and there is already TODO here
 http://trac.osgeo.org/grass/browser/grass/trunk/lib/vector/Vlib/field.c#L582

 The problem can be tested either by v.db.connect -p, no key printed or
 d.what.vect for example (key field missing in query).

 I dont think it can be easily fixed. It would be possible to add OGR FID
 to attributes, but OGR SQL engine most probably does not know about FID,
 it only works on true attributes (to be verified, maybe FID is available
 with some special name).

 Radim

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev