kibichii / geoda

Automatically exported from code.google.com/p/geoda
GNU General Public License v3.0
0 stars 0 forks source link

rate map - new map type #58

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
There is a discrepancy in the logic for new map type when the
first map is a rate map. For example, creating a box map for
the raw rate of malaria over population gives the proper map.
Right clicking on the current map and changing the map type
to say natural breaks makes a map for malaria only, i.e., for
the numerator of the rate, but not for the rate.
This is counterintuitive at best (I didn't realize it was not a map
for the rates until I thought is looked really weird and double
checked). Somehow, the interface does not remember that the
map in question is a rate map.
Using GeoDa 1.4.6.
L.

Original issue reported on code.google.com by lanse...@gmail.com on 21 Nov 2013 at 12:30

GoogleCodeExporter commented 9 years ago

Original comment by lanse...@gmail.com on 21 Nov 2013 at 12:35

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
Solution: add a one-time-warning flag.

Original comment by mmcc...@gmail.com on 11 Feb 2014 at 5:23

GoogleCodeExporter commented 9 years ago
Implemented warning message in GeoDa 1.5.26, SVN commit 3017

Original comment by mmcc...@gmail.com on 12 Feb 2014 at 10:20