As indicated in Fig. 1, the first step in transforming (x,y)coordinates in the plane of projection to celestial coordinates is to convert
them to native longitude and latitude,
.
The equations for the
transformation depend on the particular projection and this will be specified
via the CTYPE ia keyword. Paper I defined "4-3'' form for such purposes;
the rightmost three-characters are used as an algorithm code that in
this paper will specify the projection. For example, the stereographic
projection will be coded as STG. Some projections require additional
parameters that will be specified by the FITS keywords PV i_ma for
,
also introduced in Paper I. These parameters may be
associated with the longitude and/or latitude coordinate as specified for each
projection. However, definition of the three-letter codes for the projections
and the equations, their inverses and the parameters which define them, form a
large part of this work and will be discussed in Sect. 5.
The leftmost four characters of CTYPE ia are used to identify the celestial
coordinate system and will be discussed in Sect. 3.
The last step in the chain of transformations shown in Fig. 1
is the spherical rotation from native coordinates,
,
to
celestial
coordinates
.
Since a spherical rotation is completely specified by three Euler angles it
remains only to define them.
In principle, specifying the celestial coordinates of any particular native
coordinate pair provides two of the Euler angles (either directly or
indirectly). In the AIPS convention, the CRVAL ia keyword values for the
celestial axes specify the celestial
coordinates of the reference point and this in turn is associated with a
particular point on the projection. For zenithal projections that point is
the sphere's point of tangency to the plane of projection and this is the pole
of the native coordinate system. Thus the AIPS convention links a celestial
coordinate pair to a native coordinate pair via the reference point. Note
that this association via the reference point is purely conventional; it has
benefits which are discussed in Sect. 5 but in principle
any other point could have been chosen.
Section 5 presents the projection equations for the
transformation of (x,y) to
.
The native coordinates of the
reference point would therefore be those obtained for
(x,y) = (0,0).
However, it may happen that this point lies outside the boundary of the
projection, for example as for the ZPN projection of
Sect. 5.1.7. Therefore, while this work follows the AIPS approach it
must of necessity generalize it.
Variable(s) | Meaning | Related FITS keywords (if any) |
i | Index variable for world coordinates | |
j | Index variable for pixel coordinates | |
a | Alternate version code, blank or A to Z | |
pj | Pixel coordinates | |
rj | Reference pixel coordinates | CRPIX ja |
mij | Linear transformation matrix | CD i_ja or PC i_ja |
si | Coordinate scales | CDELT ia |
xi | Intermediate world coordinates (in general) | |
(x,y) | Projection plane coordinates | |
![]() |
Native longitude and latitude | |
![]() |
Celestial longitude and latitude | |
![]() |
Native longitude and latitude of the fiducial point | PV i_1a![]() ![]() |
![]() |
Celestial longitude and latitude of the fiducial point | CRVAL ia |
![]() |
Native longitude and latitude of the celestial pole | LONPOLE a ( = PV i_3a![]() ![]() |
![]() |
Celestial longitude and latitude of the native pole
![]() |
|
![]() |
Inverse tangent function that returns the correct quadrant |
Accordingly we specify only that a fiducial celestial coordinate pair
given by the CRVAL ia will be associated with a
fiducial native coordinate pair
defined explicitly for
each projection. For example, zenithal projections all have
,
while cylindricals have
.
The AIPS convention has been honored here as far as practicable by
constructing the projection equations so that
transforms
to the reference point,
(x,y) = (0,0). Thus, apart from the one exception
noted, the fiducial celestial and native coordinates are the celestial and
native coordinates of the reference point and we will not normally draw a
distinction.
It is important to understand why
differs for different
projection types. There are two main reasons; the first makes it difficult
for it to be the same, while the second makes it desirable that it differs.
Of the former, some projections such as Mercator's, diverge at the native
pole, therefore they cannot have the reference point there because that would
imply infinite values for CRPIX ja. On the other hand, the gnomonic
projection diverges at the equator so it can't have the reference point there
for the same reason. Possibly
chosen at some mid-latitude
could satisfy all projections, but that leads us to the second reason.
Different projection types are best suited to different purposes. For example, zenithal projections are best for mapping the region in the vicinity of a point, often a pole; cylindrical projections are appropriate for the neighborhood of a great circle, usually an equator; and the conics are suitable for small circles such as parallels of latitude. Thus, it would be awkward if a cylindrical used to map, say, a few degrees on either side of the galactic plane, had its reference point, and thus CRPIX ja and CRVAL ia, at the native pole, way outside the map boundary. In formulating the projection equations themselves the native coordinate system is chosen to simplify the geometry as much as possible. For the zenithals the natural formulation has (x,y) = (0,0) at the native pole, whereas for the cylindricals the equations are simplest if (x,y) = (0,0) at a point on the equator.
As discussed above, a third Euler angle must be specified and this will be
given by the native longitude of the celestial pole,
,
specified
by the new FITS keyword
LONPOLE a (floating-valued). |
The default value of LONPOLE a will be 0 for
or
for
.
This is the condition for the celestial
latitude to increase in the same direction as the native latitude at the
reference point. Thus, for example, in zenithal projections the default is
always
(unless
)
since
.
In cylindrical projections, where
,
the default value for
LONPOLE a is 0 for
,
but it is
for
.
Since
differs for different projections it is apparent
that the relationship between
and the required Euler
angles also differs.
For zenithal projections,
so the CRVAL ia
specify the celestial coordinates of the native pole,
i.e.
.
There is a
simple relationship between the Euler angles for consecutive rotations about
the Z-, X-, and Z-axes and
,
and
;
the ZXZ Euler angles are
.
Given this close correspondence it is convenient to
write the Euler angle transformation formulæ directly in terms of
,
and
:
Projections such as the cylindricals and conics for which
are handled by providing formulae to
compute
from
whence the
above equations may be used.
Given that
are the celestial coordinates of the point
with native coordinates
,
Eqs. (6) and
(7) may be inverted to obtain
Note, however, that if
,
as is usual, then when LONPOLE a
(
)
takes its default value of 0 or
(depending on
)
then any combination of
and
produces a valid argument to the
in
Eq. (8), and at least one of the solutions is valid.
LATPOLE a (floating-valued) |
is chosen. It is acceptable to set LATPOLE a to a number greater than
to choose the northerly solution (the default if LATPOLE a is
omitted), or a number less than
to select the southern solution.
These rules governing the application of Eqs. (8-10) are certainly the most complex of
this formalism. FITS writers are well advised to check the values of
,
,
,
,
and
against
them to ensure their validity.
In Sect. 2.2 we formally decoupled
from
the reference point and associated it with
.
One
implication of this is that it should be possible to allow
to be user-specifiable. This may be useful in some circumstances, mainly to
allow CRVAL ia to match a point of interest rather than some predefined
point which may lie well outside the image and be of no particular interest.
We therefore reserve keywords PV i_1a and PV i_2a attached to longitude
coordinate i to specify
and
respectively.
By itself, this prescription discards the AIPS convention and lacks utility
because it breaks the connection between CRVAL ia and any point whose pixel
coordinates are given in the FITS header. New keywords could be invented to
define these pixel coordinates but this would introduce additional complexity
and still not satisfy the AIPS convention. The solution adopted here is to
provide an option to force
(x,y) = (0,0) at
by
introducing an implied offset (x0,y0) which is computed for
from the relevant projection equations given in
Sect. 5. This is to be applied to the (x,y) coordinates
when converting to or from pixel coordinates. The operation is controlled by
the value of PV i_0a attached to longitude coordinate i; the offset
is to be applied only when this differs from its default value of zero.
This construct should be considered advanced usage, of which Figs. 33 and 34 provide an example. Normally we expect that PV i_1a and PV i_2a will either be omitted or set to the projection-specific defaults given in Sect. 5.
So that all required transformation parameters can be contained completely within the recognized world coordinate system (WCS) header cards, the values of LONPOLE a and LATPOLE a may be recorded as PV i_3a and PV i_4a, attached to longitude coordinate i, and these take precedence where a conflict arises.
We recommend that FITS writers include the PV i_1a, PV i_2a, PV i_3a, and PV i_4a cards in the header, even if only to denote the correct use of the default values.
Note carefully that these are associated with the longitude coordinate, whereas the projection parameters defined later are all associated with the latitude coordinate.
![]() |
Figure 2:
A linear equatorial coordinate system (top) defined via the
methods of Wells et al. (1981), and the corresponding oblique
system constructed using the methods of this paper. The reference
coordinate
![]() ![]() ![]() ![]() |
A change of coordinate system may be effected in a straightforward way if the
transformation from the original system,
,
to the new system,
,
and its inverse are known. The new coordinates of the
,
namely
,
are obtained simply by
transforming
.
To obtain
,
first transform
the coordinates of the pole of the new system to the original celestial system
and then transform the result to native coordinates via Eq. (5)
to obtain
.
As a check, compute
via Eq. (8) and verify that
.
It must be stressed that the coordinate transformation described here differs
from the linear transformation defined by Wells et al. (1981) even
for some simple projections where at first glance they may appear to be the
same. Consider the plate carrée projection defined in Sect. 5.2.3
with ,
and illustrated in Fig. 18.
Figure 1 shows that while the transformation from (x,y) to
may be linear (in fact identical), there still remains the
non-linear transformation from
to
.
Hence
the linear coordinate description defined by the unqualified CTYPE ia pair
of RA, DEC which uses the Wells et al. prescription will
generally differ from that of RA--CAR, DEC--CAR with the
same CRVAL ia, etc. If LONPOLE a assumes its default value then they
will agree to first order at points near the reference point but gradually
diverge at points away from it.
Figure 2 illustrates this point for a plate carrée
projection with reference coordinates of
right ascension and
declination and with
.
It is evident that since
the plate carrée has
,
a non-oblique graticule
may only be obtained by setting
with
.
It
should also be noted that where a larger map is to be composed of tiled
submaps the coordinate description of a submap should only differ in the value
of its reference pixel coordinate.
Copyright ESO 2002