nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Hellingshoogte

AnsuLouw1

<\/HEAD>

Hallo<\/P>

<\/P>

Ik probeer de hoogte van hellingen te bepalen van de daadwerkelijke teen tot de kam, zonder de teen en kam te hoeven digitaliseren. Ik ben niet lui - het interessegebied is groot en het zou erg tijdrovend zijn om dat laatste te doen. In wezen hoop ik dat er een methode is in Spatial Analyst \/ 3D Analyst of een formule die ik kan gebruiken in Raster Calculator.<\/P><\/BODY><\/HTML>

Vind meer berichten getagd met

Mining

Accepted answers

All comments

AnsuLouw1

Dan,

Many thanks for your response. It is much appreciated.

Your questions have got me questioning myself.

I am busy digitizing the crest and the toe as I realized that this will be necessary. I realize i need to calculate the difference in height between the toe and crest; but I don't want to display the actual difference in elevation values between the toe and the crest but rather the length of the slope from the toe (i.e. 0m to e.g. 300m).

Xander has given me a pretty good sense of how to obtain this.

DanPatterson_Retired

I will have a look through Bill's links later, but I do remember him doing something like this and curvature is coming to mind, but don't quote me. Some of my concerns in my original post still haven't be answered as yet even if the surface length is still being sought after. Contour lines would help IFFF they are at least representative of the underlying DEM, you can atleast propagate normal lines etc. I will have a look, just trying to finish up some einsum stuff

XanderBakker

mmm... I think this is the (ancient) thread I was talking about Finding peaks from a DEM where William Huber collaborated.

AnsuLouw1

Hi Xander,

Yes that is correct. I want the actual slope length (perhaps height is not the right wording).

If I were to simplify it and try obtain the length of the "brown line" what would you suggest?

XanderBakker

Hi Ansu Louw ,

I'm afraid I'm a bit lost in the explanation... When you refer to the "actual height of the slope", are you referring to the elevation or the length of the slope?

For what I understand you are not interested in the length of the brown line following the surface, but in the slope length, right? ... and you want to generate contours in a 50 m interval based on the length of the slope... If so, that will probably be a very complicated process and include some heavy coding (even if you would already have lines representing crests and toes)...

XanderBakker

mmm, just wondering... I remember that your friend William Huber did some magic in Avenue to detect crests...

Would it be possible to generalize the aspect of the surface using the SciPy circular mean (scipy.stats.morestats.circmean(numpy_raster)) as Shaun Walbridge showed in his presentation at the DevSummit this year (Python: Working With Scientific Data ) and using a moving window to detect opposite aspect angle ranges to depict crests and toes (won't work with rather flat and wide valleys)?

AnsuLouw1

Hi Xander,

I don't have the toes and crests extracted as yet.

The client wants to see the height of the slope as contours / colour grid ranging from 0m to ± 300m in 50m intervals. The length should be the actual height of the slope and not the values of the surface elevation

DanPatterson_Retired

You will have to digitize the toe and crest since a slope value only applies for a very small 3x3 window so all you could do is figure out the length by considering the slope value and aspect at a cell. This would give you the ability to get an estimate of the surface length for the window...but consider that the slope derived for one cell is not know by its adjacent cells. You task would be to make these cells self-aware.

Consider the following example:

a 500 m line of constant slope denotes the space between the toe and crest
each cell along that line has the same slope value
each cell doesnt what the values of its neighbor
the directional slope is currently not known since you need to determine the slope at various directions from those normal to the slope

So the questions become:

what criteria are you going to use to identify areas of 'constant' slope?
how are you going to identify the toe and crest from these data
how are you going to account for the fact that you could have slope areas with different slope values? (for example, a 25% slope on one side of a v-shaped valley versus 22% across...what if the valley is u-shaped?
once you have identified the areas, how do you ensure that the slope determined, its length and elevations are normal to the direction of the contours?

You can easily do this in your head...can't you? The task becomes translating your 'rules' to those that can be implemented in raster and/or vector world. So some discussion of your criteria, would be useful. Are you only interested in

particular slope, elevation difference values?
do you want to rule out areas where the elevation differences are less that a threshold values regardless of the slope?
etc etc

Interesting problem, there are some things that could be done, but rather than throwing tools at a problem and hoping a solution arises, formulate the required steps to see if the solution is realizable without human intervention.

XanderBakker

Do you already have the crests and toes extracted?

How many of those slope "lines" should be created?

Should the length show the length using the surface or a straight line?

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.