-
Notifications
You must be signed in to change notification settings - Fork 26
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
AIS infopage crashes #393
Comments
It does not happen on all AIS targets, for some the info page is displayed as expected, but for many others it crashes as described. |
Here is some test data (click on the vessels in the Kadetrinne)
|
The JS console does not show any error messages. |
Thanks for reporting - will have a look. |
It happens not only on current master but also in version 20241128. Maybe it is due to malformed AIS data (but the data look OK), but even if he data was malformed, it should not crash. |
It looks like this. Bildschirmaufzeichnung.vom.2025-01-01.17-13-23.mp4 |
I found something: The "crash" happens when the target is outside the AIS-range (config value). Clicking on a target inside that range from the own boat works fine. When panning away from the boat, targets inside the AIS range from the map center are displayed as well. When clicking on a target inside this range but outside the range from own boat, the page "crashes". I think, when clicking the target and the info page opens, the map center is lost, the target gets out of range and is no longer displayed. |
That fixed it. I have a question concerning AIS. I did not find anything in the docs.
|
see #397 |
I created a simple plugin https://github.com/quantenschaum/aisstream-plugin to pull AIS data from https://aisstream.io/ into AVnav.
The plugin injects the AIS data as NMEA sentences.
I works, the AIS targets show up on the map. But when I click on a target, the AIS infopage opens, displays the data shortly, then all data fields become empty and the page closes, the map is shown again and all AIS target are gone, but reappear quickly.
The text was updated successfully, but these errors were encountered: