globalQuantiles specified but viewportQuantiles is used
See original GitHub issueI’m trying to use globalQuantiles to classify polygons with sequential color ramp, but the classification looks like it’s changing when the map view changes.
It looks like global vs viewport classification was being worked on in VL repo, maybe CARTOFrames issue is related?
https://github.com/CartoDB/carto-vl/issues/1275#issuecomment-466586846 https://github.com/CartoDB/carto-vl/pull/1281#issuecomment-470048194
Code snippet that produced the error
qSFR = '''
SELECT * FROM la_join
WHERE specificusetype = 'Single Family Residence'
'''
vector.vmap(
[vector.QueryLayer(
qSFR,
color='ramp(globalQuantiles($saleprice, 7), sunset)',
strokeWidth='ramp(zoomrange([12,14]),[0,0.7])',
strokeColor=colorRamp,
interactivity={
'cols': ['formatted_saleprice','formatted_size'],
'header': ['<h2>Single Family Residence<h2>', ],
'event': 'hover'
}
),
],
context=cc,
basemap=vector.BaseMaps.voyager
)
Relevant error messages
No error messages, but a polygon’s classification should not change on zoom if Global Classification is used.
Here’s an example showing that a polygon’s classification is changing as what’s included in the viewport changes on zoom:
cartoframes version (find it with print(cartoframes.version))
‘0.9.2’
Python version (e.g., 3.5, 2.7, etc.)
3.7.1
Operation system (Windows, Linux, etc.)
Using Docker environment on a Mac: ~~https://github.com/mbforr/docker-cartoframes~~ from private end-to-end-demo repo
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (8 by maintainers)
Top GitHub Comments
OK thank you both, closing in favor of https://github.com/CartoDB/carto-vl/issues/1335
I’m going to add it as a CARTO VL issue because it should be tackled from this project. Once solved, then we’d update the version in CARTOFrames. Thank you very much for the update!