search

sinambelamarzuki / geoda

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

wrong eror message with rates #197

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
GeoDa 1.7.37-2 (nightly), 13 July 2015
CA tract data (Julia)

when you go to raw rate (UTZM001 over OID_) GeoDa generates an error message 
that the base field has zero values even though this isn't true (see attached).

It then prompts you if you want to save a new file with observations excluded 
that have non-zero base values. When you do this, it generates a shapefile with 
the same # of observations as before (8,038) since there were no zero values.

Original issue reported on code.google.com by jkoschin...@gmail.com on 14 Jul 2015 at 1:25

Attachments:

GoogleCodeExporter commented 8 years ago 
fixed in ci 3705

Original comment by lixun...@gmail.com on 14 Jul 2015 at 6:19

GoogleCodeExporter commented 8 years ago 
fix in >= 1.7.39

Original comment by lixun...@gmail.com on 15 Jul 2015 at 2:43

GoogleCodeExporter commented 8 years ago 
GeoDa 1.7.39 (beta), 14 July 2015

tested with same shapefile and variables again and worked fine.
The export without zero values for base variables now also works, as does the 
project file export.

One remaining issue:
When I use the Awater variable as the base, which does have a lot of zeros, I 
get the attached blank map with error message. IMO it would be more 
user-friendly to not generate any map after the error message that the base 
contains zero values -- otherwise it's like getting two error messages.

Original comment by jkoschin...@gmail.com on 15 Jul 2015 at 5:17

Attachments: