Hello Markus,
first of all thank very much for your efforts.
Unfortunately, the error message "Projection UTM (zone invalid) did
appear anyhow although I replaced the *.prj file by that one you sent.
But now I figured out the following (after importing the shape file and
making active):
-
Hi Martin,
On Wed, Jul 1, 2020 at 4:29 PM Martin Bittens wrote:
...
> I don't know why this happened but obviously GRASS provides different
> metadata for the same shape-file depending on the command you are using.
To analyse this in depth access to the dataset would be required (even
an
On Wed, Jul 1, 2020 at 11:04 PM Rich Shepard wrote:
>
> A 5m DEM displays very quickly on the monitor (using d.rast
> map=basin_5mtopo) but when that map is the raster in a psmap script it takes
> a very long time for grass to process the script (with the vector overlays).
>
> Why might this be?
Dear all,
As some of you might know, we have been working on the development and
setup of a new and shiny GRASS GIS website (finally!) for a long time.
It is now available for testing at: https://staging.grass.osgeo.org/
We will start the release procedure described in
A 5m DEM displays very quickly on the monitor (using d.rast
map=basin_5mtopo) but when that map is the raster in a psmap script it takes
a very long time for grass to process the script (with the vector overlays).
Why might this be?
Regards,
Rich
___
One project has 70 DEMs (13G worth) that I don't need now and I'd like to
tar and move them to an external hard drive. What's the recommended way to
do this so they can be restored for future projects?
TIA,
Rich
___
grass-user mailing list
On Wed, Jul 1, 2020 at 11:25 PM Rich Shepard wrote:
>
> One project has 70 DEMs (13G worth) that I don't need now and I'd like to
> tar and move them to an external hard drive. What's the recommended way to
> do this so they can be restored for future projects?
I see two options:
- export the
On Wed, 1 Jul 2020, Markus Neteler wrote:
As some of you might know, we have been working on the development and
setup of a new and shiny GRASS GIS website (finally!) for a long time. It
is now available for testing at: https://staging.grass.osgeo.org/
Markus and the new website team,
I'm
On Wed, 1 Jul 2020, Markus Neteler wrote:
The monitor shows pixels only at needed resolution (it uses nearest
neighbors to downsample on the fly) while ps.map operates at map
resolution (not sure if that can be set differently besides resampling it
to a new map at lower resolution if acceptable
On Wed, 1 Jul 2020, Markus Neteler wrote:
I see two options:
- export the DEMs, still in GRASS GIS format, with r.pack (in a loop)
- or simply package the mapset(s) containing the DEMs.
Markus,
With changes to GRASS over the years I was no sure whether making a tarball
of the mapset would
Dear Grass Users --
I am struggling to understand the usage of the
"solver=" option featured by both r.cost and
r.walk.
The r.walk manual page gives no details about it.
The r.cost manual page does contain an illustration
of the working principle, but no examples on how
to quantify the cells in
Hi Markus
you developed a nice web-site, congratulations.
I can see, that you categorize the users, and that might be an asset.
Perhaps there are really classes like newbies, regular users and power users
and they need different information channels.
It took me some time to make use at least of
Hi,
On Wed, May 27, 2020 at 8:50 AM Stefan Blumentrath
wrote:
> Hi Ashley,
>
> The possibility to return negative horizon values was introduced here:
>
> https://github.com/OSGeo/grass/commit/688d5885557f22c7ea6618dcac3ddfbfc764731a#diff-5ce8290f429502e23efaf9ebdc18bd2b
>
>
> The output with the
13 matches
Mail list logo
