You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@timlinux I found out that this is caused by the aggregation_id field you used in Quarters layer all use the same id = 0. That's why the aggregation process put it in the same bucket, and every aggregation row use the same result.
We can ignore this as data preparation issue or treat is as bug because we should put validation in place for any id field. However I'm not sure where to put the validation logic and show the error.
Maybe in the pre analysis run hook if we have something like that?
Sample of results if I manually edited all class attribute in Quarters layers to all have different value.
Not sure why you use class attribute in the first place as an id field. class implies that it categorizes each features into a common trait, so it is definitely not unique.
Problem
Summary by district produces same numbers for all rows
The text was updated successfully, but these errors were encountered: