Thanks Vero, Looks like I need to update my workflow. I have used ps.map before, but I like to start with d.mon, d.vect & d.rast <http://d.mon/d.vect/d.rast> so I can interactively add maps and change zoom/pan before working out the details for a static result. Or at least I did, until I ran into the problems I described. I guess I can do almost the same thing with ps.map, along with an image viewer that will refresh the display when the source file changes.
Best, Tyler -- plantarum.ca On Wed, May 15, 2019, at 9:38 PM, Veronica Andreo wrote: > Hi Tyler, > > Yes, if you use d.mon plus d.vect or d.rast commands it takes a while to load > each map, you should do it one by one... indeed, d.mon interface is not so > cool for scripting visualizations, unless you use is as in > https://grass.osgeo.org/grass76/manuals/cairodriver.html. See also here: > https://gitpitch.com/veroandreo/grass-gis-conae/master?p=slides/05_temporal&grs=gitlab#/14/3. > Still if maps are heavy to load, I'm not sure how it will work. Others will > know better. > > Another option for high quality cartography is ps.map or g.gui.psmap. You can > check the manual pages and grass wiki for examples. It is scriptable and it > provides nice features for creating maps. You spend time the first time > setting everything where you want it to be, but then just replace map names > and done (well, at least for rasters, that works nicely :)). > > You cannot control de main Map Display from the GUI with d.vect and d.rast > from the terminal. It does work to run them from the Console tab in the Layer > Manager window, though. > > HTH, > Vero > > El vie., 10 may. 2019 a las 23:48, Tyler Smith (<ty...@plantarum.ca>) > escribió: >> Hi, >> >> I'm an occasional GRASS user, currently working with GRASS 7.6 on Debian. >> Since I often go months between GRASS sessions, I like to work in text mode >> with scripts. My scripts are useful 'cheatsheets' to figure out how to >> reproduce my work. >> >> However, I've noticed that the display that's available via `d.mon >> start=wx0` doesn't work as well as the visually identical display I can get >> with `g.gui`. For example, plotting large vector maps on `wx0` I often find >> I can't get multiple maps to display at once, or if I zoom or pan the >> display stops refreshing and I'm stuck with a blank screen. These problems >> don't occur with the g.gui system. >> >> Having just tediously transferred several complex `d.vect` commands from my >> script to the gui "add a vector map", I was hoping there was a way I could >> continue to enter my scripts at the terminal prompt, and have the display >> commands directed to the g.gui map window. If I open `g.gui` and try that, I >> get the following error: >> >> ERROR: Neither MONITOR (managed by d.mon command) nor >> GRASS_RENDER_IMMEDIATE (used for direct rendering) defined >> >> Is there anyway to combine the convenience of scripting at the terminal >> with the reliability of the g.gui display windows? >> >> Thanks, >> >> Tyler >> >> -- >> plantarum.ca >> _______________________________________________ >> grass-user mailing list >> grass-user@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/grass-user
_______________________________________________ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
