To get a better mean of the values metadata for a point is calculated by selecting the points +- 25 m form that point. Only if a point far enough is found the variables to derive all secondary data are set. For some points in the middle no other point has a distance of 25m. Therefor both points are the same resulting in an invalid slope.
Solution: If no point is 25m away use the one that is most far.
Steps to perform a simple smoke test:
Use the track from the ticket
Does the code comply to the coding rules and naming conventions Coding Guidelines:
[x] yes
Is every user facing string in a tr() macro?
[x] yes
Did you add the ticket number and title into the changelog? Keep the numeric order in each release block.
What is the linked issue for this pull request:
QMS-#692
What you have done:
To get a better mean of the values metadata for a point is calculated by selecting the points +- 25 m form that point. Only if a point far enough is found the variables to derive all secondary data are set. For some points in the middle no other point has a distance of 25m. Therefor both points are the same resulting in an invalid slope.
Solution: If no point is 25m away use the one that is most far.
Steps to perform a simple smoke test:
Use the track from the ticket
Does the code comply to the coding rules and naming conventions Coding Guidelines:
Is every user facing string in a tr() macro?
Did you add the ticket number and title into the changelog? Keep the numeric order in each release block.