LISA: Flag and block use of residuals

[GoogleCodeExporter]

Add flag to global Moran scatterplot and LISA maps when people try to load the 
OLS residuals field, sth like: "It is not appropriate to use OLS residuals 
here. Please see documentation for details." We could discuss if this should be 
a flag or blocker (to get around a blocker version, people could just rename 
the field).

For background, see GeoDa Workbook, p. 193:
... it is not appropriate to use the permutation approach to assess 
significance [of global Moran's I for OLS residuals]. This is because OLS 
residuals are already correlated by construction and the permutation approach 
ignores this fact. For the same reason, it is also not appropriate to construct 
LISA maps for the residuals. 

Original issue reported on code.google.com by jkoschin...@gmail.com on 16 Apr 2011 at 12:42

[GoogleCodeExporter]

Not sure when we want to do this.  There is currently know easy way to know how 
a particual field was created: the user is fee to name any field whatever they 
want.

Original comment by mmcc...@gmail.com on 15 Sep 2011 at 6:22

• Added labels: Milestone-Release1.0.1

[GoogleCodeExporter]

Great, I like that solution.  Let's leave the bug open until we update the new 
Tutorial so that we don't forget.  I suppose that we could create a Tutorial or 
Documentation update tag if we really wanted to.

Original comment by mmcc...@gmail.com on 15 Sep 2011 at 7:17

[GoogleCodeExporter]

Original comment by jkoschin...@gmail.com on 18 Oct 2011 at 3:00

• Changed state: WontFix