Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarifications on decimal years representations #21

Open
tomdonaldson opened this issue May 15, 2020 · 0 comments
Open

Clarifications on decimal years representations #21

tomdonaldson opened this issue May 15, 2020 · 0 comments

Comments

@tomdonaldson
Copy link
Contributor

(This suggestion was first made on the Applications mail list.)

In section 3.5:
Usage of besselian or julian years for timestamps apart from making timeorigin un-useful (and then forbidden) also implies some inference on the timescale used (see the TIME WCS paper for references and discussion). It has been suggested to add the the following sentence at the end of timeorigin explanation: "When using calendar epochs written in yr or Ba, note that conventionally Julian years are tied to the TDB timescale and Besselian years to ET (written here as TT) (Rots and Bunclark et al., 2015)."

On a related topic, in 3.4 (COOSYS):
We don't explicitly constrain the representation of time in equinox and epoch attributes. This however clear in the xml schema. The suggestion is to add after "... the epoch of the positions if necessary", the following sentence: " Both equinox and epoch MUST be expressed in the Julian or Besselian calendar".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant