mwort / m.swim Goto Github PK

• move or copy the width estimation from m.swim.substats
• also make sure each subbasin only has one mainstream feature

Font size mismatch found here:
https://github.com/mwort/m.swim/wiki/m.swim.subbasins

Grass vector subbasins created by m.swim.subbasins contains column catchmentID but m.swim.substats tries to create a new column based on input catchment_id by calculating averages of catchment_id (catchment raster) for each subbasin. In cases where subbasins and catchments do not fit exactly (e.g. due to cleaning) this introduces artificial catchment IDs that do not exist.

Hi @mwort,

I wonder if it wouldn't be wise to keep the cat column in the subbasins' attribute table? In the current workflow of m.swim.subbasins it is removed and subbasinID used as key column. However, GRASS seems to be quite fond of the cat column. For instance, I imported the subbasins map into R for some subsequent analyses and when writing it back to GRASS the column was silently added which screwed up my following workflow. Namely, m.swim.camaflood then uses automatically the cat instead of subbasinID column as now cat is used as key column.

How do you think about that?