[GRASS-user] Problems with v.outlier and v.lidar.edgedetection

[Michael Perdue]

Hi Roberto,

Thanks for the info. I'm still pretty new to macintosh and so far  
haven't had much luck (read lazy) at setting up the environment for  
building binaries myself. I did run it with the qgis option however,  
and although it didn't complain about a "bus error", it did shut down  
with the same error reported by v.lidar.edgedetection;

>> DBMI-DBF driver error:
>> Table 'Auxiliar_edge_table' doesn't exist.
>> Error in db_execute_immediate()
>>
>> ERROR: Impossible to write in the database

So, it seems that what ever is causing the error is specific to mac  
and may be common to all the v.lidar.* programs. I have a linux  
workstation in the office and I did a cvs update earlier today. The  
binaries were building when I left so in the morning I'll run  
everything through it and then move the files over to my mac and see  
if the issue also affects v.lidar.* and v.surf.bspline. I'll let you  
know what I find out. Let me know if there is anything I can do to be  
of assistance.

Cheers and thanks again!

Mike



On 10-Nov-06, at 3:43 AM, Roberto Antolin wrote:

> Hi Michael and all,
> I'm the v.outlier and v.lidar.* developer. First of all, I'm very  
> sorry for these bugs.
>
> I knew the v.outlier bug from long time ago but I didn't fix it and  
> I forgot it. I've just fixed and now I will send it to the CVS. So,  
> you will able to download the new version from there. A dirty  
> solution is:
> ~ > v.outlier input=pslc2k_sub2 output=clean outlier=outlier  
> qgis=clean_qgis
>
> This should run ok.
>
> So, if you don't need the qgis output you can remove it. The qgis  
> output vector parameter was done to allow the visualization of the  
> point's color as a function of its height within qgis. But this  
> approach needs that the topology is built and the height is  
> considered as a category. However, the standard output ("outlier="  
> and "outlier=") are done without topology and with the height as  
> the z-coord in a 3d-vector.
>
> The v.lidar.edgedetection bug is a new one. I'll try to fix it as  
> soon as possible. Another thing, I advice you about this module. It  
> doesn't run with dbf driver and db because the sql setences used  
> are not allow for them. But this is not the error in this case.
>
> I'm sorry very much,
> Roberto.
>
>
> Michael Perdue ha scritto:
>
>> Good Morning,
>>
>> I've been playing with some tools for working with lidar data sets  
>> and I've encountered two problems. First, when I try to run  
>> v.outlier the module immediately exits with "Bus error" warning.
>>
>> GRASS 6.2.0 (Mudflats):~ > v.outlier input=pslc2k_sub2  
>> output=clean outlier=outlier
>> Bus error
>>
>> Second, in my attempts to classify the point clouds  
>> v.lidar.edgedetection runs for a while and then exits with the  
>> following error;
>>
>> GRASS 6.2.0 (Mudflats):~ > v.lidar.edgedetection input=Gldcrk_sub2  
>> output=edge
>> DBMI-DBF driver error:
>> Table 'Auxiliar_edge_table' doesn't exist.
>> Error in db_execute_immediate()
>>
>> ERROR: Impossible to write in the database
>>
>> I'm running GRASS on an intel mac (OSX 10.4.8). Does anyone have  
>> any insight into either of these issues?
>>
>> Cheers,
>>
>> Mike
>> __________________________________________________
>> Do You Yahoo!?
>> Tired of spam? Yahoo! Mail has the best spam protection around  
>> http://mail.yahoo.com
>> _______________________________________________
>> grassuser mailing list
>> grassuser at grass.itc.it
>> http://grass.itc.it/mailman/listinfo/grassuser
>
>
>
> -- 
> Roberto Antolín Sánchez
> Politecnico di Milano – Polo Regionale di Como
> (Laboratorio di Geomatica V2.8)
> Via Valleggio, 11 – 22100 Como, Italy
> tel: +39 031 332 7533 || fax: +39 031 332 7519 email:  
> roberto.antolin at polimi.it
>

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com