Open kantntreiber opened 11 years ago
The route in the example forks at this point, which segments the route into four parts. "forward"/"backward" is not taken into account at all at the moment.
"forward"/"backward" is not taken into account at all at the moment.
That's why I have filed this issue :). If e.g. only members with no role or a "forward" role would be taken into account, the route would not longer fork and an elevation profile could be evaluated.
Thanks a lot for the great project!
There is code in the pipeline to solve this problem in a more general way, i.e. for any possible segmentation of the route, so that you always get a elevation profile. Just need to find a free minute to finish it.
It seems that currently no elevation profile is shown for routes which have a member with a "forward" and "backward" role even if the route has only two end points and doesn't consist of more than one segment (e.g. [1]).
[1] http://www.openstreetmap.org/browse/relation/1423700