3.4. Changing view parametersΒΆ

Contours must be re-calculated by the server when the contour parameters (levels, mode or smoothness) change. However, as contour rendering is done on the frontend, any changes to the contour rendering parameters (visibility, opacity, thickness, colour, line style) do not require any server interaction.

_images/6dfb28dd5e9c0366ae0602661f647ba3215c34ba58f05403b67af1e4fc897cca.svg

Similarly for raster images: As all the rendering is done on the frontend, any changes to the raster rendering configuration (colour map, range, scaling type) do not require any interaction between frontend and backend:

_images/ecfddc8ed77a156c41c28f49b4adb3357ad4a6f9c32d05dc087093ca66a49745.svg

Vector overlay rendering requires image data for both the vector angle (normally calculated from polarization angle PA) and length/intensity (normally calculated from polarized intensity PI). The image data is first downsampled on the backend using block downsampling with an even block width, and then masked with a threshold value. Adjusting the block width or threshold value will require the data to be recalculated and streamed by the backend. The backend streams data tile-by-tile.

_images/a989420e39e81bb0f07c43c6194f93b36bd33280bb549b41b59873da12dcdf19.svg