astropy:docs

Note

This is an old version of the documentation. See http://docs.astropy.org/en/stable for the latest version.

Using and Designing Coordinate Frames

In astropy.coordinates, as outlined in the Overview of astropy.coordinates concepts, subclasses of BaseCoordinateFrame (“frame classes”) define particular coordinate frames. They can (but do not have to) contain representation objects storing the actual coordinate data. The actual coordinate transformations are defined as functions that transform representations between frame classes. This approach serves to separate high-level user functionality (see Using the SkyCoord High-level Class) and details of how the coordinates are actually stored (see Using and Designing Coordinate Representations) from the definition of frames and how they are transformed.

Using Frame Objects

Frames without Data

Frame objects have two distinct (but related) uses. The first is storing the information needed to uniquely define a frame (e.g., equinox, observation time). This information is stored on the frame objects as (read-only) Python attributes, which are set with the object is first created:

>>> from astropy.coordinates import ICRS, FK5
>>> FK5(equinox='J1975')
<FK5 Frame (equinox=J1975.000)>
>>> ICRS()  # has no attributes
<ICRS Frame>
>>> FK5()  # uses default equinox
<FK5 Frame (equinox=J2000.000)>

The specific names of attributes available for a particular frame (and their default values) are available as the class method get_frame_attr_names:

>>> FK5.get_frame_attr_names()
OrderedDict([('equinox', <Time object: scale='utc' format='jyear_str' value=J2000.000>)])

You can access any of the attributes on a frame by using standard Python attribute access. Note that for cases like equinox, which are time inputs, if you pass in any unambiguous time string, it will be converted into an Time object with UTC scale (see Inferring input format):

>>> f = FK5(equinox='J1975')
>>> f.equinox
<Time object: scale='utc' format='jyear_str' value=J1975.000>
>>> f = FK5(equinox='2011-05-15T12:13:14')
>>> f.equinox
<Time object: scale='utc' format='isot' value=2011-05-15T12:13:14.000>

Frames with Data

The second use for frame objects is to store actual realized coordinate data for frames like those described above. In this use, it is similar to the SkyCoord class, and in fact, the SkyCoord class internally uses the frame classes as its implementation. However, the frame classes have fewer “convenience” features, thereby keeping the implementation of frame classes simple. As such, they are created similarly to SkyCoord object. The simplest way is to use with keywords appropriate for the frame (e.g. ra and dec for equatorial systems):

>>> from astropy import units as u
>>> ICRS(ra=1.1*u.deg, dec=2.2*u.deg)
<ICRS Coordinate: (ra, dec) in deg
    (1.1, 2.2)>
>>> FK5(ra=1.1*u.deg, dec=2.2*u.deg, equinox='J1975')
<FK5 Coordinate (equinox=J1975.000): (ra, dec) in deg
    (1.1, 2.2)>

These same attributes can be used to access the data in the frames, as Angle objects (or Angle subclasses):

>>> coo = ICRS(ra=1.1*u.deg, dec=2.2*u.deg)
>>> coo.ra  
<Longitude 1.1 deg>
>>> coo.ra.value  
1.1
>>> coo.ra.to(u.hourangle)  
<Longitude 0.07333333333333335 hourangle>

You can use the representation attribute in conjunction with the representation_component_names attribute to figure out what keywords are accepted by a particular class object. The former will be the representation class the system is expressed in (e.g., spherical for equatorial frames), and the latter will be a dictionary mapping names for that frame to the attribute name on the representation class:

>>> import astropy.units as u
>>> icrs = ICRS(1*u.deg, 2*u.deg)
>>> icrs.representation
<class 'astropy.coordinates.representation.SphericalRepresentation'>
>>> icrs.representation_component_names
OrderedDict([(u'ra', u'lon'), (u'dec', u'lat'), (u'distance', u'distance')])

The representation of the coordinate object can be changed, as shown below. This actually does nothing to the object internal data which stores the coordinate values, but it changes the external view of that data in two ways: (1) the object prints itself in accord with the new representation, and (2) the available attributes change to match those of the new representation (e.g. from ra, dec, distance to x, y, z). Setting the representation thus changes a property of the object (how it appears) without changing the intrinsic object itself which represents a point in 3d space.

>>> from astropy.coordinates import CartesianRepresentation
>>> icrs.representation = CartesianRepresentation
>>> icrs  
<ICRS Coordinate: (x, y, z) [dimensionless]
    (0.999238614955, 0.0174417749028, 0.0348994967025)>
>>> icrs.x  
<Quantity 0.9992386149554826>

The representation can also be set at the time of creating a coordinate and affects the set of keywords used to supply the coordinate data. For example to create a coordinate with cartesian data do:

>>> ICRS(x=1*u.kpc, y=2*u.kpc, z=3*u.kpc, representation=CartesianRepresentation)
<ICRS Coordinate: (x, y, z) in kpc
    (1.0, 2.0, 3.0)>

For more information about the use of representations in coordinates see the Representations section, and for details about the representations themselves see Using and Designing Coordinate Representations.

There are two other ways to create frame classes with coordinates. A representation class can be passed in directly at creation, along with any frame attributes required:

>>> from astropy.coordinates import SphericalRepresentation
>>> rep = SphericalRepresentation(lon=1.1*u.deg, lat=2.2*u.deg, distance=3.3*u.kpc)
>>> FK5(rep, equinox='J1975')
<FK5 Coordinate (equinox=J1975.000): (ra, dec, distance) in (deg, deg, kpc)
    (1.1, 2.2, 3.3)>

A final way is to create a frame object from an already existing frame (either one with or without data), using the realize_frame method. This will yield a frame with the same attributes, but new data:

>>> f1 = FK5(equinox='J1975')
>>> f1
<FK5 Frame (equinox=J1975.000)>
>>> rep = SphericalRepresentation(lon=1.1*u.deg, lat=2.2*u.deg, distance=3.3*u.kpc)
>>> f1.realize_frame(rep)
<FK5 Coordinate (equinox=J1975.000): (ra, dec, distance) in (deg, deg, kpc)
    (1.1, 2.2, 3.3)>

You can check if a frame object has data using the has_data attribute, and if it is preset, it can be accessed from the data attribute:

>>> ICRS().has_data
False
>>> cooi = ICRS(ra=1.1*u.deg, dec=2.2*u.deg)
>>> cooi.has_data
True
>>> cooi.data
<UnitSphericalRepresentation (lon, lat) in deg
    (1.1, 2.2)>

All of the above methods can also accept array data (or other Python sequences) to create arrays of coordinates:

>>> ICRS(ra=[1.5, 2.5]*u.deg, dec=[3.5, 4.5]*u.deg)
<ICRS Coordinate: (ra, dec) in deg
    [(1.5, 3.5), (2.5, 4.5)]>

If you pass in mixed arrays and scalars, the arrays will be broadcast over the scalars appropriately:

>>> ICRS(ra=[1.5, 2.5]*u.deg, dec=[3.5, 4.5]*u.deg, distance=5*u.kpc)
<ICRS Coordinate: (ra, dec, distance) in (deg, deg, kpc)
    [(1.5, 3.5, 5.0), (2.5, 4.5, 5.0)]>

An additional operation that may be useful is the ability to extract the data in different representations. E.g., to get the Cartesian form of an ICRS coordinate:

>>> from astropy.coordinates import CartesianRepresentation
>>> cooi = ICRS(ra=0*u.deg, dec=45*u.deg, distance=10*u.pc)
>>> cooi.represent_as(CartesianRepresentation)  
<CartesianRepresentation (x, y, z) in pc
    (7.07106781187, 0.0, 7.07106781187)>

Transforming between Frames

To transform a frame object with data into another frame, use the transform_to method of an object, and provide it the frame you wish to transform to. This frame can either be a frame class, in which case the default attributes will be used, or a frame object (with or without data):

>>> cooi = ICRS(1.5*u.deg, 2.5*u.deg)
>>> cooi.transform_to(FK5)  
<FK5 Coordinate (equinox=J2000.000): (ra, dec) in deg
    (1.50000660527, 2.50000238221)>
>>> cooi.transform_to(FK5(equinox='J1975'))  
<FK5 Coordinate (equinox=J1975.000): (ra, dec) in deg
    (1.17960348105, 2.36085320826)>

The Reference/API includes a list of all of the frames built into astropy.coordinates, as well as the defined transformations between them. Any transformation that has a valid path, even if it passes through other frames, can be transformed to. To programmatically check for or manipulate transformations, see the TransformGraph documentation.

Defining a New Frame

Users can add new coordinate frames by creating new classes that are subclasses of BaseCoordinateFrame. Detailed instructions for subclassing are in the docstrings for that class. The key aspects are to define the class attributes default_representation and frame_specific_representation_info along with frame attributes as FrameAttribute class instances (or subclasses like TimeFrameAttribute). If these are defined, there is often no need to define an __init__ function, as the initializer in BaseCoordinateFrame will probably behave the way you want. As an example:

>>> from astropy.coordinates import BaseCoordinateFrame, FrameAttribute, TimeFrameAttribute, RepresentationMapping
>>> class MyFrame(BaseCoordinateFrame):
...     # Specify how coordinate values are represented when outputted
...      default_representation = SphericalRepresentation
...
...      # Specify overrides to the default names and units for all available
...      # representations (subclasses of BaseRepresentation).
...      frame_specific_representation_info = {
...          'spherical': [RepresentationMapping(reprname='lon', framename='R', defaultunit=u.rad),
...                        RepresentationMapping(reprname='lat', framename='D', defaultunit=u.rad),
...                        RepresentationMapping(reprname='distance', framename='DIST', defaultunit=None)],
...          'unitspherical': [RepresentationMapping(reprname='lon', framename='R', defaultunit=u.rad),
...                            RepresentationMapping(reprname='lat', framename='D', defaultunit=u.rad)],
...          'cartesian': [RepresentationMapping(reprname='x', framename='X'),
...                        RepresentationMapping(reprname='y', framename='Y'),
...                        RepresentationMapping(reprname='z', framename='Z')]
...      }
...
...      # Specify frame attributes required to fully specify the frame
...      location = FrameAttribute(default=None)
...      equinox = TimeFrameAttribute(default='B1950')
...      obstime = TimeFrameAttribute(default=None, secondary_attribute='equinox')

>>> c = MyFrame(R=10*u.deg, D=20*u.deg)
>>> c  
<MyFrame Coordinate (location=None, equinox=B1950.000, obstime=B1950.000): (R, D) in rad
    (0.174532925199, 0.349065850399)>
>>> c.equinox
<Time object: scale='utc' format='byear_str' value=B1950.000>

You can also define arbitrary methods for any added functionality you want your frame to have that’s unique to that frame. These methods will be available in any SkyCoord that is created using your user-defined frame.

For examples of defining frame classes, the first place to look is probably the source code for the frames that are included in astropy (available at astropy.coordinates.builtin_frames). These are not “magic” in any way, and use all the same API and features available to user-created frames. A more annotated example is also available in the Example: Defining A Coordinate Frame for the Sgr Dwarf documentation section.

Defining Transformations

A frame may not be too useful without a way to transform coordinates defined in it to or from other frames. Fortunately, astropy.coordinates provides a framework to do just that. The key concept for these transformations is the frame transform graph, available as astropy.coordinates.frame_transform_graph, an instance of the TransformGraph class. This graph (in the “graph theory” sense, not “plot”), stores all the transformations between all of the builtin frames, as well as tools for finding shortest paths through this graph to transform from any frame to any other. All of the power of this graph is available to user-created frames, meaning that once you define even one transform from your frame to some frame in the graph, coordinates defined in your frame can be transformed to any other frame in the graph.

The transforms themselves are represented as CoordinateTransform objects or their subclasses. The useful subclasses/types of transformations are:

  • FunctionTransform

    A transform that is defined as a function that takes a frame object of one frame class and returns an object of another class.

  • StaticMatrixTransform

  • DynamicMatrixTransform

    These are both for transformations defined as a 3x3 matrix transforming the Cartesian representation of one frame into the target frame’s Cartesian representation. The static version is for the case where the matrix is independent of the frame attributes (e.g., the ICRS->FK5 transformation, because ICRS has no frame attributes). The dynamic case is for transformations where the transformation matrix depends on the frame attributes of either the to or from frame.

Generally, it is not necessary to use these classes directly. Instead, use methods on frame_transform_graph that can be used as function decorators. Then just define functions that either do the actual transformation (for FunctionTransform), or that compute the necessary transformation matrices to transform. Then decorate the functions to register these transformations with the frame transform graph:

from astropy.coordinates import frame_transform_graph

@frame_transform_graph.transform(DynamicMatrixTransform, ICRS, FK5)
def icrs_to_fk5(icrscoord, fk5frame):
    ...

@frame_transform_graph.transform(DynamicMatrixTransform, FK5, ICRS)
def fk5_to_icrs(fk5coord, icrsframe):
    ...

If the transformation to your coordinate frame of interest is not representable by a matrix operation, you can also specify a function to do the actual transformation, and pass the FunctionTransform class to the transform graph decorator instead:

@frame_transform_graph.transform(FunctionTransform, FK4NoETerms, FK4)
def fk4_no_e_to_fk4(fk4noecoord, fk4frame):
    ...

Furthermore, the frame_transform_graph does some caching and optimization to speed up transformations after the first attempt to go from one frame to another, and shortcuts steps where relevant (for example, combining multiple static matrix transforms into a single matrix). Hence, in general, it is better to define whatever are the most natural transformations for a user-defined frame, rather than worrying about optimizing or caching a transformation to speed up the process.