Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • arosics arosics
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • 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
  • Daniel Scheffler
  • arosicsarosics
  • Issues
  • #37
Closed
Open
Issue created Aug 27, 2020 by Daniel Scheffler@danschefOwner

Provide full support for projections other than UTM or geographic coordinates.

AROSICS currently provides full support for UTM and geographic coordinates and is also applicable to images without any projection. However, it would be nice to have full support for any other kind of projection.

Currently, the local co-registration fails in case of projected coordinate systems other than UTM as reported here: https://github.com/GFZ/arosics/issues/3

Assignee
Assign to
Time tracking