This repository has been archived by the owner on May 29, 2022. It is now read-only.
Fixed incorrect accuracy assignment in Rinex3NavData from EphemerisGPS #19
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.
We suspect that in Rinex3NavData::operator GPSEphemeris should be
accuracy = gpseph.accuracy;
Because
gpseph.accuracy
is never used during constructionGPSEphemeris::accuracyFlag
isshort
butRinex3NavData::accuracy
isdouble
And because of description
Unit test with conversion check added