Dear Helmut,
On Sat, Jan 3, 2015 at 1:49 PM, Helmut Kudrnovsky hel...@web.de wrote:
as the extent of the r.slope.aspect output is 1 pixel less then DEM input,
the extent of the calculation output shrinks from one step to the next as
the resolution is coarsening.
any idea how to overcome such
Hi Pietro,
this is not a bug.
I unterstand the same. my question is more about how to implemented the
mentioned iterative algorithm which uses coarser resolution by each step and
how to avoid an extent shrinking of e.g. about 400m with the coarsest
resolution.
-
best regards
Helmut
--
Helmut,
you can use r.resamp.rst which computes slope and aspect and does not shrink
the region. But you may need to adjust the parameters
to make sure it works well.
Another way would be to modify r.slope.aspect to compute the values at the
edges - a second order polynomial min.square
Just compiled the latest gdal (1.11) and grass (trunk - rev 63950) and now
want to compile gdal again with grass support. However, I am getting an
error, which appears to be a problem in gdal/frmts/grass (see below). Any
idea how to solve this?
Helmut Kudrnovsky wrote
hi devs,
I've added a script [1] with following calculations ideas:
- do some calculations with r.slope.aspect output
- coarse the resolution (but meet the DEM extent)
- do some calculations with r.slope.aspect output at the coarser
resolution
- coarse the
#2525: Unable to open sqlite database if path contains non-latin letters
-+--
Reporter: marisn | Owner: grass-dev@…
Type: defect | Status: new
Priority:
#2525: Unable to open sqlite database if path contains non-latin letters
-+--
Reporter: marisn | Owner: grass-dev@…
Type: defect | Status: new
Priority:
Dear Helena,
I believe that any reasonable estimate is better than the current
shrinking region (in r.flow we just
propagate the same values to the edges), but that does not seem to be the
consensus.
I agree with you that a reasonable estimate is better than the current
situation.
I've
On Fri, Jan 2, 2015 at 10:08 AM, Benjamin Ducke bendu...@fastmail.fm wrote:
Hi Markus,
On 01/01/15 22:18, Markus Metz wrote:
Hi all,
a new spatial index for point data is available in lib/btree2: a
multidimensional search tree, also known as k-d tree.
Excellent news.
What is it good
On Sat, Jan 3, 2015 at 4:41 AM, Anna Petrášová kratocha...@gmail.com wrote:
On Fri, Jan 2, 2015 at 1:10 PM, Markus Neteler nete...@osgeo.org wrote:
On Fri, Jan 2, 2015 at 2:05 AM, Anna Petrášová kratocha...@gmail.com
On Wed, Dec 31, 2014 at 9:31 AM, Markus Neteler nete...@osgeo.org
Hi,
On Sun, Jan 4, 2015 at 3:48 PM, Paulo van Breugel
p.vanbreu...@gmail.com wrote:
Just compiled the latest gdal (1.11) and grass (trunk - rev 63950) and now
want to compile gdal again with grass support.
It is recommended to compile the plugin (way easier than dealing with
circular dependencies):
On Fri, Jan 2, 2015 at 3:34 PM, Vaclav Petras wenzesl...@gmail.com wrote:
On Thu, Jan 1, 2015 at 5:49 PM, svn_gr...@osgeo.org wrote:
Author: neteler
Date: 2015-01-01 14:49:11 -0800 (Thu, 01 Jan 2015)
New Revision: 63924
Added:
grass/branches/releasebranch_7_0/general/g.list/testsuite/
#2526: extend r.slope.aspect to compute the values at the edges
-+--
Reporter: hellik | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal
On Sun, Jan 4, 2015 at 10:30 PM, Markus Neteler nete...@osgeo.org wrote:
On Sun, Jan 4, 2015 at 3:48 PM, Paulo van Breugel
p.vanbreu...@gmail.com wrote:
Just compiled the latest gdal (1.11) and grass (trunk - rev 63950) and
now
want to compile gdal again with grass support.
It is
On Sun, Jan 4, 2015 at 10:54 PM, Paulo van Breugel
p.vanbreu...@gmail.com wrote:
On Sun, Jan 4, 2015 at 10:30 PM, Markus Neteler nete...@osgeo.org wrote:
Convince the GDAL developers to take care of
http://trac.osgeo.org/gdal/ticket/2953
I would try if I knew how. To file a bug report I would
Hi all,
it seems that PyGRASS tests are down for some reason. This happened few
days ago between r63925 and r63939.
http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2015-01-02-08-00/report_for_nc_spm_08_grass7_nc/testfiles.html
#2528: r.shade not in menu
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
#2527: r.shade not in menu
--+-
Reporter: cmbarton | Owner: grass-dev@…
Type: defect| Status: new
Priority: normal
Is there some way to check for recently renamed or new modules? I just found
that r.shade (new in GRASS 7) is not in the menu and r.relief (renamed) needs
to be revised in the menu from its old name (r.shaded.relief). I created
tickets for both of these, but if there is a way to ID new or
#2527: r.shade not in menu
---+
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal
#2527: r.relief not in menu
---+
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal
21 matches
Mail list logo
