1. 16 Mar, 2019 1 commit
  2. 07 Mar, 2019 2 commits
  3. 05 Mar, 2019 7 commits
  4. 28 Feb, 2019 3 commits
  5. 27 Feb, 2019 2 commits
  6. 26 Feb, 2019 1 commit
  7. 22 Feb, 2019 2 commits
  8. 21 Feb, 2019 1 commit
  9. 20 Feb, 2019 2 commits
    • Luc Maisonobe's avatar
      Improved robustness of recovery algorithm when refining returns null. · 0efb1aa8
      Luc Maisonobe authored
      Direct location is performed in two phases, with a first intersection
      being computed without corrections, then correction are applied and the
      first solution is "refined". It was expected that the DEM cell did not
      change there. Unfortunately, sometimes the refining did not find a
      result in the same DEM cell. This was a very rare occurrence, and was
      detected first on very ... rugged areas like mountains.
      
      Now, when this rare event is detected, we restart a full-blown
      intersection but starting from a point just after the exit of the
      failing cell, when LOS is still above DEM and we prevent the algorithm
      to find solutions backward (i.e. we prevent it from finding the previous
      solution again and looping infinitely).
      0efb1aa8
    • Guylaine Prat's avatar
      Better management of dumped data in TilesCache when updating the tile · de9daade
      Guylaine Prat authored
      In the updateTile method (to be developed by the user according to the
      kind of raster to be read), it happens that some useless data are
      dumped. For instance, when reading some SRTM data, one needs to read
      also some Geoid data. When reading the Geoid data, the elevations may be
      dumped (if using the SimpleTile.interpolateElevation method).
      de9daade
  10. 19 Feb, 2019 1 commit
  11. 18 Feb, 2019 2 commits
  12. 15 Feb, 2019 2 commits
  13. 14 Feb, 2019 2 commits
  14. 13 Feb, 2019 2 commits
  15. 12 Feb, 2019 3 commits
  16. 11 Feb, 2019 3 commits
  17. 08 Feb, 2019 4 commits