Skip to content
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

Rebase: Ship Formatting Updates #359

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Conversation

rbollar
Copy link
Contributor

@rbollar rbollar commented Jan 30, 2025

Add destination to callsign when available to make ais extended labels look like adsb. I think at this point ship / air extended labels look fairly harmonized.

Add shiptype = 0 with value UNKN for ships that don't report a shiptype -- more likely than deliberately using a reserved value.

Replace blank callsign / registration with MMSI. Since non-ships don't have a callsign & may not have a registration, this gives them a unique identifier.

rbollar and others added 3 commits January 31, 2025 09:29
In the extendedLabels, have ships that have destination information display like aircraft.
Populate callsign / registration with mmsi if  either is blank. Non-ship ais objects may not have a callsign. mmsi is a unique identifier and can be used for filtering.
Copy link
Contributor Author

@rbollar rbollar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No worries on the mmsi -- I was trying to fix the situation that aids to navigation don't have callsigns and sometimes don't broadcast registrations. Would you consider a substitution of mmsi for registration like we did for callsigns in planeObject.js? Or should I just let it go?
image

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