I think it might be best to review your architectural approach to this whole thing. You have data scattered in a few places. They need to be centralized. you already have postgres so I would highly recommend you have it centralized there.
I think your solution is very elegant for automated software, but difficult to let it use to my users. In Superset they choose maps, fields and values in a very simple way when they have to create a single map.
It looks like grafana can only create area objects from geojson static files and not from a query that returns geojson (or any geometry data). It can only work with lat/lon, geohash or lookup (but also returning lat/log)
Grafana only uses static geojson files. They can use formatting rules but those rules does not lookup any data from queries. I didn’t test but the screenshot shown here suggests that variables can be used (although the complexity will grow fast). However, without a way to use query data to setup the style, it cannot be used to represent data.
As a suggestion for grafana, I would say that we need a new layer type similar to “Markers” or “Heatmap” (or improve the existing geojson one), but with geometry where it uses lat/lon/hash/lookup.
Thanks, @yosiasz ! It does work. However, it still needs some polishing:
with geometry as a field, we do need some way to customize the popup dialog. The polygon I’m using is a little bit large and it covers the screen. The plugin github shows a “Properties” field after the “Pop up Time”, but in my case, it is missing. (It looks like I’m using the latest 1.4.4 version)
the shape border is not configurable. I tried to use the mark size but it looks like it is a fixed value.
Value mappings can set a color but the map ignores it.
This is just a partial screenshot to illustrate my panel: