Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • HabitatSampler HabitatSampler
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Habitat Sampler
  • HabitatSamplerHabitatSampler
  • Issues
  • #36

Closed
Open
Created Jun 23, 2021 by Carsten Neumann@carstennOwner

check data type of input image for processing time optimization

I recognized that we use a FLT4S (float 4 byte signed) datatype for our benchmark image. This is absolutely not necessary and decreases processing speed drastically!!! A smart solution would be to always automatically rescale input imagery between 0...10,000. However, it is not easy in the raster/rgdal *.tif environment since values in memory are not affecting datatype when not writing out on disk. Any solution on datatype change on the flow would be cool to speed up processing. Have a look on our benchmark image to see what it means to artificially blow up an integer type to float! I guess it is already considered in the *json approach of the GUI.

Assignee
Assign to
Time tracking