Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spatial range of a rotated field in the file info #1050

Closed
kswang1029 opened this issue Mar 14, 2022 · 0 comments · Fixed by #1067
Closed

spatial range of a rotated field in the file info #1050

kswang1029 opened this issue Mar 14, 2022 · 0 comments · Fixed by #1067
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@kswang1029
Copy link
Contributor

as confirmed with @markccchiang, currently the spatial range of an image cube is derived using the bottom-left (BL) pixel and the top-right (TR) pixel. This works nicely if there is no sky rotation (mostly true with radio image cube). However, for image cubes from optical observations, there might be a non-zero sky rotation. When this happens, using the BL and TR pixels to derive the spatial range is not accurate.

To have a better estimate of the spatial ranges in both ra/dec or lon/lat coordinates, we need to use the four corners of the images to get the world coordinates first. Then from the four ra (or lon) to fine the maximum range. Same applies to dec (or lat).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants