Click or drag to resize
Earth Class

Note: This API is now obsolete.

NOVAS-COM: Represents the "state" of the Earth at a given Terrestrial Julian date
Inheritance Hierarchy

Namespace: ASCOM.Astrometry.NOVASCOM
Assembly: ASCOM.Astrometry (in ASCOM.Astrometry.dll) Version: (
[ObsoleteAttribute("This class will be withdrawn in the next major release, please use the SOFA or NOVAS31 classes instead")]
public class Earth

The Earth type exposes the following members.

Public methodEarth
Create a new instance of the Earth object
Public propertyBarycentricPosition
Earth barycentric position
Public propertyBarycentricTime
Earth barycentric time
Public propertyBarycentricVelocity
Earth barycentric velocity
Public propertyEarthEphemeris
Ephemeris object used to provide the position of the Earth.
Public propertyEquationOfEquinoxes
Earth equation of equinoxes
Public propertyHeliocentricPosition
Earth heliocentric position
Public propertyHeliocentricVelocity
Earth heliocentric velocity
Public propertyMeanObliquity
Earth mean objiquity
Public propertyNutationInLongitude
Earth nutation in longitude
Public propertyNutationInObliquity
Earth nutation in obliquity
Public propertyTrueObliquity
Earth true obliquity
Public methodSetForTime
Initialize the Earth object for given terrestrial Julian date
NOVAS-COM objects of class Earth represent the "state" of the Earth at a given Terrestrial Julian date. The state includes barycentric and heliocentric position vectors for the earth, plus obliquity, nutation and the equation of the equinoxes. Unless set by the client, the Earth ephemeris used is computed using an internal approximation. The client may optionally attach an ephemeris object for increased accuracy.

Ephemeris Generator
The ephemeris generator object used with NOVAS-COM must support a single method GetPositionAndVelocity(tjd). This method must take a terrestrial Julian date (like the NOVAS-COM methods) as its single parameter, and return an array of Double containing the rectangular (x/y/z) heliocentric J2000 equatorial coordinates of position (AU) and velocity (KM/sec.). In addition, it must support three read/write properties BodyType, Name, and Number, which correspond to the Type, Name, and Number properties of Novas.Planet.

See Also