Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Average slope calculation #18

Open
MichaelPil opened this issue Apr 15, 2022 · 14 comments
Open

Average slope calculation #18

MichaelPil opened this issue Apr 15, 2022 · 14 comments
Labels
feature request Something to add question Further information is requested

Comments

@MichaelPil
Copy link

Greetings,

Could you please explain how the average slope of the stream (used for the calculation of concentration time) is calculated ?

We have been experimenting with other tools, such as QGIS and its plugins, and also with some average slope calculation formulas on excel spreadsheets. The results we get on the average slope calculations using these methods, significantly differ from the slope calculated on the same stream by Lekan. Lekan always calculates almost 10% (in absolute value, for example 3.16% vs 14.28% on QGIS or by "hand") lower average slope values, meaning also higher concentration times and lower flow rates. Note that we use the same flow path on the same DEM on both Lekan and QGIS.

In fact we also copied the distance and altitude values on the Longitudinal Profile window to our spreadsheet and calculated the average slope, which didn't match to the average slope by Lekan.

So our goal is to evaluate the accuracy of our spreadsheets and of the QGIS tools we use. Or perhaps there is some kind of error on the formula used by Lekan?

At the moment we are using Lekan version 2.2.1.

Thank you very much
Kind regards,

@vcloarec
Copy link
Owner

Hi,
Can you put here a screen shot of the longitudinal profile in Lekan with the table?

@vcloarec
Copy link
Owner

vcloarec commented Apr 15, 2022

The formula used in Lekan is this one:

averageSlope

where
L is the length of each segment
p is slope of each segment

@MichaelPil
Copy link
Author

This is the Longitudinal profile (it usually prints the slope % of its segment but for some reason this time it doesn't):
image

And here is a snapshot of the table :
image

This is one of the watersheds where we observe the differences. In this one for example Lekan calculates 2.40 % average slope, while with other methods I calculated 12 - 14 % average slope.

@vcloarec
Copy link
Owner

Some strange stuff...
Normally, the direction of the stream is from left to right in the plot.
did you draw the stream by hand ?

@MichaelPil
Copy link
Author

Yes I did draw it by hand because the DEM was not very precise and the software couldn't determine the flow path automatically.

And perhaps I drew it from downstream to usptream.

@vcloarec
Copy link
Owner

vcloarec commented Apr 15, 2022

Yes I did draw it by hand because the DEM was not very precise and the software couldn't determine the flow path automatically.

better to do in the other side to have a better behavior of Lekan. Anyway, this should not explain the difference.

Be sure you approach in the same as the one with this formula

The formula used in Lekan is this one:

averageSlope

@MichaelPil
Copy link
Author

This is another stream, also drawn by hand, but from upstream to downstream.
image

And its table:
image

The average slope calculated is 10.68% and with other methods we calculate 20%. But I 'm not sure which formula qgis algorithms use.

@vcloarec
Copy link
Owner

which tool do you use with QGIS?

@MichaelPil
Copy link
Author

I use the qprof plugin with the "drape" and "extract Z values" commands.

@MichaelPil
Copy link
Author

For our spreadsheets we use 2 simple formulas :

  1. s average = si*wi,
    where wi is the percentage of each line segment on the full path

  2. s = (Hmax-Hmin) / ΣLi

Could you please give me a citation (reference) for the formula Lekan uses?

@vcloarec
Copy link
Owner

It is a commonly used formula used for average slope, it can be named formula of Taylor Schwartz.

@vcloarec vcloarec added the question Further information is requested label Apr 15, 2022
@MichaelPil
Copy link
Author

Ok , Thank you very much for the information.

May I suggest an addition for newer versions? Perhaps it would be useful to add a few more formulas for the average slope calculation and give the user the option to select the preferred formula. It seems to me that Taylor Schwartz model is calculating a little milder slopes than I would expect, so it would be useful to be able to compare it with other models and choose one in a way similar to choosing the appropriate concentration time formulas.

Once again thank you for your response and congratulations for your great work and software!

Kind regards

@vcloarec vcloarec added the feature request Something to add label Apr 15, 2022
@vcloarec
Copy link
Owner

Yes, it could be a improvement, but not the priority for now. If you need it, don't hesitate to sponsor it to make it a priority 😃

Note that it is not mandatory to use the slope calculated by Lekan, you can override this slope by your own.

Thanks for your kinds words and don"t hesitate to help if you like Lekan: https://www.reos.site/en/how-to-support/

@pertetotale
Copy link

sorry to be a bit late:
Did you fill sinks on DEM?
Also I noticed your pic with enlarged slope distance.

But the expr. I got with DEMs of "less interesting locations": there might be area's that are not scanned 3*, only 2*,
so we might miss accurate slopes in certain angles.

Btw, Vincent, I remember an error in a formula which showed in a pop up: exp x -y vs. exp +y, which seemed to me caused by an [latex] ()/{} misplacement, so I hoped it would be correctly implemented and I did not signal it. But I did not look closer in it.

On a good note, I did a Green Ampt run, and it seemed to be even a bit better, but you really need to have decent soil info, (depth, infil, soil mixes, the layers...) and general soil type insight.

Just for your info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Something to add question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants