NPI-3676 Exception handling on (unsupported) SP3 velocity data output #66
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.
gnssanalysis
currently does not correctly support output of SP3 velocity data.At present, currently calling
gen_sp3_content()
on aDataFrame
containing velocity data, will result in a non-compliant SP3 file with velocity data in additional columns (not in additional, interlaced rows as the spec calls for).This PR adds a check for velocity columns. If any velocity columns are found a warning is logged, the columns are deleted, then output continues as normal on just the position data.
Optionally based on a new parameter to
gen_sp3_content()
, aNotImplementedError
can be raised instead of logging a warning.