Hello All!
#39734
Replies: 1 comment 1 reply
-
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
Hello fellow Superset enthusiasts!
I'm Cam, I've worked as a data scientist, data engineer and am currently head of data at the company I work for. I have many years experience with multiple BI tools and have begun using Superset for the first time in some personal projects.
I have taken note that Superset seems to be rapidly adopting an extensible platform architecture. That's very exciting. I am keen to contribute some extensions and would also like to contribute to the main code base. I am still familiarising myself with the main codebase, but can see a few small issues to cut my teeth on.
I see there has been some recent discussion on semantic models, I have my own thoughts, but am still developing them.
I have deployed Superset 6.0.0 using the 0.15.2 helm chart and a custom Dockerfile, all seems to be working well so far. My main connections are to ClickHouse and Postgres.
I am wanting to do some visualizations with deck.gl in Superset. I don't think my exact use-case is covered, so a custom deck.gl visual may be my first attempt at an extension. I have a Tegola server that serves map tiles, the map tiles are the outlines of buildings. I intend to use deck.gl to extrude the buildings in the vertical axis as a form of bar chart, across the city. The extrusion height will come from the datasets I have in Superset -> each record will have an id that maps to a building in the tileset. This interplay between a custom tileset and a dataset is what I do not think is supported in any of the base deck.gl visuals?
Anyway, that's my rambling over. Hope you are all well!
Beta Was this translation helpful? Give feedback.
All reactions