VD02: Bad number type in JSON object response

Follow

Under NDA

• March 10, 2021 02:22
• Edited

Looking at the example values for VD02 (Similar results observed when actually calling the API) with msgtype: jsono (applies to json too), the returned data is (formatted):

{
  "METADATA": {
    "TOTAL_RESULTS": 1,
    "TOTAL_PAGES": 1,
    "CURRENT_PAGE": 1
  },
  "DATA": [
    {
      "MMSI": "275507000",
      "IMO": "9375783",
      "NAME": "LIBERO",
      "PLACE_OF_BUILD": "",
      "BUILD": "2006",
      "BREADTH_EXTREME": "12.4",
      "SUMMER_DWT": "2930",
      "DISPLACEMENT_SUMMER": "",
      "CALLSIGN": "YLPS",
      "FLAG": "LV",
      "DRAUGHT": "4.36",
      "LENGTH_OVERALL": "88.53",
      "FUEL_CONSUMPTION": "",
      "SPEED_MAX": "",
      "SPEED_SERVICE": "10.5",
      "LIQUID_OIL": "",
      "OWNER": "BOJEN",
      "MANAGER": "BOJEN",
      "FINANCIAL_OWNER": "",
      "TECHNICAL_MANAGER": "",
      "VESSEL_TYPE": "GENERAL CARGO"
    }
  ]
}

All values are quoted as string, despite some response fields having numeric types (integer and real).

{
  "METADATA": {
    "TOTAL_RESULTS": 1,
    "TOTAL_PAGES": 1,
    "CURRENT_PAGE": 1
  },
  "DATA": [
    {
      "MMSI": "275507000",
      "IMO": "9375783",
      "NAME": "LIBERO",
      "PLACE_OF_BUILD": "",
      "BUILD": "2006",
      "BREADTH_EXTREME": 12.4,
      "SUMMER_DWT": 2930,
      "DISPLACEMENT_SUMMER": null,
      "CALLSIGN": "YLPS",
      "FLAG": "LV",
      "DRAUGHT": 4.36,
      "LENGTH_OVERALL": 88.53,
      "FUEL_CONSUMPTION": "",
      "SPEED_MAX": null,
      "SPEED_SERVICE": 10.5,
      "LIQUID_OIL": null,
      "OWNER": "BOJEN",
      "MANAGER": "BOJEN",
      "FINANCIAL_OWNER": "",
      "TECHNICAL_MANAGER": "",
      "VESSEL_TYPE": "GENERAL CARGO"
    }
  ]
}

Notice all number fields are not quoted and missing values which were before empty string are now null.

By comparision with the competition, vesselfinder returns a JSON with correct types.

Is there a way to get a JSON with the correct types, or is this planned in the near future?

Thanks for your help.

0

• 

  Under NDA

  • May 05, 2021 10:08
  • Edited

  Can anyone from MarineTraffic or the community provide me with an update on this issue?

  Thanks.

  0

  Comment actions Permalink
• 

  Valia Gelasiou

  • May 06, 2021 07:29

  Dear User,

  Thank you for your comment,

  We are looking at this issue and we will get back to you as soon as we have updates.

  Kind regards,

  0

  Comment actions Permalink
• 

  Valia Gelasiou

  • May 24, 2021 09:58

  Dear User,

  Thank you for the feedback.

  Indeed we have identified the issue you are reporting. We are planning to address it in the next versions of the API which will be launched in the future.

  We apologise for any inconvenience this might have caused.

  Kind regards

  0

  Comment actions Permalink

Please sign in to leave a comment.