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
  • #2119

Closed
Open
Created Nov 02, 2020 by Guillaume Pasero@gpaseroOwner

Support otb::Image writers in OutpuImageParameter

It would be nice if the applications could use otb::Image writers (in addition to otb::VectorImage writers). When the application produces an otb::Image<T,2> , and the output pixel type corresponds to T, we can therefore avoid the double cast filters, and save some RAM space.

I know that applications using otb::Image internally is not generic, but it gives more performances in some projects outside OTB.

The implementation is not difficult:

  • separate macros CAST_IMAGE_BASE and CAST_VECTOR_IMAGE_BASE
  • separate functions SwitchInput and SwitchVectorInput
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None