Skip to content

feat(rtk): position saving and reloading#104

Open
zarcell wants to merge 74 commits intoskybrush-io:devfrom
zarcell:rtk-savepos
Open

feat(rtk): position saving and reloading#104
zarcell wants to merge 74 commits intoskybrush-io:devfrom
zarcell:rtk-savepos

Conversation

@zarcell
Copy link
Copy Markdown

@zarcell zarcell commented Oct 29, 2025

This still needs testing on field, use this only for code review!

@zarcell zarcell closed this Oct 29, 2025
@isti115 isti115 reopened this Oct 31, 2025
@isti115 isti115 changed the title RTK position saving and reloading WIP: RTK position saving and reloading Oct 31, 2025
@isti115 isti115 marked this pull request as draft October 31, 2025 09:26
@isti115 isti115 marked this pull request as ready for review November 17, 2025 09:48
@isti115 isti115 changed the title WIP: RTK position saving and reloading RTK position saving and reloading Nov 26, 2025
@isti115 isti115 marked this pull request as draft November 27, 2025 14:49
@zarcell zarcell changed the base branch from main to dev December 8, 2025 09:51
@zarcell zarcell marked this pull request as ready for review December 8, 2025 09:51
@zarcell zarcell changed the title RTK position saving and reloading feat(rtk): position saving and reloading Dec 10, 2025
Copy link
Copy Markdown
Member

@isti115 isti115 left a comment

Choose a reason for hiding this comment

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

I tried to provide inline suggestions for all the optional nitpicks, so they can be batch accepted without any extra hassle, as I didn't want to introduce any unnecessary burden requiring further effort on your part. If it still seems too much, I can try to either mark the actually important comments separately or commit some of the trivial changes myself.

Copy link
Copy Markdown
Member

@isti115 isti115 left a comment

Choose a reason for hiding this comment

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

I tried to provide inline suggestions for all the optional nitpicks, so they can be accepted without any extra hassle, as I didn't want to introduce any unnecessary burden requiring further effort on your part. If it still seems too much, I can try to either mark the actually important comments separately or commit some of the trivial changes myself.

Copy link
Copy Markdown
Member

@isti115 isti115 left a comment

Choose a reason for hiding this comment

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

I tried to provide inline suggestions for all the optional nitpicks, so they can be accepted without any extra hassle, as I didn't want to introduce any unnecessary burden requiring further effort on your part. If it still seems too much, I can try to either mark the actually important comments separately or commit some of the trivial changes myself.

Copy link
Copy Markdown
Member

@isti115 isti115 left a comment

Choose a reason for hiding this comment

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

I tried to provide inline suggestions for all the optional nitpicks, so they can be accepted without any extra hassle, as I didn't want to introduce any unnecessary burden requiring further effort on your part. If it still seems too much, I can try to either mark the actually important comments separately or commit some of the trivial changes myself.

@zarcell zarcell requested a review from isti115 January 25, 2026 16:43
Comment on lines +137 to +138
return hasECEF && (surveyedCoordinateValid || typeof accuracy === 'number');
// Consider fix valid only with ECEF position, valid-coordinate flag, and numeric accuracy.
return hasECEF && surveyedCoordinateValid && typeof accuracy === 'number';
Copy link
Copy Markdown
Member

@isti115 isti115 Feb 2, 2026

Choose a reason for hiding this comment

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

@ntamas Please review this logic with @zarcell as discussed, by testing using local RTK base stations and remote NTRIP sources as well!

Copy link
Copy Markdown
Author

@zarcell zarcell Mar 16, 2026

Choose a reason for hiding this comment

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

Notes for @ntamas when review is done: the LED on the RTK widget shows the surveys current state, which can be misleading when using fixed coordinates from server config or even from this feature. One solution can be a FIXED bit in the survey flags that the Live can handle to show exactly what is happening to the user.

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