Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • astrotools astrotools
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • astroastro
  • astrotoolsastrotools
  • Issues
  • #53
Closed
Open
Issue created Sep 10, 2019 by Niklas Uwe Langner@niklas.langnerOwner

Weird behaviour of crs['vecs'] if the key doesn't exist

Using crs['vecs'] without the key 'vecs' existing sometimes uses crs['pixels'] to calculate the vectors instead of crs['lon'] and crs['lat'] even though those exist. This might result in undesired outputs if changes to lon and lat were not also applied to pixels.

Assignee
Assign to
Time tracking