Re: [GRASS-dev] r.geomorphon multiresolution mode
Hi Michael,
On 2021-02-15 at 14:23 -08, Michael Barton wrote...
> Can anyone explain how multiresolution model works in r.geomorphon? It
> does not seem to respond to any setting changes and seems to always
> produce blank maps (testing with NC demo set). There is nothing about
> multiresolution mode in the manual for 7.8 or 7.9
I'm getting core dumps if I set the 'step' keyword.
Looking through some old notes it seems I created my own multi-resolution
implementation in parallel with:
parallel "r.geomorphon -m elevation=z_b search={} forms=forms_{}
ternary=pattern_{}" ::: 450 1000 4500 1 45000
-k.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Bugs in r.stream.extract
On 2020-11-25 at 04:17 -08, ming han wrote... > And another problem I got is that the flow accumulation I got from > r.accumulate and r.watershed is different when r.accumulate using flow > direction from r.watershed. Again is there anyway r.watershed supports > using flow direction, so we can get the consistent result. There may be reasons for these differences? For example, if SFD v. MFD, or the "-a" flag to r.watershed? > We need this when we need to adjust the flow direction from > r.watershed or r.stream.extract. and then we need to determine new > flow accumulation with an adjusted flow direction dataset. If the > result is inconsistent, not sure what is the solution is. It isn't clear why you are adjusting the flow direction. Is this required? >> But, If I only want to use flow direction to drive streams, which >> function I should use? https://grass.osgeo.org/grass78/manuals/r.water.outlet.html but this only works for 1 outlet. -k. ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Bugs in r.stream.extract
Hi Ming, On 2020-11-23 at 09:05 -08, ming han wrote... > Hope this email finds you well. I got a weird result when using > r.stream.extract, as shown in the following figure. The back grids is > the flow accumulation layer with a flow accumulation threshold larger > than 1000. while the blue line is the stream generated by > r.stream.extract. Why the stream from r.stream.extract did not follow > flow accumulation results? And how to fix this problem? Is there any chance you can share the raster that includes this region so I can examine it? And the exact command you ran? -k. ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] g.extension: still fetching from SVN?
On 2019-08-05 at 16:26 -04, Martin Landa wrote... > Hi, > > po 5. 8. 2019 v 22:22 odesÃlatel Markus Neteler napsal: >> https://trac.osgeo.org/grass/milestone/7.6.2 >> -> 5th Aug 2019 was planned :-) > > yes, there is one blocker issue which should be solved before any > release. How to deal with svn keyword propagation in the code ($DATE$, > $REVISION$, ...). There is no straightforward replacement for git to > my knowledge. Any suggestion very welcome! It seems like this is not officially supported, can be done easily with some scripts [1], but is not recommended [2]. Why is it needed? I regularly use the gitinfo LaTeX package that provides a git commit hook. This hook simply puts latest hash (and some other commit data such as author, branch, date, etc.) into a file, that the LaTeX package then uses to make nice headers or footers with the commit info. Could a commit hook make a file that is then somehow included in the footer of each HTML file? -k. [1] https://stackoverflow.com/questions/11534655/git-keyword-substitution-like-those-in-subversion [2] https://git.wiki.kernel.org/index.php/GitFaq#Does_Git_have_keyword_expansion.3F ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] dealing with null values in rasters only within mask
Hi Moritz, More generally from Stefan's answer: 1) MASK is a raster that you can use is your r.mapcalc expressions 2) A two-step process where everything is filled, and then the parts outside the mask are re-nulled? -k. ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] git howto get a single diff for a PR with multiple commits
On 2019-06-04 at 23:12 +02, Markus Metz wrote... > I would like to speed up reviewing of a PR with multiple commits by > reading a single diff file. How is this possible with git? [...] can > git (on CLI on my local copies) also do this? I think git can diff any two commits. Do this by providing two commit hashes instead of just one (which defaults to that v. the currently checked out hash + any local changes). -k. ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
