#73: r.out.gdal tiff output does not work
-+--
Reporter: helena | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.5.0
#629: WinGRASS: spaces in pathnames
---+
Reporter: hamish| Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: normal| Milestone: 6.4.0
#73: r.out.gdal tiff output does not work
-+--
Reporter: helena | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.5.0
Glynn wrote:
> However, some of those wrappers will be unusable because of an
> inability to pass an argument from Python or return the result to
> Python.
is NumPtr of any help here? (see examples/m.distance.py)
https://trac.osgeo.org/grass/browser/grass/trunk/swig/python/NumPtr
Hamish
Thanks very much for the reply Glynn (sorry about the misspelled version of
your name). Do you think I could use G_put_map_row_random to fill a new raster
with the modified values of cells at various locations in the region and then
use patch to change the original raster? What would the other
#73: r.out.gdal tiff output does not work
--+-
Reporter: helena | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: critical | Milestone: 6.
chris carleton wrote:
> I've read somewhere (by Glenn, I think) that Python-SWIG might not
> go much farther with GRASS due to some limitations of the SWIG
> interface (I'm not expert enough to know either way). Despite that,
> I can't see another way to program what I want to do with GRASS. So,
#629: WinGRASS: spaces in pathnames
---+
Reporter: hamish| Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: normal| Milestone: 6.4.0
Hi All,
I've read somewhere (by Glenn, I think) that Python-SWIG might not go much
farther with GRASS due to some limitations of the SWIG interface (I'm not
expert enough to know either way). Despite that, I can't see another way to
program what I want to do with GRASS. So, I was hoping that s
Very Nice work. Is this an extension to ps.map, or something new? Can
you elaborate on the intermediate format-- is it completely
vector-based?
Cheers,
Dylan
On Sat, Jun 6, 2009 at 9:08 AM, E. Jorge Tizado wrote:
>
> Hi all,
>
> I present two new features in ps.output (soon in grass-addons) as yo
Jorge,
This is beautiful! Thank you…
Tom
E. Jorge Tizado wrote:
Hi all,
I present two new features in ps.output (soon in grass-addons) as you see in
attach:
- transparent colors. This is possible only using ghostscript (with standard
postscript is not implemented) via -g flag of ps.output,
#629: WinGRASS: spaces in pathnames
---+
Reporter: hamish| Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: normal| Milestone: 6.4.0
#629: WinGRASS: spaces in pathnames
---+
Reporter: hamish| Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: normal| Milestone: 6.4.0
#629: WinGRASS: spaces in pathnames
---+
Reporter: hamish| Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: normal| Milestone: 6.4.0
#629: WinGRASS: spaces in pathnames
+---
Reporter: hamish | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.
Glynn:
> The GRASS startup scripts should have already added this
> directory to PYTHONPATH.
note that for GRASS 6 this wasn't happening until a few days ago due to
a typo in init.sh.
Hamish
___
grass-dev mailing list
grass-dev@lists.osgeo.
Markus Neteler wrote:
> > Hy everybody,
> > this is me again. Bound_box work very well and i am happy. I need to
> > know something new. When I can launch my program directly in grass using
> > python test.py there is this error message:
> > File "test.py", line 4, in
> > from grass.lib imp
Francesco P. Lovergine wrote:
> I noted that both r.proj/r.proj.seg use floor() in the NN method
> (at least in 6.4). Should not be a proper rounding to the nearest integer
> more appropriate?
No.
If a projected point has grid coordinates (2.99, 3.99), the cell with
indices (2,3) contains tha
18 matches
Mail list logo
