Skip to content

BUG: FiltersShipMMSI filter not working and not receiving data. #23

@leo300

Description

@leo300

I have been trying to use the FiltersShipMMSI filter in the WebSocket subscription message to receive data for specific MMSI numbers, but it appears to be non-functional. When using the filter, no data is returned, and I do not receive the expected messages for the specified ships.

const subscriptionMessage = {
    APIkey: 'my-api-key',
    BoundingBoxes: [[[-90, -180], [90, 180]]],
    FiltersShipMMSI: ["368207620", "367719770"], // MMSI filter not working
    FilterMessageTypes: ["PositionReport"] // Optional
};

socket.send(JSON.stringify(subscriptionMessage));

When I remove the FiltersShipMMSI filter, I start receiving data, but it seems to result in endless streams of messages for all ships globally, which is not feasible for my use case.

Has anyone successfully tested the FiltersShipMMSI filter in the JavaScript example? I’d appreciate any guidance or confirmation of whether this feature has been tested or is known to work.

Steps to reproduce:
Use the provided example from the documentation.
Apply the FiltersShipMMSI filter with valid MMSI numbers.
Wait for incoming data.

Expected Behavior:
I expect to receive data only for ships with the provided MMSI numbers.

Actual Behavior:
No data is received when using the filter.

Any help or insights would be greatly appreciated. Thank you!

Suggestion::It would be useful to include support for filtering by IMO number (FiltersShipIMO) in the API, as the IMO number is widely used in maritime tracking. This would be a helpful addition for users who may not have MMSI numbers available but do have IMO numbers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions