Hi,
I have started the draft list of new features in GRASS 7:
http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures
This will help to better advertise our progress. Please add
missing items (there will be many).
thanks
Markus
I have started the draft list of new features in GRASS 7:
http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures
Wow,
looks great.
O question on this here:
Improved Python API: * read/write GRASS rasters to/from NumPy
How do I trigger this?
Will a command r.out.numpy save the raster in a pickled array?
How will the geographic information be retrained?
This gives a big potential for plotting with basemap!
Is such a feature also planned for vectors? They could be exported to a
format usable by Shaply...
Tim wrote:
O question on this here:
> Improved Python API: *read/write GRASS rasters to/from NumPyHow do I trigger this?
Will a command r.out.numpy save the raster in a pickled
array? How will the geographic information be retrained?This gives a big potential for plotting with basemap!
try with r.out.mat. AFAIU NumPy/SciPy is essentially an attempt
to clone Matlab in python. Given that, I would not be surprised
if it just sort of worked, given the right command.
Is such a feature also planned for vectors? They could be
exported to a format usable by Shaply...
I'm pretty sure I wrote a v.out.mat, have a look in wiki addons.
(I've got no idea what Shaply does or wants)
Hamish
Tim Michelsen wrote:
O question on this here:
> Improved Python API: * read/write GRASS rasters to/from NumPy
How do I trigger this?Will a command r.out.numpy save the raster in a pickled array?
How will the geographic information be retrained?
The grass.script.array module defines a class "array" which is a
subclass of numpy.memmap with .read() and .write() methods to
read/write the underlying file via r.out.bin/r.in.bin.
Example:
import grass.script.array as garray
a = garray.array()
a.read("elevation.dem")
b = garray.array()
b[...] = (a / 50).astype(int) * 50 # or whatever
b.write("elev.50m")
The size of the array is taken from the current region.
The main drawback of using numpy is that you're limited by available
memory. Using a subclass of numpy.memmap lets you use files which may
be much larger, but processing the entire array in one go is likely to
produce in-memory results of a similar size.
Unfortunately, I don't think that it's possible to define an array
subclass which provides the data in chunks.
--
Glynn Clements <glynn@gclements.plus.com>
On Mon, Jan 25, 2010 at 11:17 AM, Markus Neteler <neteler@osgeo.org> wrote:
Hi,
I have started the draft list of new features in GRASS 7:
http://trac.osgeo.org/grass/wiki/Grass7/NewFeaturesThis will help to better advertise our progress. Please add
missing items (there will be many).
I'll give a talk in 23hs from now - please tell me about things
missing in the features list 
You can also just respond here
and I'll update the Wiki.
Just to avoid that central improvements are not mentioned.
cheers
Markus
Hello Markus,
new IMHO noticeable features in GRASS 7 are:
gmath:
* Replacement of most of the numerical recipes code with ccmtah
functionality (lu solver is work in progress)
* Implementation of blas level 1,2 and 3 functions which are in use by
all gmath solver, the gpde library and many modules.
* ATLAS wrapper for blas level 1 functions (level 2, and 3 are work in progress)
raster:
r.neighbours -> added new option to process only marked cells (i.e:
selective elevation map improvement)
r(3).gwflow -> Added support for water budget calculation,
documentation largely improved
r.solute.transport -> New module to compute the solute transport of
groundwater in porous media using an implicit finite volume approach
imagery:
i.cca -> supports now much more raster maps for canonical analyses
(multi-spectral (8) -> hyper-spectral (thousands)), converted from
Fortran style to C-style
Just my 2c
Soeren
2010/1/26 Markus Neteler <neteler@osgeo.org>:
On Mon, Jan 25, 2010 at 11:17 AM, Markus Neteler <neteler@osgeo.org> wrote:
Hi,
I have started the draft list of new features in GRASS 7:
http://trac.osgeo.org/grass/wiki/Grass7/NewFeaturesThis will help to better advertise our progress. Please add
missing items (there will be many).I'll give a talk in 23hs from now - please tell me about things
missing in the features list
and I'll update the Wiki.
Just to avoid that central improvements are not mentioned.cheers
Markus
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Hello,
sorry for the noise, i forgot to mention:
I have ported r.sim.water and r.sim.sediment to be functional in grass
7, but they are still
not compiled by default. Vector point support is still missing, the
old "site" code is only commented out.
Much more testing is needed.
WPS:
libgis supports the automatic generation of a WPS 1.0.0 process
description XML document for each module (c, c++, python, shell)
Best regards
Soeren
2010/1/26 Markus Neteler <neteler@osgeo.org>:
On Mon, Jan 25, 2010 at 11:17 AM, Markus Neteler <neteler@osgeo.org> wrote:
Hi,
I have started the draft list of new features in GRASS 7:
http://trac.osgeo.org/grass/wiki/Grass7/NewFeaturesThis will help to better advertise our progress. Please add
missing items (there will be many).I'll give a talk in 23hs from now - please tell me about things
missing in the features list
and I'll update the Wiki.
Just to avoid that central improvements are not mentioned.cheers
Markus
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Soeren Gebbert wrote:
I have ported r.sim.water and r.sim.sediment to be functional in grass
7, but they are still
not compiled by default. Vector point support is still missing, the
old "site" code is only commented out.
Much more testing is needed.
If you suspect that they'll compile on most systems, I'd suggest
enabling them.
Given the frequency of library changes in 7.0, any code which is
disabled will be prone to bit-rot, i.e. not being updated to account
for library changes.
--
Glynn Clements <glynn@gclements.plus.com>
Hello,
try with r.out.mat. AFAIU NumPy/SciPy is essentially an attempt
to clone Matlab in python. Given that, I would not be surprised
if it just sort of worked, given the right command.
Thanks for providing that pointer.
Here is a example that I was trying out with Spearfish location:
### PY ###
import scipy.io as sio
elev = sio.loadmat('elev.mat')
elev.get('map_data')
data = elev.get('map_data')
import pylab
pylab.plot(data)
pylab.show()
pylab.contour(data)
pylab.contour(data.reverse())
import numpy as np
data_rev = data[::-1]
pylab.contour(data_rev)
# => this is a quick plot. basemap mapping may provide a nicer map!
#######
Is such a feature also planned for vectors? They could be
exported to a format usable by Shaply...I'm pretty sure I wrote a v.out.mat, have a look in wiki addons.
(I've got no idea what Shaply does or wants)
Please see also:
http://permalink.gmane.org/gmane.comp.gis.grass.devel/37719