Open michaeljfazio opened 4 years ago
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. Thanks in advance for your clarification.
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 have determined that AisLib can be extended to the extent of decoding AIS Single Slot Binary Messages (Message 25) into a binary array. However, the extraction of the meaningful payload will need to be handled by the API utilizing AisLib. This is because Message 25 is an Application Specific Message, since the data content of this binary message is defined by the application.
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).