Ascent, descent, and elevation not consistent when planning different routes between same start and end

[bevoorrading]

When making a route between two points, the elevation difference often does not remain the same when adding a via point.

Steps to reproduce:

1. Go to openrouteservice.org
2. Select start and end point for route
3. Look at nett ascent, i.e., Ascent - Descent
4. If for pedestrian, look at elevation of end point
5. Add a via point somewhere
6. Look at nett ascent of new route. This often turns out to be different from the one in 3.
7. If for pedestrian, look at elevation of end point. Also often different from the one in 4.

Examples:
For pedestrian
Simple A-B route
With a via point
In the first case the nett ascent is 75m-79m = -4m, and in the second it is 72m-59m = 13m.
The elevation of the end point is in the first case 294.5m, and in the second it is 303.8m.

For car
Simple A-B route
With via point
In the first case the nett ascent is 62m, and in the second case it is 148m-92m = 56m.

[TimMcCauley]

thanks for sharing @bevoorrading we are investigating!

[TimMcCauley]

The reason for this mismatch is the quite low resolution of SRTM data. The result origins from smoothing and snapping the data. Nothing we can do at this point. Considering this issue as resolved.