Skip to content

Conversation

@fpezzinosn
Copy link
Contributor

Description

@swift-nav/devinfra

These messages are:

  • MSG_SSR_FLAG_HIGH_LEVEL
  • MSG_SSR_FLAG_SATELLITES
  • MSG_SSR_FLAG_TROPO_GRID_POINTS
  • MSG_SSR_FLAG_IONO_GRID_POINTS
  • MSG_SSR_FLAG_IONO_TILE_SAT_LOS
  • MSG_SSR_FLAG_IONO_GRID_POINT_SAT_LOS

API compatibility

Does this change introduce a API compatibility risk?

No, just adding new messages to a new package.

API compatibility plan

If the above is "Yes", please detail the compatibility (or migration) plan:

JIRA Reference

https://swift-nav.atlassian.net/browse/OTA-121

@fpezzinosn fpezzinosn force-pushed the fpezzinosn/OTA-121 branch from 3f1fcf0 to 1b06134 Compare May 6, 2022 15:12
@fpezzinosn fpezzinosn force-pushed the fpezzinosn/OTA-121 branch from 3f59390 to 4347492 Compare May 9, 2022 15:09
@fpezzinosn fpezzinosn self-assigned this May 9, 2022
@fpezzinosn fpezzinosn marked this pull request as ready for review May 9, 2022 18:01
@fpezzinosn fpezzinosn requested review from a team and notoriaga as code owners May 9, 2022 18:01
Copy link
Contributor

@silverjam silverjam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fpezzinosn -- FYI, we need a follow-up task to review the PDF documentation for these messages, see https://github.com/swift-nav/libsbp/blob/staging/docs/sbp.pdf and check out the "units" columns in particular (mainly, the units need to very simple otherwise they'll overflow the layout in the PDF, so any "usage notes" or "caveats" for the units need to move into the message description).

@fpezzinosn
Copy link
Contributor Author

@fpezzinosn -- FYI, we need a follow-up task to review the PDF documentation for these messages, see https://github.com/swift-nav/libsbp/blob/staging/docs/sbp.pdf and check out the "units" columns in particular (mainly, the units need to very simple otherwise they'll overflow the layout in the PDF, so any "usage notes" or "caveats" for the units need to move into the message description).

Ok, will do. I'll also enable the others that are currently set as private to check how their documentation looks.

@fpezzinosn fpezzinosn merged commit 3288120 into staging May 11, 2022
@fpezzinosn fpezzinosn deleted the fpezzinosn/OTA-121 branch May 11, 2022 17:18
fpezzinosn added a commit that referenced this pull request Jun 17, 2022
* Add support for SSR_ORBIT_CLOCK_BOUNDS message [OTA-65] (#1108)

* Add support for MSG_SSR_CODE_PHASE_BIASES_BOUNDS message [OTA-119] (#1127)

* Add Atmospheric Corrections and Bounds [OTA-120] (#1131)

Co-authored-by: Jason Mobarak <jason@swift-nav.com>

* Add support for MSG_SSR_ORBIT_CLOCK_BOUNDS_DEGRADATION message [OTA-133] (#1137)

* Add Integrity Flags messages [OTA-121] (#1132)

* Add transformation parameter message [OTA-149] (#1144)

* Add leap second message [OTA-148] (#1145)

* Clean up the documentation for the new messages [OTA-150] (#1149)

Co-authored-by: swiftnav-svc-jenkins <42622338+swiftnav-svc-jenkins@users.noreply.github.com>
Co-authored-by: Jason Mobarak <jason@swift-nav.com>

* Updates messages to ICD v1.2 [OTA-161] (#1155)

* make all

Co-authored-by: Jason Mobarak <jason@swift-nav.com>
Co-authored-by: swiftnav-svc-jenkins <42622338+swiftnav-svc-jenkins@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants