August 2026 Updates

New Feature:

BAPLIE 3.1 (SMDG 3.1.1 / D:13B) support

What's new

BAPLIE Viewer Online now accepts and displays BAPLIE files sent in the SMDG 3.1.1 specification (also referred to as v3, D:13B, or SMDG31). Until now the site accepted only BAPLIE 2.x (D:95B / SMDG22); a v3 file was rejected with the message "BAPLIE files only support specification directory D.95B".

With this update:

A file whose UNH header declares BAPLIE:D:13B:UN:SMDG31 is parsed against the SMDG 3.1.1 mapping.
Containers, ports, carriers, hazardous goods, temperatures, dimensions, and other supported fields render in the 2D and 3D viewers exactly as they do for a v2 file.
The header banner and File Management columns show the correct version, 3.1 for genuine SMDG 3.1.1 files.
Additional identifiers used more often in v3 (IMO number, radio Call Sign in the TDT segment) are surfaced in the file header details.

Round-trip on Download

Every Download current version as BAPLIE option (Original, Original without NAD, Original without NAD full, Original without NAD full with only hazardous container numbers, Original stripped of RFF) has been updated so that when the uploaded file was BAPLIE 3, the downloaded file is BAPLIE 3 too, with all v3-only segments (CNT, HAN, ATT, extended NAD parties, temperature history) preserved from the original. Files downloaded before this update were emitted as BAPLIE 2 and lost those fields; from now on, round-trip is lossless.

Any edits you made in the viewer (container position, weight, hazardous flags, etc.) survive the round-trip. The version-specific converters (Download as v1.5, v2.0, v2.2, v2.2.1) continue to intentionally down-convert; those are unchanged.

Files that carry a v3 UNH but v2 content

Some senders label their files as v3 in the UNH header but the actual container structure inside is still BAPLIE 2.x. Uploading one of these now shows a clear message:

This file's UNH header claims BAPLIE v3 (D:13B) but the container structure looks like BAPLIE 2.x. Please contact the sender to confirm the intended format, or click below to re-parse it as BAPLIE 2.0.

A single click on Re-parse this file as BAPLIE 2.0 resubmits the same file with the correct spec and the viewer opens as normal. No need to re-drag the file, no need to change the dropdown manually.

Files that don't match any BAPLIE specification

If the file's UNH says v3 but the message type isn't a BAPLIE at all (for example, a Notification Report dressed up as BAPLIE), the upload is rejected with the message "This BAPLIE file does not conform to any recognised SMDG BAPLIE specification (invalid BGM code or missing mandatory segments). Please contact the sender."