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.

Sign up for GitHub

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

Jump to bottom

spatial conditions - allow access to tree outputs #803

Closed
4 tasks done
shawnlaffan opened this issue Nov 16, 2021 · 1 comment
Closed
4 tasks done

spatial conditions - allow access to tree outputs #803

shawnlaffan opened this issue Nov 16, 2021 · 1 comment
Assignees
@shawnlaffan
Labels
spatial conditions
Milestone
Release_4.0

Comments

@shawnlaffan
Copy link
Owner

shawnlaffan commented Nov 16, 2021 •
edited
Loading

It would be useful to access clusters (or region grower outputs) to define spatial neighbourhoods.

It is already possible to use these to control the calculation of indices. However, this will also allow the cluster groups to be used to define randomisations.

Related to #757 as it will allow us to skip the shapefile generation.

To do:
@shawnlaffan shawnlaffan added this to the Release_4.0 milestone Nov 16, 2021
@shawnlaffan shawnlaffan self-assigned this Nov 16, 2021
shawnlaffan added a commit that referenced this issue Nov 16, 2021
@shawnlaffan
Add spatial condition to use cluster groups
87d4ca6 
Any tree based output, really, so long as it
lives with the cluster analyses in a basedata.

Updates #803
shawnlaffan added a commit that referenced this issue Nov 16, 2021
@shawnlaffan
Add examples for sp_points_in_same_cluster_group
fe5e987 
Updates #803
@shawnlaffan shawnlaffan mentioned this issue Nov 16, 2021
Open
shawnlaffan added a commit that referenced this issue Nov 16, 2021
@shawnlaffan
TreeNode.pm: refactor group_nodes_below
3226bc1 
Related to #803
shawnlaffan added a commit that referenced this issue Nov 16, 2021
@shawnlaffan
TreeNode.pm: more refactoring of group_nodes_below
580d43e 
Also broadly related to #803
shawnlaffan added a commit that referenced this issue Nov 16, 2021
@shawnlaffan
TreeNode::group_nodes_below args: override target_value if num_cluste…
20668b7 
…rs passed

And some more cleanup

Updates #803
shawnlaffan added a commit that referenced this issue Nov 16, 2021
@shawnlaffan
TreeNode::group_nodes_below args: override target_value if num_cluste…
73e03eb 
…rs non-zero

No need to override if caller does not want any clusters...

Updates #803
shawnlaffan added a commit that referenced this issue Nov 16, 2021
@shawnlaffan
sp_points_in_same_cluster_group: Add test that num_clusters overrides…
d29e89a 
… target_distance

Updates #803
shawnlaffan added a commit that referenced this issue Nov 16, 2021
@shawnlaffan
sp_points_in_same_cluster_group: work from arbitrary node
0e8faec 
Updates #803
shawnlaffan added a commit that referenced this issue Nov 17, 2021
@shawnlaffan
Add spatial condition to test if a group is in a cluster
108fe85 
Probably most useful for definition queries.

Updates #803
shawnlaffan added a commit that referenced this issue Nov 17, 2021
@shawnlaffan
rename test file
1dedb18 
Updates #803
shawnlaffan added a commit that referenced this issue Nov 17, 2021
@shawnlaffan
sp_points_in_same_cluster_group: simplify element assignment logic
62dddf4 
It does not matter which is which given the return condition.

Updates #803
shawnlaffan added a commit that referenced this issue Nov 17, 2021
@shawnlaffan
rename method to be more generic
f13c1e8 
Updates #803
shawnlaffan added a commit that referenced this issue Nov 17, 2021
@shawnlaffan
Further simplify/shorten some conditions
acb6c6c 
Updates #803
shawnlaffan added a commit that referenced this issue Nov 17, 2021
@shawnlaffan
sp_points_in_same_cluster metadata: Clarify intent
9ff21db 
Updates #803
@shawnlaffan
Copy link
Owner Author

All tasks done, marking as fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shawnlaffan shawnlaffan

Labels
spatial conditions
Projects
None yet
Milestone
Release_4.0
Development

No branches or pull requests
1 participant
@shawnlaffan