Bug description
If you try to select a numerical column for the Point Radius field other than the default Auto value, the chart doesn’t display anything. How to reproduce the bug 1. Create a MapBox with the sample GeoData dataset 2. Drag and drop the LON and LAT columns to the respective fields 3. Go to the Point Radius field and select the radius_miles column 4. Select miles in the Point Radius Unit field 5. Click on Update Chart
Expected results
You see your chart shows the points according to the numerical values of the radius_miles column
Actual results
The chart doesn’t display any value, just an empty map.
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.11
Node version
18 or greater
Browser
Firefox
Additional context
No response
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
This is a confirmed bug in the current Superset master: when you select a numerical column for the MapBox chart's Point Radius field, the frontend passes the column name as a string instead of a number, which breaks the rendering logic and results in an empty map. The backend does include the correct per-point radius in the geoJSON, but the frontend expects a numeric fallback and mishandles the string value, causing the issue. No recent pull requests have addressed this bug as of July 2025, and it's not documented as a known limitation or fixed in recent updates [source].
As a workaround, make sure your radius column contains only valid numeric values and, if your data source uses NUMERIC/DECIMAL types, try casting the column to BIGINT in your SQL query to avoid type conversion issues that can cause rendering problems in Superset charts [source]. If the problem persists, it will likely require a code fix to ensure the frontend always passes a valid numeric fallback for pointRadius.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: sadpandajoe
Looks like @rusackas started a PR on this here: https://github.com/apache/superset/pull/33247. Feel free to take it over and get it across the finish line if it's blocking you.