-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Table - stack: problem with edit variable properties #1810
Labels
Comments
lixun910
added a commit
to lixun910/geoda
that referenced
this issue
Feb 23, 2019
For stack function, there are two cases: 1. working dataset is table-only, can be stacked with both table-only dataset and dataset with geometry features. 2. working dataset has geometry features, can only be stacked with dataset with geometry features. Also, the geometrical type (e.g. point/polygon/line) should be the same. All other cases should raise warning message and cancel stack operation. GeoDaCenter#1809 there is "title" in "selection tool" dialog not translated
lixun910
added a commit
to lixun910/geoda
that referenced
this issue
Mar 5, 2019
1. add item "Default displayed decimal places" in preference dialog, so users can configure the default displayed decimal places. 2. let GeoDa project file overwrite the "default displayed decimal places", so that user can always preserve different displayed decimals fro different variables(columns)
GeoDa 1.12.1.211 (macOS Mojave, 10.14.3). Mar. 18 build. Fix verified. Stacking csv tables does not produce the geometry error mentioned above. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that something is wrong with the edit variable properties functionality after two tables have been stacked. Here is what I did. 1. edit variable properties to set number of decimals for "value" to 2 in table1; 2. do same in table2; 3. stack table1 and table2.
In the new stacked table, the number of decimals is 15 or something, even though in the edit variable properties it is given as 2 (see screen shot). It is possible to adjust the number of decimals in the stacked table, but first they need to be changed to a different number, e.g., 3, and then they can be changed back to 2. But initially, there is a mismatch with what is shown in the table and listed in the edit variable properties dialog.
The text was updated successfully, but these errors were encountered: