You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experiencing issues with the latest update. The reference lines, which were previously visible, are no longer displaying
Additionally, the polygon layer is behaving inconsistently. In some areas, the polygons render correctly, while in others, they are completely absent. This makes the data visualization incomplete and unreliable.
It seems likely that you started with an empty database. The reference line will only appear if the station in the path is known at the time the packet is received. Typically, stationary stations send a packet only once every 30 minutes or so. I recommend waiting about an hour and then checking to see if received packets have a reference line.
I'll keep this issue open so you can confirm before I close it.
I have now setup the latest version on several different servers (using docker containers directly and deployed using kubernetes). I have not seen this problem on any of my setups. Note that I am using the docker files provided in the repository.
I would like to help you, but I need more information on how to reproduce it.
I'm using Docker and serving through a Cloudflare tunnel. There was no problem with the old version, but I think the latest WebSocket has an issue displaying reference lines through Cloudflare.
I'm still experiencing display issues with both the coverage polygon and reference lines. The behavior is inconsistent for both elements: in some areas, they render correctly, while in others, they are completely absent. This intermittent visibility makes the data visualization unreliable and incomplete. This is a regression from the previous version, where both the coverage polygon and reference lines displayed consistently.
Activity
qvarforth commentedon Jan 7, 2025
Hi,
Thank you for your report!
It seems likely that you started with an empty database. The reference line will only appear if the station in the path is known at the time the packet is received. Typically, stationary stations send a packet only once every 30 minutes or so. I recommend waiting about an hour and then checking to see if received packets have a reference line.
I'll keep this issue open so you can confirm before I close it.
9M2PJU commentedon Jan 8, 2025
After a while, still not showing and symbols also not loaded.
previous version is ok, has reference lines and also all symbols loaded.
qvarforth commentedon Jan 8, 2025
Ok, that was unexpected.
I've cleaned everything and rebuilt the docker images, but I can't reproduce your problem (neither this nor the other regarding missing symbols).
How do you start everything? Are you using docker or are you doing it in a different way?
9M2PJU commentedon Jan 12, 2025
I still use docker on a raspberry pi. I think the problem is from the SSL setting on the apache.
qvarforth commentedon Jan 18, 2025
I have now setup the latest version on several different servers (using docker containers directly and deployed using kubernetes). I have not seen this problem on any of my setups. Note that I am using the docker files provided in the repository.
I would like to help you, but I need more information on how to reproduce it.
9M2PJU commentedon Jan 19, 2025
I'm using Docker and serving through a Cloudflare tunnel. There was no problem with the old version, but I think the latest WebSocket has an issue displaying reference lines through Cloudflare.
9M2PJU commentedon Jan 22, 2025
I'm still experiencing display issues with both the coverage polygon and reference lines. The behavior is inconsistent for both elements: in some areas, they render correctly, while in others, they are completely absent. This intermittent visibility makes the data visualization unreliable and incomplete. This is a regression from the previous version, where both the coverage polygon and reference lines displayed consistently.