Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
otb
otb
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 305
    • Issues 305
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 15
    • Merge Requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Main Repositories
  • otbotb
  • Issues
  • #2161

Closed
Open
Created Feb 26, 2021 by Thibaut ROMAIN@thibromDeveloper

Pleiades : improve input DIMAP support

Description

When a user provides a DIMAP as an input of an OTB application (instead of a jp2/tif), the metadata read by OTB are not correct which leads to issues in the application's output. This is due to GDAL's DIMAP driver not giving the same metadata as the JP2. In OTB 7.x, the dimap metadata reading was done using OSSIM, which has been removed in OTB 8.x

Steps to reproduce

In OTB 8.x , calling OpticalCalibration -in DIM_PHR.XML leads to the following error : Unknown sensor, Additional parameters are necessary, please provide them The same kind of error happens in Orthorectification for example

Configuration information

Reproduced on Ubuntu 18.04, OTB 8.0-alpha

Assignee
Assign to
8.0.0
Milestone
8.0.0
Assign milestone
Time tracking
None
Due date
None