Skip to content

Do you support BAPLIE version 3?

Yes. BAPLIE Viewer Online supports the SMDG BAPLIE 3.1.1 specification. It is also called v3, D:13B or SMDG31. The viewer also supports BAPLIE 2.x (D:95B, SMDG22, SMDG20 and SMDG15).

A file with the UNH header BAPLIE:D:13B:UN:SMDG31 is read with the SMDG 3.1.1 mapping. It opens in the 2D or 3D viewer in the same way as a BAPLIE 2.x file. When BAPLIE 3 is on for your account, the upload area shows a small ribbon: BAPLIE 3 now supported.

The upload area with the ribbon BAPLIE 3 now supported at the right

  • Container positions, ports of load and discharge, carriers and voyage details
  • Hazardous goods, temperature, dimensions, references and free-text notes
  • Multi-lift and bundled equipment groups
  • The ship’s radio call sign and IMO number, when the TDT segment has them

When you use any of the Download current version as BAPLIE options on a v3 file, the new file is BAPLIE 3 too. The segments that exist only in v3 stay as in the original file (CNT, HAN, ATT, extended NAD parties and temperature history). Your edits in the viewer stay in the file.

The converters for a given version (Download as v1.5, v2.0, v2.2 and v2.2.1) change a file into that BAPLIE 2.x version. They were made for v2 files and work as before.

A file that says v3 but has the v2 structure

Section titled “A file that says v3 but has the v2 structure”

Some senders write BAPLIE 3 in the UNH header, but the containers in the file still follow BAPLIE 2.x. In this case the upload shows a message that explains the difference. The message has the link Re-parse this file as BAPLIE 2.0. Click it to send the same file again with the right specification. You do not need to drag the file again or change the list yourself.

If the UNH header says v3 but the message type is not a BAPLIE, the upload is rejected. The message asks you to contact the sender. An example is a Notification Report with a BAPLIE header.

We support the current SMDG BAPLIE 3.1.1 specification. Files from the earlier SMDG 3.0 and 3.2 drafts open in the same way, but we cannot promise that every field shows correctly. If a field does not show as you expect, contact support.