Repository navigation
mission: correct _INT frame guidance - #796
Merged
Merged
Conversation
The _INT global frames were made synonyms of their non-_INT counterparts in mavlink/mavlink#2092 and are tagged <superseded since="2024-03"> in common.xml, but this page still instructed plan items to use them and tied 1e7 scaling to the frame rather than to the field. Scaling is a property of the field: MISSION_ITEM_INT.x/y are int32_t holding degrees * 1e7 regardless of which spelling of the frame is set. Recommend MAV_FRAME_GLOBAL / _RELATIVE_ALT / _TERRAIN_ALT, and keep the note about the _INT variants as a compatibility aside.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
hamishwillee
approved these changes
Oct 29, 2026
hamishwillee
left a comment
Collaborator
There was a problem hiding this comment.
Thanks @julianoes
I moved this up and made it more of a warning. While strictly accurate too easy to miss how implementers should work with these.
This file contains hidden or 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
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.
The
_INTglobal frames became synonyms of their non-_INTcounterparts in mavlink/mavlink#2092 and are now marked superseded.mission.mdstill told plan items to use the_INTframes, and tied the 1e7 lat/lon scaling to the frame rather than to the field.This recommends
MAV_FRAME_GLOBAL/_RELATIVE_ALT/_TERRAIN_ALTinstead, notes that scaling comes from theMISSION_ITEM_INTfield type, and keeps the_INTvariants as a compatibility note.Tested:
yarn docs:build, plus markdownlint, prettier and cspell on the changed file.@julianoes