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

Clustering - neighbours bleed across non-overlapping boundaries when more than one spatial condition is used #397

Closed
GoogleCodeExporter opened this issue Mar 27, 2015 · 12 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.  Run a cluster analysis using a non-overlapping spatial condition as the 
first condition, then sp_select_all() as the second (or some other condition).  

What is the expected output? What do you see instead?
The cluster analysis should contain a sub-tree constrained within the full 
tree.  The issue is that the sub-tree is not so contained, and instead has 
values from all across the data set.  

This appears to be something to do with how the linkages are being run.  
Matrices are being built correctly.  


Original issue reported on code.google.com by shawnlaffan on 19 Aug 2013 at 5:41

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

No branches or pull requests

2 participants