Re: [GRASS-dev] [GRASS GIS] #1048: wxgui: g.region: can't reset `rows=' nor `cols='

#1048: wxgui: g.region: can't reset `rows=' nor `cols=' -+-- Reporter: msieczka | Owner: grass-dev@… Type: defect | Status: new Priorit

Re: [GRASS-dev] [GRASS GIS] #957: v.voronoi has extra lines in output

#957: v.voronoi has extra lines in output -+-- Reporter: helena | Owner: grass-dev@… Type: defect | Status: closed Priority: major | Milestone: 6.4.4

Re: [GRASS-dev] [GRASS GIS] #770: Close wxGUI on GRASS CLI exit

#770: Close wxGUI on GRASS CLI exit -+-- Reporter: marisn | Owner: grass-dev@… Type: enhancement | Status: new Priority: minor| Milestone: 6.4.4

Re: [GRASS-dev] [GRASS GIS] #413: doxygen comments in get_row.c are wrong?

#413: doxygen comments in get_row.c are wrong? -+-- Reporter: karme| Owner: grass-dev@… Type: defect | Status: new Priori

Re: [GRASS-dev] wxGUI data catalog

Hi Martin, On Thu, May 1, 2014 at 7:18 PM, Martin Landa wrote: > Later could be added support for copying maps between > different locations (including automated reprojection) I would love to have this functionality somewhere on the python library, maybe we could add a "copy" method to the Loca

Re: [GRASS-dev] Python: core.create_location() available but core.create_mapset() yet missing

HI, attached a new attempt to generate a new location within a Python script (goal: batch processing). All fine except for the fact that GRASS 7 started with -c ... creates a location but then actually *starts* the session rather than returning. How to overcome this issue? thanks Markus #!/usr/

[GRASS-dev] Output to Postgis Topology very slow

Hello everybody, I'm trying to track why converting from grass 7 vector to postgis topology vector is so slow. (http://trac.osgeo.org/postgis/ticket/2695), few sec to import it into grass , few sec to build topology in grass,* several minutes to push it*into PostGIS topology. So far I found that

Re: [GRASS-dev] [GRASS GIS] #2279: wingrass71: rendering problems with raster layers automatically added by finished modules

#2279: wingrass71: rendering problems with raster layers automatically added by finished modules -+-- Reporter: hellik | Owner: grass-dev@… Type: defect | Status: n

Re: [GRASS-dev] [GRASS GIS] #2282: r.external.out: keep GRASS maps and external files in sync

#2282: r.external.out: keep GRASS maps and external files in sync -+-- Reporter: sbl | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal

Re: [GRASS-dev] [GRASS GIS] #413: doxygen comments in get_row.c are wrong?

#413: doxygen comments in get_row.c are wrong? -+-- Reporter: karme| Owner: grass-dev@… Type: defect | Status: new Priori

Re: [GRASS-dev] Python: core.create_location() available but core.create_mapset() yet missing

Markus Neteler wrote: > > This would help folks who want to batch-process data and appears to be > > the missing piece to completely generate a new location in the Python > > way. > > Is it possible, that create_location() only works *within* a GRASS session? If you're not within a GRASS sessio

Re: [GRASS-dev] Python: core.create_location() available but core.create_mapset() yet missing

On Tue, May 6, 2014 at 10:21 PM, Glynn Clements wrote: ... > IMHO, the logical approach is to start a GRASS session with a dummy > database, location and mapset, create the new database, location > and/or mapset, then switch to it with g.mapset. Agreed. This should ideally be offered as a Python

Re: [GRASS-dev] [GRASS GIS] #1467: include/gis.h hard-coding version a the SVN revision level

#1467: include/gis.h hard-coding version a the SVN revision level -+-- Reporter: strk | Owner: grass-dev@… Type: enhancement | Status: new Priority: minor

Re: [GRASS-dev] [GRASS GIS] #1049: optional histogram sidebar for legends

#1049: optional histogram sidebar for legends --+- Reporter: hamish| Owner: grass-dev@… Type: enhancement | Status: new Priority: minor |