On Wed, Feb 4, 2015 at 9:46 AM, Margherita Di Leo direg...@gmail.com wrote:
On Tue, Feb 3, 2015 at 9:22 PM, Markus Metz
On Tue, Feb 3, 2015 at 2:41 PM, Margherita Di Leo direg...@gmail.com
wrote:
anyone has experience with .raw files? I happen to have one to analyze
(quite large indeed) and
On Wed, Feb 4, 2015 at 5:27 AM, RichardCooper richtcoo...@hotmail.com wrote:
Apologies for re-posting, but I noticed that much of the post's content
disappeared in the email.
Also, as an update I tried to add both a start and end date to the input
file (following the t.register manual) but
Markus,
On Wed, Feb 4, 2015 at 10:30 AM, Markus Neteler nete...@osgeo.org wrote:
On Wed, Feb 4, 2015 at 9:46 AM, Margherita Di Leo direg...@gmail.com
wrote:
On Tue, Feb 3, 2015 at 9:22 PM, Markus Metz
On Tue, Feb 3, 2015 at 2:41 PM, Margherita Di Leo direg...@gmail.com
wrote:
anyone
Markus,
On Wed, Feb 4, 2015 at 10:51 AM, Markus Neteler nete...@osgeo.org wrote:
On Wed, Feb 4, 2015 at 10:45 AM, Margherita Di Leo direg...@gmail.com
wrote:
On Wed, Feb 4, 2015 at 10:30 AM, Markus Neteler nete...@osgeo.org
wrote:
...
... are you using the same GDAL version in QGIS and
Hi Markus,
On Tue, Feb 3, 2015 at 9:22 PM, Markus Metz markus.metz.gisw...@gmail.com
wrote:
On Tue, Feb 3, 2015 at 2:41 PM, Margherita Di Leo direg...@gmail.com
wrote:
Hi,
anyone has experience with .raw files? I happen to have one to analyze
(quite large indeed) and r.in.gdal doesn't
On Wed, Feb 4, 2015 at 10:45 AM, Margherita Di Leo direg...@gmail.com wrote:
On Wed, Feb 4, 2015 at 10:30 AM, Markus Neteler nete...@osgeo.org wrote:
...
... are you using the same GDAL version in QGIS and GRASS GIS?
1.10.1 (2013/08/26)
Not that new :-)
But if it is a mosaic, the camera
Hi,
the problem is that the model year has 360 days, ignoring the
Gregorian calendar that is the based on absolute time in GRASS. Hence,
the 29. and 30. February do not exist in 1951.
You can use relative time with a daily resolution, so you don't have
to to deal with Gregorian calendar time.
Hi,
I just tested in trunk, and it works: The temporary file that is create
when assigning a raster to an python array is deleted once e.g.
the python session is closed again. So this would be a nice
thing also to have implemented in the next RC of GRASS7.
/johannes
On Tue, Feb 3, 2015 at
On 04/02/15 15:23, Markus Metz wrote:
On Wed, Feb 4, 2015 at 1:14 PM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
On 04/02/15 11:48, Martin Album Ytre-Eide wrote:
Hello!
I trying to set a label for a range of values in a raster.
I am using r.category (grass 7.0)
r.category
On Wed, Feb 4, 2015 at 11:24 AM, Markus Neteler nete...@osgeo.org wrote:
- copy-paste the command here
$ gdalinfo mosaic_RGB.raw
ERROR 4: `mosaic_RGB.raw' not recognised as a supported file format.
gdalinfo failed - unable to open 'mosaic_RGB.raw'.
- run file thefilename and post the
On 04/02/15 11:48, Martin Album Ytre-Eide wrote:
Hello!
I trying to set a label for a range of values in a raster.
I am using r.category (grass 7.0)
r.category map=lwc_2014 separator=':' rules=lwc.rules
My lwc.rules looks like this:
0:30:0.9
31:90:0.7
91:252:0.5
so, r.category does not
On Wed, Feb 4, 2015 at 10:59 AM, Margherita Di Leo direg...@gmail.com wrote:
On Wed, Feb 4, 2015 at 10:51 AM, Markus Neteler nete...@osgeo.org wrote:
...
What does gdalinfo report on the file? If that works, r.in.gdal will work,
too.
Says that it is not recognised as a supported file format.
Mistery SOLVED.. the file got damaged during copy. The proper file is read
by gdal and obviously by grass. sorry for noise
madi
On Wed, Feb 4, 2015 at 11:54 AM, Margherita Di Leo direg...@gmail.com
wrote:
On Wed, Feb 4, 2015 at 11:24 AM, Markus Neteler nete...@osgeo.org wrote:
-
On Wed, Feb 4, 2015 at 1:14 PM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
On 04/02/15 11:48, Martin Album Ytre-Eide wrote:
Hello!
I trying to set a label for a range of values in a raster.
I am using r.category (grass 7.0)
r.category map=lwc_2014 separator=':' rules=lwc.rules
On 04/02/15 15:45, Moritz Lennert wrote:
On 04/02/15 15:23, Markus Metz wrote:
On Wed, Feb 4, 2015 at 1:14 PM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
On 04/02/15 11:48, Martin Album Ytre-Eide wrote:
Hello!
I trying to set a label for a range of values in a raster.
I am using
On 04/02/15 11:36, Robert Nuske wrote:
Hi GRASS-Users
is there a way to generalize polygons including their holes?
I am not too worried about topology, there are only polygons of one class in
the dataset.
I tried the following
v.generalize in=m3 out=m5 type=area method=douglas threshold=5000
Hello!
I trying to set a label for a range of values in a raster.
I am using r.category (grass 7.0)
r.category map=lwc_2014 separator=':' rules=lwc.rules
My lwc.rules looks like this:
0:30:0.9
31:90:0.7
91:252:0.5
so, r.category does not seem to read my range, but in stead gives me labels
Hi GRASS-Users
is there a way to generalize polygons including their holes?
I am not too worried about topology, there are only polygons of one class in
the dataset.
I tried the following
v.generalize in=m3 out=m5 type=area method=douglas threshold=5000
which simplified the outer boundaries
Hi,
I just try to follow some examples r3.out.vtk
to get some nice 3D plots in paraview.
http://grass.osgeo.org/grass70/manuals/r3.out.vtk.html
In the manual there is an example that
uses the r.in.onearth add-on
(http://trac.osgeo.org/grass/browser/grass-addons/grass6/raster/r.in.onearth
)
that
19 matches
Mail list logo
