-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Aircraft not removing themselves #20
Comments
They should expire within their stale period, which defaults to about 5
minutes if I remember correctly. This can be changed with the COT_STALE
config parameter.
There's also been some bugs in various TAK clients in the past where
expired markers don't actually have their onscreen labels or glyphs removed.
…On Sat, Jan 21, 2023 at 12:03 AM Joshua ***@***.***> wrote:
Is it normal that once an aircraft goes out of range that they remain on
the TAK map or do I need to change something?
—
Reply to this email directly, view it on GitHub
<#20>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAWIXWQXVDR3Y3IT6R4YZDWTOJ6HANCNFSM6AAAAAAUCIRHZI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Greg Albrecht ***@***.***> W2GMD
EMT & ICT Specialist
Signal: +1-310-621-9598
https://ampledata.org/ <http://ampledata.org/>
https://github.com/ampledata
|
Thanks! You're correct in that this seems to affect different apps differently. I'm sure it's more of a bug with the various interfaces and not this project now that I've had a little more time with it. BTW, is there a more complete list of all the config parameters available somewhere? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is it normal that once an aircraft goes out of range that they remain on the TAK map or do I need to change something?
The text was updated successfully, but these errors were encountered: