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

Map Legend Binning Incorrect #7486

MarcGJA opened this Issue Apr 28, 2018 · 0 comments


None yet
2 participants
Copy link

MarcGJA commented Apr 28, 2018

Why do the map & legend not match? Modified the screen shot to include part of the table results as well (and moved the legend out of the way too). The table is fine, but the map & legend are not matching for the second to the last binning category. A bunch of those are being reflected in the map as if they are part of the last binning category when clearly they are not. It's as if anything above a certain amount (17.5?) in this case is being tossed into the last binning category when projected onto the map. Are the map and legend even using the same binning algo?
Searched issues and the closest is this:
Used two custom maps to rule out problems with the geojson, both are doing exactly the same thing:
One (used here) was cleaned up very meticulously from original US Census tigerline data with JOSM.
And the other is this publicly available one on GitHub:
This array can be used with the above to reproduce the behavior:
COUNTY_D, Alameda, Amador, Calaveras, Colusa, Contra Costa, El Dorado, Fresno, Glenn, Humboldt, Kern, Kings, Lake, Los Angeles, Madera, Mariposa, Mendocino, Merced, Monterey, Napa, Nevada, Placer, Riverside, Sacramento, San Benito, San Bernardino, San Diego, San Joaquin, San Luis Obispo, San Mateo, Santa Barbara, Santa Clara, Santa Cruz, Shasta, Siskiyou, Solano, Sonoma, Stanislaus, Sutter, Tehama, Trinity, Tulare, Tuolumne, Ventura, Yolo, Yuba
AGE, 18.6, 19, 15.5, 22.8, 18, 18, 15.8, 23, 17.8, 21.8, 11.5, 19.1, 17.9, 20.2, 15.2, 20.7, 20.7, 17.8, 18.8, 23.9, 10.9, 18, 17.6, 15, 21, 12.1, 18.3, 17.3, 13, 17.1, 16.3, 18.1, 22, 14, 18, 20, 18.2, 17, 15, 12.6, 14.7, 17, 8, 17.4, 19
Have I missed something, is this a known Metabase issue already?

Metabase version v0.28
Firefox 52.7.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment