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
Problem
The current SIFT export image functionality basically takes a simple screenshot of what is currently shown in the image area, at the desktop resolution, and saves it to file.
Feature Request
A user request at the last Convection Working Group (9th CWG Recommendation 2), asks for the functionality of exporting what is in the image area (up to) the native full resolution of the data.
Additional Note
If possible, in addition to simple image formats, an export in GeoTiff including the projection information shall be selectable.
The text was updated successfully, but these errors were encountered:
What is expected to be visible in this final result? The overlay/boundaries? The polygons/probes from the SIFT UI? The colormap changes by the user? The easiest way to do this would be to get the extents of the current viewpoint and extract that portion of the data array out and put it in an image. The hard part is reproducing anything in the UI, especially the color stuff which are mostly GPU only as shaders.
I suppose if you drew to a fake buffer that was the appropriate size to make one specific layer be at full resolution (if there are multiple resolutions you'd have to pick one if you expected to draw more than one layer) that might work.
Problem
The current SIFT export image functionality basically takes a simple screenshot of what is currently shown in the image area, at the desktop resolution, and saves it to file.
Feature Request
A user request at the last Convection Working Group (9th CWG Recommendation 2), asks for the functionality of exporting what is in the image area (up to) the native full resolution of the data.
Additional Note
If possible, in addition to simple image formats, an export in GeoTiff including the projection information shall be selectable.
The text was updated successfully, but these errors were encountered: