spatial conditions - allow access to other outputs in the basedata

[GoogleCodeExporter]

A useful addition to the spatial conditions, particularly definition queries, 
is to allow the user to check results in other outputs from the same basedata.  

In this way one could, for example, restrict the analyses to those groups which 
score highly for one of the indices (e.g. endemism).

Supporting code was added in r710.  Documentation needs to be updated.

Original issue reported on code.google.com by shawnlaffan on 19 Apr 2011 at 11:46

[GoogleCodeExporter]

Updated by r736

Original comment by shawnlaffan on 10 Jul 2011 at 11:44

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

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by shawnlaffan on 18 Sep 2011 at 8:37

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

[GoogleCodeExporter]

Basedata ref isn't being passed in call from Biodiverse::Index.pm

[INDEX] Case of 36: Neighbour set 1
Predicting index offsets based on 4 corner cases and their first order nbrs
(index resolution: 0.09 0.09)
0.0277777777777778   2%
Can't call method "get_spatial_output_ref" on an undefined value at (eval 
5973201) line 1.
 at C:\biodiverse_googlecode\lib/Biodiverse/Index.pm line 570

Original comment by shawnlaffan on 27 Sep 2011 at 6:13

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

[GoogleCodeExporter]

Push back to next release.  It can be an undocumented feature for 0.16.

Original comment by shawnlaffan on 9 Nov 2011 at 9:27

• Added labels: Milestone-Release0.17
• Removed labels: Milestone-Release0.16

[GoogleCodeExporter]

This issue was closed by revision r993.

Original comment by shawnlaffan on 4 Jul 2012 at 10:42

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

[GoogleCodeExporter]

This issue was updated by revision r996.

Set type to be always_same to take advantage of the optimisation.  

Original comment by shawnlaffan on 4 Jul 2012 at 11:20

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