Fixed a numerical issue at tile exit.
The low point at tile minimum elevation was computed with a tiny positive error, meaning the point really was above min elevation (at micrometer level). The line segment between entry and exit stopped just before traversing the Digital Elevation Model, and an error was triggered. The solution was to take some margin when computing the segment endpoints at entry and exit: we now start above max elevation and end below min elevation so the intersection should be really on the line.
Showing
- rugged-core/src/main/java/org/orekit/rugged/core/duvenhage/DuvenhageAlgorithm.java 2 additions, 2 deletions.../org/orekit/rugged/core/duvenhage/DuvenhageAlgorithm.java
- rugged-core/src/test/java/org/orekit/rugged/core/AbstractAlgorithmTest.java 5 additions, 5 deletions...st/java/org/orekit/rugged/core/AbstractAlgorithmTest.java
- rugged-core/src/test/java/org/orekit/rugged/core/duvenhage/DuvenhageAlgorithmTest.java 21 additions, 0 deletions.../orekit/rugged/core/duvenhage/DuvenhageAlgorithmTest.java
Please register or sign in to comment