Hi,
I just added the support of exporting image from wxGUI and d.mon through command line. It does not support the advanced options of d.out.file in GRASS 64 (mainly because of different rendering mechanism). Testing (especially in d.mon) is welcome.
Related to this, any ideas if wxGUI should support d.erase? And if yes, what should it do? Erase display, uncheck all layers or perhaps remove all layers from the layer tree? The third one seems to be the most useful, at least for me.
Best,
Anna
Anna wrote:
I just added the support of exporting image from wxGUI and d.mon
through command line. It does not support the advanced options of
d.out.file in GRASS 64 (mainly because of different rendering
mechanism). Testing (especially in d.mon) is welcome.
Hi Anna,
one very useful advanced option of the GRASS 6 d.out.file is the
output format geotiff, that way you can compose a scene and export
it, then reimport it as a georeferenced RGB image. Do we still have
a way of doing that?
The quadruple size is problematic for making poster sized output
since the grid, barscale, vector line overlays are still exported
as 1 px wide, which shrinks to 1/4 the size when you try and export
as high quality. The cairo and vector-based output drivers may help,
but the main solution I have for that is to encourage people to use
ps.map for when they want hi-res hardcopy outputs.
thanks,
Hamish
On Wed, Feb 12, 2014 at 6:13 PM, Hamish <hamish_b@yahoo.com> wrote:
Anna wrote:
> I just added the support of exporting image from wxGUI and d.mon
> through command line. It does not support the advanced options of
> d.out.file in GRASS 64 (mainly because of different rendering
> mechanism). Testing (especially in d.mon) is welcome.Hi Anna,
one very useful advanced option of the GRASS 6 d.out.file is the
output format geotiff, that way you can compose a scene and export
it, then reimport it as a georeferenced RGB image. Do we still have
a way of doing that?No, we don't. Or better say, accoring to the fact that d.out.file is being
reintroduced, we don't have the way yet.
But my question is: wouldn't be d.out.rast/d.to.rast even better than
d.out.file to GeoTIFF with subsequent import and r.composite.
d.out.rast/d.to.rast would do the mentioned process automatically.
Clearly, there is a place for both and I think I would use both; export as
GeoTIFF, referenced PNG, or what ever for use in other applications as well
as direct (at least from user point of view) conversion to raster map (for
3D view surface cover).
Vaclav
The quadruple size is problematic for making poster sized output
since the grid, barscale, vector line overlays are still exported
as 1 px wide, which shrinks to 1/4 the size when you try and export
as high quality. The cairo and vector-based output drivers may help,
but the main solution I have for that is to encourage people to use
ps.map for when they want hi-res hardcopy outputs.thanks,
Hamish
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev