Introduce HeaderClass #59
Closed
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.
Dear Michael,
I am looking into speeding up the RINEX3 processing. While reading the code, I saw that the header information handling is done quite confusing. I thought of an easier way to using a HeaderClass, which I want to implement first. I am convinced its more comprehensible and easier to maintain. I also took some ideas from @anand-satnav
What do you think about this solution? If you like it, I will continue to implement it, while also fixing the speed. I am willing to implement this also for rinex2 and nav, which should eventually shorten the code.
Note: The code does not run yet.