> This is my first question
as already mentioned in other threads, gdalinfo your.tif should always be
your first step.
ias GRASS is based upon GDAL, the gdalinfo oztput is needed to understand
how GDAL sees the tif raster data.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x
On Fri, 13 Jul 2018, Rich Shepard wrote:
2. The command, 'grass75 -c EPSG:32126' created a new location.
However, I cannot re-project these raster maps because there's no
projection information in that location:
$ ls EPSG\:32126/PERMANENT/
CURGROUP MYNAME WIND cell/ cellhd/
Not sure what's going on since I've not seen this before. But have you
tried different threshold values?
On Fri, Jul 13, 2018 at 2:06 PM Erin Hanan wrote:
> Hello,
>
> I am new to the list; please let me know if my question should be
> formatted differently.
>
> I have been running r.watershed o
'gdalinfo --proj4' returns this string from the ESRI GRID file:
+proj=lcc +lat_1=44.34 +lat_2=46 +lat_0=43.66
+lon_0=-120.5 +x_0=250 +y_0=0 +ellps=GRS80 +units=ft +no_defs
Using that to create a new location then running 'r.in.gdal' produces this
warning:
WARNING:
* Frank David [2018-07-13 19:26:36 +0200]:
Le 11/07/2018 à 09:31, Nikos Alexandris a écrit :
* Frank David [2018-07-10 15:44:51 +0200]:
Le 10/07/2018 à 12:25, Nikos Alexandris a écrit :
* frank [2018-07-10 08:05:29 +0200]:
Hi dear grass users,
I'm trying to get two field name of an
Le 11/07/2018 à 09:31, Nikos Alexandris a écrit :
* Frank David [2018-07-10 15:44:51 +0200]:
Le 10/07/2018 à 12:25, Nikos Alexandris a écrit :
* frank [2018-07-10 08:05:29 +0200]:
Hi dear grass users,
I'm trying to get two field name of an attribute table (ctx_map) by
the options of
Hello,
I am new to the list; please let me know if my question should be formatted
differently.
I have been running r.watershed on a large (>400 km2) basin using a 10 m
resolution dem. I am finding that it produces some half basins that are
either fragmented or very small (i.e., just a few pixels
On Fri, 13 Jul 2018, Moritz Lennert wrote:
Try pointing to the directory instead of the hdr.adf file.
Moritz,
As I posted to the list, it was a typo in the command saved in my grass
processing log (a file I maintain with emacs). How that one letter was
capitalized I don't know, but there it
On 13/07/18 17:25, Rich Shepard wrote:
I'm not seeing why grass7.5svn has this issue with r.in.gdal:
r.in.gdal -o
in=$HOME/projects/oregon/estacada-rock/data/topography/estacada-45122C3/2009_OLC_Hood-to-Coast/Highest_Hit/hh45122c3/hdr.adf
out=estacada_hhdem2009
ERROR 4:
/home/rshepard/pro
On Fri, 13 Jul 2018, Rich Shepard wrote:
I'm not seeing why grass7.5svn has this issue with r.in.gdal:
Now I see it:
in=$HOME/projects/oregon/estacada-rock/data/topography/estacada-45122C3/
s/C/c/
Rich
___
grass-user mailing list
grass-use
On 13/07/18 09:51, marion-bru...@sfr.fr wrote:
Hello,
I am working on Windows and I tried using GRASS 7.2.2, GRASS 7.4.0 and
GRASS 7.4.1 to see if there is any difference, but it is always the same.
I have a ratser map calleddec-juin
First I didr.clump input=dec-juin@1217_Interpo0618 output=
I'm not seeing why grass7.5svn has this issue with r.in.gdal:
r.in.gdal -o
in=$HOME/projects/oregon/estacada-rock/data/topography/estacada-45122C3/2009_OLC_Hood-to-Coast/Highest_Hit/hh45122c3/hdr.adf
out=estacada_hhdem2009
ERROR 4:
/home/rshepard/projects/oregon/estacada-rock/data/topography
Hi
I noticed you have a raster with a "minus" character in the name.
Sometimes that gives trouble. Not sure if it's relevant to the
current problem, but it might be worth renaming to something like
"dec_juin" (underscore instead of '-') and trying again.
On 07/
Sorry I
hit send before finishing my email...
De :
marion-bru...@sfr.fr
A : "Helmut Kudrnovsky" ,"grass-user"
Envoyé: vendredi 13 juillet 2018 12:43
Objet : ***SPAM*** Re: [GRASS-user] calculate the volume of a DEM with
r.volume
(sorry for the html emails, hope this one is readable)
I tri
(sorry for the html emails, hope this one is readable)
I tried with the North Carolina dataset (in GRASS 7.4.0), I had those
results:
r.volume input=elevation@PERMANENT
clump=geology_30m@PERMANENT
Volume report on data from using clumps on
[could you send plain text mails? as html mails aren't readable in the ML,
see:
http://lists.osgeo.org/pipermail/grass-user/2018-July/078772.html]
>As you can see, I have nothing at the end of the command...
tested here with
System Info
Hello,
I am working on Windows and I tried using GRASS 7.2.2, GRASS 7.4.0 and GRASS
7.4.1 to see if there is any difference, but it is always the same.
I have a ratser map called dec-juin
First I did
r.clump input=dec-juin@1217_Interpo0618 output=test
to get the clumps
Then I did
r.volume inp
17 matches
Mail list logo