Closed GoogleCodeExporter closed 9 years ago
Original comment by lanse...@gmail.com
on 21 Nov 2013 at 12:35
This is the way GeoDa has always worked. Unfortunately, this is not a trivial
change in the current map design. The workaround is to create a new variable
based on the rate calculation and then show that as Natural Breaks. I would
estimate a week of coding effort to change the current design. Can this be
moved to a 1.8 feature?
Original comment by mmcc...@gmail.com
on 21 Jan 2014 at 5:10
Solution: add a one-time-warning flag.
Original comment by mmcc...@gmail.com
on 11 Feb 2014 at 5:23
Implemented warning message in GeoDa 1.5.26, SVN commit 3017
Original comment by mmcc...@gmail.com
on 12 Feb 2014 at 10:20
Original issue reported on code.google.com by
lanse...@gmail.com
on 21 Nov 2013 at 12:30