Skip to content

feat: add MAVLINK_M_COORD_TYPE operator coordinate-display hint - #9

Open
nick-tolentino wants to merge 1 commit into
Dronecode:mainfrom
nick-tolentino:feat/coord-type
Open

feat: add MAVLINK_M_COORD_TYPE operator coordinate-display hint#9
nick-tolentino wants to merge 1 commit into
Dronecode:mainfrom
nick-tolentino:feat/coord-type

Conversation

@nick-tolentino

Copy link
Copy Markdown

Add an OPTIONAL, ADVISORY MAVLINK_M_COORD_TYPE enum (WGS84 decimal / DMS / MGRS / UTM) and a coord_type field on the lat/lon-bearing messages. The value is a UI presentation hint only: on-wire lat/lon remain WGS84 degE7 and consumers must not reinterpret coordinates from it. Unset (0) means decimal degrees.

Applied to: TARGET_SET_COORD, TARGET_BOX_COORD, TARGET, FIRES, SPLASH_CORRECTION, TARGET_HANDOVER, BATTLE_DAMAGE_ASSESSMENT, RWS_POSE, TARGET_CUE, PARTICIPANT_POSITION.

Add an OPTIONAL, ADVISORY MAVLINK_M_COORD_TYPE enum (WGS84 decimal /
DMS / MGRS / UTM) and a coord_type field on the lat/lon-bearing
messages. The value is a UI presentation hint only: on-wire lat/lon
remain WGS84 degE7 and consumers must not reinterpret coordinates from
it. Unset (0) means decimal degrees.

Applied to: TARGET_SET_COORD, TARGET_BOX_COORD, TARGET, FIRES,
SPLASH_CORRECTION, TARGET_HANDOVER, BATTLE_DAMAGE_ASSESSMENT, RWS_POSE,
TARGET_CUE, PARTICIPANT_POSITION.

Re-implements the coordinate-type feature from the pre-rewrite fork
(commit bde0206) on top of the full MAVLink-M dialect, following the
new MAVLINK_M_ naming convention and appended-field style. Generated C
headers are intentionally left to the generate_c_lib.yml CI workflow.
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.

1 participant