Hi Yann,
On Thu, Jun 20, 2013 at 4:37 AM, Yann Chemin yche...@gmail.com wrote:
I am running into an issue with i.atcorr in pyGRASS:
Thank you to discover this! should be fix in: r56813
All the best
Pietro
___
grass-dev mailing list
grass-dev
are assign a new name to the raster, but the
map already exist...
Therefore as Luca said, should be sufficient to add:
{{{
visited.overwrite = True
visited.name = 'visitati'
}}}
let us know.
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http
0.3+ (memory/CPU usage in status bar)
Optional modules:
IPython 0.13 (enhanced Python interpreter)
pylint (code analysis)
pep8 (style analysis)
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
should test it, RasterSegment allows you to open a map in 'rw' read
and write mode, that is specially useful for the map visited.
have fun!
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
xml.etree.ElementTree import fromstring
Do you receive the same error?
TypeError: __new__() takes at most 2 arguments (3 given)
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
', mtype='CELL')
This should work, however I had some Segmentation Fault using
RasterNumpy and integer in the past and I'm not sure it is working at
the moment...
Let me know! :-)
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http
and installing python locally in your home...
Best regards
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
and running GRASS. Is this possible?
yes, it is possible:
http://grasswiki.osgeo.org/wiki/Working_with_GRASS_without_starting_it_explicitly
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
the hierarchical segmentation is working quite well...
ml.classify group=rgb seg_thresholds=0.02,0.05,0.1
seg_opts=method=region_growing,similarity=euclidean,minsize=2
seg_name=seg__%.2f -s
If you think that could be useful, perhaps I could split into a
separate module.
Pietro
for other purposes than
classification.
And don't hesitate to publish your classification module as early as
possible in addons. This way we can all test and contribute.
ok, I can do it... which name should I use for the hierarchical module?
Pietro
: 9.99s
}}}
Best regards
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Hi Moritz,
On Thu, Aug 1, 2013 at 12:40 PM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
Pietro,
On 31/07/13 10:01, Pietro wrote:
I'm working to develop a module that use several machine learning
technique to classify the segments results...
the part concerning the hierarchical
of the HDF file
ychk Name for the training values in the HDF
Kchk Name for the training values in the HDF
ERROR: Sorry Kchk=K_chk is not a valid option
}}}
Do you understand what I'm doing wrong? why is ychk working?
I'm using grass r57429
Best regards.
Pietro
On Wed, Aug 7, 2013 at 2:58 PM, Anna Petrášová kratocha...@gmail.com wrote:
On Wed, Aug 7, 2013 at 1:39 PM, Pietro peter.z...@gmail.com wrote:
I'm trying to write a grass7 add-ons, but I'm fighting with one
parameter that wont work... and I'm not able to understand where the
problem
the same fragment of code sparse in the
grass code...
Should I put this function in grass.script.core?
Do you have any better function name?
Do you have any particular advice?
Best regards
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
if this has already been discussed, but I was not able to find
any reference in the mailing-list's archive.
Best regards
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On Mon, Aug 12, 2013 at 4:54 PM, Benjamin Ducke bendu...@fastmail.fm wrote:
On 08/12/2013 05:39 PM, Pietro wrote:
http://trac.osgeo.org/grass/browser/grass/trunk/general/g.region/main.c#L203
Why should we not use TYPE_DOUBLE for these parameters (n,s,e,w,)? Is
it to not loose significant
the
function in python.script.core.mlist_grouped as suggested by Anna.
Best regards
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
is still there...
I'm running 64bit Linux.
Pietro
[0] http://grass.osgeo.org/sampledata/north_carolina/nc_spm_08_grass7.tar.gz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
-optimize
something... :-)
Sorry for the noise.
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Hi Yann,
thank you for testing!
On Mon, Sep 16, 2013 at 11:19 AM, Yann Chemin yche...@gmail.com wrote:
output = raster.RasterSegment(rainfall[t-1])
output.open('w','FCELL')
for row in range(nrows):
for col in range(ncols):
print - , col, row
output[col, row] = 0.0
ignorant on Windows and maybe virtualenv is useless in this
case... or maybe integrate virtualenv on the windows installer is too
complex, I have no clue!
Pietro
[0] https://pypi.python.org/pypi/virtualenv
___
grass-dev mailing list
grass-dev
and max are functions in python, so from my point of view
it is much better minimum and maximum to avoid possible conflicts.
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
your code
should work writing:
{{{
from grass.pygrass.modules.shortcuts import raster as r
r.report(map='r_ndvi', units=['c', 'p', 'h'])
}}}
Please, let me know...
Have a nice day.
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http
containing
one of the following values: ['mi', 'me', 'k', 'a', 'h', 'c', 'p']
What do you think?
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On Thu, Oct 31, 2013 at 3:03 PM, Luca Delucchi lucadel...@gmail.com wrote:
[0] https://github.com/zarch/i.segment.hierarchical
Could I suggest you to use the grass-addons repository ;-)
Ok, moved (i.segment.hierarchical) to grass-addons (r58137).
Pietro
rewrite the categories to
link the new layer with the geometry features? Or if not define the
geometry features inherit the categories from the previous layer?
Best regards
Pietro
[0] http://grass.osgeo.org/programming7/structdblinks.html
___
grass-dev
=Combabula_Nearmap.red zones=seg005_64_zones
percentile=90. output=red.csv -e --o
The module termanate with:
D1/1: G_find_raster(): name=MASK mapset=pietro
Current region rows: 28545, cols: 27645
ERROR: G_realloc: unable to allocate 68000 bytes of memory at
r.univar_main.c:327
Any idea?
Maybe is a stupid
data set.
All the best.
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
, with_statement, print_function, unicode_literals)
so we can start slowly to move from python2 = python3
what do you think?
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
that it does not
affect their ArcGIS installation, with it's own ESRI - specific version of
python.
I completely agree.
Personally I see a complete isolate python installation as a plus in that case.
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
the knowledge to set
and configure a setup.py file for such complex project like GRASS.
Pietro
[0] https://pypi.python.org/pypi/setuptools
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
that setuptools could be the solution for our
problems, at least not in the short term. And I agree with you,
creating .bat files, it seems the best/easier solution so far.
Pietro
ps: Small note: python 3.3 insert the native support for virtual
environment in the standard library
(http://docs.python.org/3
also help users to move they bash
scripts to python.
All the best.
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On Fri, Jan 31, 2014 at 3:53 PM, Vaclav Petras wenzesl...@gmail.com wrote:
I've used doctest to cover some of the pygrass' functions and modules,
but I don't like too much, at the moment to test the pygrass' doctest
you have to be inside the NorthCarolina/user1 location/mapset, that is
not
= 2.6?
Best regards.
Pietro
[0] http://www.python.org/getit/releases/2.6.9/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On Mon, Feb 10, 2014 at 10:43 AM, Martin Landa landa.mar...@gmail.com wrote:
2014-02-10 11:39 GMT+01:00 Pietro peter.z...@gmail.com:
So are you agree to change the requirements for grass70 from Python =
2.4 to Python = 2.7 or Python = 2.6?
personally I would keep support for Python 2.6
or not (and it is!) :-D.
Between python 2.6 and 2.7, as far as I know, there are not big
differences in term of portability to python3, so both versions should
be fine.
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman
Hi All,
On Tue, Feb 11, 2014 at 11:12 PM, Hamish hamis...@yahoo.com wrote:
Pietro wrote:
So are you agree to change the requirements for grass70
from Python = 2.4 to Python = 2.7 or Python = 2.6?
to add another me too for keeping support for python 2.6,
Debian/Squeeze: Python 2.6.6
Ubuntu
to the python interpreter in use and the
dictionary is the result of the script.core.region function.
Why is not working?
How can I fix this?
Pietro
# -*- coding: utf-8 -*-
START GRASS #
import os
import sys
## set PATHs
if sys.platform.startswith('linux
Hi Javier,
On Thu, Feb 27, 2014 at 4:45 PM, Javier Martínez-López
javi.martinez.lo...@gmail.com wrote:
I have a couple of problems when using pygrass for analyzing raster
maps stored in GRASS with the numpy library:
The RasterNumpy class was quite buggy, I did some changes last week
that
=0.006694380022900787
north: 228500
south: 215000
west: 63
east: 645000
nsres: 10
ewres: 10
rows: 1350
cols: 1500
cells: 2025000
after100.0135100.0150
Any Ideas?
Pietro
___
grass-dev mailing list
grass
chars in people’s names though.
I don’t see the reason to avoid source code in utf-8, at least on
python files, in particular when it is explicitly declare in the file
header like this (as in PEP 0263):
# -*- coding: utf-8 -*-
regards
Pietro
___
grass
chars in people’s names though.
I don’t see the reason to avoid source code in utf-8, at least on
python files, in particular when it is explicitly declare in the file
header like this (as in PEP 0263):
# -*- coding: utf-8 -*-
regards
Pietro
ps: sorry my previous email lost the format
. does the file
C:\Users\Pietro\Desktop\GRASS_FILE\ncb7\user1\WIND
exist?
yes, it exists, and I can use GRASS inside this mapset without problems.
Pietro
#print(sys.executable)
C:\Program Files (x86)\GRASS GIS 7.0.svn\extrabin\python.exe
#pprint(script.region())
{}
#pprint(os.environ
out as a tiff file instead to avoid this problem?
Why not using r.out.tiff [1]?
Thank you for testing.
Pietro
[0] http://trac.osgeo.org/grass/changeset/59192
[1] http://grass.osgeo.org/grass70/manuals/r.out.tiff.html
___
grass-dev mailing list
grass
Hi Javier,
On Tue, Mar 4, 2014 at 5:26 PM, Javier Martínez-López
javi.martinez.lo...@gmail.com wrote:
Thank you Pietro! I will try again! However, there seems to be a bug
(at least in version 59147) since I am getting NaN values reading some
maps with RasterNumpy, which are perfectly fine when
to set to nan some values, so I think is
a bug in the RasterNumpy class, the weird thing is that it seems to
work for the first two lines...
I have no time to work on it at the moment.
Best regards
Pietro
___
grass-dev mailing list
grass-dev
these parts separately, leaving
the decision to split in several packages to the package maintainer of
each distribution (Debian, Fedora, etc.).
Regards
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
be much clearer...
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
that using Sphinx and reStructuredText for Python will be beneficial.
Sphinx has support for python/C/C++/javascript [0].
May be we could reconsider [1] to move everything under sphinx.
But I'm not sure it is feasible.
Best regards
Pietro
[0] http://sphinx-doc.org/domains.html
[1] https
for user scripts,
but in wxGUI I still prefer to use GRASS Scripting Library to call
GRASS commands on the background.
+1, or using pygrass through Soeren's RPC interface.
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http
Dear dev,
I would like to know just a quick info that seems to be missing in the
r.watershed manual...
Are the basin or the stream number sorted hierarchically? from the
main to the smaller stream?
Pietro
___
grass-dev mailing list
grass-dev
',
u'build_polylines',
u'category',
...
u'what_rast',
u'what_rast3',
u'what_vect']
Someone has a deeper understanding on how the auto-complete works on
ipython/GRASS shell, Do you have any idea on where could be the
problem and how we could fix it?
Thanks
Pietro
[0]
http://trac.osgeo.org/grass
Hi Glynn,
On Tue, Jun 3, 2014 at 8:55 AM, Martin Landa landa.mar...@gmail.com wrote:
Reminder for all Windows users, please note that winGRASS 7.1 no.981
will be broken (calling python script from python script issue - eg.
wxGUI Extension manager) again.
2014-06-03 7:24 GMT+02:00
/ wxguiclean
make[1]: Entering directory
'/home/pietro/docdat/src/gis/grass71/gui/wxpython/docs/wxgui_sphinx'
rm -rf _build/*
rm -f _templates/layout.html
make[1]: Leaving directory
'/home/pietro/docdat/src/gis/grass71/gui/wxpython/docs/wxgui_sphinx'
make -C ./gui/wxpython/docs/wxgui_sphinx/ wxguiapidoc
On Fri, Jun 13, 2014 at 1:59 PM, Pietro peter.z...@gmail.com wrote:
I'm trying to build the docs with: make sphinxdoc , I think the
problem is that on my system the default python interpreter is
python3
Solved using the follow command:
{{{
$ make SPHINXBUILD=sphinx-build2 sphinxdoc
Hi Yann,
On Fri, Jun 20, 2014 at 7:21 AM, Yann Chemin yche...@gmail.com wrote:
line 86, in __init__
self.typedesc = diz['gisprompt']['prompt']
KeyError: u'prompt'
Thanks to find out this bug, should be fix in r60881.
Let me know.
Pietro
and wxGUI.
The compilation failures in temporal are a consequence of
lib/python/pygrass/gis/__init__.py calling grass.script.gisenv() at
the top level, which it shouldn't be doing.
Thanks to pointed out this! It was my fault sorry for that.
Removed in r60909
Pietro
, in module
m.inputs['elevation'] = elevation
File
/home/pietro/docdat/src/gis/grass71/dist.x86_64-unknown-linux-gnu/etc/python/grass/pygrass/modules/interface/typedict.py,
line 40, in __setitem__
raise TypeError(str_err % (value, self._type.__name__))
TypeError: The value: 'elevation
a Parameter instance.
Se the method that is called when you are trying to set an item to a
TypeDict is __setitem__.
I hope it makes sense.
Best regards
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass
in grass.script.errors or
grass.script.exceptions, or outside script so something like
grass.errors or grass.exceptions.
Do you think it is a bad idea?
Best regards
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass
On Fri, Jul 4, 2014 at 8:53 AM, Luca Delucchi lucadel...@gmail.com wrote:
On 3 July 2014 17:35, Pietro peter.z...@gmail.com wrote:
What do you think if we unify all our custom exceptions in one common file?
Just to avoid code repetitions and help consistency.
Perhaps we could create a new
Hi Vaclav,
On Mon, Jul 7, 2014 at 2:57 PM, Vaclav Petras wenzesl...@gmail.com wrote:
On Thu, Jul 3, 2014 at 11:35 AM, Pietro peter.z...@gmail.com wrote:
What do you think if we unify all our custom exceptions in one common
file? [snip]
Looking into the code I found the following custom
, otherwise please ask me! :-)
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
any effect.
I found the same thing some months ago:
https://lists.osgeo.org/pipermail/grass-dev/2014-February/067543.html
as explained by Vaclav:
If you change region in C or using ctypes in Python, it is affecting
only the current process.
best regards
Pietro
a vector map, created
some months ago, the g.gui.iclass crashed (without errors...).
I'm working on grass trunk on Linux.
It is working for you?
Best regards.
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman
]: Module('r.mapcalc')
}}}
but I think is less intuitive, do you see any other solutions?
Kind regards
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
programming in python? are you using
a shell or the gui?
I suspect that is missing grass, the following line is working on my pc:
from grass.pygrass.modules.shortcuts import raster as r
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http
import raster as r
from grass.pygrass.modules.shortcuts import imagery as i
I believe that you are using grass6.*, and unfortunately the pygrass
modules is available only on grass7.*
Let me know.
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
Il 14/set/2014 19:33 Markus Neteler nete...@osgeo.org ha scritto:
how will this be solved? Then we could start backporting python lib etc
to relbr7.
I will fix this tomorrow...
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http
Hi Sören,
On Sat, Sep 27, 2014 at 3:23 PM, Sören Gebbert
soerengebb...@googlemail.com wrote:
I would like to directly link to the source code
docs, hence referencing temporal framework Python functions and
classes in this document. But i don't know how? Are there any code
examples howto link
++
| Map: el Date: Mon Oct 6 10:29:19 2014|
| Mapset: user1 Login of Creator: pietro |
| Location: nc_basic_spm_grass7 |
| DataBase: /home/pietro/docdat/gis
casting the result in the scaler function
with dtype(...), the result is not properly casted, do you have an
idea on how could I solve this problem?
All the best
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman
On Mon, Oct 6, 2014 at 2:25 PM, Anna Petrášová kratocha...@gmail.com wrote:
On Mon, Oct 6, 2014 at 4:51 AM, Pietro peter.z...@gmail.com wrote:
Again everything is NULL, I'm doing something wrong or it is a bug?
Glynn could perhaps give you some more precise comment, but basically, max
On Mon, Oct 6, 2014 at 3:17 PM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
On 06/10/14 14:54, Pietro wrote:
Trying to circumvent the r.mapcalc min/max limit,
Just out of curiosity: why don't you just use r.recode or r.rescale ?
r.rescale was my first option, but it just reclassify
Il 06/ott/2014 17:04 Moritz Lennert mlenn...@club.worldonline.be ha
scritto:
On 06/10/14 16:14, Pietro wrote:
On Mon, Oct 6, 2014 at 3:17 PM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
On 06/10/14 14:54, Pietro wrote:
Trying to circumvent the r.mapcalc min/max limit,
Just out
to test
the existing libraries, and I#m not able to understand where the
problem.is.
Best regards
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
if it is a good idea to make pygrass a dependency of
the GUI.
I'm not able to reproduce the problem, what kind of error did you get?
Any way I will work in the __init__ file to isolate the ctypes stuff.
All the best
Pietro
___
grass-dev mailing list
grass
On Wed, Oct 8, 2014 at 12:38 PM, Glynn Clements
gl...@gclements.plus.com wrote:
do you think could be useful?
Not really. Just use r.info (or r.univar if you want the min/max for
the current region) and substitute the result into the expression.
Yes, I did in this way.
Thank you.
Pietro
On Wed, Oct 8, 2014 at 11:24 AM, Glynn Clements
gl...@gclements.plus.com wrote:
Pietro wrote:
So even if I'm explicitly casting the result in the scaler function
with dtype(...), the result is not properly casted, do you have an
idea on how could I solve this problem?
This is a bug
On Wed, Oct 22, 2014 at 10:49 AM, Martin Landa landa.mar...@gmail.com wrote:
Hi,
it's seems that currently PyGRASS doesn't support shorten parameters, eg.
Module('v.db.addcolumn', map='p5', col='vymera_ha double')
[cut]
grass.pygrass.errors.ParameterError: col is not a valid parameter.
On Wed, Oct 22, 2014 at 11:12 AM, Martin Landa landa.mar...@gmail.com wrote:
there is also another issue where pyGRASS seems to be too much strict, eg.
Module('d.vect', map='p6', type='point', color='purple',
icon='basic/star', size=10)
fails with
File ./u01.py, line 37, in compute
On Wed, Oct 22, 2014 at 5:40 PM, Martin Landa landa.mar...@gmail.com wrote:
2014-10-22 17:36 GMT+02:00 Pietro peter.z...@gmail.com:
Any chance to change this behaviour?
Actually I don't like the idea of shorten parameters... :-)
So I wont fix this.
well, pyGRASS should behave similarly
On Wed, Oct 22, 2014 at 5:45 PM, Martin Landa landa.mar...@gmail.com wrote:
This is fixed in grass71, should be backported.
are you planning to to this? Martin
Yes, I would like to do it...
The main problem are the difference between grass70 and grass71 on the
exception...
I would like to
.
hm, Soeren/Pietro any idea why it fails? Thanks, Martin
yes I think it fails because has broken the pickability of the
Module instance.
It should be fix in r62374.
However, I would like to revert your change... :-)
Introduce the debug message in the Module class it is a bad idea
because
Hi,
On Fri, Oct 24, 2014 at 12:56 PM, Sören Gebbert
soerengebb...@googlemail.com wrote:
However, I would like to revert your change... :-)
Introduce the debug message in the Module class it is a bad idea
because in this way also Module class is indirectly using ctypes.
Therefore all the
On Fri, Oct 24, 2014 at 1:05 PM, Martin Landa landa.mar...@gmail.com wrote:
2014-10-24 12:04 GMT+02:00 Pietro peter.z...@gmail.com:
However, I would like to revert your change... :-)
Introduce the debug message in the Module class it is a bad idea
because in this way also Module class
Hi,
On Sun, Oct 26, 2014 at 9:50 PM, Markus Neteler nete...@osgeo.org wrote:
On Sun, Oct 26, 2014 at 9:05 PM, Martin Landa landa.mar...@gmail.com wrote:
2014-10-26 17:51 GMT+01:00 Markus Neteler nete...@osgeo.org:
-the python API back port
it seems to be done by Pietro in r62382. Martin
grass.script.core as gscore
+1
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On Thu, Oct 30, 2014 at 10:49 AM, Markus Neteler wrote:
On Thu, Oct 30, 2014 at 8:40 AM, Glynn Clements wrote:
Are the replacements sufficient? g.setproj had a lot of logic for
dealing with the relationships between various parameters. Has that
been incorporated into the GUI? Is it
virtualenv [1].
my 2 cents.
Pietro
[0] http://pypi.python.org/pypi/pip - https://github.com/pypa/pip
[1] http://pypi.python.org/pypi/virtualenv
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Hi everyone!
I'm Pietro Zambelli a ph.D student of Trento University, I would like
to apply to the GSoC, my idea in short is: extend the python GRASS API
to make it more pythonic :-).
I would like to interact with region, raster and vector maps as
object, using and interacting with the map
you be interested in being my mentor?
Best regards.
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
the project page on melange to follow your advice.
What do you think?
I think that you are pushing the idea forward and in the right direction.
Thanks
Best regards
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org
are ALL backup mentors on the -dev list, especially those
of us who have participated in GSoC in the past years, but it's good
to have someone listed there)
I can do the co-mentor, i'll try the work of Pietro and I can help him
for what I know
Thank you Luca!
For all the developers
Hi all!
as reported in the new web page [0] of the pyGRASS project, at the moment you
can interact with a raster map in this way (read-only): ::
# import the raster function
import obj
# instantiate a Raster
dtm = obj.Raster('dtm')
# open the raster in read mode 'r'
:
http://pygrass.googlecode.com/files/week3.zip
and you can have the daily update version from the git repo:
git clone https://code.google.com/p/pygrass/
Questions, doubts, and criticism are welcome!
Best Regards,
Pietro
___
grass-dev mailing list
grass
classes are available here:
http://pygrass.readthedocs.org/en/latest/raster.html
Comments are welcome!
Best regards,
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
download, the weekly snapshot from here:
http://pygrass.googlecode.com/files/week4.zip
Questions, doubts, and criticism are welcome!
Best Regards,
Pietro
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo
1 - 100 of 276 matches
Mail list logo
