Skip to main content

Do you support BAPLIE version 3?

Yes. BAPLIE Viewer Online supports the SMDG BAPLIE 3.1.1 specification (also referred to as v3, D:13B, or SMDG31) in addition to BAPLIE 2.x (D:95B / SMDG22 / SMDG20 / SMDG15).

A file whose UNH header declares BAPLIE:D:13B:UN:SMDG31 is parsed against the SMDG 3.1.1 mapping and opens in the 2D or 3D viewer the same way any BAPLIE 2.x file does. When BAPLIE 3 is enabled for your account, a small "BAPLIE 3 now supported" ribbon appears in the upload area as a reminder that you can drop a v3 file with confidence.

What renders from a v3 file

  • 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 identifier of the ship's radio Call Sign and IMO number where present in the TDT segment

What happens on download

When you use any of the Download current version as BAPLIE options on a v3 file, the resulting file is BAPLIE 3 too, with all v3-only segments (CNT, HAN, ATT, extended NAD parties, temperature history) preserved from the original. Any edits you made in the viewer are kept.

The version-specific converters (Download as v1.5, v2.0, v2.2, v2.2.1) are intended to down-convert to a target BAPLIE 2.x version; they were designed for v2 files and continue to work exactly as before.

Files labelled as v3 but shaped as v2

Some senders declare BAPLIE 3 in the UNH header but the actual container structure inside the file is still BAPLIE 2.x. In that case the upload shows a message explaining the mismatch, with a single-click Re-parse this file as BAPLIE 2.0 link that resubmits the same file with the correct specification. There's no need to re-drag the file or change the dropdown manually.

Files that aren't BAPLIE at all

If a file's UNH says v3 but the message type isn't actually a BAPLIE (for example, a Notification Report dressed up in a BAPLIE header), the upload is rejected with a clear message asking you to contact the sender.

Older BAPLIE 3 drafts

Support is targeted at the current SMDG BAPLIE 3.1.1 specification. Earlier SMDG 3.0 and 3.2 draft variants are accepted through the same code path but should be considered best-effort; contact support if any field doesn't render as expected.

Back to top