Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#318 new composite area aggregation #284

Open
wants to merge 26 commits into
base: main
Choose a base branch
from

Conversation

Santonia27
Copy link
Collaborator

No description provided.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I played around the other day with this file and accidently pushed the changes but I changed everything back to the original state so I was hoping this would disappear from the PR

@@ -1014,6 +1014,7 @@ def setup_new_composite_areas(
aggregation_area_fn: Union[List[str], List[Path], str, Path] = None,
attribute_names: Union[List[str], str] = None,
label_names: Union[List[str], str] = None,
new_composite_area: bool = True
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this used?

@panosatha
Copy link
Collaborator

Some of the issues I found:

  • Most important: the splitting based on the aggregation areas is performed after the max potential value has been assigned. This means that the same value is just repeated to all the splitted objects. This took take place at the beggining before assigning this.
  • It seems that if there are more than one aggregation types, and they have the same field name the process will fail since the column name is changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants