-
Notifications
You must be signed in to change notification settings - Fork 98
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
Message Type 25 Not Implemented #65
Comments
I am afraid that (to my knowledge) there's no current funding or maintenance of this project. I hope that this will improve in the future - but for now it's a bit of a DIY project. If you can submit a pull request for decoding of message type 25 I'll be happy to merge it though. |
@michaeljfazio we have been looking at the issues reported for the AIS decoding library, I see this quite old issue raised by you. However according to the AIS specs, message type 25 is used to transmit binary data from one device to another. Therefore there is no standard to decode this message. What would be the idea that you had to parse this message? It seems that there would be no data structure to derive from this binary data message which is not a standard. |
I would think a message type with just a raw byte array would be sufficient @mith-emsa. |
That’s how my alternative (decoding only) library AISmessages does it. So maybe that could be for inspiration? |
@michaeljfazio We are looking at implementing the feature for the future but without a planned date for implementation. |
I'm processing a satellite AIS feed (global coverage) and quite often we receive AIS Message 25 which fails to parse with an exception. Given that this is a valid AIS Message type I would think it should probably be implemented (unless there is a good reason not to).
The text was updated successfully, but these errors were encountered: