how to change the height of map

[HaveF]

I can't set the height of the map, even I set 3 lines in layout.

- [map1, map1, map1, map1, map1, map1]
- [map1, map1, map1, map1, map1, map1]
- [map1, map1, map1, map1, map1, map1]

have any suggestion?

[HaveF]

height also not works.

[rclement]

Where are you specify the height attribute?

[HaveF]

I'm just experimenting with if there are any hidden properties 😂

[rclement]

Indeed, currently the grid implementation makes use of:

• grid-template-areas + grid-area to position the grid/matrix of charts
• grid-auto-columns: minmax(100px, 1fr); to specify the min/max width of columns

So by default a row will have a height of 1fr (which seems to be defaulting to 200px). We could use grid-auto-rows to try something smart and/or configurable to specify row height but I cannot grasp a good solution for now. Happy to get some propositions if any.

Please note these CSS Grid constraints apply to all chart types, not only maps.

Nevertheless, if you want to checkout the chart in full height and full width, simply click on the chart title to display the chart page!

[rclement]

Here is a thought: what about having dashboard filters displayed at chart view level?

This would allow:

• To display a single chart full-screen (already the case)
• To display the same dashboard filters
• To link to a chart URL and still allow users to manipulate it as if it was a single-chart dashboard

However, there is a catch: if a chart does not use all dashboard filters, all filters would be displayed by default which might not be the best UX.

This issue is actually also related to another idea: defining charts independently to be able to use them within one or more dashboards (like in other BI tools), which would require to specify chart-level filters + dashboard-level filters + links from a dashboard-filter to a chart-filter.

[HaveF]

I don't understand/imagine the meaning of dashboard filters displayed at chart view level? Is it an index to list all related charts?

This issue is actually also related to another idea: defining charts independently to be able to use them within one or more dashboards (like in other BI tools), which would require to specify chart-level filters + dashboard-level filters + links from a dashboard-filter to a chart-filter.

About this idea, I believe it maybe more easy to use embedding-dashboards-and-charts? If there is something native support iframe charts, we can easily reuse these charts?

But in my case, I would like to copy and modify separate vega lite spec 😂

[rclement]

I don't understand/imagine the meaning of dashboard filters displayed at chart view level? Is it an index to list all related charts?

Imagine clicking on this link (a standalone chart view) AND having the possibility of tweaking the chart filters:
https://datasette-dashboards-demo.vercel.app/-/dashboards/job-offers-stats/offers-map?date_start=2021-01-01
That would answer your request about having a single chart in fullscreen (instead of having a dashboard with only one chart trying to be fit in fullscreen)

About this idea, I believe it maybe more easy to use embedding-dashboards-and-charts? If there is something native support iframe charts, we can easily reuse these charts?

Not really. Do you have some previous experience with a standard BI tool such as Metabase? Basically, you can:

• Define charts with their own filters ("chart-level filter")
• Then define dashboards laying-out some charts
• Define "dashboard-level filters" (not necessarily exactly the same filter names and parameters as the charts ones)
• Define the how to link a "dashboard-level filter" to a "chart-level filter" so that a chart within a dashboard is reactive to the dashboard filters

By making charts independent of dashboards, you can actually reuse charts across dashboards in a single strike. And this way charts can define their own filters and can be displayed independently.

You can read more about these types of BI operations in Metabase documentation:
https://www.metabase.com/docs/latest/dashboards/filters

But in my case, I would like to copy and modify separate vega lite spec 😂

I don't get it. What are you trying to do? What is the problem at hand?

[HaveF]

Thank you very much for your patience to explain. I understand. I think that's a good idea.

However, there is a catch: if a chart does not use all dashboard filters, all filters would be displayed by default which might not be the best UX.

As for what you said, I think we can use a hide/show button, and when the user needs to understand the dashboard filters, click the button to display.

But in my case, I would like to copy and modify separate vega lite spec 😂

I'm talking about the reuse chart thing here, I don't like reusing charts very much, if there is really a need to reuse charts, I tend to copy and modify directly. That is to say, I don't like to abstract and reuse functions, but like to copy and paste directly :D

[HaveF]

FYI, vega lite's chart level filter is easy with Parameters

[HaveF]

• To display a single chart full-screen (already the case)

Btw, does the single chart support autorefresh property defined for dashboard? it doesn't, right?

So, is it correct to say that the purpose of using standalone charts is either to embed them in other applications or for reuse?
However, if a standalone chart is intended to be embedded in another application and it does not support the originally defined refresh time, would it be necessary to adjust the refresh time again in other application?

so, maybe add property autorefresh in standalone charts is a good idea?

[rclement]

Btw, does the single chart support autorefresh property defined for dashboard? it doesn't, right?

That's right, it does not for now. Another reason for having standalone charts independent of dashboards 😉

So, is it correct to say that the purpose of using standalone charts is either to embed them in other applications or for reuse?

The initial use-case is that you can "zoom-in" on a dashboard chart to make it full-screen while doing a presentation or an exploration.

However, if a standalone chart is intended to be embedded in another application and it does not support the originally defined refresh time, would it be necessary to adjust the refresh time again in other application?

Indeed.

so, maybe add property autorefresh in standalone charts is a good idea?

Let's first define how to specify charts + dashboards + filters independently, but yes that could be an option