I am using the v.clean tool with the option "prune". According to the manual, threshold values have to be in map units. I am using this with a latlon map with vertices as close as 0.0001 degrees. However, v.clean only removes vertices at threshold values of about 50 or up. This seems to suggest that the tools assumes threshold values are in meters?
I am using the v.clean tool with the option “prune”. According to the manual, threshold values have to be in map units. I am using this with a latlon map with vertices as close as 0.0001 degrees. However, v.clean only removes vertices at threshold values of about 50 or up. This seems to suggest that the tools assumes threshold values are in meters?
The prune tool of v.clean never really worked. Please use v.generalize instead.
OK, will do. Still the question remains whether this is a bug, an error in the manual page (i.e., threshold values are not in mapping units, but in meters like for the rmarea) , or I am doing something wrong (note that it seems to work fine if one assumed threshold values have to be in meters). If a bug or error in the manual page, I can create a ticket.
I am using the v.clean tool with the option “prune”. According to the manual, threshold values have to be in map units. I am using this with a latlon map with vertices as close as 0.0001 degrees. However, v.clean only removes vertices at threshold values of about 50 or up. This seems to suggest that the tools assumes threshold values are in meters?
The prune tool of v.clean never really worked. Please use v.generalize instead.
I am using the v.clean tool with the option “prune”. According to the manual, threshold values have to be in map units. I am using this with a latlon map with vertices as close as 0.0001 degrees. However, v.clean only removes vertices at threshold values of about 50 or up. This seems to suggest that the tools assumes threshold values are in meters?
The prune tool of v.clean never really worked. Please use v.generalize instead.
OK, will do. Still the question remains whether this is a bug, an error in the manual page (i.e., threshold values are not in mapping units, but in meters like for the rmarea) , or I am doing something wrong (note that it seems to work fine if one assumed threshold values have to be in meters). If a bug or error in the manual page, I can create a ticket.
It’s a bug in the code [0], the algorithm is not working properly. There is v.generalize, therefore I recommend to remove the prune tool from v.clean.
I am using the v.clean tool with the option “prune”. According to the manual, threshold values have to be in map units. I am using this with a latlon map with vertices as close as 0.0001 degrees. However, v.clean only removes vertices at threshold values of about 50 or up. This seems to suggest that the tools assumes threshold values are in meters?
The prune tool of v.clean never really worked. Please use v.generalize instead.
OK, will do. Still the question remains whether this is a bug, an error in the manual page (i.e., threshold values are not in mapping units, but in meters like for the rmarea) , or I am doing something wrong (note that it seems to work fine if one assumed threshold values have to be in meters). If a bug or error in the manual page, I can create a ticket.
It’s a bug in the code [0], the algorithm is not working properly. There is v.generalize, therefore I recommend to remove the prune tool from v.clean.
It’s a bug in the code [0], the algorithm is not working properly. There is
v.generalize, therefore I recommend to remove the prune tool from v.clean.
Maybe keep (for consistency) and replace the functionality with an
G_fatal_error() pointing the user to v.generalize?
For the GUI, and the manual page, I think it would be better if the functionality is removed completely. Presenting an option that is really not available would, i.m.h.o. be confusing.
For command line use, it is good to get a error with pointer to v.generalize if users attempt to use ‘prune’ in v.clean. Especially important to warn people properly if using this in a script.
For legacy reasons, it is furthermore probably good to mention in the Note section of the help file that this function has been removed and that the user can use v.generalize for this.