Based on what we have discussed (including some off-list), the best shot
seems to be using directions based on r.watershed on the carved DEM
together with the given (not computed) streams for HAND (streams are also
used for the carving and r.lake steps).
An alternative is using streams from
Ok cool. When I I try to run the r.stream.distance with this new new
stream direction layer (that I calculated with r.mapcalc
"streams_direction_8 = int((streams_direction + 45) / 45)" ),
it just hangs on the part that says: "caclulating downstream parameters".
So I am not sure what is going on
On Sat, Sep 29, 2018 at 1:55 PM Shane Carey wrote:
> My last bit of the puzzle is to create the flow direction raster. How do I
> reclassify in order to get the stream direction using r.mapcalc?
>
Hi Shane,
You are welcome. What you need to do are 2 steps: 1) vector to raster
conversion with
Super Vaclav - I am nearly there now - My last bit of the puzzle is to
create the flow direction raster. How do I reclassify in order to get the
stream direction using r.mapcalc? I am just coping in what you said from
your last email Vaclav so that you know which part I am stuck on. This is
really
On Thu, Sep 27, 2018 at 12:10 PM Shane Carey wrote:
>
> Is there anyway of the algorithm just being able to create a floodlain for
> actual real rivers as opposed to the derived river dataset?
>
Yes, just convert your streams to raster (presence-absence) and a raster
for flow direction as I
Hi,
Is there anyway of the algorithm just being able to create a floodlain for
actual real rivers as opposed to the derived river dataset?
Thanks
On Máirt 25 MFómh 2018 at 15:49, Shane Carey wrote:
> Image attached shows rivers (black line) and floodplain of where it thinks
> there are rivers
Image attached shows rivers (black line) and floodplain of where it thinks
there are rivers and in some cases where there may not be rivers.
Cheers
Le gach dea ghui,
*Shane Carey*
*GIS and Data Solutions Consultant*
On Tue, Sep 25, 2018 at 3:45 PM, Shane Carey wrote:
> Yes, this is the
Yes, this is the problem - there is not exact stream matching with the ones
derived on the carved DEM with the "Real" rivers. Any advice on how to get
around that?
Thanks
Le gach dea ghui,
*Shane Carey*
*GIS and Data Solutions Consultant*
On Tue, Sep 25, 2018 at 3:53 AM, Vaclav Petras wrote:
On Mon, Sep 24, 2018 at 6:33 PM Shane Carey wrote:
>
> This works well, but doesn't capture every river - is it a case of making
> the threshold value smaller or making a deeper carve in the rivers???
>
It's probably the threshold. How your rivers compare to the ones derived on
carved DEM?
Hi All,
This works well, but doesn't capture every river - is it a case of making
the threshold value smaller or making a deeper carve in the rivers???
Thanks in advance - I think this method would will work well, if it were
able to "flood" all rivers.
Thanks
Le gach dea ghui,
*Shane Carey*
Thanks, I will compare them and let you know the differences.
Thanks
On Domh 23 MFómh 2018 at 02:09, Vaclav Petras wrote:
> These are steps based on:
>
>
>
These are steps based on:
https://grasswiki.osgeo.org/wiki/From_GRASS_GIS_novice_to_power_user_(workshop_at_FOSS4G_Boston_2017)#Hydrology:_Estimating_inundation_extent_using_HAND_methodology
You need r.stream.distance module from Addons:
g.extension r.stream.distance
Get drainage and streams
On 09/21/2018 06:39 PM, Shane Carey
wrote:
Hi All,
I have used r.carve to carve out the rivers of a DTM - a
really super job. I now need to pour 3meters of water into
every cell in the river
13 matches
Mail list logo
