Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D diapotb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Remote Modules
  • diapotb
  • Issues
  • #21
Closed
Open
Created Dec 01, 2021 by Gaëlle USSEGLIO@ussegliogMaintainer

ossimGeoidEgm96 in SARDEMProjection

A ossimGeoidEgm96 is used instead of DEMHandler in SARDEMProjection.

This purpose was to improve performance, only. When a emg96 is provided, results between ossimGeoidEgm96 and DEMHandler are equal (cf : otbSARGeoidProjectionTest)

On HAL (a whole g2019 node), we have :

  • S4Reunion (diapOTB.py) : 15min for ossimGeoidEgm96 vs 16min30s for DEMHandler
  • IW_IRAN (burst 3-4 with SARMultiSlc_S1IW.py) : 9min30s for ossimGeoidEgm96 vs 16m51.229s

S1IW calls SARDEMProjection for each burst => a higher impact on performance.

Results are equivalent.

Edited Dec 02, 2021 by Gaëlle USSEGLIO
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking