Skip to content

Discard updates from pilots above 5000ft and distance > 10nm #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

herver
Copy link

@herver herver commented Jan 29, 2025

Idea for improvement: Replace hardcoded distance with configurable

Todo: Replace hardcoded distance with configurable
@herver
Copy link
Author

herver commented Jan 29, 2025

Note: as I chopped up commits in different PRs it's possible that this one creates a merge conflict, but it should be easy to resolve 😅

@LeoKle
Copy link
Member

LeoKle commented Feb 11, 2025

Filtering traffic updates by departed makes sense, but I would recommend another implementation to do so.
This implementation requires the Pilot model (typdef) to be extended and does not actually filter the update from getting into the plugin. However we can avoid having to extend the model and prevent it from getting into the update queue by doing the necessary checks at

if (false == flightplan.IsValid() || nullptr == flightplan.GetFlightPlanData().GetPlanType() ||
for example.

@LeoKle LeoKle closed this Feb 11, 2025
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.

2 participants