-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
from_gregorian but in GPST #257
Comments
Yes, that's a good idea. Is this something we can implement in version 4?
It sounds like it would be quite a bit easier in there. What do you think?
…On Wed, Aug 30, 2023, 02:28 gwbres ***@***.***> wrote:
Hello @ChristopherRabotin <https://github.com/ChristopherRabotin>,
I would be interested in having an Epoch construction method similar to
Epoch::from_gregorian_utc but in TimeScale::GPST.
from_gregorian_utc is the best thing to use when all data fields are
already known.
Such feature would solve the requirement I face in two of my parsers:
- in RINEX when parsing NAV ephemeris - the SV broadcasts Epoch
expressed in their timescale (GPST for example)
- in SP3, all Epochs are expressed in a unique GNSS time scale
—
Reply to this email directly, view it on GitHub
<#257>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABEZV2FKQUUO3W2KHEEVI3LXX32RVANCNFSM6AAAAAA4EEI7RA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes, definitely easier if the new approach gets finalized. I don't have a need for this immediatly either |
Would this make more sense in #229 to avoid proliferation of more initializers? |
I agree that if Epochs can be built from durations directly, it's okay to get rid of all the Now we have |
Hi Guillaume, |
Hello @ChristopherRabotin,
I would be interested in having an
Epoch
construction method similar toEpoch::from_gregorian_utc
but inTimeScale::GPST
.from_gregorian_utc
is the best thing to use when all data fields are already known.Such feature would solve the requirement I face in two of my parsers:
The text was updated successfully, but these errors were encountered: