Skip to content
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.

Sign up for GitHub

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

Jump to bottom

bug in natural breaks #1829

Closed
lixun910 opened this issue Mar 5, 2019 · 2 comments
Closed

bug in natural breaks #1829

lixun910 opened this issue Mar 5, 2019 · 2 comments
Assignees
@lixun910
Labels
bug fixed: verify!

Comments

@lixun910
Copy link
Member

lixun910 commented Mar 5, 2019

In the natural breaks map the largest category (for anything beyond 2 categories) seems to always be empty if using data with extreme outlieres:
screen shot 2019-03-05 at 3 31 04 pm
@lixun910 lixun910 self-assigned this Mar 5, 2019
@lixun910
Copy link
Member Author

lixun910 commented Mar 6, 2019

fix in V205

screen shot 2019-03-05 at 3 28 26 pm

lixun910 added a commit to lixun910/geoda that referenced this issue Mar 8, 2019
@lixun910
bug in natural breaks GeoDaCenter#1829
9bbbc08 
also prepare a feature for GeoDaCenter#1552
@Ashitacarl
Copy link

GeoDa 1.12.1.217 (macOS Mojave, 10.14.3). Mar. 23 build.
Data: Guerry sample

Fix verified.
Tested with 1) a positive extreme value, 2) a negative extreme value, and 3) positive + negative extreme values; 4) extreme values with missings

1829

@lixun910 lixun910 mentioned this issue May 16, 2019
Merged
lixun910 added a commit to lixun910/geoda that referenced this issue Jul 26, 2019
@lixun910
custom category update and fix
1a931b1 
fix issues in basic mapping:
1. make sure custom breaks works when no active map window
2. custom breaks editor: make sure all combobox works when changing values
3. make sure the fixed natural breaks GeoDaCenter#1829 in custom category applies to all other maps
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lixun910 lixun910

Labels
bug fixed: verify!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lixun910 @jkoschinsky @Ashitacarl