Hi,
this is found on a cluster, it is running on Pythn 2.6.6, it is a 64 bit system
the svn tree is few days old, updating it now.
creating an issue here (it seems):
from grass.pygrass.modules.shortcuts import raster as r
---
Traceback (most recent call last):
File "./python-pygra
Markus Neteler wrote:
> Markus Metz figured it out, fixed locally (see attachment).
> Submit or not?
This part:
> +/* Alias the symbols using asm */
> +extern "C" {
> +extern int open(const char *, int, ...) __asm__("open64");
> +}
shouldn't be necessary.
AFAICT, the only parts of r.terraflow
I've worked through the changelog and the 6.4.3rc4 release summary page seems
in order now,
https://trac.osgeo.org/grass/wiki/Release/6.4.3RC4-News
anything else to add?
thanks,
Hamish
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://l
On Wed, Jun 26, 2013 at 7:40 PM, Markus Neteler wrote:
> On Wed, Jun 26, 2013 at 1:13 AM, Glynn Clements
> wrote:
>>
>> Markus Neteler wrote:
>>
>>> -bash-3.2$ cd /gpfs/home/neteler/software/grass-7.0.svn/raster/r.terraflow
>>
>>> ld: 0711-317 ERROR: Undefined symbol: .std::basic_filebuf>> std::c
On Wed, Jun 26, 2013 at 1:13 AM, Glynn Clements
wrote:
>
> Markus Neteler wrote:
>
>> -bash-3.2$ cd /gpfs/home/neteler/software/grass-7.0.svn/raster/r.terraflow
>
>> ld: 0711-317 ERROR: Undefined symbol: .std::basic_filebuf> std::char_traits >::open64(char const*, std::_Ios_Openmode)
>
> This appe
Hi Benjamin,
As far as soils data, we would probably often mask with depths min or
max, use a plan to cut the profile collection to return points ("give
the carbon value at 13.5cm depth for this collection of profiles").
Alternatively, we would try to interpolate a profile collection to
harmonise
Hi all,
> This is an excellent point. While I like the mention of AQP in this context,
> I totally support a GRASS-based implementation with as few dependencies as
> possible.
+1 - I think a native GRASS implementation would make a lot of sense.
>> Yes, the thought of such "waffel voxels" is no
I forgot to mention I'm asking this in the context of an Arch G7
PKGBUILD script I maintain on AUR.
W dniu 26.06.2013 02:24, Hamish pisze:
Maciek wrote:
If I wanted to build G7 --with-opencl on a machine with a
non-Intel/nVidia/AMD GPU would everything still build and work fine?
What othe
Hi Ivan,
On Wed, Jun 26, 2013 at 3:44 PM, Ivan Marchesini
wrote:
> Many many thanks and please let me know if you think that for the
> problem of direction and inclination the use of numpy is correct
I think that use the RasterSegment class should be faster, but you
should test it, RasterSegment
> I'm using spyder: https://code.google.com/p/spyderlib/
Many tanks Pietro...
I will try...
:-)
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Hi Pietro
many thanks for your answer
> Some note on the code:
>
> 1) maybe to this kind of things you should consider to use the
> r.mapcalc instead of pygrass;
Yes you are true but later, in the code, I need to do some more
complicated stuf, like increasing or decreasing the value of a cell
b
Hi Ivan,
On Wed, Jun 26, 2013 at 2:16 PM, Ivan Marchesini
wrote:
> concerning this problem I would ask (with the risk to be OT) which is
> the best python editor to work with.
> At the moment I'm working with Geany but I'm not so happy about that.
> What a really miss is an editor that, hopefully
Hi Luca.
thank you for your answer
>
> this is not your code right?
yes it is mine
it is supposed to be part of a larger code I'm developing
>
> > grass.run_command("v.to.rast", input=ocs, type="line",
> > output="tmp_ocs", use="val", overwrite=True)
> > grass.mapcalc("$outmap = $a",
#1997: i.landsat.toar for grass-dev is missing the option for landsat8
+---
Reporter: vesnikos| Owner: grass-dev@…
Type: defect | Status: new
Priority:
Nikos wrote:
> > I really like the mini color bars presented for each color table in the
> > manual of the "r.colors" module (sourced from
> > ).
Hamish wrote:
> ( http://grass.osgeo.org/grass70/manuals/r.colors.html )
> > I'd like to propose, though, to remove the thick black borderline or,
#1997: i.landsat.toar for grass-dev is missing the option for landsat8
+---
Reporter: vesnikos| Owner: grass-dev@…
Type: defect | Status: new
Priority:
Ciao Ivan,
On Wed, Jun 26, 2013 at 5:40 AM, Ivan Marchesini
wrote:
> I have this small code:
>
> grass.run_command("v.to.rast", input=ocs, type="line", output="tmp_ocs",
> use="val", overwrite=True)
> grass.mapcalc("$outmap = $a", a = dtm, outmap="demcut", overwrite = true)
> grass.r
On 26 June 2013 06:40, Ivan Marchesini wrote:
> Dear grass-developers
Ciao Ivan
> I'm working with Python, GRASS and Pygrass and I have some small
> problems probably due to my poor knowledge of Python.
> I would ask your help.
>
> I have this small code:
>
this is not your code right?
> g
18 matches
Mail list logo
