BRouter-like hysteresis filter for imported routes
Gathering feedback
It may be a good idea that to implement an optional Brouter-like 10m hysteresis altitude filter(BRouter final stats, Brouter-web stats) for importing externally planned routes.
It would provide better consistency for route comparison of externally and internally generated BRouter based routes.
I have observed, as a rule of thumb, that raw=Locus route ascend gives about double value(plain start-goal accend subtracted), compared to BRouter filtered ascend.
I like this idea 
Note that it is not intended for altitude data filtering, just the route stats.
And, it may not be implemented to import itself, but can be independent action, applicable to any route.
So one could eventually flip between Locus-like / Brouter-like ascend stats.
Note that it is not intended for altitude data filtering, just the route stats.
And, it may not be implemented to import itself, but can be independent action, applicable to any route.
So one could eventually flip between Locus-like / Brouter-like ascend stats.
Replies have been locked on this page!