Replies: 7 comments 18 replies
-
Is there any update from your side what you are thinking about it? Please let us know, if you have any questions or if we shall explain some aspects in more detail. |
Beta Was this translation helpful? Give feedback.
-
Hi @jansule sorry for the radio silence... this is getting a fair amount of upvotes, and I share their enthusiasm. First off, I think this looks like a great plugin to add... I think a lot of people will find interesting use cases for it. If you're willing to develop it further, I think we'd be quite supportive! Particularly if it has good tests for making sure it stays stable, and hopefully is able to support recent features that the ECharts tend to have (e.g. drill to detail, etc). There was also a thread (which I can dig up if you're interested) about augmenting or replacing the MapBox plugin with something less licensed/proprietary than MapBox (which requires an access token). I see you're well underway on that effort in this plugin, so I wonder if there's a clever way to tackle both efforts in one plugin. Or maybe that's asking too much... it just crossed my mind ;) One curiosity: Is the In general, I'd love to learn more and I, for one, would love to see such a PR! |
Beta Was this translation helpful? Give feedback.
-
Hi @rusackas thanks for your reply! We are happy to hear that our idea might be interesting for you.
Thanks, that sounds great! Since we created this discussion, we continued the development of the plugin and managed to create a (hopefully) usable prototype, which is definitely still rough around the edges.
We will try to draft a PR in January, since there is still quite some work to do. To give you a brief heads up, see below an overview of the current features and some screenshots. Regarding your questions:
We are currently using the
Our plugin supports the configuration of default layers that will automatically be included on every chart that will be created. Currently, this configuration takes place in
Currently, the geometry column is a GeoJSON string in EPSG:3857, but with some effort this could be extended.
We are creating single canvas elements for each chart and place them on the map. We created a dedicated OpenLayers layer class for this. So far, rendering the charts is definitely our bottleneck. We tested with a dataset containing around 50000 rows distributed over around 50 different locations. There, initial rendering takes a few seconds (~ <10sec), afterwards everything runs smooth, though. Features:
Screenshots: Vector layer styling Scale dependent chart size |
Beta Was this translation helpful? Give feedback.
-
Sounds really exciting!
@jansule could you share your thoughts on this, in terms of functionality and use cases? |
Beta Was this translation helpful? Give feedback.
-
Is there any progress on this? Would love to use it! |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
Finally, I managed to create a PR for this: #25869 |
Beta Was this translation helpful? Give feedback.
-
Dear Superset community,
we are working on a visualization plugin for displaying arbitrary ECharts on a map. To do so, we are developing a generic approach that makes use of the existing EChart plugins in Superset and renders them on distinct geolocations on a map. Interactions on the ECharts themselves will be preserved.
See here a (very rough) example implementation of our concept:
Example Explore View
![image](https://user-images.githubusercontent.com/12186477/194880159-a789489d-54d7-4d2e-b046-b3bdd9b59f2a.png)
Example Dashboard Panel
![image](https://user-images.githubusercontent.com/12186477/194880384-824d2b66-5aee-48df-98eb-9f925b08dcda.png)
We plan on implementing following main features:
For our approach, we make use of the established OpenLayers library and base the layer configuration on the open standards of the Open Geospatial Consortium (OGC), i.e. WMS and WFS. This ensures stability and longevity.
At the moment, the plugin is being developed as a third-party plugin. However, we think this plugin exceeds our project specific use-case and has potential value for the broader community (as can be seen in #9281). Hence, we are evaluating the interest of becoming a core plugin of Superset.
Would it be of interest for you to add such a plugin as core plugin to Superset?
We are looking forward to getting feedback from you.
Beta Was this translation helpful? Give feedback.
All reactions