id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,cpu,platform 354,v.out.ogr: bad DB read for format=GPX,hamish,grass-dev@…,"Hi, this is moved from gdal bug # 2638 http://trac.osgeo.org/gdal/ticket/2638 GPX format is not reading the DB table correctly, then filling in the category number as the elevation. It works ok using ogr2ogr: {{{ # Spearfish dataset: # export shapefile v.out.ogr in=archsites type=point dsn=archsites.shp # get PROJ.4 params of current location (Spearfish=UTM 13N) IN_PROJ=`g.proj -jf` ogr2ogr -f GPX -dsco GPX_USE_EXTENSIONS=YES \ -a_srs ""$IN_PROJ"" -t_srs EPSG:4326 \ output.gpx archsites.shp }}} result: {{{ 1 Signature Rock 2 No Name 3 Canyon Station ... }}} slight issue: cat number (column type integers) get padded? but using GRASS's 'v.out.ogr format=GPX' (via v.out.gpsbabel script) I get: {{{ v.out.gpsbabel -w in=archsites out=archsites.gpx where=""cat < 4"" --verbose Extracting data ... Reprojecting data ... Exporting data ... WARNING: No attribute table found -> using only category numbers as attributes Cleaning up ... Fast exit. }}} (but there is an attribute table found, otherwise SQL where= query would fail in the v.extract step) and output: {{{ 1 2 3 }}} So it's a v.out.ogr bug I guess. I tried copying the vector into the current mapset from PERMANENT, but it didn't help. Hamish ",defect,closed,major,6.4.0,Vector,svn-develbranch6,fixed,v.out.ogr GPX,,x86-32,Linux