Closed birderboone closed 4 years ago
See my comments on #18 about specific names. In addition, I would argue for "grouping" (column) and "grouping_row" or "single_grouping" as they seem mostly unambiguous. I would avoid "ind" vs. "multi" as they are instead ambigous: "ind" could refere to the actual individual that is tracked, and "multi" seems to imply several grouping levels, which is not necessarily the case, nor its intended meaning.
Similar to the
sfc
andsfg
classes in sf, our grouping class ('burst') has two main classes:Given we retain this structure what should the classes be named that is both short and understandable to their purposes. It has been suggested to use a similar naming structure as the sf geometry column and use something akin to 'burstc' and 'burstg' for each level.
This is somewhat dependent on if we change from calling it a
burst
to agroup
, but the idea remains the same.