You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I create a grid of (x, y) points in pixel coords in my image, and get the output (ra, dec) in sky coordinates to which they map.
But the wcs.footprint() method works like the following:
ra, dec=wcs.footprint().T
I.e. the ordering of the return values from the footprint() method is the transpose of that from the forward and reverse transforms. And also it is a single numpy array, instead of a tuple of arrays as in the former.
The text was updated successfully, but these errors were encountered:
So this isn't a bug, but more of a user interface inconsistency.
For a simple imaging WCS, I might create and call it like so:
So I create a grid of
(x, y)
points in pixel coords in my image, and get the output(ra, dec)
in sky coordinates to which they map.But the
wcs.footprint()
method works like the following:I.e. the ordering of the return values from the
footprint()
method is the transpose of that from the forward and reverse transforms. And also it is a single numpy array, instead of a tuple of arrays as in the former.The text was updated successfully, but these errors were encountered: