|
|
International Virtual Observatory Alliance |
Space-Time Coordinate (STC) Metadata Model
Version 1.31
IVOA Note 5 December 2007
This version:
http://www.ivoa.net/Documents/Notes/STC/STC-Model-20071205.html
Latest version:
http://www.ivoa.net/Documents/latest/STC-Model.html
Previous version(s):
http://www.ivoa.net/Documents/Notes/STC/STC-Model-20071030.html
Author(s):
A. H. Rots
This document provides a summary of the model for the description of the VO Space-Time Coordinate metadata. It shows the hierarchical relation between the various components with brief descriptions where needed. The Tables that are referred to may be found in the STC document. XML element names are shown in bold Courier font.
The objective is to provide a framework that allows a complete and internally consistent specification of coordinate metadata – primarily the intertwined temporal, spatial, spectral, and redshift coordinates – that is extensible to accommodate all future applications.
This is a Note. The first release of this document was 2007-12-05.
This is an IVOA Note expressing suggestions from and opinions of the authors. It is intended to share best practices, possible approaches, or other perspectives on interoperability with the Virtual Observatory. It should not be referenced or otherwise interpreted as a standard specification.
A list of current IVOA Recommendations and other technical documents can be found at http://www.ivoa.net/Documents/.
Table of Contents
1.1 Coordinate System (CoordSys, AstroCoordSystem, PixelCoordSystem)
1.1.1 Generic Coordinate Frame (CoordFrame)
1.1.1.1 Reference Position (CoordRefPos)
1.1.1.2 Generic Coordinate Reference Frame (CoordRefFrame)
1.1.1.3 Coordinate Flavor (CoordFlavor)
1.1.2.1 Reference Position (ReferencePosition)
1.1.2.1.1 Standard Reference Position
1.1.2.1.1.1 Planetary Ephemeris (PlanetaryEphem; conditional)
1.1.2.1.2 Custom Reference Position (CoordRefPos)
1.1.2.3 Time Reference Direction (TimeRefDirection; conditional)
1.1.3 Space Frame (SpaceFrame)
1.1.3.1 Reference Position (ReferencePosition)
1.1.3.1.1 Standard Reference Position
1.1.3.1.1.1 Planetary Ephemeris (PlanetaryEphem; conditional)
1.1.3.1.2 Custom Reference Position (CoordRefPos)
1.1.3.2.1 Standard Reference Frame
1.1.3.2.1.1 Equinox (conditional)
1.1.3.2.2 (Custom) Coordinate Reference Frame (CoordRefFrame)
1.1.3.3 Coordinate Flavor (CoordFlavor)
1.1.3.4 Offset Center (OffsetCenter; optional)
1.1.4 Spectral Frame (SpectralFrame)
1.1.4.1.1 Standard Reference Position
1.1.4.1.1.1 Planetary Ephemeris (PlanetaryEphem; conditional)
1.1.4.1.2 Custom Reference Position (CoordRefPos)
1.1.5 Redshift Frame (RedshiftFrame)
1.1.5.1.1 Standard Reference Position
1.1.5.1.1.1 Planetary Ephemeris (PlanetaryEphem; conditional)
1.1.5.1.2 Custom Reference Position (CoordRefPos)
1.1.5.2 Doppler Definition (DopplerDefinition)
1.1.6 Pixel Frame (PixelFrame)
1.1.6.1 Reference Position (CoordRefPos)
1.1.6.2 Coordinate Reference Frame (CoordRefFrame)
1.1.6.3 Coordinate Flavor (CoordFlavor)
1.1.6.4 Reference Pixel (ReferencePixel)
1.2 Coordinates (Coords, AstroCoords, PixelCoords)
1.2.1 Generic Coordinate (GenCoordinate)
1.2.2.1 Absolute Time (AbsoluteTime)
1.2.2.2 Time Offset (TimeOffset; optional)
1.2.3 Spatial Position (Position)
1.2.4 Spatial Velocity (Velocity)
1.2.5 Orbital Elements (Orbit; alternative)
1.2.5.1 Semi-major axis (a; conditional)
1.2.5.2 Periapsis Distance (q; conditional)
1.2.5.5 Longitude of Ascending Node (Node)
1.2.5.6 Argument of Periapsis (Aop)
1.2.5.7 Mean Anomaly (M; optional)
1.2.5.8 Orbital Period (P; optional)
1.2.6 Spectral Coordinate (Spectral)
1.2.7 Redshift Coordinate (Redshift)
1.2.8 Coordinate File (CoordFile)
1.2.8.3 FITSPosition (optional)
1.2.8.4 FITSVelocity (optional)
1.2.8.5 FITSSpectral (optional)
1.2.8.6 FITSRedshift (optional)
1.2.9 Pixel Coordinate (Pixel)
1.3 Coordinate Area (CoordArea, AstroCoordArea, PixelCoordArea)
1.3.1 Generic Scalar Range (CoordInterval)
1.3.2 Time Interval (TimeInterval)
1.3.3 Spatial Area (PositionInterval)
1.3.3.1 1-Dimensional Intervals (PositionScalarInterval)
1.3.3.2 2-Dimensional Rectangles (Coord2VecInterval)
1.3.3.4 3-Dimensional Intervals (Coord3VecInterval)
1.3.3.5 3-Dimensional Sphere (Sphere)
1.3.4.1 1-Dimensional Intervals (VelicityScalarInterval)
1.3.4.2 2-Dimensional Rectangles (Velocity2VecInterval)
1.3.4.3 3-Dimensional Intervals (Velocity3VecInterval)
1.3.4.4 3-Dimensional Sphere (VelocitySphere)
1.3.5 Spectral Interval (SpectralInterval)
1.3.6 Redshift Interval (RedshiftInterval)
1.3.7 Pixel Interval (PixelCoordInterval)
1.3.7.1 PixelCoordScalarInterval
1.3.7.2 PixelCoord2VecInterval
1.3.7.3 PixelCoord3VecInterval
3.2.1 Resource Profile (STCResourceProfile)
3.2.3 Catalog Data (CatalogEntryLocation)
3.2.4 Observational Data (ObsDataLocation)
An STC metadata description element consists of three components:
3. Coordinate area
Missing components or subcomponents shall be considered UNKNOWN; this is to be interpreted as: it is up to the client to decide whether or not to accept the metadata, and to assign a sensible default value if the component is relevant.
A Coordinate System consists of one or more Coordinate Frames.
A Coordinate Frame typically consists of a Reference Frame (orientation) and a Reference Position (or Origin), but some Frames contain more, or less, information. There are six kinds of Frames.
The three kinds of Coordinate System are:
Allows specifying metadata for non-STC coordinates.
A CoordFrame contains a Coordinate Flavor and may contain a Coordinate Reference Frame and/or a Coordinate Reference Position; it requires a frame_id.
A CoordRefPos consists of a Coordinate.
There are four types of Coordinate Reference Frame:
(All Transformation elements contain a projection attribute, using values from Table 4)
Contains:
Contains one of:
Contains one of:
Contains:
CARTESIAN, SPHERICAL, UNITSPHERE, POLAR, CYLINDRICAL, HEALPIX, or STRING; contains: dimensionality.
A TimeFrame contains a Reference Position and a Time Scale, and may contain a Time Reference Direction.
A Reference Position may be a Standard or a Custom one:
TOPOCENTER, GEOCENTER, BARYCENTER, etc., as in Table 1, noting the exceptions.
All Solar System positions, except GEOCENTER, should include a Planetary Ephemeris.
JPL-DE200 or JPL-DE405; needed when such am ephemeris is used to transform times.
A Coordinate Reference Position consists of a Coordinate.
TT (TDT), ET, TAI (IAT), UTC, GPS, TDB (TEB), TCG, TCB, LST, LOCAL (Table 2).
If Time Reference Position is not TOPOCENTER, this direction (a Coordinate element) needs to be provided.
A SpaceFrame includes a Reference Position, Spatial Reference Frame, and Coordinate Flavor, and may include an Offset Center.
A Reference Position may be a Standard or a Custom one:
TOPOCENTER, GEOCENTER, BARYCENTER, etc., as in Table 1, noting the exceptions (but including RELOCATABLE).
All Solar System positions, except GEOCENTER, should include a Planetary Ephemeris.
JPL-DE200 or JPL-DE405; needed when such an ephemeris is used to transform times.
A Coordinate Reference Position consists of a Coordinate.
A Space Reference Frame may be a Standard or a Custom one:
FK4, FK5, ICRS, ECLIPTIC, GALACTIC, etc., as in Table 3, including UNKNOWNFrame.
Bnnnn or Jnnnn, for FKi only
There are four types of Coordinate Reference Frame:
(All Transformation elements contain a projection attribute, using values from Table 4)
Contains:
Contains one of:
Contains one of:
Contains:
CARTESIAN, SPHERICAL, UNITSPHERE, POLAR, CYLINDRICAL, or HEALPIX; contains: dimensionality.
For offset coordinates; consists of a Coordinate.
A SpectralFrame only contains a Reference Position
Note that the Spectral Reference Position requires position as well as a velocity vector. A Reference Position may be a Standard or a Custom one:
TOPOCENTER, GEOCENTER, BARYCENTER, etc., as in Table 1, noting the exceptions (but including LSRx).
All Solar System positions, except GEOCENTER, should include a Planetary Ephemeris.
JPL-DE200 or JPL-DE405; needed when such am ephemeris is used to transform times.
A Coordinate Reference Position consists of a Coordinate.
A RedshiftFrame contains a Reference Position and a Doppler Definition.
It also contains an attribute that indicates whether the coordinate values represent redshifts or Doppler velocities.
Note that the Redshift Reference Position also requires position as well as a velocity vector. A Reference Position may be a Standard or a Custom one:
TOPOCENTER, GEOCENTER, BARYCENTER, etc., as in Table 1, noting the exceptions (but including LSRx).
All Solar System positions, except GEOCENTER, should include a Planetary Ephemeris.
JPL-DE200 or JPL-DE405; needed when such am ephemeris is used to transform times.
A Coordinate Reference Position consists of a Coordinate.
Allowed values: OPTICAL, RADIO, RELATIVISTIC.
A PixelFrame contains a Coordinate Flavor and may contain a Coordinate Reference Frame, a Coordinate Reference Position, and/or a Reference Pixel. It contains one or more axis_order attributes.
A CoordRefPos consists of a Coordinate.
There are four types of Coordinate Reference Frame:
(All Transformation elements contain a projection attribute, using values from Table 4)
Contains:
Contains one of:
Contains one of:
Contains:
CARTESIAN, SPHERICAL, UNITSPHERE, POLAR, CYLINDRICAL, HEALPIX, or STRING; contains: dimensionality.
ReferencePixel contains a 1, 2, or 3-dimensional Pixel.
A Coordinates element consists of up to six Coordinate elements and contains a reference to a Coordinate System. Each Coordinate has five components. Each component may occur once (a definite or typical value) or twice (indicating a range of values):
All components are optional; in addition, there may be a name. One or more Coordinate elements may be provided through a binary FITS table.
A variety of error types may be defined; statements below on the data types of errors are to be considered preliminary, contingent on additional definitions.
There are nine types of Coordinate elements, each of which is a composite of the above-mentioned components, except where noted.
Each Coordinates object needs to refer to a Coordinate System through a coord_system_id attribute.
There are three types of Coordinates elements:
Individual Coordinates need to refer to a specific Coordinate Frame through a frame_id.
The Coordinate needs to refer to a specific Coordinate Frame through a frame_id. There are four types of GenCoordinate:
Optional units; all components are scalar doubles.
Optional units; Error, Resolution, Size, PixSize may consist of:
Optional units; Error, Resolution, Size, PixSize may consist of:
Only contains a (string) Value, no other components.
The value (TimeInstant) is an instant of the AstronTime class; all other components (Error, Resolution, Size, PixSize) are doubles and need a unit (s, d, a or yr, cy). AstronTime contains an Absolute Time element and an optional relative time element. It also may have a TimeScale attribute.
AstronTime contains the following:
Absolute Time may be of type ISOTime (ISO-8601 format), JDTime, or MJDTime. This should be a decimal for JD and MJD since a double is not guaranteed to have sufficient accuracy. In addition, for use with simulations, it may be of the type TimeOrigin which currently may only have the value RELOCATABLE.
Decimal; offset with respect to Absolute Time; unit required.
Units are required for all components, angular or linear.
There are three types of Position:
All components are scalar doubles.
CError2, CResolution2, CSize2, CPixSize2 may consist of:
CError3, CResolution3, CSize3, CPixSize3 may consist of:
Same model as Spatial Position; needs a spatial as well as a time unit.
Note that this item is for true space velocities, not for derived Doppler velocities.
There are three types of Velocity:
All components are scalar doubles.
CError2, CResolution2, CSize2, CPixSize2 may consist of:
1. Two doubles
2. 2x2 matrix
3. Radius
CError3, CResolution3, CSize3, CPixSize3 may consist of: