MEQPOS — EDIFACT Means of Transport and Equipment Position Message (D.10A)
The MEQPOS message conveys the current geographic position of a means of transport (vessel, train, truck) or equipment (container, trailer): timestamped geolocation, operational status, link to the resource. It is used for logistics track & trace and real-time dashboards. This page summarises the segment structure as published by UN/CEFACT for directory D.10A.
Purpose
The MEQPOS message conveys the current geographic position of a means of transport (vessel, train, truck) or equipment (container, trailer): timestamped geolocation, operational status, link to the resource. It is used for logistics track & trace and real-time dashboards.
This page focuses on the structure published by UN/CEFACT for directory D.10A. The segments listed, their status (M / C), position and repetition factor are extracted from the official file meqpos_c.htm hosted on service.unece.org.
Segment structure
The MEQPOS D.10A message has 24 header entries, 0 detail entries and 0 summary entries (segments and groups combined). Groups are shown in bold and their members are indented by actual nesting depth.
Header
| Pos. | Tag | Name | S | Rep. |
|---|---|---|---|---|
0010 | UNH | Message header | M | 1 |
0020 | BGM | Beginning of message | M | 1 |
0030 | DTM | Date/time/period | C | ×9 |
0040 | QTY | Quantity | C | 1 |
0050 | LOC | Place/location identification | M | 1 |
0060 | SG1 | Group (×9) | C | ×9 |
0070 | RFF | Reference | M | 1 |
0080 | DTM | Date/time/period | C | ×9 |
0090 | SG2 | Group (×1) | M | 1 |
0100 | TDT | Transport information | M | 1 |
0110 | DTM | Date/time/period | C | ×9 |
0120 | SG3 | Group (×9) | C | ×9 |
0130 | LOC | Place/location identification | M | 1 |
0140 | DTM | Date/time/period | C | ×9 |
0150 | SG4 | Group (×9) | C | ×9 |
0160 | NAD | Name and address | M | 1 |
0170 | SG5 | Group (×9) | C | ×9 |
0180 | CTA | Contact information | M | 1 |
0190 | COM | Communication contact | C | ×9 |
0200 | SG6 | Group (×999) | C | ×999 |
0210 | EQD | Equipment details | M | 1 |
0220 | LOC | Place/location identification | C | ×9 |
0230 | DTM | Date/time/period | C | ×9 |
0240 | UNT | Message trailer | M | 1 |
Detail
No segment in this section.
Summary
No segment in this section.
Changes vs D.96A
The MEQPOS message is not published in directory D.96A. No "D.96A → D.10A" comparison line can therefore be produced — see the block below for details.
This message is not published in directory D.96A: it was introduced into the standard after that release and therefore has no historical baseline for comparison. The first directory indexed on ediverse.io sets the reference; later changes are then documented from one release to the next in subsequent directories.
Structural example
Minimal example of an MEQPOS D.10A message with mandatory segments only. The goal is to show the exact version declared in UNH (MEQPOS:D:10A:UN) — not to replicate a full business case.
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL010001'
UNH+1+MEQPOS:D:10A:UN'
BGM+23+MEQPOS-2026-LIVE-091+9'
DTM+137:202605141430:203'
QTY+1:1'
LOC+162+48.8566:2.3522:LATLON'
UNT+6+1'
UNZ+1+CTRL010001'Common errors
- Misaligned UNH tokens — The
UNH+...+MEQPOS:D:10A:UNtoken must reflect exactly the directory in use — a mismatch between the UNH release and the release agreed with the partner is rejected by every strict validator. - Wrong UNT segment count — The value after
UNT+must include UNH and UNT themselves. By far the most common sender-side error, regardless of the directory in use. - Stale code lists — Between D.96A and D.10A, several code lists received new qualifiers (DTM status, RFF qualifier, NAD codes…). Reusing an older directory’s code tables triggers warnings or even rejections depending on the partner’s strict-conformance mode.
Related messages
Other versions of this message available on ediverse.io: MEQPOS D.16B, MEQPOS D.21B, MEQPOS D.24A.