search

brent- / geoda

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

Table > contents displayed incorrectly after merge #139

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
This may not be new, but very strange phenomenon. After merging
two tables and saving, the table no longer displays the values of the
merged in variables, but gives 0000000 (see screen shot). The strange
thing is that the values are there, as shown by the map and box plot,
but they are not displayed in the table. Refreshing doesn't seem to 
change this.
Merge was done between dbf from shape file and csv and displayed
fine during the work session in which it was created, and saved.

Original issue reported on code.google.com by lanse...@gmail.com on 23 Apr 2014 at 1:58

Attachments:

GoogleCodeExporter commented 8 years ago 
correct that, it is not zero, but a huge number of decimals, see attached.

Original comment by lanse...@gmail.com on 23 Apr 2014 at 2:11

Attachments:

GoogleCodeExporter commented 8 years ago 
Further investigation reveals that the number of displayed decimals is being 
initialized to "-1" for the new fields.  -1 is supposed to indicate "use 
default" but is being incorrectly left as the actual value in this case.  For 
dBase, displayed decimals value is stored as an unsigned char, which would 
explain why -1 becomes 255 after the dBase file is saved and then reloaded.  
There is no problem with the dBase save per say, but rather something is wrong 
with the merge or perhaps internal DbfTable initialization.  This will be fixed 
shortly.

Original comment by mmcc...@gmail.com on 23 Apr 2014 at 7:40

GoogleCodeExporter commented 8 years ago 
Resolved by revision 3185.  Will appear in GeoDa 1.5.33

Original comment by mmcc...@gmail.com on 23 Apr 2014 at 8:05