You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most WPS processes here output charts in both HTML (with embedded javascript) and SVG formats. The charts are produced using altair, a python wrapper of d3.js (after wrapping by vega and vega-lite, which provide successively higher-level APIs). Note that d3 underlays most interactive data visualisations on the web.
Producing SVG output (from the server) requires using node.js to actually render the data. This is an add-on capability of altair, and enabling it adds about 420MB to the docker image (see #66), and complicates dependency version management (see #122 for an example). Deprecating server-side SVG would thus simplify the deployment.
We could instead let the data be rendered in the client web browser, as already takes place when choosing HTML format. This is potentially superior, e.g. enabling interactive tooltips (like hover the mouse over a datapoint in the pixel drill to see the date of that datapoint, illustrated in #127).
A potential downside is that some users may wish to save the chart, and prefer SVG over HTML format for that purpose. Unsure whether saving to SVG can be facilitated from the client. (It is also not difficult to extract the raw data series from the HTML chart, so saving to CSV would also be desirable if possible.)
The text was updated successfully, but these errors were encountered:
Most WPS processes here output charts in both HTML (with embedded javascript) and SVG formats. The charts are produced using
altair
, a python wrapper of d3.js (after wrapping by vega and vega-lite, which provide successively higher-level APIs). Note that d3 underlays most interactive data visualisations on the web.Producing SVG output (from the server) requires using node.js to actually render the data. This is an add-on capability of
altair
, and enabling it adds about 420MB to the docker image (see #66), and complicates dependency version management (see #122 for an example). Deprecating server-side SVG would thus simplify the deployment.We could instead let the data be rendered in the client web browser, as already takes place when choosing HTML format. This is potentially superior, e.g. enabling interactive tooltips (like hover the mouse over a datapoint in the pixel drill to see the date of that datapoint, illustrated in #127).
A potential downside is that some users may wish to save the chart, and prefer SVG over HTML format for that purpose. Unsure whether saving to SVG can be facilitated from the client. (It is also not difficult to extract the raw data series from the HTML chart, so saving to CSV would also be desirable if possible.)
The text was updated successfully, but these errors were encountered: