generated from ivoa-std/doc-template
-
Notifications
You must be signed in to change notification settings - Fork 4
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
ISOTime #16
Comments
if the string representation definition is to be kept then it should be called FITSTime |
Paul, I'm on leave now for the next couple weeks, but wanted to say thanks
for pinging this to the surface.
I think that what is in the Coords model should agree with DALI, but I'm
talking off the top of my head and that is risky.
If we need to discuss a change/correction to what's in the document,
hopefully others will chime in here.
Mark
…On Thu, Dec 14, 2023 at 3:23 PM Paul Harrison ***@***.***> wrote:
if the string representation definition is to be kept then it should be
called FITSTime
—
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADMLJCXVVVJ4SUKESC6AZFLYJNN4ZAVCNFSM6AAAAAAW6DZ2AKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJWGUZDSNBYGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
pahjbo
added a commit
to Javastro/CoordinateDM
that referenced
this issue
Jan 4, 2024
These updates address several issues * ivoa-std#4 * ivoa-std#16 * and the discussion around Quantity where it does not have a "value" defined mean that for practical source generation a cartesian point with a real quantity is needed IVOA base version 1.1 - potential for better unit.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The description of ISOTime says that the string representation follows FITS and drops the final Z that indicates UTC. I thought that this error had been corrected (and accepted) in the IVOA quite a long time ago. If something looks like an ISO time, is called an ISO time then it should follow the ISO rules. If you pass the bare time string to an iso time interpreting library on your computer then it will return a local time - which will possibly be incorrect depending on location and computer timezone setup
The text was updated successfully, but these errors were encountered: