Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
otb
otb
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 273
    • Issues 273
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • 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
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Main Repositories
  • otbotb
  • Merge Requests
  • !765

Merged
Opened Oct 22, 2020 by Cédric Traizet@ctraizetDeveloper

Refactor optical image metadata interface

  • Overview 4
  • Commits 21
  • Pipelines 14
  • Changes 31

Summary

Part of #2024

Refactor image metadata interface for optimal sensors. The metadata are now read by gdal instead of ossim. Concerned sensor are :

  • Dimap family :
    • Pléiades
    • Formosat
    • Spot 5
    • Spot 6
  • Digital Globe family :
    • Quickbird
    • Worldview 2
  • GeoEye family
    • Ikonos

The following metadata are parsed:

  • RPC coefficients
  • SensorID
  • SunElevation
  • SunAzimuth
  • SatElevation
  • SatAzimuth
  • AcquisitionDate
  • ProductionDate
  • PhysicalBias for each band
  • PhysicalGain for each band
  • SolarIrradiance for each band
  • SpectralSensitivity for each band

Implementation Details

When possible, metadata are read with GDAL (using the GDALImageIO class, and in particular the GetMetadataValue() method). However in many cases, all the metadata we are interested in are not parsed by GDAL, which means ImageMetadataInterface classes have to read them. Generally, this is done by finding the metadata file associated with the product (using GetRessourceFiles from GDALImageIO). Then the metadata files are parsed (for example using XMLMetadataSupplier, or by parsing the files manually)

Some metadata are not fetched from products and are hardcoded in OTB, for example this the case for Spectral Sensitivity tables.

Copyright

The copyright owner is CNES and has signed the ORFEO ToolBox Contributor License Agreement.


Check before merging:

  • All discussions are resolved
  • At least 2 👍 votes from core developers, no 👎 vote.
  • The feature branch is (reasonably) up-to-date with the base branch
  • Dashboard is green
  • Copyright owner has signed the ORFEO ToolBox Contributor License Agreement
  • Optionally, run git diff develop... -U0 --no-color | clang-format-diff.py -p1 -i on latest changes and commit
Edited Oct 29, 2020 by Cédric Traizet
Assignee
Assign to
Reviewer
Request review from
8.0.0
Milestone
8.0.0
Assign milestone
Time tracking
Reference: orfeotoolbox/otb!765
Source branch: optical_imi

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.