Re: [GRASS-user] Setting computational region to wx monitor from command line
Ok, thanks Anna, that is what I thought. ~ Eric. > On 14 Feb 2018, at 9:25 AM, Anna Petrášováwrote: > > On Tue, Feb 13, 2018 at 6:02 AM, Eric Patton wrote: > > Hi folks, > > > > I’m looking for a way to set the computational region to that of the > display > > window from within a script. I couldn’t find any d.* or g.* commands > that > > did this. > > > > What I am trying to do is pan around the wx monitor to different > portions of > > my vector coastline, and then from the command line run a script that > uses > > the current display area as its computational region and updates the > > attribute table of the features displayed in the region from null to > some > > other value. > > > > Any ideas on whether this is possible? > > Not currently, you would have to hack the GUI now to for example write > somewhere a file every time you change zoom and then create a script > that reads in this file and sets the region. > > Anna > > > > > ~ Eric. > > > > ___ > > 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
Re: [GRASS-user] Setting computational region to wx monitor from command line
On Tue, Feb 13, 2018 at 6:02 AM, Eric Pattonwrote: > Hi folks, > > I’m looking for a way to set the computational region to that of the display > window from within a script. I couldn’t find any d.* or g.* commands that > did this. > > What I am trying to do is pan around the wx monitor to different portions of > my vector coastline, and then from the command line run a script that uses > the current display area as its computational region and updates the > attribute table of the features displayed in the region from null to some > other value. > > Any ideas on whether this is possible? Not currently, you would have to hack the GUI now to for example write somewhere a file every time you change zoom and then create a script that reads in this file and sets the region. Anna > > ~ Eric. > > ___ > 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
Re: [GRASS-user] Setting computational region to wx monitor from command line
* Eric Patton[2018-02-13 03:02:59 -0800]: Hi folks, I’m looking for a way to set the computational region to that of the display window from within a script. I couldn’t find any d.* or g.* commands that did this. What I am trying to do is pan around the wx monitor to different portions of my vector coastline, and then from the command line run a script that uses the current display area as its computational region and updates the attribute table of the features displayed in the region from null to some other value. Any ideas on whether this is possible? Maybe d.info -g ? Nikos signature.asc Description: PGP signature ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Setting computational region to wx monitor from command line
Hi folks, I’m looking for a way to set the computational region to that of the display window from within a script. I couldn’t find any d.* or g.* commands that did this. What I am trying to do is pan around the wx monitor to different portions of my vector coastline, and then from the command line run a script that uses the current display area as its computational region and updates the attribute table of the features displayed in the region from null to some other value. Any ideas on whether this is possible? ~ Eric. ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user