Later steps in the workflow at the bottom of the man page do not provide
all the output I expect, presumable because this classification is
missing.
The database for my project is SQLITE. The import of the Lidar data
appears to have a complete list of columns including x, y, z, intensity,
return, n_returns, scan, edge, etc.
This is the first time I have run through this workflow so I could have
messed something up. It would be nice if someone could verify they get
similar results.
Replying to [ticket:3651 balagates]:
> The man page for v.lidar.edgedetection describes
>
> The output will be a vector map in which points has been classified as
TERRAIN, EDGE or UNKNOWN.
>
> On the "output" I see a database table named <name>_edge_interpolation
with columns
>
> Column 1: ID:INTEGER:20
> Column 2: Interp:REAL:20
This table is attached to layer 3 holding interpolation results for
internal use.
>
> I do not see a table for output=<name> nor do I see the following
>
> TERRAIN (cat = 1, layer = 1)
> EDGE (cat = 2, layer = 1)
> UNKNOWN (cat = 3, layer = 1)
>
This is correct, there is no table attached to layer 1. Category values
are stored with the geometries. You can display points classified as
terrain with `d.vect layer=1 cats=1`.
> Later steps in the workflow at the bottom of the man page do not provide
all the output I expect, presumable because this classification is
missing.
The classification is not missing, it is stored as category values without
an attribute table.