On Thu, Apr 23, 2009 at 1:13 AM, Jack Lonsdale <lonsd...@unbc.ca> wrote: > On Thu, 2009-04-23 at 00:42 +0200, Markus Neteler wrote: >> On Thu, Apr 23, 2009 at 12:38 AM, Markus Neteler <nete...@osgeo.org> wrote: >> > On Thu, Apr 23, 2009 at 12:08 AM, Jack Lonsdale <lonsd...@unbc.ca> wrote: >> >> On Wed, 2009-04-22 at 23:26 +0200, Markus Neteler wrote: >> ... >> >> The precise error message is as above 'dbmi:Protocol error, It was >> >> impossible to open this table' ... >> > You could run v.lidar.edgedetection without troubles? > > Yes, no problems here
ok good. >> please instead: >> db.describe -c alrf_subs_edge_edge_Interpolation >> >> v.lidar.growing expects here the columns Interp,ID according to the source >> code. Otherwise fails as you have seen. >> > Seems that those exist: db.describe yields the following: > > ncols: 2 > nrows: 3268897 > Column 1: ID:INTEGER:11 > Column 2: Interp:DOUBLE PRECISION:20 ok, and check for content: db.select alrf_subs_edge_edge_Interpolation | head -n 20 ? Do you use DBF? If not too fat could you package the location with *relevant* files and make it available to me? And/or otherwise, make a test with the SQLite DBMI engine? Markus _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user