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 - incorrect results when using point in polygon for nbr sets 1 & 2 #380

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

Spatial conditions - incorrect results when using point in polygon for nbr sets 1 & 2 #380

GoogleCodeExporter opened this issue Mar 27, 2015 · 2 comments
Labels
auto-migrated Priority-Critical Type-Defect
Milestone
Release_0.18

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1.  Run a spatial analysis where both neighbour sets 1 & 2 use a point in 
polygon sub (with or without shapefiles). 

The results only include the groups in the first neighbour set.

Original issue reported on code.google.com by shawnlaffan on 29 May 2013 at 11:13
@GoogleCodeExporter
Copy link
Author 

This issue was updated by revision r1568.

Cache always_true neighbour sets as an array.  Previously the system was only 
caching the first set and then re-using it for all subsequent sets.

Original comment by shawnlaffan on 29 May 2013 at 11:17

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

Mark as fixed.

Original comment by shawnlaffan on 30 May 2013 at 7:35

  • Changed state: Fixed
  • Added labels: ****
  • Removed labels: ****

@shawnlaffan shawnlaffan modified the milestone: Release_0.18 Feb 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Critical Type-Defect
Projects
None yet
Milestone
Release_0.18
Development

No branches or pull requests
2 participants
@shawnlaffan @GoogleCodeExporter