LiveMap JSON #226
Replies: 4 comments 5 replies
-
I am not yet convinced this is the right way to go. The TTGO is receiving only one sonde at a time, so there is no point in sending updates every second of all other sonde entries that certainly do not change. I see the risk of the TTGO running out of memory for having that large amount of data in network queues. I would rather handle this on the client / javascript code side. If a new sonde is being decoded, not remove the "old" one from the map, but just keep it (maybe either with a option to manually remove it, or if it is too old). That is the way I do it on the Android app and so far nobody complained that it is not good that way ;-) (Possibly, as extended version, the possibility to query all sonde entries on startup of the map via some request parameter) |
Beta Was this translation helpful? Give feedback.
-
Good point.
So perhaps have the additional sonde "slots" and handling of them in
Javascript on the client and update them with the current json structure.
That would also work yes.
…On Fri, 22 Oct 2021, 16:47 dl9rdz, ***@***.***> wrote:
I am not yet convinced this is the right way to go.
The TTGO is receiving only one sonde at a time, so there is no point in
sending updates every second of all other sonde entries that certainly do
not change. I see the risk of the TTGO running out of memory for having
that large amount of data in network queues.
I would rather handle this on the client / javascript code side. If a new
sonde is being decoded, not remove the "old" one from the map, but just
keep it (maybe either with a option to manually remove it, or if it is too
old). That is the way I do it on the Android app and so far nobody
complained that it is not good that way ;-)
(Possibly, as extended version, the possibility to query all sonde entries
on startup of the map via some request parameter)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#226 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATNONELS5GYDXGO3WU7OXDUIF2QNANCNFSM5GQWWC5A>
.
|
Beta Was this translation helpful? Give feedback.
-
@cixio would you be able to help with this handling of multiple sondes on livemap? |
Beta Was this translation helpful? Give feedback.
-
Okay, some modifications and the multi-sonde-livemap works nice, you can take a look at it in my repository: https://github.com/cixio/rdz_ttgo_sonde/commit/ec4b932c3ce7c68b133c9473e04bd822b80bee42 But now I have some problems, maybe you have an idea to solve them:
Also there is a bug with the predictions, they will be generated every 5 minutes (or earlier, depends on the height of the sonde), but when the timer pulls a new prediction only the prediction for the last sonde got from the ttgo will be updated. Need some time to fix it, because I dont know how to manage the different update-times. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I know a few weeks ago there was an issue relating to the LiveMap when you are receiving multiple sondes at once. I couldn't imagine what it would look like since I normally never have two sondes being received at once 😄
The way it was handled is that it was jumping between the locations because only one sonde data is available at any one time in the live.json.
Now I know that we always have the data for all received sondes because it's displayed in the data tab.
Would it be possible to have the live.json create something like below so that we can have the option of displaying multiple simultaneous or pick which sonde we would like to see tracked?
Currently it's just like this:
Beta Was this translation helpful? Give feedback.
All reactions