On 17/09/17 18:48, Johannes Radinger wrote:
Thank you Moritz!
Of course, v.reclass does the job. I just didn't see the column option...
Regarding the second (additional) part of this question: It seems that
v.to.db works well to report line lengths on a category-base. However,
sinuosity seems to be calculated based on features (i.e. feature ids).
Thus, I only get reasonable results if a cat only consists of one
feature. For connected lines that consist of more than one feature
(lines) the sinuosity index is not correct. So, I probably need to loop
over the cats, extract the lines that belong to one cat and build a
polyline before calculating sinuosity.
Please file a bug report on this so that someone might at least have a
look at it. ISTR, that this kind of limitation was present for other
indicators in v.to.db and is definitely worth thinking about.
Moritz
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
