Integrate SP3 lib to ecosystem #168
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
One solution to having a single cargo workspace for this ecosystem is either * have SP3 into this crate: which facilitates future developments * move all applications (non libraries, ie., library users like rinex-cli) into an external workspace Having SP3 into this is probably the best solution. For example "rinex-qc" makes no sense without SP3 and RINEX knowledge. "rinex-cli" is a heavy user of "rinex-qc" (one of the two major opmodes). I think that answers the question. Signed-off-by: Guillaume W. Bres <guillaume.bressaix@gmail.com>
gwbres
added
documentation
|
Note that you can use I've used the former, but can't say it's very pleasant. |
lnicola
reviewed
Sep 15, 2023
lnicola
approved these changes
Sep 15, 2023
Okay, maybe let's not bother 😂. |
good to know 👍 Probably not needed on this one, considering this repo is almost brand new |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One solution to having a single cargo workspace for this ecosystem is either
Having SP3 into this is probably the best solution.
For example
rinex-qcmakes no sense without SP3 and RINEX knowledge.rinex-cliis a heavy user ofrinex-qc(one of the two major opmodes).Also, new developments (advanced geodesics), calls for
rinex-cliusing local referencing.I think that answers the question.