IDunnThat opened a new issue, #33618:
URL: https://github.com/apache/superset/issues/33618
### Bug description
Summary
I'm using the "deck.gl GeoJSON" chart type in Apache Superset to visualize a
GeoJSON dataset that includes valid Polygon geometries. The chart fails to
render any shapes and shows "0 rows" returned, even though the dataset contains
45 rows with valid-looking GeoJSON strings in the geometry_json column.
Steps to Reproduce
Upload a cleaned GeoJSON file (converted from a shapefile) as a dataset.
Use geometry_json as the GeoJson Column in a deck.gl GeoJSON chart.
Leave "Ignore null locations" checked (default).
Click "Update Chart."
Expected Behavior
The chart should render the polygon shapes from the dataset.
Actual Behavior
Superset reports “0 rows” returned, even though valid rows are visible
in the data preview.
Unchecking “Ignore null locations” allows rendering in some cases, but
behavior is inconsistent.
Geometry column values are in the form:
{ "type": "Polygon", "coordinates": [[[-94.60..., 39.23...], ...]] }
Possible Causes
Superset may be overly strict in checking for nulls or geometry validity.
Superset might be expecting full GeoJSON Feature or FeatureCollection
structure rather than raw Polygon objects.
Environment
Apache Superset version: [insert version here]
Dataset uploaded as: GeoJSON
Chart type: deck.gl GeoJSON
Attachments
Screenshot of chart setup
Sample of geometry_json values from dataset
Request
Clarify the expected structure of the GeoJSON column
Suggest best practices for pre-processing spatial data for deck.gl charts
Fix or improve handling of basic geometry objects that are structurally
valid but not wrapped in a Feature
### Screenshots/recordings
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### 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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
