Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • otb otb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 210
    • Issues 210
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and 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
  • Main Repositories
  • otbotb
  • Merge requests
  • !765

Refactor optical image metadata interface

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Cédric Traizet requested to merge optical_imi into develop Oct 22, 2020
  • Overview 4
  • Commits 21
  • Pipelines 12
  • Changes 31

Summary

Part of #2024 (closed)

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
Reviewers
Request review from
Time tracking
Source branch: optical_imi