On Fri, 29 May 2020, Moritz Lennert wrote:
grass --help is your friend ;-)
Moritz,
Good to know; I never tried this.
grass -c epsg:4326 GISDBASE/LOCATION
replace GISDBASE and LOCATION with the respective names
-c can also be used with a file:
-c /path/to/georeferenced/file
Thanks
On 29/05/20 14:37, Rich Shepard wrote:
On Fri, 29 May 2020, Moritz Lennert wrote:
Importing such a large file can take a lot of time because of the
cleaning in order to get it into GRASS GIS' topological format.
Moritz,
I assumed it would taka a while, but it seemed to be stuck. Perhaps
On Fri, 29 May 2020, Moritz Lennert wrote:
Importing such a large file can take a lot of time because of the cleaning in
order to get it into GRASS GIS' topological format.
Moritz,
I assumed it would taka a while, but it seemed to be stuck. Perhaps because
that polygon was large, complex,
Hi GRASS members
Suppose you compute the "r.surf.area"(1) to some raster file and find that
the 3d area is smaller than your 2d area?
What could be the problem?
Note:
The exercise was done with a 5 m cell size raster file, with 37 km2
watershed with a slope of 0,0341 m/m, within 7.8 version of
On 28/05/20 17:25, Rich Shepard wrote:
I'm trying to import (using v.in.ogr) a rather large file (1.22G *.shp and
4.5M *.dbf). I see a lot of system disk reads, low cpu usage, but after a
half-hour it appears to have stopped processing.
Importing such a large file can take a lot of time
On 29/05/20 10:09, Micha Silver wrote:
On 29/05/2020 9:42, Uwe Fischer wrote:
Hello list,
thanks to Micha Silver and Helmut Kudrnovsky, the problem ist solved.
I did not set g.region prior to using v.what.rast. Seems to be a
typical non-Grass-Professional mistake. Now it works fine.
But
On 29/05/2020 9:42, Uwe Fischer wrote:
Hello
list,
thanks to
Micha Silver and Helmut Kudrnovsky, the problem ist solved.
I did not set g.region prior to using v.what.rast. Seems to
Hei Uwe,
It is unfortunately not obvious from the very beginning, but actually one of
the nice features of GRASS GIS.
No need to "clip" any data. You can easily operate on any subset of your data
and all data will be cleanly aligned even if the extent of on layer changes
Once you are used