API Data return - why MMSI instead of IMO?

Follow

Rosie Haworth

• October 02, 2020 15:12

Hi,

When I send off an API request for historical data tracking, I send request using IMO. However, the data I get back gives the vessel MMSI as an identifier.

In my analysis, I then use a lookup to match the MMSI to give vessel name.

However, this is a problem because the MMSI changes over time, and if we have missed an MMSI change, the formula won't work.

Instead, it would be better practice if the API return gave you the IMO as this does not change, or gave you the option of what format you wanted it to come back with.

 

0

• 

  Valia Gelasiou

  • October 13, 2020 08:33

  Dear Rosie,

  Thank you for your comment.

  The API services have specific request parameters and response fields.

  The PS01 Vessel Historical Track could be requested using the IMO,SHIP_ID or MMSI, however the response includes only the MMSI and SHIP_ID.

  Please have a look at our documentation for further details. https://www.marinetraffic.com/en/ais-api-services/documentation/api-service:ps01/

  We really appreciate your feedback as our mission is to constantly improve our services.

  Kind regards,

  0

  Comment actions Permalink
• 

  Michael Bender

  • November 19, 2020 19:28

  Why can't the API send back the IMO? Your database knows it (because you know other parameters of a ship).

  Can you create an enhancement request for this feature (to send back the IMO as well)?

   

  Thanks,

  Mike

  0

  Comment actions Permalink
• 

  Valia Gelasiou

  • November 20, 2020 08:33

  Dear Mike,

  Thank you for your comment,

  The PS01 (Vessel Historical Track) API  service returns the MMSI and SHIP_ID in the simple response.

  However, you could call it by using one of the vessel's identifiers(IMO,MMSI,SHIP_ID). 

  We will forward your feedback to our product team.

  Kind regards,

   

  0

  Comment actions Permalink

Please sign in to leave a comment.