-
Notifications
You must be signed in to change notification settings - Fork 14k
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
Impossible to set circle size less then 100 meters in deck.gl geojson chart #31176
Comments
Hello, @rdyatlov! I'm here to assist you with any bugs, questions, or contributions you have. Let's tackle this issue together!
|
@dosu,
|
The To achieve dynamic scaling of circle sizes in pixels, you would need to modify the Superset codebase. This involves implementing a feature that allows point sizes to be specified in pixels and dynamically scale with the map. Currently, this functionality is not available out of the box in Superset. |
@dosu, Thank you!
|
Yes, it is possible to achieve dynamic scaling of circle sizes in pixels by developing a custom plugin-chart for Superset. You can create a custom plugin that dynamically adjusts circle sizes based on the map scale. This involves implementing a custom chart component where you can control the rendering logic, such as dynamically calculating circle sizes in pixels. The |
Hello!
The issue is in impossibility to change size of point circles in a deck.gl geojson chart. Although the interface allows setting the size manually with any figure, if it is less than 100, all point circles disappear.
Thus, it's only possible to build enormous circles, that sometimes hide the necessary information below them. Moreover, there are no options in interface to switch static size (meters) to a dynamic one (pixels), depending on a map scale.
I've also tried to set the size manually by editing a geojson itself. I used the folowing options in "properties" dict to fit it, but didn't succeed.
So, there are two questions:
Thank you!
P.S.: Superset version: 3.1.2; also tried in 4.1.1 with the same result.
The text was updated successfully, but these errors were encountered: