Opened 12 years ago
Closed 6 years ago
#1892 closed defect (worksforme)
v.outlier loses cats and tables
Reported by: | cmbarton | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.0.7 |
Component: | Vector | Version: | unspecified |
Keywords: | v.outlier | Cc: | |
CPU: | Unspecified | Platform: | Unspecified |
Description
I've been trying out the GRASS lidar tools and it seems like v.outlier does not copy the cats and attribute table when it creates its output maps
Change History (10)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Component: | Default → Vector |
---|---|
Keywords: | v.outlier added |
comment:3 by , 12 years ago
At least for initial processing you do need the table to differentiate between last return and other return points, or do other filtering. Maybe by the time you get to the v.outlier stage, it is less important. But keeping the cats is good. I need to double check on the cats, though, since it is possible that they are there but that the query function does not show them.
Michael
comment:4 by , 12 years ago
I'll mention this here, thought it is technically a different issue.
v.outlier is missing from the lidar menu.
Michael
comment:6 by , 8 years ago
Milestone: | 7.0.0 → 7.0.5 |
---|
comment:8 by , 8 years ago
Milestone: | 7.0.5 → 7.0.6 |
---|
comment:9 by , 7 years ago
Milestone: | 7.0.6 → 7.0.7 |
---|
comment:10 by , 6 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
No activity for a long time. Closing. Feel free to reopen if needed.
I don't know if that behaviour is a bug or by design, but with the number of data points usually in a lidar dataset you don't really want a DB table, or perhaps even topology built!
it should probably hold onto cats though.
Hamish