[GRASS-user] Re: v.lidar.growing dbmi: Protocol error

[Jack Lonsdale]

On Thu, 2009-04-23 at 00:42 +0200, Markus Neteler wrote:
> On Thu, Apr 23, 2009 at 12:38 AM, Markus Neteler <neteler at osgeo.org> wrote:
> > On Thu, Apr 23, 2009 at 12:08 AM, Jack Lonsdale <lonsdale at 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'
> >
> > Perfect, so I could find it: it fails on opening the
> > table associated to the input vector map. I.e., the output of
> > v.lidar.edgedetection.
> 
> Correction (what luck that is it open source and I can see what
>    happens in the code authored by someone else!):
> 
> v.lidar.edgedetection creates a table "%s_edge_Interpolation", so
> in your case
> 
> alrf_subs_edge_edge_Interpolation
> 
> > You could run v.lidar.edgedetection without troubles?
> 

Yes, no problems here

> 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.
> 
> Markus
Seems that those exist: db.describe yields the following:

ncols: 2
nrows: 3268897
Column 1: ID:INTEGER:11
Column 2: Interp:DOUBLE PRECISION:20

Thanks,

Jack